Is it possible to install TWRP with your device running the Nougat beta ?
The recovery is separate from the firmware. So I don't see why it wouldn't be possible. Root on the other hand I wouldn't know but I suppose the SuperSU beta zip file flashed with custom recovery would get the phone rooted.
If it was a kernel being flashed then that would matter as it affects the firmware (as it replaces the stock kernel).
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
FedoraMan said:
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
Click to expand...
Click to collapse
I tried to install the custom recovery using adb, however my phone can't be detected ?
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
FedoraMan said:
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
Click to expand...
Click to collapse
Already tried this, since installing the Nougat beta my PC only recognises my phone when in recovery mode. I installed TWRP but phone still boots into the original erecovery and not TWRP
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
FedoraMan said:
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
Click to expand...
Click to collapse
Yes installed with fastboot, I manually booted into recovery (volume up + power button) right after flashing it. I thought flashify requires root ??
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
FedoraMan said:
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
Click to expand...
Click to collapse
Yeah, I just flashed the update using the dload method. The main reason I want to install TWRP is so i can downgrade. I've tried using the dload method to downgrade however it doesn't work.
For the dload method, I think you have to flash stock recovery first
FedoraMan said:
For the dload method, I think you have to flash stock recovery first
Click to expand...
Click to collapse
I am currently using stock recovery and it still won't let me downgrade, the update reaches 51% then an error occurs. Would it be possible to flash downgrade firmware using fastboot ?
I believe you can, but you should check online to see if it is.
FedoraMan said:
I believe you can, but you should check online to see if it is.
Click to expand...
Click to collapse
I will check and try this method, I'll get back to you with the results
Ok. Good luck!
Same problem here, I installed a leaked Nougat beta for the Honor 8 via TWRP and when I tried to get back to TWRP it wouldn't let me. I've tried to flash it again via fastboot but I can't boot into it :/
I have this problem too after Flashing Nougat.
I have already flashed twrp recovery via fastboot, installation complete. But I cant boot into recovery mode.
I have never had this kind of problem before. If you tried a cold boot (Hold volume up + power), try typing "adb reboot recovery" instead (or the other way around, if you've done that)
Hello.
I came from z3.
For z3 to get in recovery with N u have to hold down vol button and insert cable. Charger or PC
Sent from my EVA-L19 using XDA-Developers mobile app
I don't know if this works, but I was looking around in HiSuite (huawei's phone thing app on pc) and saw a ROM flashing option. Try that.
Related
First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results
what gapps you flashed?
blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps
Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery
Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.
Hey everyone !
I have a rooted Honor 5C NEM-L51 (European variant) with TWRP custom recovery and, as some of you may know, Nougat update is now available to download using Huawei Firware Finder.
However, a stock recovery is needed in order to get OTA updates and since I couldn't find a stock recovery image by browsing the web, I decided to go back to a full stock ROM.
So I tried to do this the usual way : creating a dload folder, placing the update.app file in it, powering off the phone and back on by pressing simultaneously the volume up, down and power button... but this always lead me right to TWRP, no matter how many times I tried. I restored my phone from soft brick using this method about two months ago with no issue, but now I can't get it to work, even if I release the power button once the phone boots or do any other shady manipulation. Could this have anything to do with the latest TWRP update ?
I also tried to do the "Power on method" by dialing " *#*#2846579#*#*" to go to the project menu and flash the file from here, but it rebooted to TWRP...
I'm at a complete loss here. Can anyone please help me with this ?
just install recovery img and other needed image files from stock firmware thru adb....
thelous said:
just install recovery img and other needed image files from stock firmware thru adb....
Click to expand...
Click to collapse
Thank you for answering. The problem is, I don't know where to find stock recovery image, all I can find with Huawei Firmware Finder is the full stock ROM. Browsing the web didn't help so far.
Can I flash the whole ROM through ADB ?
Zarou said:
Thank you for answering. The problem is, I don't know where to find stock recovery image, all I can find with Huawei Firmware Finder is the full stock ROM. Browsing the web didn't help so far.
Can I flash the whole ROM through ADB ?
Click to expand...
Click to collapse
Extract the update.app of full stock rom using huawei update extractor. There u will find recovery.img. Extract it and flash using fastboot.
Shubho20 said:
Extract the update.app of full stock rom using huawei update extractor. There u will find recovery.img. Extract it and flash using fastboot.
Click to expand...
Click to collapse
I did that and then tried to install the update through the dialer. It rebooted and I'm stuck on "Your device is booting now..." screen. Can't even turn it off, it reboot automatically to this screen. Seems like there is no recovery at all and it tried to do the update through this inexistant recovery no matter how many times it reboot...
What can I do now ?
Zarou said:
I did that and then tried to install the update through the dialer. It rebooted and I'm stuck on "Your device is booting now..." screen. Can't even turn it off, it reboot automatically to this screen. Seems like there is no recovery at all and it tried to do the update through this inexistant recovery no matter how many times it reboot...
What can I do now ?
Click to expand...
Click to collapse
Don't do it through the dialer. After flashing the stock recovery, just restart and then try the three button configuration(volume up + volume down + power)
Shubho20 said:
Don't do it through the dialer. After flashing the stock recovery, just restart and then try the three button configuration(volume up + volume down + power)
Click to expand...
Click to collapse
I can't. I am stuck on the "Your device is booting now..." screen. If I turn it off, it automatically turns on again to this screen.
Edit : Nevermind, looks like I didn't press the button correctly. Only the recovery was missing, I finally could boot to system by pressing the power button. Then I reinstalled TWRP with ADB and restored my nandroid backup. Back to the start...
I may have a hint about what went wrong. Extracting the Nougat UPDATE.APP file gave me two recovery files : recovery.img and recovery2.img. I only flashed the first. Any idea why there were two of them ? I am going to try with the FULLOTA-MF file (tried with the FULLOTA-MF-PV file before), or maybe should I try to extract files from the previous update ?
EDIT 2 : Still stuck with TWRP. I extracted several UPDATE.APP files and all have two RECOVERY.IMG files. I tried flashing them both, one after another and then reboot to erecovery, but TWRP is still here. How can I get rid of it and get back to stock recovery please ?
Zarou said:
I can't. I am stuck on the "Your device is booting now..." screen. If I turn it off, it automatically turns on again to this screen.
Edit : Nevermind, looks like I didn't press the button correctly. Only the recovery was missing, I finally could boot to system by pressing the power button. Then I reinstalled TWRP with ADB and restored my nandroid backup. Back to the start...
I may have a hint about what went wrong. Extracting the Nougat UPDATE.APP file gave me two recovery files : recovery.img and recovery2.img. I only flashed the first. Any idea why there were two of them ? I am going to try with the FULLOTA-MF file (tried with the FULLOTA-MF-PV file before), or maybe should I try to extract files from the previous update ?
EDIT 2 : Still stuck with TWRP. I extracted several UPDATE.APP files and all have two RECOVERY.IMG files. I tried flashing them both, one after another and then reboot to erecovery, but TWRP is still here. How can I get rid of it and get back to stock recovery please ?
Click to expand...
Click to collapse
I have flashed several times Twrp recovery on my honor 5c, and i didn't even had to flash the stock recovery to get back to stock rom. I had placed the dload folder with full update in it, and used the 3 button method to flash the full rom. And i was once again in full stock including recovery. Try this. If it doesn't help, just flash the stock recovery. Then type fastboot reboot, let it boot. Then power it off. Now press volume up + power button. Just see which recovery it boots.
Shubho20 said:
I have flashed several times Twrp recovery on my honor 5c, and i didn't even had to flash the stock recovery to get back to stock rom. I had placed the dload folder with full update in it, and used the 3 button method to flash the full rom. And i was once again in full stock including recovery. Try this. If it doesn't help, just flash the stock recovery. Then type fastboot reboot, let it boot. Then power it off. Now press volume up + power button. Just see which recovery it boots.
Click to expand...
Click to collapse
As I said, the three buttons method is not working and boot right into TWRP.
Which stock recovery ? There are two of them. Anyway, I tried this again, it led me back to the endless "Your device is booting now..." screen.
Okay, trouble's gone real now. I tried to flash the boot image from the update using fastboot. Now I'm stuck in "Your device is booting now..." no matter what I do...
Zarou said:
Okay, trouble's gone real now. I tried to flash the boot image from the update using fastboot. Now I'm stuck in "Your device is booting now..." no matter what I do...
Click to expand...
Click to collapse
Try the volume up + power button. Just see it's booting into recovery or not
Shubho20 said:
Try the volume up + power button. Just see it's booting into recovery or not
Click to expand...
Click to collapse
Worked. But guess what ? In TWRP. ><
But at least I can restore my system... Still, I don't understand this whole situation, why is TWRP always coming back ? I'd really like to get to flash this OTA update...
Zarou said:
Worked. But guess what ? In TWRP. ><
But at least I can restore my system... Still, I don't understand this whole situation, why is TWRP always coming back ? I'd really like to get to flash this OTA update...
Click to expand...
Click to collapse
Tell me the whole process what u r doing.
Shubho20 said:
Tell me the whole process what u r doing.
Click to expand...
Click to collapse
Well, I tried with or without uninstalling SuperSU which has an option to try to restore stuck boot and recovery images (which didn't work in my case).
I used adb to reboot into bootloader, from where I flashed either RECOVERY.IMG or RECOVERY.IMG and then RECOVERY2.IMG which I got from Huawei Update Extractor and reboot from fastboot. Then I tried to power off and back on my device by pressing volumes up and power button which led me to TWRP or endless booting screen. Flashing boot image from Update file gave me the same result.
Zarou said:
Well, I tried with or without uninstalling SuperSU which has an option to try to restore stuck boot and recovery images (which didn't work in my case).
I used adb to reboot into bootloader, from where I flashed either RECOVERY.IMG or RECOVERY.IMG and then RECOVERY2.IMG which I got from Huawei Update Extractor and reboot from fastboot. Then I tried to power off and back on my device by pressing volumes up and power button which led me to TWRP or endless booting screen. Flashing boot image from Update file gave me the same result.
Click to expand...
Click to collapse
Okay. What rom u r in now? And which twrp r u using?
Shubho20 said:
Okay. What rom u r in now? And which twrp r u using?
Click to expand...
Click to collapse
Official stock ROM with TWRP 3.1.0.0.
Zarou said:
Official stock ROM with TWRP 3.1.0.0.
Click to expand...
Click to collapse
Emui version?
Shubho20 said:
Emui version?
Click to expand...
Click to collapse
4.1.2.
Zarou said:
4.1.2.
Click to expand...
Click to collapse
Flash the meticulus twrp. Then repeat the dload process. See if that helps.
Shubho20 said:
Flash the meticulus twrp. Then repeat the dload process. See if that helps.
Click to expand...
Click to collapse
Did that. I even flashed the previous version of the official TWRP beforehand. Still nothing. I even wiped everything from TWRP except internal storage and external SD card and still, the three buttons method led me right back to Meticulus TWRP.
However, I did notice something very strange. If I boot normally by pressing the power button and then, on the "Your device has been unlocked and can't be trusted" screen, press the volume up button to "boot into erecovery to restore my device", it boots into... official TWRP 3.1.0.0 !!! What the hell ?!
Do you have any idea ? This whole situation is so weird...
EDIT : This is just complete nonsense. I even wiped the internal storage and this abomination of TWRP 3.1.0.0 was still there. I really am at a complete loss here. ><
UPDATE: I was able to install stock recovery through BOOTLOADER (it started working again) and I tried sideload 4.1.7.zip that way. It seemed to work for a while, but unfortunately, sideloading crashed. Same for 4.1.6, update fails around 45%. Phone says INSTALLATION FAILED. Any thoughts?!
Hi guys,
I'm a longtime flasher of phones, but my wife today jacked up her 3T beyond the point that I know what to do. In short:
Her phone was rooted, had an unlocked bootloader and TWRP installed. She updated (despite my endless begging never to do that) the OTA, which crashed her phone. Duh. Not smart. The problem: the phone would not restart the OS anymore. Upon restarting, the phone immediately jumped to TWRP and hung at the splash screen (which takes a while to load, but she doesn't know that). She panicked, rebooted the phone a bunch of times before giving it to me.
I was able to get into TWRP eventually, and figured I'd manually install the newest 3T firmware. This is what I did:
First, I updated TWRP through TWRP, to the most recent version. This was successful. Then, this happened:
Downloaded 4.1.7 from the OnePlus website
Placed it on the phone's internal storage
Went into TWRP, wiped Dalvik, Cache, System etc. (leaving Internal Storage in tact)
Flashed the firmware
I've done this thousands of times, never fails. Except now.
After flashing (which was supposedly successful, as I did not receive error messages), I hit 'reboot' and TWRP told me 'NO OS INSTALLED - WANT TO REBOOT ANYWAY?'
That is bad, right? So, I did not reboot, stayed in TWRP and ended up trying to wipe internal storage, thinking I could then add the .zip with the firmware again later and try flashing again. Just a clean phone, you know? I was wrong. I cannot copy anything to the phone right now, so I can't flash anything (because I can't put anything on the phone).
I'm trying to sideload things now through TWRP (adb sideload) and regular fastboot (either the firmware 4.1.7 or 4.1.6 - I've even tried flashing the stock recovery through fastboot to try and get the stock back, so I can sideload the firmware through there), but nothing works.
If anyone knows what to do, or can give me an outline on what to try, I'd be very helpful. The situation right now:
3T, without OS or ANYTHING on the phone
With functioning TWRP
Only recognized in the command prompt when in TWRP, not when in BOOTLOADER
Phone does not allow things to be copied to the phone via my laptop.
On behalf of my extremely upset wife, I thank you!
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Siddk007 said:
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Donaghy said:
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Click to expand...
Click to collapse
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Click to expand...
Click to collapse
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Donaghy said:
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Click to expand...
Click to collapse
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Click to expand...
Click to collapse
I don't own an OTG cable. The only USB option there is, is within the ADB menu in the recovery.
EDIT: locking the bootloader seemed to have made things worse, as I now cannot get the .zip files with the firmware on it to be accepted by ADB/the phone... God, this is a gigantic mess..
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
C3C076 said:
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
Click to expand...
Click to collapse
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Donaghy said:
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Click to expand...
Click to collapse
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Whichever is the most recent one that is on the OnePlus website. I downloaded the .img off of their website.
I've had a similar issue, and I tried a billion times on trying to reflash Stock OOS 4.1.0, and sadly nothing happened. I then tried LineageOS by SultanXDA, nada.
So then, I said "Scr*w my data, I'm going to start anew", and I tried the Unbrick Tool, and Voila, new phone with OOS 3.5.X. Not the latest, but it's working.
I suggest you try that mate, you can find it over here.
Cheers!
P.S. - Love your profile pic.
If you sucessfully flashed 4.1.7 then I'd just reboot into system. TWRP sometimes says "No OS installed" if /system was wiped prior to flashing.
Regardless, I recommend you do these things now (if you havent already) and report back:
-Unlock bootloader (fastboot oem unlock)
-Flash TWRP* recovery, not stock. (fastboot flash recovery twrp.img)
-Boot recovery (fastboot boot twrp.img)
-Wipe data + system + cache + dalvik from TWRP
-ADB sideload in advanced section of TWRP
-from your PC: "adb sideload oos417.zip"
-from TWRP: reboot into system (ignore "No OS installed")
If you follow this and its succesful, everything will be fixed
* flash the twrp by xda member eng.stk, not the official one: the only place I can find his TWRP is in the 3/3t toolkit zip. So extract the v5 zip and use the "TWRP_recovery.img": https://drive.google.com/drive/u/0/folders/0B1cephDrsyt_ZzJ1cXpUUlVhSzg
Edit: Instead of doing all this manually, you may want to use the toolkit. See if your device is recognised
Thanks for the help, everybody!
I used the unbrick tool, which worked! I got the phone 'alive' again.
New problem: Right after successfully booting the phone again, I set up the phone (so: clean install, no root, stock recovery, straight out of the box, you know what I mean) and then proceeded to download the OTA that OnePlus pushed to the phone (4.1.7). It downloaded quickly, but the installation has been stuck for almost an hour.
The phone says 'Updating, please wait - do not turn off your phone', and the blue bar is filling. Well, not filling, as it has been stuck at about 10% for an hour.
Is this normal? If not, what can I do? Thanks again!
I turned the phone off and was able to successfully sideload 4.1.7 via ADB. Upon updating, the phone gave me a notification (blue and white letters) that the "DECRYPTION IS UNSUCCESSFUL. The password you entered is correct, but you have to perform a factory reset to use your phone".
So I did another factory reset in recovery, rebooted, and it's up and running, with 4.1.7 on it! I can't believe we got it back from the dead. Thanks everyone, for your help! Really appreciate it!
I have honor 5c that has recovery bricked so I can't reset it. anyway, lock screen pattern doesn't allow me to access the phone. even I enter it correctly. what would be the way to fix it. I can't even use adb since I can't access it?
its not even near bricked. learn concept bricking.
But what to do in this situation?
DNSMaster said:
But what to do in this situation?
Click to expand...
Click to collapse
Can you explain how did you get in this situation ?
I tried to install magisk patched boot image and custom recovery but installing the recovery broke the recovery
DNSMaster said:
I tried to install magisk patched boot image and custom recovery but installing the recovery broke the recovery
Click to expand...
Click to collapse
Broke the recovery?
Yep. Broke the recovery. I can't access recovey mode anymore. If I try, phone will go on bootloop
DNSMaster said:
Yep. Broke the recovery. I can't access recovey mode anymore. If I try, phone will go on bootloop
Click to expand...
Click to collapse
I hope u reflashed the recovery
But I can't access the phone past the lock pattern so I can't access the adb for rebooting to bootloader so I can't flash the recovery
DNSMaster said:
But I can't access the phone past the lock pattern so I can't access the adb for rebooting to bootloader so I can't flash the recovery
Click to expand...
Click to collapse
Can you boot to erecovery?
No, I can't
U can boot in bootloader without pc and accesing phone. Just turn it off connect usb to pc and to phone and when u put it in the phone imidiatly hold down volume down button and u are in the bootloader i wipe so many times my system from twrp recovery and i thin i cant acces but this method saves me.
Just reflash the firmware via Dload and then try again
Yep but it fails getting an update. And now since I got fastboot working and flashed system.img I can't start even the system anymore. What to do now?
DNSMaster said:
Yep but it fails getting an update. And now since I got fastboot working and flashed system.img I can't start even the system anymore. What to do now?
Click to expand...
Click to collapse
By dload method as suggested by shashank.
I tried dload but it just says "incompatibility with current version"! Is there way to flash update.app or update.zip via fastboot? Where can I get that so called "android-info.txt"?
DNSMaster said:
I tried dload but it just says "incompatibility with current version"! Is there way to flash update.app or update.zip via fastboot? Where can I get that so called "android-info.txt"?
Click to expand...
Click to collapse
Why is android info txt needed?
You can flash userdata, system, boot and recovery via fastboot.