Database Info

[Q] Loopboot on Android logo

Hi,
Just received my opo yesterday and the phone never booted successfully.
When I turn the phone on, the android logo appears and, after a few seconds, it vibrates and then reboots... Over and over again.
Recovery mode doesn't work, but I can enter fastboot mode.
Tried to unlock the bootloader to flash the factory image but it seams that it isn't working even if the command returns successful because when I try to flash something it says that the device is locked.
I filled a ticket on OP's support but I'm afraid I don't get a response before 10+ days.
Does anyone have any suggestion to help?
Thanks!

This situation seems like a situation I've heard in the past. Did you happen to use a toolkit to root?
Are you able to boot into a custom recovery by typing fastboot boot recovery.img (download TWRP and rename it to recovery.img putting it into fastboot)
Please don't use a toolkit to do this.

I didn't tried boot into a custom recovery yet.
I'll try that as soon as I get home.
First I tried manually and then by using a toolkit and the results were the same.
Thanks!

I tried booting into TWRP recovery:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
OKAY [ 0.021s]
finished. total time: 0.463s
But when the booted again it didn't go to the recovery and started the bootloop again.
Any other ideias?
Thanks!

Hi, I believe your phone simply has no rom, so you have to flash one with fastboot. I've seen you already have fastboot working, so that will greatly help.
Follow this and your phone should hopefully work as expected :
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Don't hesitate to ask.
Enviado desde mi GT-P5210 mediante Tapatalk

adlx.xda said:
Hi, I believe your phone simply has no rom, so you have to flash one with fastboot. I've seen you already have fastboot working, so that will greatly help.
Follow this and your phone should hopefully work as expected :
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Don't hesitate to ask.
Enviado desde mi GT-P5210 mediante Tapatalk
Click to expand...
Click to collapse
Thanks for your help.
That was my first thought and I tried to flash the factory image a number of times...here's what I get:
target reported max download size of 536870912 bytes
sending 'modem' (56241 KB)...
OKAY [ 1.996s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.999s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.015s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.019s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'aboot' (374 KB)...
OKAY [ 0.017s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.020s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.013s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.014s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.017s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.366s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.369s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: afb25fe8
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (5798 KB)...
OKAY [ 0.208s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.227s
Press any key to exit...
It seems that the bootloader is unlocked, but I tried to unlock it several times:
...
OKAY [ 0.010s]
finished. total time: 0.010s
But, it still doesn't work!!!

Did you fastboot oem unlock? I don't remember the exact command by memory, sorry. You can probably find it on any One plus forum.
Edit: yep, command is correct.
Enviado desde mi GT-P5210 mediante Tapatalk

adlx.xda said:
Did you fastboot oem unlock? I don't remember the exact command by memory, sorry. You can probably find it on any One plus forum.
Enviado desde mi GT-P5210 mediante Tapatalk
Click to expand...
Click to collapse
Yes...it's the last piece of my last message. Sorry if it wasn't clear.
Apparently, it works fine...but then I get those messages when trying to flash anything.

Hum, I don't know then... Weird.
Enviado desde mi GT-P5210 mediante Tapatalk

adlx.xda said:
Hum, I don't know then... Weird.
Enviado desde mi GT-P5210 mediante Tapatalk
Click to expand...
Click to collapse
Yes, unfortunately it's very weird.
If you remember anything else, please let me know.
Thank you for your help!

What does it return when you issue this command?
Code:
fastboot oem device-info
Transmitted via Bacon

timmaaa said:
What does it return when you issue this command?
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
Code:
>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
Thanks!

pr3tender said:
Code:
>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
Thanks!
Click to expand...
Click to collapse
Your bootloader isn't unlocked so there's no way flashing the factory images is going to work. Can you copy/paste the text from an attempt at unlocking the bootloader?
Transmitted via Bacon

timmaaa said:
Your bootloader isn't unlocked so there's no way flashing the factory images is going to work. Can you copy/paste the text from an attempt at unlocking the bootloader?
Transmitted via Bacon
Click to expand...
Click to collapse
The text from the attempt at unlocking the bootloader is already in a previous post and it returns ok!
Nevertheless, as soon as I get home I will try again.
Thanks!

timmaaa said:
Your bootloader isn't unlocked so there's no way flashing the factory images is going to work. Can you copy/paste the text from an attempt at unlocking the bootloader?
Transmitted via Bacon
Click to expand...
Click to collapse
So, here are the results:
Code:
>fastboot devices
afb25fe8 fastboot
Code:
>fastboot oem unlock
...
OKAY [ 0.011s]
finished. total time: 0.011s
The OPO rebooted and then fastboot mode again:
Code:
>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
Any ideias?
Thanks!

Did you buy the phone directly from OPO? Or did you buy it from somewhere else? If so, where?
Transmitted via Bacon

Unlock & Tamper Bit
Have a look at this.
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

timmaaa said:
Did you buy the phone directly from OPO? Or did you buy it from somewhere else? If so, where?
Transmitted via Bacon
Click to expand...
Click to collapse
I bought the phone from OPO and I already opened a support ticket, but I know they take a long time to reply...

ultrawires said:
Unlock & Tamper Bit
Have a look at this.
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
I read every post of that topic, but it seams that to use that mod it's necessary to have the bootloader unlocked or to temporary boot into a custom recovery...and I can't do neither.

Temp recovery mode is from fastboot.
Get into fastboot mode, connect to PC. From PC, enter
fastboot boot <recovery.img>
You'll need the recovery.img file in you PC. That'll get you into temp recovery mode.

[Q] Stock Nexus S stuck on Google logo: is it possible to recover the data?

Hi guys,
I know it sounds like one of many threads already created here.
I have read a bunch of them and the information sounds a bit contradictory or at least I'm unsure.
My Nexus S i9020 has sunk in salt water. I washed it in distilled water then gave it two weeks in a dry, warm environment.
When I try to turn it on I see a menu which is asking do I want to unlock a bootloader or not.
While on Power + Volume Up I can get into recovery menu. When I choose reboot I can see a Google logo with no progress. Pressing the Power button doesn't turn the phone off so I have to take the battery out. But power off through the menu works fine.
I installed necessary drivers / bits of SDK on Windows 7. ADB doesn't see the phone but fastboot does, so I can turn the phone off or can try to reboot it from PC. Looks like USB debugging is off.
Now the question is: can I actually turn it on without unlocking a bootloader? Can I _run_ CWM without unlocking a bootloader?
If not are there other options to turn USB debugging on?
If there are no options and I have to unlock a bootloader, would it 100% kill the data on memory card?
If it will is there any chance to restore it afterwards? If so, how can I do that?
Or should I just forget about it?
Thank you!

First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!

demkantor said:
First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!
Click to expand...
Click to collapse
Hi demkantor,
Thanks a lot for reply!
Before I kill it completely... :cyclops: How do I find out which image I need to download?
I obviously need 4.1.2 one but do I need "soju" for Nexus S (worldwide version, i9020t and i9023) or "sojua" for Nexus S (850MHz version, i9020a)?
The phone I have is the UK version, as far as I remember (I'll double check it later) there was just i9020 on the phone, no other index.
Any ideas about this? Can device ID help here?
And after that the only thing I have to do would be:
> fastboot flash system system.img
> fastboot flash boot boot.img
> fastboot reboot
Am I right?

https://developers.google.com/android/nexus/images?csw=1
More than likely soju, since you can't get to about phone to check maybe it will say under battery or if you have original box?
And yes those are the correct commands
Best of luck!

Hi demkantor,
This is what I see in fastboot mode:
PRODUCT NAME - HERRING
HW VERSION - REW 11
BOOTLOADER VERSION - I9020XXLC2
BASEBAND VERSION - I9020XXKI1
CARRIER INFO - EUR
According to android-info.txt from soju-jzo54k-factory-36602333.tgz everything is fine so i downloaded it, extracted system.img and boot.img and tried to flash them with fastboot.
Unfortunately I got this:
C:\android-sdk-windows> fastboot flash system system.img
sending 'system' (337443 KB)... OKAY [ 53.034s]
writing 'system'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 53.035s
C:\android-sdk-windows> fastboot flash boot boot.img
sending 'boot' (3964 KB)... OKAY [ 0.621s]
writing 'boot'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.622s
Looks like whatever I want to flash I still have to unlock the bootloader. Any other ideas?
Can I boot into CWM without flashing and turn USB debugging on from there?

You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)

demkantor said:
You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)
Click to expand...
Click to collapse
Yep looks like it is very unlikely that I will be able to do it without unlocking. I've seen a thread somewhere where the guy was in the same situation and he had to unlock the bootloader but after that was able to restore the data.
Okay then, I'll dig on this a bit more and then try it out. Thanks a lot!

Okay. So finally I had to try unlocking a bootloader and flashing the phone with flash-all.bat script.
The log looks like this
Code:
c:\android-sdk-windows\soju-jzo54k>flash-all.bat
sending 'bootloader' (1536 KB)... OKAY [ 0.241s]
writing 'bootloader'... OKAY [ 0.355s]
finished. total time: 0.597s
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)... OKAY [ 1.925s]
writing 'radio'... OKAY [ 1.740s]
finished. total time: 3.665s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: SERIAL
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3964 KB)... OKAY [ 0.620s]
writing 'boot'... OKAY [ 0.520s]
sending 'recovery' (4308 KB)... OKAY [ 0.674s]
writing 'recovery'... OKAY [ 0.565s]
sending 'system' (337443 KB)... OKAY [ 52.764s]
writing 'system'... OKAY [ 37.667s]
erasing 'userdata'... OKAY [ 0.185s]
erasing 'cache'... OKAY [ 1.999s]
rebooting...
finished. total time: 95.001s
After rebooting the phone I got the same problem i.e. it's stuck on Google logo. The same result I get when I insert the battery while the phone is unplugged from PC. But if I press Volume Up + Power (while disconnected from PC) I get a yellow triangle and the text "Downloading... Do not turn off the target".
Data is lost. Fine. Any ideas what could be done in order to make the phone bootable?

Try wiping through fastboot and then flashing the images one by one (instead of the flash all.bat)
This may help
http://forum.xda-developers.com/showthread.php?t=2277112

[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