Transformer Prime - Unlocked Bootloader -Settings - Backup & Reset - Factory Defaul
Although im an expert in adb, roms, and android sdk development, because i dont normally contribute, im a "noob" and cant post in the development section???? Whatever, his my community contribution.
I rooted my Transformer prime, and unlocked bootloader. I held off on installing custom roms because i wanted something iron clade.
Also, had problem booting into CWM after bootloader unlocker.
I do however enjoy wipping my prime ocassionally to get a fresh install due to security fears such as installing software from outside the marketplace
So one day, after rooting and unlocking bootloader, i reset the prime to factory default.
Problem:
Factory default reset erased user data
Reinstall of this data on reboot was blocked from installing, because CWM kicked in and saw it as a wipe of data. Result, infinite bootloop into CWM which i couldnt reach before. Since the command inside the android os was never completed because of CWM, i couldntboot os.
Did i mention i never made a backup before the issue occurrered??? Ekkkk
Steps to repair:
-immediately create backup of what is still installed on prime in CWM.
-adb push a rom found on xda developers for an additional avenue of restore in the event your backup from the proceeding step fails. Adb can be a pain, if its not working, abd stop-server and thenre-push the rom to / directory, not /sdcard
-format all partitions available in CWM. Including stagging...
-restart device
-use fix 1a located here http://forum.xda-developers.com/showthread.php?t=1514088 careful with command entries, if your using windows these commands are like sudo to your device. Thanks to the genious who came up with this.
-once completed, restore your stock backup. Then make a new bakup of your fixed stock rom. You shouldnow be able to boot your stock rom and you have a backup. If not, erase everything again in CWM and installu the additional backup rom from step 2 (any rom is better than none).
Done. Restart and pad yourself on the back. You just brought prime back from the dead.
I thought it would be good to share as no one has addressed a fix from a problem caused by a data wipe factory reset on prime done inside the os.
Sorry for type ohs, i suck at typing on my tablet.
Wave, on his revived Transformer Prime
P.S. this method will also work when dealing with a bad OTA update from asus, providing you can still adb the latest CWM, boot CWM, and have rom to restore. Im buying bricked primes to resell working contact me for repair service
Finally used the Full Wipe Tool from the Transformer Prime. This tool works everytime, but it does have issues with improper file structure after using preventing you from pushing a rom via adb. The best work around, after using the tool, reboot, hold down volume button but don't hit up. wait until it boots to the Full Wipe, USB, Cold boot options. Select Full Wipe, let it wipe the system. It will repair the file structure. Reboot back into CWM, create a backup. You can now adb a rom to the sdcard. Works like a charm everytime.
I love this tool, I get that fresh install taste everytime I install a new ROM.
Link to full wipe tool I was talking about above
http://forum.xda-developers.com/showthread.php?t=1670824
Works awesome when using this technique above. The technique above is the perfect work around for errors transferring, include protocol errors in Windows, and if you are transferring using adb, but after the transfer cannot see the file transferred on the Asus Transformer Prime.
I'm beginning to think this tablet is unbrickable, unless you are really, really, dumb and flash an original OTA update.
You saved my bacon, I just used the superwipe script and am having issues with pushing a rom. Thanks a ton.
Edit: Or not....Can't get the Prime to show up when I use adb devices...
Related
Alright, after bricking my phone yesterday and spending hours finally unbricking it, I've decided that I'm just not quite ready to play around with ROMs on the Transformer Prime. At least, not until they get a little more stable.
However, I'm finding myself unable to get my Prime back to stock ICS...
What I'm currently running is a Cyanogenmod 9 nightly build from 3/4/12. Through Rom Manager I was able to install the latest CWM (5.8.2.0) BEFORE the whole bricking incident. Now I can't even get my WiFi turned on...so I suppose any further changes via Rom Manager are halted.
Anyway, I used Vipermod's tool and was able to unroot successfully. I then went into settings and attempted to perform a factory reset. However, my tablet booted up with the same, Cyanogenmod boot screen and brought me back without any changes.
So then I tried using ADB....plugging my Prime in and typing "adb reboot recovery". But I get the message "adb server is out of date. killing..." then on the next line * daemon started successfully *. My device resets...but same thing...cyanogenmod...no CWM...no changes.
I thought maybe ADB wasn't working because I had unrooted. So I re-rooted, again using Vipermod. I see superuser again now...but ADB reboot recovery is still not working.
So now I'm stuck... I seemingly can't perform a factory reset with my build of cyanogenmod, and I can't find any way of getting back to recovery (I've tried selecting recovery reboot after pushing the power button, tried selecting recovery from within Rom Manager and tried with ADB...all failed). Again, all I want to do is factory reset, and get my stock ICS back. Can anyone please help me out?
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Diamondback said:
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Click to expand...
Click to collapse
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
scaryslocuda said:
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
Click to expand...
Click to collapse
My warning only applies to STOCK blobs (like the ones in the official asus updates from their website).
The guide you posted seems to be fine.
Great! I'll give it a shot tonight.
One last thing... If I find that Virtuous isn't the best fit for me, would you advise AGAINST installing the stock firmware posted over at Android Soul? Is this what you would consider a "stock blob" or is this something different? Here is the link:
http://www.theandroidsoul.com/trans...h-cwm-recovery-on-unlocked-bootloader-primes/
That's a zip, not a blob, you can flash that
Diamondback said:
That's a zip, not a blob, you can flash that
Click to expand...
Click to collapse
Worked perfectly! Thanks so much for your help Diamondback...again!
Running 2.3.4 version 4.5.91 ATT/US SBF I believe, stock kernel, unlocked bootloader, rooted, and have Tenfar's CWM recovery.
I accidentally accepted the download for update to v4.5.141 (after hitting "Later" 1000 times), but had wifi turned off at the time and the download never started... now I can't turn back on wifi because the download will automatically start (triangle! with "Enable Wi-Fi to start download update" in notifications), and I don't want to brick the device if it runs and I can't cancel the install.
What can I do to cancel the OTA download and/or install and avoid bricking the device?
Any help is appreciated.
Hmm. I know it's possible to "freeze" the update notification (that is, either use the pro version of titanium backup, or put .bak after the appropriate system app). A few other threads have detailed how to do this.
You just accidentally downloaded it, right? It shouldn't install automatically; it would pop up another "install" vs. "later" prompt once the download finishes. I know there's another post around here (stickied?) that details how to back up your OTA update. You could probably use that thread to find your downloaded file & delete it.
Alternately, since you're unlocked you could always install another rom and skip the OTA process entirely. For example, Nottachtrix is based on the 4.5.141 build and comes with a stock Gingerbread theme if you want.
Thanks, I did see those threads you mentioned.
Before my mistake, I had already tried renaming /system/app/Upgrader.apk to .bak with root explorer, and rebooting to stop the download update popup... it didn't work, and kept prompting me, which I eventually accidentally accepted instead of hitting "Later".
I don't have the Pro version of TiBU Pro; I was thinking of upgrading it to freeze Upgrader when I was trying to stop the download update prompts, but as I mentioned I accepted the download before I could do that.
I was also considering flashing Nottachtrix since that seemed to be the only safe way I saw to update to 4.5.141 with the unlocked bootloader. can I safely flash that now, even though the update is pending?
I'll be honest and say I don't know with certainty. BUT -- I don't see why you couldn't download Nottachtrix on your computer, drop it onto your phone's SD card, and flash it from there (without ever turning your phone's wifi back on). Your phone is booted & not in the middle of an active install. It's just waiting to download a file which would requires your input to begin installing anyway.
If you're really concerned about it, you could do the Seriously Complete Wipe before flashing the new rom by using the following method (thanks CaelanT):
For the best results, when you want to flash a new ROM you should always perform a full wipe in fastboot per the following to make sure you will avoid any unforeseen complications:
reboot to recovery
wipe Dalvik
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
Click to expand...
Click to collapse
One more note: it looks like Tenfar's recovery is considered "old" round these parts, and most roms don't play well unless you flash them using romracer's CWM recovery. So that should probably be your first step. It's here.
thanks for the recommendations. I guess I will uninstall Tenfar's recovery, install romracer's recovery, do the Seriously Complete Wipe, and then flash Nottachrix. Let me know if any of that sounds wrong.
Will I lose my apps or my titanium backup of apps & system data by doing the Seriously Complete Wipe? If so what do I need to do to be able to restore my apps and system data after the wipe & flash?
Hey, no problem at all. (by the way, you don't need to uninstall your current recovery, just flash the new one per the instructions.)
Oh yeah, a second note: you'll need to rename two particular files before flashing the new recovery. From another stickied thread:
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Click to expand...
Click to collapse
Okay, on to apps & data. Yes, you're going to lose all your data in the wipes, but the backups you made will be intact. TiBu is fine for your apps; I use "MyBackup Root" (free on the market) for my contacts, SMS, MMS, etc. After flashing the new rom, you'll have the market pre-installed. Use it to re-download TiBu, restore your backed-up apps (NOT EVER system data. Just apps+their data.), then restore the rest from there.
I did everything, and it worked well. thanks for confirming it was safe and the extra tips!
I had already uninstalled Tenfar's recovery by the time I saw your response. I thought it may conflict, didn't know.
I didn't have to rename those 2 files to be able to boot into CWM recovery... the files weren't present before or after installing CWM recovery and it worked.
Thanks again for the tips on the seriously complete wipe and the MyBackup Root, they worked well.
Almost everything was restored after flashing the ROM except for a few minor settings. I somehow have a ton of contacts because I have all my Google contacts, my Blur contacts (a lot of dupes of Google ones), and a lot of extra old gmail e-mail contacts that I wish it didn't populate. Nothing to complain about because I would rather there be extra unnecessary contacts than missing ones.
The only issues I have is that the ROM shows the 3G img at all times... so I have to do some speed tests and troubleshooting to see if I am stuck in 3G or if it is just the known bug in the ROM where 3G is always displayed.
I have N_01.77.30P radio and I saw some people are running 36 or 37, and some people on AT&T installed an additional APN that improved performance.
If anyone has any input on the 3G, radio, or APN issues, please let me know.
atrix issues
Hello members,
i am new to android and learning to understand the jargon of experts here. Reason for joining xda is following:
I (from India) have a motorola atrix 4g that i purchased from a friend in US (it was on AT&T.)
1) when I start my phone -is says on top unlocked. Does it means it is unlocked / unrooted? and I cannot install the OTA updates from Motorola like ICS 4 coming in Q3?
2) I clicked on system update and downloaded the update over wifi. When it started the install it got failed with a triangle and ! mark. I had to remove the battery and start the phone after which it kept on rebooting . Saw in some forum that i had to do a factory reset and after doing that it worked but I lost everything. I had to reinstall all the apps. Is there a way to reinstall the latest OTA updates from Motorola with doing / playing much with ROM? if not then please let me know a simple and safe way.
3) After doing factory reset i accidentally clicked on system update and now the update is downloaded over wifi but i did not install by selecting "install later" . However the popup keeps coming up and i want to disable it. kindly advise how this notification can be stopped.
Thanks in advance
Hi there,
I just read a lot of threads in this section, but it realy seems as nobody was as stupid as me.
Today I decided to root my Prime and it was all simple.
I used vipermod to root, unlock and install cwm.
I made Titanium Backup of all my Apps (nothing important here), and made a backup via cwm.
With cwm I flashed Virtuous Prime and all was fine.
Then I made the big mistakes:
-I restored most of the apps with Titanium Backup.
-I used a code to unlock my prime and I also wanted to test the encryption.
After the reboot that comes after the encryption, I entered the key, and the Prime booted.
As the lockscreen appears I entered my lockscreen code (which is the same as the encryption code) and it was ... wrong!
I don't know exactly how this happend, but maybe it was due to the Titanium Backup that I restored. Maybe I restored a system app which included the code?! I don't know.
So I couldn't enter my device, but I still had cwm, so I thought this wouldn't be a problem.
I thought I could do a factory reset, and all would be ready to go.
I did a factory reset, wipe cache, wipe dalvik - nothing helped.
It was a problem, because cwm didn't let me do anything, neither restore my backup (not found, because encrypted) nor flash the ROM again (the same here).
The only thing left I tried, was formating all the things, that I could format, but this sucked me even harder in this desaster. Now my Prime got bootloops and I don't know anything to do.
Any ideas or help is apreciated!
I would thank you so much, if anyone could help me get my Prime back to me!
have you tried to adb into your device from a PC? there's a thread in developement section called do's n donts of unlocking. I think it tells you in there how to get out of bootloop.
Thanks for your answer!
You mean this, right?
Seems as I'm nearly at Brick 2, even if I don't get "unrecoverable bootloader error", but my Device also hangs in this splashscreen with the "Eee Pad" in the middle.
Looks like I'm lost
Edit: Needed a bit to get familiar with adb, but I was able to push the rom again on the sdcard.
I fullwiped and installed the rom. First reboot askes me for encryption code, then the rom needs a bit to start.
Problem remaining: The code on the lockscreen is still wrong. I can't enter my device
Is there there any possibility (if even a full wipe doesn't help) to get back to my device?
Solved: I just had to wipe via the boot menu (voldown + power button, then wait the 5 secs)
Encrypted partition has gone!
I'm relatively new to the process of rooting and flashing so please be gentle senpai. Overall, my question is, how do I get either restored to my back-up, or to a better cleaner ROM. What motivated my tampering was that bluetooth wasn't working in Cyanogenmod 10.1
I received a TF201 tablet from my brother who is fairly experienced with the process of flashing roms and working in the world of rooted devices. He lives a while away so to have him look at it with me is a challenge but I've discussed the status of the tablet with him and he's hopeful that there's a solution.
When I received the tablet it was running the following:
Cyanogenmod 10.1 (according to the settings)
twrp 2.5
JB bootloader (at least this is the best I can conclude since the nvidia insignia is in the bottom right at the splash screen.)
As a side note, when I'd power on while pressing the down volume, in order to get to fast boot I had to select the USB signal option. This changed later. (unsure when.)
The status of the tablet now seems to be (emphasis on seems since I've tried many things while attempting to get a working rom) the following:
Successfully ran restore back-up to Cyanogenmod 10.1 (success being that it ran the data and seemed satisfied when completed with no error codes or issues.)
Running Hairybean 2.31 and twrp 2.5 ( I think, not sure how hairybean fits into the functionality of the recovery but the whole UI is hairy still.)
JB Bootloader (again because the bottom right nvidia)
Fastboot is default and only 3 selections available in recovery mode. While on this screen at the top left it says "Key driver not found . . Booting OS.
When trying to boot to the restored back-up I get a regular ASUS logo with nvidia symbol at bottom right, and "the device is unlocked" at top left. This screen sits for a moment, then goes black (as if it's trying to do the right thing) and then the screen returns and the tablet stays there indefinitely.
In recovery mode, when I select "mount" I'm able to see that "system" has a red switch (so it's not mounted.) I can turn it on, and it stays on persistently while in the recovery mode, but when I've attempted to reboot the tablet either to the ROM or directly back to recovery, the "system" is unmounted again.
This is a summary of what I've done to the tablet, at first I was just trying to get the katkiss ROM according to the thread referenced below. After a few steps I realized I was in trouble and started trying to fix the tablet with anything that would work.
http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
Here is the log I made of what I did to the tablet. Maybe something here will explain the issues I'm having.
It's not completely comprehensive since I realized too late that I should have documented everything I did.
Backed up in TWRP
Flashed Hairybean http://forum.xda-developers.com/showthread.php?t=2407248
Updated TWRP to 2.6.3 as suggested #543 http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919/post56681951#post56681951
Tried to flash katkiss http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
When katkiss failed, tried grimlock kernal according to #543 http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919/post56681951#post56681951
That seemed successful.
Rebooted to twrp recovery (password required)
Searched about password, clicked cancel, attempted to format data but failed.
Attempted to clear data through fastboot according to: http://android.stackexchange.com/questions/89182/bricked-my-tf300t-how-to-re-partition-internal-storage-to-get-it-back
Couldn't get any ROM to work
Decided to try from square 1 to get virtuous prime to work according to http://sitr.us/2012/05/12/installing-a-custom-rom-on-the-transformer-prime.html
Cleared data through fastboot in system, recovery, userdata, boot, misc, and cache.
Flashed clockworkmod
Flashed virtuous prime with fastboot -i 0x0b05 flash system
fastboot -i 0x0b05 reboot
Would not boot to OS, or recovery,
"key driver not found . . booting OS" at top left
After this, I again cleared data through fastboot system, recover, userdata, boot, misc, and cache.
I flashed the default ASUS TF201 kernel from https://github.com/namidairo/android_kernel_asus_tf201
Installed a twrp.blob that I got from a page flumpster recommended it (I can't find it now.)
Able to get to recovery, but received "unable to mount" errors whenever I did any formatting in the recovery mode.
Thank you for your help. I'm open to trying whatever you think will work. I know this is a sensitive product and apparently prone to bricking but I'm really REALLY hoping that I didn't brick my new toy. I don't know if there are other diagnostic tools I'm not aware of that would give me a better read on what the status of my tablet actually is to try to pinpoint the issue or if the only way to do that is to clear everything on it and start over to be sure of what's running.
You guys are phenomenal. Thank you in advance.
aamcc
aamcc said:
I'm relatively new to the process of rooting and flashing so please be gentle senpai. Overall, my question is, how do I get either restored to my back-up, or to a better cleaner ROM. What motivated my tampering was that bluetooth wasn't working in Cyanogenmod 10.1
I received a TF201 tablet from my brother who is fairly experienced with the process of flashing roms and working in the world of rooted devices. He lives a while away so to have him look at it with me is a challenge but I've discussed the status of the tablet with him and he's hopeful that there's a solution.
When I received the tablet it was running the following:
Cyanogenmod 10.1 (according to the settings)
twrp 2.5
JB bootloader (at least this is the best I can conclude since the nvidia insignia is in the bottom right at the splash screen.)
As a side note, when I'd power on while pressing the down volume, in order to get to fast boot I had to select the USB signal option. This changed later. (unsure when.)
The status of the tablet now seems to be (emphasis on seems since I've tried many things while attempting to get a working rom) the following:
Successfully ran restore back-up to Cyanogenmod 10.1 (success being that it ran the data and seemed satisfied when completed with no error codes or issues.)
Running Hairybean 2.31 and twrp 2.5 ( I think, not sure how hairybean fits into the functionality of the recovery but the whole UI is hairy still.)
JB Bootloader (again because the bottom right nvidia)
Fastboot is default and only 3 selections available in recovery mode. While on this screen at the top left it says "Key driver not found . . Booting OS.
When trying to boot to the restored back-up I get a regular ASUS logo with nvidia symbol at bottom right, and "the device is unlocked" at top left. This screen sits for a moment, then goes black (as if it's trying to do the right thing) and then the screen returns and the tablet stays there indefinitely.
In recovery mode, when I select "mount" I'm able to see that "system" has a red switch (so it's not mounted.) I can turn it on, and it stays on persistently while in the recovery mode, but when I've attempted to reboot the tablet either to the ROM or directly back to recovery, the "system" is unmounted again.
This is a summary of what I've done to the tablet, at first I was just trying to get the katkiss ROM according to the thread referenced below. After a few steps I realized I was in trouble and started trying to fix the tablet with anything that would work.
http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
Here is the log I made of what I did to the tablet. Maybe something here will explain the issues I'm having.
It's not completely comprehensive since I realized too late that I should have documented everything I did.Backed up in TWRP
Flashed Hairybean http://forum.xda-developers.com/showthread.php?t=2407248
Updated TWRP to 2.6.3 as suggested #543 http://forum.xda-developers.com/tra...opment/rom-t2817919/post56681951#post56681951
Tried to flash katkiss http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
When katkiss failed, tried grimlock kernal according to #543 http://forum.xda-developers.com/tra...opment/rom-t2817919/post56681951#post56681951
That seemed successful.
Rebooted to twrp recovery (password required)
Searched about password, clicked cancel, attempted to format data but failed.
Attempted to clear data through fastboot according to: http://android.stackexchange.com/qu...-re-partition-internal-storage-to-get-it-back
Couldn't get any ROM to work
Decided to try from square 1 to get virtuous prime to work according to http://sitr.us/2012/05/12/installing-a-custom-rom-on-the-transformer-prime.html
Cleared data through fastboot in system, recovery, userdata, boot, misc, and cache.
Flashed clockworkmod
Flashed virtuous prime with fastboot -i 0x0b05 flash system
fastboot -i 0x0b05 reboot
Would not boot to OS, or recovery,
"key driver not found . . booting OS" at top left
After this, I again cleared data through fastboot system, recover, userdata, boot, misc, and cache.
I flashed the default ASUS TF201 kernel from https://github.com/namidairo/android_kernel_asus_tf201
Installed a twrp.blob that I got from a page flumpster recommended it (I can't find it now.)
Able to get to recovery, but received "unable to mount" errors whenever I did any formatting in the recovery mode.Thank you for your help. I'm open to trying whatever you think will work. I know this is a sensitive product and apparently prone to bricking but I'm really REALLY hoping that I didn't brick my new toy. I don't know if there are other diagnostic tools I'm not aware of that would give me a better read on what the status of my tablet actually is to try to pinpoint the issue or if the only way to do that is to clear everything on it and start over to be sure of what's running.
You guys are phenomenal. Thank you in advance.
aamcc
Click to expand...
Click to collapse
1. do you have now a working recovery?
2. What version?
3. What partitions do mount, what not?
4. Notice 'no keydriver found' is normal with HB but what numbers (bootloader version) are beside this notice?
What I conceive from your report's last readings is, that you 'cleared' (erased?) partitions trough fastboot. So it is clear, that they cannot be mounted, because they are not formatted.
There are several ways to fix this:
1. flash stock ROM (backlash: you will be set back to stock BL, 'recovery', boot, system and data).
2. Try to flash any custom ROM (for a start: KatKiss 4.4.4) if this don't work:
3. Find unblobbed blobs of tf300t stock ROM (search in XDA; I forgot where to find. If you don't find them, I could try to dropbox you some of mine) and flash them one after the other trough fastboot: 'boot', 'system', 'data'. Advantage of this procedure is, that you don't lose Hairy Bean bootloader, which is essentially the tf300t bootloader and enables you to load any kernel and ROM for tf300t.
Crucial is, that you have the right recovery. Namidairo's 2.5 had it's merits, but it is outdated. If you are really in Hairy Bean, then take 2.8.4.0 from here: http://www.techerrata.com/browse/twrp2/tf300t.
das chaos said:
1. do you have now a working recovery?
2. What version?
3. What partitions do mount, what not?
4. Notice 'no keydriver found' is normal with HB but what numbers (bootloader version) are beside this notice?
Click to expand...
Click to collapse
1. Yes I do
2. It appears to be hairybean but I flashed a twrp 2.5
3. When I format data and the system now that I've attempted the restoration of my back-up the "unable to mount" errors don't happen.
However, in the recovery menu when I select mount, the "Mount System" selection is off. I can turn it on but if I reboot to try to run the ROM, or even directly to the recovery again, the switch is turned off again when I check it.
4. At the recovery screen I have the following lines of text
Key driver not found . . Booting OS
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.1-20130711" A03
Starting Fastboot USB download protocol
aamcc said:
1. Yes I do
2. It appears to be hairybean but I flashed a twrp 2.5
3. When I format data and the system now that I've attempted the restoration of my back-up the "unable to mount" errors don't happen.
However, in the recovery menu when I select mount, the "Mount System" selection is off. I can turn it on but if I reboot to try to run the ROM, or even directly to the recovery again, the switch is turned off again when I check it.
4. At the recovery screen I have the following lines of textKey driver not found . . Booting OS
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.1-20130711" A03
Starting Fastboot USB download protocol
Click to expand...
Click to collapse
PLZ read my last post again (I edited it).
So you are on the right (tf300t) bootloader. That is fine. But you have the wrong TWRP. So go on and flash the recommended recovery (TWRP 2.8.4.0) and try mounting again. If it works, you can wipe boot, system and data an flash a custom ROM of your choice. Report back. Good luck!
das chaos said:
What I conceive from your report's last readings is, that you 'cleared' (erased?) partitions trough fastboot. So it is clear, that they cannot be mounted, because they are not formatted.
There are several ways to fix this:
1. flash stock ROM (backlash: you will be set back to stock BL, 'recovery', boot, system and data).
2. Try to flash any custom ROM (for a start: KatKiss 4.4.4) if this don't work:
3. Find unblobbed blobs of tf300t stock ROM (search in XDA; I forgot where to find. If you don't find them, I could try to dropbox you some of mine) and flash them one after the other trough fastboot: 'boot', 'system', 'data'. Advantage of this procedure is, that you don't lose Hairy Bean bootloader, which is essentially the tf300t bootloader and enables you to load any kernel and ROM for tf300t.
Click to expand...
Click to collapse
Isn't this a problem? Do I need to downgrade first like the disclamer on http://forum.xda-developers.com/showthread.php?t=2407248 which is where I went to get the hairybean recovery in the first place. It said that I have to downgrade before trying to upgrade my recovery.
das chaos said:
PLZ read my last post again (I edited it).
So you are on the right (tf300t) bootloader. That is fine. But you have the wrong TWRP. So go on and flash the recommended recovery (TWRP 2.8.4.0) and try mounting again. If it works, you can wipe boot, system and data an flash a custom ROM of your choice. Report back. Good luck!
Click to expand...
Click to collapse
Is the tf300t bootloader compatible with my tf201? Would it be better to track down the tf201 bootloader?
Solved!
Thank you so much!
I didn't entirely do what you directed me to but what you said set me on the path to fixing my problem.
First, I downgraded hairy bean with the downgrade zip at http://forum.xda-developers.com/showthread.php?t=2407248
This took me back to the twrp I had prior to installing hairy bean (which was actually 2.4.3)
I restored my original back-up.
After completing, I restarted the tablet and it started up the original Cyanogenmod 10.1-20140217-nightly-tf201
This will work for now. Another weekend I may give it another try but I'm too relieved to go for it again. My bluetooth will probably still not work so I'll likely be in the market for another new ROM soon.
Huge thanks for your quick response and your suggestions!
aamcc
aamcc said:
Thank you so much!
I didn't entirely do what you directed me to but what you said set me on the path to fixing my problem.
First, I downgraded hairy bean with the downgrade zip at http://forum.xda-developers.com/showthread.php?t=2407248
This took me back to the twrp I had prior to installing hairy bean (which was actually 2.4.3)
I restored my original back-up.
After completing, I restarted the tablet and it started up the original Cyanogenmod 10.1-20140217-nightly-tf201
This will work for now. Another weekend I may give it another try but I'm too relieved to go for it again. My bluetooth will probably still not work so I'll likely be in the market for another new ROM soon.
Huge thanks for your quick response and your suggestions!
aamcc
Click to expand...
Click to collapse
Glad I could help you, even when you reverted to a stone age ROM; this is J for Jelly Bean and now we have L for Lollipop; and that is running really fast on tf201.
das chaos said:
Glad I could help you, even when you reverted to a stone age ROM; this is J for Jelly Bean and now we have L for Lollipop; and that is running really fast on tf201.
Click to expand...
Click to collapse
Yeah, I definitely think my tf201 is laggy in a lot of places it shouldn't be and there are some bugs I'm not a huge fan of. If you have one off the top of your head or easily accessible, I'd be interested to be directed to a thread that would get me updated to lollipop. I'm a tad gun-shy to pursue ROMS I find on my own after what felt like a near miss with this fiasco.
aamcc said:
Yeah, I definitely think my tf201 is laggy in a lot of places it shouldn't be and there are some bugs I'm not a huge fan of. If you have one off the top of your head or easily accessible, I'd be interested to be directed to a thread that would get me updated to lollipop. I'm a tad gun-shy to pursue ROMS I find on my own after what felt like a near miss with this fiasco.
Click to expand...
Click to collapse
If you want to lollipop, you should read that:
http://forum.xda-developers.com/transformer-prime/help/katkiss-t2961256
Just an updat in case anyone stumble on this, I followed the thread supplied by daschaos and successfully installed katkiss.
Thanks for the help!
Sent from my TF201T using XDA mobile app
aamcc said:
Just an updat in case anyone stumble on this, I followed the thread supplied by daschaos and successfully installed katkiss.
Thanks for the help!
Sent from my TF201T using XDA mobile app
Click to expand...
Click to collapse
Have fun and don't be shy to ask in case of trouble.
Hi guys!
I somehow messed up my system with LSPosed in Gravitybox. A conflict made my phone unworkable (screen just kept flashing). No worries since I kept a Nandroid. After just putting this back (I ticked literally ALL the boxes) my phone goes trhough the OnePlus-loader (dot turning into square) and then says only "turning off" in the screen. Nothing else works. So I can only re-access the device via PC-Terminal in TWRP.
Fact is... Nandroid was taken BEFORE LSPosed was installed, Nandroid gave no errors when taking and gave no errors when "putting back". But device just kind of softbricks AFTER boot. Very strange. Any ideas?
Could it have to do with DM-Verity?
Just wondering: did anyone actually MAKE a NANDroid (ticket all the boxes) and tried to put it back? Questions:
- when putting it back: do I need all the boxes ticked, or just a few?
- when making a NANDroid - do I need to disable PIN, fingerprints etc.? Or can it stay active?
- did anyone succeed so far? - I am wondering why mine doesn't work?
Please share your experiences!
Can confirm neither my Nandroid backups are working.
Dunno if any security pin or measure needs to be disabled first, but it shouldn't.
So far, the most safe way I've found to make a full device backup, is through adb:
While booted in TWRP use the adb commands:
Bash:
adb shell
ls -la $(find /dev/block/platform -type d -name by-name)
to list all partitions.Then you can use
Bash:
mkdir /sdcard/PartitionsBackup
dd if=/dev/block/sdc"partition number" of=/sdcard/PartitionsBackup/"partition name".img
to backup every partition in your internal storage.To flash them back you can use fastboot:
Bash:
fastboot flash "partition name" "partition name".img
# Example
fastboot flash boot boot.img
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Can anyone help me in overcoming that kind of a problem .?
I've tried recovering with TWRP, I suspect the problem there is encryption, because when I factory reset the data, I can start fresh.
If you just want to have a working phone, try doing a restore and factory reset (also try reformatting the data partition if a factory reset does not work).
Just let us know if this worked for you.
exis_tenz said:
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Click to expand...
Click to collapse
I've created a Tool that could help, if you're still able to backup the original working firmware.
Anyway, I personally suggest to go with multiple type of backups (TitaniumBackup + Nandroid + PartitionsBackupper) first.
And when it's time to restore, wipe everything with the stock recovery and start fresh. Restoring the userdata partition for last, checking if everything works before flashing it.
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Raygen said:
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Click to expand...
Click to collapse
As i always say: Dont flash around without backups
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
4th factory flash???? I think u shouldnt flash somerhing anymore
Well, when I started with this phone, I made a NANDroid of stock rom, just plain, rooted. During the adventure setting it up, I kept making NANDroids.
Then when I was done (phone in use for 2 days) I installed LSPosed and Gravitybox. WARNING: if you mod the clock position in Gravitybox to middle: your phone will not work anymore (some framework error I guess). Then I decides to put back a 2 hours before made NANDroid back... Which got no errors when making and none when putting back... But the phone bootlooped. Actually it started through the loader, started Android and then only showed "switching off" in the screen. Which it didn't.
Then I needed a factory flash. The first factory flash gave me a "serial nummer incorrect", the second one a battery drain (no sim, wifi and bluetooth off, lost 50 percent battery in 9 hours without finding out what caused it). The next factory flash worked without the serialnumber error but also gave the battery drain AND did not let me enter a pinlock neither a fingerprint.
So tomorrow we'll try again.
What I noticed that even when a factoryflash @oneplus servicepoint was done... Some data survived (!) in the phone (which shouldn't). I still had a TWRP-folder there so I guess it's like more junk just survices. That probably causes all the trouble.
It's time OnePlus releases the firmware!
I've been in the same situation (even twice ) For me just deleting the Gravitybox.apk from system folders did the job.