Database Users

[GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices

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

Unbrick method.

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

Zenfone A501CG Camera not found / Black Screen

Hi guys, do you find other methods to fix this problem? I didn't nothing, just the phone updated itself and camera started to say "not found" with black screen.
I tried to back in stock rom WW-2.21.40.30 (possible fix method), now it don't says nothing but the screen still remains black, when i change to front camera it crashes.
{
"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"
}
Picture is not me, just found in google with same problem.
Asus update did this and i can't send my phone to them, so my camera is gone?

Blak3n said:
Hi guys, do you find other methods to fix this problem? I didn't nothing, just the phone updated itself and camera started to say "not found" with black screen.
I tried to back in stock rom WW-2.21.40.30 (possible fix method), now it don't says nothing but the screen still remains black, when i change to front camera it crashes.
Picture is not me, just found in google with same problem.
Asus update did this and i can't send my phone to them, so my camera is gone?
Click to expand...
Click to collapse
Is your phone rooted?
it's happen to me too, my camera gone blank/missing/not found
for me it's happen after i install TWRP, doesn't matter what TWRP version i install,
but it's can be fix.
drive.google.com/folderview?id=0B5XJj7Sujx-DWmhoY1N4UzNsblE&usp=sharing (its my first time posting so i can't post url copy it to browser)
This is the fix data on my google drive, it's for to use with WW-3.24.40.87
the problem is if you got TWRP installed, after fixing you got your camera back but you lose the TWRP.

Downgrade to KK 2.22.40.54 and follow this, http://forum.xda-developers.com/zenfone-5/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704 or this for non-Linux, https://github.com/sigo/asus-zenfone-5-root/blob/master/README.md#usage-for-other-systems

jephimax said:
Downgrade to KK 2.22.40.54 and follow this, http://forum.xda-developers.com/zenfone-5/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704 or this for non-Linux, https://github.com/sigo/asus-zenfone-5-root/blob/master/README.md#usage-for-other-systems
Click to expand...
Click to collapse
Thanks but i tried and nothing changed

FairuzOnn said:
Is your phone rooted?
it's happen to me too, my camera gone blank/missing/not found
for me it's happen after i install TWRP, doesn't matter what TWRP version i install,
but it's can be fix.
drive.google.com/folderview?id=0B5XJj7Sujx-DWmhoY1N4UzNsblE&usp=sharing (its my first time posting so i can't post url copy it to browser)
This is the fix data on my google drive, it's for to use with WW-3.24.40.87
the problem is if you got TWRP installed, after fixing you got your camera back but you lose the TWRP.
Click to expand...
Click to collapse
Thanks for write your first post to solve my problem
Story of my asus: the phone was working properly, once it fell and the glass broke so I waited for the new glass and when I repaired it, the camera was not working anymore. I tried to reconnect and everything but nothing, the only cause can be an update before or after as has happened to many.
I'll try your method as last chance on software issue because i never flashed in .87, if it doesn't works i'll buy a new camera and lets see. I tried every software fix in the web, maybe it really broke when it fell.

It happens when u unlock ur bootloader
@Blak3n.........I had this issue several times. It's nothing serious and happens when u unlock ur bootloader to flash any custom recovery. This is the only fix if you face the "NO CAMERA" issue for unocking.
Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. You must start with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip to get ur camera working. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Reboot ur device. Your camera should work.
14. Now upgrade to lollipop following the version I mention sequentially. Otherwise it will fail. Just copy them to ur SD card and disconnect USB cable. your phone will automatically detect the update. no need to flash anything in fastboot.
>> UL-ASUS_T00F-WW-2.21.40.30-user
>> UL-ASUS_T00F-WW-2.22.40.54-user
>> UL-ASUS_T00F-WW-3.24.40.78-user
>> UL-ASUS_T00F-WW-3.24.40.87-user
15. if it works hit thanks
I did a lot of research on it but no luck. there few Zen5 devices where u can't unlock the bootloader. I'm also a victim. For better understanding: http://forum.xda-developers.com/showpost.php?p=66307220&postcount=16
Good luck.

a8962383 said:
@Blak3n.........I had this issue several times. It's nothing serious and happens when u unlock ur bootloader to flash any custom recovery. This is the only fix if you face the "NO CAMERA" issue for unocking.
Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. You must start with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip to get ur camera working. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Reboot ur device. Your camera should work.
14. Now upgrade to lollipop following the version I mention sequentially. Otherwise it will fail. Just copy them to ur SD card and disconnect USB cable. your phone will automatically detect the update. no need to flash anything in fastboot.
>> UL-ASUS_T00F-WW-2.21.40.30-user
>> UL-ASUS_T00F-WW-2.22.40.54-user
>> UL-ASUS_T00F-WW-3.24.40.78-user
>> UL-ASUS_T00F-WW-3.24.40.87-user
15. if it works hit thanks
I did a lot of research on it but no luck. there few Zen5 devices where u can't unlock the bootloader. I'm also a victim. For better understanding: http://forum.xda-developers.com/showpost.php?p=66307220&postcount=16
Good luck.
Click to expand...
Click to collapse
I know, right? Why TF does A**-US need to do s#!t like mess-up the motherboards of every 5th ZenFone 5, WTF. I'm stuck in these suckly stock ROMs while others are enjoying the feature-rich environment of the custom ROM community. Well, done A**-US. If I wanted "unhackable", I'd buy an iPhone.

cnswico said:
I know, right? Why TF does A**-US need to do s#!t like mess-up the motherboards of every 5th ZenFone 5, WTF. I'm stuck in these suckly stock ROMs while others are enjoying the feature-rich environment of the custom ROM community. Well, done A**-US. If I wanted "unhackable", I'd buy an iPhone.
Click to expand...
Click to collapse
You can flash custom rom but can't ensure your camera will be working as before. I have no camera issue but to me, taking snap is less important and I'm using RR rom with the camera bug. I'm fine with that. The camera is black/dark but it captures photos at least.

a8962383 said:
You can flash custom rom but can't ensure your camera will be working as before. I have no camera issue but to me, taking snap is less important and I'm using RR rom with the camera bug. I'm fine with that. The camera is black/dark but it captures photos at least.
Click to expand...
Click to collapse
Naw. mine doesn't lose its camera when the bootloader is unlocked. I'm one of the owners of a ZenFone 5 that freezes/hangs then restarts randomly. Those are the only issues that affect the ZF5 users with their defective motherboards.

cnswico said:
Naw. mine doesn't lose its camera when the bootloader is unlocked. I'm one of the owners of a ZenFone 5 that freezes/hangs then restarts randomly. Those are the only issues that affect the ZF5 users with their defective motherboards.
Click to expand...
Click to collapse
Bro, there are no defects on the motherboard. It's because of the unlocked bootloader. If you want to unlock it properly, then check it out: http://forum.xda-developers.com/showthread.php?t=3389883
Sent from my ASUS_T00F using XDA-Developers mobile app

a8962383 said:
Bro, there are no defects on the motherboard. It's because of the unlocked bootloader. If you want to unlock it properly, then check it out: http://forum.xda-developers.com/showthread.php?t=3389883
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
A'right, mate! I'll give this a shot. I'll notify you via your post regarding the results.

a8962383 said:
Bro, there are no defects on the motherboard. It's because of the unlocked bootloader. If you want to unlock it properly, then check it out: http://forum.xda-developers.com/showthread.php?t=3389883
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, still it doesn't work. I've tried every single method regarding that here on XDA. I've even tried those from EDA, Windroidica, and InfoBros. They all don't work.
The only method that managed to make a difference is ozank's automated script. It didn't completely stop the freezes, but I noticed that the reboots are a whole lot less frequent:
NO METHOD/OTHER METHODS - freezes about every 3 minutes. A few seconds when using any app.
ozank's AUTO-SCRIPT - freezes about every 20 - 30 minutes ONLY WHEN USING APPS. Haven't encountered the freezes when the device is on standby or daydream mode.

cnswico said:
Well, still it doesn't work. I've tried every single method regarding that here on XDA. I've even tried those from EDA, Windroidica, and InfoBros. They all don't work.
Click to expand...
Click to collapse
It's been 10days for me. no freeze/reboot so far.

a8962383 said:
It's been 10days for me. no freeze/reboot so far.
Click to expand...
Click to collapse
I'm glad to hear that some have managed to fix it. But as for me, and maybe some others, we'll just have to lay in the dust until a savior picks us up. (no religion, okay? )
Either that, or I'm switching phones.

CM 13.1
Hi.. I flashed CM 13.1 latest stable build on asus Zenfone 5 (T00F). I am facing the same camera issue. Is there any fix for this camera Issue other than Downgrade?Is there any change that can be done to system/framework/bspcapability.jar in order to make it work?
Thanks in advance.

Blak3n said:
Hi guys, do you find other methods to fix this problem? I didn't nothing, just the phone updated itself and camera started to say "not found" with black screen.
I tried to back in stock rom WW-2.21.40.30 (possible fix method), now it don't says nothing but the screen still remains black, when i change to front camera it crashes.
Picture is not me, just found in google with same problem.
Asus update did this and i can't send my phone to them, so my camera is gone?
Click to expand...
Click to collapse
Dear all;
I find a solution for this error..
İf you have only black screen from back camera and th front camera has been stopped error pls read this steps..
1.. download ZenfoneAssist
I cant give you a link for zenfone assist because of the site rules (10 posts). but you can google zenfoneassist. and download from XDA..
2.Run as administrator..
3. RELOCK YoUR BOOTLOADER. wait a little minute while the ifwi and dnx files has been downloading..
4.Program says you what will you do. open droidboot menu and pls wait.
5. phone will restart and you will use your camera immediatly..
For more questions pls write me "[email protected]"
PS: the program is quotation but I tried and worked my camera..
Sorry for my english..

a8962383 said:
@Blak3n.........I had this issue several times. It's nothing serious and happens when u unlock ur bootloader to flash any custom recovery. This is the only fix if you face the "NO CAMERA" issue for unocking.
Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. You must start with this version UL-ASUS_T00F-WW-2.21.40.30-user.zip to get ur camera working. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Reboot ur device. Your camera should work.
Click to expand...
Click to collapse
I did this (more specifically "asus-zenfone.com/2015/08/how-to-fix-unfortunetely-camera-not-found-zenfone.html") and returned to stock room UL-ASUS_T00F-WW-2.21.40.30 And the camera still does not work.
Has anyone found any other solution?

niquelfer said:
I did this (more specifically "asus-zenfone.com/2015/08/how-to-fix-unfortunetely-camera-not-found-zenfone.html") and returned to stock room UL-ASUS_T00F-WW-2.21.40.30 And the camera still does not work.
Has anyone found any other solution?
Click to expand...
Click to collapse
The URL you have given, won't work. It didn't work for me as well. Seems like you didn't try my steps but you are quoting me. Would please try/retry the steps again and report it here?

a8962383 said:
The URL you have given, won't work. It didn't work for me as well. Seems like you didn't try my steps but you are quoting me. Would please try/retry the steps again and report it here?
Click to expand...
Click to collapse
Okay, I tried your steps. The problem remains the same.
This time I used the fastboot.img, boot.img, recovery.img files from the room as you suggested in step 5 and not the same files from de url.

niquelfer said:
Okay, I tried your steps. The problem remains the same.
This time I used the fastboot.img, boot.img, recovery.img files from the room as you suggested in step 5 and not the same files from de url.
Click to expand...
Click to collapse
Did you somehow kept your bootloader unlocked? There are few devices (mine as well) where the camera doesn't work if you unlock bootloader. If you port any custom ROM, you have to sacrifice your camera and vice-versa. Please relock the bootloader with a signed boot.img, fastboot.img, and recovery.img.

[HOW-TO][ROOT][Unlock BL] Sony Xperia Z3 Tablet Compact

/*
* Your warranty is (probably) now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about rooting
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* PLEASE READ THE ENTIRE THREAD BEFORE YOU DO ANYTHING!
*/
Please leave a reply if this worked or didn't work. I will be most grateful! Thanks
Hi there!
I present the best, the easiest (mm maybe not) and most proper way to root and flash a custom ROM on your Sony Xperia Z3 Tablet Compact!
Requirements:
- A basic understanding of Rooting and Android Development
- ADB and Fastboot (Have a google for Minimal ADB And Fastboot)
- A windows PC (I am not sure how to root with mac, although I am sure it is the same process)
- OEM Unlocking Enabled on your Device.
Don't know how to enable OEM Unlocking? Do this:
Settings -> About Device -> Tap Build Number 7 Times - Back -> Developer Options -> OEM Unlocking -> Enable
Also, if you ever get a message saying: Allow USB Debugging, do this:
{
"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"
}
We'll start with Unlocking your Boot loader. I might as well point out that this will remove ***ALL*** of your apps and files etc. I should also say that you will lose some capability features - such as the Camera may not be as good - although to be perfectly honest I haven't noticed any changes!
Lets start right away: Bootloader
What is your Bootloader?
Your bootloader is a part of your android device that when unlocked, allows you to do lots of things with it! This includes rooting (Like we are now :laugh, flashing recoveries and more.
Is it safe to do this?
As long as you follow my steps, you should be ok. But I have warned you.
Now head to here. This is the official Bootloader unlocking page. Scroll down to the device selection and put in "Z3 Tablet Compact"
Connect your tablet to your compter,
Do the steps it asks and... done!
Congratulations, your Bootloader is Unlocked!
It may seem silly, but for me, this is the only Hard part!
Now let's flash our TWRP!
Before you do this, make sure you have booted after unlocking your Bootloader. I dont know if it will make a huge difference, but I did it, so you should as well. It worked for me like that
What is TWRP
TWRP is a Custom Recovery
Wow, helpful. :laugh: What's a custom recovery?
As android central say:
In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. A combination of key presses (or instructions from a command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install official OS updates.
This means it is a way of changing things that you can't change if you are booted into System (System is Usual Home screen etc...)
Is TWRP Safe?
It's only ever as safe as you are! - Just make sure you flash (install) the right version!
We start by flashing TWRP.
Head to http://twrp.me and click on Devices. Find specifically YOUR version if the Tablet (scorpion_windy is the NON-LTE Version).
Download it.
Drag that file into an empty folder. Then in the address bar, type "cmd"
A black window should pop up.
In this window, type: adb devices
This should display your device.
Now type: adb reboot bootloader
You should now have a blue light on your device.
You cannot perform adb commands anymore! You now are in Fastboot mode. I dont need to explain that, but you need to know that!
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Congratulations, TWRP Recovery is now Flashed!
(Provided it says everything is ok. )
Our last step is rooting This is an easy task, but requires TWRP - hence why we installed it.
Grab the latest copy of SuperSU from supersu.com - make sure you get the XPERIA SuperSu - and boot into twrp. (Booting into twrp can be done by mashing volume keys after holding down the power key and it vibrates haha). Press install and find your copy of SuperSU (which you should have loaded onto your tablet beforehand). Swipe to flash, and done!
If your tablet bootloops (doesn't turn on), Install a custom rom. I am currently using: this unofficial lineage (14.1).
To do this, boot into TWRP and press install. Find your Rom file (Like you did for Rooting) and swipe to flash. (Make sure you wipe data, system, cache and dalvik beforehand!). You can now reflash your SuperSU Zip and bam, rooted.
You may also want GApps (Google Apps). So head to opengapps.org and select the right package for you. When you flash GApps, make sure you do right after you flashed the rom (dont boot after flashing your rom.)
When I am flashing something I will normally do this:
TWRP -> Wipe -> Advanced Wipe -> System, Cache, Data, Dalvik Cache -> Back -> Install -> ROM -> Add more Zips -> GApps -> SuperSU -> Back -> Reboot -> Reboot system.
Hopefully, you should now be rooted with a custom rom and all. Enjoy!
I should point out that (At the time of writing this) I am only 12 years old. If I have made a few mistakes, please correct me! Thank you

MajorPlayz said:
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Click to expand...
Click to collapse
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.​...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.

XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me

XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
What's 291 sorry?

MajorPlayz said:
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me
Click to expand...
Click to collapse
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
MajorPlayz said:
What's 291 sorry?
Click to expand...
Click to collapse
The FW version.

XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
Ok cool

XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
I may be mistaken though, so if it bricks the device, use Sony's Emma flash tool
It's a pretty useful tool (if you don't have just Google: Sony Emma)

MajorPlayz said:
I may be mistaken though
Click to expand...
Click to collapse
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.

XperienceD said:
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.
Click to expand...
Click to collapse
Weird ?
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
My friend did the command but he told me that is what it was. I'll grab the full list of commands from him, but flashing twrp was definitely to boot!
Nevermind haha!

MajorPlayz said:
Weird
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
Click to expand...
Click to collapse
SGP611, I just don't get it.

XperienceD said:
SGP611, I just don't get it.
Click to expand...
Click to collapse
Weird

For those with any trouble and that can't flash twrp, a full procedure for injecting TWRP into the kernel is here:
https://forum.xda-developers.com/showpost.php?p=74528751&postcount=22

Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?

Ishtvan said:
Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?
Click to expand...
Click to collapse
Hi there, sorry for long reply - I've been inactive for quite a while as I didn't have a device to hack with. My tablet unfortunately died!
Anything done on a device, whether it be playing games, streaming media, or using TWRP Recovery will consume Battery.
The un-bootloop problem will take charge from your device, but it is safe to keep the device plugged in, charging, whilst you perform the commands.
If all else fails, use Emma as I mentioned before.

hi,
Following this "how-to" everything fine till end of bootloader unlock.
going under developper option, and can't find OEM unlock
trying to make :
Code:
fastboot flash boot twrp-3.0.2-0-scorpion_windy.img
[sudo] Mot de passe de youb*:*
target didn't report max-download-size
sending 'boot' (12372 KB)...
OKAY [ 0.410s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.413s
Trying under linux and then window 7, same error
I ticked usb debug and paired with my laptop.
don't know what to do now ( I'm under firm 23.5.A.1.291)
edit:
ok working, reflash same firmware (us version) and then flash this kernel
glimmling said:
Hi,
I made a boot.img for the SGP612 [6.0.1] [23.5.A.1.291] unlocked BL.
Sony RIC disabled
TWRP 3.0.2
(DRM fix)
Root and Xposed is NOT included. I recommend flashing Magisk v12 later in TWRP and enable Magisk Core Only Mode and Magisk Hide in the settings. Then it will pass the SafetyNet test and you can use su.
To flash the boot.img, put your SGP612 into fastboot mode (Volume Up + connect USB) and then run:
Code:
fastboot flash boot boot.img
If you have a backup of your TA partition, before you unlocked, see the rootkernel thread by tobias.waldvogel, how the DRM fix works.
Thanks to codfx for give me the idea for a SGP612 counterpart and to tobias.waldvogel for his tool :good:
Click to expand...
Click to collapse
from https://forum.xda-developers.com/z3-tablet-compact/development/kernel-t3472019/page2

hazote said:
hi,
Following this "how-to" everything fine till end of bootloader unlock....
Click to expand...
Click to collapse
Where you able to get this working?
Sorry for the very late reply.

Here you find some more details incl. Magisk root instructions: https://forum.xda-developers.com/showpost.php?p=78588234&postcount=14

Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?

lacarte said:
Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?
Click to expand...
Click to collapse
Have you tried Flashtool: http://www.flashtool.net/index.php ?

[TWRP & ROOT] Ticwatch E/S & Unroot Instructions for Updates - v003

{
"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"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!​
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!

You're the best! I'm gonna try as soon as I can, and let you know.

Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?

Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.

Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.

Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.

Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.

TWRP is now persistent! Check the updated guide

Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer

Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.

EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.

Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?

elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.

Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!

elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)

EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!

Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol

hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.