Database Info

unlock state relocks after reboot

Hi all,
I have a friend's nexus 5, that I try to unbrick. Unfortunally, and after dragging all threads about unlocking via fastboot, I'm still unable to fix his device.
The fact is, I'm able to unlock (fastboot oem unlock) , then when I reboot the bootloader, it's back locked.
I've tried to flash stock bootloader (for both nexus 5 bootloaders (HHZ11k, HHZ10x) but without success
The device is locked on a bootloop Google screen, impossible to access to recovery mode (via fastboot or via vol up + power)
Anybody's got an idea ?

here is a sequence of trying to update bootloader, you can see that I must unlock for allmost each step
Code:
./fastboot oem unlock
...
OKAY [ 2.596s]
finished. total time: 2.596s
./fastboot erase boot
erasing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.217s
./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.215s]
finished. total time: 0.215s
./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.219s
./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.221s]
finished. total time: 0.221s
./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.493s]
finished. total time: 0.493s
./fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 0.404s]
finished. total time: 0.691s
./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
./fastboot oem unlock
...
OKAY [ 2.130s]
finished. total time: 2.130s
./fastboot oem unlock
...
OKAY [ 3.665s]
finished. total time: 3.665s
./fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.514s]
writing 'radio'...
OKAY [ 2.850s]
finished. total time: 4.364s
./fastboot oem unlock
...
OKAY [ 2.999s]
finished. total time: 2.999s
./fastboot -w update image-hammerhead-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ10x
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 02ffc80f08e51d0d
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ10x'.
Update requires 'HHZ11k'.
finished. total time: 0.601s

You need to flash the right bootloader first before the rest can go through

yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with fastboot boot recovery.img).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (FAILED (remote: invalid bootloader image))

benoit.bds said:
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with
Code:
fastboot boot recovery.img
).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (
Code:
FAILED (remote: invalid bootloader image)
)
Click to expand...
Click to collapse
Looks like you have corrupted memory and nothing is going to work. Time to rma.

jd1639 said:
Looks like you have corrupted memory and nothing is going to work. Time to rma.
Click to expand...
Click to collapse
i agree.

I don't want to come off as alarmist, but I'm starting to see a worrying trend here. If you look at other threads over the past few days, there have been quite a few people with dying flash chips (myself included). There are a few differences in some of the symptoms, but the most common being that 'fastboot oem unlock / lock' fails to stick. It's like the chip is left in some random state of corruption, and unable to be written to. If I were I betting man, I'd say we can expect to see a flood of these posts in coming days.
I would recommend to anyone with an unlocked bootloader, that you get it locked asap and reset the tamper flag too, just in case this same issue occurs with your phone in future, and you need to RMA it.
To the OP, can you confirm whether the device has been previously unlocked, and whether anything was done to the device leading up to the issue? I'm hoping that if this issue is happening to both locked and unlocked devices that Google / LG will have to take the issue seriously should it become an epidemic.

:crying:
My friend has admitted that his n5 had fallen into water...
He gave it for deoxidation + battery replace, but they didn't manage to boot it more than fastboot mode, so I proposed him to give it a try.
To reply to sir_earl, the device was early bought, stock rom and official OTAs.
Anyway, thank you all for your responses !
Regards

[Q] Asus Transformer TF300T bricked - not accepting flash via fastboot

Hi guys,
I have my friend's Asus Transformer tablet which was never rooted nor modified in any way. One time it went dead and did not boot up. When it finally turned back on, screen was stuck on ASUS logo (please see attachment below).
These were the troubleshooting steps taken:
Reset through the small opening at the side (NO GOOD)
Click Wipe Data at Recovery (NO GOOD)
Tried to flash stock rom through fastboot (NO GOOD)
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
And the error in fastboot was this:
Code:
C:\adb>fastboot devices
015d15b4f8041c04 fastboot
C:\adb>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.143s]
sending 'system' (800931 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 7.317s
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!

rmcalingasan said:
Hi guys,
I have my friend's Asus Transformer tablet which was never rooted nor modified in any way. One time it went dead and did not boot up. When it finally turned back on, screen was stuck on ASUS logo (please see attachment below).
These were the troubleshooting steps taken:
Reset through the small opening at the side (NO GOOD)
Click Wipe Data at Recovery (NO GOOD)
Tried to flash stock rom through fastboot (NO GOOD)
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
And the error in fastboot was this:
Code:
C:\adb>fastboot devices
015d15b4f8041c04 fastboot
C:\adb>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.143s]
sending 'system' (800931 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 7.317s
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!
Click to expand...
Click to collapse
Had the same issue. Used Linuxmint and was able to flash image with no issues.

Also had this issue happen to me one day out of the blue, with the exception of not even being able to boot into recovery. I tried everything and ended up giving up as nothing worked. I'm currently waiting for a new motherboard to see if that fixes it.

rmcalingasan said:
Hi guys,
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!
Click to expand...
Click to collapse
...are you sure that the chosen firmware is the right one that fits to your tablet exactly? I suppose it's the wrong one, because I used to take Version WW_V10.6.1.27.5 and was successful to get a clean Stock Rom JB. I also may be wrong.
However I think it's worth to make a further attempt to flash that blob as follows:
Make a folder C:\Flash and copy the .blob from WW_V10.6.1.27.5 into the folder.
Open Minimal ADB and Fastboot and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\Flash and put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Please note, I cannot guarantee any success-everything you do is on your own risk. Good luck!

ebonit said:
...are you sure that the chosen firmware is the right one that fits to your tablet exactly? I suppose it's the wrong one, because I used to take Version WW_V10.6.1.27.5 and was successful to get a clean Stock Rom JB. I also may be wrong.
However I think it's worth to make a further attempt to flash that blob as follows:
Make a folder C:\Flash and copy the .blob from WW_V10.6.1.27.5 into the folder.
Open Minimal ADB and Fastboot and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\Flash and put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Please note, I cannot guarantee any success-everything you do is on your own risk. Good luck!
Click to expand...
Click to collapse
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...

rmcalingasan said:
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...
Click to expand...
Click to collapse
It's just stuck at sending 'system'.
I've tried using the sd card method but failed too.

aem2267 said:
Had the same issue. Used Linuxmint and was able to flash image with no issues.
Click to expand...
Click to collapse
Installed Linuxmint too. (Loving the interface!)
But still stuck at sending 'system' at terminal.

rmcalingasan said:
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...
Click to expand...
Click to collapse
It's strange. As I wrote "sending..." takes a while then appears "write..." and the load status will be shown. Were you patient enough? Did you ever see the load status? Are you sure it's the right "blob"?

ebonit said:
It's strange. As I wrote "sending..." takes a while then appears "write..." and the load status will be shown. Were you patient enough? Did you ever see the load status? Are you sure it's the right "blob"?
Click to expand...
Click to collapse
Yes, I'm quite sure it's the correct blob. The JP_epad-10.6.1.27.5-20130902 shows at the top of the screen of the tablet.
One thing I noticed when erasing other parts was that it failes erasing other parts:
Code:
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot devices
015d15b4f8041c04 fastboot
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.055s]
finished. total time: 2.055s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: (Unknown error code))
finished. total time: 0.382s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase boot
erasing 'boot'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase misc
erasing 'misc'...
FAILED (remote: (Unknown error code))
finished. total time: 0.038s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: (Unknown error code))
finished. total time: 0.043s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot -i 0x0B05 flash system bloberasing 'system'...
OKAY [ 0.010s]
sending 'system' (800931 KB)...
I'm currently trying to download an older version of JP blob.

rmcalingasan said:
Yes, I'm quite sure it's the correct blob. The JP_epad-10.6.1.27.5-20130902 shows at the top of the screen of the tablet.
One thing I noticed when erasing other parts was that it failes erasing other parts:
Code:
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot devices
015d15b4f8041c04 fastboot
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.055s]
finished. total time: 2.055s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: (Unknown error code))
finished. total time: 0.382s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase boot
erasing 'boot'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase misc
erasing 'misc'...
FAILED (remote: (Unknown error code))
finished. total time: 0.038s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: (Unknown error code))
finished. total time: 0.043s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot -i 0x0B05 flash system bloberasing 'system'...
OKAY [ 0.010s]
sending 'system' (800931 KB)...
I'm currently trying to download an older version of JP blob.
Click to expand...
Click to collapse
Please try the version WW_V10.6.1.27.5. WW stands for world wide. That's what I used to take. http://www.asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Once downloaded, you need to head to the path “Settings > About Tablet” where you will have to note down the Build number. If the build number starts with “WW”, your SKU is WW. Similarly, if your build number starts with “US”, you must download the firmware for the US SKU.

Nexus 5 bootloop & recovery doesn't work

First of all, I'm german, so sorry if something's wrong with my English
Hey I've got a Nexus 5 laying around (I don't use it) and it is bootlooping. I would like to fix it but nothing works.
1. Power button isn't stuck (checked it)
2. I can boot into the bootloader
3. fastboot works fine
4. Can't get into Recovery ( when I boot into Recovery the Google Logo comes up and it keeps restarting)
5. Flashing a fresh Android doesn't work
6. Flashing a custom Recovery doesn't work
7. I don't know anything about the phone (I just got it because i wanted the display for my other Nexus 5)
8. bootloader is unlocked
I have fastboot and adb on a Windows and a Linux machine. Thanks for your help

Your English is perfect (apart from the lower case on "German" ) - if you hadn't started with that sentence I would never have known.
At the risk of boring people who may have already seen this post in other threads, see if this advice helps at all. If you have a working bootloader screen it may work. You can ignore the first sentence about backup, since in your situation it's redundant.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/images#hammerhead) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

Didn't work...
Here's my output:
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash bootloader bootloader.img
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
OKAY [ 0.453s]
finished. total time: 0.688s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash radio radio.img
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.422s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.313s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.109s]
finished. total time: 1.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash system system.img
target didn't report max-download-size
erasing 'system'...
OKAY [ 0.516s]
sending 'system' (692940 KB)...
OKAY [ 21.893s]
writing 'system'...
OKAY [ 46.692s]
finished. total time: 69.132s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase boot
erasing 'boot'...
OKAY [ 0.234s]
finished. total time: 0.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (8620 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 1.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash cache cache.img
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.484s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.063s]
finished. total time: 2.188s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (14626 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 1.125s]
finished. total time: 1.797s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
When i boot to recovery the google logo appears and still restarts all the time.
As i said, i've already tried flashing a custom recovery and Android before... Didn't work for me..

Sorry to hear that. I've never seen the "target didn't report" message. Maybe a hardware problem?

I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.

Budden6800i said:
I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.
Click to expand...
Click to collapse
Why you are using krt16m image? It's old...
Please download M4B30Z and try again...

BLL-L22 Firmware and Help

Hello,
I need help to unbrick my phone please,
After trying to back to stock i got stuck while dload method with BLL-L22C636B150 (android 6.0) Firmware after flashing RollbackPackage from same firmware (android 7.0 to 6.0)
My phone's screen is now only black, no boot logo anymore or recovery.
It's only show connected fastboot while plug in, i can only reboot to fastboot.
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.006s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.007s]
finished. total time: 0.008s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.005s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7XXXX
(bootloader) IMEI:8646XXXX
(bootloader) IMEI1:8646XXXX
What can i do please ?

Try team mt tool for unbrick provide file from marshmallow update.app

siddhrsh said:
Try team mt tool for unbrick provide file from marshmallow update.app
Click to expand...
Click to collapse
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode

Demodark said:
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Click to expand...
Click to collapse
Did you flash marshmallow files

Images
Yes i tried to unbrick with : Huawei_GR5_2017_BLL-22_C636B150_South_East_Asia_6.0.zip
17:49:30: All images are found, everything is ready for the unbricking process.
17:49:32: Unbricking started. Your computer may freezes during the process.
17:49:32: flash boot "C:\adb\B150\boot.img"
17:49:34: The Boot image is flashing successfully
17:49:34: flash system "C:\adb\B150\system.img"
17:52:03: The System image is flashing successfully
17:52:03: flash cust "C:\adb\B150\cust.img"
17:52:26: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 12.833s]
writing 'cust' 1/2...
OKAY [ 3.181s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.114s]
writing 'cust' 2/2...
OKAY [ 0.045s]
finished. total time: 16.173s
17:52:26: Error#1
17:52:26: flash recovery "C:\adb\B150\recovery.img"
17:52:29: The Recovery image is flashing successfully
17:52:29: flash userdata "C:\adb\B150\userdata.img"
17:52:36: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 3.784s]
writing 'userdata'...
OKAY [ 1.013s]
finished. total time: 4.797s
17:52:36: Error#1
17:52:36: Completed
17:52:36: Something went wrong (((
Huawei Multi-Tool by Team MT v. 8.0.3.1 beta
I dont know wich one i can try now ?
http://pro-teammt.ru/firmware-database/?firmware_model=bll-l22&firmware_page=0

Black Screen
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.

Demodark said:
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Click to expand...
Click to collapse
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot

shashank1320 said:
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
Click to expand...
Click to collapse
What is "the small data file" please ?

PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.007s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.006s]
finished. total time: 0.006s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.006s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7N17609000963
(bootloader) IMEI:864646034450028
(bootloader) IMEI1:864646034717855
OKAY [ 0.005s]
finished. total time: 0.005s
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
PS C:\adb>

Demodark said:
What is "the small data file" please ?
Click to expand...
Click to collapse
Let me check the firmware and get the link for you

shashank1320 said:
Let me check the firmware and get the link for you
Click to expand...
Click to collapse
News ?

Demodark said:
News ?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine

shashank1320 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
Click to expand...
Click to collapse
Link is dead.

Demodark said:
Link is dead.
Click to expand...
Click to collapse
Let me recheck

What can i do ?
Always black screen, but phone detected as fastboot mode, reboot only leads to fastboot mode.

have you tried unlocking again your bootloader? updating or rollbacking of EMUI makes your bootloader locked by default.
try to unlock it first and flash your OS
if you want to use the dload way. try flashing the stock recovery after unlocking your bootloader.

Demodark said:
Link is dead.
Click to expand...
Click to collapse
K.. But after that how reset the DNS to its original state

Help in TWRP Install

Hi,
I was trying to install TWRP but I keep getting the same error all the time.
Someone please help me.
Any suggestions?
My Tablet is not rooted yet also do I need to do a bootloader unlock or not?
If yes any useful links? Im so stuck I wanna install 7.1 to my Tablet.
Im still using JB android official by Asus.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash recovery "C:\twrp.img"
target didn't report max-download-size
sending 'recovery' (7126 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 4.382s

Hi, you could try flashing with the executables from my pack: https://forum.xda-developers.com/t/...0t-any-version-to-android-7-1-nougat.3554744/