Related
Kinda new to this so forgive me if i miss something somewhere and if i need to give more information somewhere just let me know.
With that out of the way I'd like to start with the fact that this is my first rooted device. Currently on C-spire (cellular south) if that matters.
A few days ago before the phone was rooted or even unlocked i went to make a phone call and the screen blacked out and a few seconds later went into a reboot loop where it would get to the Motorola Logo for about 6 seconds or so then shut off and try again ad nauseam until the battery died. After letting the battery die and connecting it to the charger it continued the loop so after a quick gogle search I began fiddling with buttons and realized i could boot into fastboot and recovery modes. I decided i might as well root since it couldnt get a whole lot worse and after a quick look around the forums and a trip to motorola to unlock my phone i was able to flash TWRP recovery, after which i accidentaly wiped the os, managed to find any number of replacement roms none of which solved the boot issue. I eventually found the stock Sprint roms which allowed the phone to boot and work for the most part, but it wont send media messages and has trouble picking up 4g service. I am also forced into using the sprint updater among other things which include having sprint plastered everywhere I have tried flashing several custom roms (pacman, paranoidandroid, and cyanogen) all of which get hung up booting just like the phone did before but the sprint stock rom will reload and work just as before. I'm not sure what would be causing this or if there is a way to fix it and i apologize for the wall of text. If any more info is needed let me know and ill provide ot to the best of my knowledge. Thanks in advance :fingers-crossed:
So all ROM's fail to boot?
Are you doing a factory reset in TWRP before you boot?
Are you flashing gapps? Although that shouldn't cause the phone to fail at booting...
Correct. All roms except the stock sprint rom fail to boot.
Now that i have everything backed up on my external sd I've tried factory reset using twrp as well as wiping everything prior to flashing a ROM as well as after but
Before booting. And the many combinations thereof
And yes i am flashing gapps.
You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.
arrrghhh said:
You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.
Click to expand...
Click to collapse
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though
AMerexican said:
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though
Click to expand...
Click to collapse
Every ROM should include a md5sum with it. If you're on Windoze, use a program like WinMD5 - check the md5sum locally, and compare it to what is on the server. If they match, the download is probably good.
So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?
AMerexican said:
So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?
Click to expand...
Click to collapse
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.
arrrghhh said:
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.
Click to expand...
Click to collapse
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
I suppose some sort of hardware issue. Like I said, I've flashed most of the newest ROM's here for the Q - all work fine. Hell, some I even ported myself...
I'm kind of at a loss. Can you get adb? Not even sure what to check for next... if you are wiping properly in recovery, that should be sufficient.
Hm, I guess that brings up a good point. Have you tried wiping system, flashing, doing a factory reset, then booting? Most, if not all of the ROM's should wipe /system before flashing... So it probably won't do anything different.
AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.
kabaldan said:
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.
Click to expand...
Click to collapse
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead
arrrghhh said:
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead
Click to expand...
Click to collapse
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot
kabaldan said:
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot
Click to expand...
Click to collapse
Ah, that makes sense - I was not aware of this apanic_console
Thank you!
arrrghhh said:
Ah, that makes sense - I was not aware of this apanic_console
Thank you!
Click to expand...
Click to collapse
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?
AMerexican said:
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?
Click to expand...
Click to collapse
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!
arrrghhh said:
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!
Click to expand...
Click to collapse
Thanks wasnt sure of the forums rules as far as that was concerned
http://pastebin.com/QFq1naK0
Any ideas?
Or anything else i need to do?
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?
Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.
Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.
Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.
Settings and command prompt pics showing problem
bb1981 said:
Yesterday afternoon at work, I rebooted by m8 (Verizon) and didn't realize there was a problem because I put it back in my pocket before it was fully booted. Next time I looked at it, I had no signal and digging deeper, I saw that the baseband is "Unknown" in settings and the IMEI is "U nkn own". I've tried the RUUs for 4.4.3 and 4.4.4 and can't get the phone to see the IMEI and baseband while booted but both show up fine in hboot/fastboot as shown in the attached pics in the next post. I was running the Viper rom when this happened.
Click to expand...
Click to collapse
bb1981 said:
Settings and command prompt pics showing problem
Click to expand...
Click to collapse
Do you always run it in airplane mode?
?
I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.
bb1981 said:
I didn't even realize that when I took the pics but without putting it into airplane mode, it would sit at the htc logo indefinitely until a few minutes pass and it reboots only to get stuck in that cycle unless I jump in and power off. I did forget to mention the reboots after a few minutes in the OP also in case that changes what the issue could be. This was coming off the 4.4.3 RUU and I had the same issue with 4.4.4 and also Sinless 3.5.5(?). It worked great before and I'm just hoping it isn't hardware failure.
Click to expand...
Click to collapse
Which method did you use for the RUU? Exe or sd?
Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.
bb1981 said:
Initially, I used the exe version but when it have the version number it was going to upgrade to, it was unreadable. Going back to 4.4.3, I flashed the firmware through fastboot then ran the ruu off the sd card. That's also why the sd card is ejected in the first pic so I could get past hboot to make sure it completely powers off.
Click to expand...
Click to collapse
Did you try a factory reset from stock recovery/hboot yet?
I'll try that next. I just tried it but it seems like I don't have a recovery installed. Instead of saying recovery booting, it just bootloops.
just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.
bb1981 said:
just tried flashing stock recovery and got stuck in a bootloop again. Running the exe again to try 4.4.4 and still get the same unreadable upgrade version. The version that it's coming from has been right all the time, but the version it's going to I'm guessing should be 3.xxxxx instead of like the screenshot attached.
Click to expand...
Click to collapse
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.
dottat said:
That's fine man. It's not an encrypted rom so it doesn't read the plain text file correctly. It will flash what it's supposed to.
Click to expand...
Click to collapse
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:
bb1981 said:
That's a relief to see that. After I ran it I wasn't sure because it gets stuck on the setup splash screen (thinking it was something not reading correctly on my end and even tried running a second time right away) and I can't get past it at all without airplane mode. I'll have to keep working on it later and see what happens. Thank you for the replies and help, especially with the RUU files and hopefully I can get it figured out. :fingers-crossed::highfive:
Click to expand...
Click to collapse
Did you try flashing the newest twrp 2.8.0.3 recovery ?
Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.
Roefastford said:
Did you try flashing the newest twrp 2.8.0.3 recovery ?
Click to expand...
Click to collapse
Twrp does work although I haven't tried it this time just to see if I could try a factory reset to maybe get back my lost baseband and IMEI.
smeejaytee said:
Fyi 4.4.4 roms can take up to 20 mins to get to the initial set up screen you might want to hang in there.
Click to expand...
Click to collapse
I wish I could. The phone once booted will reboot itself after a few minutes.
Oh ok sorry that didn't help.
smeejaytee said:
Oh ok sorry that didn't help.
Click to expand...
Click to collapse
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?
bb1981 said:
I apologize if the last reply was short and possibly coming across snippy...I was at work and didn't have longer to reply...I think I may have made some very sight progress but the phone still knows nothing about itself once booted. I flashed twrp then wiped system, data, cache and dalvik then proceeded to flash unsense 6 and the 4.4.4 insecure kernel which is recommended by the developer for this rom. It booted fine and on the just a sec screen (right after the language selection on aosp/gpe), I did the four corner tap to bypass setup, enabled dev options, then had it connected to my laptop collecting a logcat for when it rebooted to see if it could show someone who knows far more about android than I do what could be causing trouble. The only problem this time is it never did. Almost like taking a car into the mechanic and somehow it knows and doesn't misbehave.... In fact, I feel asleep for a short time and when I woke up again, the command prompt never changed indicating that it ran the whole time without a reboot. At that time, I powered off and called it a night. Is it possible for a partition to become corrupted causing this?
Click to expand...
Click to collapse
Partitions can get corrupted but as far as I'm aware the only way to fix it is with soff I'm not positive because there is an option in twrp to repair partitions also you may be able to use that without soff.
_)(_(45466_!!$$%[¥|[]®]«¥°]<<° xda app...why do I not have permission to post? [/rant]
I picked up a replacement gunmetal gray m8 on swappa and am considering putting the red one up on the boneyard there to give someone a chance to poke around with it. I was wondering if a partition that twrp doesn't have in the repair section like the one for radio/modem for instance could get damaged. The RUU should take care off any problems like that though so I'm officially stumped and haven't really had any extra time to do any troubleshooting.
bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse
dottat said:
bb1981 said:
_)(_(45466_!!$$%[¥|[]®]«¥°]
Weird quotes too...the app doesn't like you lol. If you are replacing it can you send me the broken one so I can better try to support this device?
Edit...I know you probably will get pm requests for that too. I'm all about unbricking HTC phones and I'm sure there's enough people around here to back that up between my ruu support and all.
Click to expand...
Click to collapse
I finally got wise and did a copy and paste after something like 5 times saying I didn't have permission lol....that sounds like a great idea. More (and better) support and understanding is always good.
Click to expand...
Click to collapse
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
EDIT: More googling today. Looks like my E:/Persist partition is corrupted or something, trying to figure out how to repair it right now.
Anjo_Smash said:
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
Click to expand...
Click to collapse
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
bitdomo said:
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
Click to expand...
Click to collapse
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Anjo_Smash said:
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Click to expand...
Click to collapse
I made a thread about it. Here it is http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
I made a thread about it. Here is it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Anjo_Smash said:
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Click to expand...
Click to collapse
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
bitdomo said:
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
Click to expand...
Click to collapse
Thanks for the offer. I'll try on my own and get back to you maybe tomorrow if I can't get it down.
Alright so I am definitely having problems running adb shell. even if I change the directory in cmd to my adb.exe location (android\android-sdk\platform-tools) I keep getting the error adb shell is not a recognized blah blah blah....
NVM got it working. Whenever I get frustrated enough to make a post I end up finally finding a solution.
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Anjo_Smash said:
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Click to expand...
Click to collapse
Just copy them to the root of your internal storage, then follow the guide.
I mean you just open the phone's internal storage from your PC and you dont open any folder. You just copy it there.
The guide is for nexus 5, but some people refer to the internal storage as sdcard too. I know it is a bit confusing. Thanks to point it out. I will make clear in my guide now.
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Anjo_Smash said:
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Click to expand...
Click to collapse
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
bitdomo said:
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
Click to expand...
Click to collapse
Should I try formatting it again?
Anjo_Smash said:
Should I try formatting it again?
Click to expand...
Click to collapse
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
Ok I'm going to install team viewer then.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
I'm all set up, so let me know when you are available friend, thanks for your help.
Anjo_Smash said:
I'm all set up, so let me know when you are available friend, thanks for your help.
Click to expand...
Click to collapse
I am here, send the login infos -> [email protected]
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Hi,
Can you boot into bootloader?
Press power button until phone reboots while keeping volume down pressed.
From there you can install a factory image.
What version are you actually on?
Good luck,
Sébastien.
niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
Flash the stock kernel (partitions) via Fastboot.
most users having issues like this end up getting it up and running using Google's official Android Flash Tool . It takes a lot of guesswork and/or misfires that a lot of users end up hitting the wall at...
I suggest making sure to check "don't wipe" or "keep data" (sorry, I've only used it twice, so going off of memory is foggy) so it doesn't return the device to stock...
niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
did you disable Verity and verification before flashing the kernel?
It's frustrating when someone posts a problem then never follows up
HipKat said:
It's frustrating when someone posts a problem then never follows up
Click to expand...
Click to collapse
It's why I've relegated myself to editing the title "SOLVED" for members on their threads, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
simplepinoi177 said:
It's why I've relegated myself to editing the title "SOLVED" for members, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
Click to expand...
Click to collapse
Hey,
Most likely solved it by himself, since he didn't show up since 5 minutes after his post
Anyways, hopefully, people's experiencing the same issue will find this thread with possible solutions (before opening a new thread).
Cheers,
Sébastien.