Not sure how, and more importantly, how to fix it. Previously, I unlocked with the Asus tool, did the sparky root method, installed the most current Prime version of CWM, then flashed JellyBro. Wanted to flash a new ROM last night. I booted into CWM and tried to do a backup, but got some kind of error about not being able to back up the boot image, or something like that. Not wanting to flash a new ROM without a backup, I just restarted, but now it just sits on the EEE Pad splash screen. If I hold down the power button, it restarts but still stays on the splash screen. I had to hold down the power and both volume buttons for a long time to get it to turn off and stay off without restarting. So, what do I do?
mrw1215 said:
Not sure how, and more importantly, how to fix it. Previously, I unlocked with the Asus tool, did the sparky root method, installed the most current Prime version of CWM, then flashed JellyBro. Wanted to flash a new ROM last night. I booted into CWM and tried to do a backup, but got some kind of error about not being able to back up the boot image, or something like that. Not wanting to flash a new ROM without a backup, I just restarted, but now it just sits on the EEE Pad splash screen. If I hold down the power button, it restarts but still stays on the splash screen. I had to hold down the power and both volume buttons for a long time to get it to turn off and stay off without restarting. So, what do I do?
Click to expand...
Click to collapse
Looks like this could help: http://forum.xda-developers.com/showthread.php?t=1662158
Next time I recommend using TWRP and not CWM.
qery said:
Looks like this could help:
Next time I recommend using TWRP and not CWM.
Click to expand...
Click to collapse
Yeah, people have been recommending ditching CWM for TWRP to me for a little while, now, and I continued sticking with it because I was so familiar with it and didn't want to bother with anything else. Didn't know there was a problem with the current version for the Prime. But yeah, I think I'm definitely going to make the jump to TWRP if/ when I get my Prime back up and running.
The biggest issue for me is, I'm not very familiar with actually using ADB/ command prompts for any of this stuff. Every device I've unlocked/ rooted, I used an automated script to do it, so I didn't have to bother with any of that. I also did read over the stuff about nvflash, but I couldn't really make heads or tails out of the instructions, so I thought it'd be best for me to not tamper with it. Figured I was playing safe with my Prime, so I wasn't concerned, anyway.
I believe I can still access fastboot on my Prime (I don't technically know what "fastboot" is or does, though); if I power it on holding down the power and volume down buttons, I get three options (wipe data, fastboot USB mode, and reboot), but I haven't tried connecting it to a computer yet. I'll take a look at your link.
Hm. So from what I gather, I need to get a new blob file; the one in the link you provided talks about getting it from the Virtuous Prime ROM, but the reason this concerns me is, VP seems like a stock ROM, and the unbricking thread notes that if you apply a stock blob file after installing CWM, you get an unrecoverable brick. So... not sure if I should use the Virtuous Prime blob file, or what? I don't want to permanently break my Transformer Prime. :/
mrw1215 said:
Hm. So from what I gather, I need to get a new blob file; the one in the link you provided talks about getting it from the Virtuous Prime ROM, but the reason this concerns me is, VP seems like a stock ROM, and the unbricking thread notes that if you apply a stock blob file after installing CWM, you get an unrecoverable brick. So... not sure if I should use the Virtuous Prime blob file, or what? I don't want to permanently break my Transformer Prime. :/
Click to expand...
Click to collapse
Gosh.... Stock blob = Asus blob downloaded from Support Center...
Just follow the instructions.
Striatum_bdr said:
Gosh.... Stock blob = Asus blob downloaded from Support Center...
Just follow the instructions.
Click to expand...
Click to collapse
Oh, okay, so the VP blob isn't "stock" then? I guess I'll give it a whirl then. Probably tomorrow, though, as I don't have much time today.
I'm not so sure I've set up fastboot on my computer correctly... I followed some instructions on a random site I googled, but I don't know if it worked. I put my Prime in fastboot mode, and when I connected it to my computer, Windows found and downloaded a "Fastboot" driver. But when I opened a command prompt and entered "fastboot devices", nothing happened.
Ok you sould use Universal Naked Drivers from developer forums.
VP is based on stock rom, but it is made for unlocked devices, so it does not hardbrick you (I think it doesn't flash bootloader).
You need to have files Android Platform Tools (from Android SDK) installed (or copied in folder). To this folder you copy files needed to be flashed (mine is c:\program files (x86)\android\android-sdk\platform-tools\). Then you open cmd from there (in explorer press Shift+Right click and select Open command window here).
Now reboot tablet while holding VolDown and select Fastboot (usb icon). Next connect to pc.
After that you should be able to use fastboot commands.
Sent from my Transformer Prime TF201 using Tapatalk 2
Okay, thanks everyone, looks like I'm back up and running!
Just a question; am I reading it right that with the newest version of TWRP, you can't do backups and restores without having done that nvflash thing?
Hm. This is probably unrelated, but... I'm not sure TWRP is working correctly. I installed it via GooManager after I got back up and running (I had tried to flash it via fastboot when unbricking, but for some reason, it didn't take, and I was still on CWM). Anyway, in TWRP, when I do my wipes, it doesn't appear to actually have any effect, even though it goes through the process and says they were successful. Also, when I try to install a ROM, the zips don't appear on the sdcard folder in TWRP, even though they are, in fact, on there.
Putting them on an external card allows TWRP to see them and flash them, but because TWRP apparently isn't actually doing the wipes (even though it says it is), I'm having trouble flashing other ROMs (because I'm basically "dirty flashing" from Virtuous). In particular, I'm trying to flash Blackbean; after the boot animation, it goes through the "Android is upgrading" thing for what I assume is still the Virtuous Prime stuff, then I get an error about system.media (something like that) not responding, and then it quickly goes back to the boot animation and continues to loop from the aforementioned error to the boot animation over and over until I force turn the tablet off.
Anyone know what the heck is going on? Why does it seem like TWRP isn't actually wiping the tablet, and why is it not recognizing the zips in the internal sdcard folder?
mrw1215 said:
Okay, thanks everyone, looks like I'm back up and running!
Just a question; am I reading it right that with the newest version of TWRP, you can't do backups and restores without having done that nvflash thing?
Click to expand...
Click to collapse
Yes. If you don't want nvflash, use older version - in OP it says that 2.2.1+ needs nvflash bootloader.
mrw1215 said:
Hm. This is probably unrelated, but... I'm not sure TWRP is working correctly. I installed it via GooManager after I got back up and running (I had tried to flash it via fastboot when unbricking, but for some reason, it didn't take, and I was still on CWM). Anyway, in TWRP, when I do my wipes, it doesn't appear to actually have any effect, even though it goes through the process and says they were successful. Also, when I try to install a ROM, the zips don't appear on the sdcard folder in TWRP, even though they are, in fact, on there.
Putting them on an external card allows TWRP to see them and flash them, but because TWRP apparently isn't actually doing the wipes (even though it says it is), I'm having trouble flashing other ROMs (because I'm basically "dirty flashing" from Virtuous). In particular, I'm trying to flash Blackbean; after the boot animation, it goes through the "Android is upgrading" thing for what I assume is still the Virtuous Prime stuff, then I get an error about system.media (something like that) not responding, and then it quickly goes back to the boot animation and continues to loop from the aforementioned error to the boot animation over and over until I force turn the tablet off.
Anyone know what the heck is going on? Why does it seem like TWRP isn't actually wiping the tablet, and why is it not recognizing the zips in the internal sdcard folder?
Click to expand...
Click to collapse
Try using older version of TWRP.
And in case of problems, report in twrp thread with a logcat.
Related
Hey all. I just got a new G Tablet and am trying to install CM7 I was following the instructions to the letter from (Since I an't post links, just google this) Cyanogenmod G Tablet Wiki Full
I got through the 'Installing ClockworkMod Recovery' part and everything appeared to finish successfully.
After rebooting the device, I tried to boot into Recovery to install CM7 and the device just freezes on the ViewSonic splash screen. The screen says 'Recovery key detected Booting recovery kernel image', but it just sits there.
I am able to boot the device into the stock OS, but I can no longer get into recovery.
What can I do?
Tap UI Version: 1,2-4349
Kernel Version: 2,6,32,9-00001-g0e0c333-dirty
Build number: FRF91
Thank you in advanced for your help. Please let me know if there is any other information you need about my device.
Andrew
The key to your post is
Tap UI Version: 1,2-4349
Click to expand...
Click to collapse
You're on the 1.2 bootloader, and CWM .8 will not work on it. There is a versio nthat WILL work, but I, unfortunately don't know the exact link to provide for you. I'll attempt to look it up and get back to you, though.
basically, your G-Tablet, was at some point, updated with the most recent OTA update provided by viewsonic. The update was pulled 24 hours after it was released. You're not lost with 1.2...you have many options. You can either stay on 1.2 and flash any of the many 1.2 roms...some are listed in the development section, others can be found on "another" forum.
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Download
clockworkmod v3.0.2.8 (1.2 branch / NIA rev5) Link: http://www.mediafire...2flqn8b10ebcq44
md5sum: ac4d728d74a6b608cce588d2649e79f3
(updated on 5/15/2011)
clockworkmod v3.0.2.8 (1.2 branch rev2) Link: http://www.mediafire...x61q8jlu2dx8i9u
md5sum: 48c0c40175ab38cebc1199f9d3be8a7d
(updated on 5/05/2011)
THIS REV2 VERSION HAS BEEN TESTED MORE, but nandroid restores are not working properly. Rev5 corrects that, but I need more testers to confirm stability, please!
Many thanks to bekit and rothnic, for their work with clockworkmod!! Their documentation is what assisted me to get this functioning.
NOTE ON CWM: Do not use the Android GUI tool to wipe user data, or else cwm will get stuck in a reboot loop! If this occurs, there are two ways to fix this:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
Click to expand...
Click to collapse
TJEvans (is it ok if I call you TJ for short?) thank you very much for your help, I appreciate it very much. I'm sorry if confuse some terms here as I try to address your posts inline below, but I would definitely still consider myself a novice at this process of installing custom roms.
TJEvans said:
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
Click to expand...
Click to collapse
This is a brand new G Tablet. I litteraly got in the mail today from Tiger Direct. I'm wondering if the Clockworkmod I tried to install is responsible for the custom kernel.
TJEvans said:
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
Click to expand...
Click to collapse
I don't necessarly need CM7, but that is what I have on my Nook Color, and I really like it.
The main question I have is that right now, I cannot get into clockwork or stock Recovery at all. I do have adb working, so I would think my next steps will require me to use adb.
At the moment since I can't get to recovery I seem to be stuck. Is there a process somewhere I can get recovery working again using adb?
OK...let's try something. It looks like you may actually be in stock recovery, but there's nothing for it to recover.
do you know of a way to get a file and a folder onto your internal SD?
if so, let's edit the instructions to be able to flash to 3588 stock...
What you need:
1. A stock 3588 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/...-3588-user.zip)
2. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
Click to expand...
Click to collapse
if yo ucan get those on the SD, then when you reboot, the stock recovery will run and install stock 3588 1.1 based rom and recovery, then you can install your CWM .8.
I have never used NVFlash or ADB, or APX...I have no experience with them. I'm just here helping people that have compatibility issues between 1.1 and 1.2 bootloaders.
After all, the key to fixing problems, is to first find out what the problem is...
I wish I could help more, but I've seen more and more people softbrick their g-tabs by using NVFlash than anything else. I'm not ready to go messing around with my own root files, yet.
If you can get that file, and that folder onto your SD, then stock recovery will automatically recognize it and run it...
I may have just really screwed things up. I ran 'adb reboot recovery' and I gets to the Splash screen with 'Booting recovery kernel image' and gets stuck. Now, I can't get into the device at all.
Also, none of the links in your posts seem to work for me.
try them from the original post, then:
http://forum.xda-developers.com/show....php?t=1039000
sorry, like I said, I'm not a techy...just a guy that doesn't like to see people suffer...
TJEvans said:
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Click to expand...
Click to collapse
It's far from being taboo since it's the honeycomb bootloader... their recovery was blue for a reason...
maybe they pulled those OTA update because they had not licensed honeycomb anyhow, 1.2 is perfectly good to install as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Ok, I was able to get the device working again using NVFlash. (http forum,xda-developers,com/showthread,php?t=861950 replace commas with periods).
Now, I have the following:
Tap UI:1,1-3588
Kernel is still: 2,6,32,9-00001-g0e0c333-dirty
I don't know anything about this kernel, or how I got it, other than maybe it came with my first errant clockwork install.
Can you give me some pointers on how I should proceed? (I would still like to get to CM7 at some point, but I don't know if I should get a different kernel or go back to the stock kernel as well)
GREAT NEWS....glad you god it running so far.
OK, that may be the stock kernel...the numbers looked familiar to me, and I've never seen the stock kernel on that report...so, I may be mistaken.
in any case, you are now back on stock 3588 1.1 bootloader...
Now, you should be able to install the CWM .8 that you tried before, and flash CM7 from there...basically, follow the guide you followed before. but this time, it should work fine, since you are on the right bootloader.
Just remember, research ANY new roms you want to try to make sure what bootloader they are on.
to P00r:
as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Click to expand...
Click to collapse
see, I didn't even know that...
The thing I'm seeing, is that Clemysn posted the BOS infromation here, and tried to emphasize that it's a 1.2 Rom...The 1.1 rom's though, do not indicate that they are 1.1 Roms. when 1.1 was all that existed, it made no difference, but now that there is another option, they should at least make sure to add "PLEASE BE SURE YOU ARE USING A 1.1 BASED BOOTLOADER BEFORE FLASHING THIS ROM!!!"
As you can see from Imarikinrat's post, he bought a supposedly factory G-Tablet with 4349 prepackaged on it...now, granted, you and I both know that it's more than likely a refurbished one, as I can't see Viewsonic intentionally releasing product with a bootloader and firmware that was pulled from their updater...
in any case. Roebeet kinda predicted that this would happen a bit. Since most moderators on XDA downplayed the impact of 1.2, it's gone fairly ignored. Think about Imaricanrat's post for a second. Had he not posted his system information there is no way that we would have known that it was a bootloader conflict. It would have been assumed that he was on 1.1 bootlaoder with a "brand new" g-tablet (seriously, man, I'd check that thing with a magnifying glass to make sure that there are no scratches or anything that would indicate that it was anythign other than BRAND NEW)
anyway...had he not posted that he was on 1.2, then who knows what advice he would have been given.
Well, now I'm back to my original problem. I cannot get into Recovery. When I start holding Power and Vol+, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
I have tried putting the recovery folder and update.zip in the internal memory, and on an sd card to no avail. Any other suggestions?
that most certainly sounds like stock recovery to me...
I'm at a loss...it worked fine for me when I flashed to 4349 from stock 3588...just ran and installed, then I ended up on 4349 stock...
you're following the CM7 install guide? Or are you trying to install CWM at this point? I never installed CWM myself, as mine came with it on it.
I'm trying to install clockworkmod so that I can install CM7. Is that the right way to do it? I know there was a stock recovery gui that I cannot get into now.
as long as the recovery folder is on the SDcard, it will automatically attempt to run it...
picture it this way...remember back in the day of windows 3.1 In some cases, if you inserted a floppy disk with a boot file on it, it would check there first, then boot from internal memory...
So, the recovery folder is telling it to run the file in it, which unpacks and installs the update.zip.
once again, though, I never installed CWM myself, but from what you're saying, it should be working.
what happens if you remove the folder and file (after running it), and attempt to go into recovery again?
When I remove the file, folder, and SD card and try to get into recovery, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
hmm...the box with the arrow and progress bar indicates that it's trying ot run something from recovery...weird..
ANYONE ELSE???
I'm not experienced enough to help...anyone else know enough about flashing CWM from stock, or flashing CM7, that can help out, please chime in.
thanks.
and sorry Imarican...I tried, but once again, no techie here.
No worries man, thanks for your help. Have a good night.
Update: Ok, I think somehow this whole process messed up the 'Recovery Partition' on my G Tablet for whatever reason. When I performed the NVFlash back to stock, it managed to 'fix' the majority of the device, allowing me to boot normally into Tap UI:1,1-3588. However that flash did not fix my Recovery Partition.
With all of that in mind, I found instructions on XDA to install 'clockworkmod via nvflash' (Since I still cannot post links, just google that and it should be the first link, also it's XDA thread 1058649).
After following those steps, I am now able to boot into Recovery which is now Clockwork Mod Recovery, and hopefully *crosses fingers* be able to flash CM7.
Given that I will probably never go back to stock anything on this device, does anyone know where I can download the 'Stock Recovery' for the G Tablet?
so is the point of this article Tiger direct sell used products as new?
so is the point of this article Tiger direct sell used products as new?
Click to expand...
Click to collapse
unconfirmed...what we know is that he had 1.2 4349 out of the box, stock firmware. There are a few possibilities. This could be a Tiger Direct return that was repackaged and sold as new. It could also be a direct from VS return that was repackaged as new, OR, VS actually sent a stock of G-Tablets to Tiger Direct that were packaged with the 4349 firmware on it.
Either way, people need to be careful when flashing roms and such. XDA has not, so far, made it clear which roms, kernels, and CWM versions are good on which bootloader. Some have been asking that devs start exiting posts to indicate which bootloader is needed for each mod, to attempt to avoid confusion.
We must also realize that new G-Tablets are being bought every day, and not every owner is knowledgable of the issues of the recent past, with VS, NVidea, 1.1, 1.2, etc. Most people probably, reasonably, assume that they can open it, root it, and start flashing whatever they want, not even aware that there is a difference.
Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.
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!
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.
I am rooted and S-Off. I am using the ViperOne custom ROM for my phone.
The end goal is for me to update my firmware, because my phone has an over 10 minutes boot time normally. (Not an exaggeration. I have actually timed it with a timer.) I read that in order to fix this, I should try to update the firmware by going to stock recovery and doing an OTA update.
My TWRP has worked flawlessly for me over the years, but for some reason it won't work anymore. It will hang on the boot screen for over an hour. After that hour, I assumed it's not slowly booting. (As a bit of background, recovery would boot quickly while my phone still had problems with 10 minute boot times).
Another piece of information is that the last time TWRP worked was when I used it to install .zip files from Titanium to get all my apps working. That worked perfectly fine, my apps got updated, and no trouble. I wish I could say what happened between then and now, but from what I can remember, I just used my phone normally, such as using web browsers and games. I don't remember messing with any system files.
I do know that ClockWorkMod recovery DOES work if I flash that, but my nandroids are all on TWRP. I have tried to flash different version of TWRP as well. It doesn't seem to matter which one I flash, my phone reacts exactly the same.
Another thing to note, I'm not sure if it's significant or not, is that when I got into hboot, I get the following message for a split second. I can't read the file names exactly, but I got the extensions. Then I get the normal screen with the vol instructions and choices to go to fastboot, recovery, etc... The message reads:
SD Checking...
Loading [(something).zip]
No Image!
Loading [(something).nbh]
No Image or wrong image!
Loading [(something).zip]
Loading [(something).nbh]
No Image or wrong image!
I hope this is a decent amount of information. I tried to include as much as I could, but if I'm missing any critical details, let me know and I will GREATLY appreciate your help!
have u tried to rewrite the image, download the new TWRP and load it via adb
Bradl79 said:
have u tried to rewrite the image, download the new TWRP and load it via adb
Click to expand...
Click to collapse
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Battletooth said:
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Click to expand...
Click to collapse
Having the exact same issue. Attempted to install twrp-2.8.6.0-m8.img using adb, but TWRP never loads. I can load prior versions but same results. Going to HBOOT I get a bunch of messages related to 0P6BDIAG.zip, 0P6BIMG.zip
and some .nbh. I think it's looking on my SDCARD for those.
If you're looking to update your firmware, you can use an official RUU to change the firmware of your phone. You can read more about it in this stickied thread in the general forum to see if it fits your needs. If you decide to do this, your phone will be completely stock after the RUU finishes running so use fastboot to flash TWRP (or whichever recovery you prefer).
Regarding the messages you see in hboot, it will always check for those files if you have an external sdcard mounted. If they are present, you will be given the option to flash the update. If not, you will get regular hboot access after the check. It is completely normal and nothing to worry about.