TWRP bootloop - Galaxy S 4 Q&A, Help & Troubleshooting

Hi, I've just done a standard factory reset while using TeamCanjica Cyanogenmod 12 ROM for I9500. Now it's looping with the "teamwin" screen, even when doing a standard boot (not willing to go to recovery). The recovery isn't loaded either, it just loops on that screen.
I've tried to reinstall the recovery with ODIN, but the same happens.
Any idea? Thanks

Likely a hardware issue. One or possibly both buttons in the key combo may be stuck.

It happened just after doing the factory reset. I disassembled the phone and cleaned it completely, but it's still looping.

Try booting into fastboot and running
fastboot erase cache
fastboot reboot
Hope this helps

ndlarsen said:
Try booting into fastboot and running
fastboot erase cache
fastboot reboot
Hope this helps
Click to expand...
Click to collapse
No Samsung device has fastboot.

Lennyz1988 said:
No Samsung device has fastboot.
Click to expand...
Click to collapse
Guess I gave a useless advise and stand corrected, then.

I've just fixed it. It turns out that there wasn't any hardware issue, it seems like some boot code got corrupted. The only way I found to fix it was to flash stock firmware and repartition the device.
Thanks anyway folks

Related

[Q] Nexus 7 gets stuck booting. Tried reflashing stock OS multiple times.

I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
evenstevens said:
I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
Click to expand...
Click to collapse
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Red Devil said:
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Click to expand...
Click to collapse
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
evenstevens said:
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
Click to expand...
Click to collapse
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Red Devil said:
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Click to expand...
Click to collapse
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
evenstevens said:
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
Click to expand...
Click to collapse
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Red Devil said:
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Click to expand...
Click to collapse
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
evenstevens said:
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
Click to expand...
Click to collapse
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
evenstevens said:
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
Click to expand...
Click to collapse
Okay my solution to this:
Just keep flashing it with the flash-all.bat command until it just... worked.
Must've done it about 15 times.
Well that's that ordeal over.

[Q] Need help! Did OTA update to 5.0, stuck in bootloop!

I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.
Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol
alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.
Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.
They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.
Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.
That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.
Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.

Phone seems dead

Hello,
I get an infinite bootloop with my phone, to boot it i did, fastboot reboot-bootloader and fastboot-continue. That worked fine, then i did a firmware update (i was on stock rom, but rooted), then my phone is still doing a bootlop, i tried everything but i now i am not able to detect it in fastboot, so i can't boot my phone in normal mode, and in recovery mode. The only things i get is fastboot but undetectable :/
I would like to know what to do for getting my phone resetted to a cyannogenmod rom.
Regards.
Check drivers... Than you 1st aid ( general forum thread )
I did, but my phone is still not detected, i tried with all OS (win/unix/mac). Everything is installed..I don't know what to do
Teledor said:
Hello,
I get an infinite bootloop with my phone, to boot it i did, fastboot reboot-bootloader and fastboot-continue. That worked fine, then i did a firmware update (i was on stock rom, but rooted), then my phone is still doing a bootlop, i tried everything but i now i am not able to detect it in fastboot, so i can't boot my phone in normal mode, and in recovery mode. The only things i get is fastboot but undetectable :/
I would like to know what to do for getting my phone resetted to a cyannogenmod rom.
Regards.
Click to expand...
Click to collapse
it happened to my opt too
ronyjarod said:
it happened to my opt too
Click to expand...
Click to collapse
what to do?
Did you check your Volume Buttons? Had this Problem with a friends OPO where the Volume Button was bent and so the Phone only booted to Fastboot.
Teledor said:
what to do?
Click to expand...
Click to collapse
solved accidentally. what i did was typed fastboot boot OP2_recovery .img (not in the fastboot mode but at the stuck boot logo mode). i don't know how the img went in but that was the way saved my opt from bricked. anyhow, thank you for the reply

Stuck in a sort of bootloop after flashing factory android 4.2.2

So after booting up the phone after a few months, it only booted into the recovery and couldn't get into the system, so I decided to flash the factory android, but after flashing it using the included flash-all bat file, this is happening:
youtu(dot)be/P24gyQDcx98 .
So any ideas how to fix it? At this point I'm only able to get into the fastboot mode.
mnpj22 said:
So after booting up the phone after a few months, it only booted into the recovery and couldn't get into the system, so I decided to flash the factory android, but after flashing it using the included flash-all bat file, this is happening:
youtu(dot)be/P24gyQDcx98 .
So any ideas how to fix it? At this point I'm only able to get into the fastboot mode.
Click to expand...
Click to collapse
Nevermind I got it working, I propably had some weird fastboot and adb in my pc, I downladed them again from google and it worked.

Oneplus 7T Pro Mclaren edition - Stuck in fastboot.

Recently tried the flash-all.bat without any luck.
When in the menu, choosing power off or recovery mode, will just reboot it into the fastboot.
The bootloader is currently unlocked.
Thanks.
@tommiti
To leave fastboot mode try this
Code:
fastboot devices
fastboot reboot
jwoegerbauer said:
@tommiti
To leave fastboot mode try this
Code:
fastboot devices
fastboot reboot
Click to expand...
Click to collapse
Thanks, that did work.
I did enter the recovery mode, then I did a system restore.
The issue now, is that it keeps being stuck on the startup-screen(Mclaren-logo).
Any suggestions?
Thanks.
tommiti said:
Thanks, that did work.
I did enter the recovery mode, then I did a system restore.
The issue now, is that it keeps being stuck on the startup-screen(Mclaren-logo).
Any suggestions?
Thanks.
Click to expand...
Click to collapse
You could try this thread:
https://forum.xda-developers.com/7t-pro-mclaren/how-to/op7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
Good luck!
You probably did something funky like I did.
They fastbooting to your other partition.
If that works, restart the entire flashing and rooting process over again.
If you mess up a step, for some reason the b partition gets installed / flashed too, but never marked to boot from.
So that's how you can test a proper boot and hopefully get it set properly.

Resources