Hey all. I was trying to rollback my P9 to a stock ROM, but it failed and now I am stuck with a bricked P9 (bootloop).
My phone is a European P9 (EVA-L09C432). I have an unlocked bootloader.
- Huawei eRecovery and HiSuite restore does not work.
- I've tried forcing the update using the SRK Tool brick utility, but receive the message "FAILED (remote: sparse flash write failure)" when it's strats writing 'system'.
- My TWRP backup does not work, I had a 7GB backup that installs fine, but the phone is still stuck in a bootloop.
- I can flash EVA-L09C432B378 ROM using the SRK brick utility fine, but the phone is still stuck in a bootloop.
- After I have installed B378 and try to force flash B136 using the dload method, it either gets stuck on the "going into restore mode" or it goes to the "installing package" screen, where it is stuck at 5% until it reboots.
Any suggestions?
try one more time install rollback package by download mode
I've tried. Several times, all day :crying: My process:
Write TWRP from fastboot so I can boot into TWRP and transer UPDATE.app to the dload folder
Reboot into fastboot
Write stock recovery image from fastboot
Boot into recovery mode
Get stuck at 5% on the "Installing update" screen.
I've tried the UPDATE.app or firmware B136 (stock), and UPDATE.app for B378 (Nougat)
Both get stuck at 5%.
I'm stuck at the bootloop
isn't srk tool only for MM?
maybe try extract recovery , boot and system partition from b378 and flash by fastboot , next start flash rollback package by download mode
I noticed when I tried to restore my backup using TWRP it failed at "vendor" (Failed to wipe vendor). I receive this issue at vendor and product.
I tried using fastboot to flash vendor and product manually, I receive these error messages:
"failed: remote command not allowed"
The phone won't allow me to write vendor and product.img... but my bootloader was unlocked?
Is it possible I could have relocked my bootloader? How am I supposed to get the bootloader code for my P9 again :/ It's nearly impossible.
I managed to use the recovery dload method to install a beta version of B378 (build number NRD90M test-keys). Will now try to use the recovery method to roll back to B136 and update back to B378 again.
Highfall said:
I managed to use the recovery dload method to install a beta version of B378 (build number NRD90M test-keys). Will now try to use the recovery method to roll back to B136 and update back to B378 again.
Click to expand...
Click to collapse
I'm having similar issues. Have you solved your problem? What have you tried so far?
Same problem here! Did you resolve?
Thanks you.
Try unplug charger or usb cable then do it
WTF, that ist the solution to the whole damn problem! Just unplugging the damn usb cable and it installs the update just fine. ive spend 2 whole days on this, almost giving it up beacuse everytime it got stuck at 5% and then this...
seriously thank you!
JimmyEatFood said:
Try unplug charger or usb cable then do it
Click to expand...
Click to collapse
thx i managed to boot my device, but i relocked bootloader and factory reset doesnt work correctly it deleted 3rd party apps and leaved few system apps and blotware. what should i do.
and really thanks, you saved me.
Removing cabled worked for me also
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 bricked my phone after Magisk install fail.
I first unlocked bootloader succesfully
then i installed twrp succesfully
then i flashed magisk using twrp - this failed and sent device to erecovery. (which won't find package)
i used twrp to wipe data, now i was able to boot, and it installed like a fresh EMUI. However, almost all apps were broken- could not download themes/camera shut down etc.
To fix this, i wanted to restore to stock and did the following: download update package for my VTR-L09 of EMUI b175 (I was on b162 before), used Huawei Update Extractor to extract files and flashed BOOT.IMG, SYSTEM.IMG and RECOVERY.IMG. This was done without error.
Now my phone won't boot at all. I am stuck at the 'your device can't be trusted' screen. I cannot go into recovery. When I connect via USB, I hear the chime in Windows but I can't seem to connect with ADB.
What to do now?? Am I hard-bricked? I hope that anyone knows how to deal with my phone bricked like this. Please help me to solve this issue.
Best of wishes.
Edit: I am able to enter forced recovery, however updates fail at 5%.
I am also able to fastboot with USB, however I am unsure what to do next.
I unbricked my phone! Many thanks to who ah way and his solution found here: https://forum.xda-developers.com/p10/how-to/guide-unbricking-p10-using-hwota-windows-t3714416
:victory:
why are you doing it when you dont understand it?
You cannot flash part of B175 firmwar eover B162 firmware.. OMG.
use the HWOTa to go back to stock and please stop playing with the device without propper knowledge
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
mnaceem said:
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
Click to expand...
Click to collapse
maybe a bad/corrupted download
Same issue here, I am unable to update my phone
Sent from my [device_name] using XDA-Developers Legacy app
I just got the same error too.
I also got a warning while i boot back to the old version.
System update failed
Update failed, tap to enter repair mode to try again.
guys, i had the same issue too.
Download the full rom via xda link, installation failed. Same goes for the OTA.
However, I managed to update to stock PIE.
My bootloader was unlocked when using stock OREO.
So what I did was, I RE-LOCKED the bootloader, and reboot the OP3T. (BE WARNED,IT RESET THE WHOLE PHONE)
After fresh installation, i was able to update to PIE via OTA. (Should work with local upgrade too)
So for my case, that helps.
vinoxflame said:
maybe a bad/corrupted download
Click to expand...
Click to collapse
NOPE no bad/corrupted download...
---------- Post added at 09:01 AM ---------- Previous post was at 08:52 AM ----------
Well I was upgraded to the pie with locked bootloader and after that, I had flashed official twrp and magisk but I flashed oreo rom to check if this problem is there when the bootloader is unlocked well yes the one plus detects that your bootloader is unlocked and doesn't deliver the ota so what you can do is click on download upgrade read carefully bro DOWNLOAD not INSTALL just DOWNLOAD it and then you will find it in .ota directory in File Manager now what you have to do is backup your all data via your prefered backup method from which you can restore things after the update I am going to give you a spoiler all data will be corrupted when you will flash the update file via twrp that's why the one plus package updater doesn't update and says installation failed... The pie update will be successfully installed but you have to factory reset your phone to use it that's why I told You to take a backup and after this restore your data...
***I have experienced all this by downgrading and then again upgrading with an unlocked bootloader so I would be honored if you thank me***
I was on stock Pie. I was facing some battery drain issue so I decided to install Oreo official stock which was already downloaded last month. I installed it through local upgrade and rom is still in internal memory. Now I am stuck in Recovery. It tries to boot but every time after few minutes it comes back to recovery. Please help me. It installs Oreo through recovery but unable to boot.
I think Pie can be installed through sideload but I could not find exact links for installation through sideload. Or if there is any option to copy Pie Rom in my internal memory to try installing back latest rom.
If anyone could help me It will be highly appreciated. My bootloader is still locked.
Hi i have this p9 plus vie-l29, i unlocked the bootloader, installed twrp and root, everything worked perfect until i found a backup online and restore it using twrp. Since then, P9 shows "device has failed verification and may not work properly".
I boot to erecovery, but i got this error: "getting package info failed", I tried to flash again twrp from fastboot and resccue mode, but not working because i did a factory reset and cannot activate usb debugging. It still has stock recovery but I only have 3 options, reboot, clear cache and factory data reset.
Can you give me a solution to this please? If i try dload method from sdcard, should work?
UPDATE: So, I tried dload method, did not worked for me. Now phone is in service center, I hope it can be fixed.