Develop Bugs

[Q] wiping cache and dalvik caused boot loop?

my s2 was being glitchy so i went into recovery to wipe cache and dalvik and then rebooted from recovery. i waited and then it just boooot loops and shuts off. im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery? and why did the wiping of cache and dalvik booot looped my phone? i thought wiping those just makes my phone less glitchy

You probably had some other issues to cause phone to be glitchy in the first place.
When flashing a new ROM it's recommend you wipe data, system cache and dalvik cache.(cache and dalvik can be wipe after the ROM install before rebooting)

nooob 4 ever said:
im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery?
Click to expand...
Click to collapse
No, you are going to have to update to either the newest TWRP or CWM to flash 4.3 ROMs.

I'm gonna jump in and hope this isn't a hijack. I had a similar experience but I wanted to update to the latest TWRP so I could flash a 4.3 ROM (Simbean) .
I Odined in and flashed TWRP 2.6.3. Was able to flash the Slimbean ROM but on first reboot I can't make it past the Samsung screen.
I can get back into TWRP but everything fails. - typical process. "Fix permissions- Success", then "Full wipe - Success" then "Fix permissions (cause I'm trying anything at this point)- Failed"
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.

pairustwo said:
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.
Click to expand...
Click to collapse
Some people have problems with 2.6.3.0. Try to Odin 2.6.1.0 and see if it helps.
http://techerrata.com/browse/twrp2/hercules

help
so what are my options to fix my phone with the current cwm 5.0.27?

nooob 4 ever said:
so what are my options to fix my phone with the current cwm 5.0.27?
Click to expand...
Click to collapse
i can get into cwm and thats it

nooob 4 ever said:
i can get into cwm and thats it
Click to expand...
Click to collapse
Nothing, that recovery is good for 4.1.2 and lower, of u want newer roms u can go to my beanstalk thread or @ThdDude's hellybean thread and the new recoveries are posted...
Sent from a soup'd up Herc while climbing a giant beanstalk to crazy heights.....

what I did is to hold the power button/ remove the battery of your phone. Open it again and wait for it to start. no bootloop.

[SOLVED] Unable to install custom rom after modem upgrade

Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!

Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.

Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!

acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!

I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D

Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk

It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D

wipe Dalvik and Cache before trying the rom again. If

freezing on boot screen

After some time my phone freezes at boot logo
For example in sokp 4.4.4 rom it stucks at the logo after animation and rom works after a couple of reboots
On aokp the same
But if i restore it to 4.1.2 india rom it works fine
I am on mj5 bootloader
Kindly help
This is really annoying
I have tried everything like restore
Complete wipe
I also switched to f2fs
No solution
And i have a strontium 64gb nitro566x

None?
Guys I need help

Aayush_goel said:
None?
Guys I need help
Click to expand...
Click to collapse
have you think to wipe cache ,dalvik cache?

Yup everything
Switched back to stock 4.1.2
Again to sokp 4.4.4
Same issue
No issues on stock of whatsoever

One more thing.....i had that firmware encountered and recovery via kies issue and successfully recovered by flashing stock 4.1.2

I do use agni pure cm kernel for ur more information

it also happen to me previously.. mostly stuck when reboot/reboot to recovery..
solved after i reflash the recovery (i use twrp), and then do factory reset and format my data in twrp recovery, backup to PC or external sd before you wanna try..

zone-dead said:
it also happen to me previously.. mostly stuck when reboot/reboot to recovery..
solved after i reflash the recovery (i use twrp), and then do factory reset and format my data in twrp recovery, backup to PC or external sd before you wanna try..
Click to expand...
Click to collapse
Already did that
Yes and one more thing
My rom doesnt boot after a clean flash (after wiping everything) it stucks at boot animation even booting for the first time
But if i flash agni kernel with it , then it boots
dont know what is happening

[Q] Boot loop after flashing TWRP recovery !

Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !

LegatoExia said:
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
Click to expand...
Click to collapse
You flashed the TWRP in wrong way. You need to flash it by this method.

Mirhawk said:
You flashed the TWRP in wrong way. You need to flash it by this method.
Click to expand...
Click to collapse
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method (including your tutorial in your signature, which I'm trying as I write this) solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Edit : finished following your tutorials, everything seems to work for the moment, hope it will stay stable this time... thanks for your help )

LegatoExia said:
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Click to expand...
Click to collapse
What did You do before the bootloop was caused? Did You try to flash the TWRP again?

Mirhawk said:
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Click to expand...
Click to collapse
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the Lollipop Pure AOSP rom, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. After installing the ROM, I followed your recovery tutorial using "openrecovery-twrp-2.8.5.0-LT26i.img", hope I did the right thing this time, hahah. Thank you again for your help !

LegatoExia said:
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the rom AND the recovery, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. Thank you again for your help !
Click to expand...
Click to collapse
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.

Mirhawk said:
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Click to expand...
Click to collapse
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D

LegatoExia said:
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
Click to expand...
Click to collapse
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...

Frostymoon said:
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Click to expand...
Click to collapse
I guess You are on stock firmware and flashed the "stock-6.1.A.0.452-twrp-2.4.0.0.elf" or the twrp.img file via fastboot directly. Flash the DoomKernel from here via flashtool as kernel and it will work with stock and have recovery too. Use the blue coloured "Download Now" button and the extension of file is .elf.

[Q] HELP. HTC One X Stuck in bootloop. Almost all famous solutions tried out

So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?

anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there

dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing

anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha

anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks

Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.

Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help

Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.