Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, is used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
You have flashed the latest TWRP via fastboot and it still wont flash roms? Also, what bootloader are you on?
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4
Phultara said:
Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, it used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
Click to expand...
Click to collapse
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Thats OK said:
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Click to expand...
Click to collapse
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
If you have the 4 icons that indicates JB.
Sounds like the custom recovery is not installed if your on the RCK icon and press the up volume rocker and nothing happens.
adelancker said:
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Click to expand...
Click to collapse
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Phultara said:
When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
Can you get adb shell access to your recovery?
Which ZIP are you actually trying to flash? What is the exact error message from the recovery? Try running md5sum (inside the adb shell) on the file you want to flash. Check the output of "mount". Check if /cache/recovery/log contains interesting info.
Phultara said:
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
adelancker said:
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
Click to expand...
Click to collapse
How would I go about connecting through ADB?
Phultara said:
How would I go about connecting through ADB?
Click to expand...
Click to collapse
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
_that said:
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
Click to expand...
Click to collapse
Alright, I'll have to try that when I get home in about 3-4 hours. I'll get back to you on that. Also, I noticed last night that when I was on fast boot, it would stay stuck as waiting for device on the cmd window. I'm not sure if it was my computer that didn't detect it or a new symptom. O hope its just a fluke!
Alright, here's the log from my recovery.
Phultara said:
Alright, here's the log from my recovery.
Click to expand...
Click to collapse
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
buhohitr said:
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
Click to expand...
Click to collapse
That did it!!! Thank you!!!! Looks like it was the SD that was the root of the issue! Thanks!!
Related
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
Hey guys,
I'm having some trouble with flashing a new ROM and now I've soft-bricked my device.
I was trying to flash from CROMi to CM11 so I wiped data, cache, dalvik using TWRP. But when i tried to flash CM11 M9, i would get the "failed" error. I tried flashing other ROMs but same result - "FAILED".
So I thought maybe it was the recovery. I downloaded a CWM recovery (in .zip) and tried to flash it. FAILED!
I tried to restore my device using the "Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with custom recovery" method from this post. Since it is basically flashing the stock ROM, naturally it fails.
Now I'm out of ideas. How can I save my tablet?
Thanks for your help guys!
PS: I'm trying to install CMW via fastboot. When I press power + vol down, I get to the screen with "RCK, Android, Data Wipe"; I dont see the USB icon. How do i boot into fastboot?
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks!
oh.herro said:
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks![/QUOTE]
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
r3dal3rt said:
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
Click to expand...
Click to collapse
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
lj50036 said:
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
Click to expand...
Click to collapse
Exactly.
I also would like to know how you performed the wipe you mentioned. The tablet booting only and straight to recovery would indicate that you used 'Wipe Data' from the bootloader???
Also, do not use ROM Manager. It does not work well with the Transformers and can cause a lot of problems.
I have a feeling another user is going to benefit from your excellent unbrick guide, Josh...
Aren't you glad you wrote it?? [emoji12]
lj50036 said:
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
No boot to recovery ?
No bootloader ?
No nvflash blob backups ?
If that is the case then you are not looking good ...
There is no way out of this one ...
We need fastboot or recovery one or the other ..
Sorry for the bad news ....
Thx Josh
oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
I agree with lj - not looking good. [emoji17]
Do you have adb access when it boots to the Asus splash screen?
I know there is another very similar thread that was just opened(http://forum.xda-developers.com/oneplus-one/help/completely-stock-oneplus-one-stuck-t3396207), but his solution didn't help me so I'm making this thread.
I really need to save my internal data, so only as a last resort will I wipe userdata to save my phone.
First of all my phone is completely stock. Locked bootloader, unrooted, stock recovery, and stock rom. Last thursday(June 9th), I got the CM13.1 OTA update which I installed and everything went normal. It finished installing, restarted and booted up, optimized apps, rebooted, but then optimized apps again and again. I thought it might help to just reboot my phone, but it didn't. So I immediately started looking around for solutions.
I can boot into recovery and fastboot mode and since I can boot into recovery I started with wiping cache(Stock Recovery>>Factory reset>>Wipe cache partition). It took ~20mins which seemed like an unusually long time, then I rebooted and it still got stuck in the "optimizing apps/reboot loop". Next, I set up USB drivers, ADB, and fastboot since it seems to be very important to have those set up. I used a few guides to get them properly set up and I checked that they were correct by checking that the cmds "adb devices" and "fastboot devices" returned my device, which they did. I saw someone saying he saved his friends OPO by just ADB sideloading a CM zip file, so it looked hopeful in my case. I downloaded cm 13.0 and 13.1 zip files and tried sideloading them with the cmd "adb sideload cm13.zip". I tried both and they both got to around 50% complete and the install failed. Some of the red text said, "Package expects build fingerprint of oneplus/bacon/A0001:5.1:6.0.1..... & E:Failed to install /sideload/packages.zip ". Next I tried installing TWRP, which looks like it requires an unlocked bootloader to flash it(even to to just boot into it). From all my research it looks like there's no way to unlock the bootloader without wiping data. Even the OPO toolkit says you need to wipe data to unlock your bootloader.
One thing I haven't looked too much into is using fastboot to save my device. This guide http://www.technobuzz.net/fix-bricked-dead-oneplus-one-easily/ shows to flash userdata userdata_64g.img, which I assume wipes userdata.
Maybe I'm just overlooking some simple fix, but if anyone can help me I would be eternally grateful.
Edit: I need my phone working and I'm tired of waiting for help, so I just did a factory rest. Also I've been getting tons of conflicting advice. Thanks everyone for the help anyways
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
mastersen901 said:
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
Click to expand...
Click to collapse
download and install the 15 second adb/fastboot installer (http://forum.xda-developers.com/showthread.php?t=2588979)
It'll create a folder: C:/adb, In that folder you can open a cmd prompt window to send cmds to your device through adb/fastboot. that folder is also where you place files that you want to flash or boot into.
Also for the USB drivers just download the oneplus one toolkit, or use this guide: http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
the opo toolkit is in the 2nd method
Still looking for help. Phone status: After sideloading cm 12.1 it boots up but I get tons of errors saying com.android.phone failed/ android.system.acore failed which make my phone inoperable, also my phone usually reboots after ~10 seconds after booting up and getting errors.
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
itechy said:
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
Click to expand...
Click to collapse
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...be76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
woodhaus said:
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...e76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
Click to expand...
Click to collapse
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
itechy said:
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
woodhaus said:
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
Click to expand...
Click to collapse
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
itechy said:
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
Ohh! thanks! I was looking for this!
I just got around to sideloading the cm 13.1 zip. I'm still getting a bootloop /:
Edit: My phone reboots and optimizes apps after getting hung up on the cyanogen boot screen for a while.
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
hibernick said:
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
Click to expand...
Click to collapse
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
saurav007 said:
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
Click to expand...
Click to collapse
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
hibernick said:
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
Click to expand...
Click to collapse
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
woodhaus said:
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
Click to expand...
Click to collapse
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
hibernick said:
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
Click to expand...
Click to collapse
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
woodhaus said:
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
Click to expand...
Click to collapse
Oh, thanks. I didn't even go there.
Goodmorning everyone
I have a problem on my TF300TG which I picked up from my drawer after a while
I upgraded to 7.1 nougat following the instructions given in the letter (very clear) but now my tablet does not start the system, I explain better:
it turns on and the writing unlock remains The device is unlocked with the ASUS logo in the Center but does not start.
I can go back to recover twrp at any time and reflect what I have repeated several times even with different versions but I always have the same problem.
I can also re-revise the original flash blob and start again
Giangi_TF300TG said:
I upgraded to 7.1 nougat following the instructions given in the letter (very clear) but now my tablet does not start the system, I explain better:
it turns on and the writing unlock remains The device is unlocked with the ASUS logo in the Center but does not start.
I can go back to recover twrp at any time.
Click to expand...
Click to collapse
First of all format data through Kang TWRP recovery. It may take until one hour. Be patient. Let it run. After that install rom, SUSuperuser and pico Gapps in one run.
Not boot again
ebonit said:
First of all format data through Kang TWRP recovery. It may take until one hour. Be patient. Let it run. After that install rom, SUSuperuser and pico Gapps in one run.
Click to expand...
Click to collapse
I just finished the procedure that you suggested that it did not return me errors but does not boot.
just restarted of the recovery mode updates the twrp restarts and remains nailed on the Asus screen if I want I can restart in recovery.
Any other suggestions?
Giangi_TF300TG said:
I just finished the procedure that you suggested that it did not return me errors but does not boot.
just restarted of the recovery mode updates the twrp restarts and remains nailed on the Asus screen if I want I can restart in recovery.
Any other suggestions?
Click to expand...
Click to collapse
Yes, you should do carefully a Buster99: https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
This procedure brings you back on a clean stock rom Android 4.2 Jelly Bean. Then you have to flash Kang TWRP firstly.
PS: Attention! If you restart in recovery with the 3 icons, never touch the third one in order to "Wipe Data". It bricks your device!
ebonit said:
Yes, you should do carefully a Buster99: https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
This procedure brings you back on a clean stock rom Android 4.2 Jelly Bean. Then you have to flash Kang TWRP firstly.
PS: Attention! If you restart in recovery with the 3 icons, never touch the third one in order to "Wipe Data". It bricks your device!
Click to expand...
Click to collapse
The factory reset has been done correctly the system has restarted correctly after reinserting the nougant yet the system does not boot the only thing that has changed and that now reboots into the loop by returning to the asus screen repeatedly
Giangi_TF300TG said:
The factory reset has been done correctly the system has restarted correctly after reinserting the nougant yet the system does not boot the only thing that has changed and that now reboots into the loop by returning to the asus screen repeatedly
Click to expand...
Click to collapse
It seems there has been a big misunderstanding by you. I advised to format data through Kang TWRP, but you did a factory reset, didn't you?.
Too many people mix up wipes and formats. Format only data means, not factory reset, not wipe - you format it ext4, then convert it to f2fs. Formatting in Kang TWRP takes until 1 hour. If it went faster you did not format. Kang TWRP does a deep format that rewrites everything in the partition. No moldy leftovers.
Now your device is in a boot loop, but not bricked. So doing a Buster99 is the only way to solve the problem. If you need help with fastboot, head over to the General section. Download and install "Minimal ADB and Fastboot" on your PC.
ebonit said:
It seems there has been a big misunderstanding by you. I advised to format data through Kang TWRP, but you did a factory reset, didn't you?.
Too many people mix up wipes and formats. Format only data means, not factory reset, not wipe - you format it ext4, then convert it to f2fs. Formatting in Kang TWRP takes until 1 hour. If it went faster you did not format. Kang TWRP does a deep format that rewrites everything in the partition. No moldy leftovers.
Now your device is in a boot loop, but not bricked. So doing a Buster99 is the only way to solve the problem. If you need help with fastboot, head over to the General section. Download and install "Minimal ADB and Fastboot" on your PC.
Click to expand...
Click to collapse
Excuse me surely I did not understand here now I follow your advice step by step.
Now I'm running a buster99 but I don't need ADB, I already have a fastboot working.
PS that is I'm starting fastboot not from adb but from a folder on my pc that is executing the buster commands
Then what do I reinsert the right Kang bootloader?
Excuse my ignorance
Giangi_TF300TG said:
Excuse me surely I did not understand here now I follow your advice step by step.
Now I'm running a buster99 but I don't need ADB, I already have a fastboot working.
PS that is I'm starting fastboot not from adb but from a folder on my pc that is executing the buster commands
Then what do I reinsert the right Kang bootloader?
Excuse my ignorance
Click to expand...
Click to collapse
Now my system is restarted with the original rom I reinsert twrp_tf300t_kang_2.8.7.2.img,
after how do I proceed?
Giangi_TF300TG said:
Now my system is restarted with the original rom I reinsert twrp_tf300t_kang_2.8.7.2.img,
after how do I proceed?
Click to expand...
Click to collapse
Congratulations, good job!
Please look here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
ebonit said:
Congratulations, good job!
Please look here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
Click to expand...
Click to collapse
I have already inserted this twrp tf300t kang 2.8.7.2.img, through fastboot do I have to do it with the linux procedure?
the system now has boot recovery and starts normally with the old system.
Now that I do I have to delete the given partition or do I flash the three roms?
Giangi_TF300TG said:
I have already inserted this twrp tf300t kang 2.8.7.2.img, through fastboot do I have to do it with the linux procedure?
the system now has boot recovery and starts normally with the old system. What does old system mean?
Click to expand...
Click to collapse
I'm sorry, but it is not easy to understand what you did. As far as I know your device is on stock rom Android 4.2 Jelly Bean. Correct?
The next step should be to flash (not insert!) "twrp_tf300t_kang_2.8.7.2_signed.zip" via fastboot. The command is: "fastboot -i 0x0B05 flash recovery foo.img". Replace foo.img with the recovery image name! Did you?
If yes, you may start the device into recovery. Kang TWRP should start. After that install through TWRP Nougatella #39, pico Gapps and Super SU from the external memory of your device in one run. That's it!
Please pay attention you did download the newest versions in post #1: https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 !
ebonit said:
I'm sorry, but it is not easy to understand what you did. As far as I know your device is on stock rom Android 4.2 Jelly Bean. Correct?
The next step should be to flash (not insert!) "twrp_tf300t_kang_2.8.7.2_signed.zip" via fastboot. The command is: "fastboot -i 0x0B05 flash recovery foo.img". Replace foo.img with the recovery image name! Did you?
If yes, you may start the device into recovery. Kang TWRP should start. After that install through TWRP Nougatella #39, pico Gapps and Super SU from the external memory of your device in one run. That's it!
Please pay attention you did download the newest versions in post #1: https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 !
Click to expand...
Click to collapse
Sorry I'm using google translate
So far I have flashed the recovery twrp_tf300t_kang_2.8.7.2.img.
I restarted in recovery mod TWRP and I installed the 3 zip in sequence through sd card
KatKiss-7.1_TF300T_039.zip, open_gapps-arm-7.1-pico-20200325.zip, SuperSU-v2.82-201705271822.zip all OK
I ran Wipe cache / dalvik
I restarted
performed a first start where the bar under ASUS quickly colored blue
It has restarted
but later stuck on ASUS. I don't know where I'm wrong
From the fact that you have not replied to my last message, I think we have given up.
Just one thing I'm curious to know are there versions of this Tablet with different hardware or different firmware (bios) you can update? I don't know I thought even if I had to have a rom already cooked and functioning on an equal tablet I could shoot it in a single flash
Giangi_TF300TG said:
Sorry I'm using google translate
I don't know where I'm wrong
Click to expand...
Click to collapse
I'm sorry, but I also don't know where have been wrong? How should I reply after so less information about the situation. There are many different possibilities.
Hopefully you have a backup of the system through TWRP after finishing the Buster99. If so, please start the TWRP recovery and restore the backup.
Search here for "TF300TG": https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
ebonit said:
I'm sorry, but I also don't know where have been wrong? How should I reply after so less information about the situation. There are many different possibilities.
Hopefully you have a backup of the system through TWRP after finishing the Buster99. If so, please start the TWRP recovery and restore the backup.
Search here for "TF300TG": https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
Click to expand...
Click to collapse
Sorry but once done the Buster99 procedure I don't need to do a restore of the Backup since the tablet restarts regularly with the original system I didn't perform any backup I didn't need it