Related
I have run into trouble using this method: https://www.youtube.com/watch?v=hb0jKB8OFko to flash stock firmware
My device: Droid Maxx
Bootloader locked, not rooted
4.4.4 at the start of the process
I downloaded the suggested firmware and ran into problems.
The first time I attempted it RSD appeared to flash everything except system.img which got hung up and the bootloader gave me a message in red stating: "no valid piv block in sp for system" This occured with the 1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 software.
Figuring I had the incorrect firmware i tried two other roms: 1. CFC-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 and 2. 1FF-obake-maxx_verizon-user-4.4.4-SU6-7-release-keys.xml.zip 1.0.0. Both failed with a different error message. This time RSD and the bootloader told me "preflash validation failed for gpt".
I have tried this with RSD 6.1.5 and 6.2.4
My suspicion is that I don't have the correct firmware, but I could be wrong.
The bad news is that the phone will not boot into recovery or normally. The good news is that the phone WILL enter bootloader mode and RSD WILL recognize it.
Anyways any help would be greatly appreciated.
Stanleywinthrop said:
I have run into trouble using this method: https://www.youtube.com/watch?v=hb0jKB8OFko to flash stock firmware
My device: Droid Maxx
Bootloader locked, not rooted
4.4.4 at the start of the process
I downloaded the suggested firmware and ran into problems.
The first time I attempted it RSD appeared to flash everything except system.img which got hung up and the bootloader gave me a message in red stating: "no valid piv block in sp for system" This occured with the 1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 software.
Figuring I had the incorrect firmware i tried two other roms: 1. CFC-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 and 2. 1FF-obake-maxx_verizon-user-4.4.4-SU6-7-release-keys.xml.zip 1.0.0. Both failed with a different error message. This time RSD and the bootloader told me "preflash validation failed for gpt".
I have tried this with RSD 6.1.5 and 6.2.4
My suspicion is that I don't have the correct firmware, but I could be wrong.
The bad news is that the phone will not boot into recovery or normally. The good news is that the phone WILL enter bootloader mode and RSD WILL recognize it.
Anyways any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay, as long as you can enter fastboot (bootloader mode) there is hope. That's the first thing.
Since RSD recognizes your phone then there is obviously something wrong with the flashing process. You can use either the 1FF obake-maxx or CFC obake-maxx firmware. The 1FF keeps your apps and data intact while the CFC firmware wipes everything off your phone and you start clean. I would recommend using the CFC so you do not anything left over from previous flashes. Also, make sure the entire firmware file is downloaded. I got only partial downloads( like 150/200 mb) several times when I tried to download the files. Both the 1FF and CFC should be about 900 or so mb each. Exactly what steps are you following? And where are you getting your downloads from?
classic757 said:
Okay, as long as you can enter fastboot (bootloader mode) there is hope. That's the first thing.
Since RSD recognizes your phone then there is obviously something wrong with the flashing process. You can use either the 1FF obake-maxx or CFC obake-maxx firmware. The 1FF keeps your apps and data intact while the CFC firmware wipes everything off your phone and you start clean. I would recommend using the CFC so you do not anything left over from previous flashes. Also, make sure the entire firmware file is downloaded. I got only partial downloads( like 150/200 mb) several times when I tried to download the files. Both the 1FF and CFC should be about 900 or so mb each. Exactly what steps are you following? And where are you getting your downloads from?
Click to expand...
Click to collapse
Thanks for your help, but it appears that I have resolved the issue. As it turns out, the software need to be extracted to and launched from a clean folder. I had been placing it in the same folder I had adb and fastboot. My guess is that having the other version of fastboot in the same folder as the XML file confused RSD and caused the problem.
Stanleywinthrop said:
Thanks for your help, but it appears that I have resolved the issue. As it turns out, the software need to be extracted to and launched from a clean folder. I had been placing it in the same folder I had adb and fastboot. My guess is that having the other version of fastboot in the same folder as the XML file confused RSD and caused the problem.
Click to expand...
Click to collapse
Great! Glad to hear you resolved your problem. :good:
I have a Honor 8/FRD-L14 (US model) which I purchased a couple months back. I decided I wanted to root it, so I unlocked the bootloader, installed TWRP (version 3.1.1-1 for FRD-L14) and magisk. To cut to the chase, a lot of my apps didn't work after restoring my backup so I thought I would start over from scratch.
So I had the brilliant idea to wipe all my partitions in TWRP, thinking it would be easy to restore from a blank slate. Nope.
I have obtained a copy of B389 (FRD-L14C567B389b) firmware, both update.zip and update_full_FRD-L14_hw_usa.zip. The first is about 1.3 GB, and the latter is 683 MB..
Here's what I can do:
1. I can unlock and "oem relock" the phone, using TWRP or stock recovery as appropriate.
2. I can boot into Huawei eRecovery, but it always reports "Getting package info failed". It's done this all along.
3. I can boot into TWRP, and attempt to sideload. If I try to sideload the larger "update.zip", it fails immediately. If I try to sideload the smaller "update_full_FRD-L14_hw_usa.zip", it fails at 50%. In both cases the display shows the following:
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Verifying current userdata...
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching userdata files...
Removing empty directories...
Unpacking data new files...
add link type file...
write radio image...
check_write_data_to_partition,write data error
[COLOR="red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from zip failed
[COLOR="Red"]Updater process ended with ERROR: 7[/COLOR]
4. I can "fastboot flash" system SYSTEM.img, boot BOOT.img, cust CUST.img, and recovery RECOVERY.img extracted from the UPDATE.APPs mentioned earlier.
5. HiSuite restore reports that my device is not supported, whether locked or relocked.
6. I have a 128 GB SDXC, and I have attempted to load the two UPDATE.APP files from the aforementioned zip files. Either UPDATE.app, whether placed at root level or in a directory called "dload", gives the same error when trying the 3-button flash function: "Software install failed!", always at 5%.
At no point have I been able to actually boot the OS. If I do not select one of the various recovery modes, the phone never progresses past the unlocked warning message with orange text. (If the phone is locked, it warns that it has "failed verification" with red text, but still won't proceed.)
It really seems like I must simply be doing something wrong here. Apparently I have all the tools I should need available and functional. And yet, I cannot restore the phone to stock firmware.
* Does anyone know what I'm doing wrong? And, does anyone know anything about whether I should be using some particular firmware version for this, and if so which one?
* Is the problem the /data directory? How do I repair/restore that?
marshaul said:
I have a Honor 8/FRD-L14 (US model) which I purchased a couple months back. I decided I wanted to root it, so I unlocked the bootloader, installed TWRP (version 3.1.1-1 for FRD-L14) and magisk. To cut to the chase, a lot of my apps didn't work after restoring my backup so I thought I would start over from scratch.
So I had the brilliant idea to wipe all my partitions in TWRP, thinking it would be easy to restore from a blank slate. Nope.
I have obtained a copy of B389 (FRD-L14C567B389b) firmware, both update.zip and update_full_FRD-L14_hw_usa.zip. The first is about 1.3 GB, and the latter is 683 MB..
Here's what I can do:
1. I can unlock and "oem relock" the phone, using TWRP or stock recovery as appropriate.
2. I can boot into Huawei eRecovery, but it always reports "Getting package info failed". It's done this all along.
3. I can boot into TWRP, and attempt to sideload. If I try to sideload the larger "update.zip", it fails immediately. If I try to sideload the smaller "update_full_FRD-L14_hw_usa.zip", it fails at 50%. In both cases the display shows the following:
4. I can "fastboot flash" system SYSTEM.img, boot BOOT.img, cust CUST.img, and recovery RECOVERY.img extracted from the UPDATE.APPs mentioned earlier.
5. HiSuite restore reports that my device is not supported, whether locked or relocked.
6. I have a 128 GB SDXC, and I have attempted to load the two UPDATE.APP files from the aforementioned zip files. Either UPDATE.app, whether placed at root level or in a directory called "dload", gives the same error when trying the 3-button flash function: "Software install failed!", always at 5%.
At no point have I been able to actually boot the OS. If I do not select one of the various recovery modes, the phone never progresses past the unlocked warning message with orange text. (If the phone is locked, it warns that it has "failed verification" with red text, but still won't proceed.)
It really seems like I must simply be doing something wrong here. Apparently I have all the tools I should need available and functional. And yet, I cannot restore the phone to stock firmware.
* Does anyone know what I'm doing wrong? And, does anyone know anything about whether I should be using some particular firmware version for this, and if so which one?
* Is the problem the /data directory? How do I repair/restore that?
Click to expand...
Click to collapse
I had written this guide a long time back. It didn't recieve any attention but holds true for your device. If you restore by rollback you can relock the bootloader with the "LOCKED" status rather than the "RELOCKED" which means your warranty won't be void.
Here's the guide:
https://forum.xda-developers.com/honor-8/how-to/restoring-relocking-bricked-frd-l04-t3666360
The only difference is download the rollback packages from this thread:
https://forum.xda-developers.com/ho...users-how-to-restore-downgrade-t3537433/page1
Sent from my Honor 8 using XDA Labs
Thanks for the response.
Is there any reason I should rollback to the version you discuss?
I looked at the backup I made before unlocking, and it was FRD-L14C567B391. So I downloaded this and have been attempting to use it.
Flashing the recovery.img and attempting to 3-button install UPDATE.app doesn't work. It does the same thing it's done all along: immediately stops at 5%.
If I attempt to sideload this I do get a new error (I'll share it when I get home).
BTW, is every android phone so fussy about this stuff? I will never consider this platform again after how unwilling it seems to do basic restore procedures -- not sure if that's just Huawei or all androids. Either way there's really no excuse -- just flash the damn software and try to run it.
marshaul said:
Thanks for the response.
Is there any reason I should rollback to the version you discuss?
I looked at the backup I made before unlocking, and it was FRD-L14C567B391. So I downloaded this and have been attempting to use it.
Flashing the recovery.img and attempting to 3-button install UPDATE.app doesn't work. It does the same thing it's done all along: immediately stops at 5%.
If I attempt to sideload this I do get a new error (I'll share it when I get home).
BTW, is every android phone so fussy about this stuff? I will never consider this platform again after how unwilling it seems to do basic restore procedures -- not sure if that's just Huawei or all androids. Either way there's really no excuse -- just flash the damn software and try to run it.
Click to expand...
Click to collapse
Nope this is only on Huawei phones. The reason I recommend the rollback process is because it helps you restore your phone to the state you bought it (Including a "LOCKED" not "RELOCKED" bootloader). A TWRP flash will get you on the stock ROM but future OTAs might be a pain and safetynet will not pass without Magisk. Using this method you will be on the right recovery and latest firmware with everything official. Also if you have warranty this method restores it.
On phones from Google, Samsung, etc restoring is insanely simple. Huawei doesn't encourage third party development.
Sent from my Honor 8 using XDA Labs
Device: OP7pro purchased from China with a default HydrogenOS installed (GM21 build).
Goal: to install TWRP
======================================================================
Update 1:
Using 10.0.2GM21AA, I managed to convert the HydrogenOS to OxygenOS.
But, after "fastboot boot twrp.img", the phone still freezes at reboot with oneplus logo and "Fastboot Mode" on the screen.
I have tried:
update to 10.0.3, freeze
update to 10.3.0, freeze
rollback to OxygenOS 9.5.1GM21AA, "fastboot devices" no longer detect my cell phone.
update to 9.5.7GM21AA, "fastboot devices" detects no devices.
rollback to 9.5.1, "fastboot devices" detects no devices.
Regarding "fastboot devices" unable to detect devices:
The adb and fastboot tool has been updated to the latest version.
The phone can boot normally into OxygenOS, stock recovery, and bootloader.
adb devices would detect the phone within OxygenOS.
"fastboot devices" was able to detect my other oneplus phone in bootloader.
"sudo fastboot devices" produced no different outcome.
"dmseg" shows that my computer could recognize my other oneplus phone in bootloader as a usb devices, but does not recognize the newly connected OP7P in bootloader.
Now, I am suspecting that my bootloader was somehow broken.
Frustrating.
======================================================================
Original Post:
Steps I have taken so far:
Phase 1. fastboot oem unlock (smooth and easy)
Phase 2. Install TWRP (and fail)
I have read several guides suggesting, within bootloader, "fastboot flash boot twrp.img" or "fastboot boot twrp.img" like a breeze.
I understand that OP7pro uses AB partition, and the purpose is to boot into a temporary twrp and then to install a permenant twrp.
But for me, "fastboot flash boot twrp.img" causes infinite bootloader loop; while "fastboot boot twrp.img" causes a freeze at reboot with oneplus logo and "Fastboot Mode" on the screen.
The latter can be remedied with a reboot, while the former mandates a factory reset using the default oneplus recovery.
Phase 3. Convert HydrogenOS to OxygenOS (and still fail)
After some further studies and several nights' attempts, I noticed that Hydrogen OS implements an old version of fastboot, so fastboot boot into a temporary twrp is not supported.
Instead, I should upgrade into OxygenOS first, but I could not.
The OxygenOS was downloaded from the official site
version 10.3.0.GM57AA released on Jan 6th 2020. md5 checked. this zip file is adb push'd to /sdcard/
Others seem to breeze through the conversion from HOS to OOS without the slightest challenge.
But as soon as I select "local upgrade" from HydrogenOS default update installer and the OxygenOS zip file, I would receive an error prompt "upgrade failed" with the progression bar stopping at 0%.
This doesn't seem to be caused by the version of my HOS, so far, I have tried:
3.1 Updating HOS to the lastest version 10.0.2.GM21 released on Dec 12th 2019, and installing OOS 10.3.0.GM57AA, "upgrade failed"
3.2 With version 10.0.2.GM21, perform a system and cache wipe using the default OP recovery, and installing OOS 10.3.0.GM57AA, "upgrade failed"
3.3 With version 10.0.2.GM21, perform a system and cache wipe as well as a factory reset using the default OP recovery, and installing OOS 10.3.0.GM57AA, "upgrade failed"
3.4 With version 10.0.2.GM21, perform a full downgrade using the default HOS update installer, and installing OOS 10.3.0.GM57AA, "upgrade failed".
The downgrade rom was the official downgrade tool downloaded from:
download.h2os.com/Rollback/fulldowngrade_wipe_18821_190416_2308.zip
I feel I have exhausted all my options.
Is my device malfunctioning or I did something foundamentally wrong in the process?
Would an official North America Oneplus repair service accept this device and help me converting it to OOS?
Maybe that's a dumb idea (I'm not familiar with the process) but if you're supposed to be able to install OxygenOS straight away then maybe you could try a different version? 10.0.2 instead of 10.0.3 comes to mind
Edit: or 10.3 for that matter. I'm 10.0.3 so i don't even know what 10.3 is. That the NA version?
Anyway it just seemed like that's the one thing in the process you described that never changed and i remember there being problems with that sort of thing in the past
SharxX8 said:
Maybe that's a dumb idea (I'm not familiar with the process) but if you're supposed to be able to install OxygenOS straight away then maybe you could try a different version? 10.0.2 instead of 10.0.3 comes to mind
Edit: or 10.3 for that matter. I'm 10.0.3 so i don't even know what 10.3 is. That the NA version?
Anyway it just seemed like that's the one thing in the process you described that never changed and i remember there being problems with that sort of thing in the past
Click to expand...
Click to collapse
I believe 10.3.0 NA is released at the same time with 10.0.3 EU.
Based on what I've read so far, updating from HOS to OOS should be easily handled by the default update installer, provided that the version of OOS is not lower than HOS.
I will give 10.0.2 a shot tonight. I really hope that the hardware was not damaged through the previously rounds of flashing and factory reset.
Which TWRP version are you using?
pister said:
Which TWRP version are you using?
Click to expand...
Click to collapse
I have tested 3.3.1-0, 3.3.1-2, 3.3.1-3, and 3.3.1-4
OblixioN said:
Device: OP7pro purchased from China with a default HydrogenOS installed (GM21 build).
Goal: to install TWRP
Steps I have taken so far:
Phase 1. fastboot oem unlock (smooth and easy)
Phase 2. Install TWRP (and fail)
I have read several guides suggesting, within bootloader, "fastboot flash boot twrp.img" or "fastboot boot twrp.img" like a breeze.
I understand that OP7pro uses AB partition, and the purpose is to boot into a temporary twrp and then to install a permenant twrp.
But for me, "fastboot flash boot twrp.img" causes infinite bootloader loop; while "fastboot boot twrp.img" causes a freeze at reboot with oneplus logo and "Fastboot Mode" on the screen.
The latter can be remedied with a reboot, while the former mandates a factory reset using the default oneplus recovery.
Phase 3. Convert HydrogenOS to OxygenOS (and still fail)
After some further studies and several nights' attempts, I noticed that Hydrogen OS implements an old version of fastboot, so fastboot boot into a temporary twrp is not supported.
Instead, I should upgrade into OxygenOS first, but I could not.
The OxygenOS was downloaded from the official site
version 10.3.0.GM57AA released on Jan 6th 2020. md5 checked. this zip file is adb push'd to /sdcard/
Others seem to breeze through the conversion from HOS to OOS without the slightest challenge.
But as soon as I select "local upgrade" from HydrogenOS default update installer and the OxygenOS zip file, I would receive an error prompt "upgrade failed" with the progression bar stopping at 0%.
This doesn't seem to be caused by the version of my HOS, so far, I have tried:
3.1 Updating HOS to the lastest version 10.0.2.GM21 released on Dec 12th 2019, and installing OOS 10.3.0.GM57AA, "upgrade failed"
3.2 With version 10.0.2.GM21, perform a system and cache wipe using the default OP recovery, and installing OOS 10.3.0.GM57AA, "upgrade failed"
3.3 With version 10.0.2.GM21, perform a system and cache wipe as well as a factory reset using the default OP recovery, and installing OOS 10.3.0.GM57AA, "upgrade failed"
3.4 With version 10.0.2.GM21, perform a full downgrade using the default HOS update installer, and installing OOS 10.3.0.GM57AA, "upgrade failed".
The downgrade rom was the official downgrade tool downloaded from:
download.h2os.com/Rollback/fulldowngrade_wipe_18821_190416_2308.zip
I feel I have exhausted all my options.
Is my device malfunctioning or I did something foundamentally wrong in the process?
Would an official North America Oneplus repair service accept this device and help me converting it to OOS?
Click to expand...
Click to collapse
Use MSMDownload to convert and wipe then start the root process.
SharxX8 said:
Maybe that's a dumb idea (I'm not familiar with the process) but if you're supposed to be able to install OxygenOS straight away then maybe you could try a different version? 10.0.2 instead of 10.0.3 comes to mind
Edit: or 10.3 for that matter. I'm 10.0.3 so i don't even know what 10.3 is. That the NA version?
Anyway it just seemed like that's the one thing in the process you described that never changed and i remember there being problems with that sort of thing in the past
Click to expand...
Click to collapse
Thanks for your advice.
I have successfully converted from HydrogenOS to OxygenOS.
But after the conversion, I still couldn't boot into the temporary TWRP through bootloader.
One Plus 7 Pro (GM1910) Hydrogen OS to Oxygen OS
Hello everyone,
I have just bought my OP 7 pro (GM1910) in China and it came with Hydrogen OS 9.5.9. GM21. I have downloaded the latest Oxygen OS 10.3.0. GM57AA from the official website, but when I try to flesh throughout the local storage I get "System update installation failed" and I can't see the changelog.
Could anybody give me suggestion on how to upgrade to Oxygen OS:
I have tried:
Wiping cache
Factory Reset
Downloaded two different packages
cera22 said:
Hello everyone,
I have just bought my OP 7 pro (GM1910) in China and it came with Hydrogen OS 9.5.9. GM21. I have downloaded the latest Oxygen OS 10.3.0. GM57AA from the official website, but when I try to flesh throughout the local storage I get "System update installation failed" and I can't see the changelog.
Could anybody give me suggestion on how to upgrade to Oxygen OS:
I have tried:
Wiping cache
Factory Reset
Downloaded two different packages
Click to expand...
Click to collapse
Try fastboot method
madsponge26 said:
Try fastboot method
Click to expand...
Click to collapse
Thank you.
Are there any instructions on how to use fastboot to update one plus 7 pro because I am scared that I will brick my device.
cera22 said:
Hello everyone,
I have just bought my OP 7 pro (GM1910) in China and it came with Hydrogen OS 9.5.9. GM21. I have downloaded the latest Oxygen OS 10.3.0. GM57AA from the official website, but when I try to flesh throughout the local storage I get "System update installation failed" and I can't see the changelog.
Could anybody give me suggestion on how to upgrade to Oxygen OS:
I have tried:
Wiping cache
Factory Reset
Downloaded two different packages
Click to expand...
Click to collapse
you got the same problem as me.
use oxygen OS version 10.0.2 through the stock update installer will give you the result you want.
OblixioN said:
I have tested 3.3.1-0, 3.3.1-2, 3.3.1-3, and 3.3.1-4
Click to expand...
Click to collapse
Those TWRP are outdated.
Try the 3.3.1-74 and it will work.
Download it from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Ah my bad then. I'm on 3.3.1-70 and have been for quite a while but was too lazy too check.
Quite possible that I've had problems with some TWRP versions as well. I just seem to forget these things very quickly.
So it's working then i assume?
SharxX8 said:
Ah my bad then. I'm on 3.3.1-70 and have been for quite a while but was too lazy too check.
Quite possible that I've had problems with some TWRP versions as well. I just seem to forget these things very quickly.
So it's working then i assume?
Click to expand...
Click to collapse
Yes, got TWRP, and the phone is primed for additional modding.
I really hope that there can be some indications on the TWRP website or within its official guide regarding the version.
At least inform the users that 3.3.1-4 is not the latest build and may not work.
Hey yall,
so I finally managed to successfully brick my honor :laugh:
Everything was pretty much fine, I was messing with trying different ROMs. Then I used the "Change location" option in HWOTA8 (it probably flashed some extra files) and my systems "erecovery" or something likely essential "dissappeared".
Fastboot works, I tried flashing 'system' and recovery images with no success. It won't accept TWRP or any other image as I get "partition size get error"
When I try to boot into recovery or system, I get the error
Error Mode message: Func no 11 [recovery image], Error NO 2 [load failed]
I tried dload methods with (B132, B340 and some other versions, I get the Error Mode anyway)
What I think is the core of the problem could be one of following:
boot.img,
erecovery
frp
I get a boot loop no matter what I do.
The phone model is BLN-L22 indian (debranded from BLN-L21) and the last flashed ROM was Oreo
The FRP and Bootloader are unlocked.
I think it could work if I'd flash every partition, but it doesn't seem to work with images I got from "update.app"
Could you recommend me some repair/flashing tools/flashing files?
Any help in the investigation is greatly appreciated
Update: Just bought DC Phoneix
Now I managed able to boot into the "update via usb" screen. (with the help of DC Phoneix)
I can access adb, altho I cannot use adb shell, because it cannot access /bin/sh
Does having access to adb give me any advantage?
Solved using this <3. Now I'm at android 4
https://forum.xda-developers.com/honor-6x/how-to/guide-unbrick-honor6x-boot-fastboot-t3904381
Hi,
I'm quite desperate by trying to restore this phone (has PRA-LX1 at the back) to stock firmware. I've been using Lineage 14.1 (namely lineage-14.1-20180501-UNOFFICIAL-hi6250) for some time (several years). Now I decided either to restore stock firmware and lock the bootloader and everything so the phone will be like original (and services like Google Pay will work), or to flash something based on Android 10. I started with the second option.
In the phone there was some old version of TWRP (not really sure, maybe 3.0.2), so I decided to replace it with a newer one (twrp-3.4.0-0-prague.img). That was unsuccessful, there's no TWRP anymore and I'm unable to flash it back, tried adb+fastboot and ended up with errors like 'partition length get error' when tried "fastboot flash recovery_ramdisk twrp.img" or "ERROR MODE" "Func NO : 11 (recovery image) / Error No : 2 (load failed!)".
I'm still able to boot back to the Lineage 14.1. I'm also able to boot into the dload mode, but have no firmware that would load, it just says "software install failed". I also tried the eRecovery mode, it's able to connect to WiFi, but ends up like "getting package info failed error" (does that mean those servers where the eRecovery wants to download from are already dead? Can I simulate them live with the proper content on my local network with some kind of web server or so?).
I'm just in the phase where I don't know what to try next and why I'm still unsuccessful. Is there a way to revert back to original firmware and evetually have the official Android 8 version of it?
Thanks.
Edit:
I apologize for this post, I found a great tool called Multi-Tool for HUAWEI & HONOR which told me I have PRA-L1 and also flashed the correct TWRP. I'm so stupid I don't know what model do I use... :-/
Sorry about that again, mea maxima culpa.
(w) said:
Hi,
I'm quite desperate by trying to restore this phone (has PRA-LX1 at the back) to stock firmware. I've been using Lineage 14.1 (namely lineage-14.1-20180501-UNOFFICIAL-hi6250) for some time (several years). Now I decided either to restore stock firmware and lock the bootloader and everything so the phone will be like original (and services like Google Pay will work), or to flash something based on Android 10. I started with the second option.
In the phone there was some old version of TWRP (not really sure, maybe 3.0.2), so I decided to replace it with a newer one (twrp-3.4.0-0-prague.img). That was unsuccessful, there's no TWRP anymore and I'm unable to flash it back, tried adb+fastboot and ended up with errors like 'partition length get error' when tried "fastboot flash recovery_ramdisk twrp.img" or "ERROR MODE" "Func NO : 11 (recovery image) / Error No : 2 (load failed!)".
I'm still able to boot back to the Lineage 14.1. I'm also able to boot into the dload mode, but have no firmware that would load, it just says "software install failed". I also tried the eRecovery mode, it's able to connect to WiFi, but ends up like "getting package info failed error" (does that mean those servers where the eRecovery wants to download from are already dead? Can I simulate them live with the proper content on my local network with some kind of web server or so?).
I'm just in the phase where I don't know what to try next and why I'm still unsuccessful. Is there a way to revert back to original firmware and evetually have the official Android 8 version of it?
Thanks.
Edit:
I apologize for this post, I found a great tool called Multi-Tool for HUAWEI & HONOR which told me I have PRA-L1 and also flashed the correct TWRP. I'm so stupid I don't know what model do I use... :-/
Sorry about that again, mea maxima culpa.
Click to expand...
Click to collapse
What version of stock firmware did you install? You only did PC method & not mobile or dload method? I don't have my PC so I'm stuck with trying dload.