Hello
Need some help figuring out how to go back to stock.
I have already downloaded the latest TWRP backup and recovery for my CID (621). Used 1.92.709.1 version by @topjohnwu.
I put it into the TWRP Backup folder and restored it. Now phone bootloops when I turn it on.
The question is: what am I doing wrong?
(I was running LeeDroid 4.00 Nougat ROM on the moment I decided to go back to stock)
I had the same problem yesterday when I was trying to revert to stock my self.
Turned out I had forgot to format (Did a wipe instead) the data partition and the now un-decryptable encryption was messing up the boot process.
Rebooted into twrp and formated (Not wiped) the data partition -wich also removes the encryption- and it booted normally.
I still had some other issues though, think it's because I was recovering from a sort-off allready messed up backup I guess, so I ended up flashing back the stock recovery and did an RUU update to the most recent stock nougat from SD instead. As a bonus I was able to do a Oreo OTA the moment it booted the forst time.
Elegiacal said:
Hello
Need some help figuring out how to go back to stock.
I have already downloaded the latest TWRP backup and recovery for my CID (621). Used 1.92.709.1 version by @topjohnwu.
I put it into the TWRP Backup folder and restored it. Now phone bootloops when I turn it on.
The question is: what am I doing wrong?
(I was running LeeDroid 4.00 Nougat ROM on the moment I decided to go back to stock)
Click to expand...
Click to collapse
Is your firmware newer than 1.92.709.1? If so you'll either need a newer backup that matches your firmware version or an RUU.zip that is the same or newer than you current firmware version.
What made you want to go back?
Related
Hi,
after restoring my nandroid from stock rom and flashing stock boot.img and recovery.img my HOX boots up fine. (CID T-MOB101, Hboot 1.36).
Then i´ve done a factory reset and wiped the internal SD. After that, rebooted the phone, connected it to my WLAN and started an OTA.
No errors there, but after the update Process only boot-loops. I´ve tried fastboot erase cache and the factory reset option in fastboot.
Still boot-loops.
Any Ideas what i can do now?
Thanks!
Must have removed something from the stock nandroid. Try some other backup from nandroid thread and retry the process.
Flash Stock Rom
blahquader said:
Hi,
after restoring my nandroid from stock rom and flashing stock boot.img and recovery.img my HOX boots up fine. (CID T-MOB101, Hboot 1.36).
Then i´ve done a factory reset and wiped the internal SD. After that, rebooted the phone, connected it to my WLAN and started an OTA.
No errors there, but after the update Process only boot-loops. I´ve tried fastboot erase cache and the factory reset option in fastboot.
Still boot-loops.
Any Ideas what i can do now?
Thanks!
Click to expand...
Click to collapse
Try restoring your backup once again and see if the issue persists. Maybe your backup is corrupted.
If that is the case, try flashing the Stock Rom with the 3.19 base (Latest) which is available in the development thread.
Or get a "new" stock nandroid backup here and try again !
http://forum.xda-developers.com/showthread.php?t=1975140
If the JB version is not there, get a 2.17 based nandroid matching your main version. And also flash back the 2.17 stock recovery and update again to the JB software.
Thanks to all for your answers. But - if the phone works fine after restoreing nandroid, should the problem really be searched there?
The bootloop happend at first boot AFTER the OTA.
Could it be a problem that i had installed AHRD 20 and a jb hboot and then restored an ICS nandroid (4.0.3) ?
Can anyone point me to an official T-Mobile JB RUU? I used the search, but only can find dead links or ICS Versions.
My only Target is to get the HOX completely stock (and up to date) for selling it.
It could be in the ota ! I had a similar case a while back. We solved that by :
1: flashing the firmware to update the hboot
2: restore a nandroid JB backup
Check for a JB tmob 101 backup if its there you can do the same
Ok, got it working after using a JB T-Mobile nandriod. Thanks again.
Now its time to put hands on the Nexus4
regards
[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
I tried the russian B907 stock rom but now I want to put a backup back that I made in TWRP 2.8.0.1 by BangL. which I downloaded this evening.
As it turned out, the backup must have been made by TWRP 2.8.0.1 "red clown" and now the backup does not want to boot.
Does anyone have a copy for me to download from somewhere? the original on a russian site is gone...
Solved.
It was impossible to put part of the backup back.
I installed B907 again and then reinstalled twrp by BangL again and used that to do a fresh carbon rom (which was the backed up rom) install.
Then in twrp I put the data backup back, nothing else.
Phone is back up and running as it was before trying B907.
Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way
Balteck said:
Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way
Click to expand...
Click to collapse
If I didn't mention it, then you don't have to do it .
@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Sent from my HTC One M9 using XDA Labs
I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.
shivadow said:
I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.
Click to expand...
Click to collapse
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock recovery.
Flippy498 said:
@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Click to expand...
Click to collapse
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.
Captain_Throwback said:
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.
Click to expand...
Click to collapse
OK. I guess there was a little misunderstanding.
The current version of my instructions is meant to be used if you want to return to a clean stock system. (In other words the ability to install OTAs, again, is only a side effect.) I never was talking about the boot.img being necessary for being able to install the OTA. I thought you were saying that the boot.img wouldn't be needed inside a backup if you do a full wipe before the restoration and that the phone would still boot.
Sent from my HTC One M9 using XDA Labs
I'm little confused now.
For installing an OTA update I MUST have an untouched system partition and stock recovery.
But the steps I need to do are:
1) backup apps and settings
2) restore untouched system partiton and stock recovery partition from TWRP, doing a factory reset (wipe data, dalvik and cache)
3) boot the original stock OS, configure wifi and go to Software Update
4) download OTA(s)
5) apply update and reboot phone
6) with ADB start TWRP recovery and backup the new stock recovery and the new stock system_image
7) flash TWRP and new custom ROM
8) restore apps and settings from point 1)
So, is it possible that at step 3 my HTC cannot boot because I didn't restore the boot partition (I'm coming from ViperOneM9 4.3.0)?
Or is there a simpler method, without backuping, wiping, restoring?
Flippy498 said:
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock firmware.
Click to expand...
Click to collapse
Looks liks i used an out of date tutorial then.. What a bugger..
Beamed in by telepathy.
Anyone can confirm me that my previous steps are right?
So I may uodate to Android n without doubt
Thank you very much
Hi guys,
I updated to Nougat and flashed the OxygenOS 4.1.6. Everything worked fine but I miss xposed too much so i wanted to go back to Marshmallow. No matter if I restore my newest 6.1 backup or my old Nandroid backup in twrp or flash any other ROM, my op3 always stucks in the bootscreen with the Oneplus logo now and nothing happens. Just when I flash the 4.1.6 zip again, the phone starts and works well.
Does anyone have an idea how i could restore one of my backups or flash any Oxygen 3.x ROM?
Many, many thanks for your help!
Save your backup off your phone, then clean flash whichever version of OOS you want to downgrade to. Once you can boot into OOS again, restore your old backup.