I have a Moto X Style XT1572 Indian version. I updated it to stock Nougat 7.0 via OTA when it was rolled out in India. Later in January I unlocked the bootloader and installed unofficial TWRP recovery for flashing custom ROMs. I did take a full backup of stock ROM immediately when I installed the recovery. Since then I'm using custom ROMs built for Nougat modem.
At present, how can I go back to stock Nougat? I did do a full wipe (except internal memory) and tried to restore the stock Nougat backup which I took in January. The backup always gets successfully restored. However, when the phone boots up completely and reaches the language selection screen(the first screen when the phone boots up), the phone reboots and goes into a bootloop just displaying the bootloader unlocked screen. The only option I have then is to flash any custom ROM again and they do work perfectly. So what must be restricting the stock backup to boot? Also, is there any other way to go back to stock Nougat?
anyone, please?
AsquareX said:
anyone, please?
Click to expand...
Click to collapse
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.
jason2678 said:
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.
Click to expand...
Click to collapse
I'll give a try to the fastboot version.
Related
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
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"m having issue with flashing roms, kernels and restoring on my device and i'm not sure if its cause a process was done incorrect and/or a TWRP.
I have a 2017U. Bootloader is unlocked, TWRP 3.1.0, and currently on stock B19 (no root, via TWRP with Draken's Stock system).
Here are the issues I"m facing:
1. Unable to Restore backup. I've made a backup and selected Boot, System and data. Also selected "compression". Restore shows complete, but device freeze on boot screen (the one says hit vol for more options).
2. Issue flashing kernel. I tried flashing Beastmode (a couple of previous versions up to the most currect R45). I keeps booting back into Recovery. I then tried flashing the stock kernel from Freeza and it still boots into recovery.
3. Flashing Roms. This one is possibly a rom issue, but just wanted to throw it out there any ways in case it's not. Flashed Bad Boys rom. Works fine when installing with SU or Magik, but doesn't boot if it select "no root"...
Any help/advice is appreciated.
You either need to flash supersu, or no-dmverity to patch the kernel to bypass this security feature.
3.1 is also not ready according to twrp thread.
Sent from my ZTE A2017U using Tapatalk
Thanks guys.
Just having a difficult time with TWRP recently. I wasn't able to restore properly on 3.0.4.
Every time i tried to restore, it says i need to uncheck mount system partition read only. Do need to flash the no-dmverity after i restore?
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
I have a systemless-rooted SM950FD model with AQDG firmware/baseband, with TWRP.
Before anything took place I backed up with TWRP 3.1.0 the essentials: boot, recovery, system, data, baseband & efs.
Wanting to update to the latest AQH3 firmware without losing any data, I used the 'TWRP-flashable' firmware provided by Renovate here http://www.renovate-themes.de/firmware.html
This zip claims to update bootloader, modem and TWRP.
The update seemed to go well, but when I rebooted I the phone was stuck on Galaxy S8 logo. TWRP disappeared, as did any other recovery, so I had to flash TWRP from ODIN (at which point I updated to latest TWRP version, 3.1.1-2)
Now back on TWRP, I am trying to restore a bootable system from my backup, but no combination has worked for me so far. I always do a quasi-full wipe (system, caches, data) and restore boot/system/data/baseband/efs (with minor variations between the 5). So far nothing has succeeded in booting the phone, it always gets stuck at the Galaxy S8 screen.
At this point I could totally install a stock-like rom which will fast-forward me to the latest version, but since my goal was to keep my original stock rom without losing sms/apps, I would at least need to boot up once in my original backed up state.
Any ideas?
Thank you very much,
Batman Rom Is very close to stock.
I would say flash that one. In fact it's better than stock.
Sent from my SM-G950F using Tapatalk
SM-G950F FLASHED WITH TWRP WITHOUT OEM UNLOCK
Hi guys I need your professional opinion the stupidity I done. I Flashed cf-auto root and without to enable OEM unlock i Flashed TWRP. After reboot the phone stuck on the Samsung logo.
Is the phone dead? Any chance to recover ?
Thanks for ur time
erclalle said:
I have a systemless-rooted SM950FD model with AQDG firmware/baseband, with TWRP.
Before anything took place I backed up with TWRP 3.1.0 the essentials: boot, recovery, system, data, baseband & efs.
Wanting to update to the latest AQH3 firmware without losing any data, I used the 'TWRP-flashable' firmware provided by Renovate here http://www.renovate-themes.de/firmware.html
This zip claims to update bootloader, modem and TWRP.
The update seemed to go well, but when I rebooted I the phone was stuck on Galaxy S8 logo. TWRP disappeared, as did any other recovery, so I had to flash TWRP from ODIN (at which point I updated to latest TWRP version, 3.1.1-2)
Now back on TWRP, I am trying to restore a bootable system from my backup, but no combination has worked for me so far. I always do a quasi-full wipe (system, caches, data) and restore boot/system/data/baseband/efs (with minor variations between the 5). So far nothing has succeeded in booting the phone, it always gets stuck at the Galaxy S8 screen.
At this point I could totally install a stock-like rom which will fast-forward me to the latest version, but since my goal was to keep my original stock rom without losing sms/apps, I would at least need to boot up once in my original backed up state.
Any ideas?
Thank you very much,
Click to expand...
Click to collapse
try flashing stock AQH3 then booting then flashing TWRP again.
mweinbach said:
try flashing stock AQH3 then booting then flashing TWRP again.
Click to expand...
Click to collapse
Thank you, I ended up flashing a custom ROM, unfortunately I did not have time to do this intermediary step, but thank you!