restore from TWRP - General Questions and Answers

Galaxy S3 with KitKat
I Rooted and installed TWRP made a backup
Installed CM12 Rom
Didnt like it so tried to restore from backup
Phone starts to boot see the splash screen then get alot of messages that apps have stopped working
KitKat does not start just black screen.
Any suggestions

trickyrick said:
Galaxy S3 with KitKat
I Rooted and installed TWRP made a backup
Installed CM12 Rom
Didnt like it so tried to restore from backup
Phone starts to boot see the splash screen then get alot of messages that apps have stopped working
KitKat does not start just black screen.
Any suggestions
Click to expand...
Click to collapse
Did you wipe first?

Wiped before restore yes.
I also made a backup of 5.1. I can restore to that but not 4.4

trickyrick said:
Wiped before restore yes.
I also made a backup of 5.1. I can restore to that but not 4.4
Click to expand...
Click to collapse
Might me a problem with the updated drivers, when I decided to downgrade to KitKat from lollipop the phone had low response due to the kernel can't support the updated drivers .no problem with lollipop or any other custom ROMs. I had to flash a custom kernel made for my phone to fix it.

Related

[Q] Custom firmware issues..

Howdy.
I've been using custom firmware since I got my phone over a year ago, but I'm now having big issues.
I tried to install a 4.2.2 ROM and couldn't boot, even after trying bunch of times, clearing cache, all that jazz..
So.. usually I would just put on another ROM or just restore from a backup, but I'm stuck in a weird situation.
I have a bunch of ROM backups (Clockwork Mod Recovery) going back to April last year, the 1st one is standard AT&T, then various custom ROMS (last one I used was Cynogen 10).
But I can only restore the first AT&T ROM, nothing else will restore. I also cannot even install any ROM the only way I can get a working phone is to go back to the horrible original AT&T ROM..
Clockwork mod recovery also crashes when I try to wipe cache, so think that maybe a clue....
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks
eckythump said:
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks
Click to expand...
Click to collapse
What version of CWM are you on?
You can always restore to your AT&T backup, transfer all of your other backups to your external SD or computer, ODIN to stock, do a complete wipe of the phone, flash the most recent CWM from Sk8 and try again. I'd say that's your best case scenario.
mrfeuss said:
What version of CWM are you on?
I'm on 6.0.1.4 which I believe is latest. I can't even get the original ROM to restore now either. Ughhhh hope I'm not bricked.
Click to expand...
Click to collapse
Try Odin back to stock before u do brick it that should fix any problems

Need some guidance please

guys i was running a rooted nexus s with 4.1.1, tried installing fonts through that darned font installer and it was stuck on the boot screen. i have tried many things i can't restore back to my older state, i recall i flashed clockwork mod or whatever that is when i rooted and it made a backup, how and where is that? can anyone help me get the phone up and running again? i tried the fastboot option and restored it but its still stuck on the boot logo and won't do anything more :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
jafferkhan said:
guys i was running a rooted nexus s with 4.1.1, tried installing fonts through that darned font installer and it was stuck on the boot screen. i have tried many things i can't restore back to my older state, i recall i flashed clockwork mod or whatever that is when i rooted and it made a backup, how and where is that? can anyone help me get the phone up and running again? i tried the fastboot option and restored it but its still stuck on the boot logo and won't do anything more :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Before flashing ur backup do a clean install by doing the factory reset and clear dalvik and cache.
If u get it going you should consider updating your clockwork mod recovery.
Also I would just flash a new ROM or reflash the ROM u were on that caused the boot loop.
Then make a backup of that before your try doing the font change
Good luck
Vs Nexus S4G using tapatalk2
vidaljs said:
Before flashing ur backup do a clean install by doing the factory reset and clear dalvik and cache.
If u get it going you should consider updating your clockwork mod recovery.
Also I would just flash a new ROM or reflash the ROM u were on that caused the boot loop.
Then make a backup of that before your try doing the font change
Good luck
Vs Nexus S4G using tapatalk2
Click to expand...
Click to collapse
Thanks man, I did it all with that wugrush toolkit, I think I spelled it right, thanks I'll make a backup of my rom the next time I mess with fonts which I surely wouldn't anyways

[Q] no os installed

I made mistake and wipe system folder with twrp recovery now my tab says no os installed and is stuck on Samsung screen need help plz its a Samsung tab 3 10.1 gt-5210
If you have a Nandroid backup, restore it... Or just find a new rom you like and flash it.
Regnas said:
If you have a Nandroid backup, restore it... Or just find a new rom you like and flash it.
Click to expand...
Click to collapse
ok ty

Nandroid restore issue on S4 i9500 after xposed framework

Hi,
This is my first post on XDA, so please forgive if i miss some of the things !! So i will start with the issue i am facing. I was running Prism Barebone v14.6 on my S4 i9500, i was trying to install the Xposed Framewrok for Lollipop but somehow i missed the part where it said that "Xposed it not yet working for Samsung TW roms and you will end up in bootloop if you flash it".
So as expected i ended up in bootloop, so i tried to restore my Nandroid backup from Philz recovery. Everything went just fine in the recovery but i was again stuck in bootloop and my phone was not proceeding from Samsung logo loading screen. So i flashed the PB rom again and restored my apps and data with Titanium Backup.
Since then i am having strange issue that for some reason i am not able to restore my Nand backups even after creating the fresh nandroid backups. I was creating the Nandroid backup using "Online nandroid backup" tool; so i thought maybe the issue could be with this app(though it worked just fine on my previous rom Omega v27).
So finally i thought of creating the Nandroid backup from PhilZ recovery and the weird thing was nandroid backup creation failed at "/system" saying "Error backing up /system".
So please guys help me understand what exactly went wrong and how can i fix this. I am facing this issue from last 2 days and i have tried everything which could think of, so i need help from you Android Gurus out here !!!
Thanks in advance !!
rbhanot2 said:
Hi,
This is my first post on XDA, so please forgive if i miss some of the things !! So i will start with the issue i am facing. I was running Prism Barebone v14.6 on my S4 i9500, i was trying to install the Xposed Framewrok for Lollipop but somehow i missed the part where it said that "Xposed it not yet working for Samsung TW roms and you will end up in bootloop if you flash it".
So as expected i ended up in bootloop, so i tried to restore my Nandroid backup from Philz recovery. Everything went just fine in the recovery but i was again stuck in bootloop and my phone was not proceeding from Samsung logo loading screen. So i flashed the PB rom again and restored my apps and data with Titanium Backup.
Since then i am having strange issue that for some reason i am not able to restore my Nand backups even after creating the fresh nandroid backups. I was creating the Nandroid backup using "Online nandroid backup" tool; so i thought maybe the issue could be with this app(though it worked just fine on my previous rom Omega v27).
So finally i thought of creating the Nandroid backup from PhilZ recovery and the weird thing was nandroid backup creation failed at "/system" saying "Error backing up /system".
So please guys help me understand what exactly went wrong and how can i fix this. I am facing this issue from last 2 days and i have tried everything which could think of, so i need help from you Android Gurus out here !!!
Thanks in advance !!
Click to expand...
Click to collapse
Have you tried TWRP ? PhilZ development has been stopped, so you should think about switching someday.
I would do it like this:
-Make a nadroid backup with your custom recovery
-Perform a full wipe
-Flash latest stock firmware via ODIN
-Let the system boot up
-Flash custom recovery and check if the error persists
tried TWRP as well however i was still getting the same issue(boot up process getting stuck at samsung logo screen). Will flashing the Stock Firmware reset the recovery also to Stock recovery ?
Can anyone please reply !!
rbhanot2 said:
Can anyone please reply !!
Click to expand...
Click to collapse
Yup, stock firmware will restore everything. Flash it as i linked it earlier. Once done, perform a factory reset in stock recovery before you boot up android.

No Response ,phone freeze on CM 13 ,CM12.1 Slim Bit, Resurrection Remix Help...

Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Try provide with a logcat, might be more useful in helping you.
No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.
Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz

Categories

Resources