I'll start from the beginning.
I got my loverly TF300T.
I've had my phone running cyanogenmod, so I figured I would throw that on my TF300 since it was so smooth.
My tablet came with 10.4.2.9, JB 4.1.1. I made sure to document this.
So I download the unlock APK and install it and unlock the bootloader.
Next I go into fastboot mode and flash TWRP.
I boot into recovery root the device, and boot back up to entire root is working - it was.
I then download my CM 10, drop it on the root of my internal storage.
Boot back to recovery, flash CM 10, reboot.
Get stuck at Asus/Nvidia boot screen.
Great. So I look do a bit of research and discover the Jellybean bootloader doesn't work with CM10, or something to that effect. Damn.
I'll try the CM10.1 Nightlies, They run JB, shouldn't be a problem. I throw it on my SD card, move the SD card, boot into recovery, flash it, boot it. Hooray, everything is working...except the wifi won't turn on. Well, we can't have that.
So I decide to flash back to stock. Not a big deal.
I download it 10.4.2.20 from the Asus site, extract the ZIP, throw it on the SDcard, boot into recovery, flash it.
Now I am sitting on an infinite load screen with the circular loading pattern.
So then I find 10.4.2.9 (what I started with) and flash that. Same infinite load screen.
Between every flash I wiped caches/system.
I am at a bit of a loss.
I can still access fastboot & recovery, but I can't seem to get the stock rom to boot anymore.
I can load 10.1 nightlies on it, and it works, but the wifi chip refuses to turn on.
If you have any ideas or a rom I can try or maybe I am missing something.
I am pretty new to this, so I don't know everything.
It's working!
Just an update, I got it working again!
I pulled off my titaniumbackup file, and decided to do a full delete/format of everything.
When I looked at the logs, I realized that /data was not properly mounting, leaving me to think that was part of the bad installs.
After a full cache/system wipe + a reformat of internal storage, I pushed the 10.2.4.9 blob via ADB (boy was that the longest 5 minutes of my life) and luckily it booted back up with everything working.
I then flashed my update.zip and superuser.zip, and let the titaniumbackup do it's thing, and my tablet is back.
While I didn't get a response here, I did find the commands and know-how here.
So I just wanted to say....This forum is awesome and thank you to all those who deal with this troubleshooting!
Related
Hello Forum! I've come here for a little help! Here's My Story.
After running Cyanogen 10.1 Nightlies on 4.2.2 for quite some time, I decided to do a factory reset because my TF300T seemed to be running a little slugish. I DID NOT back it up (mistake #1), DID NOT have USB Debugging on (mistake #2), and, while CWM was wiping /data, I shut off the tablet (STRIKE THREE). Prior to my bonehead move, I had everything else squared away. The unit was fully functional. Now, I'm stuck in this infernal boot loop on the ASUS screen.
I can reboot into recovery, so CWM is not compromised. I have tried to push a new ZIP of the ROM via ADB (unsuccessful, thinking the drivers are nerfed) and through CWM (also unsuccessful).
If anyone has any ideas, please feel free to comment.
P.S. Please don't kill me Mods, I'll be good after this
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Kazman101 said:
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Click to expand...
Click to collapse
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
ricco333 said:
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
Click to expand...
Click to collapse
It Unbricked!
Step 1: Flashed TWRP 2.4.4.0 blob file to overwrite CWM (Check)
Step 2: Factory Reset and Wipe Entire Device (CHECK!?!?!)
Step 3: Flash CM.zip!?!?! (Not So Check ... PLAN B!)
Downloaded Chinese Stock system blob (don't ask, I know it was stupid, but go with me here)
Flashed the system blob (after 3 minutes ... SUCCESS!)
No more boot loop and back to stock ... now to root it again to get my sweet CyanogenMod back ...
Thank you Erik, your help was much appreciated!
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.
Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?
x000111 said:
Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?
Click to expand...
Click to collapse
Restore backup or flash some other Rom,
Sent from my GT-P3100 using Tapatalk
Yes, that is what I'd like to do. But how would you suggest doing that since I cannot get into recovery and am stuck in a boot loop?
Whew... I let the tablet sit for a couple of days while I worked on other things. I decided to try, just for the heck of it, to put it into recovery mode (Power+Vol Down) and it worked. I already had a new ROM ready to install on my microSD and did it. It looks like CM10 is going to be my ROM now. It installed and is running! What a relief!
It must not have been shutting down all the way before. Even though I saw the Samsung Galaxy Tab logo, there must have been something it didn't like at the time. No idea besides that.
Last night, I downloaded the 6.0 update, copied the .zip to external storage, rebooted to CWM, and flashed it (successfully), then flashed SuperSU over it, cleared dalvik, and rebooted.
Since then, I'm stuck with the Nvidia boot screen. I can use Power/Vol Up to get in to fastboot, but when I try to boot back into recovery, the screen goes black, but goes back to the Nvidia boot screen instead of booting to recovery, even after flashing a recovery image to it via fastboot.
I can probably fix this with enough time and tinkering, but I just came back from a two week from vacation at work and don't have the time to futz around with this. Posting here in case someone already has an idea on what the problem is/how to fix this.
Update: I was able to get back into recovery using TWRP referenced in http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541. Direct link is https://www.androidfilehost.com/?fid=24345424848487676.
I'm thinking this is a kernel issue.
This was a kernel issue. Flashing a older OTA (http://ota.nvidia.com/ota/data/post...wf-full_ota-36442_589.1541.20150826095201.zip) and booting normally, then rebooting to bootloader and fastbooting the CWM image worked. I'm restoring from a backup I took before flashing the update last night, then flashing TWRP, backing up, and trying this all over again.
Thank you, I was having the same issue :good:
Have the exact same issue, except that now, for some reason, I can't even get the device to turn on!
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.