[Q] Phone bootloop after installing theme - Galaxy S 4 Q&A, Help & Troubleshooting

Hello everybody,
My celphone is in a boot loop after installing [THEME][9500/5][17/06]*DOMINATION*v1.3*HOLO*AOSP*JB LOCKSCREEN*DE/ODEX*
My phone works on Omega 5 and Adam kernel.
after i tried to flash the theme my phone went in a boot loop... After it installed.
After that i reflashed The omega rom and did a full whipe. it fixed it!
Greets,
Tunestwo

I encountered the same too. Luckily I had done a nandroid backup. I simply reflashed back to my backed up stock odexed firmware and all was well.

echenze said:
I encountered the same too. Luckily I had done a nandroid backup. I simply reflashed back to my backed up stock odexed firmware and all was well.
Click to expand...
Click to collapse
Next time i will back up to.... Happy to know i was not the only one...

Related

My backups are not working....

Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
thesystem90 said:
Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Follow full wipe procedures, have the same recovery you made the backup with, and try again.
rugmankc said:
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
Click to expand...
Click to collapse
I flashed the stock firm. Soft brick averted. Did the same goo manager recovery method, but now i'm thinking of flashing that cwm as ppl have reported the same nandroid backup issues with twrp. My version is 2.5.0.2. I will keep trying to get twrp for a while with others users till i get sick of it (semi twrp fan). Any further advice would be cool. Oh and I did a factory twrp wipe the first time this problem occurred.
I wipe data caches and system before flashing. No more advice. Had newest TWRP hang on Team Win screen. Several manual reboots into recovery till it worked. Maybe I better do restore to see if it works.
Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta

S4 9505 stuck in bootloop

Hi,
Earlier today I was trying to install the 4.3 omega rom (GE), so I went into recovery and accidently wiped the data before I installed the rom. I am not sure what caused the issue my phone is just stuck on the S4 boot screen.
I tried reinstalling the previous rom (Omega 4.2.2) and it made no difference. I have TWRP recovery and I can get into recovery fine. I noticed that I cannot factory reset from TWRP and it says E/data cannot be mount, reset failed.
I am not sure what to do and how to fix my phone I tried to look for e/data issue but I cannot find much on that issue and I am noobie to this so I cannot understand some processes that are mentioned. I tried not to mess around too much after I realised its stuck.
Please help!
S4 9505
Was on Omega 4.2.2
Adams 1.6 kernel
Manthan Harsad said:
Hi,
Earlier today I was trying to install the 4.3 omega rom (GE), so I went into recovery and accidently wiped the data before I installed the rom. I am not sure what caused the issue my phone is just stuck on the S4 boot screen.
I tried reinstalling the previous rom (Omega 4.2.2) and it made no difference. I have TWRP recovery and I can get into recovery fine. I noticed that I cannot factory reset from TWRP and it says E/data cannot be mount, reset failed.
I am not sure what to do and how to fix my phone I tried to look for e/data issue but I cannot find much on that issue and I am noobie to this so I cannot understand some processes that are mentioned. I tried not to mess around too much after I realised its stuck.
Please help!
S4 9505
Was on Omega 4.2.2
Adams 1.6 kernel
Click to expand...
Click to collapse
try flashing back stock rom via odin
dannyella said:
try flashing back stock rom via odin
Click to expand...
Click to collapse
Thanks I will try that now, takes long to download the stock rom. I will report back if success.
I just did a stock firmware install through odin, now my phone is stuck on logo! Help!
Edit: I did some research and rebooted the phone on stock recovery, did a factory reset and restarted. It solved the issue and mine is back to life and working! Thank you for all your help!
Manthan Harsad said:
I just did a stock firmware install through odin, now my phone is stuck on logo! Help!
Click to expand...
Click to collapse
did it flash successfully in odin..did it say "Pass"??

4.4.2 root/recovery problem

Hi there
I flashed a stock nordic XXUFNB9 ROM via Odin. Worked fine.
I then rooted the device with Unified Android Toolkit
I have TWRP and root, and i can make a nandroid backup in recovery, but if i wipe or restore my backup or install a custom ROM, TWRP restarts, and the phone
wont boot. I have to start all over.
Is this common, and does anybody know how to fix it ?
Thanx !
brundlefly01 said:
Hi there
I flashed a stock nordic XXUFNB9 ROM via Odin. Worked fine.
I then rooted the device with Unified Android Toolkit
I have TWRP and root, and i can make a nandroid backup in recovery, but if i wipe or restore my backup or install a custom ROM, TWRP restarts, and the phone
wont boot. I have to start all over.
Is this common, and does anybody know how to fix it ?
Thanx !
Click to expand...
Click to collapse
I had this problems too with the version 2.7. Try to flash, through ODIN, the latest one for i9505: HERE. It solved my problems
Joku1981 said:
I had this problems too with the version 2.7. Try to flash, through ODIN, the latest one for i9505: HERE. It solved my problems
Click to expand...
Click to collapse
Thanx a bunch, man. That seems to do the trick. At least i could restore my backup.
Next step is to try a wipe and custom rom...... Hope it works !

[Q] Restore CWM backup on CM11

Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
lucashs said:
Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
Click to expand...
Click to collapse
I have discovered that I need it too because my phone is loked and, to enter my carrier unlock code, i need to restore my backup made with CWM.
Looking for the same.
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
TicoDePano said:
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
Click to expand...
Click to collapse
I think this happens because the roms use different file systems
Try the Aroma Wiper to change the file system:
http://forum.xda-developers.com/showthread.php?t=2202674
I'll try this, but now i'm without time, then i report if it work.
I got my phone working.
http://forum.xda-developers.com/motorola-defy/help/tim-brasil-signal-cm11-t2824983#post54683596
About revert to stock ROM, only doing a factory reset to format my data partition fix the boot (I did not try AROMA or safewipe.zip).
I do not tried to restore data from my stock dump after got my phone working because it was not my objective, but i think that it is possible and simple after get it working.
Thanks.

[Q] N910G won't boot after TWRP restore?

Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:
One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.

Categories

Resources