Related
I am quite new to the android rooting & custom recovery and having a problem with my Huawei P8 GRA-UL00 flashing (purchased from China), when I try the procedure with MAC OS X. My step by step actions and result was as follows:
1. I installed "SDK Tools Only" for Mac. Connected the device via USB, launched terminal and successfully see the device with the "adb devices" command.
2. Vol +, Vol- and Power didn't work to enter to the fastboot&rescure mode. However, Vol- and Power worked. (Also, Vol+ and Power enters to the Huawei eRecovery mode, which shows EMUI logo, Reboot, Download new version and recovery and Shutdown buttons. I guess this is stock recovery???)
3. In the fastboot mode, I have successfully seen the device with "fastboot devices". Then I unlocked the bootloader with the code. The first problem was here, there were no auto-reboots and I entered "fastboot reboot" command, and stuck in seeing "reboooting..." in terminal. Nothing happened after this command. After 10 minutes I manually rebooted the phone by pressing power and entered into the fastboot mode. I was written as "Phone Unlocked". (Do u think it was really successful?)
4. I tried to flash the TWRP file which was uploaded by @jniklast (openrecovery-twrp-2.8.7.0-p8-ul10-r4.img). The result was like that:
MacBook-Airlatform-tools go$ ./fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img
target reported max download size of 471859200 bytes
sending 'recovery' (25566 KB)...
OKAY [ 0.703s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 1.056s
MacBook-Airlatform-tools go$
5. Tried fastboot reboot, but I wasn't successful:
MacBook-Airlatform-tools go$ ./fastboot reboot-bootloader
rebooting into bootloader...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.121s
MacBook-Airlatform-tools go$
I am not sure if I have correctly defined my problem. I guess I wasn't successful to install TWRP even it says so. What should I do after finishing the flash recovery command?
Can anyone help me with this error?
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
samusalo said:
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
Click to expand...
Click to collapse
Thank you samusalo.. Then I understand that TWRP for GRA-L09 can work on a GRA-UL00. I will try.
jniklast said:
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
Click to expand...
Click to collapse
I don't use adb reboot, I manually press Vol - and Power. Then, the Fastboot & Rescue mode opens, and I enter to the terminal "fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img". It quickly shows that the installation is successful. Then I enter fastboot reboot-bootloader (I guess this is required to launch TWRP) but it shows that usb read error.
@jniklast and @samusalo thank you for your explanations. They both worked.
I flashed the GRA-L09 version of the TWRP to my GRA-UL00 and it worked! Now I have a backup...
I also realized that I am doing something wrong.. After installing TWRP, I was trying to fastbot reboot-boatloader in order to get TWRP launched automatically. However, the only thing I need to do is to follow jniklast's instructions and after the phone shut down, press Vol+ Vol- and Power together to get the TWRP launch.
Now I will try to flash an official International ROM, instead of my Chinese ROM.
Is the following command correct for this?
fastboot flash system "HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version).zip"
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
jniklast said:
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
Click to expand...
Click to collapse
Many .img files exists in the update.app file. I guess I need to flash only the system.img?
If I flash the recovery.img or boot.img inside the update.app, will I lose the custom recovery and my backup?
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Partially Successful
jniklast said:
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
Flashing boot and system was successful! Then, again, my "fastboot reboot-bootloader" didn't work and retured me my initial error. But I rebooted manually and successfully launched my phone OS.
I now have a slow-operating new Android firmware, which is a little weird )) I think it is now a international&chinese hybrid version. Some apps disappeared and I have a complete new page for google services and apps. However, my chinese stuff (baidu spotlight search, notifications, etc.) remains The EMUI Build is: GRA-UL00V100R001C00B120, which should be V100R001C900B141 as I have flashed the img files of this update.
I tried "fastboot erase userdata", "fastboot erase cache" and "fastboot erase system" but they both returned with "FAILED (remote: Command not allowed)".
The following were my successful fastboot flash commands:
MacBook-Airlatform-tools go$ ./fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23256 KB)...
OKAY [ 0.653s]
writing 'boot'...
OKAY [ 0.569s]
finished. total time: 1.222s
MacBook-Airlatform-tools go$ sudo ./fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459646 KB)...
OKAY [ 20.184s]
writing 'system'...
OKAY [ 6.149s]
sending sparse 'system' (450260 KB)...
OKAY [ 22.868s]
writing 'system'...
OKAY [ 6.051s]
sending sparse 'system' (437337 KB)...
OKAY [ 18.146s]
writing 'system'...
OKAY [ 5.952s]
sending sparse 'system' (460637 KB)...
OKAY [ 19.570s]
writing 'system'...
OKAY [ 6.267s]
sending sparse 'system' (448019 KB)...
OKAY [ 18.582s]
writing 'system'...
OKAY [ 5.982s]
sending sparse 'system' (165186 KB)...
OKAY [ 6.853s]
writing 'system'...
OKAY [ 2.206s]
finished. total time: 138.824s
MacBook-Airlatform-tools go$
jniklast said:
it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
I was finally successful to flash cust.img with fastboot and now I have B141 and all Chinese apps are removed. All Chinese ROM specific apps are disappeared and the only remaining Chinese stuff is the text in the Magazine Unlock, accessible when swiped up from the bottom of the screen at the lock screen.
The remaining problem for now is; when I press the Dialer, Contacts and Messages apps at the bottom, they crash.
Do I need to flash any other from the following extracted img files?
3RDMODEM.img
CACHE.img
CRC.img
CURVER.img
DTIMAGE.img
EFI.img
FASTBOOT.img
HIFI.img
MCUIMAGE.img
MODEM.img
MODEM_DSP.img
MODEMNVM_UPDATE.img
RECOVERY.img
RECOVERY2.img
SENSORHUB.img
SHA256RSA.img
TEEOS.img
TRUSTFIRMWARE.img
USERDATA.img
VERLIST.img
XLOADER.img
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
jniklast said:
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
Click to expand...
Click to collapse
Hello again,
Actually the hardware is the same, it is GRA-UL00. The device originally had: GRA-UL00-UL10_EMUI3.1_Android5.0_C00B173
I tried to fastboot the following ROM:
HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version)
I was successful to flash Root, CUST and System but when I try to flash any Modem-related img files (Modem.img, 3RDMODEM.img, MODEM_DSP.img, MODEMNVM_UPDATE.img), I get the following error:
sending 'modem' (38865 KB)...
OKAY [ 1.038s]
writing 'modem'...
FAILED (remote: Command not allowed)
finished. total time: 1.039s
I didn't try to install APKs.
I am still having crash problems with the dialer, contacts, messages, google play, and some other google services.
Network Mode FREEZE AUTO
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Finally Done!
meetkhems said:
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Click to expand...
Click to collapse
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
landros57 said:
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
Click to expand...
Click to collapse
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.[/QUOTE]
meetkhems said:
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.
Click to expand...
Click to collapse
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Any Update on this anyone? I am unable to use the phone as it drains a lot of battery on 3G and i cant change it to 2G as due to Blank Mobile Network Settings.
Guys I have one problem I want to flash stock recovery for P8 L09 but in cmd it fails like not allowed command anybody knows why ?
landros57 said:
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Click to expand...
Click to collapse
Hi landro57 have you tried to flash the update.app file of 18 Kb from local update? Some owners of the P8 gra ul09 variant are using that file to debrand their P8s. The mobile networks problem you ae experiencing is the same some other people have turnaround with that trick. You should check with it and report back to us, because if that goes ok, it means no more china firmware on our P8 gra ul00, we can simply flash the international general P8 firmware V100R001C900B141.
Inviato dal mio SGP311 utilizzando Tapatalk
GryphonA said:
flash the update.app file of 18 Kb from local update
Click to expand...
Click to collapse
Hi GryphonA, I don't get it, which 18kb update.app file do you mean?
I got the same problem (no access to mobile networks settings) and I can't remember if I never had that access or it happened due to my rooting/cusomizing activities.
I have GRA-UL00C433B180. I flashed also C470B180 but that didn't solve the problem.
BTW: There are a lot of mobile network setting apps and widgets in the Play Store but all apps I tested show the same failure as the mobile network settings: There seems to be a network reset and nothing more.
I originally did a boot unlock, a fash of twrp-2.8.7.2-angler.img, and when I could not get the pattern on twrp recovery to function, I did a sideload of the twrp.img instead of an install.
This failed in a boot loop.
SO I did a flash back to stock with angler-mdb08m-factory-dbc17940.tgz (after unpacking this).
Then I restored all my apk, etc.
BUT now when I do:
fastboot flash recovery twrp-2.8.7.2-angler.img, I SEE:
target reported max download size of 494927872 bytes
sending 'recovery' (16880 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.247s]
finished. total time: 0.809s
---- all looks fine, but the device itself does not seem to react and when I reboot, and select recovery, it just goes into Google recovery.
Has anyone else seen this, and do you know how to get past this?
I already tried to unlock again and it tells me error, already unlocked.
So my next step would be to do a lock and then an unlock again, but that would probably cause me to take several hours restoring after another flash to stock, and I fear that I will be back where I am now??? any thoughts??
SOLVED!
It seems that somehow, I just hadn't waited long enough. I was able to now reboot into recovery.
Thanks to any that looked at this issue.
Hi all,
Interesting problem. I've been updating some P8 Lite units that were shipped to us with a single SIM ROM with dual SIM ROM. I've already done two phones without issues (both ALE-L21). Onto the third phone (also ALE-L21), and this time there's a problem.
I'm not quite clear if the HiSilicon Kirin 620 and HI6210SFT are the same chipset or not. An answer to this would be helpful!
Steps taken:
Unlocked bootloader via Huawei website. Fastboot says PHONE Unlocked and fastboot oem get-bootinfo replies: (bootloader) unlocked
Flashed boot, recovery, cust, and system.img via fastboot following the guide (using dual SIM unbrick files)
Phone does not boot past Huawei logo, I get a black screen and then after a minute or so it reboots
Pretty odd, since I've done this on two other phones of the same model and the process worked without any issues.
TWRP 2.8.7 does not boot on the phone (black screen and reboot to Huawei logo)
TWRP 3.0.2 does boot.
Unfortunately I didn't think to take a backup of the system before I started this since I'd done it twice before without problems.
Here's what I've tried to do to get this phone to boot again:
Took TWRP backup of another ALE-L21 running B584 and restore it. Result: bootloop/not booting past Huawei logo
Flashed B052 via fastboot from here. Result: bootloop/not booting past Huawei logo
Flash recovery.img from the guide (not sure which OS version this is based on) and put UPDATE.APP for B052 on sdcard\dload\UPDATE.app. Result: black screen after Huawei logo, no activity
Tried the above with UPDATE.APP from B584. Result: black screen after Huawei logo, no activity
Using Huawei eRecovery from fastboot. Result: "getting package info failed"
I know the phone isn't bricked, because TWRP 3.0.2 still boots.
However, I cannot for the life of me get any Huawei OS to boot on this phone anymore. I'm using fastboot for everything (Linux) and I don't have any problems to flash:
$ fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.887s]
writing 'boot'...
OKAY [ 1.692s]
finished. total time: 2.580s
$ fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 1.420s]
writing 'recovery'...
OKAY [ 2.615s]
finished. total time: 4.036s
$ fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 8.815s]
writing 'cust'...
OKAY [ 5.691s]
finished. total time: 14.507s
$ fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 24.211s]
writing 'system'...
OKAY [ 10.338s]
sending sparse 'system' (460385 KB)...
OKAY [ 23.630s]
writing 'system'...
OKAY [ 10.617s]
sending sparse 'system' (460747 KB)...
OKAY [ 23.682s]
writing 'system'...
OKAY [ 11.319s]
sending sparse 'system' (457010 KB)...
OKAY [ 23.684s]
writing 'system'...
OKAY [ 10.537s]
sending sparse 'system' (443304 KB)...
OKAY [ 23.432s]
writing 'system'...
OKAY [ 10.011s]
finished. total time: 171.461s
My next step would be to try a custom ROM, but there isn't much choice here of flashable zips, and all the custom ROMs seem to be broken or missing features. what I really want is to get this phone back to booting the Huawei OS, but this is seeming impossible.
I'm using Ubuntu 16.04 amd64 and have no issues with adb/fastboot or drivers.
Does anyone have any ideas why this phone refuses to boot after the attempted dual SIM conversion?
I don't really know about this stuff but
After flashing those .img files, have you tried to go stock recovery and tried factory reset there. I think I had something similiar problem (might have been different can't quite remember) but after that I got device to boot.
keikari said:
After flashing those .img files, have you tried to go stock recovery and tried factory reset there. I think I had something similiar problem (might have been different can't quite remember) but after that I got device to boot.
Click to expand...
Click to collapse
How do you access factory recovery? With Power + Vol UP + Vol DOWN?
I've tried this key combination after flashing via fastboot, I get a black screen after the Huawei logo and no recovery.
I'm assuming the factory recovery is supposed to look like what you see during an UPDATE.APP installation?
icewewe said:
How do you access factory recovery? With Power + Vol UP + Vol DOWN?
I've tried this key combination after flashing via fastboot, I get a black screen after the Huawei logo and no recovery.
I'm assuming the factory recovery is supposed to look like what you see during an UPDATE.APP installation?
Click to expand...
Click to collapse
Power + Vol UP
---------- Post added at 07:41 PM ---------- Previous post was at 07:34 PM ----------
Also you can test updateflaher.zip from this thread to use TWRP to install stock rom https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702. I'm not sure will it work for p8lite, but it can install p8lite firmware to honor4x so maybe it can also install p8lite firmware to p8lite. No idea will it help though.
I suspect you did not factory reset before trying to boot. Get into twrp, then factory reset, clear cache, wipe data EVERYTHING YOU CAN clean. No previous data/cache should remain.
Then flash system files using adb (follow the guide to the letter). Reboot. Give it some time, it should come back.
keikari said:
Power + Vol UP
Click to expand...
Click to collapse
Does nothing. I get the Huawei logo and then a black screen.
bumjrah said:
I suspect you did not factory reset before trying to boot. Get into twrp, then factory reset, clear cache, wipe data EVERYTHING YOU CAN clean. No previous data/cache should remain.
Then flash system files using adb (follow the guide to the letter). Reboot. Give it some time, it should come back.
Click to expand...
Click to collapse
What guide are you referring to? The one I linked to doesn't use TWRP and flashes the system via fastboot, which doesn't require a wipe.
Okay, I fixed the issue. I'm really not sure why it didn't work before.
Here are the steps I took:
Restored a TWRP backup I took of another ALE-L21 running B584
Wipe Data/Cache
Flash RECOVERY.img from B584 UPDATE.APP
But then I had the Balong bug. I figured out this is because the oeminfo partition contained data from somewhere. Lollipop or the single SIM build, I don't know.
The UPDATE.APP containing the fix for Balong wouldn't flash in the Huawei recovery. Probably because it's intended for Lollipop and B584 is MM. Or something. Whatever.
So I flashed TWRP and using adb created /data/custom.bin with
Code:
hw/eu
and permissions 0666. This got rid of Balong build, but neither SIM card was recognized by Android.
Then what I did was take a copy of oeminfo from another hw/eu phone, one I had successfully converted earlier, and flashed that. For others reading, oeminfo partition is /dev/block/mtdblk0p8. It's 32MB but almost entirely 0's, so the zip compressed version is really small (80KB).
So here are the steps again:
Restore TWRP backup of another phone running B584
Wipe Data/Cache
Flashed oeminfo for hw/eu from another phone running B584
Flashed Huawei stock recovery from B584
Performed a system update using Huawei recovery with B584 UPDATE.APP
Now the phone recognizes both SIM cards correctly, and has the correct region/oeminfo.
If anyone else has problems with Balong build and you're running MM, here is the oeminfo I used to fix the phone. You will need to unzip and flash in TWRP (or Android if you have root) using the dd command listed above.
Example:
Code:
unzip oeminfo-eu.zip
adb push oeminfo-eu.bin /tmp/
adb shell
dd if=/tmp/oeminfo-eu.bin of=/dev/block/mmcblk0p8
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
seabro01 said:
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
Click to expand...
Click to collapse
uhh no I did not see that in the tutorial.
I tried: ./fastboot flashing unlock_critical
and looks like it freezes after that command...
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
yenkoPR said:
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
Click to expand...
Click to collapse
no not rooted
now im trying to flash back to stock, but when I run flash-all.sh error keeps popping up:
remote: Error flashing partition.
FAILED (remote: Error flashing partition.)
finished. total time: 2.025s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.735s]
writing 'boot_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.782s
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (512 KB)...
OKAY [ 0.103s]
writing 'cmnlib_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.169s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (512 KB)...
OKAY [ 0.101s]
writing 'cmnlib_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.188s
...
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
What do you mean by can't boot up? Do you see boot animation and have you tried to go back to fast boot or recovery?
Sent from my ONEPLUS 3T using Tapatalk
Try different USB ports and cables. When 8.1 came out I had to swap my cable and change the port I was using on my desktop, for some reason the cable I had been using and the port I had been using since I got the phone was no longer adequate. There were a number of other people having the same issue. Some commands would look to complete properly, but following up with the same command (something un-damaging like fastboot --set-active=a | fastboot --set-active=b) would either error again or show that the 'completed' command hadn't actually done anything. I switched cables/ports around (ended up with an Antek USB-A to USB-C cable in a USB3.1 port) and everything worked properly.
If you're trying to flash a stock build image from Essential, you will probably need critical unlocked because those images do contain a bootloader that gets flashed, and that is secured behind critical.
ytlei said:
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
Click to expand...
Click to collapse
What cable are you using?
Do not use the cable that came with the phone!!!!!
We are screwed mate, I am on the same boat with you. Essential took no responsibility and offered a 200$ replacement device. The phone doesn't power on anymore and no light indicators are working, so hard bricked.
I had a Asoip screw up(did not disable password) and was only able to get fastboot. Had to see what slot was active and flashed to that slot that was active boot.img,twrp,Asoip and was back up and running. My bootloader was unlocked. I read through all the posts and peoples screw ups and was able to get it up and running again in a day. I never posted as I wanted to learn it on my own. Good luck.........
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
What cable did you use while connecting to your computer?
And what is the status now? Are you able to turn it on at all by volume and power key combination?
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
ytlei said:
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
Click to expand...
Click to collapse
and pressing the volume down key + power key at the same time doesn't work?.. what happens when you plug your phone into the charger? does it vibrate?
ive had fastboot command problems previously myself with this device and found that the usb port can play a pretty large factor. Swapping usb ports and reattempting to run the commands (as others recommended may be useful) make sure you are using latest version of adb/fastboot and have up to date drivers installed for the phone.
Look at the rooting tutorial there is information in there about swapping active slots (the essential has both a and b paritions) if you set the other slot as the active slot you may be able to regain some communication within fastboot (i would suggest you verify with fastboot devices prior to attempting to flash to partitions).
Additionally you should be able to still recover back to stock without custom recovery using the default recovery partition. I would think that if you are able to access the bootloader you should be able to access the default essential recovery partition. If you can access the standard recovery you should be able to factory reset the phone and sideload a new rom (id suggest the default factory image from essential until you can get back to square one)
I'm in the same boat. Tried to flash twrp after upgrading to 8.1 and got the same Error flashing partition, and now I'm stuck on the bootloader.
I've found that if I lock/unlock and lock/unlock critical it will let me flash the stock 8.1 boot and every other partition except for system and vendor, but gives a flash write error for those. I'm still unable to get past the bootloader.
Essential basically said I'm SOL. $200 out of warranty replacement assuming I live in the US, which I don't.
Mine was doing this too, but it was only a few days old so I returned it. I'm pretty sure it's defective flash memory.
My phone was doing this exact thing. Botched factory installs rendered my phone hardbricked.
Tried a thousand+ things to get it to turn on to no avail. LUCKILY I bought it second hand and have no warranty D:
I want to cry
Hi all I've been searching for help but can't find many similar cases to mine.
Here is the situation: after rooting my huawei p8 lite 2017 with magisk I installed xposed framework and it soft bricked my device (again for the third time this week)
I decided to restore a backup i had made, when i had magisk root but no xposed installed, via TWRP
The backup ends but the phone won't boot and TWRP doesn't want to boot either, it continues to boot between twrp and the stock rom without success.
In fastboot i can't find info of my phone to download the right software from a site to do dload but I do have an update.app file for my phone
When i flash boot.img it gives me:
C:\adb>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
My info is this:
bootloader: unlocked
recovery: not working
huawei eRecovery: tried but failed to boot after
fastboot: partly working
the android version is 8.0
device : PRA-LX1C432B209
I cannot use dload with the update.app from firmware finder
If anyone could help me i would be very thankfull.