So yesterday, I tried to root my Axon 7 A2017U 27B via tenfar's "Axon 7 root without bootloader unlocked". After a few failed attempts, I wanted to return to my stock images, so
1. I did a factory reset and formatted data in TWRP.
2. I flashed both boot and recovery via TWRP with the backups I made.
-Rebooted system to find the phone hanging on the boot screen.
4. After researching a bit, I redid tenfar's method to get access to TWRP again and restored the system image after I did a factory reset and system wipe.
-Rebooted system, still hanging.
5.Tried A2017_Bootloop_BootFix.zip after I redid tenfar's method.
-Rebooted system, still hanging.
Any ideas?
Update: Redid tenfar's method, went into terminal and inputted "reboot disemmcwp", phone booted up but no wifi...(progress at least)
Update 2: Used 27B versions of DrakenFX's fix
- ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip
- ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip
Everything works, but the phone is a bit warm...(eh)
Related
Hi,
New nexus 10 arrived today. Installed drivers from NRT.
Computer cannot see the device with ADB (usb debugging enabled) so manually rebooted into bootloader.
Unlocked bootloader successfully with fastboot then restarted system.
Watched loading screen for 10 minutes then three button reset into bootloader.
Used fastboot to push twrp 2701 successfully.
Entered twrp, attempted backup, stated failed, lots of can't mount this or that errors.
Rebooted, watched loading screen for 10 minutes, three button reset to bootloader.
Pushed philz recovery and entered. Attempted backup failed again with similar errors. Internal storage showing as 0mb.
Rebooted and currently watching loading screen.
When in the bootloader fastboot recognised the device but not adb so i've no way of pushing a rom zip to the device in order to flash it with the recovery.
Any clues on what to try next appreciated.
Crisis over.
Pushed twrp over again and entered.
Loads of cannot mount errors, unable to backup existing rom.
Factory reset failed.
then...
Format data...and yay, that seems to have fixed it.
Was then able to factory reset, reboot and it loaded.
Downloading CM11 now to flash.
What a royal PITA lol.
I have a Huawei P9 Lite and i have installed twrp and android 7.0 on it. Now I want to install Google assistant, but when i try to boot in twrp recovery (volume down + power b) it shows me the screen where it says ''Installing update'' and then freezes at 5 % so i have to hold my power button to power off the phone.
If I dont try to run in the twrp, phone works just fine.
I apologize for my bad english.
Hi there,
I will move your thread in the correct forum dedicated to Huawei P9 Lite for more relevant answers.
Good luck
Bump..
Just to state that I am in the same boat here; as I am facing the same issue. Here's what happened in my case (using a guide found here at XDA-Developers):
-- unlocked the bootloader
-- booted to bootloader and flashed twrp
-- used adb to reboot to recovery (adb reboot recovery)
-- used twrp recovery to flash nougat update (two zip files, one ~1300mb and second ~680mb)
-- had some errors that were expected, the guide said ignore them and reboot after both zips have been flashed.
-- the flash overall was successful as the phone booted in emui 5 with android nougat. However, there was no virtual keyboard; so decided to do a factory reset
-- rebooted to recovery, but this time, the phone booted to huawei erecovery
-- did a factory reset, but to no avail
-- now, i can't boot into twrp to flash anything else. booting into bootloader and using fastload to flash recovery image is successful, but the phone does not boot to twrp recovery; remain stuck on "your phone is booting up" (or something similar).
My phone is not bricked, as basic telephony, wifi and built-in apps are working fine. But, without a keyboard, its pretty useless for everyday use. Any help in this matter will be appreciated.
KashifSMalik said:
Just to state that I am in the same boat here; as I am facing the same issue. Here's what happened in my case (using a guide found here at XDA-Developers):
-- unlocked the bootloader
-- booted to bootloader and flashed twrp
-- used adb to reboot to recovery (adb reboot recovery)
-- used twrp recovery to flash nougat update (two zip files, one ~1300mb and second ~680mb)
-- had some errors that were expected, the guide said ignore them and reboot after both zips have been flashed.
-- the flash overall was successful as the phone booted in emui 5 with android nougat. However, there was no virtual keyboard; so decided to do a factory reset
-- rebooted to recovery, but this time, the phone booted to huawei erecovery
-- did a factory reset, but to no avail
-- now, i can't boot into twrp to flash anything else. booting into bootloader and using fastload to flash recovery image is successful, but the phone does not boot to twrp recovery; remain stuck on "your phone is booting up" (or something similar).
My phone is not bricked, as basic telephony, wifi and built-in apps are working fine. But, without a keyboard, its pretty useless for everyday use. Any help in this matter will be appreciated.
Click to expand...
Click to collapse
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Claleale said:
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Click to expand...
Click to collapse
Did that and it worked thanks!
Claleale said:
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Click to expand...
Click to collapse
This seems helpful; but how can I flash recovery if I can't boot to fastboot?
[Update] Oh, got to fastboot, trying the suggested recovery now.
Fixed
Fixed using the suggestion above. Thanks.
Today I decided to root my OP2. I did all the regular procedure for rooting. Fastboot > OEM unlock > Flash TWRP 3.1 > flash SU.zip via TWRP. Now this is where the problem started, after flashing SU.zip I rebooted but it was not rebooting, the 2 white dots kept rotating for quite a long time. so I turned off the phone and flashed the SU.zip again and rebooted but still didn't worked, so I went back to TWRP booted into fast boot and flash a lower version of TWRP, Now TWRP won't even start the screen got stuck on one plus logo. so I powered off again and tried doing a normal start up but that didn't workout, so I tried to start fast boot manually (power button + volume up) but this time the screen didn't even turn on . Is there anything I could do to fix it.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
use method 2 or method 3 if you have efs backup by terminal or efs backup by spanna software zip. (P.s. dont rely on efs backup by twrp)
and if don't have efs backup then after method 2 or 3 flash oos 3.5.7 to get ur imei numbers.
I was testing messi2050's arm64 TWRP and LOS. i was using it a while, then decided to restore a old backup with arm64 twrp. restored fine, but i locked myself out when my pattern was unrecognized. I pulled battery and attempted to boot into twrp using hard key method. I was unable to do so, each time it would boot back to system. It seems that the white screen prompting to factory reset has dissapeared entirely. The volume keys work fine, so I don't think that's it. I've flashed stock with LG Bridge and LGUP. I've locked and unlocked bootloader. Interestingly, when i flashed stock with LGUP, it didn't factory reset or remove my apps.
What i did stepwise -
1. Unlocked bootloader of my g5 plus
2. Flashed twrp-3.2.3-1-potter.img via adb
3. Booted to TWRP
4. Wiped to decrypt phone
5*. Booted to system to enable usb debugging, enabled it . Transfered magisk , arrow 9.0 rom , gapps to my internal storage of phone
6. Open bootloader , selected recovery mode and got nothing except error "No Command"
So i cannot flashed anything what i wanted to
What and Where i made the mistake ?
How can i get TWRP back?
Thanks all in advance
Solution
1. Flashed magisk17.1 and lazyflasher
2. Updated magisk manager and got root
3. Installed official TWRP app , granted root and downloaded same TWRP.img from which i decrypted the phone.
4. Flashed twrp fom the official twrp app.
5. No irritating No Command error again
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
echo92 said:
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
Click to expand...
Click to collapse
Thanks for your answer sir , but it didn't work
What I did again
1.I flashed same twrp from adb
2. Booted to recovery , but this time TWRP didn't asked password and I could see internal storage in twrp but not on my PC
3*.However I took the whole backup of stock nougat and cross check from restore option as there was backup in TWRP folder. I wanted copy that backup to my PC . But PC cannot detect my phone while in recovery
4. So booted to system and my PC detected my phone but there was no backup in TWRP folder.( But around 6gb(backup) of storage was used but I couldn't see it)
5.Again booted to recovery mode but "No Command" showed again .
I tried several times but I keep losing TWRP and couldn't see the backup which I make
Same problem. Resolved by flashing alternately several times twrp-3.2.1-0-potter.img and twrp-3.2.1-1-potter_persist.img and finally updated twrp-3.2.3-1-potter.img
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
NZedPred said:
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
Click to expand...
Click to collapse
I flashed magisk 17.1 and lazyflasher ,i got magisk and root but cannot install modules may be becoz of f2fs bug . By the way i lost twrp after booting to system again and No command still present in recovery mode . I am frustrated Moto software is just pain in head :silly: