Related
Hi there. I was fooling around with my TF300T (I was foolish at some point, probably) and managed to install Jellybean using this method. It started working fine. So it did that I restored my files using Titanium Backup Pro, installed from the App store right after the first boot. The apps/data I restored with Titanium Backup, as far as I can remember, were mostly games and Dolphin stuff, nothing directly related to system, as far as I know.
After this backup restoration, I used the tablet a little more, played the games to check if my progress was not lost and all that. It worked, Angry Birds at least had all the levels I completed before yet marked as completed after restore the procedure.
So far so goo... no! For some reason I can't remember I restarted the tablet, at least I tried! It got stuck on the loading screen (the white Asus, not the shiny one). So, after that I tried to restore it again, and then I probably did something completely stupid and I can't even remember what.
I even tried superwipe on it, but that didn't work neither.
At this point my tablet let me flash recovery image, CWM and TWRP. I can use adb shell with CWM but not with TWRP.
For some reason, I don't know, when I use CWM it doesn't mount /sdcard, TWRP seem to be mounting it, but go figure, I can only access the /sdcard that TWRP mounts using TWRP, if I change the recovery to CWM for some bizarre (or obvious to you guys) reason, I can't mount it.
And no matter what recovery I use, I can't flash any ROM. Both recovery tells me it was flashed, no error message (at least not at the screen) but every time it reboots to finish the installation, I see the Asus logo with a progress bar that goes from 0% to 100% in less then one second, and once it's filled, the tablet reboots itself and show me the regular boot screen with the Asus logo (again, the white one, not the silver-shiny).
So, resuming my problem, I can fastboot and adb shell it (adb only with ClockWorkMod Touch), but flashing doesn't seem to work. And I believe the internal memory/storage structure have been compromised.
How do I fix this?
Here is what I did to fix it
brbjr said:
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Click to expand...
Click to collapse
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.
Man you saved my life. Thank you very much!
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Itege said:
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Click to expand...
Click to collapse
You're welcome!
Now click thank you so you can help me
I recommend you to use the CleanROM 2.5, it's stable and fast! Really fast! Faster then the ASUS Stock ROMs. I'm really enjoying it.
Still can't flash ROMs
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
poisondminds said:
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
Click to expand...
Click to collapse
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
allram said:
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
Click to expand...
Click to collapse
For CleanROM he'll need a specific TWRP version. It's better give CleanROM thread a read before install it.
allram said:
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. 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))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Guticb said:
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. 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))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Click to expand...
Click to collapse
1. Please, make sure the Tablet is the only one Android device connected to your computer
2. The bootloader is unlocked, right?
3. It's not the matter (almost impossible to be the case), but what are you using as recovery, TWRP or CWM?
4. Are you trying to flash the Official ROM?
- Sent from the Future, using my Delorean
- Enviado do Futuro, usando meu Delorean
mizifih said:
Originally Posted by brbjr View Post
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Quote:
Originally Posted by manegonzalez View Post
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
This is an awesome fix, thought I was buggered with a tablet that couldnt mount anything, couldn't get into download mode, recovery was fubared.. and then I stumbled on this
THANK YOU
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.
Hi!
So my Nexus 5 ran into a problem. In the morning it worked fine and I shut it off when I came to school. When I tried powering it back on it showed the PIN entry screen but soon shut off. I tried turning it back on for a couple of times and it showed just that boot animation with color circles. But every once in a while the screen turned white and then continued with the animation. It looked like it was missing a frame or something. Now it just won't boot to Android. It shows the Google logo but it stays there. If it is unplugged it will shut off soon, but if it is connected to my computer it is just stuck there.
I can access TWRP 2.6.3.4 I have on my phone through fastboot but that's kinda it. I searched for a while and found the best thing to do is to restore the phone. But first I want to do a backup (I don't have any, but I will have them from now on). I have some photos on my phone I want to keep. Here comes the next problem: I am unable to do a backup. When I tap backup in TWRP I have checked System, Data and Boot. I slide to back up but it shows some errors:
Updating partition details...
E: Unable to open '/cache/recovery/.version
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/persist'
E: Unable to mount '/firmware'
E: Unable to mount '/system'
* Total number of partitions to back up: 3
* Total size of all data: 2651MB
* Availible space: 14544MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/04
E: Unable to create folder: /data/media/0/TWRP
E: Failed to make backup folder.
The last three lines, except the last one are cut off (I think). If I tap on reboot system shown under this windows it asks me if I want to install Super-SU as if I wasn't rooted. It says so.
So, what to do? I want to keep everything the same (settings, apps, photos...) I have music on my computer so I don't need to back it up. Is that possible? What seems to be the problem?
I am running Android 4.4.2 Kitkat on my Nexus 5 32gb from Canada. I live in Europe and my uncle from Canada bought it, so warranty is no good for me.
First of all clear cache/dalvic cache and try rebooting the phone and see whether OS is booted or not. If that doesn't help, flash the lastet Philz touch recovery and see whether the partitions are being mounted or not...
Since you're able to get to the bootloader, it's a soft brick.. .
Ok, thanks... I am pretty new to android I have no idea how to clear cache. Do I go to wipe then to advanced wipe and check cache and dalvik cache and wipe it so? What if I also clear data? Does that delete everything on my phone?
Edit: So I did that. It says wipe was successful. Here is the log:
Updating partition details...
E: Unable to open '/cache/recovery/.version'
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount '/firmware'
My phone still only shows the Google screen and turns off soon (10 seconds or so). What is that Philz thingy?
hofko said:
Ok, thanks... I am pretty new to android I have no idea how to clear cache. Do I go to wipe then to advanced wipe and check cache and dalvik cache and wipe it so? What if I also clear data? Does that delete everything on my phone?
Click to expand...
Click to collapse
Go to mount and check the cache and data. Then go to Wipe>advanced wipe>dalvik cache and cache
and if u clear data it will clear the apps but not what is in the internal memory.
Edit- do as @rootSU is saying.
Sometimes a simple fastboot flash cache.img fixes it
Sent from my Nexus 5 using Tapatalk
rootSU said:
Sometimes a simple fastboot flash cache.img fixes it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So, how do I do that? I tried googling it for a bit and I find everything a bit confusing. I want to be sure what am I doing with my phone when it is in this state.
Edit: I tried what varuntis1993 said and it showed that boot animation and shut off. It did that only once. I don't know.
@hofko this thread may help.
hofko said:
So, how do I do that?
Click to expand...
Click to collapse
If you're rooted, you should already know how to do this as you use fastboot during the rooting process.
Read the stickies in general and q&a. Together they contain all the information you need
Sent from my Nexus 5 using Tapatalk
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
hofko said:
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
Click to expand...
Click to collapse
can u access ur internal memory using the file manager of twrp?
Try using adb pull
or u can also use an otg cable and copy and paste the folder to usb.
hofko said:
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
Click to expand...
Click to collapse
It is a dead flashchip. RMA it.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
It is a dead flashchip. RMA it.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
hofko said:
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
Click to expand...
Click to collapse
Have you used toolkit for rooting? Because it's always better to root it manually using fastboot commands than using toolkits.
Also try this tutorial but I highly doubt if its will work for you
http://forum.xda-developers.com/showthread.php?t=2577447
hofko said:
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
Click to expand...
Click to collapse
FAILED (remote: flash write failure)
I'm afraid this means that the flashchip has died. You could try flashing a new custom rom and see whether it boots or not, but I have my doubts.
Give it a few tries and in the mean time find a place where they repair the parts. If you give it to LG/google, they will most probably charge you for the whole mobo/battery which means you're better off buying a new device.
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
hofko said:
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
Click to expand...
Click to collapse
U said some of the files, so were some files copied?
No. None.
I am now trying to just flash stock Android using this guide http://www.droidviews.com/how-to-restoreunroot-nexus-5-by-flashing-factory-images/
When flashing the boot.img and system.img I got the same error I had before: FAILED (remote write failure). Everything else seemed okay. Now I am doing step 10 on the guide which is erasing the cache. This has been going on for quite some time and I presume I should just leave it do it's job as some people had some issues when ending this processby force.
What to do? I am getting a bit panicky.
hofko said:
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
Click to expand...
Click to collapse
Whatt???? That's great.
How about you start from scratch? does you device come up with adb devices ?
Is Platform-tools and usb driver correctly installed?
Since you can access storage from recovery, why don't you download a custom rom and transfer the rom to your device via OTG cable and flash it?
You can even backup your data using the OTG cable!
Post it to Canada and ask your Uncle to RMA it.
vin4yak said:
Whatt???? That's great.
How about you start from scratch? does you device come up with adb devices ?
Is Platform-tools and usb driver correctly installed?
Since you can access storage from recovery, why don't you download a custom rom and transfer the rom to your device via OTG cable and flash it?
You can even backup your data using the OTG cable!
Click to expand...
Click to collapse
Well I can try starting from scratch, but my Nexus has been erasing cache for almost an hour. Can I just stop that?
My OTG cable just doesn't work for some reason. I works on my Nexus 7 2012 version.
I am already in the process of reinstalling stock android so i don't really know if I even have twrp installed now...
rootSU said:
Post it to Canada and ask your Uncle to RMA it.
Click to expand...
Click to collapse
Will they do that? I mean I have unlocked bootloader and a rooted phone...
So I've had quite of a rough evening today, first of all: I'm not a rooting newbie, so I really thought I could work out all errors on my own.
Haven't rootet my GM1910 yet, so I wanted to do that. Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
After some trying around and not getting it to work, I tried using this to get the device working again:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
tried both flashall.zip and flash-all-partitions.zip.
Now I'm in the QUALCOM CRASHDUMP again with the message
"dm-verity device corrupted Force Dump
kernel_restart"
I've been looking through forms for hours but nothing seems to work for me (mainly the things I wrote above)
I'd really appreciate any help, kind of getting sweaty palms now
Maybe this? It's what I used to unbrick mine but I'm tmobile GM1915....
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Yup, thanks for the reply, that worked! I'm not trying to root my device anymore though :laugh:
Thanks for making my night sleepable today
If you're trying to root your device.. and you have a pc.. just patch the boot.img of your latest rom using magisk.. then flash it via adb.. ???
thaiten said:
Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
What are the exact commands/steps did you us to flash TWRP? And why is "flashing" in quotes? You either boot TWRP.img and can just flash Magisk for root without flashing TWRP; or you boot TWRP.img, flash the TWRP installer zip, flash Magisk.
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
I suspect the condition may be due to wrong fastboot command or flashing the wrong file. But we'd need to know the details requested above to figure out what went wrong. What root guide were you following?
In any case, going to fastboot mode, the phone is most likely not bricked. Just stuck in a state that it can't boot into OOS. Probably can recovery using a fastboot ROM, or flash back to stock boot.img.
failed to load authenticate boot image load error twrp
Hi there,
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem
solid.snake said:
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem
Click to expand...
Click to collapse
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.
redpoint73 said:
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.
Click to expand...
Click to collapse
Already done, please look at my 1rst screenshot : twrp74.img
solid.snake said:
Already done, please look at my 1rst screenshot : twrp74.img
Click to expand...
Click to collapse
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Okay, i'll give a try and tell you.
redpoint73 said:
"flashing" in quotes?
Click to expand...
Click to collapse
Because I'm just booting into TWRP first and then install it I thought. And because it didnt work lol
redpoint73 said:
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
Click to expand...
Click to collapse
I am, not sure why it says boot.img
redpoint73 said:
I suspect the condition may be due to wrong fastboot command or flashing the wrong file.
Click to expand...
Click to collapse
I used
Code:
fastboot boot twrp.img
and
Code:
fastboot flash recovery twrp.img
If I'm not mistaken. Was a few days ago now
solid.snake said:
Please people, tell us your Oxyygen OS version before the incident.
Click to expand...
Click to collapse
Was on the latest OOS Beta. But since using the freshly installed ROM with the MSM Tool, my device feels way smoother and the FPS works way faster. I don't know if thats because I bought the Chinese Version of the phone and there where a lot of trojans running in the background /s
But seriously though, way smoother. Probably partly caused by the longer animation duration set by default, but no idea about the FPS
redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Same result here