Related
So, after owning my Transformer Prime for about a month now, I decided to take the plunge and root it. I followed the instructions for ViperMod and had it rooted in no time. I then followed the instructions of unlocking the bootloader and finally installing OTA Rootkeeper.
I've had rooted devices in the past (Droid Incredible) and am familiar with RomManager. So I installed RomManager on the Transformer Prime. I then attempted to create a backup of my "current Rom", which is just stock ICS. RomManager prompted me to update Clockworkmod Recovery, which I did (I now have 5.8.2.0 installed). It then rebooted...acting like it was backing up my current Rom, but when I got back into RM, and clicked "Manage Backups" and there was nothing there. I tried once more with the same result, and ultimately gave up on backing up my current config.
I then downloaded Cyanogenmod 9 (nightly). I selected Google Apps and it proceeded to download. I got an error that the Google Apps portion had an error, but it seemed to work when I attempted to download it again.
I then proceeded to attempt to install the new Rom. The menu came up, asking if I wanted to wipe data and cache, wipe dalvik and backup current rom. I selected all three and hit ok.
My tablet rebooted...quickly, and did not show any signs of installing Cyanogenmod. Sure enough, I got my stock ICS...no Cyanogenmod. I tried again...same thing. I tried a third time, and RomManager hung when I tried to select Ok after the options of backing up, etc. Ultimately I got the error popup, asking if i wanted to wait/report/ok. I hit ok.
I then...very stupidly in retrospect...performed a factory reset from within the phone's settings menu (something I've later read is a big no no). This time, when my phone rebooted, it went straight into Clockworkmod Recovery, which is where I am now. Stuck. I've read a ton and tried everything but had no success.
Strangely, I can find the cyanogenmod file by navigating through "install zip from sdcard", then "choose zip from sdcard", then "clockworkmod", then "download", then "get.cm", then "get" and finally "update-cm-9-20120301-NIGHTLY-tf201-signed.zip". And it allows me to update using this file...even giving me the message "Install from sdcard complete"...but nothing happens. I'm still stuck in Clockworkmod.
If anyone has any advice, I'm begging for your help. Really hoping I didn't ruin my brand new tablet...
Thanks.
only thing rom manager is gold for on the prime at the moment is getting the latest CWM version. other than that, trying to flash a rom, reboot into recovery, or backup doesn't work in rom manager for prime. everything needs to be done through CWM itself. whether flashing a rom or making a nandroid backup. so you have to manually go into CWM and try flashing from there. did you make sure the roms were stored on internal memory to flash(I believe it can only be done on prime this way at the moment)? try a different rom as the CM9 has alot of bugs n issues at the moment. try flashing virtuous rom or a stock modified rom from developement.
also check out developement section for a thread called the Di's n Donts of unlocking and thread called how to or not unbrick your prime. answers you seek are in there.
See my unbricking thread
http://forum.xda-developers.com/showthread.php?t=1514088
Thanks so much for your help guys!
to demandarin: Unfortunately the only ROM I downloaded before everything went haywire was the nightly cyanogenmod 9 from yesterday. And as I explained, that ROM doesn't seem to be flashing for me... I've tried downloading other ROMs onto my SD card, but I can't seem to get my Prime to recognize the SD card in CWM, and I can't figure out any way to get ROMs onto my prime...now that its stuck in recovery. Do you know if I can load ROMs onto my Prime at this point?
to Diamondback: I read your unbricking thread and its given me some hope. It sounds like I'm falling into the "1a" category. I'll have to bunker down tonight and see if I can work through those instructions (I have no familiarity with ADB at this point, which is my main concern). Anyway, I very much appreciate you pointing me in the right direction.
I am curious though, is there some place I can look for clarification on what works in RomManager and what does not? None of that was made clear in the app itself, so I just assumed it was fully functional, like it was on my Dinc. Now I'm paying the price...
Thanks again.
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
demandarin said:
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
Click to expand...
Click to collapse
Thanks, but I actually do have the latest version of CWM (5.8.2.0), according to the link you provided. The thing is, I'm just very unfamiliar with CWM, or really any recovery software. The link you posted notes the following improvements:
-Possibly fixes bricks (by properly restoring boot.img)
-Correctly comes with Staging/System unmounted
-Nandroid Restores properly the boot.img (of backups created with this CWM). This means no more issues when restoring a Rom if you are coming from another from (for example, if you are restoring Virtuous after wiping cm9)
Which all sounds great, but I have no idea how to really use any of that... Does "possibly fixes bricks" apply to my situation? I've tried selecting restore and advanced restore through CWM, but in both situations it says "cannot find files", which I'm assuming are the "boot.img" being referenced. So again, it seems like I'm hosed...
I'm just really hoping that Diamondback's unbricking method works for me. Though, I'm having a hell of a time finding instructions on how to setup ADB on my PC (Windows 7). Do you know where I can find good and current instructions?
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
demandarin said:
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
Click to expand...
Click to collapse
Thanks again! I think I need a tutorial on how to search XDA more effectively
SUCCESS!
Well, it took some jumping through hoops, but once I got ADB set up successfully, Diamondback's instructions worked like a charm!
For anyone encountering this thread with the same issues as me, I've included links to all of the sources of data I ultimately used.
Thanks so much for everyone's help!
Installing ADB
http://forum.xda-developers.com/showthread.php?t=1427008
http://www.youtube.com/watch?v=ZY4KSrgi-rE
I had to use the PDANet method, referenced in the Youtube video
http://junefabrics.com/android/download.php
Diamondback's Instructions for Unbricking the Prime
http://forum.xda-developers.com/showthread.php?t=1514088
Perhaps I spoke too soon...
My device is no longer bricked, but now I can't access CWM, can't factory reset...can't do anything. I'm stuck with a very broken build of Cyanogenmod 9
Here's the link to my new thread:
http://forum.xda-developers.com/showthread.php?p=23349041#post23349041
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
every time i do a fresh install from zip i do factory reset, wipe both d and c , and try to install, it gets through but says error at end. I reboot phone and it runs the new mean rom and the meanrom is also located on the sd with the files for over clocking. Is it ok to run like this still and what am i doing wrong? Everything has seemed to work so far. But it does seem like i have battery drain issues and i can watch my battery go down 10 percent every hour not sure if this is normal.
deneid310 said:
every time i do a fresh install from zip i do factory reset, wipe both d and c , and try to install, it gets through but says error at end. I reboot phone and it runs the new mean rom and the meanrom is also located on the sd with the files for over clocking. Is it ok to run like this still and what am i doing wrong? Everything has seemed to work so far. But it does seem like i have battery drain issues and i can watch my battery go down 10 percent every hour not sure if this is normal.
Click to expand...
Click to collapse
Could be a bad download, check the MD5 sum and re-download if need be.
DNarsingh said:
Could be a bad download, check the MD5 sum and re-download if need be.
Click to expand...
Click to collapse
ive downloaded multiple times from the direct forum.and i have used different versions starting back at 2.8 I havent had any issues running the rom,
I suggest to get the last version of TWRP and redownload and check md5. It should work.
Sent from my EVO using Tapatalk 2
Did you try to super wipe? That should start you completely new then flash the ROM
ill give it a try, how much better should the battery be?
It depends on what you are doing. If your on your phone streaming, or playing a game for that hour that might sound ok Imo. I usually get between 10-11 and a half hours with 2-3 hours being screen on time. But it will vary also if your OC and how much
Seen happen, sometimes very simply caused by where you are installing and mounted from. If you are mounted as internal, install from the internal SD. If external, install from external SD. It may work from time to time and with small update.zips as the reciprocal, but large ones will give errors at times. So, check where you are mounted.
hey guys i did a fresh install right now and i used the file downloaded from the ota updater 3.4 and it worked fine, thanks for the help. I am OC at 1.7 i dont think i detect much of a difference and wondering if i should just leave at stock? Also is there a way to download more then 1 item at a time from the play store this gets really annoying every time i re-rom and have to download 25 apps
thanks for your help guys i gave u some kudos
PRAISE ODIN!
:highfive:
Install
deneid310 said:
every time i do a fresh install from zip i do factory reset, wipe both d and c , and try to install, it gets through but says error at end. I reboot phone and it runs the new mean rom and the meanrom is also located on the sd with the files for over clocking. Is it ok to run like this still and what am i doing wrong? Everything has seemed to work so far. But it does seem like i have battery drain issues and i can watch my battery go down 10 percent every hour not sure if this is normal.
Click to expand...
Click to collapse
ok so I'm about to attempt a custom rom for the 1st time on my LTE. I've did this several times on my OG EVO. Is their anything I should do, check or be aware of before I flash. I've read about this new Mean Rom and it sounds like the business, so why not! Also do you guys prefer CWM or TWRP? Currently i'm running CWM as I was on my OG. I also couldn't receive the latest OTA from sprint. I tried yesterday and it went to CWM recovery but prompted an error before it installed.?!!?!!?!
Twrp recovery is more stable for our devices, use goo manager from the play store. Once installed open it up and hit the menu and download and install recovery from there, it will flash twrp for you
banccalif said:
Twrp recovery is more stable for our devices, use goo manager from the play store. Once installed open it up and hit the menu and download and install recovery from there, it will flash twrp for you
Click to expand...
Click to collapse
like banccalif said, use twrp, Download goomanager from play store to get it . Works amazing.
here is a step by step video watch?v=6bLaJc4_f0k (add youtube.com before watch sorry still rookie poster and wont allow links)
if you dont see the zip file on your rom make sure to go to mount (in the twrp recover) and make sure mount sd is clicked
Praise Odin
Before you dive into Meanrom 3.5 you need to make sure you are on the latest firmware, kernel, and radio. If you are currently s-on on hboot 1.15 you will probably have problems after installing. Make sure you read all the posts in the Meanrom thread that have been posted since the ota came out before proceeding.
Sent from my icrap 2 using Tapatalk HD
Hey, guys, I made a mess.
A long time ago I decided to try out CyanogenMod for my S3 and then everything went well. I got it up and running and it was a cool ROM but I decided to stick to stock at that time. So I looked for a tutorial online and managed to get it back to stock 4.1 Android running well and as usual.
The issue I had then was that I couldn't update my phone from Google's servers anymore. Every time the phone tried to update the firmware I'd get an error, no matter if I tried it through Kies, the phone or whatever. So I decided I'd just install a ROM for a more recent version.
I found a post on a tech blog here in Brazil saying that OmniROM promised they finally had a somewhat stable version of KitKat 4.4
I went on to install it to then find a beautiful, but still very glitchy ROM. My phone froze all the time and it was starting to bother me. My initial plan was to stick to it until it got better, get the daily updates and stuff, but my phone was way too unstable for that too. So I said to myself: "Okay, no problem, so let's get a stable ROM on this little guy."
I downloaded PA 4.3 and proceeded to get it on my phone. That's when the issues started happening. I couldn't find the .zip from CWM no matter where I put it, and my sdcard1 was full because of the previous backup I created (there was a problem with that too, MD5 mismatch, but I didn't lose anything important so that's okay).
Then I did something even more stupid. I figured, why not clean up the backup and get the .zip there, so maybe it'll show up? At that point the sdcard0 (internal storage) was all different and I couldn't find the .zip for the OmniROM, but when I was on CWM it showed up instead of PA's. The problem with that is that I somehow wiped out CWM and now I can't get to recovery. If I boot up my cellphone through OmniROM, it loads up fine but I can't download the ROM Manager or the superuser from the Play Store. I'm trapped with OmniROM and it's working even less well than at first.
What should I do? Is there a way back from this? I'd really like to have my phone running again soon, I need it to keep in touch with my parents since my grandma died recently.
Thank you in advance.
EDIT: Okay, some progress. I remembered that I got CWM on the phone through Odin and went through that again. I have CWM back but still, my internal storage fails to recognize the new .zip files and only shows OmniROM's. The folder is completely different when I connect the phone to my computer. I got to see the .zip files at the sdcard1 but CWM says they're bad files. I'll trust it and redownload/transfer again. We'll see what happens.
EDIT 2: Trapped again. Can't find anything on Google. It sure sucks to be me. I can't even figure out how to get everything back to stock so I can try again. Tried turning USB debugging off but it didn't make a difference. The CWM shows me the two OmniROM .zip files and my computer shows me the PA .zip files. I'm just...
first- try to flash newer cwm based recovey. I suggest philz (is has both Odin / cwm based install):
http://forum.xda-developers.com/showthread.php?t=2002953
after flashing is complete- try to download this rom:
http://forum.xda-developers.com/showthread.php?t=2060403
and check if you can see it.
(you can put it in your internal or external sd, philz can access them both)
Before installing the new rom, I strongly recommend doing a 'wipe to istall new rom', cache wipe and delvik.
good luck
Sent from my GT-I9300 using Tapatalk
Yay, thank you! I'm not trapped anymore. The PA rom I downloaded is still "bad", but that's probably its own fault. I'll wait until NeatROM's download is complete and try with that. I'll edit this if things turn out well.
Thanks again!
EDIT: So, I tried with NeatROM and it also says it's bad. But I only tried on the external storage, so maybe that could be it. My sdcard has been returning some really funky errors when I get it on my computer so I'm worried it might be a bit compromised (and I actually found it at a bus terminal, so it never really worked properly even after formatting).
Thing is when I did the wipe I picked the option that wipes it for a new ROM, so OmniROM is gone. Is there a way to get USB connection through CWM so that I can transfer NeatROM to the internal storage? I only have this one sdcard.
EDIT 2: Finally got it! Thanks so much, amirTor, my S3 is back on track! The sdcard was the bad one, not the file. But the PA ROM didn't work anyway. I might stick to NeatROM or maybe look later. I'm gonna take a week off of all this after so much trouble.
Glad I could help (even though it seems that you pretty much helped yourself...)
1)If you got Sandisk SD card, make sure to follow my post on thread: http://forum.xda-developers.com/showthread.php?t=2614170
2)You can mount your phone to be shown in your pc even when in recovery mode: Mounts and storage-> moun usb mass storage
3)You should definitely stick with neat- the best stock (and aosp) rom there is :good::good::good:
ps- hitting the 'thanks' button will be appreciated :angel:
Done and done!
I lost my Nook Tablet for a while and just recently found it again. I'd like to update the recovery tool and put a new ROM on it so I'm looking for suggestions.
I had previously rooted it and installed ClockWorkMod and then it is running some version of an Android ROM. I'm looking to update the ROM to something newer so I can make use of new apps etc. Also I know newer ROMs need newer recovery tools to install. Is CWM still the go to for that?
Thanks for any help!
OMGitsShan said:
I lost my Nook Tablet for a while and just recently found it again. I'd like to update the recovery tool and put a new ROM on it so I'm looking for suggestions.
I had previously rooted it and installed ClockWorkMod and then it is running some version of an Android ROM. I'm looking to update the ROM to something newer so I can make use of new apps etc. Also I know newer ROMs need newer recovery tools to install. Is CWM still the go to for that?
Thanks for any help!
Click to expand...
Click to collapse
I'm running CM 10.2 and have been very happy with it. This excellent post by digixmax should get you on your way. It's what I used to get up and running, and yes, the recovery is CWM-based.
nmyshkin said:
I'm running CM 10.2 and have been very happy with it. This excellent post by digixmax should get you on your way. It's what I used to get up and running, and yes, the recovery is CWM-based.
Click to expand...
Click to collapse
Thanks for that! Honestly i'm not sure what is going on. I managed to get Cyanoboot on it, installed CWM 6.0.4.8, yet every single 10.1~10.2 CM ROM I get from the official directory seems to cause it to go into a weird state where the screen goes blank, then flashes white, then goes blank again and repeat etc. Eventually the tablet just restarts. I've yet to find a single ROM that I can successfully load via SD card or internal and install it through CWM. For such an old tablet, I'm surprised things are this difficult! I've spent the last few days flashing back to stock on so many occasions when things have gone wrong. I wish I could try some other ROMs that aren't on the official CM repository however most ROMs have been hosted on Goo.im and while the site works, it is so slow you aren't even sure if the file is downloading. I wish there was more custom ROMs I could try because every official CM from 10.1 to 12.1 is bricking or failing to install! I'm honestly at my wits end.
OMGitsShan said:
Thanks for that! Honestly i'm not sure what is going on. I managed to get Cyanoboot on it, installed CWM 6.0.4.8, yet every single 10.1~10.2 CM ROM I get from the official directory seems to cause it to go into a weird state where the screen goes blank, then flashes white, then goes blank again and repeat etc. Eventually the tablet just restarts. I've yet to find a single ROM that I can successfully load via SD card or internal and install it through CWM. For such an old tablet, I'm surprised things are this difficult! I've spent the last few days flashing back to stock on so many occasions when things have gone wrong. I wish I could try some other ROMs that aren't on the official CM repository however most ROMs have been hosted on Goo.im and while the site works, it is so slow you aren't even sure if the file is downloading. I wish there was more custom ROMs I could try because every official CM from 10.1 to 12.1 is bricking or failing to install! I'm honestly at my wits end.
Click to expand...
Click to collapse
I'm not skilled enough to give advice relative to your problem, but I might suggest you go for 10.0. Many people seem to think that this is the most stable of the lot, although it does seem there is something else going on with the problems you describe--maybe the SD card?