Asus released the new Android 4.2 to our beloved devices and you may be wondering how can you update if you are unlocked and how can you root it.
Note: this guide was updated with the 2.5.0.0 TWRP. For this to work properly, you will need to use the last 10.6.1.27.1 version of the tablet, or a newer one. If you are already on a previous 4.2.1 version, please update to the new one using this same guide. If you flash this recovery with the older versions of the 4.2.1 bootloaders, you will end up with a double screen! New TWRP versions won't be able to mount boot and recovery, and won't work with all SD cards, not to talk about backup issues!
Things you should know before you start:
- I marked each title of this guide with [LOCKED BL], [UNLOCKED BL] and [BOTH BL] to specify witch ones will work with locked/unlocked or both bootloaders, respectively.
- Please verify if you have the correct drivers for the tablet installed on your computer. Windows 7/8 should install these automatically.
- The new 4.2 updates the bootloader, removing the USB icon that used to appear there and allowed you to enter fastboot. It's OK, you will be able to use it right from the bootloader menu, without selecting any option at all.
- Do this at your own risk! I'm not responsible if you break your tablet!
- Don't forget to make BACKUPS!
- If you are already on 4.2, then you can skip to the Recovery and Root parts of this guide
-- Installing / Updating to 4.2.1 --
There are three methods you can use to update your tablet to the latest Android stock version. All of them will require you to download the
firmware file located at Asus website. You can download them from here. Select Android as the OS, firmware and choose the right firmware for you SKU. You can find your SKU by following the instructions on the website itself. Don't forget to unpack the zip file you downloaded: there's another inside!
[BOTH BL] Method 1: Updating directly from stock ROM
Notes:
You must have a stock ROM installed
You need to put the update file on an SD card
You will keep all your data
I do not recommend this method: sometimes it ends up on a brick
If your tablet is stock, or have some custom ROM based on stock installed, you can directly update the tablet by simply inserting a SD Card with the firmware file inside. Android will prompt you with a notification asking if you want to update. Touch it and wait until the update is done
[UNLOCKED BL] Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash staging blob
, hit enter and wait until it completes
Hold the power button for 10 seconds to reboot the tablet
You are now updated to Android 4.2
[UNLOCKED BL] Method 3: Update using TWRP recovery
Notes:
You must have TWRP installed
You need to put the update file on an SD card
This was the method I used since I wanted to prevent any bugs due to old data and to ensure the new partitions from 4.2 would be OK
You will keep your data as long as you don't wipe Data and Factory reset (including internal memory)
Follow the steps bellow if you want to update to 4.2.1 DELETING ALL YOUR DATA , STARTING FROM SCRATCH!
Insert the SD card with the update file on the tablet
Reboot to recovery
Wipe Cache, Dalvik and System. Wipe Data if you want a fresh start on your tablet, but remember, THIS WILL WIPE ALL YOUR DATA AND INTERNAL MEMORY!!. You can also do a Factory Reset instead of data wipe if you want to remove all your android configurations/apps keeping your internal storage.
Install the Asus Firmware
Reboot (ignore the "no OS installed message) and let it finish
You have now the latest Android 4.2.1
[UNLOCKED BL]-- Installing TWRP (Recovery) --
Since this new update brings a new bootloader, older recovery versions from 4.1 won't work at all. Don't try to flash one!
This guide will give you a recovery that works just fine on the new bootloader. And yes, it can read/write to an external SD just fine. Follow this steps to install the new recovery on your device:
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and the TWRP 2.5.0.0 which works with the new bootloader)
Open a command line on the extracted folder (you can use the instructions I wrote in Method 2 if you don't know how to do this) and type
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds. Don't enter recovery directly!
You have now the new recovery for Android 4.2 .
[BOTH BL] -- Rooting --
Note: If you are willing to install a custom ROM like CROMI you don't need this. Custom ROMs have root by default.
Rooting the tablet once you have a recovery is pretty easy. Here's how you can do it:
- Unlocked devices
Download SuperSu zip file from here (choose the flashable version) ]and place it on a SD card or inside the root of your tablet's internal memory
Reboot the tablet holding vol down, and when the three icons appear, hit volume up to enter recovery
When the recovery prompts you a password, hit cancel (this is a bug from the current version of TWRP, and it should be fixed soon. It is ok to ignore it!)
Flash the zip you just downloaded
Wipe Dalvik/Cache (just in case)
Reboot
You are now rooted!
- Locked devices
If you have your bootloader locked you can root Android 4.1/4.2 by using the method discovered by Morlok8k, here: http://forum.xda-developers.com/showthread.php?t=2228613 (note that this isn't tested yet for the latest 10.6.1.27.5 firmware!)
[UNLOCKED BL] -- Downgrading to 4.1 or other firmware --
I was going to write a downgrade method but it seems that there is a good one here: http://forum.xda-developers.com/showthread.php?t=2195883
Again, do it at your own risk.
[LOCKED BL] -- Recovering your tablet from scratch --
If you are on a stock locked device and somehow got a bootloop and you can't do anything with your tablet you follow this steps to completely restore your tablet. Note that all data will be lost.
Pretoriano80 said:
========= Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with stock recovery =========
1) Download the latest firmware from Asus website
2) Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3) Rename the extracted archive to "EP201_768_SDUPDATE.ZIP" (without the " ") and upload it to a MicroSD card
4) Insert the MicroSD card in your tablet and use this button combination to Power ON and go to recovery --> Start the tablet by pressing Volume Down and POWER togheter for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire.
At this point the device will go in recovery and should start updating your firmware .
Note: Keep in mind that Windows doesn't show the known file extensions so most users don't have to put the .ZIP extension in the filename.
Click to expand...
Click to collapse
This tutorial is made of things I gathered on the forums: I do not own anything! Hit thanks if I helped you :angel: I will keep it updated once new things come out
A special thanks to elesbb for the fastboot methods
This is great. Just one question for clarification: Users have reported not being able to see their External microSD's in TWRP. Is this still the case, or did the patch to TWRP alleviate this issue?
would i need to unlock the bootloader to do this?
MrCHUPON said:
This is great. Just one question for clarification: Users have reported not being able to see their External microSD's in TWRP. Is this still the case, or did the patch to TWRP alleviate this issue?
Click to expand...
Click to collapse
Here TWRP is recognizing the external SD It lists the files and I'm doing right now a backup to it . No errors whatsoever
Here is a photo of me backing up to an 4GB SD card
{
"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"
}
And the end of it
jobankler said:
would i need to unlock the bootloader to do this?
Click to expand...
Click to collapse
Check the OP...First item. "You must be unlocked".
So yes.
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
Hoi
My device is unlocked
Must i unlocked again for 4.2.1
Thanks hope you can help my
Sent from my ASUS Transformer Pad TF300T using xda premium
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
jackie1234 said:
Hoi
My device is unlocked
Must i unlocked again for 4.2.1
Thanks hope you can help my
Sent from my ASUS Transformer Pad TF300T using xda premium
Click to expand...
Click to collapse
So I've read, upgrading does not relock you, so you shouldn't need to. For those that are locked and upgrade to 4.2.1 there is a new unlock tool to do it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Verified that this works for me. If you read ahead and placed the SuperSu zip on your SD card BEFOREhand, you can even skip one of the reboots.
WARNING
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
joelalmeidaptg said:
Hey guys! Asus released the new Android 4.2 to our beloved devices and now we are able to root it using a few steps.
Notes:
- You must be unlocked
- If you don't have 4.2.1 on your tablet yet, download it via the Asus website, unpack it, and place the file on your SD car and flash it using a custom recovery or the update notification on a stock ROM
- If you have 4.2 and want to unlock it, remember to check Asus website to download the new unlock tool available for 4.2 devices
- Please verify if you have the correct drivers for the tablet installed on your computer
Lets get started!
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and a patched version of TWRP 2.4.4.0)
Open a command line on the extracted folder and type fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds. Don't enter recovery directly!
Once the tablet boots up, download SuperSu zip file from here and place it on the root of your tablet's internal memory
Reboot the tablet again holding vol down, and when the three icons appear, hit volume up to enter recovery
When the recovery prompts you a password, hit cancel
Flash the zip you just downloaded
Wipe Dalvik/Cache (just in case)
Reboot
Aaaaand... Congratulations, you have now a rooted stock Android 4.2.1 !!
This tutorial is made of things I gathered on the forums: I do not own anything! Hit thanks if I helped you :angel:
Click to expand...
Click to collapse
:good: :fingers-crossed: :victory: :laugh: I have no words to thank you friend, excellent contribution.
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
Did you unpack the zip downloaded from Asus?
Sent from my ST25a using xda app-developers app
Tamaskan said:
Did you unpack the zip downloaded from Asus?
Sent from my ST25a using xda app-developers app
Click to expand...
Click to collapse
Again, I followed the tutorial blindly for the flash
Maybe it was something else, dunno. I just bricked, but I be managed to recover
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
avatar_pt said:
Again, I followed the tutorial blindly for the flash
Maybe it was something else, dunno. I just bricked, but I be managed to recover
Click to expand...
Click to collapse
Then you didn't brick, bud. What exactly did it do? Why do you think it "bricked".
Sent from my EVO using Tapatalk 2
pl
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
please keep your mouth shut off if you don't know what to say.
YOU CAN FLASH UPDATE FILE FROM ASUS WEBSITE WITH TWRP AND THERE IS NOT BRICK IN HERE
******
here is what i just did to update my tab to 4.2.1
-was running cleanrom 3.4.4 with twrp 2.2.2.0
-downloaded twrp 2.4.4.0 and flashed it with fastboot
-download 4.2.1 update file from asus website=> unzip this file to get the real file ( apparently, asus just put the rom.zip file into a folder, then zip this folder again, kind a stupid here ^^)=> put it in my external micro sdcard
- boot into recovery=> flash the updated rom.
avatar_pt said:
Again, I followed the tutorial blindly for the flash
Maybe it was something else, dunno. I just bricked, but I be managed to recover
Click to expand...
Click to collapse
It wouldn't flash for me either. I used your method of flashing the blob, then followed the OP's directions for flashing TWRP using the fastboot/TWRP files he provided.
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
What i have done
I download the firmware from asus and renamed to xx_epad-user-10.6.1.8.zip
XX is the ww or US you must rename this in the directory what you extract
Example WW_epad-user-10.6.1.8.zip
US_epad-user-10.6.1.8.zip
Then put it in the root of your sd card or on your root on the tablet
Then you can update
And you can root follow this forum.
I am on 4.2.1 and rooted
Thank for all who have this made it
Thanks
Sent from my ASUS Transformer Pad TF300T using xda premium
Flash zip file from asus web site it really works!
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
I did flash my asus with the zip from asus web page with no issues, I used TWRP 2.4.3
I un-zipped the file (just one time and without change the name) and I placed the next zip file to my SD card root folder, then I made a full wipe and intall the zip file from SD card.
Right now my asus belong to my wife, my youngest son and I because I can create users.
I made a backup of my apps with the asus aplication and I could reinstall all them after the update.
AB
Good to go for me. TWRP recovery and rooted. Nice write up man.
You might add in there something about the new bootloader booting directly to fastboot now, no need to select the usb icon. Also maybe mention to make sure that the drivers get installed properly once you are in fastboot. When I booted to fastboot it had to install some drivers, so I waited for those to finish before I ran the fastboot command.
Installed TB and about to uninstall some bloat. Can't wait for roms to get updated.
Thanks again man.
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
Yes , it's true , i was bricked , too
could you help me how to unbrick ????????
thanks
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
I don't understand what your bricks are. Maybe you didn't wipe your tablet as you should? I updated to 4.1 and 4.2 via recovery and never had a problem.
I updated the topic with more info
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Related
Flashing ROMs/Mirror Links - Sending Files in CWM Via ADB! & Flashed TF201 Recovery?
I'm seeing alot of people are having issues with people loosing system images/soft bricking devices but its all avoidable!
If you download a Custom ROM also make sure you download the latest ASUS Stock ROM
{
"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"
}
If you create a folder on your internal SD called ROMs if anything happens you can always flashboot CWM and then you can use CWM to install new ROMS.
ROM MIRRORS: https://docs.google.com/folder/d/0B_7VIwxjudWvLUllSVpyUW9oSDQ/edit
At the moment we dont have mount via USB or external SD so if you loose access to your internal system you could be stuffed without these files.
Also make sure you create a CWM backup
Pushing files in Recovery via ADB
Step 1: Boot into recovery ( To access it, shutdown your tablet and press Power + Vol Down, then press Vol Up before the 5s timeout)
See Picture: https://docs.google.com/open?id=0B_7VIwxjudWvUWRJRmpOd3M4WFk
Step 2:Open Windows device manager and you will probably see https://docs.google.com/open?id=0B_7VIwxjudWvNUhOVWVmSDhjWjA Transformer device listed but not mounting in ADB Devices.
Step 3:Download the ASUS USB Drivers from https://docs.google.com/open?id=0B_7VIwxjudWvLTJuQnlZU1B1TVU and extract them to where you want.
Step 4: Watch this video to install the ADB Drivers https://docs.google.com/open?id=0B_7VIwxjudWvXzJmT09RZjlPdlE
Step 5: Using ADB "Adb Push c:\romfolder\rom.zip /sdcard" wait for it to finish then using recovery you should be able to flash it now.
Flashed TF201 Recovery in ROM Manager?
Follow these steps to recover your semi-bricked TF300T Tablet All the files you need are in the ROM Mirrors link. You need to make sure you have installed the drivers as above to be able to send recovery via Fastboot. You need our TF300T Recovery and the Asus Stock ROM.
Step 1: We need to flash our recovery onto the tablet. As you probably have already done this I have copied the info from http://forum.xda-developers.com/showthread.php?t=1668173 Thanks to XpLoDWilD for this!
Step-by-step guide
Unlock your bootloader with Asus Unlock app
Connect your tablet to your computer
Shutdown your tablet
Hold Power + Vol Down until a message appears ("Press Vol. Up to enter RCK (5s)") : DON'T PRESS VOL UP
After 5 seconds, a new menu appears. Press Vol Down once to change to the USB icon, then press Vol. Up to validate (you have to do this in less than 10 seconds, otherwise your tablet will boot Android OS)
At this point, your computer should recognize Fastboot device (Windows will notify you here, OSX/Linux stays calm)
Flash recovery image with fastboot: fastboot -i 0x0B05 flash recovery recovery.img (if we suppose recovery.img is in your current directory)
Once the operation is done, type fastboot -i 0x0B05 reboot to reboot your tablet
You now have CWM installed. To access it, shutdown your tablet and press Power + Vol Down, then press Vol Up before the 5s timeout. After a few seconds, you'll be in CWM interface.
Step 2:Repeat Steps 4-6 to boot back into Fastboot
Step 3:NB: If you have followed what I said about keeping Stock ROMs on the Internal SD Card just use CWM to reflash that and you are done! If not contiune with these steps
Now you need to have the Asus Stock ROM you want to flash, Extract the ZIP so you can see the BLOB file and take note of the location you have extract too! This is the file we will send via Fastboot. You can rename the file to update.blob so it follows the picture below and save into the directory you have your fastboot command.
At the command Prompt type fastboot -i 0x0B05 flash system update.blob
Step 4: fastboot -i 0x0B05 reboot
Picture https://docs.google.com/open?id=0B_7VIwxjudWveFlOVFdHT2ZjeHM
Special Thanks to XpLoDWilD for the Dev work and BlakeC90 for recovering his tablet through this brick. I copied the details for the thread below.
http://forum.xda-developers.com/showthread.php?t=1687015
Good idea to do this, thanks!
Great post, should be stickied. This will help the people new to flashing immensely.
Cheers guys, I've also uploaded some ROMs now.
I will Mirror the CM9 ROMs and will also mirror Stock ones
I have my tf300, acer a100 and my Samsung galaxy blaze all rooted, but have yet to flash a custom rom. if someone can just clarify something that would be awesome
a nandroid back is same thing as backing up current rom threw recovery?
to even get into recovery, do you have to unlock ur bootloader first? if so after you unlock it. will you still receive firmware updates threw Asus ota. If not, is all you do is wait till rom or build.prop gets updated with the same features and just update that way. if not, what the hell do you do then. kinda confused about that lol
lastly, this might be a stupid question but a custom rom is basically a tweaked
operating system. that has more features then HC or ICS. and all the good stuff like overclocking build in? am i missing any other major features. if im even on the right track in the first place lol
if anybody can help. will be appreciated
Trevor OBrion
trevor7428 said:
I have my tf300, acer a100 and my Samsung galaxy blaze all rooted, but have yet to flash a custom rom. if someone can just clarify something that would be awesome
a nandroid back is same thing as backing up current rom threw recovery? Yes
to even get into recovery, do you have to unlock ur bootloader first? if so after you unlock it. will you still receive firmware updates threw Asus ota. If not, is all you do is wait till rom or build.prop gets updated with the same features and just update that way. if not, what the hell do you do then. kinda confused about that lol If you device unlock then you wont get OTA updates, you need to manual install them or install custom ROM
lastly, this might be a stupid question but a custom rom is basically a tweaked
operating system. that has more features then HC or ICS. and all the good stuff like overclocking build in? am i missing any other major features. if im even on the right track in the first place lol
ROMs like CM9 are based off pure Google Code rather than all the tweak/bloatware that Asus put in and yes OC is possible with custom kernals
if anybody can help. will be appreciated
Trevor OBrion
Click to expand...
Click to collapse
See above
Unlock is a permanent voiding of your warranty as well.
Sent from my SCH-I510 using XDA
Updated to recover from Flashing TF201 Recovery
Thanks for the nice Thread.
What if the TF300T cannot boot into recovery?
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
Jake2kOne said:
Thanks for the nice Thread.
What if the TF300T cannot boot into recovery?
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
Click to expand...
Click to collapse
Can you get into the fastboot menu?
Step 1 of the TF201 recovery?
Nope. When pressing Power + Vol Down will directly show message above.
I think it's over, but maybe someone has an idea.
Jake2kOne said:
Nope. When pressing Power + Vol Down will directly show message above.
I think it's over, but maybe someone has an idea.
Click to expand...
Click to collapse
Just a thought if seems it looking for a stock image? So have you tried putting the ww.29 zip file on the external SD card and seeing if it picks it up?
Also see if it detects in Windows Device manager?
Oh, forgot to mention: It even won't boot up.
It boots neither Android, nor recovery.
No joke.
Jake2kOne said:
Oh, forgot to mention: It even won't boot up.
It boots neither Android, nor recovery.
No joke.
Click to expand...
Click to collapse
Yeah I don't mean into Android, if you put the ww.29 on a external card and boot it into
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
It might be looking for a firmware, last fail attempt recovery?
When its switched on in the above state does anything show in device manager?
Although its for the TF101 seems you are having the same issue http://forum.xda-developers.com/showthread.php?t=1622343 ?
It's not mine so I have to forward each idea.
Tried with the external SD card but didn't work. Too bad.
Tested with normal boot up (stucked on ASUS logo) and tested it with the recovery mode (or whatever it is called like...)
The link could be the same problem but has no solution.
Tomorrow UPS get the tf300.
The ASUS Bootloader Unlock Tool bricked it totally. Seems like to be the first device at all.
The User said he just used the tool, restarted, stucked. Really good.
Jake2kOne said:
It's not mine so I have to forward each idea.
Tried with the external SD card but didn't work. Too bad.
Tested with normal boot up (stucked on ASUS logo) and tested it with the recovery mode (or whatever it is called like...)
The link could be the same problem but has no solution.
Tomorrow UPS get the tf300.
The ASUS Bootloader Unlock Tool bricked it totally. Seems like to be the first device at all.
The User said he just used the tool, restarted, stucked. Really good.
Click to expand...
Click to collapse
Let us know how you get on with the warranty, if Asus reject it under its been unlocked or not.
All I have to say is I hope this works. I was dumb and was curious to see after installing sparky's stock rooted rom I selected factOry restore from the devices menu in settings. It erased all! Luckily I have my tiBU saved on my ext sd.
It's pushing virtuous now by using the \data media option
My experience in using the adb push method
everything went smoothly. I didnt back up everything properly the first time i flashed a rom so i had to push a rom on the transformer.
This is important and please add it on the first post. If the files you pushed on the device dont appear on it. Restart your computer and try again. (i didnt get any errors while pushing but i couldnt find the files on the device and i fixed it by restarting my pc and pushing them again)
ok, so im lost!.. lol
I have a soft brick, im trying to push a stock rom to my tab, but can not for the life of me get my tab to show up as a ADB. It will show as a Fastboot Interface, and if i go into recovery it just shows Transformer like in the pic in the original post. I have tried installing the driver just like the youtube vid shows, but its not working.
backstory is i tried to flash a new custom ROM over another custom ROM, i wiped my usual, cache, dalvik, and wiped system, to have a fresh install, but kept getting a broken ROM with the new one, and when i flashed back to my old one. i then clicked format internal data like a tard and wiped my entire SD Card.
Any advice you guys can give would be appreciated.
UPDATE: Ok i got ADB working (i think... lol) it shows in device manager, but im not getting anything when typing adb devices in cmd prompt. I also got fastboot to reboot the device but when i try to flash the update.blob i get.... error: cannot load 'update.blob'
If i use qtADB it will flash the recovery.img for some reason i just cant get it to wok when using the actual cmd prompt. (in cmd prompt i was getting the error cant load xxxx.blob or xxxx.img regardless of where ii placed the image or blob file on my computer)
Now you need to have the Asus Stock ROM you want to flash, Extract the ZIP so you can see the BLOB file and take note of the location you have extract too! This is the file we will send via Fastboot. You can rename the file to update.blob so it follows the picture below and save into the directory you have your fastboot command.
At the command Prompt type fastboot -i 0x0B05 flash system update.blob
Step 4: fastboot -i 0x0B05 reboot
I try this but i get this error
C:\Users\VaHiD\Desktop\Fastboot>fastboot -i
0x0b05 flash system blob
sending 'system' (799748 KB)...
OKAY [138.170s]
writing 'system'...
FAILED (remote: (InvalidSize))
finished. total time: 214.335s
what is the ((InvalidSize)) error?!
I try to install recovery twrp and cwm but do not install any .....
Can you help me?
So this thread started as just a guide for root but with all the questions being asked lately I have decided to turn it into a full blown info thread this is going to take some time and some section might be empty so please bare with me.
Device Variants
(this display is not 100% correct still working out some issues and info!)
XT1049 - Republic Wireless
XT1052 - European - Sim ?
XT1053 -T-Mobile US, Dev Ed
XT1055 - US Cellular - Sim ?
XT1056 - Sprint - Sim Unlocked
XT1058 - AT&T, Rogers, Claro, Movistar, Vivo, Oi, TIM - Sim Unlocked
XT1060 - Verizon - Sim Locked
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What Devices Can Unlock There Bootloader
In this section we are going to go over what devices can have there bootloader unlocked and what ones can't this is very simple.
(if it dose not says Dev Ed next to the carrier then I am talking about consumer model.
Locked Bootloader – Verizon, AT&T, Republic Wireless
Unlockable Bootloader – Sprint, US Cellular, T-Mobile, Rogers, all Dev editions
Personally these are the ones I am not sure about yet so if you have one please let me know so I can add them.
? - Claro, Movistar, Vivo, Oi, TIM
If you want to check to see if your device is unlockable please go to motorola's website below
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Downgrading Bootloader
there has been a lot of issues around this process so I want to post the info right at the top so people stop bricking there device and we can get past this
here is a quick list of what can be done with bootloader downgrading
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
here is a thread dedicated to the discussion of bootloaders and modems
http://forum.xda-developers.com/showthread.php?t=2635366
Informative Thread Google Cached
READ CAREFULLY
WARNING
DO NOT FLASH THE NEW 4.4.2 SBF FIRMWARE UNLESS YOUR CARRIERS FIRMWARE IS AVAILABLE.
FOLKS HAVE FLASHED OTHER CARRIERS FIRMWARE AND AS A RESULT THEY HAVE NO DATA CONNECTION,
YOU CAN NOT DOWNGRADE, SO IF THIS HAPPENS CHANCES ARE YOU'LL HAVE A PHONE THATS UNUSABLE UNTIL AND IF YOUR CARRIERS SBF SHOWS UP.
THERE IS A CHANCE THAT EVEN AFTER YOU FLASH THE CORRECT FIRMWARE, YOUR RADIO SIGNAL MAY NEVER WORK
I will not in any fashion help anyone to upgrade nor downgrade their moto, this thread is for info only. I personally will not take any responsibility for any issues. You own it ., you alone broke it
Motorola bootloader unlocking website https://motorola-global-portal.custh...-your-device-a
WARNING WARNING
DO NOT FLASH ANY OTA 4.4.2 ,OTA ROM OR ANY SUCH MEANS OF UPGRADING WITHOUT HAVING YOUR SPECIFIC CARRIER 4.4.2 SBF FIRMWARE AS A BACK UP
WARNING WARNING WARNING
IF YOU HAVE A LOCKED BOOTLOADER ONLY FLASH YOUR SPECIFIC CARRIERS SBF FIRMWARE, OTHERWISE YOU WILL END UP WITH A HARD BRICKED DEVICE
************************************************** ********
If you Frankenstein a way of downgrading do not post it here, this thread is not about tricks, hacks or any such garbage. This thread is to inform folks in the correct way of maintaining your moto to work. Plain and simple
There's a tremendous amount of firmware flashing which is causing harm to many users phones.
Realize that having a unlocked boot loader moto, regardless if its a DE will also suffer from hard bricks.
Unlocked boot loaders can flash other variants system.img's without to many issues
Modems are a different story, some user report no data with European modems, so I suggest using your specific carriers modems
Stay away from motoboot.img (boot loader) or gpt.bin(partition table) be warned
Remember you and you alone are responsible for any hard bricks
********************************
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr 
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
************************************************** **************
WARNING if you manage to flash back to 4.4 or even 4.2.2 with the new 4.4.2 BOOTLOADER DO NOT UNDER ANY CIRCUMSTANCE ACCEPT ANY OTA, YOU WILL HARD BRICK YOUR DEVICE, PROOF BELOW
Quote
******** "it was running on 4.4.2 software, then i downgrade to 4.2.2. all was fine, but OTA killed it.
So after that, i read that 4.4.2 instaled new bootloader =( that cant be downgraded, and can bricked the phone, it was my mistake =(
So i think i should sent it to Motorola and if i lucky one, they should repair it, or resend new one. or if bad luck i will throw it to the trash =)"*******
Files inside sbf firmware:
Motoboot.img (bootloader)
gpt.bin ( Partition table)
NON_HLOS (modem)
System
Recovery
Bootloaders:
4.4.2 North , Central & South America:
Rogers 30.B4
US Cellular 30.B4
Brazil Retail 30.B4
T-Mobile 30.B4
Sprint 30.B4
Europe:
UK 30.B3
Modems:
Rogers 4.4.2
Stock Recovery:
Rogers Stock Recovery 4.4.w
4.2.2 pre camera boot loader 30.70
4.2.2 post camera bootloader 30.71
Issues:,
Confirmed by Steve x , you can not downgrade bootloader from 4.4.2
WARNING WARNING
The Brazilian phone and central American phones will not have a data connection with the uk or DE firmware, so do not flash any European firmware, be warned
I will credit correct posters when i get back to my pc
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Recovery's
Now this is fairly simple there are 3 custom recovery options for us right now 2 for unlocked bootloaders and 1 for locked
here are the options we have and links to there threads for info and downloading
TWRP
http://techerrata.com/browse/twrp2/ghost
CWM
http://forum.xda-developers.com/showthread.php?t=2612149
Safestrap
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to Take OTA on Root Device
flashallthetime said:
Ok tired of answering thus question constantly
To accept and flash an ota you must have the following phone set up
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
If you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO
HOPE THIS HELPS
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Locked Bootloader
[SIZE="3"]Step one[/SIZE]
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
RockMyMoto(4.2.2 root exploit)
http://forum.xda-developers.com/attachment.php?attachmentid=2369524&d=1383521170
Cydia Impactor(Required for 4.2.2 root exploit)
http://www.cydiaimpactor.com/
MotoWpNoMo(Kill Write Protect on Locked Bootloaders)
Win - http://www.rumrunner.us/MotoWpNoMo-0.0.4.zip
Linux - http://www.rumrunner.us/MotoWpNoMo-0.0.4.tar
SlapMyMoto(4.4 Root exploit)
http://forum.xda-developers.com/attachment.php?attachmentid=2463879&d=1387477699
RSD Lite(Used for downgrading to 4.2.2 camera update)
https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
4.2.2 Camera Update Firmware(download firmware for your device)
http://forum.xda-developers.com/showthread.php?t=2568334
Below are Complete Kits that i put together for Each Carrier Moto X
it contains all the files needed to Root/Downgrade/Return To Stock or what ever you need to do.
I will be posting Links as i upload them.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step two
Downgrade to 4.2.2 Camera Update
If you are on the 4.4 update already your are going to have to downgrade your device to 4.2.2 camera update. The best way to do this is to follow the guide in the link below.
Ok so more and more people are Bricking there phone with RSD Lite so i am going to add in the guide to manually flash all the img's because i no longer will refer to RSD Lite for the fact that i dont find it safe anymore.
To Flash back to 4.2.2 Camera Update Manually Follow the Below Steps it is very simple.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
Now it is time to move on to Step three and root your device
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Three
Rooting 4.2.2 camera update and disabling write protection
Before you can start to root 4.4 you first need to root 4.2.2 camera update and disable write protection. below are two links the first one is to root 4.2.2 camera update and the second one is for disabling write protection
4.2.2 Camera Root Exploit
http://forum.xda-developers.com/showthread.php?t=2509590
Disable Write Protection
http://forum.xda-developers.com/showthread.php?t=2551113
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Four
Returning back to stock again so you can start rooting 4.4
i know you have already done this but in order to root 4.4 you have to be completely stock. So use the same guide and firmware as the last time to restore your device to stock again i no longer will recommend RSD Lite so below is the steps to manually flash your device back to stock
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Five
Root 4.4 Finally
Now that we are back to 4.2.2 camera update it is finally time to start the process to root 4.4 just follow the guide below and you will finally have your device on 4.4 with Root
4.4 Root Guide
http://forum.xda-developers.com/showthread.php?t=2538896
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How To Unlock Your Bootloader
Unlock your Bootloader
This Will Erase your Data/ Factory Reset your phone
In order to install TWRP/CWM and SuperSU you need to first unlocked your boot loader. below is a link to Motorola's guide to do just that.
Click on the link below and pick your Moto X by what carrier you are with
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215/action/auth
im going to try and do this the best i can but no matter what i do your going to have to go to the moto website to get the unlock key
download the SDK and install it.
locate ware it was installed normally (C:\Program Files\Android\android-sdk)
open Command Prompt and type
Code:
CD C:\Program Files\Android\android-sdk\platform-tools
put phone into bootloader
type below commands in CMD
type
Code:
fastboot oem get_unlock_data
it should come back with something like this
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Now we need to remove all the (bootloader) and make the key into one line
we then need to paste this into the box on the bottom of the Moto unlock page and hit the button "Can my Device be Unlocked"
if your device can be unlocked you need to accept the license agreement and then click the button to request your key. It will then email you your unlock key.
Copy your unlock key then click the link Step 3
now if you left your device connected and everything ware it was then great if not we need to put are phone back into bootloader and open a CMD and CD it to the same directory as before.
then type
Code:
fastboot oem unlock UNIQUE_KEY
ware Unique_key being the code you copied from your email.
now your bootloader is unlocked.
Sorry this guide is not great but it is the best i can do for the fact that you have to be on the moto website to get your unlock key. i hope this helps somewhat.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Unlocked Bootloader
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
TWRP Recovery
http://techerrata.com/browse/twrp2/ghost
CWM Recovery
http://forum.xda-developers.com/showthread.php?t=2612149
SuperSU
http://download.chainfire.eu/supersu
MFastboot(Used for flashing TWRP)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
How to install TWRP/CWM Recovery and SuperSU
Now that you have your bootloader unlocked its time to install are custom recovery and SuperSU so we have Root
Before we worry about that phone please make sure you have installed the SDK and then copied the mfastboot files over to the directory your ADB is in.
also before we put the phone into bootloader mode we need to copy the SuperSU.zip over to are phone
Now that we have all that moved over everything that we need. it is time to get are phone into the bootloader you can do that by turning off your phone, Then turning it back on while holding volume down + the power button.
once into the bootloader plug your USB cable in and set your phone down.
now we need to open a CMD window and CD to the directory ware we placed the MFastBoot files.
this is my location but i use the Moto X toolkit yours is going to be ware ever you install the SDK
so in the CMD window type the command below but change the path to ware your files are located
Code:
CD C:\Program Files\stillthisguy\Moto X Toolkit
now that we are in the right location it is time to install TWRP/CWM we are going to do that by typeing the commands below
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
or what ever the name of your recovery img is
as soon as you type the above command to flash TWRP/CWM we need to boot the phone into recovery before we let it boot to android we can do that via the buttons below.
click the Volume - button until it highlights Recovery then press the Volume + button to select it and it should boot into recovery.
If you do not immediately boot your phone into recovery after you flash it, recovery wont work.
here is a step by step that might help everyone abit
Cozume said:
Try this:
1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If that doesn't work, repeat but omit step 4.
Click to expand...
Click to collapse
Now click on Install and find your SuperSU.zip that we copied over and click on it and install it. when it is done installing you can reboot your phone and enjoy having root access.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download pick what firmware you want from the link below
http://sbf.droid-developers.org/phone.php?device=0
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Full OTG support on 4.4.2 or older builds via Qualcomm settings
aviwdoowks ask for me to include his guide in my post so here yall go if you need support the link below is to the original thread
OP Thread
Update
This is, at least, a stock/rootless solution. The OTG/UsbDisk is now system wide! /storage/UsbDisk! Root Explorer/Explorer (free)! The standard issue "Documents" apk browses it too.
{
"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"
}
You may use many apps to browse your new /storage/UsbDisk, this is a good one.
https://play.google.com/store/apps/details?id=fm.clean
You need to create a shortcut to qualcomm settings.
The: com.qualcomm.qualcommsettings.apk is in your system/app!
I posted it for custom rom users, but it will not show up even if you install it.
I use Super Manager donation. The free version works too. (apk manager, choose activity button. The gear: launches the activity, the arrow creates a shortcut on homescreen.). I use Xperia launcher.
Then enable usb mass storage and OTG mode - peripheral. The usb will get reset but there is no need to keep it on. OTG mode sticks. Edit: try it w/o the usb checked it may not be needed at all.
Done.
Go File manager, /storage. Permissions will be rwx even from the free version.
You have a new mount/unmount option in settings/storage:
Be sure to use (^ above button) the unmount command as forgetting you have a write operation in progress and yanking out the otg adapter can trash your SD card!
I do not wonder why Moto did not enable this ability!
No need to download the attached apk. It is in your system apps already. But some custom ROMs may not have it.
USEonlyIFnotONyourPHONE.4.4.2com.qualcomm.qualcommsettings.apk
USEonlyIFnotONyourPHONE4.4.0.com.qualcomm.qualcommsettings.apk
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Credits
jcase
beaups
TechSavvy2
zhp pilot
Hashcode
Phil3759
flashallthetime
aviwdoowks
if i forgot anyone please let me know
Nice guide! First to reply, lucky!
Sent from my XT1058 using Tapatalk
I guess it would be nice to add the root tutorial for unlocked bootloader, even though it's a quick process. Some people might have little worry about voiding warranty.
Sent from my Moto X
RenSoAbrupt said:
I guess it would be nice to add the root tutorial for unlocked bootloader, even though it's a quick process. Some people might have little worry about voiding warranty.
Sent from my Moto X
Click to expand...
Click to collapse
ok sounds good i will add it
guide for unlocked Bootloaders has been added i think i got everything right lol. please let me know if there are any error's or is i am missing anything. enjoy
Thanks much for this.
Wish things were a lot more straight forward though.
Sorry but I'm not going to grab someone's guide and remake it most of the guides I linked to the creator has done a very good job with them so I want them to get the credit for it
Sent from my XT1056 using XDA Premium 4 mobile app
Yes! This is exactly what I needed. I had the jist of what needed to be done, but had trouble wrapping my head around the correct order of all the different steps. When a root process requires links to 10 different guides, you really need a Master guide like this. Thanks
Sent from my Nexus 7
No problem man glade it helped
Sent from my XT1056 using XDA Premium 4 mobile app
dray_jr said:
No problem man glade it helped
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have botloader unlocked
i flashed recovery
///solved to get into recovery
when i boot into recovery says no comands
danger2u said:
i have botloader unlocked
i flashed recovery
///solved to get into recovery
when i boot into recovery says no comands
Click to expand...
Click to collapse
i answered your question in your thread in Q and A
TWRP problem...
So I flashed TWRP to my phone. The flash went through fine, but when I tried to boot into recover it just comes up with the No Command error. Any thoughts?
AceBearpaws said:
So I flashed TWRP to my phone. The flash went through fine, but when I tried to boot into recover it just comes up with the No Command error. Any thoughts?
Click to expand...
Click to collapse
Yes this is a very common problem and i am going to edit the OP to try and make sure people dont make this mistake.
ok this is a simple fix
1.boot you phone into bootloader
2. CD adb to the folder with your recovery in it
3. re run the fastboot flash recovery imagename.img
4. do not boot your phone into android
5. right after your phone flashes TWRP type adb reboot recovery
6.it should boot right into recovery this time
for some reason after your flash TWRP you have to immediately boot your phone into recovery before you allow youe device to boot into android or you will have this issue.
Thanks! I'll give it a shot tonight!
---------- Post added at 12:40 PM ---------- Previous post was at 12:09 PM ----------
easting said:
Thanks! I'll give it a shot tonight!
Click to expand...
Click to collapse
Anyone try on XT1060 (VZW)?
I've got a problem hopefully you can help.
I've unlocked my bootloader via the moto website and getting the warning when I restart to say the bootloader is unlocked. I seem to be installing the recovery ok but when I typing adb reboot recovery I'm getting error: device not found.
When I have my phone turned on and I type adb devices it lists my phone. When I'm in fastboot and type adb devices my computer doesn't find my phone.
Do you have any ideas?
Thanks!
dray_jr said:
Yes this is a very common problem and i am going to edit the OP to try and make sure people dont make this mistake.
ok this is a simple fix
1.boot you phone into bootloader
2. CD adb to the folder with your recovery in it
3. re run the fastboot flash recovery imagename.img
4. do not boot your phone into android
5. right after your phone flashes TWRP type adb reboot recovery
6.it should boot right into recovery this time
for some reason after your flash TWRP you have to immediately boot your phone into recovery before you allow youe device to boot into android or you will have this issue.
Click to expand...
Click to collapse
Yeah I actually tracked down your post on another thread, and got it all fixed.
Though I will say this, once I flashed when I typed in adb reboot recovery it said it could not find my device for some reason. If this happens to anyone else you can still get recovery to work as described above with one small difference. It seems the moto x has a tendency to turn right back on the second you turn it off from fastboot. If you are ready for it you can quickly hit power + volume down quickly before it has a chance to boot, and it will get you back into fastboot and the recovery image will work from there.
Thanks!
~ Ace
AceBearpaws said:
Yeah I actually tracked down your post on another thread, and got it all fixed.
Though I will say this, once I flashed when I typed in adb reboot recovery it said it could not find my device for some reason. If this happens to anyone else you can still get recovery to work as described above with one small difference. It seems the moto x has a tendency to turn right back on the second you turn it off from fastboot. If you are ready for it you can quickly hit power + volume down quickly before it has a chance to boot, and it will get you back into fastboot and the recovery image will work from there.
Thanks!
~ Ace
Click to expand...
Click to collapse
Hi Ace
When you are in bootloader does adb reboot recovery work at all for you? How did you get it to reboot into recovery. I just tried flashing the recovery, restarting straight into bootloader and still cant use adb reboot recovery and selecting recovery boots android and starts the phone.
matust said:
Hi Ace
When you are in bootloader does adb reboot recovery work at all for you? How did you get it to reboot into recovery. I just tried flashing the recovery, restarting straight into bootloader and still cant use adb reboot recovery and selecting recovery boots android and starts the phone.
Click to expand...
Click to collapse
I would try reflashing the recovery one more time sounds like something went wrong
Sent from my XT1056 using XDA Premium 4 mobile app
When I flash 4.2.2 (camera update) to downgrade, the device gets stuck at boot splash. Typically with other devices I've owned, this is a sign of a bad kernel flash or an incompatible kernel. Though I've run through multiple times and get the same issue every time.
VZW locked bootloader.
Flashing using mfastboot for Linux.
Bootloader and terminal show successful data transfer and flash on all partitions.
Boot splash just shows the "M" logo without "a Google company" written underneath.
Flashing back to 4.4 yields no issues.
Any thoughts?
Sent from my XT1060 using Tapatalk
dray_jr said:
I would try reflashing the recovery one more time sounds like something went wrong
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've flashed the recovery several times before trying to reboot into recovery and it still isn't working. When I flash the recovery I get the acknowledgement on the command line and the phone. So I think the recovery is flashing. I have set up adb on another computer to try again and its not working either.
When my phone is in fastboot if I type adb devices I get error: no device found. If I type fastboot devices my phone shows up. Any other ideas? This is frustrating me to no ends!
---------- Post added at 08:23 AM ---------- Previous post was at 07:44 AM ----------
After doing some more googling it looks like adb commands won't work when your in fastboot. adb commands only work while the phone is on or in recovery. This sounds like why adb devices won't list the device and why adb reboot recovery won't reboot it to recovery
Ok I now have TWRP installed...yay
There may have been a problem with my firmware from the 4.4 OTA that was stopping me from installing twrp. I reinstalled the stock moto firmware using method 2 from here http://forum.xda-developers.com/showthread.php?t=2446515
I then followed the guide from this thread and installed TWRP with the exception that adb reboot recovery doesn't work in fastboot and did as Ace said and rebooted straight to fastboot and selected recovery from there.
Happy days
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"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"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.
eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....
Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...
Very useful guide, I revived my soft - bricked Moto G
still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks
My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom
I solved this issue with twrp sideload.It worked great.
Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error
When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .
Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip
Where do i put the command in the 4th step?
Please help
Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"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"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.
Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess
I could try today evening... will update here.
@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..
Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!
Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.
@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Warning
Before Proceeding backup your data
TRY at OWN risk I'm NOT Responsibe if you BRICK YOUR DEVICE
Update- This method is tested & working with latest ota update NMB26.54-74
[/CENTER][/B][/SIZE][/COLOR]
IF ANYTHING GOES WRONG Download & Flash Stock ROM
Stock ROM link
SPFlashTool link
Updated Stock ROM 54-74 GDrive - here
New Oreo 27.43-20 Link
Old version Stock ROM Google Drive Link Stock Rom
nvram backup file by @peacelover94 - here
Solution For
>Tool img DL fail
Just check/tick these option in spflashtool settings & Flash stock rom again
{
"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"
}
Video Guide For Stock Rom Flashing - Youtube
How to Flash Stock Rom via Fastboot Method -
1. Open CMD by Shift + Right Click in Folder where your stock firmware .img files are.
2. Reboot to Fastboot Mode by using cmd command
adb fastboot rebootOr
Switch off then Press & Hold Vol Up + Power button for while once menu appeared Select fastboot by using Vol Up key & confirm by pressing Vol Down Key
3. In fastboot type following command in CMD Window
For checking devices is connected in fastboot enter
fastboot devicesIf Connected then proceed following commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img flashing system takes 10+ mins
fastboot flash data userdata.img
fastboot reboot
Download & Install ADB from here
First Unlock your bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Now connect your phone to Computer using USB Cable.
4. When you connect your Phone to Computer, please wait until all the drivers get installed.
5. Open a command prompt window by pressing Shift Key + Right Mouse Click.
6. Now type the command below to reboot your phone to bootloader
adb reboot bootloader7. If you see a pop up to allow USB Debugging on your phone, Click OK.
8. proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
fastboot oem unlockSay Yes to unlock bootloader and then it will some time format your data
9. Reboot Your Device , You will see Orange Status bla bla bla Don't panic Its normal thing now setup your device but do not restore backup yet
Flashing TWRP and ROOT
Updated Black Screen Fix TWRP - Download
Old Download TWRP
Download latest Magisk zip from here
Or
SuperSu zip from here
Flahed & Tested SuperSU v2.82 works fine but SafetyNet Fails
Sock Recovery if needed Link
1. Connect your device to PC
2. Open CMD by Shift+Right click open cmd where your TWRP_3.1.1.0.img is downloaded.
3. Reboot to Bootloader by
adb reboot bootloader4. Now enter following command in fastboot
fastboot flash recovery TWRP_3.1.1.0.img5. DO NOT USE fastboot reboot
Use "vol up + down + power button" to manually switch off you k8 note, otherwise twrp will restore to stock if you use fastboot reboot command.
6. After Switch Off Press & hold vol up + power button then select recovery by vol up & press vol down key to enter in recovery.
7. Now Wait for 30 Sec/ till phone vibrates, Then press power button + vol up simultaneously until you see twrp lock screen.
8. Just Cancel if It asks for Enter password to decrypt and Allow modification by swipe.
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
10. GoTo install browse and select Magisk.zip or SuperSU.zip & flash.(optional if needed install Busybox for Android NDK by osm0sis magisk module for busybox)
11. Reboot Enjoy.
Known bug in TWRP-
Battery always shows 50% in TWRP
Video Guide https://youtu.be/HrbppEWlOhs
Join Lenovo K8 Note Development Group on Telegram for direct Conversation Link
WhatsApp Group Link
Enable Wireless Display/MiraCast Magisk Module - Video
Thanks to:
@andy_zhang - for stock rom post link
and me @ysalunke007 for TWRP
NEXT CUSTOM ROM
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Yes
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
ysalunke007 said:
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
Click to expand...
Click to collapse
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
flash via adb fastboot methoad i have succesfully flash adb method
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
Nice Job
Finally rooting tutorial for Lenovo K8 Note has become available.
Does SuperSu work fine?
Anas Rahman said:
Does SuperSu work fine?
Click to expand...
Click to collapse
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
peacelover94 said:
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
Click to expand...
Click to collapse
Yes it's SP flash tool but you can use adb fastboot also
ysalunke007 said:
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
Click to expand...
Click to collapse
I'll confirm it tomorrow
ysalunke007 said:
Yes it's SP flash tool but you can use adb fastboot also
Click to expand...
Click to collapse
Please tell me how to flash firmware.Im new to this device firmware flashing
lenrussel said:
Please tell me how to flash firmware.Im new to this device firmware flashing
Click to expand...
Click to collapse
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
peacelover94 said:
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
Click to expand...
Click to collapse
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
lenrussel said:
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
Click to expand...
Click to collapse
Thanks for the reply. Anyhow got a work around for downloading from baidu using chrome extension, without account. Just wanted to confirm whether the firmware zip is working fine. If some one used it and been successful, please do tell me.
ysalunke007 said:
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Click to expand...
Click to collapse
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
peacelover94 said:
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
Click to expand...
Click to collapse
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
No need to unlock bootloader again if you use fastboot method to flash stock firmware , & for spflashtool I'm not sure but I think it remains unlocked
lenrussel said:
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
Click to expand...
Click to collapse
No error while extracting firmware downloaded from baidu