Database Info

[Q] Locked or Unlocked?, boot loop, bricked.

Ok so I unlocked and rooted the my TF700 but had not yet installed any new roms or recovery on it, I was getting round to that but other things to do etc. So one day the battery ran out and when I powered it up bleary eyed one morning it said it could not boot due to being encrypted. I had not encrypted it. So the only option I had was to wipe the device.
Done so back with a working device for some weeks. Then the other day I powered it off. When I powered it back on boot-loop, gets to the point of Asus inspiring inovation persistent perfection (yeah right).
No problem I thinks I'll just use fastboot to save the day because when I boot it says "Device Unlocked" and I can get to the RCK/ANDROID/WIPE screen. So run fastboot and it says it writes to the device but I don't believe it as the copying of an image takes ~130seconds and the writing 0.094s.
So I think I am in this half-locked limbo and I am assuming there is no way out of this.
I've tried a stock rom on the sd card which gets up the Android with a spinning blue vector in his chest but this goes on for about 5 minutes and reboots again back to boot loop.
How did it get half unlocked and if its half unlocked then surely its not unlocked so how does that affect the warranty, I may just send it back and see what happens? I am annoyed because I had not got around to messing around with custom roms etc... I also thought it wouldnt OTA update I am guessing maybe this is what happened when it complained about the encrypted device.
I really am about to give up and use it for chopping onions, a very expensive chopping board.
Not sure if anyone has any bright ideas but I'm all out...

Slarty Bartfast said:
Ok so I unlocked and rooted the my TF700 but had not yet installed any new roms or recovery on it, I was getting round to that but other things to do etc. So one day the battery ran out and when I powered it up bleary eyed one morning it said it could not boot due to being encrypted. I had not encrypted it. So the only option I had was to wipe the device.
Done so back with a working device for some weeks. Then the other day I powered it off. When I powered it back on boot-loop, gets to the point of Asus inspiring inovation persistent perfection (yeah right).
No problem I thinks I'll just use fastboot to save the day because when I boot it says "Device Unlocked" and I can get to the RCK/ANDROID/WIPE screen. So run fastboot and it says it writes to the device but I don't believe it as the copying of an image takes ~130seconds and the writing 0.094s.
So I think I am in this half-locked limbo and I am assuming there is no way out of this.
I've tried a stock rom on the sd card which gets up the Android with a spinning blue vector in his chest but this goes on for about 5 minutes and reboots again back to boot loop.
How did it get half unlocked and if its half unlocked then surely its not unlocked so how does that affect the warranty, I may just send it back and see what happens? I am annoyed because I had not got around to messing around with custom roms etc... I also thought it wouldnt OTA update I am guessing maybe this is what happened when it complained about the encrypted device.
I really am about to give up and use it for chopping onions, a very expensive chopping board.
Not sure if anyone has any bright ideas but I'm all out...
Click to expand...
Click to collapse
Sorry, from your description I don't quite get what exactly you did. What did you try to write with the fastboot command? To me your problem sounds like a bootloader problem.
I understand you still have fastboot access to your device? If so, I'd suggest to follow the steps described here at "Scenario Two":
1. Load a custom recovery, e.g. TWRP with the fastboot method.
2. Download the recovery + bootloader package as described in the CROMi-X thread.
3. Boot into recovery and flash that package.
If you get to this point you should be able to flash any custom (JB based ROM), recommend the CROMi-X.
Hope this helps!

FordPrefect said:
Sorry, from your description I don't quite get what exactly you did. What did you try to write with the fastboot command? To me your problem sounds like a bootloader problem.
I understand you still have fastboot access to your device? If so, I'd suggest to follow the steps described here at "Scenario Two":
1. Load a custom recovery, e.g. TWRP with the fastboot method.
2. Download the recovery + bootloader package as described in the CROMi-X thread.
3. Boot into recovery and flash that package.
If you get to this point you should be able to flash any custom (JB based ROM), recommend the CROMi-X.
Hope this helps!
Click to expand...
Click to collapse
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.

Slarty Bartfast said:
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Click to expand...
Click to collapse
ok, thanks for the clarification. However, that is exactly what I would have done ... you have checked the download file and fastboot seems to transfer it. From then on you should be able to boot into recovery.
Forgive me please for a dumb question ..but have you tried to boot the "classic" way? Like switching the device off and then power on with the Volume minus key pressed? Other than this, I am sorry but I don't have any further suggestion

Slarty Bartfast said:
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Click to expand...
Click to collapse
Some things about your fastboot commands are very interesting..
First, what was the operating system that you were using. Second, your recovery name is not the same as you tried to fastboot with the command. Third, I think that you may do something incorrect with fastboot because your bootloader is fine and please be careful with your bootloader. If something is wrong with your bootloader, it is hard to bring it back unless you have your NVflash blobs... Last, you are still with the stock recovery and did not have a custom recovery installed yet.. Also, it seems that you have a bootloop. Any way, I think that you are still good depending on what you want to do with your device...

LetMeKnow said:
Some things about your fastboot commands are very interesting..
First, what was the operating system that you were using. Second, your recovery name is not the same as you tried to fastboot with the command. Third, I think that you may do something incorrect with fastboot because your bootloader is fine and please be careful with your bootloader. If something is wrong with your bootloader, it is hard to bring it back unless you have your NVflash blobs... Last, you are still with the stock recovery and did not have a custom recovery installed yet.. Also, it seems that you have a bootloop. Any way, I think that you are still good depending on what you want to do with your device...
Click to expand...
Click to collapse
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.

Slarty Bartfast said:
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Click to expand...
Click to collapse
Your finished times are way too fast - mine are 10 times this so I suspect it hasn't written the recovery blob correctly. Did you notice it put a blue time bar on the screen when doing the write?

sbdags said:
Your finished times are way too fast - mine are 10 times this so I suspect it hasn't written the recovery blob correctly. Did you notice it put a blue time bar on the screen when doing the write?
Click to expand...
Click to collapse
Yes I noticed that in comparison to other peoples output that it is too quick.
No there is no blue time bar put on the screen. After you fastboot the recovery the green block that pulses on the selected option RCK for example, stops pulsing and then I have to pinhole reset.
I am thinking that the unlock didn't correctly unlock the device orthe time it would not boot requiring a data wipe because it said the device was encrypted, I guess somehow it got an OTA although it shouldn't have received one. But I cant understand how the unlock could be reverted because the consensus is it cannot.
If the unlock didnt work I may try an RMA on the grounds that its not properly unlocked therefore the T&C for unlocking is not really valid as I would have expected to have an unlocked device.

Slarty Bartfast said:
Yes I noticed that in comparison to other peoples output that it is too quick.
No there is no blue time bar put on the screen. After you fastboot the recovery the green block that pulses on the selected option RCK for example, stops pulsing and then I have to pinhole reset.
I am thinking that the unlock didn't correctly unlock the device orthe time it would not boot requiring a data wipe because it said the device was encrypted, I guess somehow it got an OTA although it shouldn't have received one. But I cant understand how the unlock could be reverted because the consensus is it cannot.
If the unlock didnt work I may try an RMA on the grounds that its not properly unlocked therefore the T&C for unlocking is not really valid as I would have expected to have an unlocked device.
Click to expand...
Click to collapse
I seriously doubt your arguments will get you anywhere with Asus since they don't support unlocking, but I've never heard of a "partial unlock". Either it works or it fails.
I suspect your problem is related to "bleary eyed", the encryption and data wipe you did. Or a driver issue on your PC.
If you cannot install a custom recovery via fastboot, I would try to flash the stock firmware and start at square 1.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

Slarty Bartfast said:
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Click to expand...
Click to collapse
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:

LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot...
Click to expand...
Click to collapse
Are you sure? The bootloader mounts the /data partition to read some Android setting? Does not look plausible to me.

LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
Click to expand...
Click to collapse
Thats a good question, I would have thought so (always do for everything else) but now you mention it. I can't say for sure. And it won't accept the stock recovery from sd card, 5 minutes of spinning blue thing in chest then reboot into boot loop...
Is it time to start chopping onions?

berndblb said:
I seriously doubt your arguments will get you anywhere with Asus since they don't support unlocking, but I've never heard of a "partial unlock". Either it works or it fails.
I suspect your problem is related to "bleary eyed", the encryption and data wipe you did. Or a driver issue on your PC.
If you cannot install a custom recovery via fastboot, I would try to flash the stock firmware and start at square 1.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thats the wierd thing, I did not encrypt the tablet, just discovered it with the green android telling me it needed to do a full data wipe because the tablet was encrypted, I've never encrypted any of my android devices. After this process it worked fine again. Then last time I powered it off it came back up in a boot loop.
I've put the stock firmware on an sd card and the it spins for a few minutes 3 or so then reboots into boot loop.

Slarty Bartfast said:
Thats a good question, I would have thought so (always do for everything else) but now you mention it. I can't say for sure. And it won't accept the stock recovery from sd card, 5 minutes of spinning blue thing in chest then reboot into boot loop...
Is it time to start chopping onions?
Click to expand...
Click to collapse
Well, I can kind of confirm this. Without having done scientific research, but recently I fought my fastboot connection as well. It turned functional only after I checked the USB debugging thing.

_that said:
Are you sure? The bootloader mounts the /data partition to read some Android setting? Does not look plausible to me.
Click to expand...
Click to collapse
That was how I learned to fastboot. I never have problem with fastboot. I can do a test for you when I fastboot twrp 2.6.3.1 without usb debugging..
Edit: @_that
You are an expert in this area. Do you have any good advices for someone in need? Do you know why some users can not flash anything even though they follow the instructions closely? It would be nice if you can share your knowledge with new users like us...

LetMeKnow said:
That was how I learned to fastboot. I never have problem with fastboot. I can do a test for you when I fastboot twrp 2.6.3.1 without usb debugging..
Click to expand...
Click to collapse
Would be interesting.
LetMeKnow said:
Edit: @_that
You are an expert in this area. Do you have any good advices for someone in need? Do you know why some users can not flash anything even though they follow the instructions closely? It would be nice if you can share your knowledge with new users like us...
Click to expand...
Click to collapse
The real experts in this area are those who brought you wheelie and flatline... for me it looks very confusing. The twrp.blob md5sum matches mine, and I don't understand why it finishes so fast, says "OKAY" but doesn't work. If there was a problem with the fastboot protocol or with writing to flash memory, I'd expect some error message. Anyway, maybe try a different/newer fastboot binary or another USB port or another PC? I assume it's Linux on the native machine and not a VM?
I've seen a bootloader which would not flash anything in the case where someone cross-flashed a TF300 bootloader on the TF700, but I assume the OP has never tried such a crazy thing. Check the bootloader version, it should be 10.6.1.14.x.

LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
Click to expand...
Click to collapse
Like this
http://www.youtube.com/watch?v=q53_9tuD5HA
Next thing I ****ing know some arse is ****ing defending ASUS. Total Fanny boys.Dont help me much.May as well cut ****ing onions.

Slarty Bartfast said:
Like this
http://www.youtube.com/watch?v=q53_9tuD5HA
Next thing I ****ing know some arse is ****ing defending ASUS. Total Fanny boys.Dont help me much.May as well cut ****ing onions.
Click to expand...
Click to collapse
Wow nice response to people trying to help you.......

sbdags said:
Wow nice response to people trying to help you.......
Click to expand...
Click to collapse
I agree. Figured some people prefer failing over learning.
Enjoy your new cutting board. Should work great on peppers too. Probably will last you longer screen down - just some friendly advice....

sbdags said:
Wow nice response to people trying to help you.......
Click to expand...
Click to collapse
Indeed. Seemed like a good idea at the time. Fed up with this rubbish now, gpl'd but still managing trying to foist essentially drm on it. I think what annoys me most is the insidious and slow corruption of the ideal. Must say its partly my own fault, i have stood by and done nothing.
Apologies anyway.
Think I'll buy a Rasberry Pi.

Motorola Photon Q - Crashing all apps, can't erase or flash anything

Good day, its my first thread here, so I'm sorry for my english and terminology.
My Photon Q had CM-13-Nightly installed, bootloader unlocked and Clockwork recovery installed. Everything was working fine, till few days ago. Phone was left unused with drained battery, so I charged it and powerd on. After that, all app started to crash one after another. I was trying to do factory reset from recovery, erase everything from bootloader menu or using bootloader commands (bootloader erase data, bootloader -w) but nothing worked. I still have my system, with same apps, wallpaper etc and apps still crash. Are these all symptoms of damaged partition or internal storage? Will be thankful for any help

Erasing in bootloader/fastboot mode can be dangerous... be careful.
I would just factory reset and reinstall the ROM. Don't use ClockworkMod for recovery tho, use TWRP. CWM hasn't had updates in a long time (and frankly I'm surprised it was able to flash the latest CM).

I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery

greedo85 said:
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
Click to expand...
Click to collapse
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?

I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
HTML:
C:\fastboot>fastboot flash recovery twrp-2.3.0.0-asanti_c.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6702 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 1.786s]
finished. total time: 2.298s
arrrghhh said:
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
Click to expand...
Click to collapse

greedo85 said:
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
Click to expand...
Click to collapse
I think you can safely ignore the bootloader message.
As for flashing TWRP, did you boot TWRP immediately after flashing, or did you boot Android?
I believe you need to make sure you boot TWRP immediately after flashing, otherwise CM Recovery will blow it out.
After flashing TWRP hold power until the device shuts off, release, and now hold power + vol down to enter recovery. Please use the latest version of TWRP from kabaldan, or the latest official TWRP.

I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think

greedo85 said:
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
Click to expand...
Click to collapse
Sorry it's power + vol UP (according to my own guide...)
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!

Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?

greedo85 said:
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
Click to expand...
Click to collapse
I'm not sure why people have issues with this... I always thought it was how they 'completed' the flashing process. I don't recall being able to reproduce the condition.
Perhaps boot Android then boot TWRP? Or try to reboot directly to recovery from the fastboot cli? Try something different... or just fastboot boot the TWRP image? There is a problem in the process, I'm just not sure 'where' since I don't have the phone in front of me.

Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?

greedo85 said:
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
Click to expand...
Click to collapse
IIRC this device will let you 'fastboot boot' images directly - I think I suggested this - have you tried it?
I'll dig around and see what else I can find from the TWRP thread. I was pretty sure it had to do with the process, but I could be mistaken.
Edit - I'll flash CM Recovery on my old Q and see if I can recreate this as well. It's always bothered me...

How would I boot images directly? From where?

greedo85 said:
How would I boot images directly? From where?
Click to expand...
Click to collapse
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...

arrrghhh said:
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
Click to expand...
Click to collapse
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s

greedo85 said:
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
Click to expand...
Click to collapse
I guess they only allow fastboot booting kernels... at least I used to do that on this device.
So I just flashed CM Recovery no problem. Going to flash back TWRP.

Is there anything I can do now to put this phone back to work?

greedo85 said:
Is there anything I can do now to put this phone back to work?
Click to expand...
Click to collapse
I'm... kind of at a loss. Make sure you have the latest TWRP. I just downloaded the latest CM Recovery, fastboot flash recovery <cmrecimg> and it rebooted to Android on its own. I reboot to recovery, CM Recovery is installed. All good.
I reboot to bootloader mode, grab the latest official TWRP, fastboot flash recovery <twrpimg>, this time when I unplugged it was still in fastboot mode. So I hit the power button, phone turns off. Then I hold power + vol up until I see the screen turn on. Continue to hold vol up, but release power. Then when the screen dims (or when recovery starts if you can't tell) release vol up.
Maybe that'll help you? Good luck.

Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?

greedo85 said:
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
Click to expand...
Click to collapse
Dunno why it would make any difference at this point, but have at it.

Fastboot no Recovery Flash

655/5000
Hello everybody,
I have a small or big problem.
I wanted to flash a new ROM. Unfortunately, I can not flash the TWRP.
Each time:
PHP:
C: \ Users \ Marcel \ Downloads \ adb 1.0.36 and fastboot> fastboot flash recovery twrp-3.1.1-0-frd.img
Target reported max download size of 471859200 bytes
Sending 'recovery' (25184 KB) ...
OK [0.544s]
Writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. Total time: 0.557s
In Fastboot mode, PHONE is unlocked (in red) and FRP lock (in green). Does the FRP have anything to do with it?
Since then I can not use the Honor Recovery. He wants to download something, but that does not work.
Also with the "dload" upgrade he makes a rebootart and the Screen " YOur devices is booting now..."
Can anyone give me a hint?

It's the FRP lock. Delete all the Google accounts on your phone, that should free up the FRP lock and let you flash recovery.

Hello,
Thank you very much. About settings I could disable the FRP.
FRP and Phone ist UNLOCK.
TWRP I can copy. About the one Huawei multitool I came 1 time in the recovery mode. There I made a wipe. The installation of the new Custom Rome did not work (Error Code 7).
Now I'm only in the fastboot mode. In the TWRP I come no more pure.
The mobile phone is constantly running again.
It is not recognized in the Huawei Multitool. From the console (cmd) I can use fastboot mode.
How can I save it?

I've never used the multitool, so I can't help you there. I always flash directly from ADB.

Via the cmd I can copy the recovery (twrp). But if I want to restart the devices, the twrp does not start. Therefore, I try the tool.
It is very annoying that you can not just start the twrp.
Also delete or copy system, boot, etc is not (FAILED (remote: Command not allowed))

Use the button combo to get into TWRP. Power the device off, then hold down Power + Vol Up. When you feel the short vibrate, let go of power, keep holding Vol Up. It should boot you into TWRP.

many thanks for the help. Apparently I must be too stupid for it.
I have only 2 options.
1. Volume down (-) with power to fastboot mode.
2. Volume high (+) (the topmost pressure point (head)) with power. Here I get into the overview:
Your devices has been unlocked and can't be trusted.
(1) Presspower key to continue
(2) Press VOlumen Up key to 2 Secondary to restore your device.
(3) Your devices will continue to boot 5 seconds later if there is no operation
No matter how, it always stands YOur devices is booting now ...
After a few minutes he makes a reboot
EDIT: After I have done the Unbrick with the tool, the mobile phone starts again. But if I install TWRP or get to use, then it is only version 3.0.2.0

File/picture recovery from freezing Pixel - debugging enabled, original bootloader

I would REALLY appreciate help if possible. I'm trying to recover my honeymoon pictures from a Pixel that freezes as soon as it boots.
It has the locked, original bootloader, but debugging is enabled. Sailfish Oreo 8.1.0/OPM1.171019.012/4470837 installed.
I thought after enabling debug that I could adb shell or adb pull files in recovery mode, but I can't figure out how (assuming it's possible). I can boot into "no command" recovery, and get into the Android Recovery menu with "Apply update from ADB", "Mount /system", etc. I've even upgraded the OS with adb sideload successfully...
But booting into Android, it freezes almost always on the "G" loading screen...but rarely, it will display the clock and notifications and immediately freeze. Even more rarely (like once in a thousand boots), it will give me maybe 10 seconds before it freezes. The last time it did this, I had just enough time to enable dev options, enable debugging, and "always enable with this computer"...then it froze.
What are my options or the most likely way to recover my files? Is there anything I can do from recovery, or if I get another 10 seconds in Android, is there anything I should try?

Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning

KittyRgnarok said:
Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning
Click to expand...
Click to collapse
Thanks for the suggestion! I'll try this tonight, but I worry it won't work since my bootloader is the original and locked. If I understand correctly:
- you need an unlocked bootloader to do "fastboot boot"
- you have to factory reset and wipe all your files to unlock the bootloader
Is that not true?

Yes, it looks like I can't "fastboot boot" because it's not unlocked. Everything I've found says unlocking should wipe my device.
Is there any way to boot an img or get to adb shell/pull without wiping it?
Code:
>>> fastboot boot twrp-3.2.1-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.868s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.967s

Oh yeah I forgot about that. Uhhhhh no I think ur boned sorry

are you sure you did not have google photos automatically backing up your photos?

mruno said:
are you sure you did not have google photos automatically backing up your photos?
Click to expand...
Click to collapse
Yes, I'm sure. I was away from any connection on my honeymoon and it crashed right before coming home.

If your phone is under warranty still you can likely RMA it to get a phone that isn't bootstuck but as far as the data I think it's pretty safe to say you can't access it unless you have already disabled forced full disk encryption prior(which I'm not even sure is safe to do on these devices).

Nvidia Shield Tablet OEM Unlock

Ive scoured the web for the solution to this but for the life of me can not get my boot loader to unlock. I know enough of this to get me by, but obviously I am not an expert by any means. This is one of the pre recall tablets that I had rooted to avoid the kill code. It was so long ago when I did this that I don't completely remember how I did it. But apparently I didn't have to unlock the bootloader to root it.
I haven't used this tablet in ages and decided to pick it up again but was getting errors that I needed to update google play services but it was not allowing me to do so. I have the Custom Rom Blisspop installed but it appears that they have quite support for it. So I was going to wipe that off and load Lineage. so I tried to get into recovery and it kept just stalling at the loading screen. So now I am wondering if I even flashed a recovery to it to make a backup. Regardless I wouldn't want to restore and risk getting the kill code delivered.
So the next thing I tried to do was flash twrp (and yes I did use the NVidia shield tablet version) and it said that it was successful but still could not boot into recovery. Then I noticed that it said my bootloader was locked on the bootloader screen. So I installed the platform tools and the drivers and adb was recognizing my tablet and everything was good. Until.... I did "adb reboot bootloader" and then "fastboot devices" or even "fastboot oem unlock" nothing worked. No devices would show up. But this whole time adb works. No matter what drivers I install or anything, I cannot get fastboot to recognize the device. I even changed the USB port to the back of my pc straight off the mobo and ran the cmd as admin and nothing is working.
I am starting to get discourage that my efforts are going to be for naught. Expecially since I am not sure exactly how I rooted it in the first place? which is completely my fault for not documenting it. Any and all help is greatly appreciate and I apologize if this has already been solved else were or is being posted to an incorrect location.
Thank you!
Brandon

Ok, i finally figured out that the fastboot driver wasnt working. I ran "adb reboot bootloader" and while in fastboot mode, i found in the PC's device manager that there was an error with the driver. I manually updated it and i am finally able to successfully run "fastboot oem unlock".
But now im getting an error with it saying it failed....
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I am unsure what this means and will do some more researching. I will post back if i make any headway. Once again, i thank anyone in advance for any assistance they may be able to provide.

Apparently i had to unplug the tablet after installing the driver for fastboot before "fastboot oem unlock" would work. But it now says "Device = unlocked"!!!! hopefully i dont mess anything else up...

So now the tablet is "unlocked". I went to do "fastboot flash recovery twrp.img" and said it succeeded. I then proceeded to to do "fastboot reboot" and read that you should immediately load back into bootloader because some tablets will overwrite the recovery to stock if twrp isnt given a chance to correct this. So i did just that then volume keyed down to recovery and its back to doing the same thing where i am stuck on the nvidia logo loading screen. Does anyone have any suggestions on a fix for this? It appears that the tablet is refusing to enter recovery mode?
The reason why i need to get into recovery is for A: to make a backup. and B: to clear my current blisspop rom so that i can load a different Rom. I doubt it would be a good idea to install an OS on top of another OS. But who knows, maybe thats fine?
Code:
C:\Users\bwach>fastboot flash recovery twrp.img
target reported max download size of 570425344 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.579s]
finished. total time: 1.015s
C:\Users\bwach>fastboot reboot
rebooting...
finished. total time: 0.004s
Once again, I thank you for the help.

I was up all hours of the no ight last night trying to solve this with no luck. Is there anyone here who might be able to help me?

Still can't get recovery to load... Tried everything. I did "fastboot - w", I tried flashing lineage on top of bliss pop. Nothing I do will give me access to recovery...
Any ideas?

You have to use hardware keys combination (power + volume + or - not sure exactly which) to boot to twrp for the first time after flashing. So hold the combination while you're still in fastboot (bootloader) mode and release when you see nvidia logo. Good luck
Edit : fastboot reboot is a command that takes you to system, not recovery, to reboot to recovery by using commands you habe to type fastboot reboot recovery. But still, I believe you have to enter for the first time using the buttons combination but it may work with fastboot reboot recovery

It's possible the bootloader is too old for the current twrp release to boot. Which version of android is on the tablet? If it's like L, then you'll have to either update the bootloader manually or update stock first, then twrp will work. There's a note about this on the twrp device page.