pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work
babyshark1983 said:
pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work
Click to expand...
Click to collapse
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?
zgfg said:
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?
Click to expand...
Click to collapse
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)
babyshark1983 said:
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)
Click to expand...
Click to collapse
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
zgfg said:
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official
babyshark1983 said:
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official
Click to expand...
Click to collapse
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything
zgfg said:
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything
Click to expand...
Click to collapse
hi just bootloader unlock
frp locked
thx
babyshark1983 said:
hi just bootloader unlock
frp locked
thx
Click to expand...
Click to collapse
That is the problem - to flash you need both Bootloader and FRP unlocked but with wrong TWRP or so, you locked FRP
To unlock FRP you would need to boot to System and check OEM Unlock under Developer Options - but if you ccannot boot to System, it is bricked
IMO, no other way now but to buy 15 EUR credit for DC Phoenix, they can unlock (TG, I didn't need to use DC Phoenix , hence cannot help about, you can ask them over their page)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
You can also search here on XDA, there were other users who un-bricked by their tool, if I recall there was also somebody with a similar brick: FRP locked but cannot boot to System
Related
I tried to force update to b170, resored the backup from howtoroot thread and flashed stock recovery from within twrp, rebooted and my devicve is stuck on
ERROR MODE
err no11 recovery image
errror no 2 load failed
doesnt boot to fastboot, cant be seen by pc
cant even turn it off... it is infinite loop if i hold power button it boots "huawei logo for 1 second and again error mode"
Please help me to recover my device :/
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode
aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
HI man I have the some problem error mode screen but in oreo update p8 lite 2017 any solution plz
p181153 said:
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode
Click to expand...
Click to collapse
If you solved your problem tell me plz plz plz
jalel25 said:
If you solved your problem tell me plz plz plz
Click to expand...
Click to collapse
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
I hope one of them help me ?
jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.
mijanto313 said:
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.
Click to expand...
Click to collapse
I tried that. My phone has been in this state for probably a month already. I heard the only solution is DC Phoenix via testpoint method.
Try Firmware finder for huawei + erecovery method , which is :
- download firmware finder on *another android phone* and search for exact phone model (ex : PRA-LA1C185)
- choose the very first firmware down the list
- Get an update thorugh dns >> Manually >> Register update
- After that , reboot your bricked phone into erecovery by ( power + volume*+*)
- press download recovery and last firmware
- wait till getting package
- by now should firmware start downloading
- let phone complete it's work and reboot
Hope that's work for you ?
p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots
Botar230 said:
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots
Click to expand...
Click to collapse
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !
Freysheur said:
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !
Click to expand...
Click to collapse
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot
Botar230 said:
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot
Click to expand...
Click to collapse
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !
Freysheur said:
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !
Click to expand...
Click to collapse
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs
Botar230 said:
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs
Click to expand...
Click to collapse
Why before i used the flash recovery and it worked ?
Do you have an answer to the error " FAILED (remote: partition length get error) " ?
---------- Post added at 11:25 AM ---------- Previous post was at 10:40 AM ----------
Ok, i try install ROM via TWRP..
I have no errors but i bootloop again.. and he puts me in the menu Huawei eRecovery..
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I try install ROM via Fastboot CMD.
C:\Users\Alban\Desktop\fastboots>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
C:\Users\Alban\Desktop\fastboots>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15524 KB)...
OKAY [ 0.389s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.413s
Hmmmm, i installed MorfuZ rom, he boot but he restart alone..
So I do not have a rom ...
jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Everyone, I made a guide on my website to unbrick the device.
Here is the link:
http://mrviking.simplesite.com/440246066
So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
virusdunil said:
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
Click to expand...
Click to collapse
I can have the phone in fastboot and run adb reboot bootloader and it says no devices found although the huawei HiSuite can detect the device being plugged in as it loads up when I plug the phone in
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
virusdunil said:
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
Click to expand...
Click to collapse
Not going to lie I am slightly out of my depth here, could you explain that further? I'm assuming I need to download an update.app but I have no idea where from or extracting the kernel from it
thanks
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
virusdunil said:
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
Click to expand...
Click to collapse
That Didn't work i just got:
C:\Users\jamie\Desktop\platform-tools>fastboot flash recovery KERNEL.img
target reported max download size of 471859200 bytes
sending 'recovery' (24576 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.537s
im assuming its due to the bootloader not being unlocked. and in the meantime im running a deepscan on my hard drive to see if I can recover my unlock code which was lost when cloning to a new ssd. It has a few hour left though
you have it wrong...
its fastboot flash kernel KERNEL.img
virusdunil said:
you have it wrong...
its fastboot flash kernel KERNEL.img
Click to expand...
Click to collapse
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
virusdunil said:
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
Click to expand...
Click to collapse
I have android studio, how do I flash the img with it?
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
virusdunil said:
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
Click to expand...
Click to collapse
exactly the same :
C:\Users\jamie\AppData\Local\Android\Sdk\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.533s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.542s
Is it maybe worth seeing if I can get the serial number product emei and product id without the os?
Jyndon said:
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
Click to expand...
Click to collapse
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
kwaichang said:
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
Click to expand...
Click to collapse
I don't know that I do have access though as the device doesn't appear in adb devices list and the bootlaoder is locked.
Although I think I may have found a way of flashing a new bios without bootloader by using the huawei recovery installation.
The default one that uses wifi obviously doent work because its crap but while the device is off I can hold vol+ vol- and power and it loads into an installation screen that shows installation failed but i found that it maybe possible to flash the bios this way by putting the update.app onto the sd card. However the problem I'm having is that windows says the file is too big to copy and unzipping it inside of the sd card doesnt work either. Any ideas as to how I might be able to do it like this? (similar to this: https://android.stackexchange.com/q...are-installation-failed-error-when-booting-up and this too https://forum.xda-developers.com/p9-plus/help/software-install-failed-updating-p9-t3587676)
SOLVED
I managed to get most of the information to unlock the bootloader from the box which I luckily kept, then for the product ID I used https://imei24.com/warranty_info/Huawei/865545034273084/ and it worked perfectly!
Bootloader unlocked and then I used the common HWOTA to rebrand it back to its original firmware.
Thanks to those who helped.
Jyndon said:
So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Click to expand...
Click to collapse
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
I know this is late but none the less, using the emei code I was able to request my code to unlock the bootloader through hwota. You cannot request this code anymore a way so you have to pay for dc unlocker which can rip the unlock code from the device.
petr.hybler said:
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
Click to expand...
Click to collapse
Is your bootloader unlocked?
If not you have your bootloader unlock code?
If not then you will need to pay for some software to get that code.
From there you can unlock the bootloader and use adb/fastboot again
Hi there! So, I unlocked my bootloader yesterday and I've been trying to install a custom rom, no luck at all, it doesn't boot. It just stays in a bootloop. I think that's because I wiped the system and data instead of just wiping data then performing a factory reset, how it told me in the installation guide. Now, I have a european EVA-L09 with a unlocked bootloader and TWRP installed. What can i do to get it boot up? Thanks in advance
Try with HWOTA by installing the same stock ROM you had before messing up
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Btw, Huawei portal for Bootloader codes was down for days - was it up now again or you paid for DC Unlocker
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
zgfg said:
Try with HWOTA by installing the same stock ROM you had before messing up
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Btw, Huawei portal for Bootloader codes was down for days - was it up now again or you paid for DC Unlocker
Click to expand...
Click to collapse
I paid for DC Unlocker. I'll try it out. Ummm, I bought mine from UK, what version should I get? I had the latest EMUI 5.0.1 (Naugat 7.0) Stock ROM. It was my mistake that I didn't backed it up, had no storage left on my SD Card... Stupid me
fler_tb said:
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
Click to expand...
Click to collapse
Hi there! I'll try it out!
fler_tb said:
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
Click to expand...
Click to collapse
Code:
C:\Users\Whiskey\Desktop>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (449861 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 20.379s
well, this is what happens...
BlazedMC said:
Code:
C:\Users\Whiskey\Desktop>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (449861 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 20.379s
well, this is what happens...
Click to expand...
Click to collapse
Sorry for late answer. Maybe your bootloader is locked so you can't direct flash it trough fastboot...?!
fler_tb said:
Sorry for late answer. Maybe your bootloader is locked so you can't direct flash it trough fastboot...?!
Click to expand...
Click to collapse
I solved it a long time ago, the same day. Thanks anyway!
BlazedMC said:
I solved it a long time ago, the same day. Thanks anyway!
Click to expand...
Click to collapse
How did you??
So what happend is i wanted to get oreo on my pra la1 so i re branded it to al00c chinese version (after unlocking my bootloader)
using the al00c oem file , i flash d it in twrp and then i wanted google play services which is not there in chinese version so i unlocked bootloader again and flashed oreo twrp and then flashed pra lx1 oem info and i did not dload the lx1 software:crying: so stupid of me now i m running chinese software on lx1 and without google play now my frp and bootloader is locked. now when i try dload it goes to 5% and says system update failed . WHAT DO I DO NOW TO GET PRA LX1C432 OREO??
THANX IN ADVANCE
Try Firmware finder for huawei + erecovery method , which is :
- download firmware finder on *another android phone* and search for exact phone model (ex : PRA-LA1C185)
- choose the very first firmware down the list
- Get an update thorugh dns >> Manually >> Register update
- After that , reboot your bricked phone into erecovery by ( power + volume*+*)
- press download recovery and last firmware
- wait till getting package
- by now should firmware start downloading
- let phone complete it's work and reboot
Hope that's work for you ?
I have the bootloader unlocked via DC Unlocker. Must pay 3,99€ because it's okay.
NOW: I want flash twrp via adb-fastboot and it comes
FAILED (remote: partition length get error)
EgonsS said:
I have the bootloader unlocked via DC Unlocker. Must pay 3,99€ because it's okay.
NOW: I want flash twrp via adb-fastboot and it comes
FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)
I don't understand why there isn't any one who can develop something that can push the img files with fastboot without restriction like it's done by dc phoenix
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
victoriordachi said:
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)
Click to expand...
Click to collapse
this is what this pra-la1 fastboot reply
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.894s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.905s
RAR1991 said:
I don't understand why there isn't any one who can develop something that can push the img files with fastboot without restriction like it's done by dc phoenix
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
this is what this pra-la1 fastboot reply
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.894s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.905s
Click to expand...
Click to collapse
Try this recovery https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 . 0.2 test build . Install using the same command
victoriordachi said:
Try this recovery https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 . 0.2 test build . Install using the same command
Click to expand...
Click to collapse
thanks for the interest but like always.
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.937s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.953s
victoriordachi said:
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)
Click to expand...
Click to collapse
FAILED (remote: partition error)
So I was digging on my phone and I was able to put it in recovery mode it shows USB logo with 5 % and adb devices command give that result
E:\>adb devices
List of devices attached
PSEDU17315000315 recoveryif anyone can get something from that
Hassan__12 said:
So what happend is i wanted to get oreo on my pra la1 so i re branded it to al00c chinese version (after unlocking my bootloader)
using the al00c oem file , i flash d it in twrp and then i wanted google play services which is not there in chinese version so i unlocked bootloader again and flashed oreo twrp and then flashed pra lx1 oem info and i did not dload the lx1 software:crying: so stupid of me now i m running chinese software on lx1 and without google play now my frp and bootloader is locked. now when i try dload it goes to 5% and says system update failed . WHAT DO I DO NOW TO GET PRA LX1C432 OREO??
THANX IN ADVANCE
Click to expand...
Click to collapse
Try this:
fastboot flash recovery xxx(name of recovery).IMG.
It's the old nougat command. Might work. Depends on what partition scheme your device has. Give it a shot. Likely won't but you can try.
Got same issue yesterday. After some i got a length partition issue.
I did the full OTA from eRecovery. Now i'm on PRA-LX1 8.0.0.368 C02 (NOT C432).
I should try again (i believe my device is now totally stable - i think i flashed bad rom with HuRUpdater...) and see if i can flash a TWRP (certainly 3.2.1 Oreo) with fastboot flash recovery_ramdisk twrpfile.img
Will let you know.
hello colleagues need your help huawei PRA-LA1 on the screen only huavei write how the bootloader will unlock me
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
EDIT: Now fixed. In case anyone has a similar issue, I flashed in fastboot the stock recovery_ramdisk found in the UPDATE.APP I extracted with the Huawei update extractor, then ran fastboot -w to erase userdata and it booted successfully.
MrDanMak said:
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
Click to expand...
Click to collapse
Have you tried eRecovery?
danifilth4king said:
Have you tried eRecovery?
Click to expand...
Click to collapse
Yeah same issue with 'your device is booting now...'
MrDanMak said:
Yeah same issue with 'your device is booting now...'
Click to expand...
Click to collapse
Hmm that's not good. Maybe you've wiped/flashed over the eRecovery partition (I think it's recovery2, not recovery_ramdisk) try downloading the latest update.zip from firmware finder that matches your model number and unzip, then use Huawei update extractor to extract recovery2.img from UPDATE.APP and try flashing it through fastboot
fastboot flash recovery2 *filename*.img
Then reboot to eRecovery and see if you can recover?
This is just a guess based on what you've told me and may not work. Attempt at your own risk ?
---------- Post added at 06:24 PM ---------- Previous post was at 06:03 PM ----------
MrDanMak said:
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
EDIT: Now fixed. In case anyone has a similar issue, I flashed in fastboot the stock recovery_ramdisk found in the UPDATE.APP I extracted with the Huawei update extractor, then ran fastboot -w to erase userdata and it booted successfully.
Click to expand...
Click to collapse
Just seen your edit. Glad you got it fixed!
I have you found a solution i have the same issue?
It's the factory reset with twrp to provoque the issue...
I was able the get the same problem. I am just able to get into fastboot mode... Now I am unable to find out which files for emui 8 erecovery are needed -.- If I try to flash erecovery_ramdis.img to recovery2 just get a error which tells me partition length error.
I am mad now xD
Fixed it with just flashing every sinlge .img which I extracted out of the updater.app xD Some errors while flashing occured but it worked xD
Kaffee4Eck said:
Fixed it with just flashing every sinlge .img which I extracted out of the updater.app xD Some errors while flashing occured but it worked xD
Click to expand...
Click to collapse
***
how did you that? im trying but every single img sais something like this
fastboot.exe flash fastboot FASTBOOT.img
Sending 'fastboot' (3351 KB) OKAY [ 0.234s]
Writing 'fastboot' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.344s
Luis2k33-XDA said:
***
how did you that? im trying but every single img sais something like this
fastboot.exe flash fastboot FASTBOOT.img
Sending 'fastboot' (3351 KB) OKAY [ 0.234s]
Writing 'fastboot' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.344s
Click to expand...
Click to collapse
There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Yes but you said you flashed all the img files from the update.app, is near of 20 or 30, i only can flash, cust.img, kernel.img, recovery ramdisk and system.img but do nothing, still not booting
Kaffee4Eck said:
There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Click to expand...
Click to collapse
---------- Post added at 11:40 AM ---------- Previous post was at 11:05 AM ----------
I mean what all imgs you had flashed? i flashed cust.img kernel.img recovery_ramdis.img and system.img but didnt boot :/
QUOTE=Kaffee4Eck;78461118]There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img[/QUOTE]
download firmware
Where do iget the firmware from?
The downloads
Kaffee4Eck said:
There is no fastboot.img to be flashed.
from firmware finder dont finish downloadin or are corrupted.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Click to expand...
Click to collapse