Currently I have CM12 on my trusted Z3CT, and I am very happy with it - but it does seem like development of CM has sort of stopped for this device so I wanted to try PA.
My device is rooted, but flashed with Cyanogen Recovery (an ancient one, haven't updated I think since I initially installed CM12), and installing from this did not god well.
I rebooted into recovery, wiped partitions and cache and tried to install PA, which fails after about 20sec, not giving an error message. So i installed CM again without any issue.
Do i need to flash with TWRP, following this guide; http://forum.xda-developers.com/z3-...torial-stock-android-marshmallow-6-0-t3409486
or is there an easier way since my device is already rooted?
Please bear in mind that I am not that savvy when it comes to rooting and flashing. When initially installing CM i followed I guide to the letter. Going off-script would be something that I would.... not look forward to
Thanks for any help.
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
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Factory reset Last option
snowman4839 said:
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Click to expand...
Click to collapse
if nothing works, factory-reset but last option.
yeah I just started downloading the stock rom to flash with ODIN in the morning. I just wanted some reason why this would happen so I won't always have have this problem and to know why it only works with some roms over others.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Zothar said:
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Click to expand...
Click to collapse
I restored to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=237 to flash through ODIN. Rerooted by flashing the older kernel, rooting, installing superSU, then reflashing the newer kernel (normal root procedure). Then I insatlled ROM Manager and gave it root to install CWM recovery. Then I flashed to my same Hyperdrive ROM I was using before and now everything works beautifully. Nothing gets stuck anywhere an no more "cannot mount /data"
Just use that site and restore to stock and everything should work fine.
I'd like to add some confirmation to this. I had similar problems after flashing my first ROM- phone wouldn't reboot a second time, and when I attempted to make nandroids the files would be ridiculously large (~1 TB). I restored to the stock Touchwiz, rerooted normally, and reflashed normally. The strange thing is that I did the rooting and the flashing with the same files I had used the first time, implying something went wrong during the first rooting/flashing process.
Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
cherokee990 said:
Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
Click to expand...
Click to collapse
Cherokee.. I am pretty busy at the moment working on Android TV boxes but I can see that you have nflash backups so everything should be fine.
I will pm you my Google talk address and add me on there with a message saying who you are, this is a bit too complicated to go through on the forums.
Can't promise you I can help you straight away but I will get around to it in the next day or two.. I'm UK time by the way.
So I'm very new to all of the rooting stuff. I got an HTC 4G LTE off Ebay just to use as sort of like a tablet. The firmware on the phone kinda sucks so I wanted to root it and go with a better version of Android that the bloatware-inflated version HTC provides. Not to mention updates are no longer supported.
I successfully rooted the phone with TWRP and followed the instructions to wipe the phone and such. This is where the instructions I found were kinda "off" and started using way too much lingo so I decided to wing-it a bit, thinking I had sort of understood it. I went to install, installed the BeanStalk and Gapps zip folders that are available in the the other section.
Rebooted my phone and it wouldn't go past the HTC boot logo... So I tried again. No luck.
I managed to get back in TWRP and I'm wondering what I need to do in order to get this bad boy to work. I checked the troubleshooting threads and found the section on boot-looping, but so I did the cache wipes it stated, selected "Factory Restore" and it rebooted back into TWRP. I'm not really sure what to do. Do I re-install the BeanStalk and Gapps zips, or am I missing something?
Thanks for any help.
If the phone is S-on you'll have to flash the kernel separately from the ROM itself. Hit the top link in my sig and read the entire guide. I think it will be quite useful to you:thumbup: