Develop Bugs

[Q] Unable to fix bootloop - even tried STOCK flash in fastboot. No luck.

Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.

What is in the update image and where did you get it? I'd flash everything manually, skip the update command.

bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.

Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?

Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?

One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...

give a try to omap flash
Good Luck

samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?

Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center

samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.

While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus

bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?

Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus

Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!

lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app

I cannot downgrade my device... is it not allowed?

Hey guys, I have a Nexus 7 16gb 2013 wifi running 5.1.1 lollipop LMY48G.
I'm trying to downgrade it to kitkat so I can install some software the only works correctly on kitkat on it.
I follow this guide: laptopmag(.com)articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and whenever I finish, I get a green android laying down with a red caution symbol ontop of him.
But the weird thing is I'm able to install 5.1.1 no issues using the same method, but if I pick anything older... The green android shows up..
Right now I'm back on a fresh 5.1.1 install.
Is there something I'm missing? From all my googling it seems like I should be allowed to installed kitkat no issues on this device. What am I missing?

Diesel47 said:
Hey guys, I have a Nexus 7 16gb 2013 wifi running 5.1.1 lollipop LMY48G.
I'm trying to downgrade it to kitkat so I can install some software the only works correctly on kitkat on it.
I follow this guide: laptopmag(.com)articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and whenever I finish, I get a green android laying down with a red caution symbol ontop of him.
But the weird thing is I'm able to install 5.1.1 no issues using the same method, but if I pick anything older... The green android shows up..
Right now I'm back on a fresh 5.1.1 install.
Is there something I'm missing? From all my googling it seems like I should be allowed to installed kitkat no issues on this device. What am I missing?
Click to expand...
Click to collapse
Do you get that android after when you try to boot normally? If you turn it off and turn it back on again normally does it still show up? It is weird if it does because that sounds like the stock recovery, and shouldn't really show up unless you try to boot into it via the bootloader.
When you follow the guide, do you also do the last step, where you interrupt the reboot to lock the bootloader? If you do could you try to let it boot uninterrupted after the update?

theminikiller said:
Do you get that android after when you try to boot normally? If you turn it off and turn it back on again normally does it still show up? It is weird if it does because that sounds like the stock recovery, and shouldn't really show up unless you try to boot into it via the bootloader.
When you follow the guide, do you also do the last step, where you interrupt the reboot to lock the bootloader? If you do could you try to let it boot uninterrupted after the update?
Click to expand...
Click to collapse
Hello, Thank you for replying..
I ran the flash-all.bat from the 4.4.4 image files stock from google and it got this error:
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-04.05'.
Update requires 'FLO-04.02'.
I guess my bootloader is too recent? Google does not want us downgrading?
Update: I ran fastboot oem unlock and was able to run the flash-all.bat
Now i'm waiting on the device to boot up, its currently stuck on a black screen that has white text in the middle saying "google".
Update: It is permastuck on the google screen... I don't know what to do Also to answer your question, yeah I reboot it multiple times. It doesn't work. If I choose "start" from the bootloader it will be stuck on the black google page permanently.
Is there some way I can just wipe the device and install 4.4.4 on it? Kinda like a regular PC?

You need to flash the bootloader before executing the flash-all file. To do that boot into the bootloader then use the command
"fastboot flash bootloader 'bootloader file'"
where bootloader file is the file with bootloader in its name you got from your zip file. Then
"fastboot reboot-bootloader".
Then you can use the flash-all file.

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....

Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.

I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please

sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.

This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work

emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!

Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE

Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!

It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!

Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

NERVOUS about flashing Lineage 18 :-(

HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler

Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom

Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler

pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me

"too many links" error message when trying to boot into the recovery image through fastboot

hello! i've been trying to install a custom recovery on my redmi note 8 pro for a while now, everytime i flash it and try to boot to it through fastboot the logo appears, screen goes black for a second, reboots and boots to miui when i try to directly boot in it thru fastboot, i get a "too many links" error

igetalittlebitlazy said:
hello! i've been trying to install a custom recovery on my redmi note 8 pro for a while now, everytime i flash it and try to boot to it through fastboot the logo appears, screen goes black for a second, reboots and boots to miui when i try to directly boot in it thru fastboot, i get a "too many links" error
Click to expand...
Click to collapse
Be sure to run the latest ADB/fastboot. Check if other device/emulator is also connected. Avoid a hub USB, specially if your PC is running out of memory/RAM

SubwayChamp said:
Be sure to run the latest ADB/fastboot. Check if other device/emulator is also connected. Avoid a hub USB, specially if your PC is running out of memory/RAM
Click to expand...
Click to collapse
thank you, but i actually flashed the wrong vbmeta image and after reflashing a patched one twrp works! not the official one, only this one works https://sourceforge.net/projects/be...ic/Dynamic-TWRP-Begonia-23-12-21.img/download | do you know why standard twrp wont work but this "dynamic" one does?

igetalittlebitlazy said:
thank you, but i actually flashed the wrong vbmeta image and after reflashing a patched one twrp works! not the official one, only this one works https://sourceforge.net/projects/be...ic/Dynamic-TWRP-Begonia-23-12-21.img/download | do you know why standard twrp wont work but this "dynamic" one does?
Click to expand...
Click to collapse
Because dynamic partitions was introduced later, the old, still, didn´t support it.