[Q] TF101G bricked??? unable to restore backup! - Eee Pad Transformer Q&A, Help & Troubleshooting

Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....

Can you still get into clockworkmod recovery touch? If you can try using the ADB from there to 'adb push rom.zip filepath/filepath' to get it onto your Internal SD and then reflash from there. I just use cwm 3.2, it's rock stable and never gives me issues, and after reading all of the issues with new versions and lack of ext SD support I refuse to update.

Darth Valda said:
Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Click to expand...
Click to collapse
You 101G is NOT nvflash compatible. You don't have SBK v1.
The only thing you can try is ADB push the necessary files to the internal sd storage.

I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX

Darth Valda said:
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Click to expand...
Click to collapse
Good to hear you got it working. Just a little FYI for the future.
Nandroid restore does not restore the kernel so next time just flash the ROM before or after the nandroid restore. That should put the correct kernel in place for it to boot up.

Did you try reflashing an earlier kernel? Those backups haven't been designed to store/restore kernel data (for us anyway). I think I had a similar experience, back when I was trying early AOSP ICS.

Hey! Thanks for the heads up, everybody!
I always thought that the nandroid backup restores everything (e.g. ROM, settings, base, kernel, etc.). That explains why the restore after the screwed up update to ICS didn't work anymore and why I got stucked in a bootloop again.
So even that seems not to be the last line of defense if you brick your device....

Related

[Q] adb impossible and more

Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
deralaand said:
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
Click to expand...
Click to collapse
If you have access to fastboot and assuming your flash storage isn't damaged, you should be able to flash over /boot with a boot.img and over /system with a system.img... But you might have to search around for them. Sorry i can't be more help.
kernels ; battery ; ROM ; gov/sched
http://www.mediafire.com/?wg9krukqp43nq1i theres a link to the boot.img for the apex bigxie rom (ics 4.0.3), try flashing that through fastboot i think the command is "fastboot flash boot %imglocation%.img" so just put the img in the folder you usually flash stuff with the fastboot bat in it, then try and flash this boot and tell me what happens.
ps, the %imglocation% should be the name of the img wherever you put it, so it will probably be boot.img.

[Q] Where do I go from here?

I have a Transformer TF101 US and I have rooted it, I installed recovery, but whenever I try to install a ROM it just sits on the splash screen and loops forever. I was able to install a rooted stock ROM and I just left it at that, but the launcher crashes and I have to restart. It reboots randomly and I was having problems with the market not processing my requests. I had an old recovery so I thought that might be the problem so I installed roach's recovery 5.5.0.4 r2 and it installed but no change on the status of the ROM when I reflashed them. Now I can only access the internal SD card with the recovery but only have access to the external SD card due to the looping ROM. What's my next step?
The ROM I've been trying to install is the new CM9 nightly. I have tried to install other in the past but the looped too. Other people have had success with installing it. Why doesn't it work for me?
Thanks
-Munchi3s
If you need access to the internal SD, plug your TF into the computer and use 'adb push' to send the files you need to flash to it, or if you can get far enough into usb mode just drag and drop.
Also make SURE to 'wipe cache' when flashing anything, and factory wipe/wipe script if the Rom requests it.
You can also try flashing a custom kernel or a rom which includes one with fixes to help with reboots. Guevor's test kernels and the Tastymehics kernels are good for this.
Minor problem with that
Thanks for the reply, but that's what I tried first too. On windows ADB dosn't see my device in recovery mode and the drivers from ASUS wouldn't fix it. Next I tried ADB on my ubuntu machine and it shows something on the ADB devices but it says
??????????????? no permissions
If I try to push anyways it tells me there is a problem with permissions
Ok. You were right. Wiping the cache fixed up everything. The ROM booted normally and no other problems to date. Thanks for your help.
-Munchi3s

help! please

Hello, Good afternoon.
So here's my problem, as you may or may not have (hopefully you have) read the post title i am having troubles with my CWM mounting my SD card so that i am able to either A: Load a ROM or B: connect it to my PC via usb so i can transfer over a ROM.
I have used the all in one toolkit to unlock my bootloader and root my phone, i have also installed the latest versions of SU, so originally after doing all of this everything was fine, A-OK. i then proceeded to download one of the cyanogenmod nightlies via CWM (the latest i believe) this is where as they say "**** hit the fan" so it seemed like everything installed all fine but then it reboots and nothing for hours it was just stuck on the HTC screen. i then switched the phone off and booted into recovery (volume down and power button) i then not sue it if was the right thing to do i wiped the data from the phone thinking it was corrupted and could simply put a new rom on via usb and boot it. however i have the problem of it not being able to mount my USB either to the pc or on the phone it self, i believe i still have access to the phone via ADB (im not 100% sure what ADB is) but i can flash new recoveries via CMD prompt. i have tried older CWM (modecco < did i spell this right? its the touch CWM) and i also tried TWRP Recoveries both of which cannot mount SD card and recieve the error "unable to open ums Lunfile" or "error mounting SD card".
i have searched many of the forums but form what i can see my solution requires me to boot into the OS but i cant do that nor can i mount my SD card to load a new one i.e putting on an Update.zip file to load a rom/os to the phone.
i dont generally ask for help as i enjoy trying to solve these issue and problems but i have been trying for a few days now and thought i would ask the experts.
any help would be greatly appreciated
Thanks

[Q] Only fastboot accessible to flash / restore my TF700

Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl

[Q] Stuck in recovery some time after flashing cwm

Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...
If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Sideload worked perfectly! Thank you so much!
cm11 working only TWRP here , with cwm appears same error
mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse

Categories

Resources