[SOLVED]
Hello guys, hope that someone could help me.
I had a 4.4.2 rom (note4neo 2.0) and i wanted to try 5.1.1 so first of all i mad a full Nandroid Backup through TWRP and also a titanium bkp. Later on i installed lollipop original rom through ODIN and everything was ok. I then followed a guide from Noble Rom for rooting and installing TWRP. Everything went ok, but i had problems with some rooting app (like titanium) and so i decided to revert back to 4.4.2.
At first I rebooted into recovery, made a full wipe (even system) then restored previously backup. Seemed to be ok, but then when rebooted it stucks on boot logo (i left booting for 28 minutes, so....).
Then i tried to wipe cache, dalvik and data and reboot again: no changes.
I then decided to reflash previously twrp (the one that i used for bkp). Flashes went ok, but i have "recovery is not seandroid enforcing" message on the top (even with the lollipop twrp: maybe is this the key of my problem?!?).
Restoring backup from older twrp didn't work as well...
Of course i can enter both Download and Recovery mode.
Now i flashed back the original 5.1.1 through ODIN in order to go back to original lollipop and see what u guys can tell me to do to restore backup i made..
Thank you very much for your help
I was thinking that maybe i should flash a stock 4.4.2 before restore the backup...
Now i'm downloading it and see what happens...tell me if i may be right
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
lennon123 said:
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
Click to expand...
Click to collapse
Update: Flashed 4.4.2, all ok. Then rooted, twrp and all ok again
After i restored Backup and stuck on boot.
Then i made again all the steps: STOCK, ROOT, TWRP, then Base version of the Rom and all ok.
At this point i was thinking it was done and restoring would have been just fine...unfortunatley it doesn't. Stuck on boot again.
So i reflashed the Base version of the mod rom and: it started with my restored app Btw i'm encountering problems like no home button, no volume icon, no settings shortcut. Now i made a cache and dalvik wipe but problems still remain..
Any idea?
After some attempts to solve those problems i stucked again on boot..
So now my plan is to: Flash STOCK rom, Root, Twrp, Base mod rom (everything always ok so far) and then restore JUST DATA from backup... Not touching system and boot should let the rom works just fine...at least i hope so :'D
Ok, as i was expecting the problem is solved. I did not restored System and Boot and all apps works just fine. Even though i miss some settings i made now i'm happy to be 90% back to origin ^^
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
lennon123 said:
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
Click to expand...
Click to collapse
Yes, it's solved I'll mod the title
Related
I am just tired of wiping, trying a new rom, setting it up, finding problems too big to live with and repeating the process. So I used TWRP to put my backed up system back on the phone but when it boots up tons of things are missing. Google apps are all gone, no root. Did I do something wrong? I backed up all the tick boxes when I made my backups, yet so much is missing?
Flash th stock through odin. Then flash twrp and this time restore only data from nandroid.
sasank360 said:
Flash th stock through odin. Then flash twrp and this time restore only data from nandroid.
Click to expand...
Click to collapse
Thanks. I did flash my original firmware just now via odin, but I thought that would resolve my encryption problem. I made a thread about it here, I don't know if you could chime in on that thread if you have any ideas on my new issue? Thanks: http://forum.xda-developers.com/general/help/questions-relating-to-fresh-odin-t3057860
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
I will be travelling and i wont have access to odin for a little while, so i'm less inclined to go breaking things till i get back home. I thought maybe someone here has run into this or knows how to fix this.
Thanks for the help
Dom
wascalwabbit said:
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
Click to expand...
Click to collapse
Was the original CM11 nandroid made with the same recovery make and version which would not install it? I am pretty sure TWRP will not install a CWM or Philz nandroid. I don't know if there are issues installing a 2.6.x.x TWRP nandroid with the 2.8.x.x version of TWRP.
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
wascalwabbit said:
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
Click to expand...
Click to collapse
Since Philz was originally based on CWM I wouldn't expect it to work with TWRP nandroids either.
Have you tried installing only specific partitions of the nandroid, such as the /data/data partition where the user installed apps are stored. As opposed to restoring the entire nandroid. I have heard mention of this, but in your case it may be problematic since your nandroid is of CM11 and the ROM you are running is SlimKat.
Oh that's a great idea, thanks, that may work. I i'll just flash CM and then restore data. I'm literally heading into the jungle right now, so in not sure if I'll be able to try this out for few days, but I will as soon as I get a chance.
Thanks for tour help
Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.
Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.
In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0
It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.
Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.
I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.
I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)
I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.
Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it
Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.
Hi to all!
P600 xKat 4.4 TWRP
Today I tried to update to Lollipop from xKat rom last version. Before starting I Nandroid backed up everithing with TWRP (can't remember version, guess the one xKat flashes). After failing the update via Odin 3.09 (black screen for 1h20min) I wanted to go back to my rom to use it as normal.
Flashed TWRP last version, boot recovery, and in TWRP the touchscreen didn't work (if I pressed up power button the classic slide to unlock thing appeared but couldn't slide).
Flashed TWRP 2.6.3.3 and recovery booted ok. Made restore (selecting the correct backup and all data/system/boot options)
Finally the tablet booted and the problems started:
Half my apps disappeared
No data in my apps (ie: no notes on S Note)
No lockscreen
Nova luncher settings gone as shortcuts
All settings reseted
I've tried:
Wipe data/system/dalvik/cache again
Restore again
Wipe cahes
This is the first time, in many devices, a Nandroid backup fails to me.
Any idea/suggestions?
Thanks
Hello
I'm trying to install Resurrection Remix, but everytime the flashing is done (Rom an Gapps) the phone reboots into TWRP only. No Lenovo logo, zero, nada. I thought it was a problem with RR and tried Lineage OS just for kicks but the same thing happened.
I've done the dd if=/ command method which i used some time ago with my beloved nexus 4 and Cyanogenmod nightlies; worked like a charm back then, however this time the path doesn't seem to exist.
Glad i made a nandroid backup. My phone can be brought back as new, no loss there, but i want to try custom ROMs.
What could i possible do to fix this?
Regards
r0ckm4n said:
... the phone reboots into TWRP only. No Lenovo logo, zero, nada.
Click to expand...
Click to collapse
Do you mean you don't see the Lenovo bootlogo during boot? What do you use to make and restore the Nandroid backup? Does everything work well after restoring the Nandroid backup? Also, most importantly, what's the model name of the device you're using?
Droidge said:
Do you mean you don't see the Lenovo bootlogo during boot? What do you use to make and restore the Nandroid backup? Does everything work well after restoring the Nandroid backup? Also, most importantly, what's the model name of the device you're using?
Click to expand...
Click to collapse
The phone never gets to the Lenovo Logo, goes directly into TWRP after Reboot or Power On. Everything works after restoring from TWRP 3.0.3.
Phone model is A6020I36, Hardare Version H201.
Thank you.
r0ckm4n said:
The phone never gets to the Lenovo Logo, goes directly into TWRP after Reboot or Power On. Everything works after restoring from TWRP 3.0.3.
Click to expand...
Click to collapse
All right, time for a little bit of experimentation. Now, this could be dangerous, and I hope you know how to recover a bricked phone using QPST.
Does the Nandroid backup have a backup of the boot partition? If so, I'd like you to reproduce the issue; and when you get to the point of restoring the backup, restore everything but the boot partition. Let me know if you see the Lenovo bootlogo during the reboot sequence that follows.
Droidge said:
All right, time for a little bit of experimentation. Now, this could be dangerous, and I hope you know how to recover a bricked phone using QPST.
Does the Nandroid backup have a backup of the boot partition? If so, I'd like you to reproduce the issue; and when you get to the point of restoring the backup, restore everything but the boot partition. Let me know if you see the Lenovo bootlogo during the reboot sequence that follows.
Click to expand...
Click to collapse
I'll read everything about QPST first and then i'll proceed hopefully this weekend, i'll keep updating here.
Kind Regards
Turns out i just needed to downgrade TWRP from 3.0.3 to 3.0.2 and everything worked as it should have been from the start.
Thank you for your replies. Cheers!
Happened to me one day, Shreps TWRP it's bugged, it have two or three bugs related with F2FS and the bootloop, you always can flash the Russian TWRP for solving this
KiiKeEp said:
Happened to me one day, Shreps TWRP it's bugged, it have two or three bugs related with F2FS and the bootloop, you always can flash the Russian TWRP for solving this
Click to expand...
Click to collapse
I dont get it, can u pls explain it bro
This happened to me when I installed AOKP. Remove the battery and boot again. It works for me and that is how I do it every time there is an update. First boot takes time so don't panic.