Hello,
I have the device HTC Desire 825 with the pre-installed 6.0.1. I have tried loads to root my device, I have tried all the one-click root ways from Kingo etc but they all fail.
I tried to find a way to flash the device but on the list of devices, the HTC Desire 825 is not on the list. Not sure if there is a way to root it or not, I done it before on previous devices but never been stuck like this. If someone knows a way, please tell me how, it would be much appreciated
Thank you,
zemauk said:
Hello,
I have the device HTC Desire 825 with the pre-installed 6.0.1. I have tried loads to root my device, I have tried all the one-click root ways from Kingo etc but they all fail.
I tried to find a way to flash the device but on the list of devices, the HTC Desire 825 is not on the list. Not sure if there is a way to root it or not, I done it before on previous devices but never been stuck like this. If someone knows a way, please tell me how, it would be much appreciated
Thank you,
Click to expand...
Click to collapse
Why not you try goes to HTC dev..might be they knew it much better..I mean rooting your devuces
HTC dev - all other devices.
Twrp found in a discussion here in one of the threads.
Latest Superuser Beta zip or img.
brunkonjaa said:
HTC dev - all other devices.
Twrp found in a discussion here in one of the threads.
Latest Superuser Beta zip or img.
Click to expand...
Click to collapse
And how I can install TWRP to use for root my device?
Xxshark888xX said:
And how I can install TWRP to use for root my device?
Click to expand...
Click to collapse
Go to HTC dev site. Register. Log in. Look for "unlock bootloader" option. Click on it. Follow instructions. Great, you have now unlocked your bootloader !
Now, in order to unlock bootloader you had to download HTC fastbooot . Open the folder where that HTC fast boot has been extracted.....
Now, previously downloaded Superuser and Twrp files......
Place them in that folder where you extracted your HTC fastboot files.
Right click on empty space anywhere inside that folder while holding "shift", and you will get an option to "open cmd window here". Click on it. Type "adb devices". Your phone should show as some numbers followed by the word device ( "1234567 device").
Your device should be recognized and you can continue to the next step. If it isn’t recognised then you should re-install all the USB Drivers for your device.
Next, enter the following command line in CMD in order to flash the TWRP Recovery files:?*fastboot flash recovery "name of downloaded recovery".img.
When the TWRP Recovery file is successfully installed, CMD will display a confirmation message. Disconnect the device from computer now.Use the Volume buttons to select ‘HBOOT’ option on your smartphone and select it by pressing Power. Test to see if the RECOVERY mode works by selecting the ‘RECOVERY’ option. Your phone should boot into TWRP Recovery mode now and this means that the install has been successfully completed.
To install Superuser, repeat above steps BUT instead of typing "Twrp xxxxxx.img" type "name of superuser file". Once you have confirmation of the file being sent, disconnect from PC, enter recovery, choose install, and click on the superuser file.
Little tip: I spent hours trying to send both Twrp and superuser files to the phone with all kinds error messages showing inside cmd screen. File too big, can't read file, destination unreachable...... then I found simple solution:
Inside the fastboot folder I created new empty folder.
I copy/pasted Twrp and superuser files inside of it.
Opened cmd folder inside of that new folder and tried sending files again, one at the time. It worked flawlessly straight away.
Little tip 2: if you have trouble writing the names of your Twrp and superuser files in your cmd window, you can do the following:
Type "fastboot flash recovery", press space bar once, now left click on the required file in you fastboot folder (Twrp or superuser) and drag it across into your cmd window.
If you need anything else, feel free to ask. When dealing with this kind of fiddling with your device, no question is stupid or irrelevant.
brunkonjaa said:
Go to HTC dev site. Register. Log in. Look for "unlock bootloader" option. Click on it. Follow instructions. Great, you have now unlocked your bootloader !
Now, in order to unlock bootloader you had to download HTC fastbooot . Open the folder where that HTC fast boot has been extracted.....
Now, previously downloaded Superuser and Twrp files......
Place them in that folder where you extracted your HTC fastboot files.
Right click on empty space anywhere inside that folder while holding "shift", and you will get an option to "open cmd window here". Click on it. Type "adb devices". Your phone should show as some numbers followed by the word device ( "1234567 device").
Your device should be recognized and you can continue to the next step. If it isn’t recognised then you should re-install all the USB Drivers for your device.
Next, enter the following command line in CMD in order to flash the TWRP Recovery files:?*fastboot flash recovery "name of downloaded recovery".img.
When the TWRP Recovery file is successfully installed, CMD will display a confirmation message. Disconnect the device from computer now.Use the Volume buttons to select ‘HBOOT’ option on your smartphone and select it by pressing Power. Test to see if the RECOVERY mode works by selecting the ‘RECOVERY’ option. Your phone should boot into TWRP Recovery mode now and this means that the install has been successfully completed.
To install Superuser, repeat above steps BUT instead of typing "Twrp xxxxxx.img" type "name of superuser file". Once you have confirmation of the file being sent, disconnect from PC, enter recovery, choose install, and click on the superuser file.
Little tip: I spent hours trying to send both Twrp and superuser files to the phone with all kinds error messages showing inside cmd screen. File too big, can't read file, destination unreachable...... then I found simple solution:
Inside the fastboot folder I created new empty folder.
I copy/pasted Twrp and superuser files inside of it.
Opened cmd folder inside of that new folder and tried sending files again, one at the time. It worked flawlessly straight away.
Little tip 2: if you have trouble writing the names of your Twrp and superuser files in your cmd window, you can do the following:
Type "fastboot flash recovery", press space bar once, now left click on the required file in you fastboot folder (Twrp or superuser) and drag it across into your cmd window.
If you need anything else, feel free to ask. When dealing with this kind of fiddling with your device, no question is stupid or irrelevant.
Click to expand...
Click to collapse
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Xxshark888xX said:
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Click to expand...
Click to collapse
Oh the joys of bloatware!!!!!!!
Here's what I did: after trying to remove it, and soft bricking ????, I installed xposed, lucky patched and Greenify. In this forum I am not allowed to explain how I got specific version of Greenify that works with lucky patcher patch in order to gain pro version, so I won't explain it ????.
I simply greenified most of bloatware, so it's out if the way.
I know it doesn't really answer your question but at least it allows to keep the beast at bay.
brunkonjaa said:
Oh the joys of bloatware!!!!!!!
Here's what I did: after trying to remove it, and soft bricking ????, I installed xposed, lucky patched and Greenify. In this forum I am not allowed to explain how I got specific version of Greenify that works with lucky patcher patch in order to gain pro version, so I won't explain it ????.
I simply greenified most of bloatware, so it's out if the way.
I know it doesn't really answer your question but at least it allows to keep the beast at bay.
Click to expand...
Click to collapse
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Xxshark888xX said:
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Click to expand...
Click to collapse
Unlike stock Android, manufacturer skins like TouchWiz, Sense etc. come with a plethora of pre-loaded apps that you can’t uninstall. Be careful.
Xxshark888xX said:
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Click to expand...
Click to collapse
Hi! Did you manage to uninstall any of the bloatware?
Xxshark888xX said:
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Click to expand...
Click to collapse
The uninstalled Apps will crawl back after reboot because the device is still S-ON. There are couple ways to handle this. One is to S-OFF the device using Sunshine or similar app. Method 2 is using TWRP. Use the TWRP built-in file explorer, mount system, head to where the apps are and delete the ones you wouldn't need.
Hello guys. Does someone have a back up of the htc 825 stock recovery.img? Maybe someone can extract the stock recovery and share it here please ?
stenlibi said:
Hello guys. Does someone have a back up of the htc 825 stock recovery.img? Maybe someone can extract the stock recovery and share it here please ?
Click to expand...
Click to collapse
Hi, did you manage to find the recovery img?
I need to flash it instead of buggy twrp, searched for hours and nowhere to be found
Ok, i've managed to find it This is the stock recovery IMG, working fine, extracted from original firmware.
https://mega.nz/#!yYd30a7A!hK7RoQjhWkG8S2nS3__B8xbnwAssN4QI59rXJyQ1y9o
Credits go to nkk71 https://forum.xda-developers.com/member.php?u=2605798 for the great tool to exctract the firmware image,
without it i wouldn't accomplish the task.
If the link will die, PM me, i'll reupload.
Related
I am having trouble finding how do this ..i am not even sure if its been achieved ..hope you guys have come up with something !! (Or i cud flash2.2 again and then install custom recovery and then flash 2.3 back but i dont want to go through all taht trouble )
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf
then use superoneclick (psneuter)
This is my problem these days.
There is no root application for original rom 2.3.3
Download the attached ZIP and flash the recovery via LGMDP. (CWM 3.1.0.0 included, if you want something else, replace it with whatever you want.)
- Unzip, run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job.
abccccc said:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf
then use superoneclick (psneuter)
Click to expand...
Click to collapse
Frozen while running psneuter.
(superone click 1.9.5)
doktornotor said:
Download the attached ZIP and flash the recovery via LGMDP. (CWM 3.1.0.0 included, if you want something else, replace it with whatever you want.)
- Unzip, run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job.
Click to expand...
Click to collapse
Thanks mate.
Works great. Its automatically rooted and custom recovery. Should I install superuser too?
optimusblack said:
Thanks mate.
Works great. Its automatically rooted and custom recovery. Should I install superuser too?
Click to expand...
Click to collapse
LOL, yeah, you definitely need that. Flash this from recovery. Once done, grab Busybox Installer from market and install busybox.
I updated my HTC EVO. And now have 2.3.3 but its not rooted anymore I want to root my phone please help me. SMH
Sent from my PC36100 using XDA App
uninvited03 said:
I updated my HTC EVO. And now have 2.3.3 but its not rooted anymore I want to root my phone please help me. SMH
Click to expand...
Click to collapse
Wrong section of the forum, dude... This one is for LG Optimus One.
doktornotor said:
Download the attached ZIP and flash the recovery via LGMDP. (CWM 3.1.0.0 included, if you want something else, replace it with whatever you want.)
- Unzip, run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job.
Click to expand...
Click to collapse
I followed the steps.. But ,it is still un-rooted..
clawsright said:
I followed the steps.. But ,it is still un-rooted..
Click to expand...
Click to collapse
Of course... It is not supposed to root your phone at all!!! It flashes custom recovery so that you could flash a rooted ROM from there, or flash the superuser ZIP (see my howto)
People, really - please think about what you are doing.
optimusblack said:
Frozen while running psneuter.
(superone click 1.9.5)
Click to expand...
Click to collapse
Hi guys, regarding the problem about rooting the original GB, it can be done, and it's not that complicated.
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20G GB ROM.
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse, after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf,
Do not close the window, live it like that.
7. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it, after that start SuperOneClick.exe.
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
This is the method that i did and it worked like a charm.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you is you allow or deny it's access. click allow.
If you do not get the Allow Deny message the root was not completed successfully. do a factory reset and try again the same steps.
If you do get the message you have rooted the phone, go to market and update the superuser and install busy-box. After you can install a custom recovery. Also you can install your preferred Kernel if you don't like the stock one.
As a recovery i use AmonRa i don't like Clockworks. if you like clockworks install rom manager and install it from there. if you like amonRA download it and follow the steps from here.
I don't know this will work or not. But if it will work the cheers to you boy.
g0mezz said:
Hi guys, regarding the problem about rooting the original GB, it can be done, and it's not that complicated.
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20G GB ROM.
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse, after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf,
Do not close the window, live it like that.
7. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it, after that start SuperOneClick.exe.
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
This is the method that i did and it worked like a charm.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you is you allow or deny it's access. click allow.
If you do not get the Allow Deny message the root was not completed successfully. do a factory reset and try again the same steps.
If you do get the message you have rooted the phone, go to market and update the superuser and install busy-box. After you can install a custom recovery. Also you can install your preferred Kernel if you don't like the stock one.
As a recovery i use AmonRa i don't like Clockworks. if you like clockworks install rom manager and install it from there. if you like amonRA download it and follow the steps from here.
Click to expand...
Click to collapse
After step 5 i forgot to write connect the phone in USB debugging, and when you put the first command adb devices is should find your device.
@sweetbinodray: this method works 100%, i told you i tested it.
it's worked man
neoonix78 said:
it's worked man
Click to expand...
Click to collapse
Told you .
i get a lot of fc of superuser when i try to open apps that requires root permission
neoonix78 said:
i get a lot of fc of superuser when i try to open apps that requires root permission
Click to expand...
Click to collapse
What is fc?
and if you mean that the applications that require root prompts the super user for access is normal.
g0mezz said:
Hi guys, regarding the problem about rooting the original GB, it can be done, and it's not that complicated.
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20G GB ROM.
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse, after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf,
Do not close the window, live it like that.
7. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it, after that start SuperOneClick.exe.
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
This is the method that i did and it worked like a charm.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you is you allow or deny it's access. click allow.
If you do not get the Allow Deny message the root was not completed successfully. do a factory reset and try again the same steps.
If you do get the message you have rooted the phone, go to market and update the superuser and install busy-box. After you can install a custom recovery. Also you can install your preferred Kernel if you don't like the stock one.
As a recovery i use AmonRa i don't like Clockworks. if you like clockworks install rom manager and install it from there. if you like amonRA download it and follow the steps from here.
Click to expand...
Click to collapse
This method did not work for me .. I have V20B Stock Gingerbread. Is there any way to root it .??
If not please guide me to return to stock froyo with proper baseband .
try this
KEEP IN MIND THAT YOU HAVE TO MAKE A NAND BACKUP ALWAYS WHEN YOU ARE MAKING A ROM FLASH.
Good luck.
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
I was going to flash CM 11 today and kept getting this error code" no recoveries found for your device".in twrp!....Anthing i try to flash through twrp fails..could the recovery image itself been corrupted? .. I guess twrp wont recognise my device type ,iTried uninstall re installing twrp a half dozen times but to no avail. tried using search but didnt find anything defininitve,im sure some one has ran across this before ,but its a new one to me ,twrp has always run flawless for me .. any ideas anyone?
Get a fresh copy here http://techerrata.com/browse/twrp2/jewel
After flashing twrp type fastboot erase cache
heliguide62 said:
I was going to flash CM 11 today and kept getting this error code" no recoveries found for your device".in twrp!....Anthing i try to flash through twrp fails..could the recovery image itself been corrupted? .. I guess twrp wont recognise my device type ,iTried uninstall re installing twrp a half dozen times but to no avail. tried using search but didnt find anything defininitve,im sure some one has ran across this before ,but its a new one to me ,twrp has always run flawless for me .. any ideas anyone?
Click to expand...
Click to collapse
Did you use the version of TWRP posted in the OP of the CM11 thread? You have to use it, otherwise the flash will fail.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Did you use the version of TWRP posted in the OP of the CM11 thread? You have to use it, otherwise the flash will fail.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
^This.
I also compiled a version with the updated kernel: http://tinyurl.com/TWRP-Recovery-2-6-3-0-selinux
Essentially the same as deck's, just the font in recovery appears much larger and more readable .
Thanks for the help guys!... but im still not getting it ..twp must be really messed up for me .. i downloaded both versions of twrp ..captain t/backs and the one from topic .. and i cant find either or them in "install" mode of twrp.,however i CAN find them in file manager mode,which is baffling, but when i try to move them to some place flashable they are nowhere to be seen!..i also can see them in ES file explorer and tried to move them that way but same result...maybe my download path is incorrect?..this one has me stumped.. anyone have any advice?
heliguide62 said:
Thanks for the help guys!... but im still not getting it ..twp must be really messed up for me .. i downloaded both versions of twrp ..captain t/backs and the one from topic .. and i cant find either or them in "install" mode of twrp.,however i CAN find them in file manager mode,which is baffling, but when i try to move them to some place flashable they are nowhere to be seen!..i also can see them in ES file explorer and tried to move them that way but same result...maybe my download path is incorrect?..this one has me stumped.. anyone have any advice?
Click to expand...
Click to collapse
You have to flash the image files via fastboot, not through recovery.
no wonder i couldnt do it ..lol..havnt to used fast boot since the og evo days hope i can remember how..
Connect the phone to your pc and boot into bootloader, then go to fastboot.
you can test if your comp sees your phone by using
Code:
fastboot devices
Then, just open up cmd wherever your recovery image is stored (if on pc) by holding shift and right clicking. Then in the code below, replace recovery.img with the name of the recovery file you have.
Code:
fastboot flash recovery recovery.img
sorry if im turning this thread into a fastboot tutorial.. but i have the phone in usb fast boot .. downloaded sdk again and when i type in cmd Fast boot .. i get " not recognized as internal or Internal command".. so its not recognizing phone?
heliguide62 said:
sorry if im turning this thread into a fastboot tutorial.. but i have the phone in usb fast boot .. downloaded sdk again and when i type in cmd Fast boot .. i get " not recognized as internal or Internal command".. so its not recognizing phone?
Click to expand...
Click to collapse
Open the cmd from the platform tools folder
ok so downloaded sdk manager .. and maybe i didn't download the right version or something, but nothing will "open up" in sdk .. perhaps i need some drivers or something?.. cause it shows everything is installed .. tools, platform ect .. what i downloaded dosnt look like anything ive seen looking around the web.
heliguide62 said:
ok so downloaded sdk manager .. and maybe i didn't download the right version or something, but nothing will "open up" in sdk .. perhaps i need some drivers or something?.. cause it shows everything is installed .. tools, platform ect .. what i downloaded dosnt look like anything ive seen looking around the web.
Click to expand...
Click to collapse
This is what I use http://developer.android.com/sdk/index.html
You can also download the version that's included in my Hboot guide (top link in my sig). It's not the entire SDK-just ADB & Fastboot. It's what I use. Just download and install. Once installed, highlight the file & hit Shift+right click on mouse, and you're ready to go.
Sent from my HTC EVO 4G LTE
I'm sorry if this isn't the right place.
I rooted my LG G2 D802 around 2 months ago, and completely forgot about it.
I got the Kitkat update about 5 hours ago, and stupidly downloaded it.
The phone got stuck in a team win bootloop and again, in a bit of a panic I wiped the phone (not thinking of just restoring my back up from when i rooted the device)
after that didn't solve anything, i reverted to google. I found a guide on here for my exact problem http://forum.xda-developers.com/showthread.php?t=2451696
I read it carefully and proceeded to follow this by the letter. I think I messed up though, with the 'ADB' thing, the last i remembered about it was using it to root the device, so I followed to guide but using the root folder i had used. now I'm no longer in a team win bootloop, I'm not in a LG splash screen boot loop, I can just about manage to get into recovery and get back to team win, but can't get into download mode.
I really wasn't looking to replace this device until the LG G3 got released, and don't really have the money to spare - so i'm really hoping this is fixable.
a note is, to root the device i followed a guide, and the TWRP (I'm not actually sure) I think i just went with it and managed it so i'm not very good when it comes to the terms, and stuff like that, any help would be greatly appreciated!
I can use a Win7 laptop to do whatever is needed, it is an EE LG G2 D802, UK, 16GB black.
I don't have insurance, I kept pushing myself to wait to do anything like this until I had insurance, but at 2 in the morning, nothing to do, ready to root - It's hard to resist.
(I do have the USB drivers on my laptop)
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
es0tericcha0s said:
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
Click to expand...
Click to collapse
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
I have just had another read through, mainly the comments and that guide seems to get you to the point where you can get into recovery and enter those commands in the guide on my opening post - i can get into recovery and i did both fixes, the one using adb if using the adb in the root folder on my laptop i used to root the device is okay, and then again using the terminal emulator in recovery, after neither worked (actually, the terminal emulator one got me from a TWRP bootloop into an lg splash screen bootloop, after reading into thr comment to about page 7 there was an additional line to the terminal emulator method changing only the /fota to /misc which did nothing for my device. The fix there simply changed the type of bootloop i am in
yoalphadied said:
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
Click to expand...
Click to collapse
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
es0tericcha0s said:
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
Click to expand...
Click to collapse
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
yoalphadied said:
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
Click to expand...
Click to collapse
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: https://mega.co.nz/#!rU0RkSaK!JzUCoZ5emWOsc_Tw6h8a3JZtRNT1-JvGvc8EC_u9rnI
adb and fastboot files: https://mega.co.nz/#!SJ8ijCKY!UKpr4ufVyPq4DVL2i90RI9CD7TX5AETPHrcqMQdpG5w
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Just making sure I understand correctly, the 'rom' i need ks the stock rom, right? Im not looking to root again as the whole reason i rooted was because it was everywhere that ee werent releasing the kitkat update for the g2, since they have now i dont need root anymore.
Ill try this fix later on and tell you if it worked! Thanks
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
yoalphadied said:
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
Click to expand...
Click to collapse
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
http://forum.xda-developers.com/showthread.php?t=2736854
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
es0tericcha0s said:
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
Click to expand...
Click to collapse
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
yoalphadied said:
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
Click to expand...
Click to collapse
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
Okay, I just tried pushing the rom, the line entered, i got no return so far but it won't allow me to type anything else in the CMD, i'm guessing its because it's pushing the file?
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
The recovery is working fine, but after factory resetting, and then trying to install the rom.zip it tries to open it
then e: cant open /data/media/rom.zip
(bad)
installation aborted
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
yoalphadied said:
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
Click to expand...
Click to collapse
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
es0tericcha0s said:
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
Click to expand...
Click to collapse
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
yoalphadied said:
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
Click to expand...
Click to collapse
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
*EDIT*
install Kernal & supersu doesn't resolve the issue, going to try the new rom you posted now
yoalphadied said:
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
Click to expand...
Click to collapse
That's what I would do. Won't make it worse. Might help. If not, it's only a few more minutes altogether to try. Just make sure to wipe cache and dalvik cache.
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Okay, I came across another problem.
with the several versions of the same ROM at /sdcard/ my memory was running low, so i formatted it - then it wouldn't let me push anything to it, anyway i sorted that (can't remember how) and then installed the Kernal and superuser, which didn't seem to sort anything, but I did a little digging and mounted all the directories on Philz.
Then after I restarted the phone, whilst trying to get into recovery I heard the 'LG' splash screen animation noise. and then the phone loaded up the country setting - and then I got an error which made the screen unresponsive, I tried reloading to get yet another error, similar but not the same.
I booted into recovery, did a factory reset and again rebooted the phone and now it works, with the Knock Code! thank you so much you have saved my phone..
Is there anything I can do to say thank you properly, you've just saved me over £250
Hi guys
I've tried everything, i bought this watch today and i was so hyped about it.
I tried to update it to 6.0.1 using adb on my mac.
The problem is when i do this command "adb reboot recovery" and then "adb devices" it shows no devices! (before entering recovery it actually shows the device in the list!
This is so wierd and there is absolutely no solution that worksfor me... anyone has any ideas?
Edit: The problem more clearly:
Ok guys so the problem was that my LG G Watch (square) for some unknown reason wasn't available in recovery mode through adb, that means when i would use the command "adb devices" in recovery mode, i would see the empty list without any devices, while anywhere outside the recovery (system, fastboot etc) i was able to communicate with the device. (Since i was so frustrated i didn't make it clear enough in the original post ) And my watch was on 4.4! ( :| )
The solution:
Ok, so the problem was the watch, because i tried a OS X (and a windows on the same mac) and 2 windows laptops, all with drivers installed (and done the "update driver..." stuff on all) and the problem still persisted.
This solution is for people whose device is not displayed while in the recovery mode in cmd/terminal.
This is what i did: (i didn't do this in the order because i literally tried every solution on the internet! but this is the order that i was finally able to solve the problem with.)
1. I downloaded this tool from this topic (go to the link, click on LG G Watch > G watch script tool > LG G Watch Restore Tools V9.8.zip)
2. Run this bat (i used a windows but it works on the mac too) 1 LG G Watch Tools for Windows.bat
3. Let it recognize the device
4. When the blue list comes up choose 4 ( you should be in bootloader)[cmd > adb reboot bootloader] when it's done, your device should be on 5.1.1.
5. Download this tool from this topic
6. In cmd/terminal type "adb reboot bootloader" then type "fastboot flash recovery [draggedfile] and drag the downloaded .img to the cmd and press enter.
7. Now you have installed a custom recovery called CWM
8. In cmd type "fastboot reboot" then after reboot "adb reboot recovery"
9. Now inside this tool swip down to "install ..." and swip (to right i guess) and stay here on the watch.
10. Now in cmd type "adb push -p [draggedfile] /sdcard/0/Download" and drag the 6.0.1 OTA update and press enter
11. Now the update is in your device as a zip file in this path : /sdcard/0/Download (it didn't work when i wanted to push it to "/sdcard" folder so i had to go deeper)
12. Now swip on install from sdcard and navigate to the path and choose the zip file.
13. Done! you have successfully updated your device without going into recovery mode!
Thank you very much @lfom for sticking to this topic and helping out in the process!
I just tried it with windows as well and ain't working... im so frustrated...
There's a guide in General section that you may want to read:
http://forum.xda-developers.com/g-watch/general/guide-how-to-fix-6-0-1-adb-bug-t3347122
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
miladkalbasi said:
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
Click to expand...
Click to collapse
So you are on 4.4 and want to update? What else? Rooted and custom recovery?
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
lfom said:
So you are on 4.4 and want to update?
Click to expand...
Click to collapse
Yes, i bought this watch yesterday and it's on 4.4 and i want to update to 6.0.1 (or any newer update)
lfom said:
What else?
Click to expand...
Click to collapse
I have never had developer experience with any android device before so i learned everything in like 6-7 hours, therefore there is a high probability that i might have made mistakes in the way but here's what i have done so far:
1. i tried to update the watch from "About" on the watch itself but kept getting "Something went wrong" error and couldn't fix it.
2. so i moved on to use my mac to do the update which took me 4-5 hours to figure out what SDK platform tools, ADB, OTA updates, bootloader, fastboot etc means.
3. i figured out all this and went on until i reached here: i have to use this commend in the terminal (it's like windows cmd): adb devices
so that i know my device is there and authorized on the companion android device (i see the device in the command shell), i then proceed to this command : adb reboot recovery , as soon as i type this command and press enter, the device reboots and enters recovery mode but it is also vanished from the system, by typing adb devices i no longer see it, i just see an empty list.
4. i also did unlock, wipe, restore back to stock ROMs (5.1.1 ROMS), tried TWRP (i then realized i can't do OTA updates with this tool)
5. i did all of these steps several times and always got the same results!
6. i also tried the windows on my mac and got the exact same results.
7. i tried 3 different windows laptops in the household (2 of which run win 8 and one runs win 7) but was not able to make it through installing the drivers (i couldn't see the android device when i clicked on update drivers...)
lfom said:
Rooted and custom recovery?
Click to expand...
Click to collapse
no i haven't rooted the device
lfom said:
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Thank you very much for your suggestion, i have already tried that and it doesn't actually give me any more options that i already have.
I've come to the believe that it's either my laptop (which only has 2 USB 3.0 ports and some people say it causes issues) or my watch. I have to try to use a different computer but i don't think i can access more computers or solve the driver problem on the 3 existing ones.
I really wish i could solve this by myself, i live in a country that i can't access warranty and stuff so i either have to fix it myself or get a professional's help.
i found this topic as well, that's exactly my problem.
I can communicate with the watch in bootloader and TWRP but not in the recovery mode (stock)
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
lfom said:
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
Click to expand...
Click to collapse
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
miladkalbasi said:
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
Click to expand...
Click to collapse
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
lfom said:
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
Click to expand...
Click to collapse
I solved the problem!
Funny thing is i didn’t see your answer and fixed it by myself but you actually proposed exactly what i had to do! Thank you very much for your effort and spending your time on this topic!
For others who might run into the same problem in the future I'm gonna update the first post and say what i did.
Cheers!