[No-Brick Method]New All-in-One D2G recovery & Root CD for .629 update(EzSbf method)
I have put together a modified version of 1KDS EzSbf CD's, combining the necessary tools to unbrick and root devices that have taken the .629 update.
I have tested it several times on my own phone, and it has worked well.
As with everything, I have done my best on this, but can provide no guarantees that it will work for you. It worked well for me, and others have used all of these tools, but like everything else here, use this at your own risk.
The CD is a combination of the tools from the following sites.
EzSbf from http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html
phifc's preinstall method from http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
Suggested reading before starting:
http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
Instructions: (all instructions are on the CD prompts)
This is ONLY for the Droid 2 Global, and more specifically only for the Droid 2 Global that has already had the 4.5.629 OTA update. If your phone has not had the OTA update to .629, I recommend you do not use this.
If using a CD, burn ISO to disc, and boot from that. It will come to a prompt with instructions.
If using USB stick.
Use Unetbootin (http://unetbootin.sourceforge.net/) to install ISO to USB drive, and when booting choose the Slitaz option.
If you need to flash the SBF, you will need to have the phone in bootloader mode, if you need to root, you will need to start the process with the phone turned on and usb debugging enabled. You will then need to put the phone in bootloader mode when prompted.
Credits:
I did not develop any of the software used, I just compiled it into one location.
Credit should go to:
1KDS for developing the EzSbf method, and for helping me as I was putting the CD together
phifc and the method he posted at
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
djrbliss, and the others who developed the symlink method
Skrilax_CZ, and his Motorola Android Firmware (De)packer
Here is a link to download the ISO if you would like to try it. I don't expect anyone to have troubles with it, but as with everything, I have done my best on this, but can provide no guarantees that it will work for you. It worked well for me, and others have used all of these tools, but like everything else here, use this at your own risk.
Updated CD:
Thanks to phifc and the method he posted at
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
we have an improved method available to root the D2G, and no longer need to brick our phones (presuming all goes well) in order to root them. Since there is now a direct rooting method of .629 available, I put it together with an EzSbf style CD of the full .629 SBF.
One item of note with this CD, it does require at least 1GB of RAM in order to work properly. Also, if you only have 1GB of memory, and you need to both SBF and root your phone, it will be necessary to reboot the computer after flashing the .629 SBF. If you are unsure of the amount of RAM that you have, go ahead and reboot to be on the safe side.
Also, I noticed that I neglected to put instructions for putting your phone in bootloader in the SBF Step. To put your D2G in bootloader mode, power down and power on while either holding both volume buttons, or the up arrow on the keyboard.
SBF and Root CD
The CD is available at
https://rapidshare.com/files/2650843793/D2G_4.5.629_SBF-and-RootCD.iso
and the MD5 is
579d7d5095fc2560205033456db150a2
Root Only Multi-Device CD
There is also a root only CD available, that covers multiple devices (Droid 2, Droid 2 Global, Droid X, and Droid X2).
It is a little over 50 Meg in size, so if all you want to do is root your phone, it might be a handier option.
the link for it is
http://www.mediafire.com/?mim304k214kl41h
and the md5 is
7baee9c34f6ef7ad0b4fa219ae387c68
Additional Mirror:
Rapidshare has had some trouble recently, but thanks to themib/sd_shadow for putting up a mirror that has most of these CD images as well. They can be found at
https://docs.google.com/document/d/1-Oj1a1wNZKhZMPUqU_6KzzYzQJ2RKzvvumTx-41f3h4/edit#
If anyone finds a CD helpful, and would like to upload it to a mirror, they are welcome to. If they give me the link to a mirror, I will be glad to add it to this post.
Older items still working but obsolete
Hopefully these have served their purpose, but should now be superseded.
I uploaded it to Rapidshare at
https://rapidshare.com/files/1957071604/D2G_629Recovery-and-Root_CD-With_OTA-Update.iso
and the md5 checksum for the iso is
45dff90da46bd30c33f005c853e058d1 (Updated CD including the OTA Update
Here is also a clean Nandroid backup of rooted .629.
This would be useful for the band unlockers (those want to use this phone on AT&T or T-Mobile), or for those that would prefer to restore a backup instead of taking the OTA update. Once you have rooted the .608, you bootstrap recovery, and restore this nandroid backup.
You will need to extract it, and place the folder in the sdcard\clockworkmod\backup folder. Hope this is helpful for someone.
The link to download the file is
https://rapidshare.com/files/782850895/2012-06-10_Rooted_629-Nandroid.7z
and the MD5 checksum is
c43101a5b01d7c69887a0668be24e5c9
more details
updated many times see change log
created by phifc modified by bhigham
2 options mirror links posted Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
Multi-Device Root (54mb)
D2G_4.5.629_SBF-and-RootCD.iso (219MB)
How this works
Originally Posted by phifc
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
what is ezSBF?
original [TOOL] ezSBF (not for 2.3.4)
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP) or (Load to a USB flash drive)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"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"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
________________________________________________
You will now be in the script and ready to flash.
Click to expand...
Click to collapse
select D2G for multi device root cd or /select root for the SBF-and-Root CD
don't use numbers on right side of you keyboard, just use the ones above qwerty
turn phone on, connect to pc with usb cable
on phone check usb debugging (settings/apps/development)
on phone select charge only usb mode
on pc press continue
program will use adb to push
Code:
data/local.prop /data/preinstall_md5/magic.md5
program will prompt you to
manually reboot phone to bootloader
program will flash repacked sbf (less than 50mb)
program will reboot twice, very important (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
adb pushes su,superuser, and busybox
program will reboot to recovery,
manually press both volume buttons when you see !, triangle, & android andy
manually select wipe cache
manually select reboot
rooted
error info
when running program you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
by bhigham -One item of note with this CD, it does require at least 1GB of RAM in order to work properly. Also, if you only have 1GB of memory, and you need to both SBF and root your phone, it will be necessary to reboot the computer after flashing the .629 SBF. If you are unsure of the amount of RAM that you have, go ahead and reboot to be on the safe side.
Also, I noticed that I neglected to put instructions for putting your phone in bootloader in the SBF Step. To put your D2G in bootloader mode, power down and power on while either holding both volume buttons, or the up arrow on the keyboard.
Click to expand...
Click to collapse
if you plan on creating nandroid backups or flashing roms read
[HOW TO] Install/Use Droid 2 Bootstrap
Band unlock Droid 2 Global with 629 instructions
original D2 thread New root method for stock 2.3.4 (621/622) found (Droid2, R2D2) - Droid 2 / R2D2 / Milestone 2 / Droid 2 Global - RootzWiki
30 Aug 2012 added links
02 Oct 2012 added mac info
09 Dec 2012 major rewrite
Click to expand...
Click to collapse
If anyone has been able to try this out, please let me know how it goes, so I can update the post. Once others have verified it works well for them, I will post more complete and detailed instructions for those who don't have experience.
I also have a clean .629 Nandroid backup available for Band Unlockers, who would like to cut down on the number of steps necessary to get their phones on AT&T or T-Mobile, and will post detailed instructions for that as well.
i try this but wifi can't connect ..just at obtaining ip adress only...
please help...
Sent from my DROID2 GLOBAL using xda premium
WiFi won't work until you take the OTA update.
Make sure to protect root using Voodoo OTA rootkeeper first, rootkeeper should already be installed and in your list of applications.
CONFIRMED, I have .629 ROOTED, and working WIFI, GREAT job , many thanks.
but i feel the the WIFI is become weak in catching the signal, in addition to the phone signal now become -2 all the day,
and how can I remove the Verzion app, as i use the phone outside USA
---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------
sd_shadow said:
nice work, hope it works well for other D2Gs
Click to expand...
Click to collapse
Did u find any method to enable the GSM on MIUI or CM7 ???
Glad it worked for you, as far as removing apps, I haven't really done any of that, I have used Titanium backup to freeze the ones I don't want running.
Does putting the old .608 on (step 1) wipe the phone? My only root experience was a one click HTC. The only reason I want to root the d2g is to do a backup of app data to move to a droid4, because after that I will be putting the d2 in a drawer.
Thanks for the info.
flashing a SBF, doesn't wipe data, just flashes the system
but normally wiping data in android recovery, is recommended to prevent bootloops
bhigham said:
WiFi won't work until you take the OTA update.
Make sure to protect root using Voodoo OTA rootkeeper first, rootkeeper should already be installed and in your list of applications.
Click to expand...
Click to collapse
i already install dude..but nothing happen..
you may have to wipe data again
Thanks OP! The CD worked great, and Murphy must have been on vacation today because I was able to get through it without clearing data, which meant I could back up the phone with TBP. :good:
Okay So I Tryed Once Already & The Disk Leads Me To This:
Disk Err 01, AX = 4200, Drive A0
Im Running A W7 64Bit Laptop, Any Help?
did you verify the md5 checksum before burning iso to cd?
Sent from my DROID2 using xda app-developers app
sd_shadow said:
did you verify the md5 checksum before burning iso to cd?
Sent from my DROID2 using xda app-developers app
Click to expand...
Click to collapse
Please Explain This, I Don't Know What Your Talking About.
How long do you have to hold down X key + power button to see recovery triangle screen?
When I do that, I immediately see the bootloader Err:A5,70,70,00,1F screen?
I've held it down for 30sec and doesn't change?
UPDATE:
Even though I didn't get the recovery triangle, I did the .629 repack update anyway on the bootloader error screen and it worked!
Thanks for this awesome post!
fyi: to boot to android recovery, start with phone power down
then x and power
it's in the wiki
Sent from my MB870 using xda premium
wiping data is only recommended, not always required, as it prevents bootlooping
Sent from my MB870 using xda premium
Got It.
Thanks So Much! ;3
8o8OhBby said:
Got It.
Thanks So Much! ;3
Click to expand...
Click to collapse
sorry that i didn't get back to you about md5
did you figure it out? it's in my links page
Related
THIS IS ONLY FOR NON-NAND, TheBiles should put one out for NAND rooting soon.
Here's a guide for people who either don't have a PC or don't want to use one.
You will need the following files:
PC36IMG.zip
Update.zip (listed below)
A rom image of your choice
put all these files on your SD card root then power off your phone.
THIS CAN WIPE YOUR DEVICE, IF YOU NEED TO BACKUP DO STEPS 1-13 HERE
1. Hold volume down and power, keep holding volume down till the white screen appears
{
"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"
}
2. Wait for it to search for PC36IMG.zip on the sd card then hit yes when it asks if you want to update
http://www.flickr.com/photos/mrono/4694475803/
3. Wait for it to finish(it takes awhile) then press yes to reboot
http://www.flickr.com/photos/mrono/4694475829/
YOU NOW HAVE ROOT
now we will flash a custom rom
4. When the white "Evo 4g" screen appears, pull the battery
http://www.flickr.com/photos/mrono/4695109532/
5. Hold volume down and power, keep holding volume down till the white screen appears
http://www.flickr.com/photos/mrono/4695109576/
6. Press no to updating, then no to rebooting
http://www.flickr.com/photos/mrono/4694475803/
7. Select recovery and press power
http://www.flickr.com/photos/mrono/4695109576/
8. Wait for the red triangle
http://www.flickr.com/photos/mrono/4694475545/
9. Hold vol up and press power, wait for the menu, then select apply sdcard:update.zip and press power again
http://www.flickr.com/photos/mrono/4695109674/
10. Select install zip from sd card
http://www.flickr.com/photos/mrono/4695109714/
11. Select choose zip from sd card
http://www.flickr.com/photos/mrono/4695109744/
12. Select your rom of choice and hit power
http://www.flickr.com/photos/mrono/4695109770/
13. Wait for it to install
http://www.flickr.com/photos/mrono/4695109790/
14. Select -go back-
http://www.flickr.com/photos/mrono/4694475723/
15. Select reboot system now
http://www.flickr.com/photos/mrono/4694475763/
16. Enjoy your custom rom and rooted device!
http://www.flickr.com/photos/mrono/4695109864/
All the credit goes to:
toast: without him we wouldn't have root http://forum.xda-developers.com/showthread.php?t=690762
Koush: for the fake-flash recovery http://forum.xda-developers.com/showthread.php?t=699043
I'm glad you wrote this up. I performed root the exact same way. I still don't know anything about adb, sdk, shell, or whatever. But this way is truly rooting for dummies!, and totally without a PC. I also used rom manager to download my first rom that i flashed. But then downloaded a new one. I plan on using dcupdater for new updates.
This should be a sticky. Rooting for dummies! No PC required.
Sticky this for all of us root wanting fools that have no sense of adb.
This is sooo what I just posted, only you have photos of the recovery screen.
TheBiles said:
This is sooo what I just posted, only you have photos of the recovery screen.
Click to expand...
Click to collapse
Lol we should just combine them, feel free to combine mine into yours
Re: Rooting without ADB, a photographic guide
mrono said:
Lol we should just combine them, feel free to combine mine into yours
Click to expand...
Click to collapse
That would be great, and it would save me a lot of time. I will do that first thing tomorrow. Thanks!
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Thanks for this. Helped me get past a step I got hung on for hours tearing my hair out.
Aparently my web server is down >.> that's why the images arn't appearing.
Re: Rooting without ADB, a photographic guide
If you post them in a .zip I will upload them to mine with the rest of my pics.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
TheBiles said:
If you post them in a .zip I will upload them to mine with the rest of my pics.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Click to expand...
Click to collapse
Sure, here you go.
Woot, will be doing this soon.
I hope a 100% Senseless rom comes out.
Thanks for this method with all the images. But, I have been trying all night to gain root. First using Toast's version and adb, and now with your method on my sdcard. Using either method, I never get to a screen where I can choose to update, in step 2. I have the searching for PC36IMG.zip, with the blue progress bar, but it dumps me into this screen:
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I've downloaded the file at least twice, but I get the same result. I also flashed the stock RUU between trying Toast's version with adb and yours from the sdcard.
Do you have any idea where I went wrong? Also, is your update.zip Clockwork? (Just curious.) I'm not a complete beginner at this, as I have a Hero and was able to flash custom ROMs to it...
Thanks for any help you can give.
smarcin said:
Thanks for this method with all the images. But, I have been trying all night to gain root. First using Toast's version and adb, and now with your method on my sdcard. Using either method, I never get to a screen where I can choose to update, in step 2. I have the searching for PC36IMG.zip, with the blue progress bar, but it dumps me into this screen:
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I've downloaded the file at least twice, but I get the same result. I also flashed the stock RUU between trying Toast's version with adb and yours from the sdcard.
Do you have any idea where I went wrong? Also, is your update.zip Clockwork? (Just curious.) I'm not a complete beginner at this, as I have a Hero and was able to flash custom ROMs to it...
Thanks for any help you can give.
Click to expand...
Click to collapse
This is happening to me too.. Though I think it's because I'm already rooted? I did go through Toast's method and looks like I'm rooted, wish there was a way to tell. Also If I load a ROM then check ROM manager to see which rom I'm currently running, nothing is there -just blank.
Settings, About phone, Software information will tell you if it is rooted. Look at build number, should be Fresh Evo 0.2 by flipz or whatever ROM you used.
Mine says Fresh Evo 0.2 but during the root process it skips [8] TP and bypasses [9] TP, wondering if something is wrong with the root process? Also my sd card seems to have lost all my backup data and when I connect to pc it says my card has issues. Do I have a problem?
Did it, worked 100% easy.
Thanks man.
Are you supposed to be able to open (explore) the PC36IMG.ZIP file through Windows? I have downloaded it 12 times from 4 different places and the message says the file is invalid. I haven't put it on my SD yet, this is just on my PC.
Edit: Well, I tried doing the update to root with the downloaded PC36IMG.ZIP file and all I get is a non-rooted wiped clean EVO after it does the update.
Can someone please download load PC36IMG file "now" (not try a previous version) and see if it corrupt and also see if you can open already downloaded one through windows as a zip file.
Thanks....
MisterEdF said:
Are you supposed to be able to open (explore) the PC36IMG.ZIP file through Windows? I have downloaded it 12 times from 4 different places and the message says the file is invalid. I haven't put it on my SD yet, this is just on my PC.
Edit: Well, I tried doing the update to root with the downloaded PC36IMG.ZIP file and all I get is a non-rooted wiped clean EVO after it does the update.
Can someone please download load PC36IMG file "now" (not try a previous version) and see if it corrupt and also see if you can open already downloaded one through windows as a zip file.
Thanks....
Click to expand...
Click to collapse
I think that's what I have too: "a non-rooted wiped clean Evo." I never had the prompt to say yes to update or yes to reboot. I'm not a total n00b at this. I was able to successfully root and put Fresh's ROM on my Hero. I thought maybe it was adb drivers, but I can use my Evo in disk mode, and run HTC Sync. (I have no use for HTC Sync.)
I'd love to try d/ling the file, but my dsl is down. I've spent the last 2 hours troubleshooting it and arguing with Qwest. They've finally agreed it might be their problem and are coming out to fix it. I NEED root so I can us WiFi tether!
MisterEdF said:
Are you supposed to be able to open (explore) the PC36IMG.ZIP file through Windows? I have downloaded it 12 times from 4 different places and the message says the file is invalid. I haven't put it on my SD yet, this is just on my PC.
Edit: Well, I tried doing the update to root with the downloaded PC36IMG.ZIP file and all I get is a non-rooted wiped clean EVO after it does the update.
Can someone please download load PC36IMG file "now" (not try a previous version) and see if it corrupt and also see if you can open already downloaded one through windows as a zip file.
Thanks....
Click to expand...
Click to collapse
I just tried to open my pc36img.zip file off my sd card, the one that I used to root and it says that it's inva'id. I think it's because it's not really a zip file. The one your downloading is fine.
smarcin said:
I think that's what I have too: "a non-rooted wiped clean Evo." I never had the prompt to say yes to update or yes to reboot. I'm not a total n00b at this. I was able to successfully root and put Fresh's ROM on my Hero. I thought maybe it was adb drivers, but I can use my Evo in disk mode, and run HTC Sync. (I have no use for HTC Sync.)
I'd love to try d/ling the file, but my dsl is down. I've spent the last 2 hours troubleshooting it and arguing with Qwest. They've finally agreed it might be their problem and are coming out to fix it. I NEED root so I can us WiFi tether!
Click to expand...
Click to collapse
Why don't you just download the unrevoked root till you get your DAL back online.
http://m.unrevoked.com
Hey guys, I want to flash to another Rom with this method. Do I just do all the steps all over again?
Zardos66 said:
Hey guys, I want to flash to another Rom with this method. Do I just do all the steps all over again?
Click to expand...
Click to collapse
no, just get into recovery, you don't have to flash the .img file
First things first...
Credits:
Mast3rpyr0 - Original creator of a simple one click root. Most the code used here is based on his work with some tweeks. [ Link ]
webs05 - For the outstanding help he has provided to those who were having issues using Simple Root!!! Thanks!
toastcfh - For root and nand unlock. [ Link ]
Koush - Recovery image [ Link ]
maejrep - For helping with the code to remove sendkeys!! Thanks alot!!
If I forgot anyone that I should have mention, let me know....
{
"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"
}
Automatic updates and create update patches with wyBuild.
After hours of trying to figure out a way to make Mast3rpyr0's batch files work correctly, I noticed it had problems sending certain commands. So I decided to use some of his batch file codes, and create a VB.NET application along with batch files. I have unrooted and rooted my personal phone multiple times trying to get this to work. I tested the app 3times!! Each time Unrooting my phone! All three times its has been successful!
What exactly does this do?
Exactly what it say, Root your EVO in 3 Steps.
How do you use it?
Make sure your phone is on USB Debug mode. (MENU > Settings > Applications > Developement > USB debugging = Checked ) Click the buttons starting from Step 1.
Why the large file size?
This includes all the .img and .zip files that are needed to root. (2 PC36IMG.zip @ ~ 170MB = 340mb) and a couple of other smaller files. I decided to add them to make things more simple and avoid having to explain where to get these files.
Youtube Example
sorry for all the video splits...not my fault, blame youtube.
Video quality might be bad, give them a few to process 720p version
Part 1-1 - http://www.youtube.com/watch?v=GAqTEAWxh7U
Part 1-2 - http://www.youtube.com/watch?v=578jDEJ6M_c
Part 2-1 - http://www.youtube.com/watch?v=I-FbYqPOrpg
Part 2-2+3 - http://www.youtube.com/watch?v=qk7lBDpSp-A
AndroidPolice.com Review + Tips
Download:
Megaupload - had to put this up, account suspended due to the amount of downloads =( they want my to go dedicated smh...
Official Page | Full (Download this if you never used this program before)
If you have downloaded this program before, please read this
Note: Its recommended to flash a custom ROM. Reason I say this is because for whatever reason, the eng-image doesnt allow proper SU permission!!
Requires: Dot Net Framework 4 and HTC SYNC
I would try it if I didn't fully root yesterday. But props to you guys for putting that together. Seems like a one step jailbreak. Very nice.
WOW! Great work. This will unlock NAND too? If so you might want to update your thread title....
jiqqaman said:
First things first...
FOLLOW THE DIRECTIONS!! IF IT SAYS DONT MOVE YOUR MOUSE, DONT CLICK ANYTHING, DONT TOUCH YOUR KEYBOARD... THEN DONT!!!!
The reason for this is because for some reason a batch file cant send the command
Code:
adb shell cat sdcard/flash_image > /data/flash_image
The only way I found to get around that was using Sendkeys. I know, send keys is lame, and poor programming, but its the only way that I could get this to work.
Basically, Sendkeys sends keystokes to a targeted window, as if you were typing. You might see your keyboard NumLock, Caps light blink while this is being used, which is perfectly normal. (Enjoy the light show)
Click to expand...
Click to collapse
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
this is amazing. too bad noobs like myself could not wait to root and unlock nand. but the process was well worth it. great job, i hope this save someone a headache
Re: [Program] SimpleRoot .1 ---- 3 Click Root!!
smw6180 said:
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
Click to expand...
Click to collapse
Thanks, I'll see how that works later on, and if it works ill just upload a zip file with the updated code. Don't like the whole sendkeys thing,...I'd like to figure out on making it work without batch files... but I no pro code lol
Sent from my HTC EVO using Tapatalk
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
It wont hurt to re-root just run the whole thing. make sure you backup of course
thanks OP great work I'm sure it will get even better and easier once you get rid of key presses
STICKY!!!!
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Damn after I followed the 50 step-by-step and wish I had seen this earlier nice work might try this on my older bros in a few days
Sent from my Sprint HTC EVO 4G. via tapatalk
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
Yes, but you must run on the pushfiles.bat file before you goto step 2.
CYBERxNUKE said:
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Click to expand...
Click to collapse
http://www.megaupload.com/?d=N6GV5NNP - no .img or .zip files
make sure you have the first PC36IMG.zip from the first root tutorial and the 2nd PC36IMG.zip from the nand unlock rename it eng-PC36IMG.zip or else you'll break it =(
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
OP theres an updates restore image much better options from armon .02 works for people who have bad sectors ALLOT of us have
but 01 is for those who dont try that first
http://forum.xda-developers.com/showthread.php?t=705026
ken987 said:
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
Click to expand...
Click to collapse
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
great job on making this easy guys.... To bad I couldnt wait longer than a week to root.
jiqqaman said:
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
Click to expand...
Click to collapse
Thanks for the quick reply. No, I am a new EVO owner and this is my first android phone. I was an iPhone user but I have come over to the Android side. No regrets. I have basically a new EVO with the OTA update installed. So my goal would be to run your one click method and then learn how to load roms. I also read that people have some kind of rom loader on their phone that sounded pretty easy so I need to do more searching on the forums here so I can learn.
Ken
This would have saved me 3 hours....
Thanks dude though this seems awesome.
Videos are titled "Hero 4g" btw.
Part 1 worked for me but part 2 doesn't. When I click yes on part 2 I get a screen that says "Unhandled exceptin has occured" and it gives me a option to continue or quit and I click continue and it closes out.
Does this method work if I already have the .6 stock rom on my device?
Obsolete: Go HERE: Unrevoked's reflash Root/Recovery flash tool
attn1 said:
This will root the device and allow you to install things like wireless tether.
Edit: I can connect to wireless tether, but it's not routing to anything and takes forever to get an IP address. Once I get an ip address, I can't even ping the gateway. I suspect further AT&T foolery. I am working on it.
Custom recovery is a bear to get to. You can however, get to custom recovery, and we can flash custom roms.
For the most part, I used the root method and files from the MT3G root procedure. However, I could not get the adb to read my in recovery until I used my gold card. Many failed attempts before, and it pretty consistantly worked afterword. I suspect the difference was the SD card itself, and not that it was a gold card, because it makes no sense that a gold card should make a difference. Both cards were 2 gb Sandisk cards, but the one I used was from a Hero, which was what I used to make my goldcard to root that.
Folks, the MT3G method works. This isn't mine, I was just the first to make it go on the Aria.
Here's eugene's "How to Root the Slide thread"
Eugene, Koush, Modaco, ChiefzReloaded, brokensanity, the EVO Unrevoked team and many others, on behalf of an awful lof frustrated AT&T Android fans, thank you.
The Unrevoked team has more info here if you get stuck.
Update:
Instead of slideroot.zip and superuser.apk, you can just flash my rom. (See next post in this thread).
That includes root, busybox, superuser.apk and strips AT&T applications & brings the ROM much closer to a generic HTC sense ROM.
Check out this thread: http://forum.xda-developers.com/showpost.php?p=6909467&postcount=1
Once you have root (either by pushing slideroot and installing superuser.apk or skipping those and installing my rooted ROM) do yourself a favor and check out this thread: Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
Once rooted, you don't have to do the adb chase anymore; you can now flash custom recovery with the tool in that thread. It works!
{
"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"
}
Click to expand...
Click to collapse
Installing a custom ROM and loading Clockwork Recovery on an unrooted HTC ARIA.
Installing a custom ROM on Aria/loading Clockwork Recovery on an UNROOTED HTC Aria.
(like mine, found here: ROM Liberated_Aria)
This method is borrowed heavily from eugene's MT3GS root method, using Unrevoked exploit.
OS X/Linux Users: remember to preface abd commands with ./ (./adb)
We now have the ability to flash custom recovery on the phone! (Thanks to the Unrevoked Team)
PREREQUISITE #1: You must have the android sdk installed on a Windows machine and know how to use adb. Alternatively, you can use a *nix/OS X box if you don't mind verifying devices without the loop to watch.
PREREQUISITE #2: Download Clockwork_Aria_MT3GS.zip
Process:
Format the SD card supplied with the phone like this: http://forum.xda-developers.com/showpost.php?p=7029045&postcount=283 (Thanks Yoshiofthewire) in a card reader if at all possible.
Copy your new ROM zipfile to the root directory of the SDCARD. DO NOT name it update.zip. DO NOT unzip it. You must flash the zipfile later.
Copy the contents of Clockwork_Aria_MT3GS.zip to the tools directory of your SDK, along with your ROM zipfile of choice.
Power up the phone, holding down the VOL-DOWN button.
Wait about 30 seconds, until some diagnostic checking is done.
Press volume down to highlight recovery, but to do not push power to execute just yet.
Open a command prompt and navigate to your SDK tools directory.
Start the loop.bat file and let it run. (Optional if you don't mind running adb devices until the decide to show up).
Get ready to connect the phone to the computer with the USB cable, but don't connect one end until you read the next step.
This part is a PIA and it's critical, and it's inconsistent and therefore may take quite a few tries to get it right: Pushing the power button first and then approximately one second later plug in the USB cord. (Think ONE THOUSAND ONE-PLUG)
When the triangle/exclaimation over phone graphic appears, hold volume up and press power. This will bring you to stock recovery.
If this works, your loop running the adb devices command will list the device. If not, start from the beginning from power up. This can take a lot of tries, be patient and don't give up. Not all SD cards will work reliably.
Once devices are listed in the loop, hit CTRL-C to terminate the loop if you've started one. Hurdle one complete.
In recovery, use volume down to select Apply sdcard:update.zip and push the power button to execute (This will fail, but it's enabled write access for me.)
adb push ota.zip /sdcard/update.zip and press the enter on keyboard to execute. (No - that's not a typo)
If that pushes without error, then enter adb push update.zip /sdcard/update.zip but do NOT press enter.
In recovery, again scroll down with power down to select sdcard:update.zip but do not execute yet.
Press the power button and then watch phone to say "verifying" and then press enter IMMEDIATELY on the keyboard. If timed right, Clockwork recovery should load. If not, start back at step push ota.zip /sdcard/update.zip and repeat from there until clockwork loads.
Optional: From Clockwork Recovery, do a Nandroid backup.
From Clockwork Recovery, select install zip from sdcard, and execute, then choose zip from sdcard and execute, and then you can scroll down to your pre-rooted rom of choice and execute that to flash it. In Clockwork you can scroll with trackpad or volume buttons, and you can execute with either the power button or a trackpad button push.
If you get stuck trying to get Clockwork to load:
Try a different sdcard and start again from the first step.
Check out Modest Android's post here: http://forum.xda-developers.com/showpost.php?p=7006760&postcount=2
The Unrevoked Team has more info here: http://www.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery
On a rooted Aria, do yourself a huge favor and install Clockwork Recovery. See this thread: Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
Also, enable installation of non-Market (untrusted) apps (sideloading):
COMMON:
Start the phone normally.
Enable USB debugging (settings > applications > development > USB Debugging)
Leave the phone running - do not reboot to Clockwork.
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X:
echo "update secure set value = 1 where name = 'install_non_market_apps';"|./sqlite3 settings.db
WINDOWS:
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON:
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Reboot phone and sideloading works. (thanks to fluffyarmada)
When I get a chance, I'll figure out how to do a proper menu toggle.
ROM Downloads:
liberated_aria_b003_signed.zip
(HTC Boot theme, AT&T apps removed, Google Search default web page)
MD5: 2d7a3aeb8ebe2c33247897be7ef22740
aria_shipped_rooted_signed.zip
(Stock with ROOT, AT&T Boot theme & Apps)
MD5: af56f22d24e4dcc4b205cf9bb3bc9ba1
Aria Issues:
Even with root, wifi tether does not work.
Thanks attn1 and whoever else worked on the Aria. Awesome job.
very impressive!
Remember I told you I had a feeling it would work!
Oh and whenever went into recovery during the root process after running the loop did you actually select recovery from the menu or did you use the other method we talked about in that other thread?
What is the procedure for removing the bloatware? As I said in the other thread, this will be my first endeavor into the Android market and I hope this is not a stupid question.
_Opiate_ said:
very impressive!
Remember I told you I had a feeling it would work!
Click to expand...
Click to collapse
You did - and you were right!
attn1 said:
You did - and you were right!
Click to expand...
Click to collapse
Im just glad it worked! I can't wait to give it a go myself.
does anyone have a stock rom for the HTC aria? Just wondering if ever i want to go back to the original ROM.
if you give this a try, please let us know how it went. that would be a big bonus.
thanks!
icedude said:
does anyone have a stock rom for the HTC aria? Just wondering if ever i want to go back to the original ROM.
Click to expand...
Click to collapse
You are still on the stock ROM....rooting doesn't flash a different ROM
I am trying this but i can't get past the start of running loop...i am following the guide linked to, can anyone give me a bit more explanation?
ko0ky said:
if you give this a try, please let us know how it went. that would be a big bonus.
thanks!
Click to expand...
Click to collapse
Its already confirmed to work but I'm going to give this a go as soon as I get home and ill update. I'm headed there now.
_Opiate_ said:
Its already confirmed to work but I'm going to give this a go as soon as I get home and ill update. I'm headed there now.
Click to expand...
Click to collapse
Thanks Opiate, but so far, just one person has confirmed. I only asked to get general census on how well its going for everyone.
I trust the op too.. but still, for some of us... this will be our first 'rooting' a android. I love the phone way too much to screw something up.
I followed the instructions on the 'Root the Slide' page... But I must have done something wrong... because I still can't su. And now I can't get adb to detect the phone in recovery mode. Hmm...
Everything seemed to work though... this is strange.
And, yes, USB Debugging is enabled. I'm trying to re-do the whole process, but I can't get the phone to show up on adb.
icedude said:
does anyone have a stock rom for the HTC aria? Just wondering if ever i want to go back to the original ROM.
Click to expand...
Click to collapse
Sure. Once your are in clockwork, you can do a Nandroid backup. You can always restore that.
How did you get this to work?
Even with a fresh gold card I am not seeing an Offline Device
ko0ky said:
Thanks Opiate, but so far, just one person has confirmed. I only asked to get general census on how well its going for everyone.
I trust the op too.. but still, for some of us... this will be our first 'rooting' a android. I love the phone way too much to screw something up.
Click to expand...
Click to collapse
This is not the easiest root I've ever done. Read the MT3G thread carefully, especially the last few pages. Getting adb to work in recovery takes some patience and some retries.
Loading ota.zip as update.zip and then switching with update.zip as the file is verified also takes time to get just right.
It's a PIA, but it's doable.
Very new at this kinda lost. Got my first android phone trying to figure all this stuff out. Is there a complete idoits gudie to this whole process. Btw loving my little android.
I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).
wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?
Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.
RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.
Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?
llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.
Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!
Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?
do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.
factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5
sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge
Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!
madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"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"
}
This is a very nice budget tablet from Tablet Express. I found mine on eBay for $93.00, new + free shipping, and have been very pleased with it. I love that it came with Developer Options already on, had USB Debugging enabled right out of the box, and has a screen protector installed by the manufacturer. Add the fact that the bootloader isn't even locked, and you really can't go wrong with this device.
I used the AIO TWRP Compiler script by @yuweng, to build this recovery, it's a very efficient tool to work with and he put a lot of work into it. Many, many thanks there!!
Well, enough rambling, lets get started...
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
Verify Partition Scheme
Over the past few months, it seems some devices have different names for the partition scheme, either "nand" or "mmcblk". So, the first step will be to check which type you have before installing TWRP and rooting the device. Here's how you check:
1) Connect the device to your PC, and open a terminal
2) Type the following:
Code:
# to make sure the device is recognized:
adb devices
# result should be:
List of devices attached
00000000000000000000 device
# Now type:
adb shell
# followed by:
ls -al /dev/block/by-name
# First Line should be 1 of the 2:
# This is a "mmcblk" device
lrwxrwxrwx root root 2016-07-20 00:08 UDISK -> /dev/block/mmcblk0p1
# This is a "nand" device
lrwxrwxrwx root root 2016-07-20 00:36 UDISK -> /dev/block/nandk
Once you know which device type you have, follow the below directions accordingly.
Root (Works for Android 4.4.4 and 5.1.1)
Rooting the device is easy, there are two methods that I know work:
1) Install TWRP, then flash Chainfires current SuperSu zip, find it Here (<-- recommend method)
2) Using Kingo Root for PC, find it Here (Use the Root Again option)
Install TWRP
You should already have ADB installed on your PC, or BusyBox and Terminal Emulator installed on your tablet, I will not cover installation of either of those. And you should know which type of mount partitions your device is using. To get the TWRP recovery on your device, you have a few options:
1) Use ADB to "push" the image (Android 4.4.4 and 5.1.1)
2) Use the included shell script, via BusyBox and Terminal Emulator (Android 5.1.1 and the device must already be rooted to use this option)
Download the appropriate zip for your device, located below, under Downloads, and extract it to a convenient location on your PC. If using your Tablet, the shell scripts and TWRP image must be in the root directory ( / ) to work properly.
Using ADB (Android 5.1.1) on "nand" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push X10_twrp3.0.2.img /dev/block/nandf
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 5.1.1) on "mmcblk" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push x10_twrp_mmc.img /dev/block/mmcblk0p9
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 4.4.4)*As of now, KK uses "nand" ONLY
This is the only way I could get it to work right on KitKat, sorry, no Terminal Emulator for this one...
Put the X10_twrp2.8.7.0.img file in the same directory as your working ADB, then enter the following, one line at a time:
Code:
adb push X10_twrp2.8.7.0.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/X10_twrp2.8.7.0.img of=/dev/block/nandf
#After it finishes:
reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That wasn't too bad, was it?
Using Terminal Emulator (Android 5.1.1 using "nand" ONLY)
Put the X10_twrp3.0.2.img and twrp.sh files in the root ( / ) folder of your tablet, then open the Terminal Emulator, enter the following, one line at a time:
Code:
su
sh twrp.sh
The script will tell you when it's done, now, power off the tablet. Boot into recovery by pressing and holding the Volume Down and Power Buttons. When the Dragon Touch logo appears, release the Power Button but continue to hold Volume Down until TWRP boots.
I hope you enjoy my work, and keep in mind that I like to keep things up to date, when a new version of TWRP comes out, I'll build it and post it here.
Downloads
X10 TWRP for "nand" devices
X10 TWRP for "mmcblk" devices
~ Also see Extras Section Below ~
Credits
@yuweng (bunch of help there)
@MSF Jarvis
@trillwizzard (for mmc fix)
@amw2320 (for modified firmware)
TeamWin
Extras
Themes for TWRP
TWRP 3.x Themes for Tablets (Landscape Devices)
Factory Firmware
TabletExpress.com
Modified Firmware
X10-V2-5.1-amw-TWRP_SuperSU.img (Created by: @amw2320, has TWRP (nand) and SuperSu already installed)
Using PhoenixUSBPro
My "short" guide on using the PhoenixUSBPro tool can be found here
X10 Device Tree (For Android 5.1.1)
GitHub
Change Log
Change Log (Newest First)
Added modified stock firmware (8-20-16)
Added info about devices using "mmcblk" instead of "nand", provided TWRP for each (7-23-16)
Added TWRP 2.8.7.0 for KitKat (Android 4.4.4) users and flash instructions (5-19-16)
@NepoRood, great work! One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
I am sure the flag has dir rather than folder in its name, but you can easily confirm that from the thread and you have to use an absolute path for folder name, so include the device/vendor/codename also, before rootdir.
MSF Jarvis said:
One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
Click to expand...
Click to collapse
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
That's what I'm here for, no?
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Franzferdinan51 said:
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
NepoRood said:
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
Click to expand...
Click to collapse
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
MSF Jarvis said:
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
Click to expand...
Click to collapse
Thank you for the offer my friend!
I've only tried to build for one device, well 2 actually, both RCA (MT8127), both failed miserably. Even though I got a "successful" build (ie: no errors/make completed) CM12.1 wouldn't boot. Come to find out, the zip and system.img had limited files, I can't remember which, but not enough for a complete rom
So, I decided to learn everything I could about building TWRP (thanks for your help with that too )
I'll pull all the vendor blobs from the X10 and try to put together the device tree for rom building and get back to you.
Thanks Again,
Nepo
marshmallow
you think this tablet is able to be upgraded to marshmallow?
i found a rom for 6.0.1 that has the same processor A83T
it has the same processor so do you think it would flash?
Thanks!
the firmware is
A83T_N106_N1061L6BC_20160309
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
The flag is actually this
Code:
RECOVERY_RAMDISK_DIRS += device/<vendor>/<codename>/ramdisk
As seen in this reverted commit
stickz42o said:
the firmware is
A83T_N106_N1061L6BC_20160309
Click to expand...
Click to collapse
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it here
PS, you can also use Phoenix Card to boot from External SD just to test
Ahhh Please Help?
@NepoRood
All images from TabletExpress Dragon Touch X10 10'' Android 5.1.
X10-HT-PW-V1-AL-5.1-A83T_N106_N1061L2BC_20151126
X10-HT-PW-V1-AL-4.4-20151104
X10-HT-PW-V2-AL-5.1-20150115
X10-HT-PW-V2-AL-4.4-20160116
A83T_N106_N1061L6BC_20160309-ok NOT WORKING. RED/WHITE BOOT SCREEN.
I have downloaded and flashed all these images and I cannot get TWRP to work? I have installed Via Adb and Terminal, but it will not flash the recovery.
All I get is the factory recovery. I can confirm it pushed it to device, but will not work.
Can someone else verify.
Regards
Paxster
For Users: The Best and Easy App to use is the PhoenixSuit (Just Google lol)
I'm using this one:
Paxster said:
X10-HT-PW-V2-AL-5.1-20150115
Click to expand...
Click to collapse
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
NepoRood said:
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it
PS, you can also use Phoenix Card[/URL] to boot from External SD just to test
Click to expand...
Click to collapse
I am going to try it tonight. I didn't know about the phoenixcard boot to test it. I will try that method and post my results if someone doesn't beat me to it
thanks for the info about the phoenixcard
I can't post a link till 10 posts for the firmware btw :/ i'll try to message it to you.
NepoRood said:
I'm using this one:
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
Click to expand...
Click to collapse
{
"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"
}
Yes Recovery is in the same Dir as ADB. It confirms being sent in the Adb Window to my booted Tablet.
Also if I use a Terminal app, it is also confirmed as being flashed, but I still get a 3e recovery? So strange.
Its driving me nuts lol..
Q:Should it work with any V5.1 Android Firm? I am using X10-HT-PW-V2-AL-5.1-20150115 from tabletexpress.
Can you confirm what version yours is working on please.
UPDATE... 5 Hours later.. I managed to flash the TWRP on Android V4.4 using Rashr. and when in recovery the screen is corrupted, unable to use? and Twrp is in Landscape mode. Shall try this method on V5.1.
Regards
Paxster
PS: @stickz42o A83T_N106_N1061L6BC_20160309 Does not work. I posted above.. Red/White Stuck Boot.
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment PAXSTER.LOG So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Paxster said:
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment 3747215 So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Click to expand...
Click to collapse
When building, I ran into problems of only TWRP booting, turns out it was an init.rc and recovery.fstab issue. But, I had that fixed for the final release I'm using the exact same firmware as you are, and TWRP works perfectly.
Could you attach your TWRP log?