Related
Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.
Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.
Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking
toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.
You don't need adb.
sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
kyle_2103 said:
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
Click to expand...
Click to collapse
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
ChaseRxx said:
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
Click to expand...
Click to collapse
I think there is not solution for this problem. We have to wait. (I have the same problem but in Al00 running Al19 rom)
How do you check for FRP lock on a Huawei phone just curious.
ChaseRxx said:
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
Click to expand...
Click to collapse
Okay to unlock the bootloader, go into fastboot and plug in the USB to your computer, then by either using SRK tool or adb you need to flash this command: fastboot oem unlock (insert bootloader code) *don't put brackets* if you are unaware of your bootloader code then I cannot help you, however if you do know it, then once you unlocked the bootloader flash system.img and stuff to see if that works for you
kyle_2103 said:
Okay to unlock the bootloader, go into fastboot and plug in the USB to your computer, then by either using SRK tool or adb you need to flash this command: fastboot oem unlock (insert bootloader code) *don't put brackets* if you are unaware of your bootloader code then I cannot help you, however if you do know it, then once you unlocked the bootloader flash system.img and stuff to see if that works for you
Click to expand...
Click to collapse
Already tried this, I have the unlocking password but can't unlock BL through fastboot oem unlock (code) because the OEM Unlock is disabled.
ChaseRxx said:
Already tried this, I have the unlocking password but can't unlock BL through fastboot oem unlock (code) because the OEM Unlock is disabled.
Click to expand...
Click to collapse
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
kyle_2103 said:
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
Click to expand...
Click to collapse
I've tried some command in fastboot mode but there's always an error: Remote: command not allowed.
I can't do anything with fastboot mode
1. Try to force update with Power Button + Min Vol Button + Max Vol Button, liked you said this isn't working try to do the button combination with the phone connect it to the PC; in my case some times dload din't works after I connected the phone to the computer.
2. Other thing, something happend if you turn of the phone and leave Max Vol Button pressed, you should be entering to eRecovery.
3. Remember that sometimes enter in eRecovery mode requires to the phone be turn off otherwise you can't access to Recovery. So if this is the case follow bullet #2 and them #1.
PD: OFC I'm assuming you already have the dload folder with an compatible version of stock ROM on your SDCARD. If you don't have any version tries this one: https://forum.xda-developers.com/p9...dload-file-p9-eva-l09-b136-t3382818?nocache=1
Hope I helped you, I already bricked twice my P9 corrupting System Table Partitions.
Jeremy Molina.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
kyle_2103 said:
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
Click to expand...
Click to collapse
If you did the change of Unlock OEM before the bricked in an previous authorized computer you will still have rights for, otherwise new Android Security features is going to rejected the request.
Exacly
Dload/ no network
ChaseRxx said:
Exacly
Click to expand...
Click to collapse
Hi guys! Im new sorry if posted in wrong place/topic, I did dload method as here https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 to debrand my L09 Vodafone to stock software and now I end up in EVA-C900B136 and my sim card/network is not working anymmore I had download the software package is in the above post and did force flash.
Many thanks for help!!!
kyle_2103 said:
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
Click to expand...
Click to collapse
How did you unlock the bootloader through adb ? I'm in the same position as you put I have a P9lite.
dondrog said:
How did you unlock the bootloader through adb ? I'm in the same position as you put I have a P9lite.
Click to expand...
Click to collapse
fastboot oem unlock (followed by bootloader code)
kyle_2103 said:
fastboot oem unlock (followed by bootloader code)
Click to expand...
Click to collapse
Hello gays i install nougat 7
install with TWRP after install my phone is no keybord no all problems and i can`t active oem waht i do all command
remote not allowed coomand and i try to install all veriosn but still problem please help me
i install
EVA-L19C432B322-update
and my phone 6369C-EVA L19
my mistake please help me
i try to swoftware sim but swoftware failed
--
incompatibility with current version please download the correct update package
i upload vedio on youtube see please https://www.youtube.com/watch?v=V2yH...ature=youtu.be
sry for my bad engilsh
Any help would be greatly appreciated
I have a P9 L09, i have unlocked the bootloader, flashed TWRP recovery, and started flashing some roms. I have succesfully flashed a cyanogenmod, and it booted properly, but when it started it asked me for a password which i did not know, so i google searched and found out that it is a common issue and i need to wipe data from recovery. I tryed that but it did not work it says failed, and nothing works in the wipe advanced section, beside system. And also in the custom recovery it says that the internal storage has 0MB ! I was able to put other custom roms on the SDcard and flash them, they booted but every single one asks for the password.. I then tryed to install stock rom with the dload method, but it crashes and 40% , and i tryied the System Recovery option in HiSuite and it says it is not compatible with my device. Any help would be greatly appreciated! Thank you!
kyle_2103 said:
fastboot oem unlock (followed by bootloader code)
Click to expand...
Click to collapse
Hello. I have the same problem. I have my unlock code but in fastboot, adb command says it failed. Sorry for bad english. What can i do?
FAILED: REMOTE COMMAND NOT ALLOWED FINISHED.
Same problem on my honor &x locked bootloader and bricked. unlocking the oem like you said above does not work
Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!
Hi !
I bought in January the nice P8 Lite 2017 and received a PRA-LX1C432 (dual sim europe no carrier).
It was with Android 7.0 and EMUI 5.0 and i wanted to root it.
I did it well, and was with the firmware PRA-LXA1C432B182 in stock and rooted with the tuto from this thread
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
and uninstalled TWRP to put back stock recovery.
Later, I wanted to unroot my phone, and that's where things went wrong. I tried to do it with the superSU option and after a hard reset it was working and not rooted, but i'd still have the message "this phone can't be trust" so i tried to relock the bootloader and it did hard reset the phone again and now, i'm stuck with a phone that can send sms or go through the internet with LTE, but can't access fm, camera, google music, nfc is going on and off, calls don't work, etc... In dev options, Allow OEM unlock is greyed and I can't change anything. Phone is recognized by computer and I can acces memory of the phone.
I can hard reset it won't change, i ca also accessFastboot, or recovery or eRecovery, but in Fastboot mode it says "PHONE Unlock FRP Lock" and from my computer i can't do anything : if i try to flash twrp with fastboot command, i have the message "FAILED remote the command is not allowed", if i try to lock/unlock/relock bootloader it says "FAILED remote root type is risk".
Clearly, I don't know what to do. I'm used with rooting/unrooting smartphones from different brands (Samsung, LG, Sony, Huawei...), even though i'm far from being a master, and using Fastboot/ADB commands, but... I don't know.
If someone has any idea, I'm taking. I'm thinking about dload method but, of cooourse, I do NOT have a sdcard, so it's the last thing i would have tried from all i have seen on xda and elsewhere.
Thanks for reading and taking time to answer and help me, and sorry for not perfect english, i'm french but trying my best !
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Fr0nK said:
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Click to expand...
Click to collapse
I can't, it says that it can not get package infos from server. :/
MrCrumble34 said:
I can't, it says that it can not get package infos from server. :/
Click to expand...
Click to collapse
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Fr0nK said:
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Click to expand...
Click to collapse
TWRP is not installed, and I can't flash it in any way. Fastboot says "FAILED (remote : command not allowed)" if I try flashing recovery or system or anything. It also says "FAILED (remote : root type is risk) if I try to lock/unlock/relock the bootloader.
Ok, I'm actually trying something. I plugged the phone into my computer, and HiSuite told there was an update available for my phone, so I just clicked on it. It's doing right now, I will edit my post after it has finished (for good or bad).
EDIT : Ok, si it did work ! My phone is now on PRA-LX1C432B194, everything is working, not rooted. I relocked the bootloader with Fastboot, the command did work (guess I can root it again if I need now). But I think I'll leave it like that ^^'
Allow OEM unlock isn't greyed anymore, I came back to the original state of my phone but with an update not (yet) available in my country, no more "Device can't be trusted" message. Like if nothing had ever happened (expect it will be written PHONE Relocked).
This phone is really sensitive, haha^^
But as anyway I made it
Thanks anyway for trying to help !
HI All,
My CLT-L09 (UK Model with 128GB of Memory and 6GB of Ram) is in a bootloop after I screwed up. I've got access to Fastboot and eRecovery, but eRecovery is refusing to download a fresh image. It always complains of a server error, even though I can see a good connection going out to Huawei in my firewall logs. The two are talking to each other. I suspect Huawei doesn't like my phone!
Anyone have a copy of the STANDARD recovery ramdisk they could share? I've tried the CLT-L29 standard ramdisk, the "recovery_ramdisk_nocheckP20.img", the "recovery_ramdisk_BKL-L04_nocheck.img" and none of them coax eRecovery into downloading a fresh image and fixing my phone.
Any ideas?
Cheers,
Mich
mictho100 said:
HI All,
My CLT-L09 (UK Model with 128GB of Memory and 6GB of Ram) is in a bootloop after I screwed up. I've got access to Fastboot and eRecovery, but eRecovery is refusing to download a fresh image. It always complains of a server error, even though I can see a good connection going out to Huawei in my firewall logs. The two are talking to each other. I suspect Huawei doesn't like my phone!
Anyone have a copy of the STANDARD recovery ramdisk they could share? I've tried the CLT-L29 standard ramdisk, the "recovery_ramdisk_nocheckP20.img", the "recovery_ramdisk_BKL-L04_nocheck.img" and none of them coax eRecovery into downloading a fresh image and fixing my phone.
Any ideas?
Cheers,
Mich
Click to expand...
Click to collapse
eRecovery and Recovery Ramdisk are separate partitions. Flashing different recoveries won't affect how eRecovery works. Is your bootloader unlocked? How did you get into bootloop state?
danifilth4king said:
eRecovery and Recovery Ramdisk are separate partitions. Flashing different recoveries won't affect how eRecovery works. Is your bootloader unlocked? How did you get into bootloop state?
Click to expand...
Click to collapse
Thanks for your fast reply!
So, you may have figured that I am merely a follower of instructions, when it comes to flashing phones.... Unfortunately I screwed up and neglected a small but very important details when I followed this thread: https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283
My phone is the CLT-L09. But for some bizarre reason I thought I had the CLT-L29. No idea how I got that idea! I was on build 110, like a lot of unfortunate people, and I was sick and tired of not getting timely security updates. So I took matters into my own hands (which I regret now....)
I followed the above thread and managed to get my phone onto CLT-L29C432B131A. And it worked! At first I was quite happy, but then I found some issues.
I found was that the build number was showing up as "Chipset-boston 8.1.0.001(01V2)". And I was having issues with a bunch of apps not wanting to show up in Google Play for my phone, which I have had on this phone before flashing it. For example Netflix and Amazon! I knew then that I couldn't stay on this build and had to find a way back onto the legit L09 release.
I followed https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 again trying to apply a L09 release, but it didn't work. I could get proper root anymore, no matter what I tried. I also tried the HuRu updater, and that didn't make any difference. The CLT-L29C432B131A image I managed to get myself on just didn't want to budge from the phone.
In my desperation (and lack of understanding!) I started playing with different ramdisk images, trying to get eRecovery to allow me to re-image the phone.
So, long story short; I am now at the point where all I have is two things:
1 - eRecovery boots, but refuses to re-image my phone with a "Getting package info failed" error. I suppose my L29/L09 image mix is confusing the sh!t out of it!
2 - Fastboot works and allows me to flash ramdisk images
3 - TWRP 3.2.0 *was* working until this morning, but has now quit. Not sure how I broke that.
Is there any way back from this?
mictho100 said:
Thanks for your fast reply!
So, you may have figured that I am merely a follower of instructions, when it comes to flashing phones.... Unfortunately I screwed up and neglected a small but very important details when I followed this thread: https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283
My phone is the CLT-L09. But for some bizarre reason I thought I had the CLT-L29. No idea how I got that idea! I was on build 110, like a lot of unfortunate people, and I was sick and tired of not getting timely security updates. So I took matters into my own hands (which I regret now....)
I followed the above thread and managed to get my phone onto CLT-L29C432B131A. And it worked! At first I was quite happy, but then I found some issues.
I found was that the build number was showing up as "Chipset-boston 8.1.0.001(01V2)". And I was having issues with a bunch of apps not wanting to show up in Google Play for my phone, which I have had on this phone before flashing it. For example Netflix and Amazon! I knew then that I couldn't stay on this build and had to find a way back onto the legit L09 release.
I followed https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 again trying to apply a L09 release, but it didn't work. I could get proper root anymore, no matter what I tried. I also tried the HuRu updater, and that didn't make any difference. The CLT-L29C432B131A image I managed to get myself on just didn't want to budge from the phone.
In my desperation (and lack of understanding!) I started playing with different ramdisk images, trying to get eRecovery to allow me to re-image the phone.
So, long story short; I am now at the point where all I have is two things:
1 - eRecovery boots, but refuses to re-image my phone with a "Getting package info failed" error. I suppose my L29/L09 image mix is confusing the sh!t out of it!
2 - Fastboot works and allows me to flash ramdisk images
3 - TWRP 3.2.0 *was* working until this morning, but has now quit. Not sure how I broke that.
Is there any way back from this?
Click to expand...
Click to collapse
Run this command in fastboot:
fastboot oem get-product-model
This will help you figure out what model your phone thinks it is.
And this command:
fastboot getvar vendorcountry
Will help you figure out what region it's currently on. Let me know.
danifilth4king said:
Run this command in fastboot:
fastboot oem get-product-model
This will help you figure out what model your phone thinks it is.
And this command:
fastboot getvar vendorcountry
Will help you figure out what region it's currently on. Let me know.
Click to expand...
Click to collapse
Looks like it doesn't have a product model defined! I ran the command twice:
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.002s
[email protected]:~/Mich/android$
Would you recommend using the Huawei Update Extractor tool to flash the individual partitions manually, with the correct (original) image? My device is a CLT-L09C782. And was on b110. I have the update here, and I can extract the various images. But I have never done this kind of low level flashing. If you reckon it'll fix it, would you be happy to give me some quick tips?
This is the process I have found on the subject, but I am not sure whether it is correct or still up to date: https://www.theandroidsoul.com/extract-huawei-firmware-update-app/
Thanks!!!
mictho100 said:
Looks like it doesn't have a product model defined! I ran the command twice:
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.002s
[email protected]:~/Mich/android$
Would you recommend using the Huawei Update Extractor tool to flash the individual partitions manually, with the correct (original) image? My device is a CLT-L09C782. And was on b110. I have the update here, and I can extract the various images. But I have never done this kind of low level flashing. If you reckon it'll fix it, would you be happy to give me some quick tips?
This is the process I have found on the subject, but I am not sure whether it is correct or still up to date: https://www.theandroidsoul.com/extract-huawei-firmware-update-app/
Thanks!!!
Click to expand...
Click to collapse
Well it's returning 'hw/eu' so your device is still C432 but looks like oeminfo is damaged, I think.
I wouldn't try the low level flashing business - could result in a brick.
I'm on CLT-L09C432. I'll link you to a TWRP backup of my oeminfo you should be able to restore it from that then hopefully eRecovery will be able to get the right package info for you then.
Flash the unofficial TWRP from here https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
Make sure you follow the step to boot straight to recovery after flashing. Then make a backup of your oeminfo via TWRP, then adb pull the backup to your PC (instructions here: https://www.howtogeek.com/240655/how-to-copy-twrp-android-backups-to-your-pc-for-safe-keeping/ )
Now download these 2 files:
https://drive.google.com/file/d/1hv2HjIEo3bUoveceZWtH8b8uWTB5cuAJ/view?usp=drivesdk
https://drive.google.com/file/d/1EXrnTkbAdI6qaKvo6Du3LwuN6XIuayNb/view?usp=drivesdk
and replace the backup files on your PC with the downloaded ones.
Using the file manager in TWRP, delete the TWRP folder from internal memory then ADB push the backup folder from your PC back to the phone. (Instructions on howtogeek post earlier)
Use TWRP to restore the backup then reboot to fastboot and try
fastboot oem get-product-model
If it returns CLT-L09 them you're good to try eRecovery again.
Hope this helps!
Afternoon Sir!
Tried to follow the above instructions but hit a snag; I cannot boot into TWRP when the cable is plugged into the phone, so I cannot pull the files from it!
If no cable is plugged in, TWRP boots fine and everything works. But as soon as I plug the cable in, the phone reboots automagically and boots into eRecovery. F**DN£(D annoying!
I've flashed TWRP again, just in case it hadn't copied properly, but it made no difference. Had a look on the tintertubes, but couldn't find any references to anybody else experiencing this issue. In fact, my TWRP was working fine with the cable a couple of days ago. I distinctly remember being able to mount the sdcard via USB, to copy files to/from it. No idea how this broke!
So, back to the original idea of flashing the IMG files?
mictho100 said:
Afternoon Sir!
Tried to follow the above instructions but hit a snag; I cannot boot into TWRP when the cable is plugged into the phone, so I cannot pull the files from it!
If no cable is plugged in, TWRP boots fine and everything works. But as soon as I plug the cable in, the phone reboots automagically and boots into eRecovery. F**DN£(D annoying!
I've flashed TWRP again, just in case it hadn't copied properly, but it made no difference. Had a look on the tintertubes, but couldn't find any references to anybody else experiencing this issue. In fact, my TWRP was working fine with the cable a couple of days ago. I distinctly remember being able to mount the sdcard via USB, to copy files to/from it. No idea how this broke!
So, back to the original idea of flashing the IMG files?
Click to expand...
Click to collapse
That's odd. Did TWRP successfully do a backup of your oeminfo? I thought it might fail as your oeminfo seems corrupted.
Have you been able to use ADB before now? It could be a drivers issue...
Try booting to TWRP with cable unplugged, then in your command dialogue type 'adb devices' wait for the daemon to start and then plug in the cable when it says 'waiting for device's or something.
I've never heard of TWRP randomly rebooting when a cable is plugged in.
danifilth4king said:
That's odd. Did TWRP successfully do a backup of your oeminfo? I thought it might fail as your oeminfo seems corrupted.
Click to expand...
Click to collapse
Yup, TWRP has successfully backed up oeminfo. I can see the files in the TWRP file browser.
danifilth4king said:
Have you been able to use ADB before now? It could be a drivers issue...
Click to expand...
Click to collapse
Yeah, ADB works a treat. Not had any problems with it.
Try booting to TWRP with cable unplugged, then in your command dialogue type 'adb devices' wait for the daemon to start and then plug in the cable when it says 'waiting for device's or something.
I've never heard of TWRP randomly rebooting when a cable is plugged in.[/QUOTE]
Tried that, unfortunately it didn't make any difference.
This is such a weird problem. I have TWRP, and I have the oeminfo files. I just can't get stuff on or off the phone! (if it had an SD card, it would be easy, but it doesn't have one!)
Is it possible to pull files via fastboot?
OK, found the problem with the reboot when plugging in the cable! It was a dodgy USB-C cable!! OMG!
I'll run through the process on howtogeek now and will let you know what happens!
So, I'm all up and running again!! !! !!!!!! :laugh:
Replacing the oeminfo files did the trick and the phone then identified itself as CLT-L09 in Fastboot.
I then ran eRecovery and it too was happy to finally download the stock recovery and re-image the phone to CLT-L09 8.1.0.128(C432).
I really cannot thank you enough mate. Honestly. I had been fighting with this phone for over 5 days, and running in circles without getting anywhere., and you pulled me out of the quagmire!
mictho100 said:
OK, found the problem with the reboot when plugging in the cable! It was a dodgy USB-C cable!! OMG!
I'll run through the process on howtogeek now and will let you know what happens!
Click to expand...
Click to collapse
Great news, good luck!
---------- Post added at 08:24 PM ---------- Previous post was at 08:21 PM ----------
mictho100 said:
So, I'm all up and running again!! !! !!!!!! :laugh:
Replacing the oeminfo files did the trick and the phone then identified itself as CLT-L09 in Fastboot.
I then ran eRecovery and it too was happy to finally download the stock recovery and re-image the phone to CLT-L09 8.1.0.128(C432).
I really cannot thank you enough mate. Honestly. I had been fighting with this phone for over 5 days, and running in circles without getting anywhere., and you pulled me out of the quagmire!
Click to expand...
Click to collapse
So glad I could help you mate! No worries
I've been in your position with this phone before and know how frustrating it is when you can't figure out how to fix something. Cheers for the gift
---------- Post added at 08:29 PM ---------- Previous post was at 08:24 PM ----------
If you wanna root, I recommend Magisk 16.4 and latest magisk manager. I've had issues with later magisk versions.
I guess your phone got factory reset after the recovery? Bit of a bummer if so.
You can update with HuRUpdater now to build 152 if you're feeling brave. You're on C432 now too, so no more slow updates ?
Just don't forget to uninstall Magisk with the Uninstall feature in Magisk Manager before using HuRUpdater or you'll bootloop again ?