Related
I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.
Guticb said:
I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.
Click to expand...
Click to collapse
Try this link for access to recovery or apx.
No luck. The tablet literally doesn't have a recovery at all. Trying to flash any stock ROM through fastboot results in failure.
Every time I try, command prompt gives me the error FAILED (remote: (InvalidSize)) and my tablet does the "Failed to process command flash:system error(0xa)" message
I'm not sure if any flashes through fastboot are even working right. It says success, but the reboot command never works (Even though that says success, too)
Have you tried reflashing your recovery then installing a stock rom from there?
Guticb said:
No luck. The tablet literally doesn't have a recovery at all. Trying to flash any stock ROM through fastboot results in failure.
Every time I try, command prompt gives me the error FAILED (remote: (InvalidSize)) and my tablet does the "Failed to process command flash:system error(0xa)" message
I'm not sure if any flashes through fastboot are even working right. It says success, but the reboot command never works (Even though that says success, too)
Click to expand...
Click to collapse
No fastboot, no recovery, no apx backup
Sell it for parts
Lcd
Digitizer
Battery
Etc
Or buy a new mobo
Envoyé depuis mon ASUS Transformer Pad TF300T avec Tapatalk
lightitwithfire said:
Have you tried reflashing your recovery then installing a stock rom from there?
Click to expand...
Click to collapse
Yeah. No luck. It'll say success, but the tablet freezes and the reboot command doesn't work. After I manually reboot, no luck either.
I've looked up some information about it. People who experience the same problem (not able to get into recovery, adb, etc) had to send their tablet into Asus and it got shipped to Czech Republic, then in about 3 weeks it's returned ready to go. Maybe that's a possible route? If not, search xda-developers deeper and check out transformerforums. They have alot of stuff linked to XDA so who knows, maybe what you're looking for is on there.
Best of luck to you!
Guticb said:
Yeah. No luck. It'll say success, but the tablet freezes and the reboot command doesn't work. After I manually reboot, no luck either.
Click to expand...
Click to collapse
Which recovery do you flash
Jb or ics version
Cwm or twrp
Envoyé depuis mon ASUS Transformer Pad TF300T avec Tapatalk
dont waste more time
As i posted somewhere else, this tablet is a pretty bad purchase.
I bricked mine without unlocking bootloader, without flashing anything, without even connecting it to the computer.
One day it got stuck in asus screen.
After hard reset, recovery and wipe data i was left out with a brick. (no more snk, usb, wipe data screen)
Interesting you can brick a tablet without doing all those things they warn you not to do.
Dont waste more time looking for a solution. theres none, your tablet is now a useless brick.
sell it to someone who needs the parts.
gomezdf said:
As i posted somewhere else, this tablet is a pretty bad purchase.
I bricked mine without unlocking bootloader, without flashing anything, without even connecting it to the computer.
One day it got stuck in asus screen.
After hard reset, recovery and wipe data i was left out with a brick. (no more snk, usb, wipe data screen)
Interesting you can brick a tablet without doing all those things they warn you not to do.
Dont waste more time looking for a solution. theres none, your tablet is now a useless brick.
sell it to someone who needs the parts.
Click to expand...
Click to collapse
Wow, that's really weird. Hard to believe that it just bricked itself one day. Since it was never unlocked, did you take advantage of the warranty and say it was a manufacture defect?
Guticb said:
I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.
Click to expand...
Click to collapse
I had the same issue although it stemmed from a different origin. I'm guessing it won't reboot on its own because you've wiped the /system files. Can you still connect to your PC using fastboot? If yes, try the command "fastboot -w", then try fastbooting the stock ICS blob file. By the way, I'm still new to the Android platform but I've learned quite a bit in the last few weeks by tinkering with my two Android devices and soft-bricking them several times in the process.
A
I had the same problem, and my understanding is that it stems from a messed up bootloader. Literally, I had the -exact- same error messages so I know what you are going through.
Fortunately, I was able to use NVFlash to recover mine. I don't know what other solution there would for you, my friend. Best of luck, let us know what ASUS charges for the repairs if you decide to go that route.
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.
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.
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).
OnePlus 7 Pro was running 10.3 . Was rooted with Magisk, bootloader is currently unlocked (though it locked after an attempt with MSM Download Tool.)
Through a series of increasingly unfortunate choices, my phone will only go to the bootloader screen. While it receives commands from adb or Tool-in-One, those always result in a reboot and back to the bootloader. I was able at one point to use the MSMDownload Tool on it, even though I'm not clear at all what the various choices on that tool mean. It did appear to successfully clear the phone, but I was unable to install TWRP and a stock rom. (I do have a TWRP backup but we're not even close to being able to use it.)
Right now I can't get the MSM tool to recognize the phone; the phone will not turn off. As soon as it is "off", it boots right back to bootloader screen. I've held every combo of buttons and I can get it to go off for a second, then immediately reboot. So far I have been unsuccessful getting the tool to be useable again.
EDIT: Further info. Used flashall with a fastboot rom, all appeared to go successfully, but still only boots to fastboot. I used the Tool in One to flash a TWRP recovery, and each time get the error: Booting TWRP...
Sending 'boot.img' (31440 KB) OKAY [ 0.679s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Waiting the TWRP boots...
And I remain stuck at Fastboot . Thanks again for any help
Any suggestions for help would be much appreciated.. Without a phone, this quarantine stuff (I'm in NYC) is 100X worse.
Thank you.
Further edit: Appears to me that perhaps when I used the MSM tool, it took me back to an OOS earlier than OOS 9.5.4 GM21AA , which apparently will not accept the "fastboot boot" command. Now what? (Apparently OOS 9.5.4 GM21AA is where OnePlus fixed this bug.)
BeachNYC said:
OnePlus 7 Pro was running 10.3 . Was rooted with Magisk, bootloader is currently unlocked (though it locked after an attempt with MSM Download Tool.)
Through a series of increasingly unfortunate choices, my phone will only go to the bootloader screen. While it receives commands from adb or Tool-in-One, those always result in a reboot and back to the bootloader. I was able at one point to use the MSMDownload Tool on it, even though I'm not clear at all what the various choices on that tool mean. It did appear to successfully clear the phone, but I was unable to install TWRP and a stock rom. (I do have a TWRP backup but we're not even close to being able to use it.)
Right now I can't get the MSM tool to recognize the phone; the phone will not turn off. As soon as it is "off", it boots right back to bootloader screen. I've held every combo of buttons and I can get it to go off for a second, then immediately reboot. So far I have been unsuccessful getting the tool to be useable again.
EDIT: Further info. Used flashall with a fastboot rom, all appeared to go successfully, but still only boots to fastboot. I used the Tool in One to flash a TWRP recovery, and each time get the error: Booting TWRP...
Sending 'boot.img' (31440 KB) OKAY [ 0.679s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Waiting the TWRP boots...
Will MSM detect your phone if you try this fastboot command?
Code:
fastboot reboot edl
And I remain stuck at Fastboot . Thanks again for any help
Any suggestions for help would be much appreciated.. Without a phone, this quarantine stuff (I'm in NYC) is 100X worse.
Thank you.
Click to expand...
Click to collapse
Will MSM detect your phone if you try this command?
Code:
fastboot reboot edl
Turn off your Phone.
Hold volume up (and down) sumultanious while connecting your Phone to a computer.
Settup the right drivers and use the msm tool to flash stock firmware. EVERYTHING WILL BE RESET!
than update to latest Version 10.x and try rooting again if you like.
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Otherwise... to me it looks like you have you dont have the right recovery installed. Try flashing the right Version for you current bootloader https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943 and try flashing the latest firmware via adb
I hope this helps.
Goodluck!