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
Related
After rooting my N7 a few weeks back, I have tried flashing at least 3 different grouper custom roms through TWRP 2.4.2.
After flashing the rom, when I reboot from TWRP, the N7 gets stuck on bootscreen logo of the respective rom. I have to use Nexus Toolkit 1.6.3 to reboot into TWRP and restore from nanroid backup of stock rom, and everything works fine.
Why are Custom ROMs not being able to boot past the bootscreen logo?
I would appreciate help.
Thanks in advance.
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Nico_60 said:
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Click to expand...
Click to collapse
Nexus 7, I have tried flashing simbean 4.2.2, latest XenonHD and another which i have forgotten the name (all latest grouper versions).
I downloaded ROMs on my PC from XDA.
Copied zip file into nexus 7 via USB cable.
Rebooted into TWRP 2.4.2.0
Wipe System/ cache/ dalvic cache
flashed Rom (indicated flash was successful)
Rebooted from TWRP
bootloop (getting stuck at the bootanimation of the custom rom)
Used Nexus Toolkit 3.6.1 to reboot into TWRP
Restored my stock rom from backup.
Stock Rom working fine.
Ive tried flashing faux kernel and an aroma installer for boot animation change, which has worked fine both times.
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Maybe try flashing with a more recent version of TWRP, 2.4.4.0
http://forum.xda-developers.com/showthread.php?t=1779092
http://www.teamw.in/project/twrp2/103
--------
Fastboot flash the latest recovery image from here...
http://techerrata.com/browse/twrp2/grouper
...and then try again, flashing your preferred ROM in recovery.
--------
Don't know if it will work... but it's got to be worth a shot.
What is odd, is you seem to have no problem NANDROID restoring back to stock...
Anyway, hope you get it sorted.
Rgrds,
Ged.
Nico_60 said:
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Click to expand...
Click to collapse
thanks , problem solved
fslnwz101 said:
thanks , problem solved
Click to expand...
Click to collapse
I was having issues with my phone not getting a GPS fix. So, I figured I'd try a few different ROMs. I was on this rom, http://forum.xda-developers.com/showthread.php?t=2771110, and everything worked great except the GPS. I then did a TWRP backup and installed Cyanogen 11. It booted fine into it, but I still couldn't get a GPS lock. So, I thought, maybe it's a kitkat issue with my phone. So, I tried installing this rom, http://forum.xda-developers.com/showthread.php?t=2595586, after doing a full wipe except for internal storage. It sat at "formatting", as the OP says it may, but it finally finished. Then, it wouldn't boot. It just sat at the LG logo screen. I went back into TWRP and tried a few wipes (cache, dalvik, and data), but it still wouldn't boot. So, I decided to restore my TWRP backup of Lam Hoang 7.1, and now it is still stuck at the LG logo, and won't boot.
Any help would be appreciated!
Try a different recovery. I'd start with Philz recovery. After flashing Philz recovery I'd reflash the most recent ROM listed in your second link. In my experience twrp has given me quite the trouble. Good luck.
Sent from my SAMSUNG-SGH-I317.
CharliexCharger said:
Try a different recovery. I'd start with Philz recovery. After flashing Philz recovery I'd reflash the most recent ROM listed in your second link. In my experience twrp has given me quite the trouble. Good luck.
Sent from my SAMSUNG-SGH-I317.
Click to expand...
Click to collapse
Can I restore a TWRP backup with Philz recovery?
ledvedder said:
Can I restore a TWRP backup with Philz recovery?
Click to expand...
Click to collapse
Not that I've ever been made aware of.
Sent from my SAMSUNG-SGH-I317.
ledvedder said:
Can I restore a TWRP backup with Philz recovery?
Click to expand...
Click to collapse
Yes you can but you cannot restore a philz backup with twrp
Sent from my Potato powered G2 D800
How? When I go into restore backup in Philz and select my backup, it just shows me a bunch of files (some with a .md5 extension).
I got it back up. Flashed Philz and installed a rom. Then, I restored one of my backups, and it booted fine.
ledvedder said:
I got it back up. Flashed Philz and installed a rom. Then, I restored one of my backups, and it booted fine.
Click to expand...
Click to collapse
Awesome. Twrp just seems buggy from time to time.
Sent from my SAMSUNG-SGH-I317.
Still have no GPS though. I wish I knew why, because it used to work fine.
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.
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Hi
Bibi if you’re still active on xda reply to this
Help me i got same issue with you. Can provide me with ur stock rom and stock recovery? And how to do. Thanks very much.
Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse
Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse
can you put a link where you find the stock recovery, cos i've restore stock recovery on twrp but my device keep booting to twrp
After reading up and being waived off the Official TWRP I originally used the open source (which I cant find on my phone or desktop) TWRP for my recovery.
I've been playing around with different ROMS on my Oneplus5 and ran into a TWRP loop after restoring from one ROM to another. It was suggested, and I followed the advice, to flash the Official TWRP and no more TWRP loop.
A week or so later, trying to restore from the Resurrection ROM to xXx ROM and I'm back in a TWRP boot loop.
I've tried different wipes before restoring and still looped.
Tried flashing this version of TWRP to recovery https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134 and it was no help.
Any suggestions?
Try flashing no verity op5.zip
I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.
jhs39 said:
I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.
Click to expand...
Click to collapse
Thanks, it was getting a bit frustrating and before your solutions posted, in the interim I used Method 2 from here:https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727 loading the stock bootloader wiped my device clean (all pics, my files, my TB folder gone) but I was able to load a ROM and boot (I hate Goggle, they can f up just about anything, but that god for their backup/restore, it got me up and running from scratch quickly ). I will give the blu spark a shot and @ se7ensde take a look at your suggestion.
It is a shame that TWRP restore is such a problem, and a random one at that. I have restored from ROM to ROM to compare them without an incident until....