Related
Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?
razi914 said:
Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?
Click to expand...
Click to collapse
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize
Carlos_Manuel said:
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize
Click to expand...
Click to collapse
You better get some rest bro, u didn't read anything,! This issue also happened to you also, you said a 10-15 pages back that ur stuck on google too after rebooting, ! P.s i will install dreams 4.1.x , and wait for a 110% stable cm10.2 by you!
if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.
lastforone said:
if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.
Click to expand...
Click to collapse
no didnt worked for me,, had to flash factrory image
Hi there! i have a wierd problem when i try to falsh a 4.3 rom the phone wont boot. it just bootloop's
This happens with any 4.3 rom i have tryed. if i go on and falsh a 4.2.2 rom the phone fires up perfect and everything is working as it shuld.
Here here is how i do when i flash 4.3
Put it on SD card.
boot Recovery
Wipe / factory reset
Wipe cache
Wipe Dalvik
Format system.
Falsh rom
Flash Gapps
Wipe Cache
Wipe Dalvik
Reboot
and end up in endlessly bootloop untill i reflash a 4.2.2 rom. why is this happening ?
i belive i have been trying almost every single 4.3 rom out there for the GT-N7100 ¨
even been trying to flash other kernels to see if that would do anything but its just the same
nyvang101 said:
Hi there! i have a wierd problem when i try to falsh a 4.3 rom the phone wont boot. it just bootloop's
This happens with any 4.3 rom i have tryed. if i go on and falsh a 4.2.2 rom the phone fires up perfect and everything is working as it shuld.
Here here is how i do when i flash 4.3
Put it on SD card.
boot Recovery
Wipe / factory reset
Wipe cache
Wipe Dalvik
Format system.
Falsh rom
Flash Gapps
Wipe Cache
Wipe Dalvik
Reboot
and end up in endlessly bootloop untill i reflash a 4.2.2 rom. why is this happening ?
i belive i have been trying almost every single 4.3 rom out there for the GT-N7100 ¨
even been trying to flash other kernels to see if that would do anything but its just the same
Click to expand...
Click to collapse
try it with the latest recovery with 4.3 support latest philz recovery is recommended or twrp
shhbz said:
try it with the latest recovery with 4.3 support latest philz recovery is recommended or twrp
Click to expand...
Click to collapse
thanks for the tip. been trying TWRP latest version alredy. also latest CWM. and still no luck
nyvang101 said:
thanks for the tip. been trying TWRP latest version alredy. also latest CWM. and still no luck
Click to expand...
Click to collapse
try it with this super wipe script http://d-h.st/fWr flash the super wipe script and then flash the rom 4.3
u can try this recovery too http://forum.xda-developers.com/showpost.php?p=44337722&postcount=223
shhbz said:
try it with this super wipe script http://d-h.st/fWr flash the super wipe script and then flash the rom 4.3
u can try this recovery too http://forum.xda-developers.com/showpost.php?p=44337722&postcount=223
Click to expand...
Click to collapse
Still no luck
nyvang101 said:
Still no luck
Click to expand...
Click to collapse
that's strange which rom you trying to install
shhbz said:
that's strange which rom you trying to install
Click to expand...
Click to collapse
Been trying to install Pac man. asylum and carbon.
the only 4.3 rom that have been working for me is http://forum.xda-developers.com/showthread.php?t=2384208 then i tought if i flash that rom then do a dirty flash of any of the other roms it might work but i was wrong. and im compleately blind folded on what to try next. shuld i just trow the phone in the toilet and call the insurance company. this is going on my nerves now. so open to any solutions.
nyvang101 said:
Been trying to install Pac man. asylum and carbon.
the only 4.3 rom that have been working for me is http://forum.xda-developers.com/showthread.php?t=2384208 then i tought if i flash that rom then do a dirty flash of any of the other roms it might work but i was wrong. and im compleately blind folded on what to try next. shuld i just trow the phone in the toilet and call the insurance company. this is going on my nerves now. so open to any solutions.
Click to expand...
Click to collapse
ok try this go for a dirty flash , flash the rom but dont reboot the phone instead get back to recovery and fix permission, wipe cache and dalvik cache twice before re booting.
this should get you on I would recommend to try with philz recovery .
if not then it really need some pills to get adapted to 4.3 rom
shhbz said:
ok try this go for a dirty flash , flash the rom but dont reboot the phone instead get back to recovery and fix permission, wipe cache and dalvik cache twice before re booting.
this should get you on I would recommend to try with philz recovery .
if not then it really need some pills to get adapted to 4.3 rom
Click to expand...
Click to collapse
Thanks for taking your time to help me out. i flashed philz touch recovery and choose Whipe to install. that fixed it. im now on Pacman 4.3 rom.
Again thanks alot
nyvang101 said:
Thanks for taking your time to help me out. i flashed philz touch recovery and choose Whipe to install. that fixed it. im now on Pacman 4.3 rom.
Again thanks alot
Click to expand...
Click to collapse
your phn got saved from the stink of the toilet
same problem
I ve got the same problem. Installing PhilZ recovery didn't help at all. I can install any 4.3 ROM but can't get the to reboot. After the installation and the initial boot everything runs fine until I reboot or shut the phone down an boot again.
I tried CWM, Team Win and PhilZ.
I can always go back to 4.2.2 without hassle...
No idea, what is causing this.
vonDudemeister said:
I ve got the same problem. Installing PhilZ recovery didn't help at all. I can install any 4.3 ROM but can't get the to reboot. After the installation and the initial boot everything runs fine until I reboot or shut the phone down an boot again.
I tried CWM, Team Win and PhilZ.
I can always go back to 4.2.2 without hassle...
No idea, what is causing this.
Click to expand...
Click to collapse
Fixed it.
Using CWM now instead of Team Win and everything works. Needed to test some versions though.
Im facing the same problem.The rom gets flashed and Im able to play around with it.The issue arises when i reboot -it ends in a bootloop.Tried a lot of 4.3 roms and all with the same result.I changed recovery and wiped twice,did a super clean install but the same problem.I can run cm (4.2.2) without any issues ..
What should i do ? and why is this happening ? Coz the issue arises only when i reboot ...
i find out my own fix for it i have used odin then after everything being done i haved go to recovery and wipe factory reset and dalvik cache reboot and works for me always.
Its funny how every one is experiencing diffrent problems. Technologo
Any suggestions ??
joshphilips said:
Any suggestions ??
Click to expand...
Click to collapse
Update:
Flashed prerooted stock through odin and it works now.Donno what caused the bootloop though ...
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.
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.
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