Related
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
jflynn0 said:
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
Click to expand...
Click to collapse
What instructions did you follow? Is the bootloader unlocked and can you boot into it? Does adb work? Need more info if we're going to help you.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
bootloader unlocked
I was looking around in cwm menu before I tried to install the stock asus rom. Just going thru the menu's looking trying to familiarize myself with cwm. I went to backup and restore menu and there was Zip there. I hit to power button instead of the volume and it starting restoring the device. After that i have not been able to get it to do anything after the asus screen. But I can get into the menu of cwm. When i tried following the adb, i go into cmd on my computer and change directory it tells me the device is not ready. I tried putting a zip on a sd card but I cant get it to show on the device to install.
Try a factory reset in CWM, see if that helps.
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
jflynn0 said:
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
Click to expand...
Click to collapse
Can you flash a different ROM, maybe the stock one?
Had the same problem. Tried to flash stock from Twrp recovery.
Wipe do a factory reset, wipe system and than flash the aokp rom again.
Then reboot and when you are back in System you can put the rom you like on your internal SD.
Back to Recovery and flash the new rom.
I got adb working and it come up in devices list. How do i flash the aokp rom on the device. I'm learning this as i go along, after this i might get the hang of this . I cant seem to push files using adb either my directory is wrong. I unzip it into a folder (C:\romfolder\aokp_tf201_build-38.zip/sdcard) and all that comes up scrolling page of commands and help for adb when i push
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
jflynn0 said:
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
Click to expand...
Click to collapse
Do not flash a 201 rom or image. Thats for the prime. Never flash roms designed for another device no matter how similar they are.
ok I downloaded this on
http://goo.im/devs/termleech/tf300t/aokp_tf300t_unofficial_20120617_2100_build-39.zip
have to go to bed but when i get up this afternoon will try to get it o go to device.
How am I suppose to get it to the device if the sd card does not show up on file list in cwm?
Can you still use ADB? You can always push the files with that.
how do i use adb to push the file on to the device itself. because i can add it to the sdcard by just putting in on there and then placing sdcard in device but the menu as far as install zip from sdcard never shows any zips that are on the card itself. Only thing that shows up are list of directories that look like a standard list from cwm. Also if you choose any of directories from that list it returns no file found. If I choose apply update on sdcard no matter how many time i have called the file update.zip says "no such file or directory install aborted". Or how do i push and image to the restore section of the device and where do i find an image at?
well still no luck. I think I will give it a few more days and if I still cant get it guess will go to best buy and buy another on. Any thoughts on Toshiba excite?
Try this i posted a tutorial on how to fix this http://forum.xda-developers.com/showthread.php?t=1738825 hope it helps
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
MidniteKitten said:
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
Click to expand...
Click to collapse
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
No, actually, I didn't. I haven't seen a guide point it out or a video that went through this step. Lemme' give this a shot and see if that helps with the problem I'm running into Thanks for the quick response, hoping this is what I was missing!
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
Unfortunately this didn't seem to fix my problem. Still encountering:
E:format_volume: make_ext4fs failed on /dev/block/mmblk0p2
Formatting /sdcard/ .android_secure...
And frozen again -_- It's bad enough that the sidekick sucks as stock (took me this long to finally want to do something about it) and that it's being difficult and resisting change.
Hmmm was your phone stock before you did anything to it? Or did you get the phone used or something?
My advice would be Odin to stock and start over try redownloading the recovery.zip to make sure it wasn't a bad download. And try again go slow and tripple check to make sure your following the instructions word for word. I've messed them up a few times cuz I got cocky but I got everything down from doing it so much and checking my work. The first time I rooted my sk4g I did it with adb not superoneclick and it was my first android phone it took me 2 hours of reading and following steps perfectly.
Sent from my Team Nightmare Amaze4G with Sense 4.0
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
ultraprimeomega said:
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
Click to expand...
Click to collapse
You are my saviour! I seriously love you! This worked PERFECTLY! I'm now running Glorious Overdos v3.3 and loving every single second of it. Because of you my phone is no longer a nightmare. You deserve a thanks
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!
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!
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.