I wanted to root my Transformer Prime TF201 so I could use busybox. However, no exploits exist for the .21 firmware.
I unlocked the firmware, intending to use a rooted .21 rom. I wasn't able to backup using clockworkmod recovery, which I read was because I encrypted my device.
I couldn't find anyway to decrypt it, so I tried to reset to factory settings, which seems to have made something go horribly wrong, clockworkmod cannot mount /sdcard, and I can't seem to ADB into clockworkmod.
When I boot, it just goes straight to clockworkmod.
Is this recoverable, or am I left with an aesthetically pleasing brick running clockwork mod, only a week after getting the device?
q.q
Any help at all is appreciated, I'm in a sorry state, and being new to this, I am lost as to what to do.
Thanks in advance.
Okay, thanks to the excellent support of the guys on IRC, I've recovered using option 1a- the 'three thuds' sound was Windows' not so stable USB drivers choking.
I'm no expert at this but this might be the "recovery" brick i've seen some people have. Check this post and see if u find something helpfull. http://forum.xda-developers.com/showthread.php?t=1514088 or head to the irc chat and ask for help there Alot easier to help "live". More info here http://forum.xda-developers.com/showthread.php?t=1367016
check out option 1a in the link McT posted
[Moved to top]
Related
Well guys actually I did a kind of a mess. I dumped the original recovery when I bought the phone and today I flashed it back just to see if the backup was fine (I was researching the yaffs filesystem and the dump seemed strange, phew).
Well it was. I didnt knew that original recovery would delete installed apks as well as settings etc, without even asking.
So now the phone is booting fine, stock recovery, stock system but no launcher cos I deleted LG Home (how stupid).
Is there a way to open the settings? That way I can enable usb debug mode and use adb shell.
Any help is much appreciated, and sorry if this was already asked but I did not know what to search for this specific case.
PS: LG tools arent helping. The updater keeps telling me the system is updated and refuses to flash it. Even the recovery mode of the tool acts the same (Did they even know the difference between update and emergency recovery?)
PS2: I hope to solve this problem before LG releases Gingerbread lol
Thanks in advance!
EDIT:
Well I found it was easier to flash a stock rom with KDZ Software Update. I couldnt wait. Worked like a charm. Sorry for filling forum database with auto answered question.
Just an advice, get rid of that damn stock recovery and never go back!
This thread can be closed, deleted. Thanks.
Hey everyone,
Have Prime with .21 Firmware
Did/do NOT want unlocked bootloader, but I want the root.
Downgraded the Prime to the .15
Rooted it using the ViperMod
-Now this next part if it doesn't make sense I blame it on me being sick, and it being late here.-
So, it wasn't offering the OTA .21 update to me after this.
I read that wiping the cache was a step that I may have missed.
From my experience with tinkering with the old Galaxy S and rooting/throwing on custom roms I remembered that CWM is the way to go for this!
Puts on Rom Manager
Flashes CWM and then the new CWM Touch after that.
Tries to reboot into recovery mode so that I can do the wipe.
Doesn't work from manual hard reset, adb commands, or from the Rom Manager UI.
Now I just want to get rid of CWM and go back with stock recovery, and then just push the .21 blob on there instead.
Please tell me I didn't somehow unlock my bootloader... >_< I thought I would have had to agree to something to do that.
If I didn't, how do I pull the CWM off, but keep the root and the bootloader UNLOCKED.
Yes, I have been hunting through the Forum, and through Google. I'm finding things that are close, but just far off enough that I'm not sure the answers are applying to this situation.
(By the way, if I did something completely stupid in my thought process let me know... but I'm still going to bank on being sick and tired )
You cant install cwm unless you unlocked your bootloader... So im not sure how you flashed it with rom manager. Are you sure you didnt select the option to unlock and install cwm in viperMOD?
Positive that I didn't. Mainly because it mentioned the unlock tool in the same line as CWM.
Everything that I did after following Wolf's directions was through Rom Manager (aka the CWM install and ROM backup).
another advice: don't think "cwm" when you want to install asus blobs
still, everything i read so far says that to install cwm you need unlocked bootloader.
Sent from my Transformer Prime TF201
bk201doesntexist said:
another advice: don't think "cwm" when you want to install asus blobs
still, everything i read so far says that to install cwm you need unlocked bootloader.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
I don't think that I was "thinking" properly >_<. But I will make sure and keep that in mind.
That's what I've read too. What's strange is that, unless some program did it without telling me that it did it, I avoided anything that looked like it said "unlock".
So, just did some more Google searching and came across this link: http://forum.xda-developers.com/showthread.php?t=1575138
(tl;dr Don't need to unlock bootloader, just need to have root)
I know it's not a TF201 thread, but should the principles still apply (you actually have to read the thread to see what I mean).
Alright, after a little more reading, investigating on the prime, and putting a little more thought into it I think I've come to believe that (even though OM Manager thinks it is) CWM isn't actually installed on the Prime. I'm thinking that when ROM Manager supposedly flashed it, it only installed a random file or two that it could. the ONLY CWM folders I could find in ANY directory on my prime was in the sdcard folder and the clockworkmod folder.
I just deleted that, restarted, and it isn't broken... yet.
So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
LivioDoubleFang said:
So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
Click to expand...
Click to collapse
Not sure what recovery you have now but I suggest you go here >>
http://forum.xda-developers.com/showthread.php?t=1615990 and install twrp recovery through the fastboot method. Boot into trwp recovery. After that, download the nvflash files from here http://forum.xda-developers.com/showthread.php?t=1774352
Not saying you should use nvflash at this point but the file also contains a known good adb.exe file. Unzip the file and while in that directory press and hold the shift button while right clicking the mouse. This will bring up a menu select open command prompt here.
Put your rom into the same folder as the adb.exe then in the comand window type adb push /name of your rom.zip /sdcard/ if this doesn't work use /sdcard/media At this point you should be able to install the rom. As for the rom, a good starting point would be androwook rom since it seems to install quite easily (do not unzip). Also when you are performing commands in either fastboot or adb, it is best to copy (control c) from the webpage then in the command window right click and paste, this eliminates errors. Having the files you are flashing in the same directory of fastboot or adb eliminates the need to type pathways, this is where many people run into issues, 1 wrong letter make everything not work....
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
LivioDoubleFang said:
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
Click to expand...
Click to collapse
Most people don't have a stock backup since once you are unlocked, trying to install the ota update can make the tablet inoperable. So basically when Asus updates the software then the developers here pick up the stock rom and enhance it. This goes anywhere from the base stock rom with root up to taking the rom and customizing it with options, kernel changes and such. The only thing I will say about changing kernels is only use kernels that were developed for the particular rom or you will have trouble. Kind of like taking a Ford motor and trying to mate it to a chevy transmission.
If you do change roms, make sure you wipe cache, dalvik and do the factory reset from within twrp. When you become comfortable, I suggest looking at the NVflash thread in the dev section. This will provide you with a bit of assurance that you can recovery from most software brick situations. Read over the instructions a few times before you go a head and take some time to read through the thread so you know what could potentially go wrong. It really isn't that difficult to do but you should be well informaed before proceding. If you need anything else don't hesitate to ask
Another thing that i find helpful, keep a stock rom in your sdcard. When i semi-bricked my 201, i was able to flash the stock rom using CWM, then do a factory reset. Once back to factory, i was able to boot and start over again.
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
mroshaw said:
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
Click to expand...
Click to collapse
you could use fastboot method: http://www.teamw.in/project/twrp2/93
also it is recommended to use AndroidRoot bootloader: http://forum.xda-developers.com/showthread.php?t=1774352
Thank you for the reply. I'm not that comfortable with that level of tweaking and I had really hoped that Goo Manager would sort me out. Is it a known issue that Goo Manager cannot install TWRP if another recovery is present?
If so, I'll give the fastboot method a go at the weekend.
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
Yeah, not a particularly helpful response to be honest. If you don't know the answer to the question, probably best not to post a reply.
emptyshell said:
The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid
Click to expand...
Click to collapse
Indeedy - thanks for that.
The Androwook flashing process felt really safe and gave a lot of less techy Prime users access to a ROM that transformed (excuse the pun) the TF201 into a usable device. I don't think a lack of a full understanding of the inner workings of the technology or process should stop people from using it or from asking questions. Otherwise, what's the point of the forum?
If anyone is able to answer the question as to why Goo Manager will not install TWRP on top of an existing CW recovery, I'd greatly appreciate it. :good:
emptyshell said:
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Click to expand...
Click to collapse
I had problem with GooManager too, so I flashed TWRP manually via fastboot.
Be aware her if you want to use twrp backup/restore you'll probably need modified bootloader as stated above. Twrp uses .img backup format, not blob, and modified bootloader can handle them correctly, which is not the case of original one.
You could have a non functional restore process for /boot. One solution could be to reflash the ROM after the restore in that case, so if you don't want to modify the bootloader always keep the zip of the ROM that you backup.
Thanks all.
I'll go the manual route then, I think. Be as well to go the whole hog and do the modified boot loader too, by the sounds of things.
Thank you for your useful responses and input - much appreciated.
Couple of things to be aware of, firstly, fastboot method for installing twrp not too hard, read the instructions a couple times before you proceed. If you do run into problems, go back to the forum and ask, don't try to "fix" it with a method that hasn't been proven. Secondly, when you install twrp, you can forget you cwm backups, they are now worthless. That being said, make a back up in twrp at your earliest convinence.
Third, read the instructions, most are pretty clear but if you don't understand something ask before you start you can save yourself a lot of trouble.
I recently rooted my phone and I would like to make a backup before I mess around with a few things. The phone I have is a Galaxy K Zoom. It's running 4.4.2 Kitkat.
My problem is that CWM and TWRP don't seem to work. CWM tells me that my phone is unsupported, and TWRP says it will backup, but when it reboots to create it, I get an error. Is there another recovery app that is available? Or am I stuck having to restore to stock if I soft brick it? I'm ok even using ADB and/or Odin to flash it back to the phone, but I just need to make a recovery to start with.
Also, I have a recovery file that I found in a rooting thread for my phone. Won't that recovery file restore to their phone's settings? How can I make my own? I'm sort of a noob at this, so sorry for asking.
Thanks in advance and I really hope I get get some direction here. I'm more than willing to read through threads, I just don't know if I'm searching for the right terms. I noticed that there have been some posts on this before and there were no replies. Hopefully I can get one!