Android M Boot Error - Nexus 6 Q&A, Help & Troubleshooting

I do realize I am beating a dead horse but I'm having trouble finding the specific answer that I'm looking for. When I first flashed M Dev preview the day it was releaser I did not get the boot error. I rooted got the error, then it wouldn't boot until I flashed a custom kernel. We all know that this is what needs to be done.
However, I've flashed stock lollipop and gone back to M several times, stock recovery, correct boot loader and wiped all data and cache several times however I am still getting the boot error. Now all you have to do is wait the 5 seconds or however long it is and the device boots fine, but I've also noticed that ever since this began happening back when I first rooted, my LTE signal indicator goes away. I still have data and I can still use the device to get online and such. I wouldn't really are except there's one thing, when the LTE indicator goes away I can't make calls either. I am not set to LTE only or anything, I have the correct radios flashed and it doesn't matter what I do.
I can flash factory images manually or in NRT and I still get the boot error, and I still get the signal issue.
Don't worry so much about the LTE issue because I feel like it is caused by whatever is wrong and causing me not to be able to go back to complete stock.
I just need some advice on how go back to TOTAL stock, (UNrooted, stock recover, stock kernel, stock everything) so I will no longer get the boot error.
Thanks in advance to anyone who is willing to help.

jonzey231 said:
I do realize I am beating a dead horse but I'm having trouble finding the specific answer that I'm looking for. When I first flashed M Dev preview the day it was releaser I did not get the boot error. I rooted got the error, then it wouldn't boot until I flashed a custom kernel. We all know that this is what needs to be done.
However, I've flashed stock lollipop and gone back to M several times, stock recovery, correct boot loader and wiped all data and cache several times however I am still getting the boot error. Now all you have to do is wait the 5 seconds or however long it is and the device boots fine, but I've also noticed that ever since this began happening back when I first rooted, my LTE signal indicator goes away. I still have data and I can still use the device to get online and such. I wouldn't really are except there's one thing, when the LTE indicator goes away I can't make calls either. I am not set to LTE only or anything, I have the correct radios flashed and it doesn't matter what I do.
I can flash factory images manually or in NRT and I still get the boot error, and I still get the signal issue.
Don't worry so much about the LTE issue because I feel like it is caused by whatever is wrong and causing me not to be able to go back to complete stock.
I just need some advice on how go back to TOTAL stock, (UNrooted, stock recover, stock kernel, stock everything) so I will no longer get the boot error.
Thanks in advance to anyone who is willing to help.
Click to expand...
Click to collapse
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=2954008
Follow method #2.

Evolution_Tech said:
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=2954008
Follow method #2.
Click to expand...
Click to collapse
You, my friend, deserve a 4th of July beer. ?

Related

[Q] Stock Rogers Canada ROM

Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
try this: http://forum.xda-developers.com/showthread.php?t=867617
There are others like it too. Just don't try flashing the bootloader or sbl !
AbsoluteZero said:
Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
Click to expand...
Click to collapse
Gin's got you on the right path for sure. A couple more items for you:
This post should help with removing the AT&T bootup logo: http://forum.xda-developers.com/showthread.php?t=849789
If you use Heimdall to flash the Rogers stock firmware that is in the post the Gin linked to then you will absolutely need to follow the instructions to use the Heimdall drivers for your captivate when it's connected or it won't see the device when you tell it to start. Like gin said, don't touch primary or secondary bootloader, leave those out and don't try to repartition it.
Restoring the stock firmware will remove the custom kernel that is installed with Cognition (at least it should) and so the Clockwork recovery should no longer be installed once the restore to stock is done. You can double-check once you are back to stock by powering off the phone and then hold both up and down volume + power, let the power button go after it restarts once and you see the I896 for the 2nd time. It should take you to the stock 2e recovery screen. If it does, you should be golden.
HTH
Wow, thanks all,
I used that method without the PIT file,
I just want to say thanks to everyone that offered help,
Goina try to send it for warranty now.
thanks again,
Joe / AZ

[Q] HTC Hero looping on the boot screen. How can this be fixed?

Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...

ICS update now phone just reboots

how can i fix this and its frustrating phone was working fine and when i update it does nothing but reboot...when i am in safestrap, the "install" tab is not lit to be able to select, so i can not even install a different rom on there....is there a way to fix this
If you are stuck in a bootloop, probably going to have to flash the .246 fxz to get you to stock OTA untouched and then roll from there. I went through this back in ancient days of yore with the DroidX and Froyo, had to fxz(sbf) the phone.
scottyd035ntknow said:
If you are stuck in a bootloop, probably going to have to flash the .246 fxz to get you to stock OTA untouched and then roll from there. I went through this back in ancient days of yore with the DroidX and Froyo, had to fxz(sbf) the phone.
Click to expand...
Click to collapse
It would boot up to the normally then a minute later it will automatically reboot I had flashed .246fxz and still the same issue...I did noticed that the baseband build was "unknown"......so makes me think that something was not flashed or updated right...the reception bar has a red circle with a line thru the center....so I hope somebody understands this and can help me out...
vk4559 said:
It would boot up to the normally then a minute later it will automatically reboot I had flashed .246fxz and still the same issue...I did noticed that the baseband build was "unknown"......so makes me think that something was not flashed or updated right...the reception bar has a red circle with a line thru the center....so I hope somebody understands this and can help me out...
Click to expand...
Click to collapse
Redownload the file from another source and flash it. You also might want to boot into the stock recovery and do a complete factory reset if you haven't already. I also have had to do this on previous phones I've owned when updating.

[Q] only boots into recovery

ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.

Note 3 4.4.2 ATT [ROOTED] Bootloop type glitch

hello,
ive been searching around for about an hour and i havent found a thing.
Let me describe my phone:
Safestrap
rooted
android 4.4.2
Scenario:
got a nasty ad virus yesterday, so i restarted my phone today and went into safestrap. Then i installed my previous back up from about a month ago. (not sure if i needed to delete anything left of the device) I restored data and system and it worked fine. I was in android for about 5 minutes then it restarted. so i assumed it was normal then it did it continuously.
First off im not sure what a bootloop is but i assume it doesnt post to the android system and continuously loops the boot logos.
Whats happening to me is that my phone will boot for a few seconds, sometimes minutes, and i can get on android for a few. Then the phone restarts. Ive been looking around for a few hours now and i cant find a fix or a way to restore my phone to the restore i made on 4/22/17.
ANY help would be greatly appreciated and please correct me if i did something i wasnt supposed to.
If you need more info i will gladly post more
-LL
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Sicuro said:
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Click to expand...
Click to collapse
I got it fixed i had to flash a new stock rom and root it again. up and running from a softbrick. Its also running Android 4.4.2

Categories

Resources