after fastboot oem relock I can boot just to TWRP, PWR+Vol- will boot only to TWRP, also if if press reboot to bootloader in TWRP it boots into TWRP.
tried to install update.zip but throws errors
what state am I in an any idea how to recover?
I just wanted to unroot/relock
Thanks for any advise
Phone was working, unlocked and still rooted ?
Then, you decided to boot to bootloader to send a 'fastboot oem relock' command then you rebooted ?
Now you stated bootloader is replaced with twrp ?
When trying to flash random update.zip throught twrp, it gives you error message.
What's the problem here ?
---------- Post added at 15:16 ---------- Previous post was at 15:14 ----------
xequtor said:
what state am I in an any idea how to recover ?
Click to expand...
Click to collapse
...
oslo83 said:
Phone was working, unlocked and still rooted ?
Then, you decided to boot to bootloader to send a 'fastboot oem relock' command then you rebooted ?
Now you stated bootloader is replaced with twrp ?
When trying to flash random update.zip throught twrp, it gives you error message.
What's the problem here ?
---------- Post added at 15:16 ---------- Previous post was at 15:14 ----------
...
Click to expand...
Click to collapse
yes, was working, unlocked and still rooted
also yes to 'fastboot oem relock'
bootloader was TWRP before
not flashing random update.zip, just the b120.
I don't think trying to flash stock update.zip through twrp will achieve anything...
oslo83 said:
I don't think trying to flash stock update.zip through twrp will achieve anything...
Click to expand...
Click to collapse
I just extracted what's in update.app, recovery.img, boot.img etc, any idea what do I can or must flush?
I suspect the bootloader is locked, is there a way to unlock it from within TWRP, same as with fastboot oem unlock xxxxxxx ?
I'll assume you meant bootloader was twrp AFTER you locked bootloader and was still bootloader before you locked it ?
By the way, before you locked you're bootloader, you were on which firmware and wich region ?
oslo83 said:
I'll assume you meant bootloader was twrp AFTER you locked bootloader and was still bootloader before you locked it ?
By the way, before you locked you're bootloader, you were on which firmware and wich region ?
Click to expand...
Click to collapse
yes, correct TWRP was before I locked and it is still now.
I was on B120 EU
Ok, from your C432B120 you could try to restore the dload way to stock C432B130 with this file :
http://androidhost.ru/v5
(instructions are inside the file, and you will need a formated exfat >8GB sdcard)
Source:
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
oslo83 said:
Ok, from your C432B120 you could try to restore the dload way to stock C432B130 with this file :
http://androidhost.ru/v5
(instructions are inside the file, and you will need a formated exfat >8GB sdcard)
Source:
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
update.app in /sdcard/dload/ folder
volume down+ volume up+ power button
just did that, nomather which key combination I press, TWRP will boot
I did try to flash recovery.img in TWRP and now I'm in this, no more TWRP but ERROR MODE
soo, I guess I reach the point of no return just send for repair? I'm still under warranty
after draining the battery overnight as turning off did not work, I'm back to TWRP, TWRP appeared "magically" again
now the question ist, what can I flush in TWRP to go in to fastboot/bootloader again?
update:
forced to reproduce the ERROR MODE (see previous photo) with flashing boot.img and recovery.img in TWRP and could unlock bootloader again with:
c:\adb>fastboot oem unlock xxxxxxxxxx
< waiting for any device >
--------------- hier I pressed Vol- plus PWR to force reboot after that fastboot unlocked and had on the phone the question if I want to unlock------------------
...
(bootloader) The device will reboot and do factory reset...
OKAY [ 20.001s]
finished. total time: 20.021s
now I have to figure out what to flash with fastboot, anyone have an idea?
update2:
drained the battery, rebooted Vol- + PWR
and I'm in fastboot now, stange stuff happens here
but same question, what to flash with fastboot to get it working again?
update 3:
extracted recovery.img and recovery2.img from B120 FW and flashed with fastboot
then B130 from https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
now everything works.
the important thing was to unlock bootloader, even if you get the ERROR MODE you still have fastboot ad can lock/unlock the bootloader, see post #13
Congratulations
Related
Hello Guys,
I was trying to install OxygenOS 3.1.0 when I was on Sultanxda's CM13 but instead bricked the device.
What I did:-
1. Rebooted to TWRP and flashed stock OOS recovery and then clicked reboot into recovery.
2. Instead of rebooting in recovery my phone got stuck at the OnePlus logo.
3. I booted into fastboot to flash twrp.img but it says 'writing 'recovery'...
FAILED (remote: device is locked. Cannot erase)'
4. I repeated the same with stock recovery but no success and was not even able to boot to CM13 now.
Hence I was stuck on the OnePlus logo without any booting ROM or recovery and a locked bootloader (according to fastboot)
What I have already tried but failed:-
1. Tried to root with kingroot etc. (Before bricking)
2. Tried to unlock bootloader but failed because it has no recovery.
3. Tried to flash stock OOS 2.1.3-x
4. For now I used fastboot continue to boot back into CM13
Please help, I'm now stuck with cm13 without root and without any recovery installed.
P.S. I'm not even sure that if I clicked reboot then the phone will boot.
Thanks.
Okay, calm down.
Go to developer options and see if "OEM Unlocking" is enabled. If not, enable it.
Cool. Now enable USB Debugging, connect the phone to PC, open CMD and type
Code:
adb reboot bootloader
then
Code:
fastboot oem unlock
Download TWRP from the official website, rename it to recovery.img and then
Code:
fastboot flash recovery recovery.img
Now you have a recovery and an unlocked bootloader. Profit?
I hope this helps.
Thunderbottom said:
Okay, calm down.
Go to developer options and see if "OEM Unlocking" is enabled. If not, enable it.
Cool. Now enable USB Debugging, connect the phone to PC, open CMD and type
then
Download TWRP from the official website, rename it to recovery.img and then
Now you have a recovery and an unlocked bootloader. Profit?
I hope this helps.
Click to expand...
Click to collapse
Thanks for your help,
But if you read my post then you'll understand that due to absence of a recovery I can't unlock the bootloader and hence cannot flash twrp
gavisharora said:
Thanks for your help,
But if you read my post then you'll understand that due to absence of a recovery I can't unlock the bootloader and hence cannot flash twrp
Click to expand...
Click to collapse
You don't need recovery to unlock bootloader, you need fastboot.
Thunderbottom said:
You don't need recovery to unlock bootloader, you need fastboot.
Click to expand...
Click to collapse
But in OnePlus devices the phone asks a confirmation through recovery recovery to wipe data and unlock
gavisharora said:
But in OnePlus devices the phone asks a confirmation through recovery recovery to wipe data and unlock
Click to expand...
Click to collapse
Try the Mega Unbrick Guide then.
Deleted
Same problem. But i dont have pc with windows and can't use mega unbrick guide(
Any news with solution?
I just install TWRP RECOVERY without unlock tablet.
Now, when booting i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
And fastboot mode shows the message "Invalid boot image !!!".
Fastboot mode is fine. I try flash boot.img recovery.img i can find.
But it still not work.
I download ASUS website firmware V10.10.3.39.
I try fastboot update, but get the message "update package has no android-info.txt"
Because i dont unlock bootloader first, i cant fastboot boot twrp.img.
Does anyone have stock boot.img recovery.img system.img or update.zip for ME302KL? Or anything I can try?
wch0503 said:
I just install TWRP RECOVERY without unlock tablet.
Now, when booting i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
And fastboot mode shows the message "Invalid boot image !!!".
Fastboot mode is fine. I try flash boot.img recovery.img i can find.
But it still not work.
I download ASUS website firmware V10.10.3.39.
I try fastboot update, but get the message "update package has no android-info.txt"
Because i dont unlock bootloader first, i cant fastboot boot twrp.img.
Does anyone have stock boot.img recovery.img system.img or update.zip for ME302KL? Or anything I can try?
Click to expand...
Click to collapse
Did you find any solution? İ have same problem.
wch0503 said:
I just install TWRP RECOVERY without unlock tablet.
Now, when booting i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
And fastboot mode shows the message "Invalid boot image !!!".
Fastboot mode is fine. I try flash boot.img recovery.img i can find.
But it still not work.
I download ASUS website firmware V10.10.3.39.
I try fastboot update, but get the message "update package has no android-info.txt"
Because i dont unlock bootloader first, i cant fastboot boot twrp.img.
Does anyone have stock boot.img recovery.img system.img or update.zip for ME302KL? Or anything I can try?
Click to expand...
Click to collapse
Try unlocking bootloader type in
* Fastboot OEM unlock
Danyaelgaina said:
Try unlocking bootloader type in
* Fastboot OEM unlock
Click to expand...
Click to collapse
I've got the same problem when I was installing And 7 on the device. Unfortunately I need a step by step leading! I'm not exactly expert.
MikeHugi said:
I've got the same problem when I was installing And 7 on the device. Unfortunately I need a step by step leading! I'm not exactly expert bbbbbiiiittttccchhhheeesssss.
Click to expand...
Click to collapse
Type in fastboot oem unlock
Or get tutorial for bootload3r unlock for ur phone
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
MikeHugi said:
I've got the same problem when I was installing And 7 on the device. Unfortunately I need a step by step leading! I'm not exactly expert bbbbbiiiittttccchhhheeesssss.
Click to expand...
Click to collapse
Ok
I have done it already , but nothing happened by typing "Fastboot OEM unlock"!
I couldn't find any tutorial for bootloader unlocking for ME302KL
I have the same problem and my pad does not unlock. What solution is there and where should I write fastboot oem unlock?
Thank you
---------- Post added at 04:11 PM ---------- Previous post was at 04:04 PM ----------
Danyaelgaina said:
Try unlocking bootloader type in
* Fastboot OEM unlock
Click to expand...
Click to collapse
please help me
im in the iran
me302kl-unluck app writing .
an unknown error occurs. which may be a network connection issue.
please help me
Hi all,
Currently running Oreo (via OldDroid manual update) then LOS 15.1 (Berkley unofficial) on top, which is great but would like NFC, buttons, flashlight.
What is the best method to reinstate this functionality? I have tried the rollback for OldDroid rollback to no avail. I believe this method assumes you are rooted, which i am not.
Happy to be on EMUI 5 if necessary as i believe i can now update to Oreo OTA.
Cheers
Can i provide further pertinent information or ask elsewhere to get replies?
What did you do in the fist place to go from stock oreo to LOS 15.0 ; any links ?
Thank you.
I flashed the system image using "fastboot flash system system.img" via article https://www.xda-developers.com/lineageos-honor-view-10-huawei-mate-10-pro-project-treble/
Cheers
I think, once unrooted, you'll have to flash back stock system.
oslo83 said:
I think, once unrooted, you'll have to flash back stock system.
Click to expand...
Click to collapse
Great, thank you. I am not rooted so I extracted the system.img from STF-L09SC432B360a (from http://pro-teammt.ru/firmware-database/?firmware_model=STF-L09&firmware_page=0) using this guide https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
Then using that stock emui 8 system image:
"fastboot flash system system.img"
I receive the following error:
error: cannot load 'SYSTEM.img'
Any ideas?
Cheers
Another attempt at system.img extract using my windows box and the windows software referred to in https://forum.xda-developers.com/mat...files-t3756733.
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
I performed this reset and device booted to TWRP some commands took place but too quick (saw selinux buts thats it). Device rebooted twice then loaded Huawei eRecovery where the only option is :
Download latest version and recovery
Restore system with wifi
Entered wifi details
Getting package info from server
Getting package info failed.
Booting into TWRP the 'Factory Reset' option performs the same process that i saw when Huawei eRecovery recommended the factory data reset. Some i'm confident in what happened at that point now. Unsure as to what to try at this point. The phone does not boot into EMUI and will only boot to Huawei eRecovery.
The bootloader is unlocked, as per the process to install LineageOS 15.1 in the link in the OP. I've not checked if its still unlocked, but guess that could be causing a problem?
Just checked and bootloader is unlocked.
Interestingly the process to re lock it from the Huawei site (https://emui.huawei.com/en/unlock_step) shows that you have to use the same command to lock the bootloader as to lock it again:
Note: to re-lock the bootloader after unlocking it, restore the device’s software to the Huawei official version using a microSD card then switch the device to fastboot mode and enter “fastboot oem unlock ****************” in the computer’s command prompt, where * refers to the 16-digit unlock password. The device will then restart, and the bootloader lock status will change to “Bootloader Lock State: RELOCKED”.
If i follow those instructions i get the below error:
Code:
fastboot oem unlock **************** <-my 16 digit code
...
FAILED (remote: already fastboot unlocked)
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Thanks. So I can leave the boot loader unlocked at this point and run stock emui? I'll flash stock recovery. Perhaps that will suggest factory reset and then I'll be able to boot.
Thanks again.
oslo83 said:
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Click to expand...
Click to collapse
In order to revert to the stock recovery is it necessary to flash all three recovery images from the update.app file? :
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Looking at flashing the recovery_ramdisk image with the stock version i have extracted using the below:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Noticed the stock recovery_ramdisk i extracted has a filename of 'RECOVERY_RAMDIS.img', not ending in 'K' for 'RAMDISK. Presumably i can simply rename my recovery_ramdisk to "RECOVERY_RAMDISK.img" unless a 15 character filename is a limitation, or adjust my fastboot command to :
Code:
fastboot flash recovery_ramdisk RECOVERY_[B]RAMDIS[/B].img
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
mightyjcb said:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
Click to expand...
Click to collapse
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
oslo83 said:
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
Click to expand...
Click to collapse
Many thanks @oslo83 followed that and just as you said hardware functioning correctly once again!
One further question for future reference, am i now in a position to apply OTA updates when released?
Cheers
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
mightyjcb said:
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
Click to expand...
Click to collapse
You need to flash stock recovery and do a factory reset in stock recovery.
oslo83 said:
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
Click to expand...
Click to collapse
Great, i should be able to meet this criteria quite easily then :
+ I've never rooted the device
+ I have reverted to stock recovery
+ I flashed the stock kernel over the top of the button fix kernel mentioned earlier in this thread.
Thanks again for your help, much appreciated.
zxz0O0 said:
You need to flash stock recovery and do a factory reset in stock recovery.
Click to expand...
Click to collapse
That seemed to do the trick! Ta.
[you can use this tool to solve brick problems https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279]
Hi everyone, I'm "new" on the forum. "New" because they are days looking for answers to repair my Honor 9...
After unlocking it, installed twrp and RRos 6.0 I made a mistake, I uninstalled the gapps from the system manually, and after restarting the phone, various error messages continued on terminated processes (com.google... stopped working).
I tried again to reinstall the gapps via twrp but nothing to do, after trying to reinstall the RRos (with full wipe), new error messages kept going out, but this time not only the gapps.. (trebuchet etc ...).
Trying several wipes and reinstallations of the RRos, I tried to go back to the EMUI 8.0, so I tried to install the European firmware via SD and folder DLOAD, but once I got to 5% the installation crashes.
Via fastboot I also tried to install the twrp again, but the recovery stock continues to appear.
Looking on xda and generally on the internet I have found various people with this problem and they have tried to solve with programs like DC-Unlocker or Phoenix, but they had locked bootloader or frp .. I from fastboot I have PHONE Unlocked and FRP Unlock.
I also tried to flash the img contained in the UPDATE.APP file, but nothing happens ... just recovery stock. Help please i am desperate :crying: and sorry for my english.
EDIT - 27/03/2018
-I solved many of the problems I had in this post, now I'm still in the twrp and I can not flash the stock firmware.
-I'm trying to format the microsd in exfat and then install update.app.
-I can not copy the 4.66GB update.app file to the MicroSD in exfat, fat or ext4 via twrp / PC. I will try with another SD reader.
-I formatted the sd in exfat and I managed to copy the dload folder, run the restore and no longer blocked at 5% (gave a 99% error). The system started and I went back to the b130 with nougat, now I try again to install the b120 to restore the captive keys. (trying again with hwota)
-Hwota worked, now with the b120 everything works correctly, now I'm looking for a way to restore OTA Updates.(I will try to install the b183)
-With the b183 ota works, but not the keys / flash. I will try to downgrade to b120, than reupdate to b183 without wipe anything .
-b120 keys working, update to b183 and not working again, I try update ota oreo and search for a kernel.
-Almost everything resolved! After switching from the b183 to the b360, I reunlocked the Honor and installed the kernel with the fix to the capacitive keys. Relock the phone but the Google Logo appears at boot, even after installing the stock kernel.
Kodex_99 said:
Trying several wipes and reinstallations of the RRos, I tried to go back to the EMUI 8.0, so I tried to install the European firmware via SD and folder DLOAD, but once I got to 5% the installation crashes.
Via fastboot I also tried to install the twrp again, but the recovery stock continues to appear.
Click to expand...
Click to collapse
If you were on oreo, it's normal the nougat service repair files don't work with dload.
You're still on RRos ?
oslo83 said:
If you were on oreo, it's normal the nougat service repair files don't work with dload.
Click to expand...
Click to collapse
Can I try with non-European firmware such as Russian or Chinese upgraded to Oreo?
oslo83 said:
You're still on RRos ?
Click to expand...
Click to collapse
No, I did several wipe and tried to restore other system.img
Kodex_99 said:
Can I try with non-European firmware such as Russian or Chinese upgraded to Oreo?
No, I did several wipe and tried to restore other system.img
Click to expand...
Click to collapse
To my knowledge, they are no oreo service repair firmware publicly available yet. So, for now, no flashing firmware with dload once on oreo.
You could use HWOTA8to8 or HWOTA8to7 or the translated russian TOOL from last febuary.
oslo83 said:
You could use HWOTA8to8 or HWOTA8to7 or the translated russian TOOL from last febuary.
Click to expand...
Click to collapse
I only find missing files
Honor 9 multitool eng (feb2018)
https://forum.xda-developers.com/hon...5#post75662105
oslo83 said:
Honor 9 multitool eng (feb2018)
https://forum.xda-developers.com/hon...5#post75662105
Click to expand...
Click to collapse
========================================================================================
Copying the firmware files to the SD card
Please wait ....
========================================================================================
adb: error: failed to get feature set: no devices/emulators found
unfortunately when I try to install the EMUI 8 (the one I had previously installed) from fastboot I get this error message..
Kodex_99 said:
Copying the firmware files to the SD card
Please wait ....
========================================================================================
adb: error: failed to get feature set: no devices/emulators found
unfortunately when I try to install the EMUI 8 (the one I had previously installed) from fastboot I get this error message..
Click to expand...
Click to collapse
You need to be in twrp or system to copy file from your pc to sdcard with adb.
oslo83 said:
You need to be in twrp or system to copy file from your pc to sdcard with adb.
Click to expand...
Click to collapse
The problem is just that... also flash system or twrp, I always get eRecovery, I can try to copy the files on sd from another system however (as I did previously with the dload) but erecovery stucks at 5%
Kodex_99 said:
The problem is just that... also flash system or twrp, I always get eRecovery, I can try to copy the files on sd from another system however (as I did previously with the dload) but erecovery stucks at 5%
Click to expand...
Click to collapse
Once in fastboot boot, what command did you typed to flash stock recovery ?
---------- Post added at 20:20 ---------- Previous post was at 20:20 ----------
Or twrp
oslo83 said:
Once in fastboot boot, what command did you typed to flash stock recovery ?
---------- Post added at 20:20 ---------- Previous post was at 20:20 ----------
Or twrp
Click to expand...
Click to collapse
As I had an official oreo, I used it "fastboot flash recovery_ramdisk twrp.img"
I have just discovered that I can not even wipe from the recovery stock :/
Good, maybe you're doing the key combination wrong:
https://4pda.ru/forum/index.ph...72246&st=800#entry55689846
---------- Post added at 20:27 ---------- Previous post was at 20:26 ----------
So you manage to boot to stock recovery or was it erecovery again ?
oslo83 said:
Good, maybe you're doing the key combination wrong:
https://4pda.ru/forum/index.ph...72246&st=800#entry55689846
Click to expand...
Click to collapse
404
oslo83 said:
So you manage to boot to stock recovery or was it erecovery again ?
Click to expand...
Click to collapse
I have Stock recovery with + button, eRecovery with normal system boot and Fastboot with - button
So, boot to fastboot and flash oreo twrp.
Then boot to twrp recovery like you would have done for booting to stock recovery.
---------- Post added at 20:37 ---------- Previous post was at 20:31 ----------
https://4pda.ru/forum/index.php?showtopic=772246&st=800#entry55689846
oslo83 said:
So, boot to fastboot and flash oreo twrp.
Click to expand...
Click to collapse
I flash it, but when I try to start it I always go back to the recovery stock...
Previously I had installed the twrp but I do not know why the stock returned after several wipes
Do again:
fastboot devices
Then
fastboot flash recovery_ramdisk twrp.img
Then
fastboot reboot recovery
Paste us your output.
What twrp do you used ? 0.2 or 0.3 ?
oslo83 said:
Do again:
fastboot devices
Then
fastboot flash recovery_ramdisk twrp.img
Then
fastboot reboot recovery
Paste us your output.
Click to expand...
Click to collapse
" PS C:\Users\Kodex\Downloads> fastboot devices
7BK0217B04002898 fastboot
PS C:\Users\Kodex\Downloads> fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (27144 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.289s]
finished. total time: 0.979s "
unrecognized reboot command.
oslo83 said:
What twrp do you used ? 0.2 or 0.3 ?
Click to expand...
Click to collapse
Up to a few hours ago the 0.2, now the 0.3 but does not change anything...
Keep trying to boot to twrp recovery
---------- Post added at 21:03 ---------- Previous post was at 21:02 ----------
Usb must be unpgugged
oslo83 said:
Keep trying to boot to twrp recovery
Click to expand...
Click to collapse
nothing.. only stock recovery
oslo83 said:
Usb must be unpgugged
Click to expand...
Click to collapse
i tried this
PS C:\Users\Kodex\Downloads> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.696s
Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
sentavn said:
you should format by using fastboot. First download your stock ROM and extract with Huawei Firmware Extracter. Select UPDATE.APP and extract following files:
erecovery_kernel.img
erecovery_ramdisk.img
erecovery_vbmeta.img
cust.img
erecovery_vendor.img
kernel.img
ramdisk.img
recovery_vbmeta.img
recovery_vendor.img
system.img
Reboot your device in to fastboot mode (recovery mode) and flash those files one by one:
fastboot flash erecovery_kernel erecovery_kernel.img
...
fastboot flash system system.img
//
Erase your userdata space:
fastboot -w
//reboot
fastboot reboot
Now go to your stock recovery and do factory reset, wide cache.
Now your device back to stock OREO
Click to expand...
Click to collapse
Any Ideas?
HOW I FIXED:
I downloaded this EMUI 5 Nougat, Thanks to bozka1:
https://androidhost.ru/5SZ
I extracted UPDATE.APP file using Huawei Update Extractor.
I was trying to flash everything via fastboot: BOOT.img, RECOVERY.img, RECOVERY2.img, CUST.img, SYSTEM.img but nothing helped me.
I found out what you can flash via fastboot here:
https://forum.xda-developers.com/general/general/huawei-fastboot-commands-t3850123
There was no hope for me, so I tried to flash USERDATA.img
fastboot flash userdata USERDATA.img
Click to expand...
Click to collapse
And then cmd promped something unusual:
target reported max download size of 471859200 bytes
sending 'userdata' (24576 KB)...
OKAY [ 0.646s]
writing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.401s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then I proceeded to flash: BOOT.img, RECOVERY.img, RECOVERY2.img and CACHE.img
I didn't flash SYSTEM.img because I flashed it before like 1500 times.
My phone didn't work yet so I used the DLOAD method because RECOVERY finally worked, so I shut down the device and used three buttons combo:
First holding Volume Up, Volume Down and then pressing Power Button.
There is a documentation in the firmware I downloaded, SDcard must be in exFAT format.
Thank You bozka1.
voltzero2 said:
Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
Any Ideas?
Click to expand...
Click to collapse
What is your original location, C461?
Which oeminfo you have flashed?
bozka1 said:
What is your original location, C461?
Which oeminfo you have flashed?
Click to expand...
Click to collapse
My original location is C432, I don't remember flashing any oeminfo
voltzero2 said:
My original location is C432, I don't remember flashing any oeminfo
Click to expand...
Click to collapse
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
bozka1 said:
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
Click to expand...
Click to collapse
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
voltzero2 said:
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
Click to expand...
Click to collapse
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
bozka1 said:
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
Click to expand...
Click to collapse
It says its unlucked:
https://imgur.com/a/LEDKWFr
I hope this link works
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
So I'll have to wait a little before I'll download Service ROM, my internet connection isn't the greatest, but I flashed Your TWRP and unfortunately it doesn't work;
If I hold the Power button and Volume Up - the same story as before, I see the loading TWRP screen and nothing happends,
If I let the device to boot up and then press only the Volume Up button - it says "Your device is booting up" and nothing happens.
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
EDIT:
I did some testing and Your TWRP doesn't boot at all on my device, I flashed another one, Catuva21 3.1.1 Nougat, and that is the one that I had before - it is booting but never loads.
voltzero2 said:
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
Click to expand...
Click to collapse
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
bozka1 said:
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
Click to expand...
Click to collapse
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
voltzero2 said:
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
Click to expand...
Click to collapse
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
bozka1 said:
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
Click to expand...
Click to collapse
Yeah, I've done it already, unfortunately nothing changed. How about BOOT.img? Can this influence something?
EDIT:
I also wonder about just following the steps in my first post, I've got UPDATE.APP for Oreo, but I don't know if it will only make it worse.
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
Do I have to install oeminfo to be able to use the "three buttons combo"? Because I tried it today and it doesn't work, phone is just stuck at "Your device is booting.." screen, guess I'm out of luck
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
voltzero2 said:
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
Click to expand...
Click to collapse
You're welcome
Hi help me
Bozka1
My huawei mate 10 lite is brick stock on erecovery what can i do now
Lj08 said:
My huawei mate 10 lite is brick stock on erecovery what can i do now
Click to expand...
Click to collapse
Hi, have you tried to do something with your phone? Can you provide some info?
voltzero2 said:
Hi, have you tried to do something with your phone? Can you provide some info?
Click to expand...
Click to collapse
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Lj08 said:
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Click to expand...
Click to collapse
Alright, so did it just happened randomly or did you tried to do something with your phone? Did you unlocked bootloader or flashed custom recovery etc? You need to explain what happened, that's quite important if you want someone to help you.