Related
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Clearly you haven't done any searching in the Android Development section.
But that's OK. Go ahead and get an Epic. Enjoy your screwed-up GPS and all that, and make sure to change your password on here to something you won't remember, so we never have to see you again.
mainguy21 said:
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045
there you go. Just follow the directions and make sure you use the correct file locations.
real problem
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
thats funny i just typed in the search bar root evo hboot 2.02 and the first thread was the guide on how to do it.
@op if you are going to lie about searching the forum do it somewhere else. we know when a search isnt performed.
mainguy21 said:
and ive searched everywhere
Click to expand...
Click to collapse
Sure you have, buddy... sure you have.
ohhhhhhhhhhhhhh
You have been misinformed due to stupid people making stupid and false posts such as this one:
http://forum.xda-developers.com/showpost.php?p=9578042&postcount=8
Kingmac38 said:
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I am 20 and have ADHD and search is my best friend plus I've followed many rooting guides successfully so op has no excuse
Second that my girls epic is a pain in the ass and she kinda of.wish she got my phonr instead
Sent from my PC36100 using XDA App
thanks for help even though i searched everywhere.
but since i cant root my phone im stuck in the middle of it with a red triangle can i atleast go back to my phone? like unroot or something even though i didnt get all the way to root? please thanks
Follow these revised instructions from illogos pg 121 of hboot 2.02 root guide and everything should work. I've already rooted two hboot 2.02 hw 004 and in process of doing another one now. Everything works just fine if you understand and follow the instructions. Anyways, this was a lot simpler than the old school toast part 1 and 2 root methods so acquire some knowledge so you can someday help others and not be such a newbie.
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
mainguy21 said:
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
Click to expand...
Click to collapse
Which instructions though? Please follow these ones by illogos-
illogos said:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V8.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V8 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
Click to expand...
Click to collapse
my wife got an evo on black friday from radio shack and i rooted it with unrevoked in like 5 minutes.
I have adhd... I wonder if 4g transmissions cause an increase in autistic spectrum disorders!?!?
Sent from my PC36100 using XDA App
animal7296 said:
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Click to expand...
Click to collapse
he wouldn't regret getting the epic, it's a cool ass phone. if you want a crisper lcd and a keyboard get the epic.
fixxxer2008 said:
If you want a cheap-ass plasticky POS, get the epic.
Click to expand...
Click to collapse
Fixed that for you.
tejasrichard said:
Fixed that for you.
Click to expand...
Click to collapse
Thank you. It seems all these Samsung phones feel like garbage. Way too flimsy. Now I have a friend with an LG Optimus S which I just rooted for her, and I have to say the build quality is very nice.
A big thanks to RoboBear, tphillips, Lorddeff07, and anyone else that has helped make this happen.
I try to make my guides simple and straightforward so that the average user can root their device. I show every detail and walk you through the process. This guide is a complete video walkthrough on how to root the Galaxy Tab 10.1 WiFi with edits based on the issues that some may run into with previous guides. Without further ado, let's get started!
LINK TO MOD EDITutdated links
◄●REQUIRED DOWNLOADS●►
Just download, do not install or run anything yet.
◄●Instructions●►
This method is done on Windows. I recommend this way as its the easiest. If you don't have Windows, borrow from a friend.
◄●Downloading Files and Installing Drivers●►
Download the I have linked.
Extract the zip file by right clicking and selecting "Extract All," or by using an extracting program of your choice.
Open the folder and double click the driver file labeled "GT-p7510_USB_Driver_v1_3_2360_0-Escape.exe"
Install the driver. Its pretty much just Next, Next, Install, and Exit when its done.
◄●Connecting the Device●►
Turn on USB Debugging by going to Settings>Applications>Development and checking USB debugging. Click Okay to confirm
Power off the device by holding the power button and selecting Power off
Put the device into Downloading mode
Hold the Vol Down button (the left Volume button) and then hold the Power button as well.
Keep holding until you see two icons. First you'll see the Samsung Galaxy Tab 10.1 logo and then the icons will show up. Let go.
Press the Vol Up button (the right Volume button) to select Downloading mode.
Connect the device to your computer with the USB cable.
◄●Flashing a Custom Recovery●►
Go into the same root folder as before.
Double click the root application named "Odin3_v1.85.exe"
Select PDA
Double click the clockworkmod recovery file labeled "recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5" to select it.
Click Start
Once it is complete, you can close the program
◄●Completing the Root●►
Disconnect your USB cable
On your device, turn off USB Debugging by going to Settings>Applications>Development and unchecking USB debugging
Plug your USB cable back in
On your computer, go to the same root folder as before and transfer the zip file labeled "Samsung_Galaxy_Tab_10.1_root.zip" to your device. Don't put it inside any folder.
Confirm that it was transferred by clicking inside the device folder
Power off the device by holding the power button and selecting Power off
Put the device into Recovery mode
Hold the Vol Down button (the left Volume button) and then hold the Power button as well.
Keep holding until you see two icons. First you'll see the Samsung Galaxy Tab 10.1 logo and then the icons will show up. Let go.
Press the Vol Down button (the left Volume button) to highlight the left icon.
Press the Vol Up button (the right Volume button) to select Recovery mode.
You should see that you are in ClockworkMod Recovery. If not, start over
Use the volume buttons to highlight "Install zip from SD card" and hit the Power button to select it.
Use the volume buttons to highlight "Choose zip from SD card" and hit the Power button to select it.
Use the volume buttons to highlight "Samsung_Galaxy_Tab_10.1_root.zip" and hit the Power button to select it.
Use the volume buttons to highlight "Yes - Install..." and hit the Power button to select it.
When it finishes, the last line should say "Install from sdcard complete."
Use the volume buttons to highlight "*****Go Back*****" and hit the Power button to select it.
Hit the Power button to select "reboot system now"
Your device will reboot
You're now rooted!
Excellent Guide.
Thank you.
This one is Noob-Safe
I love how you have proper grammar and punctuation skills. Spacing is good, fonts are bold where they need to be, this is how a guide should look!
All guides should be written like this, can u offer classes for the uneducated?
EyeAndroid said:
I love how you have proper grammar and punctuation skills. Spacing is good, fonts are bold where they need to be, this is how a guide should look!
All guides should be written like this, can u offer classes for the uneducated?
Click to expand...
Click to collapse
Would there be a higher demand for that than my guides? lol. But thanks a lot, I appreciate it Just trying to make it easy for everyone.
Wow. A guide that is easy to follow, in plain and understandable English, and thorough!
Thanks a lot! I'll be following this when I get my Tab this week.
perfect instructions! Thanks!
just rooted this way. It was the easiest root I have ever done!
I have rooted two different androids and the rooted process took really long on my other phones. This took me the same amount of time as your video.
Very good guide.
1,000,000 points for not hosting your files on one of the uber-annoying file hosting sites. I used your video to root my EVO phone as well, have been waiting for your guide for the 10.1. great job....
All done, started after posting my thanks and now I am all rooted..(sp?) Just need an Easy Button boot screen after the root.
Perfect guide
Does this work with 16GB WIFI UEKME 3.1 tab?
djR3Z said:
A big thanks to RoboBear, tphillips, Lorddeff07, and anyone else that has helped make this happen.
I try to make my guides simple and straightforward so that the average user can root their device. I show every detail and walk you through the process. This guide is a complete video walkthrough on how to root the Galaxy Tab 10.1 WiFi with edits based on the issues that some may run into with previous guides. Without further ado, let's get started!
Click to expand...
Click to collapse
Thanks for the detail root instruction, it is very clear easy to understand (I have clicked the thank button).
Question: Just want to confirm whether this root method only applied to wifi only tab or applied to all wifi and 3G tab and with different version.
bdejong11129 said:
1,000,000 points for not hosting your files on one of the uber-annoying file hosting sites. I used your video to root my EVO phone as well, have been waiting for your guide for the 10.1. great job....
Click to expand...
Click to collapse
Haha yeah I hate that too, which is why I will always host files myself. But thanks a lot man, I really appreciate the support.
yongck7 said:
Thanks for the detail root instruction, it is very clear easy to understand (I have clicked the thank button).
Question: Just want to confirm whether this root method only applied to wifi only tab or applied to all wifi and 3G tab and with different version.
Click to expand...
Click to collapse
Unfortunately this is just for the Wifi only version. I could probably make a written guide for the others, but I don't have the devices to support that. Sorry dude.
Moderator, please make this sticky !!!
Thx.
MagicOnline said:
Moderator, please make this sticky !!!
Thx.
Click to expand...
Click to collapse
Ohhh, that'd be nice Hopefully I can get my hands on a 3G and 4G version. Someone PM'd me that this worked on their 3G but their gtab is now unlocked so hopefully I can figure that out blind
Sticky this thread!
Boot loop and no recovery mode ability
Sorry in advance for the long thread.
Great documentation. I hope you can help me. I posted the below at the stickied root thread but I haven't received any responses. It seems I blew away recovery mode. My tablet consistently boot loops. I have the option to choose recovery but when selected the screen goes blank for several seconds then reboots. I can get into download mode but my PC doesn't recognize the hardware and will not install the proper Samsung drivers. After reading your thread I'm wondering if this is because I didn't set debugging mode properly.
"Hi all I need some help. Verizon LTE 10.1 tab is boot looping after attempting bone head maneuver. Attempted root per Lorddeff07's method. Installed recovery file, system rebooted. Installed kernel file, system rebooted. Installed clockwork mod premium from market. Installed clockwork mod recovery for galaxy tab. Initiated backup via cwm, system rebooted and started boot looping. I can get into downloading mode but when I try to access recovery mode the tablet starts to boot loop.
I tried odin but the USB drivers are not installing properly. If I force the driver to install as Samsung ADB the tablet will display "start odin" when in downloading mode. However the odin app does not recognize the tablet. I'm running W7 pro Sp1 x64.
I also tried to use nvflash per shep211's tutorial but that didn't work. I get to section 2 step 17 when the command fails and the tablet will disconnect from the PC.
I know there has to be a way to fix my fUP. can anyone asist?"
FIXED: Removed the Verizon SIM card. Booted into download mode. Manually added the unrecognized driver as Samsung Mobile USB Serial Port. Opened odin flashed the ltecwm.tar.md5 file. Rebooted. All is good. Rebooted into recovery and installed root using Samsung_Galaxy_Tab_10.1_root.zip. Everything is up and running.
Thank you so much nice eay guide just rooted my tab thanks to you!!1 I pass you a beer sir
jobless said:
Sorry in advance for the long thread.
Great documentation. I hope you can help me. I posted the below at the stickied root thread but I haven't received any responses. It seems I blew away recovery mode. My tablet consistently boot loops. I have the option to choose recovery but when selected the screen goes blank for several seconds then reboots. I can get into download mode but my PC doesn't recognize the hardware and will not install the proper Samsung drivers. After reading your thread I'm wondering if this is because I didn't set debugging mode properly.
"Hi all I need some help. Verizon LTE 10.1 tab is boot looping after attempting bone head maneuver. Attempted root per Lorddeff07's method. Installed recovery file, system rebooted. Installed kernel file, system rebooted. Installed clockwork mod premium from market. Installed clockwork mod recovery for galaxy tab. Initiated backup via cwm, system rebooted and started boot looping. I can get into downloading mode but when I try to access recovery mode the tablet starts to boot loop.
I tried odin but the USB drivers are not installing properly. If I force the driver to install as Samsung ADB the tablet will display "start odin" when in downloading mode. However the odin app does not recognize the tablet. I'm running W7 pro Sp1 x64.
I also tried to use nvflash per shep211's tutorial but that didn't work. I get to section 2 step 17 when the command fails and the tablet will disconnect from the PC.
I know there has to be a way to fix my fUP. can anyone asist?"
FIXED: Removed the Verizon SIM card. Booted into download mode. Manually added the unrecognized driver as Samsung Mobile USB Serial Port. Opened odin flashed the ltecwm.tar.md5 file. Rebooted. All is good. Rebooted into recovery and installed root using Samsung_Galaxy_Tab_10.1_root.zip. Everything is up and running.
Click to expand...
Click to collapse
Glad you got it fixed! Did you use the Samsung_Galaxy_Tab_10.1_root.zip in my pack or from the LTE section in lord's thread?
I used the Samsung_Galaxy_Tab_10.1_root.zip that you provided.
Hi folks.
I'm new to this device, but not to Android, and I have one question.
I bought this tab for my wife and she don't want me to root it I wonder if I can update to 4.4.2 without root ? If yes, how?
Thanks
You can update by OTA which has rolled out for n10 and wait for sometime you will have notification about it or check it manually....
Piyush Pastor said:
You can update by OTA which has rolled out for n10 and wait for sometime you will have notification about it or check it manually....
Click to expand...
Click to collapse
Do I need root for the manual way ?
The Wugfresh Nexus Root Toolkit (http://www.wugfresh.com/nrt/) will let you flash a stock image and root and/or unroot your device. It's always worked for me, with the major hassle being getting the correct drivers loaded and working on the PC.
tjupille said:
The Wugfresh Nexus Root Toolkit (http://www.wugfresh.com/nrt/) will let you flash a stock image and root and/or unroot your device. It's always worked for me, with the major hassle being getting the correct drivers loaded and working on the PC.
Click to expand...
Click to collapse
Don't you have to unlock it first before you can do anything which isn't OTA? So unlock, then flash stock+unroot, then lock.. You can do each of those 3 steps with WUGS NRT. Not sure about if unlock needed before stock+unroot.
Then it will be 100% vanilla 4.4.2 and receive OTAs in the future.
Don't you have to unlock it first before you can do anything which isn't OTA?
Click to expand...
Click to collapse
Good point. I unlocked and rooted as soon as I got the tablet in the first place. Actually, Wugfresh has done a good job of "bulletproofing" the scripts and the informational messages are, in fact, informative so I suspect that it'll tell you if you need to unlock.
Hi,
You can Google for Nexus 10 OTA (the version you want) and then installing it via the stock recovery, just plug your tablet to your computer, copy the OTA zip to your adb folder and do the following steps:
1 - Make sure that USB Debugging is on (if it's not search how to do it)
2 - Open a cmd in your adb + OTA zip folder and type the following:
Code:
adb reboot recovery
3 - Wait for your tablet to boot and then you'll probably see an android with a red exclamation mark, press volume+, hold it and press power (if it didn't do the trick try the opposite, hold power and press volume+).
4 - You'll see a menu now, using volume - go to flash zip via sideload and press power button.
5 - Now simply type on your cmd in the folder
Code:
adb sideload *inserttheOTAzipfullnamehere*
And you're done. If the tablet didn't reboot, do it yourself by the same way you selected sideload, select reboot.
Hope this helps,
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
XxLordxX said:
Hi,
You can Google for Nexus 10 OTA (the version you want) and then installing it via the stock recovery, just plug your tablet to your computer, copy the OTA zip to your adb folder and do the following steps:
1 - Make sure that USB Debugging is on (if it's not search how to do it)
2 - Open a cmd in your adb + OTA zip folder and type the following:
Code:
adb reboot recovery
3 - Wait for your tablet to boot and then you'll probably see an android with a red exclamation mark, press volume+, hold it and press power (if it didn't do the trick try the opposite, hold power and press volume+).
4 - You'll see a menu now, using volume - go to flash zip via sideload and press power button.
5 - Now simply type on your cmd in the folder
Code:
adb sideload *inserttheOTAzipfullnamehere*
And you're done. If the tablet didn't reboot, do it yourself by the same way you selected sideload, select reboot.
Hope this helps,
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Click to expand...
Click to collapse
That's what I wanted to know. Thank you all !!
MoFo will NOT work on 5.1 so do NOT upgrade to the 5.1 bootloader or partition table if you want to use MoFo.
This method involves purchasing a piece of software named mofo.exe that allows you to flash a modified, unsigned system image to your device despite its locked bootloader. The cost is $20. Links to the modified images for the XT1096 and XT1097 are found in the OP of the MoFo support thread:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
This Method Does Not Disable Write Protection. Please read the following post if you don't know what that means:
http://forum.xda-developers.com/showpost.php?p=60412113&postcount=292
This Method Trips the Root Checker and Your qe Will Convert to qe 1/1 Permanently! What this means is that if you boot your phone into recovery, you will see qe 1/1, which means you are currently running modified software. The qe will stay at 1/1 even if you flash back to stock.
1. Check Your Software Version and Enable USB Debugging
Go to Settings -> About Phone and read your Android Version – it should say 5.0 on the XT1096 and 5.0.2 on the XT1097. If not, and it says 4.4.4, you are still on 4.4.4 and as long as you have not modified your system by flashing using mofo.exe, you should still be stock and can take the 5.0 or 5.0.2 OTA.
If you haven’t already, go into Settings -> About Phone and click on Build Number repeatedly until you get the message you are developer now (or something like that). Then hit the back button and you will see that the Developer Options now appear. Click on Developer Options and check USB Debugging.
2. Install Motorola Device Manager (MDM) and Drivers to Your Computer
You can download MDM and the drivers here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Install MDM on your computer after you download it. MDM should install the drivers.
3. Download Copies of Adb and Fastboot
You can get these from the Adroid SDK but you don’t need the whole Android SDK. Root Junky has the files you need on his site here:
http://rootjunkysdl.com/?device=Adb Fastboot Files
I made a folder on my computer named c:\mx2014 and put the zip file in there. Then I unzipped it with 7-zip.
http://www.7-zip.org/
4. Download a Copy of the Official Firmware
Root Junky has a copy of the XT1096 5.0 official firmware here:
http://rootjunkysdl.com/?device=Moto X 2014&folder=Official Firmware
and the XT1097 5.0.2 fxz is here:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
You should download it into a separate folder (I put mine in a folder named c:\mx2014\lollipop) and unzip it so if you have any problems you can flash back to stock. Place a copy of fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll in the folder with the lollipop official firmware.
Also if you are planning on taking the 5.1 OTA when it is released, you would need to flash your system back to stock so it is a good to have it ready. And if you are planning to update to 5.1 via MDM I would still flash back to stock because if you don't, IME MDM will detect that you are running a modified software and will wipe your device when it upgrades you to 5.1. If you flash back to stock first, MDM will not wipe your data and sdcard when it upgrades you to 5.1.
5. Test the Drivers and Adb
Once you have completed Steps 1-3, you can test the drivers and adb. Power on your phone and after it boots, connect it to your computer via the data cable. Open a command prompt, and then navigate to the directory where you have adb and fastboot by typing:
cd c:\mx2014 (or wherever you have adb and fastboot stored)
and hitting enter. Then type:
adb devices
You should then see a prompt on your phone asking you to authorize your computer. Check always allow and click OK. Adb should show you the serial number (not the IMEI) of your device.
Now type:
adb reboot bootloader
to get into bootloader (BL) mode (aka fastboot mode).
6. Test the Drivers and Fastboot
Once you are in BL mode, double check that on your phone’s screen right above the first green line you see this:
Transfer Mode: USB Connected.
If it does not say that, go to Root Junky’s site and download the Motorola drivers and manually install them.
http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola
Then type:
fastboot devices
and hit enter. Fastboot should return your device’s serial number.
7. Test Getting into Recovery and Wiping Cache
While in BL mode, scroll down to Recovery by pressing the vol dwn button to highlight Recovery. Then select Recovery by pressing vol up. You should see the dead android with a red triangle having an exclamation point in it coming out of its stomach. Then press the pwr button for a couple of seconds and then press and release the vol up button and then release the pwr button to get into the recovery menu. Use the vol dwn button to scroll to wipe cache partition and then press the pwr button to select it. You should see that the cache is being formatted.
When cache is done being wiped, the recovery menu should reappear and you should hit the pwr button to reboot into system.
8. Test That You Know How to Get Into Bootloader Mode Using Buttons
Disconnect your phone from your PC, power down your phone and then hold down volume down and then press and hold the power button. Hold both buttons simultaneously for about 4 seconds and then release the power button and then the volume down button. This should put you in Bootloader mode (aka fastboot flash mode). Alternatively, you can try pressing volume down + volume up + power and holding for about 4 seconds then releasing.
Once in BL mode, you can either hit the power button to boot back into Android or if you want to test that you know how to flash back to a stock system, complete the instructions in Step 9.
NOTE – flashing the system partition does NOT affect your apps/settings/text messages/call history, which are stored on the data partition, not the system partition. Updates to system apps since 5.0/5.0.2 was rolled out will be lost as well as any system app settings that are relevant to the updates or stored on the system partition.
NOTE – flashing the system partition does NOT affect your stored media (e.g, pictures, music, videos), which are stored on the sdcard partition, not the system partition.
9. Test That You Know How to Flash Stock System (Optional)
While in BL mode you can test that you know how to flash back to a stock system. This is optional but if you have never done it before, it is a good idea to do it IMO. When you flash a system.img, you do not lose your apps/data/texts or your media unless the app is a system app, then you will lose the updates since 5.0 was rolled out (but those can be re-downloaded from the Playstore). However, it is always a good idea to backup before you flash in case you do something wrong. I use SMS Backup and Restore to backup my texts and my photos are backed up to my Google account.
Put your device in BL mode and then connect it to your computer. Open a command prompt and navigate to where you have the stock 5.0/5.0.2 image stored on your computer. Type the following:
fastboot flash system system.img_sparsechunk1
and then hit enter to flash the first sparsechunk. Repeat for the other sparsechunks until you have flashed all 9 of them. Then boot into recovery, wipe cache and boot into system.
10. Purchase MoFo.exe
First you should go to:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
and read all of the information. And be sure to watch Root Junky’s video here:
https://www.youtube.com/watch?v=AXAYjbf76II&feature=youtu.be
The high level summary of what you will be doing is this:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
2. Using the link generated by MoVerify to navigate to where you can purchase mofo.exe; and
3. Purchasing and downloading mofo.exe.
11. Download, UnZip and Flash a Pre-rooted Ext4 Image
The OP of the MoFo thread has links to the pre-rooted images that are available for the XT1096 and XT1097. Once you download one of them, unzip it and move the image file to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofo.exe flash [Insert name of image file here]
then hit enter. Of course you do not put brackets around the name of the image file. Once the pre-rooted image has been flashed (about 25 minutes), boot into recovery and wipe the cache then boot into system.
It may take a few seconds for the boot animation to start so don’t panic. Once the system has booted, to check that you are rooted, download root checker basic from the Playstore and confirm that you are rooted. Your device will also bypass the subscription check when you turn on WiFi hotspot.
The copy of mofo.exe that you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it - unless you upgrade to a higher version of Android. If you upgrade to a higher version of Android, once that higher version of Android is supported by MoFo for your device, you can re-download mofo.exe for the higher Android version.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432
Mofo will NEVER be updated to support 5.1 as the exploit was closed with the 5.1 bootloader.
Thank you for the guide and for the testing - its a great service to Moto X owners.
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?
HTC-OH_SNAP said:
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?
Click to expand...
Click to collapse
It is best to ask on the MoFo support thread where you are more likely to get maiko1's attention.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Adding this to the OP
This is from the MoFo support forum - there appears to be some confusion about mofo.exe being device specific. The copy of mofo.exe you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432
JulesJam said:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
Click to expand...
Click to collapse
might want to expand the MoVerify process with little baby steps.... the Mofo site and the Mofo forum here are again very sparse on details.
1) download and unzip the MoVerify program
2) connect you phone to computer
3) open cmd window
4) navigate to c:\mx2014 (or wherever you have adb and fastboot stored)
5) type adb devices
6) type adb reboot bootloader
7) navigate to the MoVerify folder
8) go to the folder that represents your computer's OS; let's assume Windows here
9) in the Windows folder, double click on "mofoverify_gui.bat"
10) MoVerify will open a cmd window and return back that your devices was found and give a link that looks like
https://mofo.disekt.org/verify/ [big long alphanumeric string]
11) right click anywhere in the text that is in the MoVerify cmd window and select "Select All" and then hit enter
12) open Notepad or other text editor and past the text
13) cut and paste the https address into your browser
14) follow steps to purchase Mofo
i have purchased but have not gotten farther yet... may have some more suggestions later...
Nice job putting this together. And thanks for all of your testing during the process!
is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill. if these two merhids are equivalent for this mofo process, maybe both options should be stated in the step by step.
is there any time when the button method MUST be used?
---------- Post added at 06:40 AM ---------- Previous post was at 06:33 AM ----------
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?
[email protected] said:
is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
Click to expand...
Click to collapse
No.
[email protected] said:
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
Click to expand...
Click to collapse
I tend to use the buttons so that is why I wrote it up that way.
[email protected] said:
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
Click to expand...
Click to collapse
Yes, that would work.
[email protected] said:
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill.
Click to expand...
Click to collapse
True but if you soft brick your phone, the buttons are the only way to get into bootloader mode so best to be familiar with this way.
Did you try holding vol dwn/up and pwr simultaneously for 4 seconds and then releasing? After the lollipop update I swear that works the best for me. Let me know if that works more reliably for you - it does for me.
[email protected] said:
is there any time when the button method MUST be used?
Click to expand...
Click to collapse
If you get into a bootloop or your screen goes black and the phone is unresponsive.
[email protected] said:
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?
Click to expand...
Click to collapse
Standard fastboot has a size limitation on how large of a file it can flash. So system images above that size limitation have to be broken down into smaller chunks. The version of the 5.0 Official firmware that is available to us is the one on Root Junky's site and that one is broken down into chunks.
Motorola made a modified version of fastboot, often referred to as mfastboot, that can flash larger files. However, I cannot find a version of mfastboot that can flash the 5.0 system.img (fxz) that we have available to us. If anyone has a version of mfastboot that can flash the 5.0 fxz system.img, then you could flash it. RSD Lite may be able to flash it, idk I didn't try it.
As for mofo.exe - mofo.exe has a way to avoid the size limitations of standard fastboot. Idk why standard fastboot has a size limitation in the first place. But it does and so large files have to be broken down into chunks when you use standard fastboot to flash. Mofo.exe doesn't have that same size limitation.
JulesJam said:
Once you download one of them, unzip it and move the image to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofoe.exe flash XT1096_5.0_22.21.11_rooted.img
then hit enter.
Click to expand...
Click to collapse
ok. so i attempted this today
1) powered off phone
2) booted in BL mode using power and volume buttons (yes it does work very well, esp after taking the phone OUT of the case so buttons are more fully accessible) - phone screen says "AP Fastboot Flash Mode (S)" at very top
3) plugged phone into computer
4) double clicked the mofo_gui.bat to open cmd window
5) copy and pasted your text exactly
6) after hitting enter, i got the following error
======================================
'mofoe.exe' is not recognized as an internal or external command,
operable program or batch file.
======================================
methinks you have a typo in your mofo command... extra "e" that should not be there??
taking out the "e" worked and it flashed
it then said
=====================
Flashing 'XT1096_5.0_22.21.11_rooted.img' to device. Do not interrupt.
Progress: 100%
Complete. Press power to start.
=====================
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
if i hit the power button again, it still showed the battery level screen
so i pressed and held BOTH the power and volume buttons, and it booted!
when i power down, it goes to the batter level screen. and i can't seem to get into BL mode using the power and volume buttons
however, i can get to BL, then Recovery using adb, and was able to wipe cache partition
i installed and ran Root Checker Basic ... make sure you click "Grant" when it asks for permission while checking root access, or it will return a "no root access" message.
i now have wifi tethering! yahoo!
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
i am running Nova Launcher... could that be the issue with the widget not working?
otherwise, i have to go into Settings to turn it on/off... which is better than NOT having hotspot at all!
[email protected] said:
methinks you have a typo in your mofo command... extra "e" that should not be there??
Click to expand...
Click to collapse
Oops! Thanks for catching that - I will edit!
[email protected] said:
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
Click to expand...
Click to collapse
Disconnect it from your PC and then press the power button to turn it on.
[email protected] said:
when i power down, it goes to the batter level screen.
Click to expand...
Click to collapse
That is b/c it is connected to your computer. The same thing will happen if you have it plugged into the wall.
[email protected] said:
i now have wifi tethering! yahoo!
Click to expand...
Click to collapse
Yay!!!! I am at over 50GB this month from all of the downloading of images I did to test them, lol! I have never used that much before.
[email protected] said:
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
Click to expand...
Click to collapse
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
[email protected] said:
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
you want a hotspot toggle then, but idk of any off hand.
JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
might want to just add the words "disconnect the phone fromthe usb cable" somehwere in the OP directions, you know, just for all those noobs out there that might get panicked
JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.
mikeoswego said:
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
Click to expand...
Click to collapse
thanks! I suggest booting into recovery and wiping cache before you boot back into Android.
mikeoswego said:
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.
Click to expand...
Click to collapse
yeah I noticed that last night, it is great!
[email protected] said:
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
There is a Hotspot toggle in quick settings. From your lock screen, just swipe down from the top of the screen to see it. From your home screen, swipe down with 2 fingers.
Anyone know whether the January security patch has started rolling out OTA on this thing yet?
I ask because up until this month I had been using custom ROMs. It was only a few weeks ago I decided to flash stock on the NP and focus my modding efforts on my phone, where I don't have to deal with OTG cables and Netflix's DRM. Now I'm starting to wonder whether my former tweaking is blocking me from updates somehow, or whether it always takes this long. I mean I'm back to stock recovery and I'm not even rooted, and four days for a critical security update seems like an awful long time.
I'm in the UK, stock 6.0.1 unrooted, and still no OTA yet
Sent from my iPad using Tapatalk
If you got tired waiting (as I was):
1. Get the January patch OTA for sidleloading (MMB29M to MMB29T)
2. Turn on Debugging on the NP
3. Connect the NP to your PC and run adb reboot bootloader
4. Using NP power button, select recovery (press once to change and then long press 2 sec to select)
5. Once "no command" appears, long press 2 sec to make the recovery menu appear
6. Select ADB sideload zip (press once to scroll and then long press 2 sec to select)
7. From your PC then run adb sideload file-downloaded-before.zip
The process will take 2-3 minutes and after that your NP will have Jan 2016 patch!
jeppo said:
If you got tired waiting (as I was):
1. Get the January patch OTA for sidleloading (MMB29M to MMB29T)
2. Turn on Debugging on the NP
3. Connect the NP to your PC and run adb reboot bootloader
4. Using NP power button, select recovery (press once to change and then long press 2 sec to select)
5. Once "no command" appears, long press 2 sec to make the recovery menu appear
6. Select ADB sideload zip (press once to scroll and then long press 2 sec to select)
7. From your PC then run adb sideload file-downloaded-before.zip
The process will take 2-3 minutes and after that your NP will have Jan 2016 patch!
Click to expand...
Click to collapse
Woah! I had no idea Google put out sideloadable zips. I figured my only option for stock was the fastboot images.
For future reference, where did you find that URL? I'm also wondering if these could be flashed with TWRP, or whether it would fail with anything other than stock recovery. I mean I already have an SSH app for easy file transfers, so it'd be amazing to install future updates without lugging my computer over to connect with the player. But stock recovery doesn't exactly have a file manager or anything.
Either way, thank you. This is awesome.
EDIT: Actually stock recovery surprisingly has an "apply update from SD card" option, but it throws me a "couldn't mount /sdcard" error every time. I guess I'll stick with ADB sideloading for now, unless I get some kind of indication a custom recovery would work with these patches. But I get the feeling it wouldn't.
Unfortunately there is no public listing of the OTA URLs. You have to wait for someone to posts it online (or on xda forums).
About custom recoveries, those zips will not work with them because the update process checks the integrity of the system and it fails if you have something different from clean stock.
Sent from my Nexus 5 using Tapatalk
Yup still waiting here, more curious to see how fast or slow it will come.
are there instructions to load this in TWRP? thanks
knives of ice said:
are there instructions to load this in TWRP? thanks
Click to expand...
Click to collapse
Unfortunately based on what jeppo is saying it wouldn't work with TWRP. Otherwise it would be the same process. TWRP has an "ADB sideload" option under "advanced" if I recall correctly.
I got my OTA update last night... (it says January 1, 2016 security patch) not sure if I see any difference in color though
if someone would make a flashable zip in twrp i'd even willing to paypal a few bucks
pretty please?!
Must have gotten the update sometime today.