This is a guide to loading a custom rom onto your TELUS HOX+ device if you have no rom but have bootloader access.
I would recommend using the HTC One X+ All-In-One Toolkit V1.1 from hasoon2000.
It can be found here
You will need the HTC drivers installed and adb/fastboot to do this process. You can the newest adb/fastboot here
Using the HTC One X+ All-In-One Toolkit V1.1
Step 1 - Unlock your bootloader with the Toolkit
Step 2 - Get into the bootloader>fastboot
Step 3 - Flash the TWRP(ATT Model) recovery via the Toolkit
Step 4 - Reboot into recovery
Step 5 - Choose advanced tab in TWRP Recovery(should be bottom left)
Step 6 - Choose ADB Sideload
Step 7 - Pick a rom you wish to load. Because we are TELUS and have a hboot 1.32.0000 with no RUU or firmware update you can only choose 1 of 4 roms atm
1st rom that will work is [ROM][AT&T/Telus][12-1-12] QX Senseless v2.1 | Lightweight | OTA Updater | JB 4.1.1 here
2nd rom that will work is [ROM][ATT]InsertCoin 1.1.3 |JB & Sense 4+|STABLE & FAST|APM|%Battery|JellyBlue here
3rd rom that will work is [ROM] |ATT & TELUS| █ ELEGANCIA™ █ ◄| 2.3.1 |►| Stock & Colored | Sense & Senseless | here
4th rom that will work is [ROM][Dec 15] Blackout 1X+ v1.0 U.S AT&T [4.1.1][JB Sense 4+][Mods][Insecure Boot] here
Don't ask me why but I have flashed every rom and those were the only ones to actually boot. Might be because of our 1.15.661.11 base.
Step 8 - Once you have the rom, run adb sideload “rom”.zip from your command prompt on your pc.
The “rom” is whatever the name of the custom rom you downloaded. I put the rom in the directory of my adb to make things simple.
If you are running into trouble you might have to do some commands to help the pc see your device.
So run the adb kill-server command
then run the adb device command
if it sees the phone
then run the adb sideload command
You might have to alt ctrl del windows and kill adb.exe as well
Just make sure your ADB version is at least 1.0.31.
At this point you should be in the TWRP Recovery > Advanced Tab > ADB Sideload on your device and your "rom" that you uploaded via sideload should be installing on your device.
If you need to re-flash the rom, as long as you have completed a full boot if you go back into Recovery>Install>/sdcard, it will be labelled as Sideload.zip
Step 9 - Reboot into bootloader and flash the boot.img from the rom via fastboot flash boot boot.img from your command prompt on your pc. I also put my boot.img in the adb folder to make it easier when flashing anything.
*at this point it wouldn't hurt to do a fastboot erase cache* Optional
Step 10 - Once your rom boots you have to add TELUS APN
Settings>Mobile data>Access point names>Menu>New APN
Name: TELUS SP
APN: sp.telus.com
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
Server: Not set
MMSC: http://aliasredirect.net/proxy/mmsc
MMS Proxy: 74.49.0.18
MMS Port: 80
MMS Protocol: WAP 2.0
MCC: 302
MNC: 220
Authentication type: None
APN type: default,mms,hipri
APN enable/disable: APN enable
Bearer: Unspecified
http://androidforums.com/hero-support-troubleshooting/45005-mobile-network-apn-settings.html
Tethering APN (Only use the following 3 fields, leave all other fields Not set or default)
Name: TELUS ISP
APN: isp.telus.com
APN type: dun
https://www.telusmobility.com/en/ON/phones-and-devices/setupdata.shtml
This will allow you to have data on your phone.
If you want to revert back to stock...just click here and flash the RUU
This is just an initial write up. I will make changes as my thoughts get collected better
Thanks to:
Hasoon2000 for his awesome toolkits
mfpreach for input
Right on point. Wish I had had this when I originally flashed.
PS. Should add isp.telus.Com apn for tethering.
Sent from my HTC One X+ using xda app-developers app
mfpreach said:
Right on point. Wish I had had this when I originally flashed.
PS. Should add isp.telus.Com apn for tethering.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip! I added it. Not sure if I added it correctly or not. I'm unclear as to where...does it get its own APN and when you want to tether, you are required to switch them?
Cheers
Clonz said:
Thanks for the tip! I added it. Not sure if I added it correctly or not. I'm unclear as to where...does it get its own APN and when you want to tether, you are required to switch them?
Cheers
Click to expand...
Click to collapse
Make sure to change the APN type to "dun"
otherwise the rest of the settings leave default
Just add it, I'm fairly confident you don't have to switch it, when you set the apn type it knows.
If anyone is interested in "purchasing" the stock Ruu, I got $10 on it, need another $10. PM me and we'll sort it out (it's not me selling it FYI).
Clonz said:
At this point you should be in the TWRP Recovery > Advanced Tab > ADB Sideload on your device and your "rom" that you uploaded via sideload should be installing on your device
Click to expand...
Click to collapse
wrong, it doesn't install automagically, you need to install "sideload.zip" like any other rom from the install menu
Lloir said:
wrong, it doesn't install automagically, you need to install "sideload.zip" like any other rom from the install menu
Click to expand...
Click to collapse
Umm I would have to politely disagree Lloir...from my experience in doing this several times, as soon as the sideload file has finished uploading to the device, on all occasions, the aroma installer automatically starts and in the case of the QX Senseless it just installs.
You need to understand that my TUT is for people that don't have a rom on their phone. This means that there is no zip file(rom) on their /sdcard so they can't choose install .zip file nor can they mount the system or cache as they don't exist at this point.
Thank you for your input tho
Cheers!
I agree my aroma started automatically too. I did have to manually flash it for some reason though. If anyone needs to the rom will be named sideload.zip
Sent from my HTC One X+ using xda app-developers app
Awesome. Changed it on my phone and it works perfect! Tx
Also updated it
20 bucks sounds cheap although I have never bought one before. I would be willing to get in on that if it was legit
Clonz said:
Awesome. Changed it on my phone and it works perfect! Tx
Also updated it
20 bucks sounds cheap although I have never bought one before. I would be willing to get in on that if it was legit
Click to expand...
Click to collapse
I'm sure it is, that's what football quoted me, and he's the guy that releases all the RUUs.
I'll message him and let you know.
mfpreach said:
I'm sure it is, that's what football quoted me, and he's the guy that releases all the RUUs.
I'll message him and let you know.
Click to expand...
Click to collapse
Sounds awesome. Thanks
Hi thanks for the help. Sorry for the dumb question but i really dont know how to do this.
Can someone please explain step by step how to perform step 8
Step 8 - Run adb sideload “rom”.zip from your command prompt on your pc. You need HTC drivers installed and adb / fastboot Where “rom” is whatever the name of the rom you downloaded is. I put the rom in the directory of my adb to make things simple. If you are running into trouble you might have to do some commands to help the pc see your device.
So run the adb kill-server command
then run the adb device command
if it sees the phone
then run the adb sideload command You might have to alt ctrl del windows and kill adb.exe as well
Just make sure your ADB version is at least 1.0.31.
At this point you should be in the TWRP Recovery > Advanced Tab > ADB Sideload on your device and your "rom" that you uploaded via sideload should be installing on your device.
Im so lost!
rgdutriz said:
Hi thanks for the help. Sorry for the dumb question but i really dont know how to do this.
Can someone please explain step by step how to perform step 8
Step 8 - Run adb sideload “rom”.zip from your command prompt on your pc. You need HTC drivers installed and adb / fastboot Where “rom” is whatever the name of the rom you downloaded is. I put the rom in the directory of my adb to make things simple. If you are running into trouble you might have to do some commands to help the pc see your device.
So run the adb kill-server command
then run the adb device command
if it sees the phone
then run the adb sideload command You might have to alt ctrl del windows and kill adb.exe as well
Just make sure your ADB version is at least 1.0.31.
At this point you should be in the TWRP Recovery > Advanced Tab > ADB Sideload on your device and your "rom" that you uploaded via sideload should be installing on your device.
Im so lost!
Click to expand...
Click to collapse
OK I see where it could be confusing, maybe the OP can edit the instructions
In TWRP go to advanced and select 'adb sideload' YOU CAN then run the adb sideload command from the command prompt.
put the rom.zip (whatever you are using it will have a different name) in the adb folder where adb.exe is
Then run: adb sideload rom.zip (replace 'rom' with whatever the filename is)
It will run aroma automatically. If it still doesn't boot, go into TWRP and install the sideload.zip from the internal storage.
You must do this because there is no way to mount the phone like you can with samsung or other phones.
PS: I didn't bother with the adb kill server command.
Gl
mfpreach said:
OK I see where it could be confusing, maybe the OP can edit the instructions
In TWRP go to advanced and select 'adb sideload' YOU CAN then run the adb sideload command from the command prompt.
put the rom.zip (whatever you are using it will have a different name) in the adb folder where adb.exe is
Then run: adb sideload rom.zip
It will run aroma automatically. If it still doesn't boot, go into TWRP and install the sideload.zip from the internal storage.
You must do this because there is no way to mount the phone like you can with samsung or other phones.
PS: I didn't bother with the adb kill server command.
Gl
Click to expand...
Click to collapse
I will try to make it more clear...remember it was an initial draft still working on clearing up directions
mfpreach said:
OK I see where it could be confusing, maybe the OP can edit the instructions
In TWRP go to advanced and select 'adb sideload' YOU CAN then run the adb sideload command from the command prompt.
put the rom.zip (whatever you are using it will have a different name) in the adb folder where adb.exe is
Then run: adb sideload rom.zip (replace 'rom' with whatever the filename is)
It will run aroma automatically. If it still doesn't boot, go into TWRP and install the sideload.zip from the internal storage.
You must do this because there is no way to mount the phone like you can with samsung or other phones.
PS: I didn't bother with the adb kill server command.
Gl
Click to expand...
Click to collapse
no dice!
rgdutriz said:
no dice!
Click to expand...
Click to collapse
Try killing the server as the OP Suggested.
This is indicating that the phone isn't being detected by your computer.
Have you flashed the elegancia kernel yet? Do that before you install the rom.
rgdutriz said:
no dice!
Click to expand...
Click to collapse
try to end task adb.exe in your windows task manager. Once you have done that you can do an adb device...if it sees your phone then you should be able to continue with the upload.
Edit: You can also try trolling through this thread http://forum.xda-developers.com/showthread.php?t=1987885 there is a convo between me and another person doing the same thing but with more dialog it starts at post #818
Clonz said:
try to end task adb.exe in your windows task manager. Once you have done that you can do an adb device...if it sees your phone then you should be able to continue with the upload.
Click to expand...
Click to collapse
No device found. How do I do this "TWRP and install the sideload.zip from the internal storage". Also please dm your email I will send donate for your help
---------- Post added at 05:23 PM ---------- Previous post was at 05:17 PM ----------
mfpreach said:
Try killing the server as the OP Suggested.
This is indicating that the phone isn't being detected by your computer.
Have you flashed the elegancia kernel yet? Do that before you install the rom.
Click to expand...
Click to collapse
How do I flash the elegancia kernel? Also will donate to the cause dm email
ugh since im a n00b i have to wait 5 min between posts
rgdutriz said:
No device found. How do I do this "TWRP and install the sideload.zip from the internal storage". Also please dm your email I will send donate for your help
---------- Post added at 05:23 PM ---------- Previous post was at 05:17 PM ----------
How do I flash the elegancia kernel? Also will donate to the cause dm email
ugh since im a n00b i have to wait 5 min between posts
Click to expand...
Click to collapse
Take the boot.img out of the elegencia.zip and flash it via Hansoon's tool, his tool tells you where to put it.
OR
Put the boot.img in the fastboot folder and run:
fastboot flash boot boot.img
fastboot reboot
You can donate to me so I can buy the STock RUU for Telus for all of us!
mfpreach said:
Take the boot.img out of the elegencia.zip and flash it via Hansoon's tool, his tool tells you where to put it.
OR
Put the boot.img in the fastboot folder and run:
fastboot flash boot boot.img
fastboot reboot
You can donate to me so I can buy the STock RUU for Telus for all of us!
Click to expand...
Click to collapse
I would add the fastboot erase cache after you flash the boot.img just for good measure
Clonz: how many bars of LTE do you get on the reg? I'm usually 2, no higher than 3. I get blazing speeds though.
Related
How-TO Root the
HTC Slide
HTC Aria + See this Link > http://forum.xda-developers.com/showthread.php?t=708233
&
Nexus One
Works With ALL 2.1 HTC PHONE"S with 2e Recovery!
Must be able to See the Device From the ADB in recovery for it to work!
See this Thread if you Have a New Slide or Updated the OTA to version 1.35.531.1
http://forum.xda-developers.com/showthread.php?t=754669
If at anytime You have Trouble or Can't get my Method to work, Please see wesgarner's [Root] SimpleRoot v1.3 (Linux/Windows)
Link > http://forum.xda-developers.com/showthread.php?t=713347
Just use my Update.zip if you just want root only
Download This Package > Root.zip
*EDITED* 6/29/2010 Update Now Contains Su & Superuser.apk. Permission Fixed on SU / Sh as well
-Contains Dusty51 script for Partitioning the a2sd & Swap
-fstab install so swap will work
-Default partition table's are:
-Linux Swap @ 32mb
-ext2 a2sd partition @ 512mb
-Fat32 Partition is based on the size after the 2 above
How-to Use:
Once You load the Recovery via update.zip, Unplug & Plug the USB to make sure the Device is Seen..
- Open Command Prompt from Computer
- Adb shell
- sdparted
- Next Follow the Command, y = Y to confirm..
Note: Backup your SDCARD first, only thing should be on it is the update.zip then Follow the above to Format for a2sd support!
Click to expand...
Click to collapse
Stratis1978 said:
I've got root now and just wanted to repeat what made the difference for me (also posted pages back):
when you're ready to run recovery in the bootloader be sure to unplug the USB from your phone until 'HBOOT' not 'HBOOT USB PLUG' displays.
So basically you unplug the phone until 'HBOOT' appears, have 'RECOVERY' highlighted, and plug the phone in a moment before you select 'RECOVERY'.
The moment I did that I had 'recovery' displaying in my loop.
Continue with the directions...
Click to expand...
Click to collapse
How-TO Root the Slide
First!! - Go to Settings > Application > Development and turn on USB Debugging. This should save you headaches.
NOW… Power Off the Slide
Step 0.
Un-zip the Package you Downloaded
Step 1.
Place the Contents of "update.zip" & "ota.zip" & "loop" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like) ( ./ Is used For OSX )
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Hit Volume Up + Power button to Bring up the Selectable Menu
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please.)
Step 11.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
This is the Command, We do not Push this Yet adb push update.zip /sdcard
Click to expand...
Click to collapse
step 12.
Hit run update.zip, as soon as you see a Little Bar appear under the text, push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 13.
In successful, you should see Clockwork Recovery & you Now have Su & Superuser.apk Installed! You can Now Reboot Your Phone into the OS to verify.
If unsuccessful, repeat steps 11 & 12.
Congrats.
Next Guide For Flashing the ENG-BUILD with Test-key Recovery http://forum.xda-developers.com/showthread.php?t=703076
Updating the Radio Once Everything Is Done http://forum.xda-developers.com/showthread.php?t=705064
Special Thanks to:
Paul O'Brien: > http://android.modaco.com/forum.html
Koushik K. Dutta: His ClockWorkMod Recovery can Be found here > http://www.clockworkmod.com/
&
http://unrevoked.com/ OTA Spoofing Method
&
ChiefzReloaded for Huge amount of Suggestion & Brain Storming.
GREAT JOB!
Thank you sir, for your diligence, and hard work! Let's get to work boys!!!
Tips: May want to be a little more clear on "SDK Directory". Some may think that you "must" have this directory, but all that is important to know is that you know the directory where the contents were placed... If that IS the case, then I'd mention that...
Also, might be important to mention the phone should already be plugged in, and should have prerequisite of ADB working...
Thaaaaaaank you! got some fun stuff to do right after work now
Re: How-TO * Root The Slide * *6/15/2010*
Thanks guys. You've made a lot of people happy.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Having trouble at step 5. ADB works when the phone is powered on. However, when in Recovery, adb devices list is blank.
Other problems: is Step 8 really a step? It says to select Update.zip... is this just anecdotal, as in "Now we will select an update.zip"...?
And how are you "selecting" things in Recovery? My recovery simply has the phone with a triangle...
What is ADB i come from rooting g1 and i dont remember or know what it is i rooted my g1 when it first came out and every since then all i had to do is name file update then push. could u be alittle more clear for a retard like me I dont want to miss my phone up when i just got it today, I really want to get rid of some of the bloatware on it tho
richierich118 said:
What is ADB i come from rooting g1 and i dont remember or know what it is i rooted my g1 when it first came out and every since then all i had to do is name file update then push. could u be alittle more clear for a retard like me I dont want to miss my phone up when i just got it today, I really want to get rid of some of the bloatware on it tho
Click to expand...
Click to collapse
ADB is part of the Android SDK, you'll need to download it and extract it to your PC before you can use it.
http://developer.android.com/sdk/index.html
My problem may be that I'm using a Mac, but I cannot get my Terminal to recognize the "loop" command. I've tried many things and it won't work properly just keeps giving me errors. I'm gonna keep trying though.
android007 said:
My problem may be that I'm using a Mac, but I cannot get my Terminal to recognize the "loop" command. I've tried many things and it won't work properly just keeps giving me errors. I'm gonna keep trying though.
Click to expand...
Click to collapse
Loop is just a batch file (.bat). I don't know about Macs using batch files. All it's doing is looping the "adb devices" command to see if it detects the device.
fermunky said:
Having trouble at step 5. ADB works when the phone is powered on. However, when in Recovery, adb devices list is blank.
Other problems: is Step 8 really a step? It says to select Update.zip... is this just anecdotal, as in "Now we will select an update.zip"...?
And how are you "selecting" things in Recovery? My recovery simply has the phone with a triangle...
Click to expand...
Click to collapse
You have to Repeat then... It Don't always work everytime!! That's why I said Repeat.. You have to Power Off, run loop & if you see now Devices then you have to Repeat again!!
You Must boot into bootloader First!! Run Loop, Then to Recovery!
my computer doesn't find the device in recovery mode. Any advice on getting around this? adb works when phone is on.
eugene373 said:
You have to Repeat then... It Don't always work everytime!! That's why I said Repeat.. You have to Power Off, run loop & if you see now Devices then you have to Repeat again!!
Click to expand...
Click to collapse
Wow, cant believe I missed that order. May need to update the how to though... it says to run loop, then go to bootloader, then to recovery. You need to add a step after getting into bootloader of "Wait for device to be listed, then goto recovery"... or similar.
My error when trying to invoke the loop file:
: command not founde 1: :TOP
sdk/tools/loop: line 2: adb: command not found
sdk/tools/loop: line 3: GOTO: command not found
Click to expand...
Click to collapse
Sweeeet! Awesome job guys.
On Mac replace the loop.bat with loop.sh and change the contents of the file to the following:
#!/bin/bash
while [ 1 ]
do
adb devices
done
On the command line, run "chmod 755 loop.sh" to give it execute permission. To run the file type "./loop.sh"
Are there any roms for it yet?
android007 said:
My error when trying to invoke the loop file:
Click to expand...
Click to collapse
You have not added the tools directory to your PATH system variable. Explained on the SDK page. Also, you don't need to be in the /tools folder, just go to the folder you extracted the files to.
Eugene, I noticed while the loop was running, I chose recovery, and on one instance, I saw an offline device, but then subsequent loop commands, it stopped listing them. Also, it is still not clear what to do on Step 8. Most of us only see an image in recovery, no menus.
With no menus, anyone know how to reboot the phone in recovery other than removing the battery?
marvinp said:
On Mac replace the loop.bat with loop.sh and change the contents of the file to the following:
#!/bin/bash
while [ 1 ]
do
adb devices
done
On the command line, run "chmod 755 loop.sh" to give it execute permission. To run the file type "./loop.sh"
Click to expand...
Click to collapse
you think you can do quick little rewrite of the tutorial for us mac users
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
hahmoode said:
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
Click to expand...
Click to collapse
On an unlocked device I don't think there can be aproblem to install a recovery.
All methods (terminal one or apps like Rom Manager and Goo) are in fact the same, copying the img or blob file in the flash partition, and the real flash occurs at next boot.
hahmoode said:
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
Click to expand...
Click to collapse
yes should be in Q & A
1. YOU ARE NOT RUNNING ASUS SOFTWARE ANYMORE. THAT IS WHY ASUS PROVIDED A WARNING WHEN YOU UNLOCK. YOU SHOULD EXPECT ISSUES WITH ROMS, IT IS BOUND TO HAPPEN.
2. The full wipe of the internal SD is for a fresh start. Its basically the same as re-installing windows, Kiss all your stuff goodbye unless you back it up beforehand. Don't cry to use that you lost your stuff because you decided to rush and not read the menu and select the correct choice.
3. Team Wookie are normal people with normal jobs and somewhat normal families that in turn this things take priority first, NOT YOUR PRIME. If issues arise we will work best with you as long as you are respectful and not a prick towards the team demanding stuff. We will address these issues on our clock, not yours.
4. Any future things you would like to see in future editions of this ROM please send me a PM and I will forward the information on to the rest of the team to discuss if it is possible. Keep in mind that we will not include paid apps in this rom because we will not rob out of other developers pockets for their hard work and also dropping the soap in prison leads to bad things that we want to avoid. JUST BECAUSE A REQUEST IS MADE IT DOES NOT GUARENTEE THAT IT WILL BE HONORED OR IN THE NEXT VERSION WHENEVER IT COMES OUT.
5. Team Wookie greatly appreciates all it's followers and feedback so don't ever think that your not appreciated, at least when it comes to a rom on a tablet level, the rest of your real world life is on you.
6. RESEARCH RESEARCH RESEARCH. We know there are a lot of posts now, 178ish pages and growing, please search through these pages to see if a solution has been found to your problem first before posting.
7. This is not the forum to ask how do I root my tablet or flash a rom. There are plenty of other threads on XDA and videos on youtube that explain how to do it with the current version software that you have.
This has been a public service announcement from Team Wookie, Long live the rebellion.
---------- Post added at 09:14 AM ---------- Previous post was at 09:06 AM ----------
Download goo manager from the play store and in the upper right hand corner select recovery. It will ask for superuser permissions then let it do its thing. However it will not show a progress bar or anything but rather just go back to the main menu. Just wait a few minutes and you will ge a pop up saying it is now installed.
---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------
This is not an issue because the rom is designed to work this way and I have flashed it this way many times. I have a video coming up shortly showing the whole install from twrp to desktop, im just editing it now. If anyone is feeling scared about doing this before you flash get the adb software package and try to push a test file to your tablet ( i just made a test.txt file) and see if it actually works. If the poop hits the fan then you know you can always push the zip file back because you confirmed ADB working with your computer and tablet.
For those having ADB issues follow this guide I made up. the best thing to do is to try to push a test file before you flash is you are going to super wipe and if you are really that nervous about it. This is based off of windows 7 64 bit but should be the same for windows 7 32 bit. I can confirm this works. Regardless ADB is good to have if you run any Android devices, not just this ROM so in case poop ever hits the fan here ya go:
This solved it for Winblows 7 64 bit. For others having the same problem on Winblows 7 64 bit (should be the same for 32 bit miuns the X86 Directory)
1. Go into settings on the prime and make sure USB debugging has a check in it in under SYSTEM > Developer options > USB Debugging
2. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers. If you see at the top of device manager ASUS Android devices and when you expand it you see ASUS Android Composite ADB Interface you already have the ADB drivers installed and can skip down to #6
3. Go to ASUS website and download the USB drivers for the TF201. Download Vipermod Primetime 4.6 here for the ADB drivers http://goo.im/devs/viperboy/Prime/vi...eTime_v4.6.zip then extract the zip file to a normal file. You only need the drivers from the tool.
4. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers.
5. You should see the prime listed under portable devices. Uninstall the driver then update the driver manually. Browse to the folder you created from the Vipermod primetime zip. Make sure there is a check in check sub folders. Winblows should detect the drivers and then convert the prime to a ASUS Android Device.
6. Go into settings on the prime and make sure there is no check in Launch ASUS Sync under PERSONAL > Accounts & Sync > Launch ASUS Sync
7. Press Control, Shift, Escape at the same time and make sure there are no instances of ASUS Sync or Splashtop runnung in services in Winblows 7.
8. Download and Install the latest Android SDK. I installed all the libraries and such just to be on the safe side. http://developer.android.com/sdk/index.html
9. DISCONNECT YOUR PRIME FROM THE USB AND REBOOT YOUR PRIME AND YOUR WINBLOWS LAPTOP. After both devices reboot plug in your tablet into your Winblows laptop.
10. Navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools and click on the ADB file. A command prompt will open and spool up a bunch of stuff then close. All the stuff spooling I am assuming was the ADB server starting.
11. Hold down shift then right click inside platform-tools folder and select open command prompt here. You should be in a command prompt window showing the directory C:\Program Files (x86)\Android\android-sdk\platform-tools
12. type adb devices. You should see your primes serial number pop up.
13. make a test file in the platform-tools directory, i just used a simple text file to test then type:
adb push test.txt /sdcard/
It would be easier to just put the Rom you are going to flash in this directory so when it is time to push the rom it would be:
adb push nameofrom.zip /sdcard/
If SDCARD not recognized try:
adb push nameofrom.zip /system/media/
14. browse to your sdcard and you should see your file there. If you are already in the sdcard folder window on your prime, leave the folder then come back and it should be there.
15. You should be able to push files now after superwiping. You may need to push to /system/media/ if /sdcard/ is not found. Make sure you have all the / in the directory structure when pushing.
16. From inside recovery select install zip from sdcard and browse to the folder you pushed it to then flash awa
Sent from my Transformer Prime TF201 using xda app-developers app
So with those steps it still hasn't installed recovery! So the thing is that i have full root, and my prime is unlocked, but it just WONT install recovery using any app or manually! Is there a idea on why my prime wont let me?
(Thanks for that long answer btw i tried a lot of it but stil no dice )
Have you tried twrp? The link is HERE. I found its more reliable on the prime. Just my opinion.
fredgar75 said:
Have you tried twrp? The link is HERE. I found its more reliable on the prime. Just my opinion.
Click to expand...
Click to collapse
I will deff try it when i get home from work thank you i will let you know later! (THANKS SO MUCH FOR SOME MORE ADVICE ON THIS)
Ok just to be sure. You did unlock through asus? And you are rooted I know you said you have but just want to make sure. The only reason you wouldnt be able to flash a recovery is if your not unlocked. Just trying to rule out the obvious.
Simple steps:
1-Unlock prime
2-Download the ROM of your choice.
3-Download Goo Manager from the Play Store. Open it and hit menu - Install OpenRecoveryScript. The app will ask for su perms and may exit back to the main screen. Hit the install button again and the app will download the recovery, flash it and reboot. You'll see the flashing process and your tablet will reboot again. At this point you can hold vol down, then up to enter recovery.
4-Flash ROM
5-Profit!!
Doesn't get any easier, takes about 10 minutes for everything.
I used the multi root tool, viper mods tool I think it was, from a long time ago that was designed for rooting the .15 firmware, even though I was on .21 or .28 and I didn't use it to root, I only used the option to install recovery, which installs the latest TWRP recovery when I had a similar issue.
It worked great, I just ran the program on the computer and told it to install recovery.
Sent from my ADR6425LVW using xda premium
Hi to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
I wanted to get rid of some apps that I dont use at all e.g Amazon Kindle but found out with research that I can do that. Also tried to use apps like Titanium Backup again I couldnt. I am new to the Tablet world this is my first. So I did some research and terms of root, unlock etc came up. So I know the difference between them. In order not to lose my warranty and since I just want to be able to delete certain unwanted apps and add other apps, I just want to for now root my TF201.
Did more research but I still cant get an answer or get some of the methods to work for me.
Below is the specs for my Asus TF201
1. So I have JB (Android Version 4.1.1), dont know if it came with it or got updated like I said I didnt mess with the tablet alot
2. Build #: JRO03C.US_epad-10.4.2.17-20121018
I plugged in the USB to my Windows XP laptop for the first time today and ofcourse I am missing the drivers. I went to ASUS website and couldnt figure what I need.
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB
ramez75 said:
Hi to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
*SNIP*
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB
Click to expand...
Click to collapse
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
TWRP Page
On that page are instructions including a download link for JB BOOTLOADER ONLY! MAKE SURE YOU GET THE RIGHT TWRP FILE FOR YOUR DEVICE. THE ICS ONE IF YOU ARE ON ICS, OR THE JB ONE IF YOU ARE ON JB:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
When that is downloaded you can compare the MD5 hash because its a good idea to do that. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it saysthe files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Copy the unlocker APK to the SD card. Run a file explorer on our tables and browse to the SD card (/Removable/MicroSD). Tap the APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
if you don't get the command window here option then you will have to open a command prompt. open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tab must be plugged in to the USB port of the computer of course.
If you installed the SDK tools it is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Edits:
I have editted this based on questions below to make it more complete..
First Thank yo uso much for taking the time and sharing the good info. Ofcourse there is alot of foreign terminology you have used and I will need to read you reply a number of time till it soaks in and I am sure I will have follow-up questions.
So it seems the only way I can get to root my TF201 (running JB) is to unlock it which means losing the warranty. Well if thats the only route then so be it....
I guess first thing is to successfully unlock the TF201
hx4700 Killer said:
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Run the unlocker tool you downloaded. For here its fuzzy for me because I found the APK file I got from the Asus download and copied it over to my tablets SD card via USB. Then I used the built in file browser to find it on my SD card and ran it. By whatever means you will need to run the unlocker tool on your tablet to unlock. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed. ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse
Yes, unlock it. There is no root method for tf201 on JB outside of unlock. An exploit may come up some day but nothing soon I would wager.
I tried to organize it by Al the stuff you need to download first. Then steps to use what you downloaded. It you follow it precisely things would become clearer.
Hi,
Ok I was going through the instructions and downloading all the necessary files and I ran into an issue with downloading the TWRP for JB. Well the link you have allows me to download either the *.img or the *.blob extensions. So I went ahead and downloaded the *.blob extension. I did the MD5 as you recommended and visually checked it with the image on the website and they dont match. I got the below
"b6bae17dac81a126d5d3ad8e27fd5007" which is entirely different than the one on the webpage. I also tried the *.img and no luck there. So I stopped. What do I do now where can I get the TWRP
Thanks
hx4700 Killer said:
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Click to expand...
Click to collapse
hx4700killer
I did some googling and found the below link
http://forum.xda-developers.com/showthread.php?t=1510737
the link has "Direct apk link (dropbox)"....Is this what you referred too? I downloaded the file, should I move it to the SD card and run it from within the tablet?. Is there a way to run an apk file.
Also
I downloaded Android SDK on my laptop. I run the eclipse.exe as per the instructions on the website but nothing happens
Thank you
RB
Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.
The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app
ramez75 said:
The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
The second link that says it is for the unlock tool is the APK.
Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
hx4700 Killer said:
Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.
Click to expand...
Click to collapse
ramez75 said:
Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
Click to expand...
Click to collapse
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.
Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
hx4700 Killer said:
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.
Click to expand...
Click to collapse
ramez75 said:
Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
Click to expand...
Click to collapse
This is the MD5 hash that you should get:
19d93f4ec4685b8124468684eb2913fc
This is the exact download link I used for my TF201 running the most recent JB Update:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
The file you get is: openrecovery-twrp-2.3.1.0-tf201-JB.blob which is the one I say to rename to twrp.blob
I would NOT flash anything not from the source on this one. If its wrong your device is trash.
Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
hx4700 Killer said:
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
...
Click to expand...
Click to collapse
Yes, just open CMD and "cd" your way to the directory. Just make sure you end up inside the directory (ie. "...\UBTv1.3.2>")
ramez75 said:
Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
Click to expand...
Click to collapse
Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
hx4700 Killer said:
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse
ramez75 said:
Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
Click to expand...
Click to collapse
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.
By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
hx4700 Killer said:
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.
Click to expand...
Click to collapse
ramez75 said:
By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
Click to expand...
Click to collapse
What I meant was I use ADB from that root method from bin4ry. He includes ADB.EXE and needed DLL files so its a quick one stop shop for ADB.
Does the adb shell command give you anything? No its just proves root is available. Rootcheckers can also do it. ADB is just a way in to your device from a desktop machine.
I have never removed an APP but I believe removing its APK file from /system/app folder allows it to be removed or does remove it. ( i would save it somewhere in case you need/want it back)
Thank you for an easy to follow way to root a 4.1.1 JB OTA TF-201. It worked exactly as you described.
You may want to let some of the noob users know what in each zip file they need. It really helps if all the files you download are in one location unless you are familiar the windows command line.
HOX+ Tutorial for Unlocking, Rooting & installing a custom ROM [BEGINNERS FRIENDLY ]
[SIZE="+2"]-- Step-by-Step Tutorial for Unlocking, Rooting and Installing a Custom Rom for your HTC ONE X+ --[/SIZE]
Here is my beginner friendly manual method for Unlocking, installing an alternative Recovery, Rooting and installing a custom ROM for HTC ONE X+
Why should you do it manually?
At first glance, an all in one tool to do the work for us seems a good idea, but what happens if a step fails? Do you know how to use the right tools to recover? Does your computer have the basics prerequisites installed to allow you to recover your device? In performing this task manually all the basic tools will be installed and in the event that some bugs occurs, at least you will have the certainty of having all the tools in hand to fix it. It is an easy task to obtain if you follow this step-by-step tutorial rigorously. All you need is in this thread, no need to search to find that file or that app, all you need is 30-60 minutes of attentive reading and performing the described procedure. If something goes wrong, read again and simply perform the procedure another time. Remember, you decided to root and customize your phone, no one can be held responsible for your action. If something goes wrong we are here to help, but if you have the ability to read, you should be able to perform this without a swear.
Be aware that the HTC ONE X+ comes in two versions, one version called INTERNATIONAL (ENRC2B) that come WHITOUT the so-called LTE technology.
Then the North American version for AT&T and TELUS (EVITARE_UL) version that comes WITH so-called LTE technology.
LTE is an initialism of Long-Term Evolution. To determine which version your phone is you can simply download an application called CID Getter from the Google Play store available HERE Simply open the program once installed and navigate to the line named [ro.aa.project]:[your version model]
ENRC2B is INTERNATIONAL
EVITARE_UL is AT&T / TELUS
Now that you know which version is your phone lets start with the installation of your SDK tool folder. ADB is a versatile command line tool that lets you communicate with your Android device. This tool is MANDATORY and will serve you very often. Let's do this.
-- Screenshots for the visual ones --
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Unlocking your Bootloader --[/SIZE]
This step is mandatory since there is no other solution yet to unlock the bootloader on the ONE X+. !! PLEASE BE ADVISED TO BACKUP ALL YOUR DATA FROM YOUR PHONE'S USB MEDIA, THIS PROCEDURE WILL TOTALLY AND FULLY WIPE YOUR PHONE. ALSO, BE ADVISED THAT YOUR WARRANTY IS MOSTLY VOID !!
Before doing this you can visualize what is an unlocking procedure HERE. Or you can watch this video HERE
Ready?
To unlock your bootloader go to HTCDev create your account with a valid email address, then select on the right field : All Others Supported Devices and click on Begin Unlock Bootloader (If you followed this tutorial to the letter, your SDK tool/adb command should work flawlessly for this procedure.)
Follow the on screen instructions to get your Token ID.
To submit your Token ID you need to highlight everything between the two spades ♠< < < < <Identifier Token Start> > > > > ....token ID string.... < < < < <Identifier Token End > > > > >♠
Now simply right click and Copy/Paste in the correspondent field to submit.
You will received your unlocking code in your email account (almost instantly, check in your SPAM folder if it take more than 5 minutes) you registered with on HTCDev.
Complete the unlocking procedure and wait for your phone to reboot.
Congrats! The Unlocking process is successful!
____________________________________________
[SIZE="+1"]-- Recovery installation --[/SIZE]
Let's install your new recovery now. !! Be advised that installing CWM Recovery on this device is NOT RECOMMENDED, this recovery is untested, unreliable, unsupported and outdated. The ONLY recovery you should use on your HTC ONE X+ is TWRP Recovery !!
Download this TWRP Recovery for the International version (ENRC2B) : HERE MD5:0a708f4c27d69d2d1505ce7832d4b3be
Download this TWRP Recovery for the AT&T/TELUS version (EVITARE_UL) : HERE MD5:6e24a6686bc4840043a57cb61b63f22c
Once downloaded to simplify the operation rename your file like this : TWRPrecovery.img
Take this TWRPrecovery.img file and Copy/Paste it in the platform-tool of your SDK folder.
TIP : Since your are in the platform-tool folder you can create a batch file to open a command window right from your Desktop.
Do this directly into the platform-tools folder.
Right click on an empty space and select Create New text document
In the new text paste this : c:\windows\system32\cmd.exe
Save it with this name StartADB.bat (important to save it with .bat extension and overwrite the warning)
Now right click again on your new .bat file, and create a shortcut to your Desktop.
Now try to : adb devices your phone via your new Start ADB batch file directly form your Desktop shortcut with your phone plugged on your USB cable.
If you have a serial number as confimation you have done it right!
This a ONE TIME OPERATION TO DO, IT WILL WORK AS LONG AS THE SHORTCUT WILL BE ON YOUR DESKTOP.
Time to plug your phone on your USB cable if it is not already plugged.
Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
Confirmation of the serial.
At the prompt type >adb reboot-bootloader (Enter)
The phone will reboot in bootloader mode.
Make sure the FASTBOOT USB is highlighted.
At the prompt type >fastboot flash recovery TWRPrecovery.img (Enter)
If Success is achieved, type again at the prompt >fastboot erase cache (Enter)
You now have TWRP Recovery installed.
Unplug your USB cable and hit Power button one time.
Select Recovery with your Volume rocker.
Hit Power button one time.
Your phone should reboot in Recovery
Familiarize yourself with it.
Click on BACKUP and perform a full backup of your actual ROM.
Once done REBOOT System.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Time to install the root --[/SIZE]
This is fast to obtain, simply download this SuperSU.zip file and transfer this at the root of your USB media (SD card).
You can now click on your Start SDK batch file from your Desktop to start a command window while your phone is still plug on the USB cable.
Type at the prompt > adb devices (Enter)
Then again at the prompt (if serial confirmation is positive) >adb reboot-bootloader (Enter)
Phone will reboot in Bootloader
Unplugged the USB cable
Hit Power button once
Select Recovery in the menu with the Volume rocker
Hit Power once to reboot in Recovery
Select Install
In the Select Zip to Install menu located your SuperSU.zip file
Click on it and in the new menu simply Swipe to Confirm Flash
Reboot system
You are done rooting your phone.
____________________________________________
[SIZE="+1"]-- Custom ROM installation --[/SIZE]
So far all is good and the above instructions were all successful as we expected now you want that wonderful ROM from that thread, right? This procedure is very simple, but one rule applied here : ALWAYS BACKUP YOUR ACTUAL ROM BEFORE FLASHING ANYTHING! Do transfer it on your computer and keep this file in a safe place follow this path to locate the TWRP folder. At the root of your SD card locate TWRP -> Backups -> your_One X+_serial_number -> You should have one file stamped with date and time. This is your backup you can rename it. Copy/Paste it and put it in a safe place in your computer.
Now the fun part begin!
Once you have selected the ROM for your model version INTERNATIONAL OR AT&T/TELUS, simply download it.
Take also the correspondent boot.img that need to be flashed just before or just after (doesn't really matter) the ROM installation.
Transfer your ROM.zip at the root of your internal storage of the HTC ONE X+ via your USB cable.
While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
Leave your phone plugged to your USB cable
Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
Confirmation of the serial.
At the prompt type >adb reboot-bootloader (Enter)
The phone will reboot in bootloader mode.
Make sure the FASTBOOT USB is highlighted.
At the prompt type >fastboot flash boot insert_your_boot_image_name_here.img (Enter)
If Success is achieved, type again at the prompt >fastboot erase cache (Enter)
You now have a customized boot.img installed.
Unplug your USB cable and hit Power button one time.
Select Recovery with your Volume rocker.
Hit Power button one time.
Your phone should reboot in Recovery
(!! The following instruction are with TWRP Recovery installed !!)
Select Wipe menu, then select Factory reset (swipe), select System (swipe)
Go back to the Install menu and select it.
Locate your ROM.zip and select it.
Swipe to confirm.
Probably Aroma installer will start, simply follow the on-screen instructions and complete the installation.
!! Confirm the Rebooting option ONLY IF YOU FLASHED THE BOOT.IMG BEFORE ROM INSTALLATION !!
Otherwise select the Reboot Bootloader and perform the 4 to 8 steps
Reboot the phone.
-- Screenshots for the visual ones --
Your phone should Reboot with your new ROM, put your phone aside for ~10 minutes to let the new installation performing all it's task. Then you can customize your phone at your desire. Don't forget to reboot your phone when done.
Enjoy!
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Lucky Thirteen said:
you should be able to perform this without a swear.
Click to expand...
Click to collapse
I don't do anything without swearing, but thanks for a great, thorough tutorial. Mods - please sticky this!
sup, i have been using your guide to root and i have been getting trouble getting through the "adb device" part, no matter how many htc drivers i download i end up with the same error, it says devices but mine is never shown. but i guess its all good now as is followed it through the htcdev site...... but anyways would like to know how i can add these roms cause i am really confused about there kernels and stuff would be appreciated if you could explain how it works and whats a good rom to start with.
Hi decoy,
Can you specified at which portion of the tutorial you are stuck at?
i was getting stuck at lets try all this---> AndroidSDK\platform-tools> type this -> adb devices. over here when i type this my device does not show up i have tried updating my drivers several times still no success.
Are you with stock OS on your phone?
Have you tried another USB port? USB 3.0 ports are known to create issues. Also make sure your USB cable is not on a USB hub. If you have Enable USB debugging and you have followed the procedure to the letter, obviously there is a little thing missing.
Please try to describe your computer type and Windows version, where your USB cable is plugged in your computer, is Java installed correctly. Do describe at the most of your knowledge your situation. If it's really not working we can try to arrange a TeamViewer session to have a deeper look at it.
Yo its cool now cause I already rooted it, I guess the problem was the device connection on adb, as it was not being shown even though my computer recognized it, but when I went through the steps on Htcdev it worked cause I was able to unlock and install the recovery..... And I was using it on a usb 3 hub on windows 7. And yes at the moment I am running the stock Rom. I have An other question if you don't mind.... When you install the international recovey how does the back up work and how can you use it?
Sent from my HTC One X+ using xda app-developers app
You simply reboot in recovery and you will see menus, from there it is easy simply pick your choice and swipe to confirm.
Once you will be in Recovery you will see how simple it is, it is very intuitive.
New to android and new to rooting, thanks so much for this guide, unlocked, rooted and custom rom installed. I had no issues with this guide and it was a clean and new experience
Thanks! Successful completion with a few questions
First off, thank you very much for the thorough and easy to follow guide. This was my first attempt at installing a custom ROM on my phone and it went without a hitch.
I do have a few questions for you. First, I decided to install the Elagancia rom. It was a somewhat arbitrary decision, but is there any place that lists the pros and cons about various roms so it can be easier to decide which is right for my phone?
I was hoping to find a 4.2.2 based rom that was pretty much stock without sense, but I couldn't find one for the AT&T HTC One X+, is there one out there that I'm missing?
When I went through the install, it asked me various questions about install options. I didn't know what many of the options did, so I was wondering if there was a guide somewhere about the rom which describes the tweaks I could install. And I also wanted to know if there's a way to go back and change my options without wiping the phone clean and doing a fresh install again.
And again, thanks!
BlueWRXPride said:
First off, thank you very much for the thorough and easy to follow guide. This was my first attempt at installing a custom ROM on my phone and it went without a hitch.
Click to expand...
Click to collapse
Glad if it helped you! Please take the time to rate this thread, it will help to reference it. Take the time also to read this FAQ, you will probably learn a trick or two about your phone.
BlueWRXPride said:
I do have a few questions for you. First, I decided to install the Elagancia rom. It was a somewhat arbitrary decision, but is there any place that lists the pros and cons about various roms so it can be easier to decide which is right for my phone?
Click to expand...
Click to collapse
No, there's not a specific thread for that usage, but in each ROM thread there are Changelog and Screenshots that describing what you should expect from that specific ROM. It's not perfect but generally it's a good... appetizer!
BlueWRXPride said:
I was hoping to find a 4.2.2 based rom that was pretty much stock without sense, but I couldn't find one for the AT&T HTC One X+, is there one out there that I'm missing?
Click to expand...
Click to collapse
Unfortunately, not yet, at least, not that I know of.
BlueWRXPride said:
When I went through the install, it asked me various questions about install options. I didn't know what many of the options did, so I was wondering if there was a guide somewhere about the rom which describes the tweaks I could install. And I also wanted to know if there's a way to go back and change my options without wiping the phone clean and doing a fresh install again.
Click to expand...
Click to collapse
Again, in each Changelog and Add-on section of the intend ROM should have a brief description of tweaks and options available in Aroma Installer, but you can perform a search or ask for a description if you don't find an satisfying answer about a given option.
If you flash over the same ROM, all your settings, apps and data will be preserved, only the system will be updated, so simply flash over to change some options. The vital thing is to have a perfect backup done and saved just in case something goes bad with one flash or update.
BlueWRXPride said:
And again, thanks!
Click to expand...
Click to collapse
You are welcome!
I have a more general question about different roms. First, I'm assuming while it's easy to load a different ROM on the phone, there's no way to put it on there and try it out without wiping your phone clean. That makes the process of trying our different roms to find what you like pretty lengthy. Am I missing anything there?
Second, am I right to assume that most roms that are based of Sense 4+ will more or less look the same, and that the variations from rom to rom will mostly be behind the scenes?
BlueWRXPride said:
I have a more general question about different roms. First, I'm assuming while it's easy to load a different ROM on the phone, there's no way to put it on there and try it out without wiping your phone clean. That makes the process of trying our different roms to find what you like pretty lengthy. Am I missing anything there?
Click to expand...
Click to collapse
Well there is some way to migrate your apps & DATA from one ROM to another with applications like Titanium Backup or My Backup Pro. What I usually do is a full backup of my everyday ROM just before trying another ROM, than I can full wipe (this mean a factory reset and system format) and install the intend ROM I wanna try on my phone without setting everything at the first boot, I play with it and check for options, fluidity, speed, customization,etc. If I find the ROM worth installing my thing, I go on and start the processus to migrate my personal preferences, apps and DATA. This process can take two,three,four days to set the ROM like I want. I simply full backup the unready installed ROM and simply restore my everyday ROM until the other will be completely up and running. Then I suddenly have two perfect ROM to play with only by restoring them at my desire.
BlueWRXPride said:
Second, am I right to assume that most roms that are based of Sense 4+ will more or less look the same, and that the variations from rom to rom will mostly be behind the scenes?
Click to expand...
Click to collapse
Even if the base is the same, the developers do magnificent work to customize, personalize them very differently. Options and tweaks are very different from one dev to another. They all have their personal strength and usually the ROM reflects that talent.
Again, you have to try some at first, then you will see the personality of each ROM. You will learn also if you like a strongly customized ROM or maybe you will prefer a more Vanilla ROM (close as stock as possible) it is all yours to discover.
Lucky Thirteen said:
Well there is some way to migrate your apps & DATA from one ROM to another with applications like Titanium Backup or My Backup Pro. What I usually do is a full backup of my everyday ROM just before trying another ROM, than I can full wipe (this mean a factory reset and system format) and install the intend ROM I wanna try on my phone without setting everything at the first boot, I play with it and check for options, fluidity, speed, customization,etc. If I find the ROM worth installing my thing, I go on and start the processus to migrate my personal preferences, apps and DATA. This process can take two,three,four days to set the ROM like I want. I simply full backup the unready installed ROM and simply restore my everyday ROM until the other will be completely up and running. Then I suddenly have two perfect ROM to play with only by restoring them at my desire.
Click to expand...
Click to collapse
Thanks, that makes sense. Are you able to change between roms without hooking up to the computer and using adb? In your instructions you talk about how you have to flash the boot.ini file that is specifically for the rom you want so is there a way to take care of that without your computer?
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
golmar88 said:
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
Click to expand...
Click to collapse
Start SDK refers to the cmd file you created on your desktop in the -- Creating of script file for a fast access -- section
Mr. Thirteen, do you think you could offer me a little more help? Please refer to the post below.
http://forum.xda-developers.com/showthread.php?t=2226031
golmar88 said:
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
Click to expand...
Click to collapse
BlueWRXPride said:
Start SDK refers to the cmd file you created on your desktop in the -- Creating of script file for a fast access -- section
Click to expand...
Click to collapse
Probably you just missed a section like BlueWRXPride told you.
trouble with file Start SDK.bat
Lucky Thirteen said:
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Click to expand...
Click to collapse
Hey lucky thriteen ive been doing everything step by step but im having trouble making the note and copying and pasting c:\windows\system32\cmd.exe once i create the shortcut and open it its nothing like how you show it in the example any idea what it could be?? thanks
---------- Post added at 04:47 PM ---------- Previous post was at 04:41 PM ----------
Lucky Thirteen said:
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Click to expand...
Click to collapse
hey lucky thirteen ive been having trouble with the step where you have to create a note in the platform-tools file once i save the note and create the shortcut its not like the example that you post it only shows c:\windows\system32\cmd.exe any idea on what i did wrong?? thanks
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
jamesh1979 said:
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
Click to expand...
Click to collapse
Ok, if I understand you correctly, you wiped internal storage of your sdcard, so no backups to restore for safestrap.
But when wiping happened, you were on activated extra rom slot? So now safestrap cant boot there, because with internal storage you deleted image files for rom slots...
If you can boot into safestrap, can you switch to stock rom? And boot into it? If yes, and Fireos start normally, then nothing is lost, reinstall safestrap, you should have adb access, and do whatever you want to do next...
Did you disabled OTA updates on stock rom? If not, turn off wifi as fast as you can, when you boot into Fireos, so it cant update to nonrootable FW.
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
jamesh1979 said:
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
Click to expand...
Click to collapse
Well, I installed safestrap on my working kindle, so I can check what else was deleted in the wiping, unfortunately there was a little config file where safestrap stored which slot was last active. This file no longer exist, so safestrap dont know from what to switch where.
The only thing we can try (AFAIK) requires working adb connection and it must be working from safestrap, so you can use adb sideload feature - so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve this, we can try with sideloading, if not I am sorry, dont know what else to do - actually there is one thing you can try - with working adb access you can recreate directory structure needed for safestrap config file and push it there (I will attach it later), then restart and see if it boot to stock rom
edit:
I was able connect through adb from windows to running safestrap, so it is possible (at least kindle is recognized in "adb devices")
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
jamesh1979 said:
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
Click to expand...
Click to collapse
Great!
Now download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device, especially this post (shows similar symptoms as your current problem)
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is "only" TWRP based, I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
C. You can consider also recreating deleted folder containing slot config file for Safestrap (active_slot file attached below (file is in archive, you need extract it)) through adb shell:
0. connect kindle to pc/laptop
1. enter Safestrap
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX recovery
3. type adb shell
4. type mkdir -p data/media/safestrap/rom-slot1
5. type exit
6. type adb push active_slot data/media/safestrap
7. reboot/reboot into recovery and see if you can switch/boot to stock rom (which is still there, otherwise safestrap will not be accessible)
C variant is a really long-shot, but relatively harmless (or maybe not who knows, I am not expert)
OK fingers crossed, I hope something will work, but things can go wrong, unfortunatelly from my side all above is just a theory, adb commands should works, I tested them all (except sideload), works on my side...
Thanx a lot guys I got I t back in action thanx for all the help
jamesh1979 said:
Thanx a lot guys I got I t back in action thanx for all the help
Click to expand...
Click to collapse
Care to share which method you use to recover your kindle?
anyone here? lol