Database Info

[Q] How to undo the unroot the official Asus unlocker (Transformer Prime)

Hi all,
I have a Transformer Prime and unfortunately I used the "official" unlock (APK) supplied by ASUS. Now I got the message "The divice is unlocked" when it boots up but I am not able to use TITANIUM BACKUP and other tools anymore because the viperMOD PrimeTime v4.1(program to unlock) also always fails.
Is there any possibilty to undo the prodedure to get an unlocked device again an then to use viperMOD PrimeTime v4.1???
Any help would be very very appreciated.
Greetings from Germany
Hans

I believes once you unlocked your device bootloader u also need to rooted your device as welll.....Vipermod v4.5 is your best choice and ts easy to do......once u rooted your device those apps you mentioned should work fine.....also boot keeper is important after rooted so in case u need to update your device you can just temp unrooted it and update......after that just go back to root keeper and restore it back on.......always temp unrooted your device before updated it cause i did it and my prime got stuck on recovery for bout a week was going nuts, eventually i got it back stock rom again.....cause i had done a back up previously which safe my life so good luck.

Thx a lot but it fails!
weakenfalls said:
I believes once you unlocked your device bootloader u also need to rooted your device as welll.....Vipermod v4.5 is your best choice and ts easy to do......once u rooted your device those apps you mentioned should work fine.....also boot keeper is important after rooted so in case u need to update your device you can just temp unrooted it and update......after that just go back to root keeper and restore it back on.......always temp unrooted your device before updated it cause i did it and my prime got stuck on recovery for bout a week was going nuts, eventually i got it back stock rom again.....cause i had done a back up previously which safe my life so good luck.
Click to expand...
Click to collapse
Thx for your quick answer. Sorry to say that Vipermod 4.5 does not work (see link to the pic).
Maybe its due that I have Build 9.4.2.21 (the latest).
To see the errorrs pls use this link:
dl.dropbox.com/u/19088805/Root1.png
There seems to be a prob with SYSTEM\BIN\SU (at least). This may be the reason because also SparkyRoot fails. I do not think that is due to the "official" ASUS boot unlocker which I installed (other people had success to root their device WITH Asus boot unlocker). I am rather sure it's because the build number.
Hm, do you have another idea???
Happy Easter from Germany
Hans

Yes your problem is the build. As of now build .21 cannot be rooted (see this thread http://forum.xda-developers.com/showthread.php?p=21007398).
If your device is already unlocked you could install a custom ROM (like VirtuousPrime.21).
Personally, I'm screwed right now. I had my .15 build rooted. And I installed a root keeper. When I upgraded to .21 the root keeper failed to restore my root.
So I thought I'd go the unlock route and install VP.21. But I can not unlock my bootloader. I have a Prime that has a bug where the S/N isn't listed in my tablet. This bug prevents the unlock app from unlocking the bootloader (was also the reason I could never OTA update my firmware). And the Ratchet tool fix for the S/N relies on the same mempodroid exploit as Vipermod that no longer works on .21 build.
Arggg!

Beermiester said:
Yes your problem is the build. As of now build .21 cannot be rooted (see this thread http://forum.xda-developers.com/showthread.php?p=21007398).
If your device is already unlocked you could install a custom ROM (like VirtuousPrime.21).
Personally, I'm screwed right now. I had my .15 build rooted. And I installed a root keeper. When I upgraded to .21 the root keeper failed to restore my root.
So I thought I'd go the unlock route and install VP.21. But I can not unlock my bootloader. I have a Prime that has a bug where the S/N isn't listed in my tablet. This bug prevents the unlock app from unlocking the bootloader (was also the reason I could never OTA update my firmware). And the Ratchet tool fix for the S/N relies on the same mempodroid exploit as Vipermod that no longer works on .21 build.
Arggg!
Click to expand...
Click to collapse
Hi,
thx for your answer. I downloaded Virtual Prime as you suggested. Before that I used Vipermod to install CWM. But during doing that there came an error message: \data\local\cwminstall: su: not found.
It's always the su-messages that drive me crazy!!
Then when shutting down the Prime and rebooting (volume down then volume up) it always fails (the lying android with the red exclamation mark!)
Do you know what went wrong?
BTW: Vipermod states on Option #5 (installing Unlocker and CWM):"Must be rooted". But my Prime ISN'T rooted... that's exactly that that I want to achive :=)
So my main problem is: how to install CWS. It always fails
Would be great if anyone could help me out of this!
all the best and greetings from Germany
Hans

handi1948 said:
Hi,
thx for your answer. I downloaded Virtual Prime as you suggested. Before that I used Vipermod to install CWM. But during doing that there came an error message: \data\local\cwminstall: su: not found.
It's always the su-messages that drive me crazy!!
Then when shutting down the Prime and rebooting (volume down then volume up) it always fails (the lying android with the red exclamation mark!)
Do you know what went wrong?
BTW: Vipermod states on Option #5 (installing Unlocker and CWM):"Must be rooted". But my Prime ISN'T rooted... that's exactly that that I want to achive :=)
So my main problem is: how to install CWS. It always fails
Would be great if anyone could help me out of this!
all the best and greetings from Germany
Hans
Click to expand...
Click to collapse
The problem, I think, is that you're trying to use the "my Prime is rooted" method of installing CWM.
Try the non-rooted instructions found here: h t t p : //androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Also, check out the video here for a how to install CWM. h t t p : //transformerprimeroot.com/transformer-prime-recovery/how-to-install-clockworkmod-recovery-5-8-2-0-on-transformer-prime/
When you do a recovery boot of your Prime do you get 3 options? One being a USB symbol? If you have the USB symbol when you do your recovery boot (ie you've unlocked your bootloader), you can flash CWM onto your Prime.

Thank you . . .n now I have ROOT!!!
Beermiester said:
The problem, I think, is that you're trying to use the "my Prime is rooted" method of installing CWM.
Try the non-rooted instructions found here: h t t p : //androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Also, check out the video here for a how to install CWM. h t t p : //transformerprimeroot.com/transformer-prime-recovery/how-to-install-clockworkmod-recovery-5-8-2-0-on-transformer-prime/
When you do a recovery boot of your Prime do you get 3 options? One being a USB symbol? If you have the USB symbol when you do your recovery boot (ie you've unlocked your bootloader), you can flash CWM onto your Prime.
Click to expand...
Click to collapse
Hi,
great reply!!! That helped me a lot - espec. the video. Some instructions are unclear (sometimes spoken of "terminal-input" ... I thought a terminal program input on the Prime!!!).
OK I pushed CWM on the Prime, got me a copy of "WW_ROOTED_CWM_Primeval_Stock_9.4.2.21-signed.zip", flashed the ZIP ... and now I have an boot-unlocked device AND I have root. Titium, Root Explorer and all my other "dear friends" work as they are exspected to do :=)
Once again THX A LOT and if you need something I could help: drop me a line!
Hans

[Q] Unlocked custom boot

Okay, as a newby poster on this forum, I can ask this question here, hopefully someone reads here that can help *smile*.
I've followed the rooting guide for my post JB OTA updated Galaxy S3. My phone is now apparently rooted, I can grant root access to apps and all. I should have a custom recovery installed as well (I chose TWRP since a lot of people seem to choose CWM, and I'm a rebel without a cause), but I'm not sure, since when I booted out of recovery after installing the SU app, I didn't see the "Disable recovery flash" prompt. And I haven't tried to boot into recovery mode yet to verify whether the TWRP version that I installed is still there. Doesn't seem to have affected the resulting root access ability one way or the other, though.
My question is that when I boot my phone normally now, I see an unlocked lock icon, and "CUSTOM". Since I re-flashed the stock boot when I was done, this is a bit disturbing, I didn't expect that. I've read that if I have a custom recovery that I'll see this even if I have stock boot. Is this true? I think that stock boot is a good idea, but am not convinced that I have it. Is there any way to tell if I have a stock boot or not?
A little puzzled, although I definitely like the rooted phone better than the non-rooted one, so thanks much for that.

Just rebooted the phone into TWRP recovery a couple of times this morning, so I guess that I still have the custom recovery installed *smile*. And I'm also assuming that flashing the stock boot at the end of rooting worked, despite the unlocked lock icon and "CUSTOM" when I boot my phone now.
I guess there's no need for a reply here, since I've answered at least part of my own questions. I'm assuming then that I'm seeing "CUSTOM" and the unlocked lock icon when I boot because I have the custom recovery installed, and when I un-root it will go away. I've already set my flash count back to 0, since I wanted to remember to do that while I still had root, in case I un-root to send the phone to Samsung, and forget to do that.
Again, thanks for the guide thread on rooting, very helpful. The only first-time snag was booting into TWRP from Odin mode so I could install the SU app. Eventually figured out how to do that, so when/if I do this again should be much quicker.

Lost root after flash via RSD Lite on JB

Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!

CoinCoin88 said:
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
Click to expand...
Click to collapse
Just to make sure you do have SuperUser, SuperSU, and I generally prefer to include BusyBox all into the mix. Also, if you would download Root Checker by Joey Krim in the Play store. Just to confirm and we know you are missing root click the verify should indicate the appropriate SU's are red and not engaged, slide to the right verify BusyBox, chances are it is green, if so you are in good condition. With Busybox in green, exit go into SuperUser and update the binaries, once that is completed go into SuperSU and click the update. Go back to Root Checker and double check, click verify root on SuperUser/SuperSU and should be green = rooted. :good:

Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)

CoinCoin88 said:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
Click to expand...
Click to collapse
If the color is Red all around then yes, there is little you can do. However, there are ways to get out of this and gain root without waiting even if they have Jelly Bean 4.1.1. For instance those on JB that own the XT926 can use the Droid Razr HD Utility 1.10 > go back to ICS 4.0.4 > apply the 1st update > Root > Voodoo OTA, SU Backup > apply the JB 4.1.1 update. I have done this twice and have been quite successful on my XT926 with Verizon.
But, in general going back to the discussion. If after the update the Supers are not showing, as long as Busy Box is Green and in place, Root can be restored by updating the binaries.

If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.

tech_head said:
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
Click to expand...
Click to collapse
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )

CoinCoin88 said:
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
Click to expand...
Click to collapse
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.

tech_head said:
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
Click to expand...
Click to collapse
edit the XML ?? I'm new to RSD lite, but from what I've understood so far, edit the xml is only neededn when flashing via RSDLite/fastboot so that you don't end-up with the "unknown fastboot command" or something like that (by removing 2 lines in the fw xml file, indeed).
How is this related to going back from JB to ICS ? I'm not sure that's possible with a locked bootloader (which I'm probably not going to unlock). Also, how is my carrier related to this operation ? (the phone was SFR simlocked, but I bought an unlock code online and I'm no using it on Free Mobile)
Or did I miss something ? (btw, no mention of a JB root for the Razr HD, only for the Razr M, and it is assumed it won't work on HD because for reasons I am yet to find)

[Q] How do I update a rooted, locked, 4.1.2 to 4.4.2 OTA?

Hello. I have a XT925 running 4.1.2. The phone was rooted a long time ago. I don't remember if I installed a recovery, nor which recovery (if any) was installed at the time (volume up + power yields a boot mode selection menu; it seems to be the original bootloader).
My carrier released the 4.4.2 OTA just today. When I try to update, the phone reboots and displays an "Update failed" error message. I uninstalled as many apps as AdAway and XPosed that I think could be tampering with the process, but still I can't install the update.
How can I update to KitKat? (If it isn't obvious by now, I don't follow most of the technicalities of this things with Android. I'm fairly knowledgeable about computers, just not Android. I've read a lot of threads here and still can't figure out how to do this!)
Will I be able to re-root the phone afterwards? Will I be able to unlock it?
Thanks!

unless you have some concerns about warranty, I suggest go ahead and unlock bootlocader via moto website. Then you are free to do as you please, meaning uprade to kk stock, custom rom and root without hassle.

hbenz2008 said:
unless you have some concerns about warranty, I suggest go ahead and unlock bootlocader via moto website. Then you are free to do as you please, meaning uprade to kk stock, custom rom and root without hassle.
Click to expand...
Click to collapse
Ok, I did it (and lost everything on the phone in the process). The phone said it was unlocked. The phone is now back to stock, clean 4.1.2. But I still can't update. I get the same "update failed" error message.
What should I do?

Dont panic! haha you will get it done I have no doubt.
First did you factory reset after all was done. Do that and try again
if not, there are other ways , some easier than others but all within your capabilities
http://forum.xda-developers.com/dro...tutorial-make-motorola-razr-hd-xt925-t2916465
http://forum.xda-developers.com/showthread.php?t=2760840&page=3

Life after ROOT

So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.

SGJ3 said:
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
Click to expand...
Click to collapse
It's better to let them on.
You can remove the TWRP recovery by flashing stock recovery. But TWRP can backup your whole android partitions (nandroid backup) that can restore your android if anything goes wrong.
TWRP can flash custom roms, mods, mount partitions, and many more. So, it's better to you have TWRP(custom recovery) installed.
If you are using SuperSU superuser app then in option you found OTA survival that prevent root from OTA updates.
I think you can't get OTA updates because you are rooted. If you get OTA updates and applied on rooted android then it chances of brick your android.

Hi every one. First sorry for bad grammar I am not so good at english. Now to the problem at hand.
Jester day I bought a smj320fn and realise it is not what I paid for, so I tried to root witk KingoRoot and fail. Then I realised there is a "bootlock" witch prevents root (I think it does that).
So I tried ODIN and installed a custom FMW and it worked, allso I instaled a custom twrp and boot win.rar file. and there is the problem.
Every time I hold the power buton the samsung logo apears for 5 seconds and then goes black. It wont take any commands. I tride the recover meny to open, no it wont, but I can restars it to boot again and fails every time.
I tried to do it from a youtube tutorial and maby I know what I did wrong. I Instaled a Sm-j320h boot on my smj320fn so I think thats the problem. Any whay how do I fix this. All and any solution are good.