Hey Everyone,
So, I'm pretty sure I'm going to unlock the bootloader on my Prime, but I had a quick question before I do, and I'm not seeing any sort of threads which help me out that much (Or at least the ones I looked at).
To make the story short, I'm looking to be able to root my tablet and install a custom ROM on there, however, it is to my understanding that there is no way to root the .21 firmware at this time. However, I was wondering if by unlocking the bootloader I would be able to manually push CWM Touch and thusly be able to boot into recovery, installing a rom that is pre-rooted, or even just rolling back to a previous update. I'm fairly familiar with ADB and terminal commands, so I am not shy to get into the nitty gritty if need be.
I apologize in advance if this has already been answered or asked, but, I'm in a time crunch and was looking for some advice !
Thanks for the information,
Horvaticus
Horvaticus said:
Hey Everyone,
So, I'm pretty sure I'm going to unlock the bootloader on my Prime, but I had a quick question before I do, and I'm not seeing any sort of threads which help me out that much (Or at least the ones I looked at).
To make the story short, I'm looking to be able to root my tablet and install a custom ROM on there, however, it is to my understanding that there is no way to root the .21 firmware at this time. However, I was wondering if by unlocking the bootloader I would be able to manually push CWM Touch and thusly be able to boot into recovery, installing a rom that is pre-rooted, or even just rolling back to a previous update. I'm fairly familiar with ADB and terminal commands, so I am not shy to get into the nitty gritty if need be.
I apologize in advance if this has already been answered or asked, but, I'm in a time crunch and was looking for some advice !
Thanks for the information,
Horvaticus
Click to expand...
Click to collapse
um...sorry....it might come across as harsh but you didnt look did you? If your familiar with ADB then you should know that rooting has nothing to do with custom roms. In order to put a custom rom you have to have an unlocked bootloader.
Review the Android development Section for info on roms/bootloaders/rooting
An unlocked bootloader was released and we had a rom available within 2 hours.
If you go to ANY thread with [ROM] they will tell you what you need to do. Easy.
And .21 is cooked into many Roms so far...i'm using virtous Prime and prefer that one so far...(it's really about preference)
So...moral of the story..please read before posting...do a quick search...it's been answered before.
monkeyboywa said:
um...sorry....it might come across as harsh but you didnt look did you? If your familiar with ADB then you should know that rooting has nothing to do with custom roms. In order to put a custom rom you have to have an unlocked bootloader.
Review the Android development Section for info on roms/bootloaders/rooting
An unlocked bootloader was released and we had a rom available within 2 hours.
If you go to ANY thread with [ROM] they will tell you what you need to do. Easy.
And .21 is cooked into many Roms so far...i'm using virtous Prime and prefer that one so far...(it's really about preference)
So...moral of the story..please read before posting...do a quick search...it's been answered before.
Click to expand...
Click to collapse
Well, I know that rooting has nothing to do with Rom installment. Admittedly I was posting from a golf course and didn't take the time to sift through the threads. So, thanks for answering my question, kinda. When I said Root & Install a custom Rom I did not mean that in sequential order. Simply that I would like a Rom that has root baked into it, or be root-able.
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
reNeglect said:
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
Click to expand...
Click to collapse
you need root access to flash cwm from rom manager, afaik.
Sent from my TF201
reNeglect said:
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
Click to expand...
Click to collapse
Yeah, you do. But I unlocked it via the unlock tool APK and then from there just installed CWM via fastboot and pushed the rom and crap to it. Thanks! Installing now!
Related
I just got a TF201. It's my first Android device, so please bear with me for this newbie issue. I wanted to root it so I tried PrimeTime without considering that I was already running version .21. Obviously it screwed up... The worst that happened is seeing a caput droid while trying to load CWM. Don't know what's the deal with that, I guess it just didn't install properly.
The device otherwise still boots fine so I'm left wondering what to do with it. Can someone explain what PrimeTime does exactly, I'd like to know in what state is my TP now...
Is there a risk that an OTA could brick it?
Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
Can I factory reset everything and lock the bootloader?
Thanks
install touch cwm or twrp and it should be fine, obiesly ota will brick it. Dunno about reseting data.
Sent from my Transformer Prime TF201 using XDA Premium App
vanista said:
I just got a TF201. It's my first Android device, so please bear with me for this newbie issue. I wanted to root it so I tried PrimeTime without considering that I was already running version .21. Obviously it screwed up... The worst that happened is seeing a caput droid while trying to load CWM. Don't know what's the deal with that, I guess it just didn't install properly.
The device otherwise still boots fine so I'm left wondering what to do with it. Can someone explain what PrimeTime does exactly, I'd like to know in what state is my TP now...
Is there a risk that an OTA could brick it?
Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
Can I factory reset everything and lock the bootloader?
Thanks
Click to expand...
Click to collapse
Another example of what may happen when people don't have patience, not reading everything.
Q: Is there a risk that an OTA could brick it?
Q: Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
A: Have you used ASUS Unlocker Tool to unlock your bootloader (thus voiding your warranty)? If you did, the awnser is yes for the first 2 questions.
Q: Can I factory reset everything and lock the bootloader?
A: Relocking bootloader isn't possible; You can factory reset everything through Android UI/stock rom only if you didn't install CWM as of yet.
bk201doesntexist said:
Q: Can I factory reset everything and lock the bootloader?
A: Relocking bootloader isn't possible; You can factory reset everything through Android UI/stock rom only if you didn't install CWM as of yet.
Click to expand...
Click to collapse
Thanks for the reply
Can you elaborate, I don't know how far PrimeTime went trying to install CWM. What happens if I reset with CWM present? Can it be cleaned?
vanista said:
Thanks for the reply
Can you elaborate, I don't know how far PrimeTime went trying to install CWM. What happens if I reset with CWM present? Can it be cleaned?
Click to expand...
Click to collapse
I think that if you try to factory reset with CWM installed it will bootloop/brick, I've read it somewhere here on xda.
Again, CWM can only be installed if bootloader has been unlocked. If you didn't and PrimeTime doesn't as well, you cannot have cwm installed.
I believe there was some information laying around about returning to stock, not sure if it's possible to return to stock recovery after flashing cwm.
bk201doesntexist said:
Again, CWM can only be installed if bootloader has been unlocked. If you didn't and PrimeTime doesn't as well, you cannot have cwm installed.
Click to expand...
Click to collapse
My bootloader is unlocked but I'm not rooted, apparently I cannot install CWM from ROM Manager. Is it possible through fastboot? When I try to go into recovery mode I get the laid down dead droid... Is that caused by a faulty CWM or just that I don't have a recovery image anymore?
I modified ViperMODS tool to add Xda user wolf849's method of downgrading a transformer without root, so you can use this http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 to downgrade to .15 then root, then install OTA rootkeeper then update via ota to .21 again. Or you can just unlock and install cwm if you want to void warranty.
Okay this is just getting more and more confusing. Everywhere I read about CWM and custom ROMs it says you have to be rooted. If that is true then I'm in a dead end because I cannot downgrade to .15 without bricking and I can't properly install CWM either.
I finally found some official doc on fastboot source.android.com/source/building-devices.html , if its accurate you don't even need CWM to flash a custom rom. That seems to be much more reliable. Isn't CWM just a wrapper for what can all be done manually through adb??
Finally found some precise instructions... androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Instructions for non-rooted Primes (or those who’d rather use fastboot):
Get fastboot from here, and extract it.
Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
Power off your prime.
Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot”.
Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
Profit!
vanista said:
My bootloader is unlocked but I'm not rooted, apparently I cannot install CWM from ROM Manager. Is it possible through fastboot? When I try to go into recovery mode I get the laid down dead droid... Is that caused by a faulty CWM or just that I don't have a recovery image anymore?
Click to expand...
Click to collapse
you awnsered yourself below
bpear96 said:
I modified ViperMODS tool to add Xda user wolf849's method of downgrading a transformer without root, so you can use this http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 to downgrade to .15 then root, then install OTA rootkeeper then update via ota to .21 again. Or you can just unlock and install cwm if you want to void warranty.
Click to expand...
Click to collapse
he's unlocked, he can't run an official blob, that method does not work for him
vanista said:
Okay this is just getting more and more confusing. Everywhere I read about CWM and custom ROMs it says you have to be rooted. If that is true then I'm in a dead end because I cannot downgrade to .15 without bricking and I can't properly install CWM either.
I finally found some official doc on fastboot source.android.com/source/building-devices.html , if its accurate you don't even need CWM to flash a custom rom. That seems to be much more reliable. Isn't CWM just a wrapper for what can all be done manually through adb??
Click to expand...
Click to collapse
don't look on source.android.com, aosp doesn't support transformer prime directly, and as you might have noticed, fastboot commands are a bit different for the prime that of galaxy nexus, for example.
why some say you need to be rooted to flash cwm? because they use ROM Manager nice UI to do it, instead of teaching people how to do it without an UI. Rom Manager needs root, as you know.
vanista said:
Finally found some precise instructions... androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Instructions for non-rooted Primes (or those who’d rather use fastboot):
Get fastboot from here, and extract it.
Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
Power off your prime.
Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot”.
Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
Profit!
Click to expand...
Click to collapse
exactly, use these steps from androidroot.mobi to flash cwm with fastboot. these are correct, and the only way to flash cwm, if you're unlocked but not rooted.
food for thought: i believe linux+fastboot is way safer than windows+fastboot.
Great! Thanks for the confirmation, quite reassuring, now I know where I'm headed... I'll at least fix my recovery with CWM. From there I don't know, I feel I have to do some more reading before I go ahead and flash any custom rom...
I may not know much on android yet, but I have 10 years experience in linux software dev, with a few pointers like this to get me started I should be able to do anything with this toy soon enough ;-)
Done, just flashed CWM as per the instructions and it works flawlessly. Backing up right now... I'm tempted to go ahead and flash Virtuous.
Done, totally virtuous now ... That was easy Thanks again for the help! Now I only hope I won't regret voiding the warranty
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.
Hey guys,
Bit of an Android noob here but I am quite tech savvy. I am gonna root my Prime and install Androwook on it but first I would just like to go over some things. I have had a look around at a lot of guides and that and have figured to do this I need to unlock the bootloader using ASUS' own app fro their support, then I need to install CWM on it through the unlocked bootloader and then I can backup and install new ROMS. But which point is the root, I can't seem to find a clear answer or is it a whole new step all together? And also could you please guide me if this is completely wrong because I am paranoid about my Prime and would hate to end up with it bricked. Sorry if this is sort of in the wrong area or a bit of a repeated question, just paranoid!
Thanks,
I saw your post completely randomly, but I think I have your answer. Rooting your device can be done at any point by either unlockroot.com or DoomLord's toolkit somewhere on the site. It has no effect on installing roms/unlocking bootloaders. It simply gives you more control over a device. I hope I understood your question and helped. Good luck
Sent from my Sony Xperia Neo using xda app-developers app
Ok, thanks, that clears a lot up. I will check that out. I didn't know it was that easy. Could I also ask, which part of the process risks the device been bricked?
mdemons12 said:
Ok, thanks, that clears a lot up. I will check that out. I didn't know it was that easy. Could I also ask, which part of the process risks the device been bricked?
Click to expand...
Click to collapse
Well unlocking the bootloader SHOULD be safe if yu're unlocking by offficial means. What can damage your device is flashing the wrong files. So be REALLY careful with what you flash on your device and always double-check the tutorials in the given thread
if i remember correctly, they said you need root was to install cwm onto your system
the rooting process is very easy anyways
http://forum.xda-developers.com/showthread.php?t=1706588
for the unlocking use the asus official one (This will void ALL warranties so if you brick your prime, well then GG)
and as above post says, most things should be very save so long as you follow to the dot.
when it says DO NOT POWER THE SYSTEM DOWN, just follow what it says and don't power things down, you should be fine
download things that are for you ONLY don't go to other threads trying to install iOS onto your prime (not that its possible.... that i know of)
just read it make sure you understand you won't brick anything~
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
mdemons12 said:
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
Click to expand...
Click to collapse
yes the devs will be able to put jelly bean on the prime if we get the official update :fingers-crossed:
mdemons12 said:
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
Click to expand...
Click to collapse
It is worth noting that you probably don't need to go through the root process if you are installing a custom ROM. Many (most?) custom roms grant super-user permissions by default.
well it does say in the requirements of Androwook that it requires a root.
one suggestion though, use TWRP as your recovery mode. quite handy...
mdemons12 said:
well it does say in the requirements of Androwook that it requires a root.
Click to expand...
Click to collapse
The reason you root your device is to gain superuser permissions. Most OEM versions of Android don't give you SU permissions because it is possible you could mess up your device by deleting systems files or changing hidden settings. However most custom ROMs give you superuser permissions by default.
After unlocking your Prime, I would recommend installing TWRP using the fastboot method, so that you don't need to install root first. Then you can backup your stock and flash AndroWook from TWRP. AndroWook is already rooted, so you won't need to worry about adding extra steps for root.
~Azrael's Kiss~
OK, thanks for the replies. I think I will wait a little and test the device for any major problems before I root and unlock because I don't want to have to send it back for an RMA.
So from what I have read around I need to:
1. Unlock bootloader using the ASUS tool
2. Install CWM or similar and backup my current ROM although I have seen trouble with installing 2.1 with CWM so I think I might use TWRP
3. Install Androwook 2.1 and from what I have read skip some things like bravia engine, sd wipe sqlite vacuum and add sio io scheduler.
There seem to be so many options with the installer which makes it a bit confusing but first up I think I will use the 1.6GHz Kernel or something and keep it mainly stock.
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 just recently rooted my Verizon Galaxy S4 and swiftly installed Rom Manager. I have used ROM manager in the past before I owned an iPhone when the Moto Droids were popular. Upon installing I flashed the recovery over to CWM - However, when I reboot into recovery I still receive the default stock options. I even purchased the CWM Touch recovery to see if that would work, sadly it did not.
I am stuck as to what to do here, I have googled the problem and cannot seem to find a cure. I can not do anything with CWM - When I click backup current ROM it simply reboots into the stock recovery.
If anyone can help me with this issue I would be extremely appreciated
Thanks,
Christopher
Reneg4d3 said:
I just recently rooted my Verizon Galaxy S4 and swiftly installed Rom Manager. I have used ROM manager in the past before I owned an iPhone when the Moto Droids were popular. Upon installing I flashed the recovery over to CWM - However, when I reboot into recovery I still receive the default stock options. I even purchased the CWM Touch recovery to see if that would work, sadly it did not.
I am stuck as to what to do here, I have googled the problem and cannot seem to find a cure. I can not do anything with CWM - When I click backup current ROM it simply reboots into the stock recovery.
If anyone can help me with this issue I would be extremely appreciated
Thanks,
Christopher
Click to expand...
Click to collapse
Did you remember to go to Rom Manager > Recovery Setup > Click ClockworkMod Recovery (Under INSTALL OR UPDATE RECOVERY) > Then click on the Samsung Galaxy S4 (Verizon).
Yes, since that is the only way to download and install the recovery that is what I did...
You might want to email the developer or get a mod to move this thread to the Q&A forum.
DarkMenace said:
You might want to email the developer or get a mod to move this thread to the Q&A forum.
Click to expand...
Click to collapse
I will email the developer the link to this thread.
Surely I am not the only one with this problem...
Reneg4d3 said:
I will email the developer the link to this thread.
Surely I am not the only one with this problem...
Click to expand...
Click to collapse
I was able to flash it with no issues.
Do you mind telling me exactly what you did (even rooting wise) - I used some compiled package that was on droid life I believe. It had all the tools compiled and was the closest thing to a one click without being one click. I think it even attempted to flash the recovery. However, that is how I rooted my device. I didn't flash another rom. Still on the stock rom.
I just rooted the device. Switched to SuperSU, restored all my programs via Titanium Backup. Then I flashed CWM.
DarkMenace said:
I just rooted the device. Switched to SuperSU, restored all my programs via Titanium Backup. Then I flashed CWM.
Click to expand...
Click to collapse
I have read conflicting posts about this but is your bootloader unlocked? I read that the bootloader was unlocked before the phone was even released - Then I read somewhere else that the Verizon bootloader was super locked down and not cracked yet. Obviously, you would need some bootstrap or the bootloader unlocked before the device would even be able to use a custom ROM. Did you flash the phone to get root, or did you use all kinds of different tools to do so?
EDIT:
this is the method I used - http://forum.xda-developers.com/showthread.php?p=41718543
Reneg4d3 said:
I have read conflicting posts about this but is your bootloader unlocked? I read that the bootloader was unlocked before the phone was even released - Then I read somewhere else that the Verizon bootloader was super locked down and not cracked yet. Obviously, you would need some bootstrap or the bootloader unlocked before the device would even be able to use a custom ROM. Did you flash the phone to get root, or did you use all kinds of different tools to do so?
EDIT:
this is the method I used - http://forum.xda-developers.com/showthread.php?p=41718543
Click to expand...
Click to collapse
That's the same method I used but I didn't unlock the bootloader. I just did the root them installed the recovery from the Play Store.
Reneg4d3 said:
I have read conflicting posts about this but is your bootloader unlocked? I read that the bootloader was unlocked before the phone was even released - Then I read somewhere else that the Verizon bootloader was super locked down and not cracked yet. Obviously, you would need some bootstrap or the bootloader unlocked before the device would even be able to use a custom ROM. Did you flash the phone to get root, or did you use all kinds of different tools to do so?
EDIT:
this is the method I used - http://forum.xda-developers.com/showthread.php?p=41718543
Click to expand...
Click to collapse
Please read about loki in the development forum. The bootloader is not unlocked and unlock is not needed to flash roms or recoveries.
http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I545 using Tapatalk 4 Beta
I will read about loki - maybe when I read about loki this will be explained, however I was always under the impression that in order to install custom ROMs you have to unlock the bootloader. I know that a bootloader or bootstrap is what tells your device what operating system to boot to and if it is locked this prevents you from loading a custom ROM. If I have this all wrong, would someone care to explain? You can use technical explanations as I will most likely be able to understand what you mean.
EDIT:
reading about loki clears this up. It's simply (yet sophisticatedly) tricks the aboot into thinking the rom passes the checksum that is physically embedded into the phone and proceeds to boot the custom rom. The boot loader itself is still locked, but is bypassed.
The only problem with this is they can release an update to patch the sequence in which the checksum is done so that it cannot be loaded over itself.
My problem still remains - Clockwork Manager is not working.
Does anyone have any suggestions?
Questions and help issues go in Q&A and help section
Thread moved
FNM
Sorry I posted it in the wrong section. If anyone knows what is wrong please let me know, I am thoroughly confused as to why this is happening. Maybe I should restore stock and reroot the device, although I don't know what that would do.
Am I supposed to install Loki? Because I never did that, I was under the impression that rom manager would do that.
Reneg4d3 said:
Sorry I posted it in the wrong section. If anyone knows what is wrong please let me know, I am thoroughly confused as to why this is happening. Maybe I should restore stock and reroot the device, although I don't know what that would do.
Am I supposed to install Loki? Because I never did that, I was under the impression that rom manager would do that.
Click to expand...
Click to collapse
Do a stock restore. Then root again. Start over.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
I cleared the Clockwork Mod data and also uninstalled and reinstalled the app and now it is working Guess it was just a fluke!