Related
Hello guys,
I am pretty new to this stuff. I have just got LG P500 early this year, my friend helped me root this phone with CyanogenMod (7.1.0-RC1-Thunderg-KANG) and the Build number was SonyGenMod v1.2 Final. Not sure if this information is needed but I really want to go back to normal settings or the best settings as I don't really know how to root/unroot or update stuff.
I just want to use the updated version of Android Market. Right now, it is very annoying that I can't go online on WIFI because I can't update apps or go in Google Play. As it comes up with some errors.
Again, I'm pretty new to this stuff. I am not experienced so I need a clear step on how to fix this situation. I need your help if possible. Not sure if this is the right place to ask. Feel free to move this thread.
Model: LG P500
Android Version: 2.3.5
Baseband Version: V07u-000-000-MAR-23-2009
Mod Version: CyanogenMod-7.1.0-RC1-Thunderg-KANG
Build number: SonyGenMod v1.2 Final
Please let me know if you need any other information to solve this.
Thanks!
Dafcee said:
Hello guys,
I am pretty new to this stuff. I have just got LG P500 early this year, my friend helped me root this phone with CyanogenMod (7.1.0-RC1-Thunderg-KANG) and the Build number was SonyGenMod v1.2 Final. Not sure if this information is needed but I really want to go back to normal settings or the best settings as I don't really know how to root/unroot or update stuff.
I just want to use the updated version of Android Market. Right now, it is very annoying that I can't go online on WIFI because I can't update apps or go in Google Play. As it comes up with some errors.
Again, I'm pretty new to this stuff. I am not experienced so I need a clear step on how to fix this situation. I need your help if possible. Not sure if this is the right place to ask. Feel free to move this thread.
Model: LG P500
Android Version: 2.3.5
Baseband Version: V07u-000-000-MAR-23-2009
Mod Version: CyanogenMod-7.1.0-RC1-Thunderg-KANG
Build number: SonyGenMod v1.2 Final
Please let me know if you need any other information to solve this.
Thanks!
Click to expand...
Click to collapse
Firstly, forget about unrooting because nobody would dare to unroot any Custom ROMs. Or if you really wanted to unroot, install a LG P500 stock Android firmware.
And I guess you've wiped data/cache/dalvik-cache in recovery in order to get correct functioning of the ROM. Not doing that would arise problems.
Android Market (now, Google Play) updates itself when an internet connection is active in phone. I'm not sure about your Wi-Fi problem, its better to ask that in your device-specific forum.
If you really need to start from beginning :
- Enter recovery, Wipe Data/cache/dalvik-cache/battery stats
- And install the CyanogenMod ROM again (Assuming you know how to install)
solution for rooting LG P500 and reflash the recovery image
With the help of tutorial below. if you are new to android and don’t know about rooting , benefits of rooting android then follow this article below to understand why we need root .
What is android Rooting and advantages of rooting android phones
Instructions to Root Lg Optimus one P500 running Stock 2.3.3 Gingerbread
[ Method 1]
Required:
First of all, grab root package from the link here http://api.viglink.com/api/click?format=go&key=9b4efad421c8b103b2c94b796db973b0&loc=http%3A%2F%2Fandroidflip.com%2Fhow-to-root-lg-optimus-one-p500-android-2-3-3-gingerbread%2F&subId=699525ab5972e28f08fc024a38568f58&v=1&libid=1342430198803&out=http%3A%2F%2Fwww.tvornica-ideja.com.hr%2Froot%2Froot.rar&ref=http%3A%2F%2Fwww.google.co.in%2Furl%3Fsa%3Dt%26rct%3Dj%26q%3D%26esrc%3Ds%26source%3Dweb%26cd%3D2%26ved%3D0CFcQFjAB%26url%3Dhttp%253A%252F%252Fandroidflip.com%252Fhow-to-root-lg-optimus-one-p500-android-2-3-3-gingerbread%252F%26ei%3DhdsDUIXTIYa3rAfN_I2nBg%26usg%3DAFQjCNHWvm-CMFcF_BG8B8hKnGa88vDrdA%26sig2%3DplGHxvIHgTVxbqsJQLKLbw&title=How%20to%20Root%20Lg%20Optimus%20one%20P500%20Android%202.3.3%20Gingerbread&txt=here&jsonp=vglnk_jsonp_13424328545198http://api.viglink.com/api/click?format=go&key=9b4efad421c8b103b2c94b796db973b0&loc=http%3A%2F%2Fandroidflip.com%2Fhow-to-root-lg-optimus-one-p500-android-2-3-3-gingerbread%2F&subId=699525ab5972e28f08fc024a38568f58&v=1&libid=1342430198803&out=http%3A%2F%2Fwww.tvornica-ideja.com.hr%2Froot%2Froot.rar&ref=http%3A%2F%2Fwww.google.co.in%2Furl%3Fsa%3Dt%26rct%3Dj%26q%3D%26esrc%3Ds%26source%3Dweb%26cd%3D2%26ved%3D0CFcQFjAB%26url%3Dhttp%253A%252F%252Fandroidflip.com%252Fhow-to-root-lg-optimus-one-p500-android-2-3-3-gingerbread%252F%26ei%3DhdsDUIXTIYa3rAfN_I2nBg%26usg%3DAFQjCNHWvm-CMFcF_BG8B8hKnGa88vDrdA%26sig2%3DplGHxvIHgTVxbqsJQLKLbw&title=How%20to%20Root%20Lg%20Optimus%20one%20P500%20Android%202.3.3%20Gingerbread&txt=here&jsonp=vglnk_jsonp_13424328545198
And download needed driver pack from link here
and install on pc then reboot pc
Enable usb debugging mode by going to settings>applications>developer
Extract root.rar to safe place like desktop
Go to ADB folder , if you are on window 7 run cmd7.exe OR if you are using Windows xp then run cmdXP.exe .
After starting cmd7 or cmdXP, type following commands
adb devices
then
adb shell
(symbol will change to $ or #) and copy paste following command into your terminal
echo 1 > /data/local/lge_adb.conf
After doing this, Reboot your phone
Now go to root folder on desktop again, and start SuperOneClick.exe
Select GingerBreak method and press root button
Wait few seconds and its done.
If you wish update superuser app from android market.
[ Method 2 ]
In First step we need to setup ADB on our pc , to setup ADB on your pc follow this article
Install Android SDK on your windows PC , follow this guide
After setting up all things , restart your pc
Download SuperOneClick tool and install it
In adb run this
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf
After that open SuperOneClick and root using pneuter.
Reboot phone and update Superuser from Market.
These rooting instructions works fine on LG Optimus One, it can have some problems while updating superuser, kept force closing, but after restart, it will work fine.
If something went wrong when trying to flash a recovery image, for example when flashing CyanogenMod or ClockWorkMod. It happened to me several times so I tried to learn to revive it without reflashing the original firmware. Note: This tutorial works only if recovery is the only one broken. (If the ROM itself is broken, then that's a subject for another tut.) In this case, the most logical thing to do is just reflash the recovery image. So how do you do it in fastboot mode? Here's how:
Symptom
You tried flashing a custom recovery like ClockWorkMod or Thunderg, or you flashed an incorrect ROM, and when you rebooted, it showed this screen:
Code:
fastboot mode started
udc_start()
and the phone stays there. When you plugin the phone to your computer's USB, it is detected and the screen has this display:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
You will need
1) Your PC and your USB cable for the phone
2) USB drivers for your phone (use B2C from LG).
3) Android SDK (download from here)
4) Java, required to run the SDK (but right now I am not sure if this is required to run fastboot!)
5) ClockWorkMod or AmonRa Recovery.
Here's what to do
1) Assuming phone is turned on in fastboot mode, plug it in to the USB of your PC. You will know that it is detected if you see the the lines "suspend", "reset" and whatnot on the phone's screen.
2) Extract the recovery image from the zipfile downloaded from step#5 above (e.g. LGp500-recovery-v12.img). Place the image file in the same folder where fastboot.exe is (usually in the tools\ folder in the SDK). For your convenience, rename the img file as recovery.img
3) Fire up your command prompt and cd to the directory where fastboot.exe is located. Then type the following command:
Code:
fastboot erase recovery
Once you get the confirmation that it was successful, type this:
Code:
fastboot flash recovery recovery.img
Once you get the success confirmation, reboot the phone, or you can also type (optional):
Code:
fastboot reboot
The phone will reboot itself, and with any luck you should be able to go back to your same old Android bootscreen. Note that no settings were modified here, so this is extremely useful for those who do not want a clean slate after a fastboot nightmare.
Also, note that if this is successful, you can now boot to recovery with the usual button-combos, thus enabling you to flash ROMs and other recovery zips.
Note: On some SDK versions, fastboot may not be included. For your convenience, I have attached the fastboot binary I got from my downloaded SDK. I have also attached AdbWinApi.dll which some user reported is missing in the SDK. Place the DLL in the same folder where fastboot.exe is located.
Questions, just drop me a line here
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Uberjim said:
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Click to expand...
Click to collapse
Thanks for the reply. I appreciate the info given. Will try to use the tool now since the rom file is no longer saved in the tablet.
Will update soon.
Thanks.
I'm just done installing the Knivesandforks on my win7. After that, the system automatically install the phyton. I dont know what its function, but as i follow this steps, i get error with cmd which shown as below:
Code:
c:\users\pc>adb reboot
error: device not found
i think i didn't miss any steps. Anybody here could help me with this?
Thanks in advance.
* my tablet is still in cmw main page and not showing anything even has been connected to the PC. i think that's the reason why the error occurs - device not found. anybody who could give some ideas on this will much appreciated.
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Uberjim said:
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
Click to expand...
Click to collapse
i did those steps again, but it seems like not helping. the script is only rebooting the tablet instead of giving me the option to flash the rom. i don't know if i did wrong. but as i know, i did as posted here.
* frust to see the cmw recovery for the whole day
Striatum_bdr said:
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Click to expand...
Click to collapse
i did follow this tutorial
at first, install universal naked drivers - done
Now do the following:
Make sure your Prime is in Recovery mode (CWM) - YES
Open a cmd line on your pc - DONE
Type: "adb shell" - DONE
You should see a "#" now - YES
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] - Ok. This part was very difficult. I see the "#" but to type all those command, I can't. Why? Because the line in cmd instantly extended to a new line of command. I mean it just like I press the ENTER button. So, the line move to below and i can't finish typing all those command.
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
titanbullet said:
i did follow this tutorial
at first, install universal naked drivers - done
Click to expand...
Click to collapse
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Striatum_bdr said:
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Click to expand...
Click to collapse
this is my first time, so i don't know if that was strange. ha ha. well, it's not about the command line which is extended or not. but the line itself creating a new line, as i said - just like i press the ENTER button.
i try to use copy-paste function (ctrl + c and ctrl + v). but i don't think it functions in cmd.
please help..
[Solved]
What i do?
I follow this step again
Installing the ADB again
And the most important thing is, pushing ROM into /sdcard should be like this:
Code:
adb push rom.zip /sdcard/rom.zip
And right-click copy paste function solving my strange cmd
Then i just follow the steps by installing the zipped rom thru cwm when my screen did not stuck at splash screens
Thanks for your kindness
My TF is now back to normal
THANKS!
June 02, 2015
Edit: If anyone has a link to the stock ROM for the Ascend G7, please let me know. I would love to make a custom ROM that doesn't take up 98% of all resources 99% of the time.
Hello everyone.
Before I get started, here is everything you need to know about this post.
- This root works as of June 29, 2015
- This is a rooting process for the Huawei Ascend G7
- I did not make this, so please consider supporting all mentioned sources
- I am a new user to XDA, but I've been developing for over a decade. I will regularly check this post if enough people who view it have questions
There are two parts to this process.
First, we unlock the bootloader
Second, we flash a recovery, and subsequently, SU (root)
Let's get started. This will take at least 16 hours. User interaction 5 minutes, and about a 16 hour wait for an email response from Huawei.
Also, I have a new account, so I cannot post links. So please bear with me. I will upload photos in as best order as I can.
Before we get started, please note that your phone will factory reset in this process.
First thing's first. The Ascend G7 requires an unlocked bootloader, before any root can take place. This is obviously temporary, until someone finds a circumvention. But for now, this is how this needs to be done.
Send an email to [email protected], with this format:
Dear Sir/Madam
Please may I request the bootloader unlock code for my Huawei Ascend G7?
Here are some Details:
Serial Number: (Found under Settings --> About phone --> Status)
IMEI: (Found under Settings --> About phone --> Status)
Baseband version: (Found under Settings --> About phone)
Please could you send me the code directly, as I cannot access the product ID on my device.
Thank You
Your name
This part is important. Sometimes, they do not even reply to your email(s). It is recommended - nay, required - for you to put "URGENT" in the subject field of the email. Something along the lines of "URGENT Request Bootloader Unlock Code." It would also be best if you mark your email as urgent/high priority, as well.
Meanwhile, while you wait for the email from them with your unlock code, (expect it to arrive the day after), download the Android SDK and the Java JDK, if you haven't already. What you need most are the SDK tools, which you can also download by typing in "SDK tools android" in Google and finding a download for the stand-alone tools.
Make sure Android Studio is updated, if you already have it. To make sure you have everything you need, open up command prompt in platform-tools, by holding shift and right clicking somewhere on the white, in the folder, (explained in attached picture).
Then, plug in your phone. Make sure USB debugging is enabled. To do so, go to Settings --> About phone --> Tap "Build Number" 7 times in a row. Then go back, and you will see "Developer options." Click on that, and enable USB debugging. Also, this optional, but I like to enable the "Stay Awake" function.
Make sure to accept any prompts that your phone will ask.
Then, go to the command prompt and type in "adb devices" without the quotations.
If you've done everything correctly so far, you should see something similar to the attached command prompt image file.
If everything checks out, let's proceed. If not, post below, and I, or fellow XDA users, will help you out.
Proceed to type in, "adb reboot bootloader" without the quotations, into the command prompt window that you opened. Your Ascend G7 should reboot into fastboot, where you will see something like the attached picture below, of the bootloader screen.
Except, it will say Phone Locked instead of Phone Unlocked.
Now, go back to your command line, and type in "fastboot reboot," to have access to your phone and its functions, while you wait for the email from Huawei.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Everything below this line should be done AFTER receiving a reply email from Huawei, with your unlock code.
Now, download the "PHILZ-TOUCH-6.rar" file. I cannot attach it here because it exceed file size limit. No virus, no surveys, here's the link, https/goo.gl/sxPv7I. Just add a colon and a forward slash after https. It is not a virus, in case your firewall or antivirus software brings up red flags. I will post the whole ZIP that I've downloaded from another website. There's a bunch of redundant elements in the folder, but just in case you know what you're doing and might need the tools, I'll keep them there. But all you will need are 2 things from the folder. They're mentioned next.
Go to where you extracted PHILZ to, and hold shift and right click and open a command window in that directory, and type in "adb devices" one more time to make sure your device is listed and connected. Then, type in "adb reboot bootloader," give it a second, and then when fastboot loads up, type in,
fastboot oem unlock 123456789123
Replace "123456789123" with the unlock code provided to you from the Huawei email. Give it a second, and then you should be good. It should now say "Phone Unlocked" in red. Now, type
"fastboot reboot"
in the command line (that was opened in the PHILZ folder), without quotations. Then type,
adb reboot bootloader, one more time, and then,
Navigate to the PHILZ folder, and run "install-windows.bat" as administrator, if using Windows.
If using Linux, run "Install-Linux.sh," and if using a Mac, run "Install-Max.sh"
Now, in CMD type,
fastboot boot recovery.img
Then, again type in
fastboot reboot
Your phone will reboot.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Aaaaaaand that's it! You should now be rooted. I recommend going to play store, and downloading a Root Checker to ascertain root access.
The last picture, where it says I have root access now, is a program called Root Genius. It's a one click tool to root any android device - obviously except the Ascend G7, (knowing my luck). But it does work as a root checker as well, if you want to ascertain root access. You can also download Root Checker from the play store; works more or less the same way.
Any questions, feel free to ask. Re-reading this, I could see if the instructions bring confusion to some. I will be glad to clarify any questions.
Works
Root confirmed G7-L01
some point that I did not understood
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) open up command prompt in platform-tools
what is platform-tools? A specific folder? I was not able to find it
2) if I open the command prompt from any forlder using the shift+right button as you said and then write adb devices I get this message:
'adb' is not recognized as in internal or external command operable progrma or batch file. What should I do?
3) when I connect the phone by usb cable, should I do something more (like enabling device file manager, pc suite or other options) or just connect it in charge only mode?
thank you for your time!
and... by the way, I'm really impressed that I got the anwer from Huawei with the code, that's really cool! Thank you!!
---------- Post added at 04:09 PM ---------- Previous post was at 03:19 PM ----------
I found the platform-tools folder, now if I type adb devices from a prompt open from that folder I don't get the error message anymore, but I get nothing, just the flashing prompt line (the huawei phone is on and usb connected to pc)
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Frankleoni said:
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"?
Click to expand...
Click to collapse
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
<device offline>
Frankleoni said:
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Click to expand...
Click to collapse
Hi Frank,
Let's troubleshoot,
If it lists your device as offline, open up cmd (Run --> cmd), and type in,
taskkill /f /im adb.exe
Then, restart your G7; when it boots up, turn off and then on USB debugging, then find PHILZ, and retry point 3. If device is still offline, please let me know. The issue sounds like it's within the phone, not within ADB.
Alternatively, if that doesn't work, please delete PHILZ off your computer, and wherever it says "PHILZ" in my guide, replace it with the attached folder, (attached with this reply).
Cheers
PS, please make sure to check that your phone is not only in USB debugging mode, but that you've approved/allowed your computer access to your phone, (a prompt will show up on the Ascend G7 that asks you whether or not you trust your PC). And also make sure your phone isn't just set to "charge" when plugged in - activate/select MTP when you connect your phone to computer.
<device offline>
lume12 said:
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
Click to expand...
Click to collapse
Please refer to my reply to Frankleoni below.
Thank you for replying chy_vak,
I tried your solution in both the PHILZ folder and the new folder you attached. The device shows offline in both of them. However in the build-tools folder it shows online. The command line taskkill /f /im adb.exe terminated adb but the device still shows offline. I did everything in the exact order you wrote.
offline
search Kings Root via Google Chrome, install it and run it Easy and without chat with Huawei support
Kingroot Works like a charm !
@chy_vak, Thank you for your Work. 1st Part works great. 2nd Part went wrong, i dunno why i`ve tried every thing. I hate this Kingroot think, don`t touch it you never will leave it.
I have connect my G7 because unlock works. When i use CMD from Adb Tool it is connected, when i use command prompt from Philz he cant see and find the mobile?? Something for you absolute clearly, isn`t for other. Sry cant do screenshot with notebook and Win 10. have fun
Another Working Method to Root Huawei Ascend G7-L01/L03
Greetings!
I got an Ascend G7 Recently and I needed to Root it as soon as I got it. That's why I kind of broke my head looking for the current methods to do it. I found this one very promising so I started working. I followed the steps that were given to us one by one. Everything was alright until I tried to install the Windos-Installer.bat as administrator, I tried to many ways to this method work, but as much as I tried, I couldn't go with it, that's why I started working for 11 hours until I got it. This Worked for me, and I want to share it with you.
Please read the following notes before you start by rooting your device:
-As usually, do it at your own risk, I'm not responsable of any brick, or issue that damaged your device.
-This Method is working great on Windows 10
-This Method is working at 04/08/2015
-This Method, was tried by me, the directions I give to you, are based on my work by rooting my device and my experience, the software and files included were made and posted by someone else including the person who wrote this post: http://forum.xda-developers.com/gen...-confirmed-t3125621/post61122491#post61122491
-You can find screenshots of the procedure below
-You will need a microSD
-I strongly recommend you to have at least 80% of battery to avoid risks of bricks
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here begins the directions:
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
After a while (Could take between 15 minutes and 16 hours depending on their time) A Huawei worker will answer you something like this:
Dear Customer,
Thank you for supporting Huawei device. My working number is ****. Your unlock code :************** , please keeping your unlock code properly.Thank you!
Huawei Terminal Company limited
1.1.- (OPTIONAL) As we are going to unlock the bootloader, we are going to make a factory reset, so I strongly recomend you to make a backup with the official huawei backup app in order to restore our settings, apps, and files.
1.2.- Once Again, as has been said, you will need to download the whole Android suite (Android Studio) the last version, update your java version, and download the last drivers for your device (A good way to do the last is by installing the HiSuite of Huawei).
1.3.- You need to activate the debug mode. You can find it in: Configuration->Developer Options->USB Debug (If you dont have the Developer options enabled, you have to go to Configuration->About the phone->Compilation And tap this last one 7 times)
2.- Download the .rar a the end of the page and extract it where you want, includes everything we are going to need. [You must put the file ''superuser.zip'' on your microSD (In the root of the microSD)]. After Downloading it, you must open a cmd window, running it as administrator. After that you will write:
cd (Here you should paste the ubication of your extracted File Ex: C:\Users\Josh\Downloads\Root Ascend G7)
Now you are in this ubication that includes adb. Write:
adb devices
You should see: List of devices attached, a code and the word device (There is a capture below). If you do, we can proceed.
3.- Type :
adb reboot bootloader
It should load a white page with the Android pet and the words FASTBOOT&RESCUE MODE Below there is the phrase ''PHONE LOCKED'' in color. Now type:
fastboot oem unlock *********** (The code Huawei gave to you)
Now your phone will make a factory reset. You will see how it reboots by itself and back to the default settings. You will need to activate the debug USB mode again. By this point its supposed your bootloader is now unlocked, to probe it, we will type again:
adb devices (To check it is correctly plugged)
Then we will type:
adb reboot bootloader
And now at the end of the page it should say: ''PHONE UNLOCKED''. If you do, we can proceed.
4.- At this point, you have two options: You can replace your stock recovery mode by a ClockWorkMod Recovery (I strongly recomend you to do that) or you can just ROOT the phone whithout replacing your stock recovery.
If you decided by replacing your stock recovery follow the next directions: We still have our CMD window opened and running adb while the phone it is on the bootloader mode. So now what you have to do it's to type:
fastboot flash recovery recoveryP.img (CMD will work and show a few commands)
And after that type:
fastboot reboot
Your phone will reboot again normally and we can proceed.
If you decided not to replace your stock recovery instead of typing ''fastboot flash recovery recoveryP.img'' you have to type:
fastboot boot recoveryP.img (This will send you directly to CWM recovery)
5.- You must acces to CWM Recovery.
If you installed it on your phone, turn off your device and then press the power button and vol+ until the Huawei logo appears, you should be in the recovery mode by now.
If you didn't install it, you already are in CWM recovery.
6.- With the vol and power buttons or the touch buttons at the end you should be able to navigate on the recovery. We go to:
Advanced Functions->Re-root System (SuperSu)->Yes-Apply SuperSu (You will see a few code at the end of the screen)
7.- Without leaving the recovery mode, go to the main screen and now we go to:
Install Zip->Choose zip from /sdcard->superuser.zip (The one that you previously putted on your microSD)->Yes-Install superuser.zip
(You will see again a few code at the end of the page) We go back to the main screen and Select:
Reboot System now
8.- It's supposed we are ROOT now. At first you will see the ''superuser'' app installed. To probe that works, Install ''android-terminal-emulator-1-0-70-multi-android.apk'' that it is included on the folder ''Terminal'' form the file you downloaded. Now open a new terminal window and type
su (If everything worked, superuser will ask for permissions)
8.1.- Restore your data with the Huawei Backup App
And that is all we have superuser acces now. If you have any question or issue let me know and I will help you.
https://mega.co.nz/#!Al9FxDBY!QHkljnnIbjURX01A59tJPNkAVQd3LbKTqRJHD_nNxrs
Thank you!
Cant boot into recovery
Hey guys so i tried following this procedure but it never works :/ if i flash the custom recovery and try boot into it, the phone directly goes to fastboot and rescue mood so cant boot into recovery, not even the stock recovery. if i try directly booting into the custom recovery it says dtb not found :/ can someone please help me?
the model is G7-L11 and the bootloader is unlocked
Engineer Mode Huawei Ascend G7 L03
Huawei Ascend G7 L03
Hi,
I have tried every thing to go into Engineer Mode.... Even Mobile Uncle Does not do that!
Please some one Help....
Huawei Ascend G7 L03
thanks for the translated philz touch
Hello everyone, I have a big problem with a Huawei G7. I did Philz Touch and Root. How can I go back to stock rom?
I've emailed Huawei 3 times now, left a week in between emails, and still haven't received my unlock code. Has anyone else had this issue?
Thanks
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
Does anyone have a good tutorial on how to flash twrp on the phone ? I've tried different things but it never works
any other method exept this email method? they wont answer me.
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.
In such cases, you cannot reach adb from the command line, so there seems to be no way to recover the watch. Fortunately, it has been discovered how fastboot can be entered without a running system.
2. Procedure
Step 1: Get into fastboot
This is the most difficult part. @kiralex1995 has developed a procedure that will lead reproducible to boot the watch into fastboot mode, but it may take many tries (one user reported that it took him 30 min of tries).
Follow this guide: https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
When you are in fastboot and see the fastboot logo, you have mastered the most difficult part.
Step 2: Choose a ROM to flash on the watch
There are currently three possible ROMs to choose from:
a.) The English AmazFit firmware 1.3.0n
Download the following file on your PC: https://mega.nz/#!xIkC1IQZ!bLLSN9BMvbp7zhZHg2oQq6p4ud-EFyUYkatCGKgHeS8
b) The Chinese AmazFit firmware 1.2.5a
Download the following file on your PC: https://mega.nz/#!tNdggR4b!VXmExGqdNixrj8pVLqTkAi_munmjF5RidRJP9L-LAXE
c) An old Chinese AmazFit firmware 0.9.50:
Download the following file on your PC: https://mega.nz/#!wY9mEQoI!0ARB0MaK0byjttgrPmJJQX4ZFdIXgHOUquxqFhghg7U
Step 3: Download flash script from xda
Download the attached flash script from this post to your PC.
Step 4: Unpack the archive on your PC
Depending on you PC choose the right method to extract the files in the ROM archive and the flash script.
Step 4: Boot the watch into special recovery
Check that your fastboot drivers see that watch (which should still show the fastboot logo):
'fastboot devices'
You should see your device listed. Otherwise check your fastboot driver installation on your PC. (Note: On Linux you sometimes need to use "sudo fastboot ...".)
Then boot the modded recovery that is included in the archive you unpacked in step 2.
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
Step 5: Transfer the ROM files and the flash script onto the watch
First check that you are now able to connect to your watch via adb:
'adb devices'
You should see your watch listed. Otherwise check you "adb driver" installation. For Windows take care that you use Khoushs universal adb drivers.
Then push the files to the watch:
'adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/'
Step 6: Enter the shell on the watch and check your files
After you have successfully transferred the files to the watch, you then enter the shell on the watch:
'adb shell'
You should see only a "#", meaning you have full root access.
Now switch drirectory to the sdcard
'cd /data/media/0/
ls'
You should see your files on the "sdcard", including the ones that were pushed before
7. Start flashing the files
Run the flash sccript with the following command on the watch:
'sh flash_rom.sh'
If everything worked correctly, you should see something like:
Code:
Validating images
boot.img.gz: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE! Press Enter to continue or CTRL-C to stop!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 2.075793 seconds, 4.3MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 107.981352 seconds, 7.6MB/s
Finished
If you see any error message during or after flashing, then DO NOT REBOOT the watch, but get some help or analyse yourself, what went wrong. You can still reflash.
8. OPTIONAL: Delete the dalvik-cache
You can erase the dalvik-cache on the watch with the following command:
'rm -rf /data/dalvik-cache'
This will make the system "re-optimize" all apps when it boots (successfully) the next time. This is optional, as you could always do that later again.
9. Reboot the watch
If everything is ok, then you can reboot the watch
'reboot'
Your watch should boot normally into the flashed system, you downloaded. CONGRATULATIONS, you unbricked your watch!
Thank you for this post.
Neuer_User said:
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.....[/B]
Click to expand...
Click to collapse
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
First watch has just successfully been unbricked (1immortals watch) [emoji106] [emoji2]
kiralex1995 said:
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
Click to expand...
Click to collapse
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Neuer_User said:
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
Click to expand...
Click to collapse
Well i guess constant WiFi would dramatically reduce the running time? On the other hand it might just be turned on for short periods, don't know how Google does that.
1immortal said:
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Click to expand...
Click to collapse
Congratulations and thanks to Neuer_User.
hi, after this step the watch reboot and restart the loop on logo. why?
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
edit: after more test, i'm not able to go to recovery mode. For an errore, when i try another time to go to Fastboot mode, i push 2 times the button and i ERASE ALL the watch, now i have a device called JZ4785 USB Boot Device.
There's some way to save this watch?
Thanks.
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
1immortal said:
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
Click to expand...
Click to collapse
This could indeed be the case. Noone of us ever entered that mode so far. It would be very good to understand, how you really got into that. It must have happened in the first step, where you were supposed to enter fastboot. Did you see the screen on the watch with the two options? There is a video in the link of @kiralex1995 post. Maybe you can comment, what exactly looked identical for you and where it exactly started to differ.
In case, you are really in that SOC flash mode, the Ingenic USBburner tool would indeed, probably, be the right tool to reflash the watch. As I mentioned, nobody here used that before. I have some experience with similar tools for the MTK platform. I believe that it should be possible to generate the necessary dump from a working watch, but this is all theory so far.
Where are you located?
well, nothing helped, there's no configs for the JZ4785, and there's no relevant information of partitions offset for flashing. we tried to flash both 1.2.5 and some generic ingenic image, with a lack of success as well
contacted ingenic for some clarification and some help, lets see where this lead to ...
Hello and thanks for tour support.
Also "launcher has stopped" i have to consider as a brick situation?
Palese led me know because i tried to update from chinese firmware but Now it doesn't work, i am able to start in fastboot mode
Thank you vero much fo and your advice
regarding the launcher errors, please try to unpair your watch and re-pair it again, it's a non-brick situation.
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
alon1211 said:
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
Click to expand...
Click to collapse
Try a different USB cable. Bad cables are known to produce that error.
This is pretty awesome! I used this to convert my Chinese Amazfit watch to English ROM, and it seems to work OK.
However, there's a piece missing from the bundle -- the recovery image. There's an OTA available, and I pulled the update.zip file using the Fastboot trick so the OS didn't load and delete it - then booted the "mod recovery". Here's that update.zip (to 1.3.2b): https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
The OTA didn't succeed -- when it went to reboot to recovery and apply the update, it booted with Chinese text in recovery boot and failed with just one word - "Error". I'd imagine that's because recovery.img wasn't part of the bundle, so my watch still has the Chinese ROM recovery on it. Looking at the update.zip, it's fairly clear it's built in English - with English error messages in "updater-script".
I'm hunting around for the English ROM's recovery image, and will probably find it in the next few minutes, but figure I should mention this hole - and that this routine is also useful for converting to English. It'd been demonstrated before that you can run the English ROM just by flashing it (and boot.img), but no unified thread seems to exist for it yet (that I can find via Googling at least). :good:
edit: Literally 5 minutes later, bam. https://forum.xda-developers.com/showpost.php?p=71264431&postcount=599 - I downloaded that Fix_recovery bundle, pushed it to /data/media/0/ from the mod recovery, ran it, and it gave some errors but fell back to the "dd" method. So, all that's needed to get a complete English ROM flash is to add recovery.img and the line:
Code:
busybox dd if=recovery.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/recovery bs=4096
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
dpenevdpenev said:
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
Click to expand...
Click to collapse
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Neuer_User said:
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Click to expand...
Click to collapse
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
dpenevdpenev said:
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
Click to expand...
Click to collapse
Hmm, if that doesn't work, try "fastboot erase cache" and "fastboot erase data". That will really completely delete all user and cache data. The next restart should take a long time.