Related
I've got a bricked LGP880 without an OS that boots up.
Although it is possible to access the bootmenu with ADB and software upgrade menu.
Is it possible to flash CMW recovery through ADB? and how?
I want to flash CM11 with it, because it isn't possible anymore to flash the stock rom on my phone because it doesn't see his imei number anymore
Thanks in advance.
eldin1234 said:
I've got a bricked LGP880 without an OS that boots up.
Although it is possible to access the bootmenu with ADB and software upgrade menu.
Is it possible to flash CMW recovery through ADB? and how?
Thanks in advance.
Click to expand...
Click to collapse
Go to software upgrade mode. this video will show you how to go into download mode.
https://www.youtube.com/watch?v=F0Vw-ZTr3xY
and follow this tutorial to flash the stock rom. after you have the stock rom then you can flash the clockworkmod recovery.
http://forum.xda-developers.com/showthread.php?t=2069723
Sippay said:
Go to software upgrade mode. this video will show you how to go into download mode.
https://www.youtube.com/watch?v=F0Vw-ZTr3xY
and follow this tutorial to flash the stock rom. after you have the stock rom then you can flash the clockworkmod recovery.
http://forum.xda-developers.com/showthread.php?t=2069723
Click to expand...
Click to collapse
I tried that but he stops at param 207, and doesn't go further
He won't flash any stock rom without an imei number(of course I have one but he doesn't see it). When I use the LG flashtool the log said: "IMEINOTACTIVE".
I don't know what to do now.
Perhaps it is possible to flash CWM trough ADB or something, and then flash a custom rom (CM11 by example).
Htc m7 one dead in home screen.
I apologize for posting on a topic of another person, thanks for the touch.
Thamgão said:
Hello friends, I need your help, I change the operating system on my htc one m7 android 4.1 jelly bean for CM11, flashyfy used the application to make the switch from rom, but I made something stupid, did not back up your system, ai happen that error in the update, and it got caught on the flashyfi application screen, how do I recover from my new htc one m7, which has as its resurrect the fastboot mode, but do not know where to find the right programs for this, if have some video recovery will be well accepted if possible Thanks Janio.
Click to expand...
Click to collapse
You've posted on someone else's thread please post a new one.
eldin1234 said:
I tried that but he stops at param 207, and doesn't go further
He won't flash any stock rom without an imei number(of course I have one but he doesn't see it). When I use the LG flashtool the log said: "IMEINOTACTIVE".
I don't know what to do now.
Perhaps it is possible to flash CWM trough ADB or something, and then flash a custom rom (CM11 by example).
Click to expand...
Click to collapse
unmount SD card and do adb sideload filename.zip
I gave it a try but without result (check image)
What can I do now?
Sideload was 100% complete but the phone won't install it.
I tried to install CMW recovery and CMW touch recovery.
eldin1234 said:
I gave it a try but without result (check image)
What can I do now?
Sideload was 100% complete but the phone won't install it.
I tried to install CMW recovery and CMW touch recovery.
Click to expand...
Click to collapse
I noticed The ROM you have is a .img file, try download a .zip file. you can't flash .img files using CWM only .zip files
Like Cyanogen mod 10 - Download this file http://download.cyanogenmod.com/get/jenkins/42666/cm-10.1.3-p880.zip
And adb push and try install it
Before you attempt to flash.Wipe data Wipe cache & dalvik cache twice.
Sippay said:
I noticed The ROM you have is a .img file, try download a .zip file. you can't flash .img files using CWM only .zip files
Like Cyanogen mod 10
And adb push and try install it
Before you attempt to flash.Wipe data Wipe cache & dalvik cache twice.
Click to expand...
Click to collapse
Thanks for responding!
I tried it as you said but again the aborted message(see image)
something else I can try?
I think ADB is the only way to get this phone alive (if he can install CMW Recovery). He won't flash any stock rom because he doesn't see his imei number anymore.
What can I try now?
Thanks for your help!
eldin1234 said:
Thanks for responding!
I tried it as you said but again the aborted message(see image)
something else I can try?
I think ADB is the only way to get this phone alive (if he can install CMW Recovery). He won't flash any stock rom because he doesn't see his imei number anymore.
What can I try now?
Thanks for your help!
Click to expand...
Click to collapse
This is to unlock the bootloader
adb reboot oem-unlock
Press volume up button
remove the cable and battery
reinsert battery
reboot into recovery
Now flash CWM (You already have the touch CWMrecovery. replace the filename, recovery.img.)
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
adb reboot recovery
And install the ROM
Once you reboot into recovery mode, it should be in Clockworkmod recovery and, you can install the Cyanogenmod.zip
Sippay said:
This is to unlock the bootloader
adb reboot oem-unlock
Press volume up button
remove the cable and battery
reinsert battery
reboot into recovery
Now flash CWM (You already have the touch CWMrecovery. replace the filename, recovery.img.)
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
adb reboot recovery
And install the ROM
Once you reboot into recovery mode, it should be in Clockworkmod recovery and, you can install the Cyanogenmod.zip
Click to expand...
Click to collapse
Thanks for your answer!
I tried to push the recovery.img file but it won't work (see picture).
My bootloader was already unlocked.
Of course I used ADB in recoverymode, on the second photo I turned into the S/W Upgrade mode for the state of the bootloader.
What can I try now?
Thanks!
eldin1234 said:
Thanks for your answer!
I tried to push the recovery.img file but it won't work (see picture).
My bootloader was already unlocked.
Of course I used ADB in recoverymode, on the second photo I turned into the S/W Upgrade mode for the state of the bootloader.
What can I try now?
Thanks!
Click to expand...
Click to collapse
ADB push didn't work. it failed to copy the file. because you typed the directory wrong, did you rename the file recovery.img,
in command prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever the directory your recovery.img is located. like here it is c:\users\eldin\desktop\android\rec***--- recovery.img
and then type adb push recovery.img /sdcard after you have kept the recovery.img in the folder you have specified.
or you can you try the same way you did adb sideload , but this time type /sdcard. at the end after the directory.
or even connect the sdcard to pc and copy it to the root directory, using a microsdcard reader.
after it copies successfully try the rest of the commands.
And if you want to use the upgrade mode you could try flashing firmware using the LG flash tool I told you about earlier.
http://forum.xda-developers.com/showthread.php?t=2069723
check your device box before you download the firmware. make sure it's the right one. the imei not acitve error might be because you're trying to flash the wrong firmware. this video is not in english but you can follow it. use the thread to download the files.
Hello,
I tried it again but without result (I don't know if I did it right this time).
Your explanaition isn't very clear to me (I am not really good with ADB hihi).
Is it also possible with an external SD card? I got an SD adapter (and a SD card of course) but I don't know the commands.
I tried also to mount the internal SD but it won't work.
About the flash tool, I tried it many times but it isn't possible to flash the stock rom because if I want to flash the stock rom, it needs an IMEI number but the phone doesn't see it anymore.
I hope you can help me!
eldin1234 said:
Hello,
I tried it again but without result (I don't know if I did it right this time).
Your explanaition isn't very clear to me (I am not really good with ADB hihi).
Is it also possible with an external SD card? I got an SD adapter (and a SD card of course) but I don't know the commands.
I tried also to mount the internal SD but it won't work.
About the flash tool, I tried it many times but it isn't possible to flash the stock rom because if I want to flash the stock rom, it needs an IMEI number but the phone doesn't see it anymore.
I hope you can help me!
Click to expand...
Click to collapse
Download stock ROM here - Download (LG P880 Stock ROM Flashable zip file)
Rename the file update.zip
Insert micro SD card in adapter and in to the PC and copy update.zip to root of SD card.
Boot into recovery mode
Open - Install zip from sdcard or Apply update from sdcard,
locate the update.zip and hit install
Let me know if it works
If it doesn't here's the download mode method
How to Flash LG Optimus 4X HD with a KDZ File
KDZ Files (Remember to flash a compatible device or you may have problems like IMEI error or even chance of bricking your phone) I'm only giving compatible ones.
V20A_00
V20B_00
If you don't have european LG optimus 4x HD p880 I suggest you check this link and find the correct KDZ file
http://www.lg-phones.org/official-lg-optimus-4x-hd-firmware-download.html
1.Download these 3 apps: Download
2.Install B2CTools
3.Extract the KDZ_FW_UPD_EN.zip
4.Install msxml.msi (located \KDZ)
5.Extract WindowsEnabler.zip to the same folder as KDZ (ex.: KDZ\WindowsEnabler)
6.Run LGMobile update (must be on your desktop) and install the USB drivers
7.Reboot your LG Optimus 4X HD in SW Upgrade mode (remove the battery, hold vol down while inserting usb cable connected to your pc)
8.Open the Windows “Device Manager” > Modems > disable the LGE Mobile USB Modem (Windows + R Type in "devmgmt.msc" and hit enter)
9.Run as administrator KDZ_FW_UPD.exe
10.Run as administrator Windows Enabler.exe
11.After you run the app, an icon will appear on your tray, single-click on the icon until the “ON” text appears over the icon
12.Click the folder yellow folder icon next to ‘KDZ file’ and choose the .kdz file you downloaded earlier.
13.Connect your phone in S/W download mode to your PC. Let Windows install all the necessary drivers.
14.Select Type : 3GQCT. Select PhoneMode : CS_Emergency
15.Click on “Launch Software Update” and don’t click on anything else
16.Your LG phone will restart at 90% but don’t unplug it for now. Let it boot completely and wait till KDZ Updater reaches 100%.
Some LG models just shut down at 90%. You need to power on them manually without unplugging the USB cable
17.WAIT until your phone completely finishes and unplug the cable.
Don’t care about the errorlog, it’s normal. If KDZ Updater is returning a “KDZ extract error”, you probably need to re-download the KDZ file.
If you got only bootloop after flash .kdz, just do a hard reset: press and hold [vol -] and [power] until you got the “android recovery figure” and wait until they reboot again.
Sippay said:
Download stock ROM here - Download (LG P880 Stock ROM Flashable zip file)
Rename the file update.zip
Insert micro SD card in adapter and in to the PC and copy update.zip to root of SD card.
Boot into recovery mode
Open - Install zip from sdcard or Apply update from sdcard,
locate the update.zip and hit install
Let me know if it works
If it doesn't here's the download mode method
How to Flash LG Optimus 4X HD with a KDZ File
KDZ Files (Remember to flash a compatible device or you may have problems like IMEI error or even chance of bricking your phone) I'm only giving compatible ones.
V20A_00
V20B_00
If you don't have european LG optimus 4x HD p880 I suggest you check this link and find the correct KDZ file
http://www.lg-phones.org/official-lg-optimus-4x-hd-firmware-download.html
1.Download these 3 apps: Download
2.Install B2CTools
3.Extract the KDZ_FW_UPD_EN.zip
4.Install msxml.msi (located \KDZ)
5.Extract WindowsEnabler.zip to the same folder as KDZ (ex.: KDZ\WindowsEnabler)
6.Run LGMobile update (must be on your desktop) and install the USB drivers
7.Reboot your LG Optimus 4X HD in SW Upgrade mode (remove the battery, hold vol down while inserting usb cable connected to your pc)
8.Open the Windows “Device Manager” > Modems > disable the LGE Mobile USB Modem (Windows + R Type in "devmgmt.msc" and hit enter)
9.Run as administrator KDZ_FW_UPD.exe
10.Run as administrator Windows Enabler.exe
11.After you run the app, an icon will appear on your tray, single-click on the icon until the “ON” text appears over the icon
12.Click the folder yellow folder icon next to ‘KDZ file’ and choose the .kdz file you downloaded earlier.
13.Connect your phone in S/W download mode to your PC. Let Windows install all the necessary drivers.
14.Select Type : 3GQCT. Select PhoneMode : CS_Emergency
15.Click on “Launch Software Update” and don’t click on anything else
16.Your LG phone will restart at 90% but don’t unplug it for now. Let it boot completely and wait till KDZ Updater reaches 100%.
Some LG models just shut down at 90%. You need to power on them manually without unplugging the USB cable
17.WAIT until your phone completely finishes and unplug the cable.
Don’t care about the errorlog, it’s normal. If KDZ Updater is returning a “KDZ extract error”, you probably need to re-download the KDZ file.
If you got only bootloop after flash .kdz, just do a hard reset: press and hold [vol -] and [power] until you got the “android recovery figure” and wait until they reboot again.
Click to expand...
Click to collapse
Hmm..
I couldn't try the flashable zip because the recoverymode hasn't got the update mode, only in combination with ADB so I couldn't try that.
I also tried the second option with the kdz update but he is stuck at param 207 (see image).
I waited more than 20 minutes but he won't do nothing at all.
LG makes it not easy to flash
I hope there's something else I can try
did you disable the LG modem in device manager? try remove the battery then re-insert it before disable LGE Modem and start flashing.
Here's another flashing tool to flash kdz files http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG_Flash_Tool_2014.zip use CSE flash or you might get stuck in bootloop.
and try flashing the update.zip like you tried to flash cyanogenmod befoere using adb.
telephone alive!
Thanks everyone for helping me!
I stopped trying, because nothing worked.
I sent the telephone to the repair service and now my phone is alive!
Thank God I had warranty of 2 years on the phone.
They replaced some stuff in the phone (as the PCB assembly main refurb).
It wasn't a software problem, but a hardware problem.
Thanks for help!:good::good:
So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
none
I would start over. The posts on how to root are very good. There are also youtube videos you can watch. It really is very easy to root this device. if nothing else load a program called team viewer on your computer and I will root it for you, but I want you to try first. You will use something called rumrunner. PM me if you need help
AlphaMons said:
So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
Click to expand...
Click to collapse
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Are you on hboot 2.49
statmonkey said:
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Click to expand...
Click to collapse
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
mrkrowely said:
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
Click to expand...
Click to collapse
Really an excellent post it's nice to have all that in one place. I also was unable to get rumrunner to work and have used firewater quite successfully (which was part of what I was trying to point out above). Also, I was unable to get HTCdev to unlock my phone. That may or may not be about me. I am a Linux person and I think I might have had the wrong adb/fastboot at the time. The one in the android sdk did not work for me but for anyone on LInux who is interested the one in this link did http://forum.xda-developers.com/htc-one-max/help/andrenaline-rom-constant-reboot-t2853591
Once again, excellent summary, I will be bookmarking this for later.
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
bryanfritz1 said:
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
Click to expand...
Click to collapse
As far as I am aware firewater still works. I used it just a few days ago and just saw a post today http://forum.xda-developers.com/htc-one-max/help/gain-s-off-t2849836 although he doesn't clearly state that he was using sense 6,
I was running the latest Gohma when the update notification appeared on my watch. I have tried the following:
-Simply swiping left to install OTA update
-Using the tools including in Gohma's zip to restore to stock, then running update
-Both locking and unlocking the booloader and running update
-Using LG G Watch Tool (v9.7) to restore to stock and then update
-Once again, locking boatloader to try updating and unlocking to try it again
I don't know what else to try. A forum search hasn't revealed anyone else with this problem.
drdoombot said:
I was running the latest Gohma when the update notification appeared on my watch. I have tried the following:
-Simply swiping left to install OTA update
-Using the tools including in Gohma's zip to restore to stock, then running update
-Both locking and unlocking the booloader and running update
-Using LG G Watch Tool (v9.7) to restore to stock and then update
-Once again, locking boatloader to try updating and unlocking to try it again
I don't know what else to try. A forum search hasn't revealed anyone else with this problem.
Click to expand...
Click to collapse
You aren't actually restoring to stock then if you're using the Tools to restore as you should be updated to 5.0.2 when you do the restore (at least that's how it worked for me coming off Gohma), I did have to do some edits to my copy of the Restore Tools as for some reason my ADB wouldn't see the online device (even after authorized and installed) so I edited to remove adb wait-for-device and rebooted the watch into Fastboot where it restored fine.
ShadowEO said:
You aren't actually restoring to stock then if you're using the Tools to restore as you should be updated to 5.0.2 when you do the restore (at least that's how it worked for me coming off Gohma), I did have to do some edits to my copy of the Restore Tools as for some reason my ADB wouldn't see the online device (even after authorized and installed) so I edited to remove adb wait-for-device and rebooted the watch into Fastboot where it restored fine.
Click to expand...
Click to collapse
How did you do that?
I'm stuck too :<
yot2703 said:
How did you do that?
I'm stuck too :<
Click to expand...
Click to collapse
I'll check when I get home to my computer with the Restore tools sitting on it. It was part of the script that dealt with flashing. The other thing you could do is reboot into the bootloader and then manually flash in command prompt the correct files for the version you'd like to restore. I think 42Qsystem.img is 4.4w's system image and so on
I do notice that every so often, my computer will refuse to recognize the ADB interface as one. You can check in your device manager to see if this is the case for you, open Device Manager and check for "G Watch" or something similar while you have Debugging on. It will show under "Unknown Devices" right click the "G Watch" selection and hit Update Driver (you may need to install the ClockworkMod Universal ADB drivers first) and then hit Manually select a driver, it will ask you the driver type, hit ADB Interface and select any of the ADB drivers that show. Once it's installed, try again.
To skip using the tools, You'd do that by doing adb reboot-bootloader, or by swiping from the top-left to bottom-right on the screen during the LG Boot Logo, then in command prompt you'd change your directory to your Restore Tools
so cd C:\Path\To\Restore Tools\
fastboot flash <partition> <image>
So it would be something like:
fastboot flash system 42Qsystem.img to flash the system partition
fastboot flash recovery 42Qrecovery.img
fastboot flash boot 42Qboot.img
Please note that this is advanced and you will need to flash all of the image files for the version you select. The version is the 42Q in the example above.
However once I get home and look for the specific part I changed, I'll attempt to post it here.
I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
JaLex77 said:
I was getting Status 7 as well.
I flashed TWRP, did a full wipe of system, Data, Cache.
(Do not install Supersu) Reboot to Bootloader.
Fastboot Flash system, recovery, boot from LG G Watch Restore Tools.
Reboot to Recovery.
ADB Sideload option.
Adb sideload update.zip from PC.
Sucess!
Optional:
reboot bootloader
Fastboot flash TWRP
reboot
Click to expand...
Click to collapse
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Restore to stock with unlocked bootloader u cant update of its rooted.
Register ADB Driver
Lodorenos said:
I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Click to expand...
Click to collapse
There shouldn't be a yellow Triangle when the driver installs. You have to assign the proper driver.
Update Driver>Browse My computer for Driver Software>Let me Pick from a list of Drivers on my computer>Android Composite ADB Interface>Next Complete
I had received this error because I had my phone rooted when I attempted to install the OTA via the /cache method.
What I sugest to you, to get this installed properly is to download the newest version of LG G Watch Tools and restore your watch to 5.0.2 and root it, push the update to /cache and make the /cache/recovery/command file but instead of rebooting normally like you would to trigger the update, instead run adb reboot-bootloader and restore your watch again to 5.0.2. The restore leaves /cache alone so this will work. Once 5.0.2 has been restored, use the fastboot options to boot into Recovery Mode, the update will start and install properly.
I do suggest doing a factory reset after running the update, as I was experiencing some performance issues after having done this until I had done a quick reset. Now it's running fantastically.
To solve any ADB problems, you should install the ClockworkMod ADB drivers, then open Device Manager, find G Watch in there and then right click, hit Update Driver, Let me find one, choose to choose a driver manually and then tell it that it is an ADB Interface, choose any of the ADB drivers that appear and then hit next. ADB should work for you after that.
ADB however does not seem to work inside recovery for 5.0.2 as I was unable to sideload mine due to it not showing in device manager at all while in recovery mode.
Hi, here I bring you a small tutorial for upgrading your rooted Realme GT 2 Pro Global Version to latest update (RMX3301_11_A17), as you may know I am not responsible of any damage and I recommend you to back up your data.
First, uninstall all your modules from magisk (technically you could just deactivate them, I prefer uninstall though). Make sure Zygisk is deactivated and turn off all the super user permissions of your apps before the update step. You should deactivate Automatic system updates under developer settings as well.
Here the steps:
1. Go to settings and download the OTA, you´ll get the 200 mb one. Since what we need is the full OTA package, once it's been downloaded when it starts to be extracted force stop the Software Update app in your settings.
2. After previous step go to your file manager (in this case I use Mixplorer, for this you will need the app with root access) and go to the next directory: root/data/ota_package/OTA/ [a folder that starts like .ota], inside you are going to delete the ota file with .zip extension. This first two steps are a way to speed up the process of getting the full OTA.
3. Go again to your software update section in settings, you will see a notification from the app software update app, touch on continue. After that you will see a message of error, and you will see a button that says "Try again", keep clicking on try again several times. You'll see then that full OTA update will start automatically (about 5 gb in size).
4. From here you will have to wait until the "Install" button appears (it'll take a while). Next, you click install.
5. After reboot, transfer the boot.img file attached on this post to your device. Magisk patch it and transfer back to your PC.
6. Open your adb terminal, type the command adb reboot bootloader
7. Test recognition by typing fastboot devices
8. Next type: fastboot boot whatevernameofyourpatchedfile.img (it has to be in the platform tools folder)
9. Your device will boot with a temporary root, check everything is working ok in your device. After that you will go to magisk app, click on install, and in the Method section select "Direct Install", and then Let's go.
10. After reboot you'll have you magisk rooted device updated and working. Now you can install back your modules again.
boot
This method can be done on the phone with root preservation directly via Magisk. No need to copy/patch boot.img files manually, as long as you have restored image in Magisk at least once. This is explained below.
Important notes:
Do not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and patched boot.img must be flashed via fastboot to restore root.
In addition, after installing to inactive partition in Magisk, do not press restart on Magisk's prompt.
The auto-update should be disabled, including the "Auto Download" setting. Otherwise, the updater will attempt to download and install while Magisk is present, and show "Extraction Failed" error, and "Try Again". If that happens, the system will only allow to download a 5GB update instead. To reset it, you can clear Software Updater app data and cache via some root app manager.
When selecting "Restore Images" in Magisk, if a message shows in Magisk "Stock boot image not found", then you need to generate backup stock boot.img on the phone. This is only done once, but you will need a stock boot.img of your current ROM version.
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder where it will keep the stock, non-patched boot.img.
This is only done once, on any future update the error will not show.
Click to expand...
Click to collapse
The 300mb OTA update steps:
1. Go to updater and it should show 300-600mb update available. DO NOT press "Download"!
2. Go to Magisk, select to restore image. Do not restart when prompted by Magisk. If you get error, read note on top.
3. Go back to updater and select "Download". It will first download then extract. When it finishes extracting, DO NOT press Install!
4. Go back to Magisk and select install to inactive partition. Once it's done, do not restart via Magisk! Close Magisk.
5. Go back to updater, and press "Install" button
Click to expand...
Click to collapse
Extra notes:
1. If you press Download before removing Magisk, it will fail extracting and show "Try Again". Do not press try again. Go to a root app manager, and clear Data and Cache of com.oplus.ota Software updater. Then repeat the process by restoring images in Magisk first.
2. If you did press "Try Again", it will only allow you to download a 5GB update. Steps are similar as long as you restore Magisk. You might be also able to clear data and cache like in step above to reset it back to smaller update, but I haven't tested this yet.
3. If you restart by Magisk prompt, it will soft-loop. You can hold Vol Up + Power until it boots into non-root partition. Go to updater and press install. It will boot to rooted partition.
4. If you pressed Install in updater before installing Magisk to inactive partition, it will boot to updated partition without root.
5. I have tested the update methods with simply Uninstall -> Restore Images, while I had Magisk modules such as BCR, Shamiko, USF, LSPosed Zygisk. It works fine without the need of removing each module.
Extra side note: Update file is downloaded to: /data/ota_package/OTA/.otaPackage/mymanifest(...).zip
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
shivrajsingh said:
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
Click to expand...
Click to collapse
I know what you mean, in fact thank you for telling me that procedure is working well on our device hahaha, since there's no proper flashing tool and no TWRP yet, the idea behind that lengthy process is trying to reduce the risks to minimum n.n
Just confirmed that this works for a 300mb (before restoring images) update file instead of the full 5GB (after restoring images), updated the guide above.
vanya.ag said:
boot
Click to expand...
Click to collapse
now my fingerprint is broken
Quake94 said:
Notes:
When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.
Click to expand...
Click to collapse
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Terrorigel97 said:
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Click to expand...
Click to collapse
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Quake94 said:
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Click to expand...
Click to collapse
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Terrorigel97 said:
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Click to expand...
Click to collapse
Lock only on clean, stock rom as per guide in the other thread.
Can't lock on rooted, but rooted can be reversed to stock clean.
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
I confirm you have to reboot via the installer and not via Magisk, since I had to manually flash boot.img multiple times in the past.
Quake94 said:
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
Click to expand...
Click to collapse
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
GIutton said:
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
Click to expand...
Click to collapse
There are four modes:
bootloader - adb reboot bootloader
fastboot - adb reboot fastboot (or the key combo)
fastbootd - fastboot reboot fastboot (from being already in fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
In my case the fastboot mode would start ok, just not the bootloader mode.
I didn't try fastbootd, but it would probably start ok.
I don't understand the fastbootd mode well though. I read somewhere that it is fastboot in Data partition.
I haven't tested rebooting to bootloader after fix, but can let you know.
EDIT: Booting to bootloader from fastboot (fastboot entered with key combo) gives me the mascot again, then it goes immediately back to fastboot. So I think I am in same position as you
Running "adb reboot fastboot" started "Fastbootd" mode (the one with wipe data/reboot/power off)
Running "fastboot reboot fastboot" from the "Fastbootd" would restart to "Fastbootd"
Running "fastboot reboot recovery" from the "Fastbootd" showed success, but 1. phone stayed in "Fastbootd" and 2. The phone deauthorized ADB (but still showed in device manager as "ossi" device)
Running "adb reboot bootloader" from System, showed the mascot and started the regular Fastboot.
Running "fastboot reboot fastboot" while the regular Fastboot was on, started "Fastbootd"
My suspicions are:
1. Regular fastboot mode is the one with green "START" on top. Somehow it is the same as bootloader. This is confirmed by Realme guide for unlocking/locking bootloader - they ask to use adb reboot bootloader, and then run a fastboot command.
2. "Adb reboot fastboot" starts the "userspace" fastboot called "fastbootd" which is isolated from bootloader and kernel.
This would mean the modes are:
bootloader/fastboot -> adb reboot bootloader (or the key combo)
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
So you can get into the start menu (fastboot/bootloader) by using the button combo but if you try fastboot reboot bootloader it shows a mascot with chinese letters then goes right back to the start menu and adb reboot bootloader shows the mascot and goes into the start menu as well? I think your phone is fine. . . fastboot and the bootloader should both be the start menu right or is there a difference?
For me I get the realme logo then a screen glitch and boots to the system when I try the button combo. When I try adb reboot bootloader I get a mascot with Chinese letters then a screen glitch then boots into the system.
Added some extra notes in my guide. If Auto download was enabled in About Device -> Software Update, the updater will display "Extraction Failed" since it attempts to download and extract update while Magisk is present. It also locks itself out of "Local install". The updater will download 5GB update instead on a retry, and 5GB method would be used.
With the Auto download disabled, user can Restore Images via Magisk and then download and install the update.
I will test this on the next update rollout.
Revised guide after C.12 to C.13 update and testing the smaller update method. The process is much more straightforward than I initially thought. No need for "Local update".