Develop Bugs

[Q] boot loop on reboot

Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:

You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img

BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail

In fastboot type fastboot erase cache

Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?

With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?

BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.

Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.

I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.

same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.

boot.img

Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.

BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics

Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.

[Q] Need assistance, please

Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
4. flashing the CM10 on my SXS with built number *.2.55 will work?
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.

chossen said:
Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.
Click to expand...
Click to collapse
I dont have an Xperia yet, but from reading and experience from other phone ...
1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware.
2) if you wiped, try to restart with flashing the firmware again and wiping everything.
3) if nothing working reflash stock, boot stock once to see if it is working without bootloops and then restart from scratch.
4) if also not working .... is it the correct firmware? did you forget something?
There are good instructions for the firmwares, if you do everything as explained, you shouldnt get bootloops. But ... no howto is perfekt.
Its mostly trying as much as possible, till you have the correct way to flash a firmware. Bootloop isnt that bad ...
If you have a way which works for you, keep the steps for later flashing and tell the community what you had to do differently or if you missunderstood some points, even then tell it, because that can make these instructions better.
---------- Post added at 04:36 PM ---------- Previous post was at 04:31 PM ----------
chossen said:
4. flashing the CM10 on my SXS with built number *.2.55 will work?
Click to expand...
Click to collapse
I would say that it doesnt matter which firmware is on the phone, as long as you unlock the bootloader and the fastboot or flashtool is working.
The custom firmwares use the same methods but might have added recovery for easier flashing later.
You should even be able to downgrade to older firmware with unlocked bootloader and flashing the ftf file.
Its only important to wipe the data, cache and dalvik cache that the firmware is working.

thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?

chossen said:
thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?
Click to expand...
Click to collapse
With different phone and different firmware i had some issues with recovery, specially if i didnt wipe directly after flashing the new firmware without reboot and without reboot into recovery ...
I hope i dont mix anything up. CWM is the recovery (?)
The recovery function is part of the kernel image which is exactly the boot.img.
You can see at the freexperia project page howto install CM10, i cant post links at the moment.
3rd point is flashing the CM kernel (boot.img)
4th point is booting into recovery
From that recovery you can flash the custom rom as described in point 5.
Point 6 is wiping the device, which is neccessary for first custom rom or if you change version (eg. CM9 to CM10) or if you change to a different ROM.
Most bootloops happen if you forget to wipe the device. I am not sure, but most important is dalvik cache, if that one is wiped the next boot takes longer, as it will be rebuilt during boot.
If you get into a bootloop after flashing kernel and custom rom, go into recovery and wipe the device, try rebooting.
If still in bootloop, try to reflash the custom ROM as in point 5 (starting at 4th point) and wipe device after flashing
If it didnt help, try reflashing the kernel and ROM, starting at point 3 and include the wiping the device.
If that didnt help, try to go back to full stock (kernel and rom) and repeat.
But check if you got the correkt ROM for your device.
Play a bit around with the steps, you can even reflash the kernel and leave the rom. I had once a bad situation with bootloops, but they are easy to fix. More important is the part with the kernel, i think there you can brick your device.
But when you follow the instructions you shouldnt have too many problems, just dont jump over a step at the first flashing. But as allways sayd, every custom rom, every kernel flashing can harm your device and you're responsible on your own.
But if you get into problems, write down what you did and you will get help here.
Edit:
"if not possible then reflash the firmware ..." There i had once a problem with a different device. I forgot to wipe after flashing a new version and got into a bootloop. In recovery i couldnt wipe the device fully, something got bugged, but reflashing helped. Reflashed wiped and i could reboot into system. As it was longer time ago i dont remember what exaclty happend, but i think the problem was about forgetting to wipe the device.

Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium

chossen said:
Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
didnt take too much time
in case of first custom rom, changing custom rom version (e.g. CM9 -> CM10) or changing to a different custom rom: all: factory reset, cache and dalvik
in case of updating (e.g. CM10->CM10): dalvik should be enough, maybe cache and dalvik.
If something not working, do a complete wipe.

As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app

daddyc00l said:
As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
No, he has no bootloops, from what i understood he is scared to get into bootloops and doesnt know what to do if it happens.
Hmm, kernel flashing after upgrading from ICS to JB? or all the time?
By kernel flashing you mean the boot.img flashing with fastboot, and its the same file as flashed before?

I've only ever fastboot'd my first kernel, advanced stock kernel. Any others have always been in recovery and never had any issues
Sent from my Android 4.2.2 Xperia S

It seems that you got the wrong Kernel. I'm not sure, of course.
But I had that issue some time ago, and a fix it flashing the right kernel that I found on xda forum. Ohh, dont forget to do the proper wipes.
I hope u solve this as soon as possible.

For some good info on recovering a phone read through the recovery thread in my signature.
Even if you don't have any issues now, you can see what others have done wrong & right.
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread

[Q] [need help] every ROM get's stuck on boot animation

I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance

As you already tried TWRP and not working, here is something u can try...
1)Flash Original miui for redmi 1s
2)then flash philz touch through stock recovery
3)then try to install CM 11 or other ROM
Not sure if it will work for you but you can try
BANG that THANKS button

lanadekat said:
I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance
Click to expand...
Click to collapse
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks

presetz said:
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks
Click to expand...
Click to collapse
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.

lanadekat said:
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.
Click to expand...
Click to collapse
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me

presetz said:
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me
Click to expand...
Click to collapse
oh haha I didn't notice you were the same guyI thought you linked me to someone else's post xD I'll try it, I hope it works!
edit: thanks! reflashing the kernel, wiping everything, then fixing the permissions ( but not the SElinux permissions ) fixed the problem for me I'm back to android 12.1
I'll see if I can close the thread.

SOLVED

Hello,
It sure has been a while since I've posted in this forums. I am having some trouble on my phone. Here's the story: I was on MIUI 7, but didn't like the way it was handling memory. It kept closing apps even when there were only 3 running, so I decided to restore a previous CM backup. So, I did that and rebooted the phone. It gave an error saying that "Encryption was interrupted", yet I have never encrypted my phone. Anyway, I decided to flash CM12 with a zip I had. Rebooted, and same problem occurred. Now, I'm trying to reboot phone into recovery, but whenever I do, the screen goes black and re-displays the teamwin logo, and just does that over and over. I tried flashing recovery through fastboot, but same problem. Is my phone savable? It should be, as it isn't hard-bricked. Any help is appreciated!

How do you solve this problem? When I flash CM12, the phone repeat reboot and can't enter recovery. At last I flash the Omini ROM.

Just flash stock rom
flash stock recovery.. go to wipe data and cache.. it will work.. if not try restoring partition with the stock recovery..
you can find stock recovery in oppo community
JackYao said:
How do you solve this problem? When I flash CM12, the phone repeat reboot and can't enter recovery. At last I flash the Omini ROM.
Click to expand...
Click to collapse

sydtek said:
flash stock rom.. go to wipe data and cache.. it will work.. if not try restoring partition with the stock recovery..
you can find stock recovery in oppo community
Click to expand...
Click to collapse
Thanks, I solved the stock recovery. And wipe data and cache, but still can't flash CM rom. At last, I flash the Omini rom. Problem is it often prompt me "Storage space running out".

Try flashing oppo's stock recovery
You can only instal oppo's rom (I.e. ColorOS) in that recovery.. First you have to flash TWRP recovery and then instal the CM rom.. This will work perfectly fine, but in some case like the above the rom would not boot into CM or whatever custom ROM.. In that case you have to instal OPPO's stock recovery to make it work..
And also the insufficient storage problem can be solved by OPPO's stock recovery by using partition - restore partition..
JackYao said:
Thanks, I solved the stock recovery. And wipe data and cache, but still can't flash CM rom. At last, I flash the Omini rom. Problem is it often prompt me "Storage space running out".
Click to expand...
Click to collapse

TWRP acts weird, crashes and breaks ROMs when reloaded.

Hey guys, could one of you please tell me how to do a complete wipe?
I'm having so many problems with TWRP at the moment, and so I want to nuke the partitions in hope that it'll fix it. I've tried using the fastboot format commands for system, data & cache. I've also tried to wipe the recovery, but it gives me the error "Formatting is not supported for filesystem with type ' ' ". So for that I just use format erase and flash the recovery again.
The only other partitions I know of are the boot and bootloader, but I don't want to touch them if at all possible.
The problem I'm having and why I want to wipe sotrage is that if I install sultan's LinageOS (haven't tested with other ROMs yet), TWRP ****s the bed and will make the device undetectable from ADB, (while TWRP is still running though), and if I then try to go into TWRP again, it'll hang, crash, and somehow make the ROM think its just been freshly installed again (data partition corruption?), and it'll do that every time I reboot from then on. The only way to fix this is to wipe the phone as I mentioned earlier, but it will always get stuck again when I re-flash the ROM.
Also, another unusual thing is that when I boot the phone, it has the old boot splash from my previous ROM when loading recovery or for the first few seconds when loading a ROM. So that might be having an effect on the problems I'm having, and what makes me believe that wiping will help.
Any help would be greatly appreciated. (Sorry if it's a bit incoherent)
TL;DR: Flash TWRP, load TWRP, flash ROM, flash Gapps, load ROM, restart, load TWRP, TWRP hangs, crashes, and breaks ROM. ROM will keep being broken until full wipe. Also weird thing where I have old boot splash from old ROM.
Edit: Ended up bricking my phone, and using the unbrick tool to fix that. It seems that it was what I was looking for, where it wiped the phone completely. I'll have to see if that actually fixes my problem.

TWRP 3.1.xx is having this problem, believe the fix is to use the blue_spark 3.1.xx version or the nethunter 3.0.4-1 version, both found here on the forums somewhere