{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, without more information about the actual error message... my suggestion would be to flash a full image from Google without the wipe command flag. (You remove the "-w" from the flash-all.bat)
You can try using the browser based flash tool if downloading platform tools/ADB is too much for you. It's supposedly easier, but I've never used it before. It also might wipe your device by default, so be careful?
MBenzKH said:
Help!
Click to expand...
Click to collapse
Being bootloader locked, about the only thing you can do is flash a FULL OTA IMAGE available from Google's website and flash it from recovery using ADB. This procedure has also been called a "rescue ota". You cannot flash a full image via fastboot (because you are locked) but you can flash the OTA from recovery. There are instructions on Google's download page. Just pick the newest OTA image available. The most important thing is to get adb/fastboot set up correctly on your PC. Always easier to learn when your phone is working properly, but still not that difficult to accomplish and verify proper installation. Start with the very latest (February 2021) adb/fastboot binaries. Drop those files (and the image) into a folder and add that folder to your path statement. ADB only works in recovery NOT in fastboot mode like your screenshot. If you have questions or need more info, PM me.
v12xke said:
Being bootloader locked, about the only thing you can do is flash a FULL OTA IMAGE available from Google's website and flash it from recovery using ADB. This procedure has also been called a "rescue ota". You cannot flash a full image via fastboot (because you are locked) but you can flash the OTA from recovery. There are instructions on Google's download page. Just pick the newest OTA image available. The most important thing is to get adb/fastboot set up correctly on your PC. Always easier to learn when your phone is working properly, but still not that difficult to accomplish and verify proper installation. Start with the very latest (February 2021) adb/fastboot binaries. Drop those files (and the image) into a folder and add that folder to your path statement. ADB only works in recovery NOT in fastboot mode like your screenshot. If you have questions or need more info, PM me.
Click to expand...
Click to collapse
I've not had a locked boot loader for longer than 7 days in the past decade, so my experience is poor... but I always thought that the locked bootloader would deny usage of foriegn images like a Magisk patched boot.img or something else. It's surprising to me that you would not be able to flash a full Google image directly with Fastboot. Am I wrong?
jljtgr said:
I've not had a locked boot loader for longer than 7 days in the past decade, so my experience is poor... but I always thought that the locked bootloader would deny usage of foriegn images like a Magisk patched boot.img or something else. It's surprising to me that you would not be able to flash a full Google image directly with Fastboot. Am I wrong?
Click to expand...
Click to collapse
From the screenshot provided, OP's bootloader is locked, so he cannot fastboot flash ANYTHING. Within the stock recovery there is an option to flash a full OTA image via ADB from a laptop or PC. A recovery OTA is the only way forward in this case, and is dependent on whether he has a working recovery. I've seen this method save many bootloader locked phones. Hopefully OP will come back and let us know he was successful.
Related
Hi,
I received the official update for my l10 from b126 to b133.
But after download I receive a checksum error.
Any ideas? Also the downloaded update.zip cannot be opened with zip viewers.
PS: rooted but stock recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: solved by deleting the HWOUC folder on external SD and initiated update again
Almost the same problem for me, once it reaches the recovery to install the update, it gives error.
Worked for me then, don't forget to be on stock recovery
Yeah I was on TWRP but then I restored the stock recovery taken from this post to install this OTA update:
http://forum.xda-developers.com/showpost.php?p=53980121&postcount=4
But no matter what after everything is downloaded and I give the 'ok' to install it, it stops at the recovery giving a 'FAIL' message big a quarter of the screen.
I'm using the same. Maybe its worth to download again by deleting the folder and initiating the download again.
Any hint on why it fails?
May I know how did you install the stock recovery?
I did the following:
-Connect phone to PC by debug mode
-adb reboot bootloader
Then phone goes into bootloader, flash mode:
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
-fastboot flash recovery2 recovery2.img
I noticed that in the archive of the stock recovery, there's also a build.prop file. Am I missing something perhaps?
Anyway the "FAIL" error appears when the recovery is attempting to install the update at the 2/10 of the status bar, therefore after the checksum which means the update file is not corrupted.
I also tried several times to delete and re-download the update as you said but still no success..
No, I only flashed recovery.img via flashify.
So maybe it is due to recovety2.img? Just a guess
I just tried to flash just the recovery.img but still the same error.
I honestly can't think of any other solution now than a a lot of time wasting full wipe..
I had the same problem. Tried deleting folder etc.
What worked for me was updating using HiSuite. Connect phone with cable with pc/laptop and use HiSuite for update. Made backup just to be sure but wasn't needed.
I was trying to do a nandroid backup and update via HiSuite like you suggested but then I encountered this.
Surely something is wrong my system partition lol, any ideas of why is it so huge? The previous backups were just 1.5 GB.
Perhaps I'll just do a backup of the apps with Helium and move on.
That's strange. For your information. I had already the original recovery in place. So I did the backup from HiSuite (It came with this option). I didn't made a backup with TWRP or Nandroid backup.
I'll try again this weekend and let you know the results, thanks anyway!
Hi, my Huawei P7-L00 is soft-bricked I think. I have access to Fastboot mode and recovery mode though, but I think I don't have any ROM installed so I can't get past the boot logo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an image of my fastboot screen. It says Phone unlocked so I think my bootloader is unlocked. Using fastboot, I can flash CWM recovery but I cannot find the correct version for the L00, the version I have is for the L05 or L07.
As you can see It says it is only for the L05 or the L07. Does anyone know a CWM recovery for the L00 they can share the download link to? TWRP recovery does not work on this phone I am unable to press any of the buttons and it renders unresponsive. Or, If anyone has the stock recovery for the L00 I would appreciate that as well.
The problem with the CWM recovery for L05 and L07 is that I cannot install updates for zip files. I have tried numerous ROMs including official and third party ROMs but the same error (bad, Installation aborted) occurs. I believe this is because of the CWM version mismatch.
Also, I have tried to use adb to flash the ROM on, but my adb cannot find my device in bootloader mode, or when my phone is in the bootloop. However, fastboot is able to recognize it in fastboot mode.
Overall, if anyone could provide help with the following areas, I would greatly appreciate it:
1. Find a working CWM recovery for the Huawei P7-L00.
2. Find a stock recovery for the Huawei P7-L00 so I can install an official ROM from Huawei's website.
3. Help me find a way to get adb to recognize my device
1. In fastboot mode you have to work with fastboot, not with adb.
2. Download firmware version you had, extract using Huawei Update Extractor cust.img, system.img, boot.img (recovery.img if you want get back to stock recovery).
3. Flash images via fastboot:
Code:
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
That's all. Three simple steps. What's the problem?
Or you can download your official ROM, extract official recovery from there and flash it and than flash the official ROM with forced update
Thanks for the quick responses! I used Kostyan_nsk's method and resolved the problem but I'm sure ibeqa's method would've worked just as well, but maybe a bit more time consuming. Thank you!
Hey there, I would have seemed to have soft bricked my phone as well. And apparently, it's says PHONE LOCKED unlike the one that has been posted above? Any advice on how to proceed?
Thanks
P/S: my phone is P7-L10
You could try to use Kostyan_nsk's method as well, but if that doesn't work, you need to figure out a way to unlock bootloader on your phone.
BadgerDev said:
You could try to use Kostyan_nsk's method as well, but if that doesn't work, you need to figure out a way to unlock bootloader on your phone.
Click to expand...
Click to collapse
do you have a process in mind to unlock bootloader in this case ?
Joseluisska said:
do you have a process in mind to unlock bootloader in this case ?
Click to expand...
Click to collapse
Unfortunately, I don't. My phone came with it's bootloader unlocked so I never went through the process of trying to unlock it.
Joseluisska said:
do you have a process in mind to unlock bootloader in this case ?
Click to expand...
Click to collapse
Flash firmware 133 and you'll have unlocked bootloader
For any soft brick
Kostyan_nsk said:
1. In fastboot mode you have to work with fastboot, not with adb.
2. Download firmware version you had, extract using Huawei Update Extractor cust.img, system.img, boot.img (recovery.img if you want get back to stock recovery).
3. Flash images via fastboot:
Code:
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
That's all. Three simple steps. What's the problem?
Click to expand...
Click to collapse
Thank you so much! You helped me a lot.
A reference guide for someone how to do it (fastboot procedure and commands) is here:
Hi All. Complete newbie to the forum here......in search of advice!
I've just got my new OnePlus 3T, so wanted to get it all set up and rooted before switching over from my Galaxy S5.
After reading several guides I followed the below steps:
Completed the OTA update to OOS 4.0.2
Unlocked the boot loader
Flashed TWRP 3.0.3
Booted into Recovery and TWRP asked for the encryption password (which was the same pattern I used in normal mode)
Internal memory was accessible so I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip. (I couldn't tell if they flashed successfully).
Rebooted
When the phone tries to reboot, I eventually get a screen saying 'Encryption Unsuccessful' and suggests I need to factory Reset.
When I select to reset, it boots back in to TWRP, but there is no request for the encryption pattern this time, and internal memory doesn't seem to mount. (showing as 0mb).
I'm wondering what my next step should be?
Should I try to flash the latest TWRP (3.0.4) via ADB?
Or would I be better off trying to flash back on stock recovery and the stock OOS 4.02 rom, and then wait for a newer TWRP before trying to get root access again?
.......Or will none of the above work?!
All I was really looking to do was root the phone. I'm not planning on changing from the stock OOS rom. I also don't mind if its encrypted or not encrypted.
I have had a look through some of the threads, but cant find examples of this scenario. Any help appreciated!
Which SuperSU file did you flashed?
The-Wexican said:
I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip.
Click to expand...
Click to collapse
I hope you didn't flash in that exact order. That could possibly be the reason for your issue. Also, you don't need the verity zip if you're flashing SuperSU.
Thanks for the feedback. Below is a link to the guide I followed on the Oneplus forums:
[GUIDE] OnePlus 3T: How to Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup and More !! (It wont let me link the thread as I'm a new user, but Google will show it!
That suggested to flash them in that order, I think.
SuperSU-v2.79-201612051815.zip was the SuperSU I used.
All, just to add, I don't need to recover any data or anything like that. I'm just looking for the best way to get out of this bot loop (of sorts).
I'm kinda thinking that because TWRP Recoveryseems to load OK, I could maybe flash back on the stock recovery and then side load the stock rom?
Any thoughts?
Or is it worth a shot at updating to the latest TWRP first (3.0.4)?
Below is the message I see when I try to boot the phone normally now (not in recovery)........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The-Wexican said:
Below is the message I see when I try to boot the phone normally now (not in recovery)........
Click to expand...
Click to collapse
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
stephlal said:
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
Click to expand...
Click to collapse
Awesome!
That worked. Thanks for your help!
Now running OP3T with OOS 4.0.2, TWRP recovery, rooted with SuperSU, and I even cleared the DM-Verity nag screen by booting into bootloader and running:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Very happy now!
EDIT: I could fix this, if you have a device that works with HuRUpdater just download an update.zip, put that and the HuRUpdater zip in a new folder and it updates the recovery through TWRP so that's how I fixed it.
So I'm stuck in ERROR MODE. The only mode that works for me is Fastboot. I tried to reinstall recovery_ramdisk, system, cust and userdata but still in the same error. Before the brick EMUI 9.1 was installed. I've tried to install LineageOS 16 on my phone with TWRP, but I got error 7. First I've restored the nanddroid backup and I went stuck at a bootloop. I've entered eRecovery and downloaded the lastest version available on server and got this error. Any solutions for it? And the bootloader is unlocked, same with FRP. The error that shows in the screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is Func. NO: 11 (recovery image) and Error NO: 2 (load failed). Would be appreciated if someone answers.
Here is how Fastboot looks like...
I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.
Another_Alchemist said:
I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.
Click to expand...
Click to collapse
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.
LucastheBowser said:
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.
Click to expand...
Click to collapse
Hello! It seems Im having a same problem, since this device is somewhat discontinued by huawei, I cannot update it to any version, and cannot downgrade it either, using the "classic" sdcard method. Could you tell me how you used HuRupdater to flash the rom on yours?
The Solution for me->
Full package->
Software.rar
drive.google.com
Put your device on Testpoint mode:
Disconect the batery, join the point to gnd and conect usb cable on your pc.
and ..
and later you can update by SD
Hello All,
Quick and dirty guide.
Warning!
I'm not responsible for any damage to you, to your device or to your data. Do this at your OWN RISK! If you don't know what you are doing, STOP now!
Steps to flash the ROM using TWRP:
Be on Android 11 (MIUI 12.5) and flash TWRP. There is a guide here on how to do it, so i'm not posting that.
Obviously, you'll need unlocked bootloader so if it's not unlocked, your case is lost
Download the ROM in the title from here and copy it to your phone
Reboot to TWRP
If you want, i guess you can wipe data - i haven't done this
Flash the ROM like you would any other (install and select the zip you copied over from the above link)
At the end, it'll give you mounting error but it's all good, reboot
Wait for the ROM to settle if you wish - you can stop here
For Magisk, follow the below steps
Enable developer settings and USB debugging
Install the Magisk Manager app (latest version 24.1 at the time of writing this little guide)
Turn off the phone and boot it into fastboot mode
Start the fastboot app of your choice from your pc and connect your phone via USB (I'm using Minimal ADB and Fastboot, you can find it on XDA)
issue the following commands in the same order:
Code:
fastboot devices
if you don't get as a response a few digits of your device ID with the fastboot text next to it, you'll doing something wrong (driver might be or you are not in fastboot mode)
Code:
fastboot flash boot_a patched_boot.img
if the command completes you'll get a finished message
Code:
fastboot flash boot_b patched_boot.img
patched_boot.img is the full path of the patched boot.img file
Code:
fastboot reboot
wait for the device to boot.
Patched boot.img is attached but if you wish, you can extract it from the rom yourself using payload dumper and patch it on your phone with Magisk. The attached boot.img is patched with Magisk 24.1, this is what you'll need as well - this is the current version. You need to unzip the attached file of course!
Enjoy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.
Pichulec said:
Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.
Click to expand...
Click to collapse
what do you mean with "no fastboot image"?
There are two types of images - recovery and fastboot.
Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(
Yuditkiichi said:
Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(
Click to expand...
Click to collapse
Hi, if TWRP worked before, it should as well now.
donjamal said:
Hi, if TWRP worked before, it should as well now.
Click to expand...
Click to collapse
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
I would probably relfash twrp as long as I'm still on 12.5.
Yesterday received OTA update for my 11t pro. I'm not in Pilot Programm..
Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
for now twrp not working for a12.
wait for update
All can download rom here https://xiaomifirmwareupdater.com/miui/vili/stable beta/V13.0.1.0.SKDMIXM/
and use updater to update it.. that dont need any mi pilot.. i just installing it.. yeeah!