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

Unroot A510

Hi everyone.
First of all I must say I've searched in this forum before I decided to ask here but I haven't seen anything clear so please accept my apologies if this was already answered. Also my English is not really good.
So this is my question, How can I unroot my Iconia A510??? I need to send it back to the Official Service to be checked.
I used this method to root: http://forum.xda-developers.com/showthread.php?t=1531646
Thanks a lot

You have to flash a stock rom to achieve this. In the following post you can view any version of the stock ROM list. You should notice that not every version is available for download, though any of them should do the job:
http://forum.xda-developers.com/showpost.php?p=27816722&postcount=2
After downloading one of the stock ROMS, rename the .zip file to update.zip, put it in the root of your A510 and then press the volume down button (with the 2 dots) and press the power on switch.
Thanks to nikagl
(Devvers, isn't it also possible to only keep a stock bootloader.blob in the update.zip and than flash it? Or will it only lock the bootloader? Or will it give an error (most likely)?)

Ey, thanks a lot for your fast reply!!
Unfortunately at the moment my A510 has this stock rom "Acer_AV041_A510_1.044.00_WW_GEN1" and it's not avaliable to download :-(
-Do you know If I install another rom it will work?
-Would I lose my guarantee if I change the rom?
-Could I install a lower version and then use the automatic update to go back to the current version?
Sorry for all these questions but I'm in a kind of a hurry trying to take my tablet to the after-sales TS.
Thanks again

The most popular method of rooting the A510 uses the A100 mempodroid exploit. To remove it, you can follow the A100 unrooting instructions in this post:
http://www.acertabletforum.com/foru...g-iconia-a100-made-easy-method.html#post28361
Note that for A510, I think busybox was placed in xbin while su was placed in bin. But the instructions should be pretty much similar.
If you also have custom recovery, it's more tricky to remove that.
Warning: Please make sure that you are using the mempodroid exploit.

You're welcome!
I have had that too with my A700, so I flashed a beta ROM instead. I sent it back with the beta ROM installed and just got a brand new one device back. You could ask on the forum here if anyone could upload the stock ROM "Acer_AV041_A510_1.044.00_WW_GEN1", but trust me, you're lucky if someone will take the time to do that.
Now to answer your questions:
- Yes. It works.
- They're probably not going to even check if you're rooted or having another ROM installed. If unlocking the bootloader voids warranty, then yes. Are they able to see if you've ever unlocked the bootloader, most likely not.
- Depends. If an update has been released by Acer, then yes. If not, then no. But probably not.
You could also try the method mentioned by the user above me (I'm having an A700, so I'm not that familair with the rooting methods with the A510. My apologies.).
Edit:
By the way, flashing a new ROM will of course remove all of your files and settings, so beware.

unable to root/unlock bootloader after repairs?=> Solved (Answer is on page 2)

Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and they've also relocked my bootloader, I think, although I can't get any OTAs.
Original question was:
What can I do to get my root again, because the scripts of sparky's tool don't seem to work anymore...
Sorry for this noobish question, but I swear that this has never happened to me before (and I have unlocked and rooted numerous devices)
What kind of sorcery is going on?!
Click to expand...
Click to collapse
Then I found the answer thanks to these amazing guys answering and trying to help.
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
It might seem complicated, but it really isn't.
Good uck to those who follow(ed) my path

adelancker said:
Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and unlocked bootloader.
Click to expand...
Click to collapse
You mean relocked your bootloader?
...or actually unlocked it?

Thats OK said:
You mean relocked your bootloader?
...or actually unlocked it?
Click to expand...
Click to collapse
Sorry for that!
I meant that they relocked my bootloader, but still I can't get any OTAs
Thanks for the answer by the way.
I'd like to get it back to CR asap, since I really like that ROM, but noone has helped be yet
That is, until you arrived!

Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.

I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.

DarkFire1985 said:
I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.
Click to expand...
Click to collapse
Thanks! I guess I'll downgrade to .30 as well, root it there and maybe attempt to unlock my bootloader.
I really wish to have CR again, so there's no option that this will not work (eventually)

Thats OK said:
Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.
Click to expand...
Click to collapse
Shouldn't I first have root?
Or directly try to unlock the bootloader.

adelancker said:
Shouldn't I first have root?
Or directly try to unlock the bootloader.
Click to expand...
Click to collapse
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.

Thats OK said:
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.
Click to expand...
Click to collapse
Thanks for all the help!
It's not the first time I root (and/or) unlock a bootloader. It's just that now, those super easy root command methods don't work anymore. I have done completely manual rooting in the past, but I am not sure that will work either.
Besides, I got adb running before on my Infinity, but I'll make sure to downgrade to ICS first before doing anything else.
Here's what I am going to do:
1) downgrade to .30
2) try to root (with or without sparky's tool )
3) unlock bootloader (although I'm not sure if that'll work, judging from the comment of the Dutchman above)

I'll let you know in this thread if it worked or not.
My prediction: root will work, unlocking bootloader won't, since it's already been unlocked one and therefore my serial number is already in their database!

So i got my infinity like 2 weeks ago. The first thing i tried to do was to root it. I plugged in my device, installed drivers and checked unknown sources and usb debugging. I opened debugfs and tried to root my device but it suddenly closes. Whats likely to be the problem. And no i dont have asus sync installed.
P.S i returned my infinity on amazon as there was a hardware problem. Ill get the new one in a couple of days.
Thanks in advance.

Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).

MartyHulskemper said:
Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).
Click to expand...
Click to collapse
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!

Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?

DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Hmm... No idea what that could be.
I managed to unlock it, but that was after I reverted to ICS .30 (not obligatory, from what I understood ) I didn't use the Unlock Tool from the Asus website itself but an older (ex-official) Unlock Tool. (v7) I think it was.
I'll have a look and see if I can find it.

That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.

adelancker said:
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
Click to expand...
Click to collapse
So glad to read that you have been successful.
...and do have fun flashing\updating\customizing!

DarkFire1985 said:
That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.
Click to expand...
Click to collapse
The unlock tools provided by ASUS to unlock the TF201, TF300 and TF700 have been proven to be identical files (by checksum verification) --- no need to reinvent the wheel there.
The unlock step indeed is crucial -- and it depends on ASUS' database. If you can't get past that, there'll no flashing available in terms of recoveries (and therefore no custom ROMs either). Have you tried dropping Gary a line yet?

No not yet. Will do that.
Sent from my ASUS Transformer Pad TF700T using xda premium

DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Maybe you should have a look here. Seems like there were a couple of guys capable of unlocking it after all, and they were in the same situation as you.
I checked and the bootloader unlock tool was indeed an offial asus one. I downgraded before unlocking, but I saw you did too...
No idea what else I can do to help.

[Q]

Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time

deathwalker01 said:
Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time
Click to expand...
Click to collapse
Welcome to the Community!
There are a few on-going threads regarding this same topic. You might want to read those and make sure you understand the lingo/jargon being used (like: fastboot, bootloader, Recovery, adb. etc) as well as what it's for before you start your hacking.
Some things to keep in mind
Currently to have Root access in JB, you need to get root in ICS then use OTA Keeper to maintain Root for JB update.
The Bootloader unlocker tool is from ASUS and needs to communicate with ASUS servers for it to unlock.
Unlocking the bootloader will void your warrenty. Make sure you have a good device before you do it.
You have a version of tablet (9.4.5.26) that is able to use NVFlash that can help recover your tablet during a soft brick.
You should use an update that is appropriate for your device. If it comes with US, stay with US. Installing an update for a different region might not cause problems but there is no guarantee. Best to avoid the possibility by staying with the region it comes with.
For some reading material, I think that my blog post might help give you some additional details. However, I highly suggest that it be used for research only until you are aware of exactly what you are trying to accomplish. Remember to ask questions if things are confusing or if you are wondering what needs to be done next. 'Tis better to ask and be delayed than to be over-eager and bricked.
Hope this helps you during your first steps of XDA Android hacking!

I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.

hong90 said:
I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.
Click to expand...
Click to collapse
It's the most efficient way.

I have nothing to add except for the remark that NvFlash is key -- GET IT WHILE YOU STILL CAN!
I'm not even kidding here. It gives you 100% flexibility in doing whatever you wish (up- as well as downgrading, even the bootloader!) and provides a key benefit in recovering your device when that whale-sized piece of excrement hits the large ventilator running at top speed.

Thanks to everyone that has replied to my post. I have successfully rooted the tablet and unlocked the bootloader. Before I do anything else Im going to run NVflash and back it up. I have a quick question though. I have download NVFlash to my computer and extracted it. Do I need to copy it across to the tablet and then enter fastboot? I havent got an extenal sd card will it save the images to the tablet's hard drive?
Cheers
Deathwalker

i followed this video:
https://www.youtube.com/watch?v=J3ypzUaKxvo&feature=youtube_gdata_player
i watched it before i actually did it once or twice to make sure i know what to do. you don't need an external sd card. following the fastboot steps will pull the files that you need onto the internal one in a folder

Last night I used NVFlash to make backup of the tablet. A big thank you to alienedd as I followed his blog and also the guide from androidmobi team and managed to get the img files done. Is there anyway to test bar for wiping the tablet?
Now all I have left to do is install OTA RootKeeper and TWRP, back up the existing tablet and then flash a custom ROM (Im thinking cleanrom)

You don't need OTA Rootkeeper anymore because you have unlocked you're bootloader. And custom roms like Cleanrom are already pre-rooted so after flashing the cleanrom you will have root anyway.

Razr hd downgrade to jb stock firmware

HELLO GUYS
i really need help with my Razr HD , i want to downgrade from kitkat 4.4.2 to jelly bean since the kikat update caused nothing but trouble to me , i am newbie , so please someone help me to downgrade my phone to 4.1.2 step by step and make it simple as possible .
i have RSD lite 6.1 , tried to flash on fastboot mode , got failed flashing process 5/27 error ,
all drivers are installed
i have stock firmware 4.1.1 , 4.1.2 , 4.4.2 xlm files
must mention that my system version is on 183.46.15XT926
Developers mode activated , USB Debugging checked
:angel:

You cannot downgrade from 183.46.15 unless you unlocked your bootloader before upgrading to 183.46.15.
You cannot now unlock your bootloader if you have 183.46.15.
What trouble are you having with KitKat? You can get root, and I then installed Nova Launcher, Titanium Backup, and Xposed Framework with GravityBox to customize things the way I like them.

Spott07 said:
You cannot downgrade from 183.46.15 unless you unlocked your bootloader before upgrading to 183.46.15.
You cannot now unlock your bootloader if you have 183.46.15.
What trouble are you having with KitKat? You can get root, and I then installed Nova Launcher, Titanium Backup, and Xposed Framework with GravityBox to customize things the way I like them.
Click to expand...
Click to collapse
first thank you for replying to me , My bluetooth is gone , i can't seem to connect or send a file to any device
and now so is my wifi , it says saved but not connected and i know it's not router issue because others can connect to the same router with no problem at all

i have Droid razr hd toolkit 5.0 , couldn't unlock my bootloader with it , also couldn't downgrade to jb
how can i root my device using this toolkit with my bootloader still locked ? any instructions please !

First, I'd try reflashing the stock firmware (183.46.15) and see if that fixes your Bluetooth and WiFi problems. I use RSD Lite and it works well. I know the stock firmware works fine on this phone, that's the same configuration I'm using.
To get root, you can either use the "hydrogen peroxide" method, or kingroot. I'd get your radio problems straightened out first before worrying about root.

Spott07 said:
First, I'd try reflashing the stock firmware (183.46.15) and see if that fixes your Bluetooth and WiFi problems. I use RSD Lite and it works well. I know the stock firmware works fine on this phone, that's the same configuration I'm using.
To get root, you can either use the "hydrogen peroxide" method, or kingroot. I'd get your radio problems straightened out first before worrying about root.
Click to expand...
Click to collapse
i tired flashing the stock firmware , but i get this error on the 5th step
i rooted my device , installed superuser , now i am having issue with cmw recovery image
i can't install it on the device

You have to comment a couple of lines out of the install package to get the firmware to flash. There's details in the hydrogen peroxide instructional thread, down where it takes about upgrading from 182.46.15 to 183.46.15.
You can't really install an effective custom recovery (like CWM) with a locked bootloader.
What on earth are you trying to accomplish? If you're trying to fix your WiFi and Bluetooth problems, then both getting root and installing a crippled recovery isn't going to get you there very well. Focus on reflashing the stock firmware first, then come back to root (and don't even waste your time with that broken CWM and the deodexed ROM, they don't gain you anything, and cause more problems than they solve. I soft-bricked my phone three times trying to get anything out of them. The only way to recover from that was to....wait for it....reflash the stock firmware. Notice a pattern here?)

Spott07 said:
You have to comment a couple of lines out of the install package to get the firmware to flash. There's details in the hydrogen peroxide instructional thread, down where it takes about upgrading from 182.46.15 to 183.46.15.
You can't really install an effective custom recovery (like CWM) with a locked bootloader.
What on earth are you trying to accomplish? If you're trying to fix your WiFi and Bluetooth problems, then both getting root and installing a crippled recovery isn't going to get you there very well. Focus on reflashing the stock firmware first, then come back to root (and don't even waste your time with that broken CWM and the deodexed ROM, they don't gain you anything, and cause more problems than they solve. I soft-bricked my phone three times trying to get anything out of them. The only way to recover from that was to....wait for it....reflash the stock firmware. Notice a pattern here?)
Click to expand...
Click to collapse
i am trying to install cm 12 custom rom , since flashing the stock failed many times
i used motoeclipse to unlock the bootloader after rooting , don't know if it works or not
now i am giving a shot at custom roms

You cannot unlock the bootloader of 183.46.15. You cannot install custom ROMs, or even older stock ROMs, with a locked bootloader.
You did not unlock the bootloader, and you're lucky you didn't brick your phone trying.
Sorry, but with that phone and that firmware, there's just no way that anyone's discovered to unlock it (and it's been that way so long that very few are even trying any more).
That rudimentary CWM that's available is not designed for your phone, is only barely compatible, will not allow you to flash custom ROMs, and that fact is stated boldly and repeatedly in the post where you found it. You're stuck with a very specific Motorola 4.4.2 kernel in the bootloader and you can't change it, and if you install a ROM that's not perfectly compatible with it (that is, anything other than the 183.46.15 firmware) you'll end up with a phone that won't boot.
You might be "giving it a shot" but your magazine's full of blank ammo.
You must slow down and read carefully before you brick your phone, because you've already missed a lot of important information that you'll need to keep you out of trouble.
Also, if you can't figure out how to flash a stock ROM, you're not qualified to pursue custom ROMs even if you could. What do you think happens if a flash fails and you're stuck with a soft-brick? The only way out of that is to flash a stock ROM and start over.
You have two options at this point: Either accept your phone the way it is without Bluetooth and WiFi, or do the research necessary to learn how to reflash the stock ROM and fix your problem. Here's a hint: I know exactly why your flash attempts failed, and it's quite easy to fix it, and I've already told you where to find the information to do so, in a previous post.
Now you're on your own, as I probably cannot help you any more.

how can i get pass the 5th step is rsd ?
i wanna go back to the same stock firmware4.4.2 or downgrade to 4.1.2 but i cant

sorry sir for bothering you , i am just doing researches haven't done anything passed the root
my phone status now : rooted with superuser , stock recovery still in
bootloader still locked
i have heard of this tool DROID_RAZR_HD_Utility_1.41_KK here: http://forum.xda-developers.com/showthread.php?t=2474393
i don't know what to do ?

You must slow down and read carefully. Especially the first paragraph of post #7.
It's not useful to do research if you don't read the results.

Spott07 said:
You must slow down and read carefully. Especially the first paragraph of post #7.
It's not useful to do research if you don't read the results.
Click to expand...
Click to collapse
thanks , just to let you know , i have found the same stock firmware and flashed successfully , still with wifi and bluetooth issues
i have been told that downgrading to jelly bean will sort all my issues
waiting for advice , don't know what to do next

I don't know who told you that downgrading to JB will help you, but they're wrong, because 1) it's impossible for you to downgrade, and 2) the KK firmware works quite well with very few bugs.
Perhaps the wireless chip inside your phone is damaged. Does the GPS work?
Perhaps the wireless service is disabled in the settings. Do you have airplane mode turned on? Do you have WiFi and Bluetooth disabled? Have you tried deleting or "forgetting" your WiFi connection, and then re-entering it again from the beginning?

i tried all of this , airplane mode , wifi advanced settings , everything
what if i downgraded the kernel from 15 to 10 , would i be able to unlock my bootloader and downgrade to jelly bean ?

You cannot downgrade the kernel. It's within the locked bootloader. I told you that in post #9.
You cannot unlock the bootloader on this phone. End of story. Hundreds of the best developers have tried every possibility they could think of, and have given up.
Perhaps some miracle will occur and someone will find a way, but don't count on it. This phone is old and those with the proper skills have moved on to newer, better things. As of right now, and for the foreseeable future, it is impossible.
Also, you never answered whether your GPS works.

flashed back to stock , now my wifi works outta nowhere

Sorry, I got confused about the conversation, I'll explain below.

it's not like that , first i followed your instructions and flashed the stock 183.46.15 , when nothing worked then i flashed the modified 183.46.10 suddenly wifi started to pick up signals , then drops every once and a while
i have no issues with rooting , i can root the device in minutes which i have

Sorry for being so rude earlier, I got confused.
I usually use the Tapatalk app to read these forums, but right now the login server is down, so I had to log in on the website. When I looked on the website, the screwy timestamps appeared to indicate that you had replied a couple hours ago, so I clicked on the link. (The timestamp options are terribly difficult to find, so I hadn't corrected them for my timezone, and then forgot that fact.) Instead of taking me to the last post in the thread, it displayed the first page of 10 posts (I'm used to seeing 50/page with Tapatalk) and I saw your (old) post at the bottom asking how to get the firmware to flash with RSD. At that point I got frustrated and failed to check any farther, and responded as if that were another repetitious request for the same information.
So, between the Tapatalk login server, the awkward behavior of this site, and my frustration and impatience, I responded very badly.
You didn't deserve that response, and I'm sorry.
I don't know why re-flashing the 183.46.15 firmware didn't work, it has few bugs and is pretty stable for everyone who's stuck with it. I don't know anything about any "modified 183.46.10" firmware that could be flashed on our phones, where did you find that? Are you referring to this? If so, it's great that it works, but it's risky and certainly won't permit you to unlock your bootloader.
Scott