Nexus 5 script completes ok(?), vendor OK but bootloops?
Page 1 of 1 (12 posts)
Tags:
None
Registered Member 
|
I read through the answered post below, and am experiencing similar outputs showing what appears to be an OK execution minus a minor non fatal mounting error, however did not achieve success and only have TWRP recovery mode working. It seems easy to navigate but I am unable to locate any images to reload from on the device or just don't know where to look, so am still using the guide at https://docs.plasma-mobile.org/Installation.html but with little change in results.
After which, I am in bootloop. If I force a fresh fastboot an execute the vendor script I get this:
and remain in fastboot mode, able to reboot.... but only into a bootloop or TWRP recovery. Can't find the solution in any of the threads, and searching has produced some progress but not past the point I'm at now. Desperate for a hand, if anyone can be so kind to offer it so this Nexus 5 dosen't become a 50 dollar brick on me. Cheers folks. Thanks in advance (: |
Registered Member
|
@personn I'm pleasantly surprised with your post, a port X5
Well, I bought yesterday a Nexus X5 35GB. (Marktplaats, a nice price to, 85 bucks (in Euro  With the intention to port Plasma on the X5.If you like working together?... In this project, you're welcome. Maybe we can complement each other. But first tings first, install an SSD drive in a Mac Mini mid 2010. Then build on Darwin-shell KDE Neon. Those are the things for this coming time. I'm not authorized to fill in a signature, Moderator? What's the difference, Cheers, Erwin
What's the difference
Kind greetings from The Netherlands |
|
Registered Member
|
I've reloaded back to android 6 and started over from scratch, but only get the same result.
Why does no one have the answer? This is such a common problem it seems and the vendor script doesn't fix it. |
|
Registered Member
|
I think it went wrong in the beginning, have a look here https://docs.plasma-mobile.org/Installa ... ght=vendor and sneak around on the xda forum
What's the difference
Kind greetings from The Netherlands |
|
Registered Member
|
I think you're right. I followed an outdated guide the first time and it instructed me to unlock the bootloader which did get completed, but I think maybe the TWRP provided root (according to the XDA guide link) is not compatible / responsible for my issue. I don't know if I can revert, but I'll try the XDA method for unlocking now that I'm back on android 6. I'm not using a 5X just a 5, but I don't think that matters. Only problem is the option the XDA guide says to look for isn't there: https://forum.xda-developers.com/nexus- ... s-t3206930
USB Debug was there, OEM unlock wasn't. I'm using Android 6.0.1 The tools all seem to complete, and while in the bootloader the messages show 'secure boot enabled' but 'OEM Unlocked' The only info I got on secure boot was that it didn't matter overall. So I'm thinking the problem is rooting, which from what I can tell never gets done in the installation guide and / or in step 1 of the XDA guide. The XDA guide gives instructions which go above and beyond unlocking and are for loading other softwares not just Plasma mobile, so am I better off trying to install the software using this other guide, or can I stop after step 1 - Unlocking the bootloader? (this will not offer root however) I think I have to go step 1 - 6, but I am not sure if the android recovery files are still on the phone. After flashing back to android with TWRP, I can no longer enter recovery mode without doing another flash. If rooting is necessary part of the process, I think the reason many users hit the bootloop is like me, they just didn't know they had to root; it wasn't in the primary instructions. |
|
Registered Member
|
Did you root your device before starting your install? That seems to be where I went wrong. Will post more updates as I advance the hopefully final, attempt. |
|
Registered Member
|
Well apparently the Super SU project fell apart in 2016 or something because drama.... so now there is no way to root?
I suppose plasma mobile will also soon too be abandoned as a result of this. |
|
Registered Member
|
.
Last edited by personn on Mon Apr 15, 2019 5:23 am, edited 1 time in total.
|
|
Registered Member
|
 Have a look to this friendly community, several channels include Plasma Connect https://telegram.me/username Telegram (kde connect devel) And https://phabricator.kde.org/project/profile/159/ But I will recommend you find out more in the XDA dev’s Success 📲 |
|
Registered Member
|
I'm sorry, I'm an asshat when I get frustrated; not an **** in general. But I could be wrong.
Well I DID root the device this time, verified within android and the super su app - - prompted for access etc... but was never asked to enter the root password during the neon install as the guide suggested I would be. The script completed and everything else, vendor good, same result: google bootlooping. Here is my output this time, I didn't see any changes
Presently sitting with TWRP 3.2.3-0, SuperSU v2.62-3-20151211162651 on Android 6.0.1; Super SU updated to 2.82 from google play after rooting in recovery mode with 2.62 (opted out of the supersu offered from twrp) |
|
Registered Member
|
Sorry, I can read... Your X5 is not rooted, its stil Hammerhead woh play the drums.
 "Google is your best friend" Because your data tels me you X5 is running on Hammerhead, your phone thinks.... Root me 4 the first time. Well, Google is your friend, when I ask Google: "How to root a Nexus X5" is read on de first row! Root Your Nexus 5—An Easy Guide for First-Timers Here your link, read carefully and succes: https://nexus5.gadgethacks.com/how-to/root-your-nexus-5-an-easy-guide-for-first-timers-0150493/
What's the difference
Kind greetings from The Netherlands |
|
Registered Member
|
I don't use windows so this is not a helpful reply, but I appreciate your answer.
If google was my friend, I wouldn't need to switch from android to linux on my phone  I followed the XDA guide and from what you are telling me the rooting isn't going right even though the apps are reporting the root is complete and like I said, the SuperSU project was abandoned or bought out by anti-open source establishment programmers who only remove the software now. Starting to think again, this is a hopeless venture for anyone who is not a developer but understands a terminal window. |
Page 1 of 1 (12 posts)
Bookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]
