Hi all, Please help me.
Just yesterday, I screwed my Honor 8 Lite.
By hoping to solve issue missing fingerprint option, I've flashed my Honor 8 Lite PRA-TL10 Russian to PRA-LA1C185B101(MiddleEast).
Flashing steps that I did:
- Unlock bootloader
- Flash Elite-TWRP and boot into TWRP
- Flash PRA-LA1C185's OEMINFO from TWRP.
- Flash StockRecovery.img from TWRP.
- Put SDCard that contains "dload" from PRA-LA1C185101 firmware
- Disconnect and Power off device.
- Force Update firmware by pressing Volume_UP + Volume_Down + Power.
- Firmware updating process began.. and I left it running...
- 10 minutes later I check the phone and IT IS DEAD! OMG!!!
Phone's screen remain black/dark, no vibration, no response to combinations buttons press, no sign of life. Then I try to connect to PC, device still detected as "ADB Sooner Single ADB Interface", and it is in bootloader mode. I can and have use fastboot command to "flash" boot/recovery/system/cust/userdata, but it failed to bring my Honor 8 Lite alive..
The screen still remain black/dark, no matter what button I pressed, it keeps rebooting into bootloader mode.
When I check from fastboot:
C:\Huawei\ROM\Restore>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: PRA-LA1C185B165
finished. total time: 0.012s
C:\Huawei\ROM\Restore>fastboot devices
DUPNW17XXXXXXXX3 fastboot
C:\Huawei\ROM\Restore>fastboot oem check-rootinfo
...
(bootloader) old_stat: NULL
(bootloader) now_stat: NULL
(bootloader) change_time: NULL
OKAY [ 0.020s]
finished. total time: 0.021s
Click to expand...
Click to collapse
My fastboot flashing results:
C:\Huawei\ROM\Restore>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (15520 KB)...
OKAY [ 2.728s]
writing 'boot'...
OKAY [ 0.300s]
finished. total time: 3.030s
C:\Huawei\ROM\Restore>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35568 KB)...
OKAY [ 5.787s]
writing 'recovery'...
OKAY [ 0.669s]
finished. total time: 6.458s
C:\Huawei\ROM\Restore>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (111459 KB)...
OKAY [ 2.794s]
writing 'cust'...
OKAY [ 0.811s]
finished. total time: 3.607s
C:\Huawei\ROM\Restore>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.158s]
writing 'system' 1/6...
OKAY [ 3.654s]
sending sparse 'system' 2/6 (457285 KB)...
OKAY [ 12.152s]
writing 'system' 2/6...
OKAY [ 3.055s]
sending sparse 'system' 3/6 (458042 KB)...
OKAY [ 12.358s]
writing 'system' 3/6...
OKAY [ 3.507s]
sending sparse 'system' 4/6 (430632 KB)...
OKAY [ 11.429s]
writing 'system' 4/6...
OKAY [ 2.938s]
sending sparse 'system' 5/6 (460799 KB)...
OKAY [ 12.158s]
writing 'system' 5/6...
OKAY [ 2.952s]
sending sparse 'system' 6/6 (456400 KB)...
OKAY [ 12.178s]
writing 'system' 6/6...
OKAY [ 2.989s]
finished. total time: 91.539s
C:\Huawei\ROM\Restore>fastboot flash userdata userdata.img
target reported max download size of 471859200 bytes
sending sparse 'userdata' 1/2 (458754 KB)...
OKAY [ 12.080s]
writing 'userdata' 1/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 3.300s]
sending sparse 'userdata' 2/2 (290817 KB)...
OKAY [ 7.655s]
writing 'userdata' 2/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.884s]
finished. total time: 24.924s
C:\Huawei\ROM\Restore>fastboot flash oeminfo oeminfo
target reported max download size of 471859200 bytes
sending 'oeminfo' (65536 KB)...
OKAY [ 7.512s]
writing 'oeminfo'...
FAILED (remote: Command not allowed)
finished. total time: 7.522s
Click to expand...
Click to collapse
Bricked conditions:
- Screen remain OFF, no Light, no Image. I believe this is NOT LCD DAMAGED issue.
- Detected(Stuck) as bootloader device.
- Updatable/flashable from fastboot.
- No responses to buttons pressed, except POWER_LONG_PRESSED to reboot... into bootloader again and again.
- Bootloader unlocked.
Please any body help me..
EDIT:
I've revived my device with DC Phoenix flashing tool, using firmware PRA-TL10C10B170.
Thanks to Mr. HasanMirza01 for his great supports. I won't be able to revive this device without him.
For others who facing this same issue, just buy service from DC(cost you min. 4 credits to 15 credits) and just flash it using DC-Phoenix and your original model's firmware. It will bring your Honor 8 Lite back to life once again.
NOTE:
NEVER convert PRA-AL00/PRA-TL00 model to PRA-LX1/PRA-LA1. Doing so will brick your device.
MultiTool Unbricking results
08:09:33: All images are found, everything is ready for the unbricking process.
08:10:10: Unbricking started. Your computer may freezes during the process.
08:10:10: flash boot "C:\Huawei\ROM\Restore\boot.img"
08:10:11: The Boot image is flashing successfully
08:10:11: flash system "C:\Huawei\ROM\Restore\system.img"
08:14:01: The System image is flashing successfully
08:14:01: flash cust "C:\Huawei\ROM\Restore\cust.img"
08:14:04: The Cust image is flashing successfully
08:14:04: flash recovery "C:\Huawei\ROM\Restore\recovery.img"
08:14:06: The Recovery image is flashing successfully
08:14:06: flash userdata "C:\Huawei\ROM\Restore\userdata.img"
08:15:18: target reported max download size of 471859200 bytes
sending sparse 'userdata' 1/2 (458754 KB)...
OKAY [ 12.109s]
writing 'userdata' 1/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 3.284s]
sending sparse 'userdata' 2/2 (272385 KB)...
OKAY [ 7.168s]
writing 'userdata' 2/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.802s]
finished. total time: 24.363s
08:15:18: Error#1
08:15:18: Completed
08:15:18: Something went wrong (((
DC - Unlocker 2 Client detection..
DC - Unlocker 2 Client 1.00.1390
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : PRA-LA1
Model : Huawei phone in fastboot mode
IMEI : 86xxxxxxxxxxxx3
Serial NR. : DUPNWxxxxxxxxxx3
Firmware : PRA-LA1C185B165
IMEI1:86xxxxxxxxxxxx6
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 0
Can u access Erecovery??
by pressing vol up with power button.. release power button when phone b0ot up...
usb cable should be connected.... phone should be in shutdown state while using these steps.
2nd way to erecovery is hold volume up & power... when bootup release both buttons then press n hold volume up...
liboct87 said:
Can u access Erecovery??
by pressing vol up with power button.. release power button when phone b0ot up...
usb cable should be connected.... phone should be in shutdown state while using these steps.
2nd way to erecovery is hold volume up & power... when bootup release both buttons then press n hold volume up...
Click to expand...
Click to collapse
Unfortunately, no sir. It can not boot into eRecovery mode.
It can only boot into fastboot mode with screen off, no light at all.
This is strange, since I did not messing with bootloader.
I have the same problem, flashed OEM-info PRA-LX1C432 on my PRA-AL00C00
I thing no way out
eifeldragon said:
I have the same problem, flashed OEM-info PRA-LX1C432 on my PRA-AL00C00
I thing no way out
Click to expand...
Click to collapse
strange!!!!!
i did this before
i have PRA-LA1C185
flashed chinese oem than europe oem info... now m back to chinese....
try to get into erecovery ur problem will be solved br0
best of luck man
eifeldragon said:
I have the same problem, flashed OEM-info PRA-LX1C432 on my PRA-AL00C00
I thing no way out
Click to expand...
Click to collapse
liboct87 said:
strange!!!!!
i did this before
i have PRA-LA1C185
flashed chinese oem than europe oem info... now m back to chinese....
try to get into erecovery ur problem will be solved br0
best of luck man
Click to expand...
Click to collapse
I think there's are differences between the PRA-LA1/PRA-LX1 with PRA-AL00/PRA-TL10/PRA-TL00 devices..
I think those devices have different board firmware.
PRA-LA1 can be converted to PRA-LX1, may be, never tested..
PRA-AL00 can be converted to PRA-TL10. TESTED..
PRA-AL00 can not be converted to PRA-LA1.. like my case.. it BRICKED
PRA-TL10 can not be converted to PRA-LX1, it will bricked, like my case too.
Beware of Honor regions conversion..
I haven't test conversion with DC-HCU tool, may be it will work since it rebuild the whole board firmware..
Note: I've recover my bricked Honor 8 Lite. Thanks to Mr. HassanMirza01 that giving me a lot of supports. I'll never able to recover my Honor 8 Lite without him. He is really my life saviour.
Unlucky for us there's no free flashing tool to use in this case.
May be some expert can sniff on usb connections with paid tool, to see what commands send to the device. To see how that paid tool can flash our phone even if it is on bootloader mode, which we certainly couldn't do that with "fastboot". And willing to put works on it to provide Huawei users a powerful enough flashing tool, that could bring phone alive..
So we no need to worry about this hard-brick issue..
Sorry, double post..
So what service from DC-Unlocker exactly did you use?
Related
So as mentioned in the title, I am stuck in a boot loop after botching the OTA upgrade.
Here's the sequence of events thus far...
Current ROM Pure Nexus (not exactly sure which version, 6.01 something I think, but I hadn't updated it in a bit)
Backed up my ROM with TWRP
Due to the fact that I didn't read anything and got over zealous, I dirty flashed the N OTA over Pure Nexus
After dirty flashing it, N booted up and seemed to work ok until apps started crashing like crazy.
Reflashed TWRP
Restored the backup I previously made
Phone has not been working since; it just boot loops
Wiped data; still boot loops
Attempted flashing older bootloaders, radios, and vendor images back to it to no avail; still boot loops
Finally, I backed up everything on internal storage and flashed the latest factory image (MTC20F) straight from Google
STILL BOOT LOOPS
Reinstalled TWRP, wiped data a few more times... still boot loops
I am officially at a loss here. I can get into fastboot and twrp no problem, but the device won't start.
Current info:
BL: angler-03.54
Baseband: angler-03.61
Device is UNLOCKED.
Qfuse Status: Enabled
Any thoughts would be appreciated! I just want to get it into ANY working state at this point.
Do a full wipe system and vendor and everything, except efs maybe. Flash the twrp 3.0.2 then fastboot flash the factory images of that doesn't work then try to ask Heisenberg.
Done, done, and done, to no avail. Same issue, just a boot loop.
Funkwheat said:
Done, done, and done, to no avail. Same issue, just a boot loop.
Click to expand...
Click to collapse
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Jammol said:
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Tried that earlier. Did it again just now following his precise instructions and still nothing. Maybe worth noting, though, that I got an error when trying to flash vendor.img. Everything else went fine. Currently not boot looping, but have been at the "Google" screen for about ten minutes.
Funkwheat said:
Tried that earlier. Did it again just now following his precise instructions and still nothing. Maybe worth noting, though, that I got an error when trying to flash vendor.img. Everything else went fine. Currently not boot looping, but have been at the "Google" screen for about ten minutes.
Click to expand...
Click to collapse
Did you wipe data with TWRP?
Heisenberg said:
Did you wipe data with TWRP?
Click to expand...
Click to collapse
I wiped it with factory recovery. I'll try again now with TWRP.
I tried..
Jammol said:
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
ArminasAnarion said:
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
Click to expand...
Click to collapse
Noooooo! Don't lock the bootloader. If you do that you'll have no way to flash anything and will be royally screwed.
Heisenberg said:
Noooooo! Don't lock the bootloader.
Click to expand...
Click to collapse
I didnt! I realized that would probably brick it
What should i do then? I did the complete back to stock guide and still a loop :C
Heisenberg said:
Did you wipe data with TWRP?
Click to expand...
Click to collapse
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
ArminasAnarion said:
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
Click to expand...
Click to collapse
Had you flashed Nougat at any point? Not sure if you're having the same issue or not.
ArminasAnarion said:
I didnt! I realized that would probably brick it
What should i do then? I did the complete back to stock guide and still a loop :C
Click to expand...
Click to collapse
Funkwheat said:
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
Click to expand...
Click to collapse
I really don't know what either of you should do. Wiping and flashing the factory images should fix anything on a Nexus.
Funkwheat said:
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
Had you flashed Nougat at any point? Not sure if you're having the same issue or not.
Click to expand...
Click to collapse
Yeah I had flashed Nougat and gotten it to work. But where some root issues so I was going to go back to Pure Nexus, I wiped everything and flash MTC20F boot and radio and vendor and on reboot started having the loop
Heisenberg said:
I really don't know what either of you should do. Wiping and flashing the factory images should fix anything on a Nexus.
Click to expand...
Click to collapse
Agreed! I just went through your guide again, verbatim, this time with a TWRP data wipe beforehand and still no luck. This time everything flashed fine with the latest MTC20F images. Here's a command line transcript...
Code:
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash bootloader bootlo
ader-angler-angler-03.54.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.316s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash radio radio-angle
r-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.082s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.255s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.014s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash boot boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12201 KB)...
OKAY [ 0.302s]
writing 'boot'...
OKAY [ 0.182s]
finished. total time: 0.487s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.031s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash cache cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.023s]
sending 'cache' (5752 KB)...
OKAY [ 0.150s]
writing 'cache'...
OKAY [ 0.106s]
finished. total time: 0.282s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash recovery recovery
.img
target reported max download size of 494927872 bytes
sending 'recovery' (13133 KB)...
OKAY [ 0.321s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.517s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash system system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.397s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 11.178s]
writing 'system' 1/5...
OKAY [ 6.861s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 11.220s]
writing 'system' 2/5...
OKAY [ 7.044s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 11.236s]
writing 'system' 3/5...
OKAY [ 7.268s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.822s]
writing 'system' 4/5...
OKAY [ 6.593s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.353s]
writing 'system' 5/5...
OKAY [ 0.808s]
finished. total time: 74.788s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash vendor vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185181 KB)...
OKAY [ 4.125s]
writing 'vendor'...
OKAY [ 2.974s]
finished. total time: 7.100s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>
Btw, how long at the "Google" boot screen should I be waiting before I give up on it ever booting? I've been waiting about ten minutes. I have heard 20 elsewhere, but that sounds excessive.
Well I am doing a complete wipe back to 6.0.0 (MDA89D) I will let you know if it works...
Funkwheat said:
Agreed! I just went through your guide again, verbatim, this time with a TWRP data wipe beforehand and still no luck. This time everything flashed fine with the latest MTC20F images. Here's a command line transcript...
Code:
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash bootloader bootlo
ader-angler-angler-03.54.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.316s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash radio radio-angle
r-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.082s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.255s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.014s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash boot boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12201 KB)...
OKAY [ 0.302s]
writing 'boot'...
OKAY [ 0.182s]
finished. total time: 0.487s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.031s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash cache cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.023s]
sending 'cache' (5752 KB)...
OKAY [ 0.150s]
writing 'cache'...
OKAY [ 0.106s]
finished. total time: 0.282s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash recovery recovery
.img
target reported max download size of 494927872 bytes
sending 'recovery' (13133 KB)...
OKAY [ 0.321s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.517s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash system system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.397s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 11.178s]
writing 'system' 1/5...
OKAY [ 6.861s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 11.220s]
writing 'system' 2/5...
OKAY [ 7.044s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 11.236s]
writing 'system' 3/5...
OKAY [ 7.268s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.822s]
writing 'system' 4/5...
OKAY [ 6.593s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.353s]
writing 'system' 5/5...
OKAY [ 0.808s]
finished. total time: 74.788s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash vendor vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185181 KB)...
OKAY [ 4.125s]
writing 'vendor'...
OKAY [ 2.974s]
finished. total time: 7.100s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>
Btw, how long at the "Google" boot screen should I be waiting before I give up on it ever booting? I've been waiting about ten minutes. I have heard 20 elsewhere, but that sounds excessive.
Click to expand...
Click to collapse
It should have booted after 10 minutes, normally. But, if is trying to encrypt it could take a very long time. Were you previously decrypted?
Just did you guide back to 6.0.0 (MDA89D) and the phone is still looping between the google screen and the "cant check for corruption screen"... Am I just bricked?? I have no idea what to even try...
I don't think so, unless that's something that happened automatically. I was on PureNexus (unsure which build).
ArminasAnarion said:
Just did you guide back to 6.0.0 (MDA89D) and the phone is still looping between the google screen and the "cant check for corruption screen"... Am I just bricked?? I have no idea what to even try...
Click to expand...
Click to collapse
Looks like you and I are having the exact same issue... We both went to today's OTA, both ended up attempting to go back, and are both in boot loop states now.... Wonder if this is an actual issue. Hope we can figure it out, cause until then I'm without a phone entirely.
so I am on pure nexus the latest build running xposed and ex kernel. How would I flash android 7..0 and not get this bootloop, if I format completely wipe my phone in twrp would that do it before I flash the ota.zip?
QHC0216226001093 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (28738 KB)...
OKAY [ 0.617s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.189s
target reported max download size of 471859200 bytes
sending 'cust' (16381 KB)...
OKAY [ 0.350s]
writing 'cust'...
FAILED (remote: sparse flash write failure)
finished. total time: 0.379s
target reported max download size of 471859200 bytes
sending 'recovery' (43578 KB)...
OKAY [ 0.934s]
writing 'recovery'...
OKAY [ 0.865s]
finished. total time: 1.803s
target reported max download size of 471859200 bytes
sending sparse 'system' (452422 KB)...
OKAY [ 10.092s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.143s
i'm totally stuck.
my phone is c432
I was on twisted rom b386, update to noguat b521 succesfully completed but after reboot i got bootloop. Tried everything and nothing works. Phone won't boot any version anymore. also i cannot install twrp 4.1 again. I can install just stock recovery. When i flash twrp i get stucked on "your device is now booting". Tried to flash through dload doesn't work either.
any suggestion is apreciated.
thx
Flash stock nougat revovery. Download C185B320. Extract update.app into the dload folder of your sdcard. And do the dload update. Try it and let us know.
looks like huawei removed from his website.
is there some mirror?
found
https://drive.google.com/file/d/0BxOdJKPsTEZZZk4ybFdHUXNNd1E/view
software installation failed! Incompatibility with current version. Please download the correct update package.
tried to extract files to debrick with italian knife and i got a partition error. is there a way to redo partitions?
Try rollback package.http://forum.xda-developers.com/mat...-to-downgrade-mate-8-emui-5-to-t3515202/page1
ok, i was able to rollback just with the asian one. now i'm trying to download stock asian firmware and i'll try to flash. i hope this works because i wasted 1 day and half to get it fixed..
it's weird that i was able to rollback just with c900
no luck. it doesn't boot. stuck on huawei logo.
ok, wiping system and cache did the trick.
thanks everyone
Icchan said:
ok, wiping system and cache did the trick.
thanks everyone
Click to expand...
Click to collapse
did you wipe in twrp? and what did you do next?
wisepy112 said:
did you wipe in twrp? and what did you do next?
Click to expand...
Click to collapse
Can you reply please i have the same problem.
please aswered i have the excacy same problem
feplau said:
please aswered i have the excacy same problem
Click to expand...
Click to collapse
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
Good afternoon to all, I need a lot of help. I have a p9 lite VNS-L23 C605B120, try to install the rom revolution nougat, unlock the bootloader, install the recovery and from there an update file, when I finish, I reset and the phone left with the black screen, I connect it, the PC and I recognize it: Android bootloader interface, do not enter with the 3 buttons: vol + vol - and button on.
I need help on how I can flash it, with some program or how I can fix it, and what are the necessary files ... Thank you very much already.
Pd: the HiSuit of hawei is opened every time I connect the phone to the PC, but it does not allow me to recover the system, at the beginning it leaves: it is acceded to the system recovery mode, I click to recover system and then leaves, the device Does not support system recovery.
Same here unfortunately
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Potato997 said:
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Click to expand...
Click to collapse
This is in flashboot mode, and yes unlock bootloader, but black screen, allows to restart with commands, but unfortunately I do not have much knowledge about this, I hope help, what steps can I take to be able to turn it on.
Try to flash again TWRP and boot to recovery.
By fastboot I can reset, install twrp, reboot, but still black screen, there is no vibration, but when connecting the phone, appears in android bootloader interface. What else can I do with commands
As I said, can you boot to TWRP?
Potato997 said:
As I said, can you boot to TWRP?
Click to expand...
Click to collapse
See
hanzox5 said:
See
Click to expand...
Click to collapse
....
But no reboot in recovery
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13810 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.788s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.143s]
finished. total time: 1.862s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (331661 KB)...
OKAY [ 7.077s]
writing 'cust'...
OKAY [ 8.053s]
finished. total time: 15.149s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (452763 KB)...
OKAY [ 10.992s]
writing 'system'...
OKAY [ 11.640s]
sending sparse 'system' (458056 KB)...
OKAY [ 10.877s]
writing 'system'...
OKAY [ 11.137s]
sending sparse 'system' (459104 KB)...
OKAY [ 11.816s]
writing 'system'...
OKAY [ 12.201s]
sending sparse 'system' (457466 KB)...
OKAY [ 11.096s]
writing 'system'...
OKAY [ 11.214s]
sending sparse 'system' (460756 KB)...
OKAY [ 11.049s]
writing 'system'...
OKAY [ 11.190s]
sending sparse 'system' (135249 KB)...
OKAY [ 3.234s]
writing 'system'...
OKAY [ 3.302s]
finished. total time: 119.793s
C:\Program Files (x86)\HiSuite\hwtools>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\HiSuite\hwtools>
Reboot to recovery in this way: shut down the phone, press volume up + power button
Factory reset
Reboot
Do not enter recovery, still on black screen, can tell me which software I can flash it
I already told you like three times.. try both TWRP and stock recovery..
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
hanzox5 said:
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
Click to expand...
Click to collapse
fastboot boot recovery.img
Try that.
Also you should try the three buttons method now.
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
hanzox5 said:
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
Click to expand...
Click to collapse
ಠ_ಠ
Weird.
479/5000
Several times I installed TWRP and stock recovery, and I can not enter any of the 2 forms and even with the three buttons, I even purchase a micro SD of 32gb class 10, with this saying that the SD was the one that did not work.
Please, let's go again, I recommend doing from 0 to try to solve this blessed problem. That I should be doing, it will be possible to clean the cache and user data from fastboot, and from there to do something more.
Have you tried three button method with update.app in dload folder in SD card?
If yes, did it gave you some error/did the update started/when did it stopped?
If I have the sd, and inside the Dload folder, update.app, but it does nothing.
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
dladz said:
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
Click to expand...
Click to collapse
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
reppinrengar said:
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
Click to expand...
Click to collapse
You don't flash using fastboot just stick with the installer.bat file, it's in the ROM zip
If that doesn't work then your system is borked, in which case like I said just use the MSM tool.
You're done in several steps.
You should never need to unlock critical
reppinrengar said:
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
Click to expand...
Click to collapse
Use the original OnePlus cable.
This phone have probably softbrick or hardbrick and bootloop and intro to recovery (no erecovery) gets a rescue mode screen
I have tried with the "potatonv" tool and trying to flash a stock rom and a custom recovery but none work and I have the bootloader unlocked but I get these following results:
>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 471859200 bytes
sending 'RECOVERY' (36118 KB)...
OKAY [ 0.986s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 1.012s
>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (36118 KB)...
OKAY [ 1.000s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.468s