I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
xFoCaLx said:
I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
Click to expand...
Click to collapse
Fair play, at least you tried and you probably learnt a lot in the process.
You have nvflash backups so don't panic. It is fixable.
I am going to send you my google talk address now over PM. Add me by going to gmail on your PC in your browser and adding me in the bottom left hand corner to chat. I will try and talk you thru it.
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
puntxo said:
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
Click to expand...
Click to collapse
This was a new one on me and I have no idea how he got himself into it but we managed to fix it anyhow.
He was the first person I have helped tho that needed to restore unlock-token.img, factory-config.img and bricksafe.img as he had some error saying failed to inject certificate, unrecoverable bootloader.
As long as you have all your nvflash backups you will be fine amigo.
Related
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
I would get nvflash set up with bekit's images and flash that to get yourself back to a working stock image. Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=861950
After that, put Clockworkmod ( v .8, get it from development forum) on it and repartition your sdcard to 2048 and 0 then you should be ready to flash.
Then get a ROM from the development forum here, there are some based off cm7 (gingerbread builds).
I was hoping not to have to use NVflash cuz people report problems with the boot loop, however I havent found any other option so far so I guess i'm trying that. Thanks for the link.
Xxlgeek,
Every time I hear boot loop I think re-partition -- because most of the time that
seems to fix the problem.
I agree you should NVFlash to get a stock version working. Then install CWM so
you can partition -- and the do the Fix Permissions, Wipe Dalvik Cache, Wipe
Cache, Wipe Factory Data.
With that I would try to wind up with a stock machine and let it OTA up to 3588.
I wouldn't load another Alternate Rom until I knew my tablet is working good and
until I know a lot more about the roms and how to work with the G-Tablet.
IMHO.
Rev
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Xxlgeek,
If it didn't work, I would erase the Cyanogenmod 7 file -- and I would go back to a stock rom until I could make sure all the hardware is working right and the system
is stable.
When you know the tablet is good and stable, you can always download and re-do.
Rev
Xxlgeek said:
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1021978
you are not alone...
it may have to do with the boot loader .... further investigation needed. CW does not replace this but the stock does I have been running the old one since december on my personal tab. but most of these woot pads are updated .... hmmmmmm
Xxlgeek said:
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Click to expand...
Click to collapse
Which version of CM7 are you running?
jivy26 said:
Which version of CM7 are you running?
Click to expand...
Click to collapse
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Just throwing this out there. I bought 2 from Woot myself. On my first G-Tab I had the same issue with every single ROM I tried. I finally used NVFlash to go back to stock and everything was good again. I then flashed to the G-Harmony Gingerbread ROM and it worked and still runs like a CHAMP. Now, I finally get the other G-Tab out and start to go through the same routine as the first and it's been a no go repeatedly. I have mostly been trying with the Cyanogen 7 Final ROM to no avail and even with the G-Harmony. Going to try NVFlash on number 2 tab and see what the result is and will post back in a bit with updates.
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
tunez23 said:
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
Click to expand...
Click to collapse
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Did you extract both archives to the same directory on your computer?
akodoreign said:
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Click to expand...
Click to collapse
2 partitions are reversed and Gingerbread roms don't like it. Using bekits original nvflash files will fix the partitioning permanently as far as flashing between froyo and gingerbread.
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Edit.....This is not all tablets. I'm guessing around 30% or so have the 2 reversed partitions but it seems 50% of the woot tabs. Helped fix many of these on irc in the last 2 weeks
KrazyOne7 said:
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Click to expand...
Click to collapse
Having the same problem too!! Any help would be much appreciated.
Tried wiping everything with FORMAT.zip from another thread, and get and error for unknown device when running that *.bat file.
This newbie needs some serious help!
Locked bootloader??!
thebadfrog said:
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Click to expand...
Click to collapse
I think I must have the locked bootloader, but tried both Gojimis's fix and nvflash fix and get the error as mentioned above.
So I am getting nowhere, won't go past the "booting..." splash screen to install any of the update.zip files from the microSD card.
Help!
K J Rad said:
Did you extract both archives to the same directory on your computer?
Click to expand...
Click to collapse
Yes, I extracted both the gtablet and the windows zip files.
KrazyOne7 said:
Yes, I extracted both the gtablet and the windows zip files.
Click to expand...
Click to collapse
Me too, and still getting the error "nvflash configuration file error: file not found Press enter to continue:"
Are they in the same directory. If they are not then nvflash can not find the files to flash. Both zips have to be unzipped in the same directory and the driver has to work. You must be able to see the tablet from the computer when you boot into apx mode. APX mode is power/vol- NOT power/vol+
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
cherokee990 said:
Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
Click to expand...
Click to collapse
Cherokee.. I am pretty busy at the moment working on Android TV boxes but I can see that you have nflash backups so everything should be fine.
I will pm you my Google talk address and add me on there with a message saying who you are, this is a bit too complicated to go through on the forums.
Can't promise you I can help you straight away but I will get around to it in the next day or two.. I'm UK time by the way.
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.
For some reason my Prime decided to be a pain tonight. It was working fine then it suddenly crashed and rebooted but would get stuck on the boot screen. Tried to boot into recovery and got the android dude with the red triangle over him. Still had fastboot so was able to flash my blob. So I'm back up and running, but recovery is still hosed. How do I go about fixing this. I am unlocked. I used to be on crombi-kk but went back to stock a few months back. That's probably when my recovery got hosed. I'm sure it's not that complicated to flash the recovery, but I just don't know the commands to use. Any help would be appreciated.
I found this thread http://forum.xda-developers.com/showthread.php?t=1927818 but it uses the unblobed 10.4.2.15 and I'm on 10.4.2.18. I have no idea how to unblob my own blob. I've tried to but can't figure it out.
Update: Figured out how to unblob the Asus stock blob and tried to flash it in nvflash. Didn't flash anything else. Rebooted and tried to get into recovery with the same results.
Update: 2 Good morning. Tried reflashing everything this morning and I can boot fine but recovery is still hosed. Any other way to rebuild stock recovery or do I need to install a custom recovery.
Final Update: So I feel like a complete Newb right now. Did some research on the stock recovery and guess what that's what you should get. I didn't have any files and such on a SD card so there were no options under recovery. So all is fine. I will probably replace stock recovery with another just so I have more options anyway.
JoanneDisFan said:
Figured out how to unblob the Asus stock blob.
Click to expand...
Click to collapse
Hello there
What do yuo mean exactly by that? And how did you "unblob"'ed it?
I'm collecting all I can for unbricking my own prime