Database Users

[Q] Google nexus 7 (2012) - Unrooting leads to total failure(no recovery, no boot up)

Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"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"
}
I think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated ​

Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk

Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )

Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid

Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk

I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?

Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet

Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...

[Q] 2012 Nexus 7 stuck in bootloop but recovery not working?

OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
Description: I flashed the device with Cyanogen Mod, all worked fine but when I then tried to install G-apps it went through the installation process, rebooted and then stuck on the spinning Cyanogenmod logo.
I've tried rebooting it into recovery mode to find a solution. Going through the factory reset option runs through the whole process and then reboots into the looped boot logo 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"
}
When I reboot the device in recovery mode I get this screen and options:
This is the text at the bottom of the recovery screen:
The screen after I hold down power & volume up (and release volume up after 3 seconds):
This is the options I get when choosing ADB mode:
Factory restore option menu:
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.

evertb said:
OK, after several weeks of google-ing and trying different solutions I still have not been able to find a fix for this so I'm hoping that a bit more details & illustrated post will help.
One of the issues I think is that the device is no longer detected by my PC which seems to remove the option of pushing a new ROM to is.
Any ideas would be very much appreciate.
Click to expand...
Click to collapse
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!

Thanks for those instructions, yes have gone into recovery from the bootloader but that leads back to the bootscreen.
Will try your instructions in the morning!

PrizmaticSmoke said:
Edit: The screens you're calling recovery are actually the bootloader, use the volume keys to select recovery mode, and power key to confirm. If you have a working recovery it should boot into it, just go from there to clean flash your rom again (or an alternate one if desired). If gapps gave you issues, you might try redownloading gapps (may as well check the ROM file too). If you don't have a working recovery, then follow the other instructions below.
Your device should be recoverable, you're booting into fastboot mode on the bootloader screen and are unlocked, so you should be able to use this to restore a factory image of your choice.
Use the steps in this thread (it's stickied at the top of this section) http://forum.xda-developers.com/showthread.php?t=1907796
First type the command "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode, if it returns your device's serial number, you should be good to go and won't need to follow the steps to install drivers. If it doesn't return the devices serial number, you have driver issues with adb/fastboot and will need to resolve this first (there are tips and links for installing or updating drivers in the guide).
Also, you can skip the "fastboot erase boot" and "fastboot flash bootloader" commands, as your bootloader is fine. There are also corrupt versions included in several of the google factory images, so i would recommend to just not do this if it's not needed.
Hope that helps and good luck!
Click to expand...
Click to collapse
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?

evertb said:
Where/when exactly do I type in "fastboot devices" with the device connected to your PC and in bootloader/fastboot mode?
Click to expand...
Click to collapse
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.

PrizmaticSmoke said:
With the device in Fastboot mode (like your second screenshot, you'll see "Fastboot Mode" in the lower left at the top of the block of text) and connected to your PC, open a command prompt on the PC, and just type the command "fastboot devices" then hit enter.
Click to expand...
Click to collapse
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...

evertb said:
At the c: prompt?
I did this and get the following error: "fastboot' is not recognised as an internal or external command, operable program or batch file...
Click to expand...
Click to collapse
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.

PrizmaticSmoke said:
Okay, then you need to install the Android SDK and Java development kit, there are links and instructions on how to do this in the guide i linked to above in the "Software Requirements" section.
Click to expand...
Click to collapse
I did that prior to trying this.
Will uninstall everything and start from scratch.

I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.

Groid said:
I think you just had to be in the folder where fastboot.exe is installed. I went to the C:\Users\myname\Downloads\Android SDK\sdk\platform-tools (where I installed the sdk files). From that folder I did a shift, rt-click and 'open a command window here'. Then I typed in the fastboot command and it executed properly.
Click to expand...
Click to collapse
I've tried all the options outlined above but am not getting anywhere for the simple reason that the device is not being detected by any computer that I connect it to.
I have deleted all drivers so it would install fresh but that hasn't made any difference either.
I looked at installing a fresh ROM via OTG but even that is not an option on the device it seems.
What I am at is the following:
- I can boot into Fastboot
- booting into recovery puts up the "dead android" screen.
- Holding down "power" and "volume up" and then releasing "volume up brings up a screen with the following options: "reboot system
now", "apply update from adb", "wipe data/factory reset" & "wipe cache partition".
- "apply update from adb" brings me to the adb screen but as the device isn't being detected I cannot do anything there. The "wipe data" & "wipe cache" options complete but then bring me back in the same screen.
There does not seem to be an option to load a ROM via the OTG cable.
Basically at this stage I cannot find *any* option to flash a fresh ROM.
Banging my head of the wall here so would really appreciate some help from people more knowledgable than me.

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed ​
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_edl-v2.zip from Here.
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"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"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3. ​
Proof:
Thanks to @emuzychenko for the Idea!

This is AWESOME!! Just tested and worked amazingly.
Thank you!
Edit: the included command prompt didn't work for me though, launched standard and traversed to this folder

It would've been better if the source of this guide is also mentioned, just my thoughts
Sent from my Redmi Note 3 using XDA-Developers mobile app

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned
Click to expand...
Click to collapse
Especially since most of text had been copied "as is".

Please add this to op
=> https://youtu.be/-6uErg52nKs

kaushal64 said:
Please add this to op
=> https://youtu.be/-6uErg52nKs
Click to expand...
Click to collapse
I have updated the fastboot.exe and the method also. Update your video with this and I will add it to OP.

I had replaced link for modified fastboot file please add it to op.

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned, just my thoughts
Click to expand...
Click to collapse
emuzychenko said:
Especially since most of text had been copied "as is".
Click to expand...
Click to collapse
Thumbs up!

This is great
My problem solved
Many thanks

not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.

BRoy_98 said:
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.
Click to expand...
Click to collapse
Where to find it?

Zarko007 said:
Where to find it?
Click to expand...
Click to collapse
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.

BRoy_98 said:
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.
Click to expand...
Click to collapse
Maybe stupid question, but wouldn't phone go to edl mode (with red led flashing) before flashing rom and what then mbn file has to do? According to your manual it is the last step?
thanks

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk

sator02 said:
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk
Click to expand...
Click to collapse
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
Don't use this tool if your device is not bricked, your rom is a distributor rom that's why you cannot unlock your device, you have to flash miui rom prior to unlocking, you can do it thru edl mode using adb, search on miui forums and you'll find it.
Edit: check this out: http://en.miui.com/thread-235865-1-1.html
Sent from my kenzo using Tapatalk

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.

BRoy_98 said:
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.
Click to expand...
Click to collapse
I have tried it already many Times but no success...

Zarko007 said:
I have tried it already many Times but no success...
Click to expand...
Click to collapse
This must be driver problem. Install MI PC suite and it will install all necessary drivers. Then try it again.

Error mode: error 11 no recovery, error 2 failed to load

Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"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"
}

Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.

How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.

Hmm....
Have you tried rebooting to fastboot using adb?

Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times

Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?

elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.

Dc unlocker needs cash and it doesn t always work.

I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.

3 button upgrade doesn't work either.

I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.

Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method

shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..

Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain

Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!

I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.

Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.

elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??

Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.

I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.

[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.