IOroot
IOroot was originally a Windows script to root the LG G2 on 4.2.2 made by IOMonster... based on the original adb backdoor found by GiantPune and later posted by jcase.
The script has grown to support various other LG devices on Android 4.0 - 4.4.2... 4.4.2 kk_root.zip by autoprime. Current IOroot25r1 by autoprime.
Supported devices include LG Optimus G, G2, G3, G Pro, G Pro 2, G Flex and G Pad just to name a few.
4.4.2 root will NOT work for you if you cannot get into the stock recovery menu w/the "adb reboot recovery" command.
Check the supported devices list below. You may have to downgrade to 4.2.2 or below and root that instead.
Or your device may not be supported at all. Again.. check the supported device list below.
Current Version - IOroot25 refresh 1
Download IOroot zip, extract and run script to root. ADB must be enabled (USB Debugging ON).
Click the button below for IOroot device support list, manual and automated root and other info.
Device Model and Firmware Supported List:
LG G Pad - 4.4.2 Only
LG Optimus G - all 4.2.2 and 4.4.2
LG G2:
AT&T D800 - D80010d/D80010o/4.4.2
D801 - TMO(all 4.2.2 // No 4.4.2 support), CLR(all 4.2.2 // 4.4.2 ??), WND(all 4.2.2 // 4.4.2 ??), VTR(all 4.2.2 // 4.4.2 ??)
D802 - all 4.2.2 and 4.4.2
D803 - all
D805 - all
D806 - all
F320K - Shipping 4.2.2 ROM/F320K20a/20f // 4.4.2 ??
F320L - Shipping 4.2.2 ROM/F320L20b/20e // 4.4.2 ??
F320S - Shipping 4.2.2 ROM/F320S20a/20g // 4.4.2 ??
Sprint LS980 - All 4.2.2 and 4.4.2
Verizon VS980 - All 4.2.2 and 4.4.2
LG G Flex:
F340 series - All 4.2.2 // 4.4.2 ??
D950 - All 4.2.2 // No 4.4.2 support
D955 series - All 4.2.2
D958 series - All 4.2.2 // No 4.4.2 support
D959 - All 4.2.2 // No 4.4.2 support
LS995 - All 4.2.2 and 4.4.2
LG G Pro - All 4.4.2 Only
LG G Pro 2:
F350 series - Shipping ROM // 4.4.2 ??
D838 - Shipping ROM // 4.4.2 ??
LG G3
F400 Series - Shipping ROM
Manual Root Method:
Code:
[B][SIZE="2"]Windows Drivers:[/SIZE][/B]
[I]Verizon Drivers - [URL="http://bit.ly/1ibRvc3"]HERE[/URL]
Drivers for everyone else - [URL="http://bit.ly/18EPHZN"]HERE[/URL][/I]
[B]4.4.2 Manual Root:[/B]
[SIZE="1"]
Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]
[B]1. adb devices[/B]
[B]2. adb reboot recovery[/B]
(when booted in recovery, select: 'apply update from adb' with power button)
[B]3. adb sideload kk_root.zip[/B]
You should see [URL="http://forum.xda-developers.com/showthread.php?p=51530027"]DAT ROOT[/URL] when finished.
reboot phone. done.
[B]4.2.2 Manual Root:[/B]
[SIZE="1"]Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]
copy/paste commands below.. hitting enter/return after each line.
Linux/Mac users may have to enter ./ before adb on each line.
Example: ./adb push g2_security /sdcard/g2_security
[SIZE="1"][B]1:[/B] [B][I]adb devices[/I][/B]
(make sure it sees your device; if "offline" turn on phone/unlock and accept RSA key prompt)
[B]2:[/B] Choose next line based on model and firmware version:
AT&T D80010d (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
AT&T D80010o/10q: [B][I]adb push ytiruces_1a_att /sdcard/ytiruces_1a[/I][/B]
KT F320k (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
KT F320K20a/20f (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
LGU F320L (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
LGU F320L20b/20e (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
D802(T) (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
D803 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
D805 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
D806 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
SKT F320S (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
SKT F320S20a/20g (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
Sprint LS980ZV7/ZV8: [B][I]adb push g2_security_spr /sdcard/g2_security[/I][/B]
Sprint LS980ZVA (OTA): [B][I]adb push ytiruces_1a_ls980 /sdcard/ytiruces_1a[/I][/B]
T-Mobile D80110c (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
T-Mobile D80110g (OTA): [B][I]adb push ytiruces_1a_tmo /sdcard/ytiruces_1a[/I][/B]
Verizon VS98010B (Shipping ROM): [B][I]adb push g2_security_vzw /sdcard/g2_security[/I][/B]
Verizon VS98011A/12B (OTA): [B][I]adb push ytiruces_1a_vzw /sdcard/ytiruces_1a[/I][/B]
Videotron D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
Wind D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
F340-Series (4.2.2): [B][I]adb push ytiruces_1a_F340JB /sdcard/ytiruces_1a[/I][/B]
D950 (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D955-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D956-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D958-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D959 (4.2.2): [B][I]adb push ytiruces_sumtz /sdcard/ytiruces_sumtz[/I][/B]
LS995 (4.2.2): adb push ytiruces_1a_ls995 /sdcard/ytiruces_1a
F350K/L/S (4.4.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
[B]********************************************************
This next depends on your computer/phone model...
USB Connection Mode needs to be toggled.
Ways to do this are listed below...
a. Unplug usb cable from phone then re-plug.
b. Toggle USB mode from Charge to MTP back to Charge
c. Toggle USB mode from Ethernet to MTP back to Ethernet (VZW users)
********************************************************[/B]
[B]3:[/B] [B][I]adb shell[/I][/B]
(you should now see a # instead of a $. # = root)
[B]4:[/B] [B][I]exit[/I][/B]
[B]5:[/B] [B][I]adb shell "mount -o remount,rw /system"[/I][/B]
[B]6:[/B] [B][I]adb push su /system/xbin/su[/I][/B]
[B]7:[/B] [B][I]adb push su /system/xbin/daemonsu[/I][/B]
[B]8:[/B] [B][I]adb push install-recovery.sh /system/etc/install-recovery.sh[/I][/B]
[B]9:[/B] [B][I]adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su"[/I][/B]
[B]10:[/B] [B][I]adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"[/I][/B]
[B]11:[/B] [B][I]adb shell "chown 0.2000 /system/etc/install-recovery.sh;chmod 755 /system/etc/install-recovery.sh"[/I][/B]
[B]12:[/B] [B][I]adb shell "sync;mount -o remount,ro /system"[/I][/B]
[B]13:[/B] [B][I]adb install Superuser.apk[/I][/B]
REBOOT AFTER STEP #13
[/SIZE]
v
Automated .bat/.sh Directions:
Download latest ioroot.zip. Unzip and run bat/sh. Follow the onscreen instructions.
4.4.2 is rooted through stock recovery. Once in recovery use volume keys to select "update with adb" then hit the power button... then continue with the script.
4.4.2 users will see DAT ROOT when finished rooting. Reboot phone. Done.
Windows:
Download and install proper ADB driver. Enable USB Debugging. Double-click on root.bat
Linux:
cd into /IOroot/ folder
chmod +x root.sh
./root.sh
Mac:
cd into /IOroot/mac/ folder
chmod +x root.sh
./root.sh
Windows Drivers:
Verizon Drivers - HERE
Drivers for everyone else - HERE
EFS Backup:
EFS is automatically backed up for all 4.2.2(and below) devices.
EFS is backed up into the ioroot folder on your computer. If running ioroot on mac.. it'll be in the ioroot/mac folder.
Store backed up EFS partitions somewhere safe.
4.4.2 devices will not have automatic EFS backup.
Use the commands below to backup EFS.
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img
Not Working?
If you are on 4.4.2 and cannot get into a stock recovery menu with adb reboot recovery then you CANNOT root 4.4.2 on your device.
You must downgrade to 4.2.2 with stock tot or kdz, retain root and take OTA updates to 4.4.2
OR
downgrade to 4.2.2 and install custom recovery and manually upgrade your way to 4.4.2 by flashing a KK rom + modem.
Make sure to read all of the scripts on-screen text or you may miss something. Hitting a button when it's not time to do so or not reading everything on screen can cause problems. Make sure the phone is unlocked with the screen on whenever possible as well.
If the scripts fail for you check out the manual directions further down the page. The manual method is only a few ADB commands and can help if I've messed up in the scripts somewhere... or if the scripts just don't seem to be working for you. Taking it one step at a time manually almost always results in success.
Still not working?
I need the output from the 4 ADB commands below along with IOroot version and if it was on Windows/Linux/Mac. Any errors you come across would help as well...
adb shell "getprop ro.product.model"
adb shell "getprop ro.build.target_operator"
adb shell "getprop ro.lge.swversion"
adb shell "getprop ro.build.fingerprint"
What's Next?
Confirm full root with rootchecker. ( @joeykrim )
Support a great dev by buying the Pro version.
If you only did the "temp root/adb only root" then you can confirm root by opening adb shell and seeing # instead of $.
For custom recovery(TWRP/CWM) on 4.2.2 and below run FreeGee ( @Shelnutt2 )
Check out the FreeGee donate version if you want to support a great dev.
For custom recovery(TWRP) on 4.4.2 run AutoRec by @Cloudyfa for a safe and easy install.
IOroot25r1 Download: HERE
Changelog:
v25r1: Fixed LG OG EFS backup. Added D802T 4.2.2 support. Script checks for 4.4.2 first.
v25: Added root for 4.4.2 devices. Now works on most LG 4.4.2 devices. Thanks to @jarari2 for the idea to go through stock recovery.
v24: added support for G2 D800 10q, G Flex D956 and G Pro 2 F350K/L/S(thanks to @hkfriends for confirming ioroot method still works)
v23: added support for AT&T G Flex D950 10c.
v22: added support for TMO D959 G Flex. Tweaked scripts EFS backup... hopefully no more errors.
v21: added support for Sprint LS980ZVA update. Added EFS backup support.
v20: added support for all D802/D805/D806. Updated all scripts. Added LG Optimus G and LG G Flex support. SuperSu now installed in /system.
v19: added support for MORE F320 4.4 firmware. Added Singtel D802 support. Linux/Mac script fixes.
v18: added support for MORE F320 4.4 firmware. Added Vodafone(VDF) carrier(should work with at least Shipping ROM). Tweaked scripts.
v17: added F320* 4.4 KitKat root. Added SuperSu.4.4 users must reboot after running root script(mac/linux)
v16: added TMO 10g root and "SCA" root(D802/D805)
v15: added ATT 10o root.
v12: added Verizon 12B root.
v11: added linux support and Sprint LS980 root(both thanks to @Shelnutt2)
y u no hit thanks button?
@autoprime You da man
id10terror said:
@autoprime You da man
Click to expand...
Click to collapse
The lack of root was the only reason I withheld from upgrading to stock KK with the G2. I can live without a lot of things, but not UDN.
Many thanks!
Thank autoprime, regained root smoothly on my newly updated G Pad.
How to make EFS backup without root? I updated my G Pad to 4.4.2 and lost root.
thank you. installed on my G Pad 4.4.2 stock
I uploaded the zip on VirusTotal (Link )
and ClamAV says it's an Andr.Exploit.Ratc.
A false report?
Recovery
I managed to root my 4.4.2 tablet with this method.
I have had no luck to unlock the bootloader or install a custom recovery.
Anybody with advice on this when the tablet is running stock 4.4.2.
mortenchristensen said:
I managed to root my 4.4.2 tablet with this method.
I have had no luck to unlock the bootloader or install a custom recovery.
Anybody with advice on this when the tablet is running stock 4.4.2.
Click to expand...
Click to collapse
dd the old aboot. Look at step 3 here. http://forum.xda-developers.com/showthread.php?t=2698267 you probably want to delete the build.prop out of the directory if you want to keep your current build.prop. I don't know if this ever got finished but this would work as well http://forum.xda-developers.com/showpost.php?p=51613184&postcount=54
Wolkenstern said:
I uploaded the zip on VirusTotal (Link )
and ClamAV says it's an Andr.Exploit.Ratc.
A false report?
Click to expand...
Click to collapse
did you look into what Andr.Exploit.Ratc even is?
it's a root exploit... deemed a virus because it roots android. you do want root right?
autoprime said:
did you look into what Andr.Exploit.Ratc even is?
it's a root exploit... deemed a virus because it roots android. you do want root right?
Click to expand...
Click to collapse
Sorry, I didn't look futher into it
But it works, I had this fastboot error because TWRP was gone, even after flashing it again.
Then I did Step 3, like suggested in the comment above and it works.
i have a problem... after upgrade from stock 4.2.2 to 4.4.2 with LG tool at first execute of ioroot they do a factory format and only after this they do a success at 2nd try.
But i lost all my data. Fortunately i have a nandroid.
how to regain root without data lost?
and if i try to restore \data partition from a 4.2.2 nandroid backup on this rooted 4.4.2 factory resetted?
nozyk12 said:
How to make EFS backup without root? I updated my G Pad to 4.4.2 and lost root.
Click to expand...
Click to collapse
bump.
EFS backup is necessary?
Works perfectly
I just downloaded KitKat (in the US) using the LG Mobile Support Tool and rooted with ioroot25 last night. Excellent root tool, very easy way to root your G Pad 8.3!
Works fine, but erase all your data
Rooting worked fine. Warning about the the possible loss of data would have been nice.
Running the Xposed Framework with Gravitybox. PIE Control gives a better real estate.
Too early to comment on the battery performance. Nova launcher gives a smooth, stutter
experience.
Done on my Gpad with 4.4.2 rooting worked fine, no data loss
autoprime, thanks a lot :good:
Sent from my LG-V500 using xda app-developers app
Hey I am trying to root with a Mac. Having troubles going about doing the process. I followed all instructions. And when the tablet goes to stock recovery.... It says no command with a android icon.
Any pointers?
Sent from my Nexus 5 using xda app-developers app
---------- Post added 12th April 2014 at 12:09 AM ---------- Previous post was 11th April 2014 at 11:13 PM ----------
Nevermind..... Rooted it
Sent from my Nexus 5 using xda app-developers app
Hi, thanks for the work!
If I root using this, can I go back to stock if I need to?
Tried it and it doesn't work for me. Followed manual precisely.
Once it boots into recovery there is no "apply update from adb" which I could click on. There are only the normal buttons from TWRP 2.7.0.1 like install, backup etc. Anyone can help?
Sent from my LG-V500 using Tapatalk
Edit:
Got it installed via adb but root didn't work. Went into TWRP, Mounted System, went to File Manager and deleted anything related to my previous SuperSU and then reflashed SuperSu and all went well.
When executing the .bat file, and then entering stock recovery,
at the bottom it reads:
E:missing bitmap stage_empty
(Code -1)
E:missing bitmap stage_fill
(Code -1)
The root is fine, and I have root access.
However does this cause problems in the future?
Related
hy
how root the lg optimus pro ?
need a guide thanks
1 º Download this suite of applications that I use (I added the zip original drivers from LG, which, with no specific model for this, worked like a charm):
www.megaupload.com/?d=U3L199Z3
2 Reset the phone manufactures (who have data to backup, use the File maneger Astro, for example), to obtain a clean file system Settings \ Privacy \ Reset factory data;
3 Extract the zip to a folder on your desktop and install the USB drivers, which are in the zip, the folder "USB driver";
4 Connect the phone to pc cable and expect drivers to be installed;
5 º Go to the pc start \ programs \ accessories \ command line;
6 After you open the command line type:
cd \
cd Users
cd (user name in question)
cd Desktop
cd (name of which are powered uncompressed zip files)
cd ADB
and the result is something like: C: \ Users \ (user name) \ Desktop \ Root Maximo LG Pro \ ADB
then enter the following commands:
adb devices (pressenter)
adb shell (press enter, and then the letter of the command line will pass to $)
echo 1> / data / local / lge_adb.conf (press enter)
7 After these commands inserted, turn off and then turn on the phone (very important this step), always with the phone connected by USB;
8 After restarting the phone, go to the folder where the files are downloaded and run the SuperOneClick.exe;
9 Select the method GingerBreak and click "ROOT"
10 When the process finishes (VERY IMPORTANT) make sure you turn off and turn it on again and update the application through the superuser Market.
That's it. Phone with root access.
Credits go to: Bruno Pinto @ AndroidPT
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
That guide is so complicated for n00b like me who has never before used Android. The stock rom is awfull anyway, any hope for costum roms on this one?
Hi!!
After running the adb command line and restart the mobile, i've started the super one click, it started rooting and in the end in step 7 he says "Remounting /system with read-write access .... FAILED", what went wrong?
I have the latest drivers for this smart and the latest super one click v.2.1.1
My LG has the 2.3.4 version of android and it's from TMN
Regards
is it possible to unlock it? (for free preferably)
hugoafsilva said:
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
Click to expand...
Click to collapse
the drivers are here: http://www.mediafire.com/?85wvjkp5ytb816y
This is NOT complicated method and it works great. I have also tried this on Optimus Net and works fine
Help..! Help..!
I have an LG-C660 Android Gingerbread 2.3.4
1 - Does anyone has an Android version fot this device..?
2 - After Root the device, it boots but dont´s shows the Desktop. It´s stucks on Carrier Screen
3 - Please Help me..!
I tried as instructions but the adb driver can't be successfully installed. I've tried installing drivers many times but it doesn't work.
Done! I removed the SD card and it worked finally!
i have a lg C660 from TMN with v2.3.4 i've tried and tried and cant make it work. anyone got it to work?
Edit :: with superoneclick v2.1.1 i get this
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
* server not running *
OK 0,10s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,14s
Waiting for device...
OK 0,08s
2.3.4
Getting manufacturer...
LGE
OK 0,02s
Getting model...
LG-C660
OK 0,03s
Getting version...
V10c-Aug-25-2011.2ED2FC6537
OK 0,03s
Checking if rooted...
False
OK 0,06s
Installing BusyBox (temporary)... - Step #1
2039 KB/s (1062992 bytes in 0.509s)
OK 0,59s
Installing BusyBox (temporary)... - Step #2
OK 0,03s
Rooting device... - Step #1
OK 0,02s
Rooting device... - Step #2
OK 0,03s
Rooting device... - Step #3
782 KB/s (16830 bytes in 0.021s)
OK 0,10s
Rooting device... - Step #4
OK 0,04s
Rooting device... - Step #5
OK 0,02s
Rooting device... - Step #6
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014354
[+] Using device /devices/platform/msm_sdcc.1/mmc_host
[*] vold: 0000 GOT start: 0x00014354 GOT end: 0x00014394
OK 80,24s
Rooting device... - Step #7
OK 8,08s
Remounting /system with read-write access...
mount: Operation not permitted
FAILED ::
When you get the #6 step you have to disable and enable debug usb on the device..in this way it should work
Sent from my LG-C660 using Tapatalk
Sir i have tried the above procedure. But after "loading gingerbreak" nothing happens. i have waited for half hour.Please tell me what went wrong?
some body know how to get in recovery mode ´cuz i can root my c660 i have gingerbread 2.3.4
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Step 5 and Step 7 problem
EDIT:
Finally Done. I used SuperOneClick v2.2 and removed the SD card (only in settings) and on step five just disable and enable usb debugging. I feel like alchymist.
And now i am looking how i can custom default rom.
simmer14 said:
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Click to expand...
Click to collapse
sir kindly make one for us too.. we are sick of Stock ROM...
unabl to root every =time it gets strucked on step 7... somebody help me
Installed at last after 3 days hardwork :/ :/
Obligatory reading before you begin: So You Want to Root and Mod Your HTC Phone
Introduction
Credit goes to Bin4ry for developing the loop-restore trick that applies to many phones, and of course CaptainRewind and jose51197 for being the first to demonstrate its applicability to the HTC Droid Incredible 4G LTE. Since that time, I have put quite a bit of work into writing these automated scripts. I am splitting them out of the original thread so that I can give them a proper home and continue to maintain them. With the start of this thread, I'm also introducing a Linux variant of the script.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usage - typical procedures
All of the below procedures assume you're still using a phone with a locked bootloader and S-ON.
Prerequisites:
Windows users: uninstall any HTC software you currently have installed (e.g. HTC Sync) and install the HTC drivers from this post. Only unlimited.io's S-OFF requires a certain driver version. Other procedures can use the latest version.
All users: Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
HTCDev Unlock: unlock the bootloader, install a custom recovery, and install superuser (for root access):
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Use task 3 of the script to revert the CID to stock (this will not affect unlock)
Unlimited.io S-OFF (DirtyRacun):
Follow the instructions for DirtyRacun: Fireball at unlimited.io very carefully
When you get to Temproot your phone via any method available, use task 6 of the script to put your phone in temp-root mode.
Continue the instructions for DirtyRacun
Facepalm S-OFF:
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Follow the directions for Facepalm S-OFF
Use task 3 of the script to revert the CID to stock (this will not affect unlock or S-OFF)
Flash the DirtyRacun HBOOT from unlimited.io - follow the instructions on the right sidebar
Notice: Windows users can run these commands by removing sudo ./ from each line.
Cautionary Notes about OTAs
When (if) fireball gets an official jellybean release from HTC/Verizon:
It is crucial that users have their CID as VZW__001 (and not SuperCID). It seems OTAs (over-the-air updates) for other HTC devices have caused bricks for users who are S-ON and SuperCID. I strongly recommend users revert their CID after unlocking or doing facepalm S-OFF.
New touch firmware may cause compatibility issues when switching between ROMs. If possible, delay updating while devs work on testing ROMs with the new firmware.
With this said, I really have NO clue whether we will ever get an official jellybean release.
Linux script notes
The linux script will only execute properly in a bash terminal!
After extracting, make runme.sh executable:
Code:
chmod +x runme.sh
Then, run the script:
Code:
./runme.sh
Manual procedures for reference
Windows
Before you begin
Uninstall HTC Sync and any other applications/drivers that come up with a search for "htc" in the uninstall programs list in Windows. Download and install the latest HTC Drivers from this post.
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a command prompt in the directory where you extracted Inc4GUnlockV6-Windows.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
The command prompt will appear to be hung. At this point you can accept the restore prompt on your phone. When the command prompt returns, type:
Code:
adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
copy cid mmcblk0p4.original
hexalter cid 0x214=0x31,0x31,0x31,0x31,0x31,0x31,0x31,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
adb shell "rm /data/local.prop /sdcard/cid"
del cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
adb reboot-bootloader
fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Windows.zip, then type:
Code:
fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
fastboot flash recovery recovery_file_name.img
fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
adb shell "rm /sdcard/cid"
del cid
Linux
Before you begin
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a terminal in the directory where you extracted Inc4GUnlockV6-Linux.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
./adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
./adb restore fakebackup.ab
./adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
The terminal will appear to be hung. At this point you can accept the restore prompt on your phone. When the terminal prompt returns, type:
Code:
./adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
./adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
./adb pull /sdcard/cid
cp cid mmcblk0p4.original
printf '\x31\x31\x31\x31\x31\x31\x31\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
./adb shell "rm /data/local.prop /sdcard/cid"
rm cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
./adb reboot-bootloader
./fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
./fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Linux.zip, then type:
Code:
./fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
./fastboot flash recovery recovery_file_name.img
./fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
./adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
./adb pull /sdcard/cid
printf '\x56\x5A\x57\x5F\x5F\x30\x30\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
./adb shell "rm /sdcard/cid"
rm cid
Changelog
Version 6.2
Linux: Fix incorrect use of grep when busybox is not available; update adb and fastboot executables
Version 6.1
Windows: (Hopefully) fixed hanging procedures due to std redirects
Linux: Allow more diverse device codes returned by adb devices
Version 6.0 - Initial Release (in this thread)
Great tool, wish I had this when I was did mine I wasted valuable angry birds time
Sent from my ADR6300 using xda app-developers app
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
kramer56 said:
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
Click to expand...
Click to collapse
I literally just put my palm to my face. You need to re-consider whether leaving your stock ROM is a good idea.
This post is relevant.
deserved. the original inc was just so easy i guess. this seems so much more involved with the windows os
I always flash roms with the og
mdmower said:
I literally just put my palm to my face.
Click to expand...
Click to collapse
I see why the new method is called Facepalm S-OFF now.
Well when i get to here adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; it asks on the phone for a encryption password and the cmd.exe says link not found and just keeps running that for 3 minutes then I exited out
maybe I am not extracting to the proper place, that is unclear to me, sorry
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
sidgallup said:
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
Click to expand...
Click to collapse
I have not seen a fireball with an FAXXXXXXXXX device code. Are you positive you have the Incredible 4G LTE (and not the Desire 4G LTE or Incredible 2, or Incredible S, or something else)?
It looks like you have two devices plugged in. If so, unplug the other device.
If you have HTC Sync or any other HTC software installed, remove it all and re-install just the driver.
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
that driver is for windows 8 i think you need 3.0.007 something like that.
Aldo101t said:
that driver is for windows 8 i think you need 3.0.007 something like that.
Click to expand...
Click to collapse
The 4.x drivers also work with Win7.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Do i need to use this same tool to get it unlocked using the HTCDev method?
sidgallup said:
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Click to expand...
Click to collapse
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
mdmower said:
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
Click to expand...
Click to collapse
Yeah, that's what i'm gonna do for now, i thought rooting this phone will be just as relatively easy as with my old Droid 2 Global but it's a completely different animal.
At least last week HTC announced they are updating stock to 4.2.2, with some luck our 4g LTE is getting the update too
mdmower said:
The 4.x drivers also work with Win7.
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
Click to expand...
Click to collapse
I stand corrected, thanks
Ok one last question just to be completely shure i'm not missing something... can i run the script witile the phone is ON or should i be running it with the phone in bootloader mode?
EDIT: ok i got it to work, that other "emulator" device was related to Blue Stacks App Player, as soon as i uninstalled it the script worked perfectly even when my phone wasn't listed as HTXXXX, just installed CM10 and everything is fine.
c:\Android>fastboot oem get_identifier_token
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
I am stuck on this, how do i get pass this the fastboot is there I see it but it won't run
I use windows vista home premium 32 bit
ok yesterday I got as far as the fast boot token on windows and now today the adb is out of date or something to that effect. every time I click sdk manager it has all the revision updates for platform and tools. yesterday it did none of stuff. My device is not found and when i run task 1 it say daemon not working switch to port 5037 and it does not list any devices. Should I do a factory reset on hboot screen? I just installed htc drivers ending in ....23 and still nothing. UBUNTU was a fail because nothing would auto run at all and I had to keep extracting to folders in which nothing found later not to mention no wireless on ubuntu either.
adb is up to date now but no device found, everything powers up just fine
wrong thread
I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
laconical said:
I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
Click to expand...
Click to collapse
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Hello. Thanks for the reply.
I am going to ask what are probably very obvious questions but I am a little out of my depth.
1) What does installing a custom recovery involve?
2)How would I backup the EFS directory? When I had ES file explorer I would have been able to try and find it. However, as it is I do not know how to find the directory and back it up. I have connected the phone to a windows laptop and it shows up as note3 but there are no folders or files visible in either the phone or on the card.
3) What is the procedure to "wipe everything"?
I think the final part I know how to do with ODIN. Just go to download boot and load and run odin with the ROM.
I got the BTU ROM is that not for the UK? I tried looking up what NC2 was but did not really find anything the explained what it is.
Thanks again and sorry for the ignorance on my side.
Let's put the custom recovery and all that on the back burner for now.
Was your phone unlocked from the factory or did you get it from a carrier? If from a carrier, which, and is it unlocked now or you are still using it with the original carrier? This one is for Vodaphone http://www.sammobile.com/firmwares/3/?download=27401 but if you are unlocked, it should work anyway, I believe.
Thanks to the people for their replies. I managed to solve the issue as below.
As mentioned previously I had flashed using ODIN and BTU version of N9005XXUENB7. The only other thing that was then required was to enter the recovery (I think power + volume up + home and then release power once samsung name appears). I then selected wipe data/factory. A reboot later and everything was solved.
es0tericcha0s said:
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Click to expand...
Click to collapse
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
christaph3r said:
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
Click to expand...
Click to collapse
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Same boat here. Please someone help!
woahs said:
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Click to expand...
Click to collapse
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
vbcomer said:
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
Click to expand...
Click to collapse
Update: I went ahead and successfully install the all-in-one file to the phone via Odin, but it still has the same issues. Can someone give a hint? thanks
FIX!!!
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
sorry guys bt i have the same note 3 and i delete the platform.xml file .....i did a factory reset bt nothing happened ...can u help plz
Re:FIX!
But you have to set the permissions of platform.xml as 0777.Right?
Step 5 how should it works
Android Goobie said:
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
Click to expand...
Click to collapse
Hi have next message in the install root step could you help me please
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode) adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n" adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only) adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-d] [-s] [--algo <algorithm name> --key <hex-encoded ke
y> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-d' means allow version code downgrade)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.) adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Hello all,
It's that time of the night where I post things on XDA and wake up to a bajillion PMs.
Without further ado, I introduce "Low Effort Root".
What is this?
Low Effort Root is a root for your LG G4, named such because this is a root we really weren't too interested in releasing, but the phone is gaining critical mass so we figured waiting any longer would be a disservice to the community.
(We also don't like that the root ends up being ~4GB, since we're flashing whole new system partitions.)
We had originally planned on releasing an in-android root app, however time constraints on all the team members has prevented us from devoting the necessary time to it.
This root will root any LG G4, provided we have a pre-rooted system image for it. This is akin to 'flashing a rooted odin' image on a Samsung phone, as we're simply writing a system partition that contains Superuser.
No exploits here, no trickery, just a plain and simple flash and be on your merry way.
Click to expand...
Click to collapse
How do I use this?
Please read the whole directions here carefully. If you miss a step, or you copy the wrong command and run it, your phone will be BRICKED. You will have flashed a partition to some random place on your phone's internal SD, and no amount of sad private messages will be able to help you.
I'm 100% serious, if you do this wrong, you will turn your phone into a paperweight - so please don't go rooting your mom/dad's phone with this method. Wait for something better from us.
Ensure you have the proper drivers for your phone. If you don't, download and install the proper driver below.
Code:
All G4 (except Verizon) - [URL="http://downloads.codefi.re/autoprime/LG/LG_G4/LGUnitedMobile_Win_Driver_Ver_3.14.1.exe"]http://downloads.codefi.re/autoprime/LG/LG_G4/LGUnitedMobile_Win_Driver_Ver_3.14.1.exe[/URL]
Verizon - [URL="http://downloads.codefi.re/autoprime/LG/LG_G4/LG_VZW_United_WHQL_v2.22.0.exe"]http://downloads.codefi.re/autoprime/LG/LG_G4/LG_VZW_United_WHQL_v2.22.0.exe[/URL]
Open this forum link and keep it up in another tab. We'll refer to it again in step 6: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (and while you're at it, give the op there a thanks!)
Download the appropriate files for your phone from the section below. Make sure to grab the Send_Command tools (named LG_Root.zip below)
Extract the tar.gz file you downloaded for your phone, and move the resulting "system.rooted.phonemodel.img" file to the root of your phone's internal SD card with MTP mode. Do not rename this file, or move it into any folders. If you don't get a file named "system.rooted.phonemodel.img" DO NOT continue. You need to properly extract the file.
On the page you opened in step 2, follow steps 1,2,3,6,7,8,and 9 on that page only, then come back here.
Ensure that on step 9, you use the right COM port.
Type "id" and press enter (no quotes).
You should get back some text starting with "uid=(0)root gid=(0)root". If not, press CTRL-C, and do step 9 again (the application sometimes doesn't respond on the first command).
Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.
After a few minutes of sitting, you should get back a "#" prompt. This indicates the process has finished.
Type "LEAVE" (no quotes) and press enter. Your phone should reboot, and your phone will be rooted.
Now that you're rooted, MAKE SURE YOU DISABLE OTA UPDATES, if you accidentally take an OTA, you might not be able to roll back or fix it.
You can also delete the system.rooted.modelnumer.img from your phone's internal SD card to save some space.
Click to expand...
Click to collapse
Commands to Run
T-Mobile H811 10H Version:
Code:
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
VZW VS986 11A Version:
Code:
dd if=/data/media/0/system.rooted.vs98611a.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
International H815 10c Version (NOT H815T, H815TR, H815P, etc - you will lose internationalization and possibly features):
Code:
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
AT&T H810 10G Version:
Code:
dd if=/data/media/0/system.rooted.h81010g.img bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0
Sprint LS991 ZV5 Version:
Code:
dd if=/data/media/0/system.rooted.LS991ZV5.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
If your phone isn't listed here DO NOT run these commands on your phone. You will break your phone.
If your phone isn't running the EXACT firmware version specified, you will need to OTA to the proper version to root. If you'd like to not OTA, sit tight while we get a better root together.
Click to expand...
Click to collapse
Download Links (more to come soon)
Send_Command tools - ALL variants require this (you'll use this in step #5):
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/LG_Root.zip"]http://downloads.codefi.re/thecubed/lg_g4/lef/LG_Root.zip[/URL]
(I'm mirroring these because unfortunately Dev-Host is tricking users into downloading malware with a 'Download' versus 'Download Now' button. As much as I feel bad for mirroring, I'd feel worse if I let people get led astray by a site that is tricking users.)
Download one of the following, depending on your phone's model
T-Mobile:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz[/URL]
Verizon:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/vs98611a.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/vs98611a.tar.gz[/URL]
International H815 10c Version:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/h81510c-eu.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/h81510c-eu.tar.gz[/URL]
AT&T:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/h81010g.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/h81010g.tar.gz[/URL]
Sprint:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz[/URL]
Please do not mirror these files. Also, you do NOT have my permission to roll any of this into a 'one-click' root.
Click to expand...
Click to collapse
Ah Gawd, something went wrong!
Did it really? That's interesting... Luckily short of running the wrong command, you can easily recover from a bad flash by simply looking for the "Return to Stock" thread here on XDA for your phone, and flashing the KDZ from there.
KDZs cover a multitude of sins (short of you putting something in the completely wrong place on the EMMC).
Click to expand...
Click to collapse
Why isn't my variant supported?
See Post #2 by @autoprime (or click here: http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2 )
Click to expand...
Click to collapse
Special Thanks
First, I really need to thank everyone that donated to get Team Codefire phones.
You all are *super* awesome, and we are very grateful to be the recipients of your kindness
That said, if you'd like to consider donating to us for our work, our donation links are here. Thanks!
@thecubed - Paypal Donate - That's me!
@IllegalArgument - Paypal Donate - As usual, IllegalArgument is a genius. He also might be a mad scientist, it won't surprise me when he achieves cold fusion somehow.
@autoprime - Paypal Donate - 99.92% of testing for this root and pretty much all our other goodies get tested by autoprime - he's awesome -- he even wrote up the instructions for this root for me
@jcase - Paypal Donate - Gotta add jcase here, he's a wealth of information and a damn smart dude all around.
Click to expand...
Click to collapse
I just wanna say thanks again to everyone who donated to the original gofundme so we could get these G4's in hand. :highfive:
If you use MTP it shouldnt take too long to move the system.img over to internal scard (no u cant use external sd for this).
If you use ADB push... it takes a good.. 20-25min to push the file over to internal storage.
Using the dd commands to flash the system img should only take a few minutes.
As for the bounty/donations for root... yes there are 4 paypals linked. Ideally you'd split each donation up... as we only get what's donated to each of us. Due to taxes.. multiple ppl involved etc... it's just more difficult (on us) to use a single email.
I'm gonna call out everyone who pledged but doesn't come thru. JK.. maybe.. :silly:
be sure to follow me on twitter to keep up with the latest news and updates.. @utoprime
Command to Flash System.img (All Variants):
These commands are an extension of the OP.. adding support for the rest of the G4 variants not included in initial release.
REPLACE "rootedsystem.img" in your command with the name of the actual rooted.system.img you're using.
Example... if you downloaded a rooted system img for F500K 10F you'd change:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
into
dd if=/data/media/0/rooted.system.F500K10F.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
(or whatever the filename is...)
AS991:
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=509952 of=/dev/block/mmcblk0
F500K/L/S :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H810 AT&T :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0
H810PR :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H811 T-Mobile :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H812 Canada (All H812s) :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H815 EU/SEA/TWN :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815L :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815P :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815T :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815TR :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H818 China:
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H818N :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H818P :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H819 China:
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
LS991 Sprint :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
VS986 Verizon :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
US991 US Cellular :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
Pre-Rooted System.img Download Links
These are links for pre-rooted system.imgs from the users.
I will not link to new threads... only system.imgs posted in this thread.
AS991 10C:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62213418&postcount=1578"]http://forum.xda-developers.com/showpost.php?p=62213418&postcount=1578[/URL]
H810 10B / 10E:
Code:
[URL="http://forum.xda-developers.com/att-g4/development/root-images-h81010b-h81010e-t3168427"]http://forum.xda-developers.com/att-g4/development/root-images-h81010b-h81010e-t3168427[/URL]
H810 10I:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62809806&postcount=2091"]http://forum.xda-developers.com/showpost.php?p=62809806&postcount=2091[/URL]
H810PR 10A:
Code:
[URL="http://forum.xda-developers.com/att-g4/development/ahhh-root-sweet-delicious-root-h810pr-t3168322"]http://forum.xda-developers.com/att-g4/development/ahhh-root-sweet-delicious-root-h810pr-t3168322[/URL]
H812 (All Variants):
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62115644&postcount=1249"]http://forum.xda-developers.com/showpost.php?p=62115644&postcount=1249[/URL]
H812 10G:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=63010862&postcount=2172"]http://forum.xda-developers.com/showpost.php?p=63010862&postcount=2172[/URL]
H815 10B Vodafone Germany:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62132150&postcount=1365"]http://forum.xda-developers.com/showpost.php?p=62132150&postcount=1365[/URL]
H815 10B Germany EUR (Open):
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62161571&postcount=1477"]http://forum.xda-developers.com/showpost.php?p=62161571&postcount=1477[/URL]
H815 10D EUR (Open):
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62225446&postcount=1596"]http://forum.xda-developers.com/showpost.php?p=62225446&postcount=1596[/URL]
H815 SEA 10B:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62140625&postcount=1400"]http://forum.xda-developers.com/showpost.php?p=62140625&postcount=1400[/URL]
H815T 10B HKG:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62114467&postcount=1242"]http://forum.xda-developers.com/showpost.php?p=62114467&postcount=1242[/URL]
H818P 10D:
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347781803"]https://www.androidfilehost.com/?fid=24052804347781803[/URL]
US991 10A Unlocked:
N/A
US991 10A US Cellular:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=64854943&postcount=2642"]http://forum.xda-developers.com/showpost.php?p=64854943&postcount=2642[/URL]
US991 10C US Cellular:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62115811&postcount=1251"]http://forum.xda-developers.com/showpost.php?p=62115811&postcount=1251[/URL]
Click to expand...
Click to collapse
Backup System to Internal Storage (Commands for all variants):
Rather than flashing a pre-rooted system.img.. the following commands are to backup your current system partition into a system.img on your internal sdcard. You would do this if you want a stock system.img.. possibly to upload/share with others on this forum so someone can pre-root it... or to unroot and go back to stock (though it's probably easier to use a KDZ to go back to stock if you have one available).
AS991:
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=509952 of=/data/media/0/system.img
H810PR, H815 (All variants), H818N/P :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
F500, H811, H812, H818, H819, VS986, US991 :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img
H810 AT&T :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
LS991 :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=557312 of=/data/media/0/system.img
Click to expand...
Click to collapse
How-to Videos:
If you have a related video I think is worth sharing I will add it below.
[How to] Root the LG G4 without bootloader unlock by @rirozizo
How to Root your LG G4 all variants by @Tomsgt aka Rootjunky
Click to expand...
Click to collapse
I'm off to bed here shortly... If anything breaks, I blame autoprime
OMG!!! the links are down though.
I want to try it on mine H815L, i could flash H815 KDZ with no problem, can i root it?
Thanks for the BEST releasing, but does it support Hong Kong H818N? Or H818P? Thank you.
Derpling said:
OMG!!! the links are down though.
I want to try it on mine H815L, i could flash H815 KDZ with no problem, can i root it?
Click to expand...
Click to collapse
Links should be back up.. had some quick scheduled maintenance.
As for if H815L or H815T or H815TR or H815P will work with the existing H815 image... not sure to be honest. It SHOULD but I'm not sure what sort of localization files are included in each of those H815X variants. I would say.. if u wanna go for it.. go for it... just confirm you can grab a KDZ for your phone first.
See here for KDZ info http://forum.xda-developers.com/showthread.php?goto=newpost&t=3147406
Worst case.. the language is wrong or something and you flash back to stock KDZ. We plan on adding more intl system images later today/tomorrow if you don't wanna risk it.
jkvndst said:
Thanks for the BEST releasing, but does it support Hong Kong H818N? Or H818P? Thank you.
Click to expand...
Click to collapse
Like my above answer.. it's hard to say. Im not sure if there are any different files due to dual sim H818N/H818P. I can confirm worst case would be.. just flash KDZ if it doesnt work out with H815 img (for your exact models you mentioned). We plan on adding H818N/P and H818/H819 etc etc later today/tmw.
I can say, if you are H818/H819 china.. do NOT flash anything yet. You need your own images.
F500, H810, H812, H818/9, H818N/P, H815X, LS991, US991 all coming soon. :good:
(we need sleep)
When i flashed H815 KDZ over my L, it does give error when u start the phone, that some language was not found, but i have all languages and all works perfect, so i guess i good to go.
Anyway i gonna try it , need root so badly to change Kernel stuff, THANK YOU!
Excellent news for those not already rooted. I have been lucky enough to have been rooted from Day One but now thanks to you guys its finally time. Let the ROM's commence!
You guys are amazing, thank you very much. You mention blocking the OTA's immediately once we have root, should we use the same method as before with the debloater tool, or is there a better method once we're rooted to disable? Thanks again
My Verizon G4 has the latest OTA update, will that be an issue? Thanks
thenewbigmack said:
You guys are amazing, thank you very much. You mention blocking the OTA's immediately once we have root, should we use the same method as before with the debloater tool, or is there a better method once we're rooted to disable? Thanks again
Click to expand...
Click to collapse
No, users should look into seeing which apks to freeze/delete from system. Debloater tool is nice without root.. but freezing with titanium backup or something.. or just removing the apk might be best bet. As for which apks or services to freeze.. that's gonna differ for each variant.. and it's gonna take a community effort to compile all of that. I think we'll have enough time between now and the next OTA to sort that out. But anyone who doesnt keep up on this and doesnt block ota.. may be stuck without root after that ota. Of course.. there's also a chance that LG will not update the "bootloader version" used for anti-rollback for each update. And if thats the case.. it may still be possible to downgrade using KDZ. Only time will tell... but better to be safe than sorry.
slick_shoes said:
My Verizon G4 has the latest OTA update, will that be an issue? Thanks
Click to expand...
Click to collapse
not an issue. you can use it on 11A. Tmo users can use it on 10h.
no current OTA period will cause an issue for root. as for anything in the future... beware.
Is it now possible to backup the drm-keys before unlocking BL?
Gesendet von meinem LG-H815 mit Tapatalk
Model H815L, root is WORKING, no errors no bootloopes whatsoever, now time to install recovery and smile.
THANK YOU VERY MUCH!!!
Anyone tried H815TUR?
Bigdaddy168 said:
Is it now possible to backup the drm-keys before unlocking BL?
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
Sure, you can backup any partition now.
Code:
su
dd if=/dev/block/bootdevice/by-name/drm of=/sdcard/drm-backup.img
would save your drm partition to your internal sdcard.
Derpling said:
Model H815L, root is WORKING, no errors no bootloopes whatsoever, now time to install recovery and smile.
THANK YOU VERY MUCH!!!
Click to expand...
Click to collapse
Awesome, thanks for confirming... you've now made the "bounty" official :good:
But this is just root... no custom recovery yet (unless you are able to unlock officially thru LG.. but that is only H815 EU Open (no carrier version).
Will this work with v10c-OPT5-SI?
H815-Poland
sardroid said:
Will this work with v10c-OPT5-SI?
H815-Poland
Click to expand...
Click to collapse
yes.. H815 is supported. Country is not relevant. Check your box or settings menu for model.
ALL H815's are supported. User above has confirmed H815L working with the H815 method.
H815T, H815TR, H815P models most likely will work but languages or localization settings may not be included.
If anyone isnt up for "taking a risk".. please wait for us to add support for your exact model.
ALL firmware versions as of today are supported by this root. Future OTAs.. too early to say.
Tmobile H811 10H rooted. No issues so far. Installed Titanium Backup and Adaway and confirm both are working as normal.
Quick question just to confirm: Factory reset shouldn't affect the root right?
Bootup said:
Tmobile H811 10H rooted. No issues so far. Installed Titanium Backup and Adaway and confirm both are working as normal.
Quick question just to confirm: Factory reset shouldn't affect the root right?
Click to expand...
Click to collapse
Sorry, don't have the answer you're looking for, but have a quick question. How have you gone about disabling future OTA's? I'm also on TMobile which is why I ask. Thank you.
---------- Post added at 10:56 AM ---------- Previous post was at 10:53 AM ----------
You guys are amazing... thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Am I doing this correctly?
Code:
C:\Users\Hubert\Desktop\LG_Root>Send_Command.exe \\.\COM3
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#id
uid=0(root) gid=0(root) context=u:r:recovery:s0
#
Code:
C:\Users\Hubert\Desktop\LG_Root>Send_Command.exe \\.\COM3
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#id
uid=0(root) gid=0(root) context=u:r:recovery:s0
#dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=52992
0 of=/dev/block/mmcblk0
#
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS3
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS3
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS3
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1609 (Chinese) and A1619 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original English Firmware with OTA updates.
Click to expand...
Click to collapse
If you are running Android, you can Pair and Sync the watch with latest CN Amazfit app (2.3.0) but with this app you will not get OTA updates probably.
Click to expand...
Click to collapse
@Neur_User for STRATOSfied Rom and other stuff
@Cracklydisc for original script and other stuff
@1immortal for his support
@Alberto Ulla Zas from Telegram group for firmware dump
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues) or flash_US2.bat if you have issues with the other installer.
4. Wait to the end of the process and don't touch anything.
** #14 output may be different.
Batch file explanation
Since 2.3.8.0 firmware installer there are new batch files (.bat files) with updated modded files. During the installation a modded recovery and boot files are used to gain adb root access, in this installer you will find old batch files which uses old modded recovery and boot files, and some other batch files which uses latest modded recovery and boot files. This is meant to be more compatible with all watches/firmwares. Note that all batch files install the same firmware but in a different way.
A explanation of each file is explained in ver.txt file.
Firmware Installers in Spanish:
flash_ES.bat: Firmware installer in ES interface and colors
flash_ES2.bat: Firmware installer in ES interface without colors
flash_ES10.bat: Firmware installer in ES interface, colors and 2.3.8.0 modded recovery and temporal root (New)
flash_ES12.bat: Firmware installer in ES interface, without colors and 2.3.8.0 modded recovery and temporal root (New)
Firmware Installers in English:
flash_US.bat: Firmware installer in US interface and colors
flash_US2.bat: Firmware installer in US interface without colors
flash_US10.bat: Firmware installer in US interface, colors and 2.3.10.5 modded recovery and temporal root (New)
flash_US12.bat: Firmware installer in US interface, without colors and 2.3.10.5 modded recovery and temporal root (New)
flash_US_30.bat: Firmware installer in US interface, colors and temporal root (New)
flash_US_32.bat: Firmware installer in US interface and temporal root (New)
Unbrick and Firmware Installers in English: This is used when your watch is bricked or stuck on initial Amazfit A logo, after going to fastboot mode using the button trick
Unbrick_US.bat: Firmware installer in US interface without colors (New)
Unbrick_US10.bat: Firmware installer in US interface, without colors and 2.3.10.5 modded recovery and temporal root (New)
Unbrick and Firmware Installers in English: This is used when your watch is bricked or stuck on initial Amazfit A logo, after going to fastboot mode using the button trick
Unbrick_US.bat: Firmware installer in US interface, without colors and 2.3.10.5 modded recovery and temporal root (New)
Unbrick_US10.bat: Firmware installer in US interface, without colors and 2.3.10.5 modded recovery and temporal root (New)
Modded recovery and temporal root
recovery-mod.img: Old modded Stock recovery.img to gain adb root
recovery-mod2.img: 2.3.10.5 modded Stock recovery.img to gain adb root (New)
boot-US-adb-root.img: Old modded Stock boot.img to gain adb root
boot2-US-adb-root.img: 2.3.10.5 modded Stock boot.img to gain adb root (New)
OTA Installers
This installer is for those who are just on the previous firmware version and didn't get latest OTA and want to update. Only adb/fastboot drivers are needed, unlocked bootloader is not needed as this is an official update and won't void your warranty.
Unzip the .zip file and run INSTALL_OTA_US.bat.
Click to expand...
Click to collapse
Multilanguage Stock Firmwares with Official Spanish, Russian, Italian, French German, Polish and Korean languages
Stock US/International 2.3.13.0 Firmware Installer with OTA updates | Mirror
OTA 2.3.12.1 -> 2.3.13.0 Installer | Mirror | More info
Stock US/International 2.3.12.1 Firmware Installer with OTA updates | Mirror
OTA 2.3.11.1 -> 2.3.12.0 Installer | Mirror | OTA 2.3.12.0 -> 2.3.12.1 Installer | Mirror | More info
Stock US/International 2.3.11.1 Firmware Installer with OTA updates | Mirror
OTA 2.3.11.0 -> 2.3.11.1 Installer | Mirror | More info
Stock US/International 2.3.11.0 Firmware Installer with OTA updates | Mirror
OTA 2.3.10.5 -> 2.3.11.0 Installer | Mirror | More info
Multilanguage Stock Firmwares with Official Spanish, Russian, Italian, French German and Polish languages
Stock US/International 2.3.10.5 Firmware Installer with OTA updates | Mirror
OTA 2.3.10.4 -> 2.3.10.5 Installer | Mirror | More info
Stock US/International 2.3.10.4 Firmware Installer with OTA updates | Mirror
OTA 2.3.9.0 -> 2.3.10.4 Installer | Mirror | More info
Revert key mapping mod + OTA 2.3..9.0 -> 2.3.10.4 + apply key mapping mod
Multilanguage Stock Firmwares with Official Spanish, Russian, Italian, French and German languages
Stock US/International 2.3.9.0 Firmware Installer with OTA updates | Mirror
OTA 2.3.8.0 -> 2.3.9.0 Installer | Mirror
Revert key mapping mod + OTA 2.3..8.0 -> 2.3.9.0 + apply key mapping mod
Multilanguage Stock Firmwares with Official Spanish, Russian, Italian and French languages
Stock US/International 2.3.8.0 Firmware Installer with OTA updates | Mirror
OTA 2.3.7.0 -> 2.3.8.0 Installer | Mirror
Stock US/International 2.3.7.0 Firmware Installer with OTA updates | AFH Mirror
OTA 2.3.6.1 -> 2.3.7.0 Installer | AFH Mirror
Stock US/International 2.3.6.1 Firmware Installer with OTA updates
OTA 2.3.6.0 -> 2.3.6.1 Installer
Stock US/International 2.3.6.0 Firmware Installer with OTA updates
OTA 2.3.5.0 -> 2.3.6.0 Installer
Multilanguage Stock Firmwares with Official Spanish and Russian languages
Stock US/International 2.3.5.0 Firmware Installer with OTA updates
Stock US/International 2.3.4.0 Firmware Installer with OTA updates
Non multilanguage Stock Frmwares
Stock US/International 2.3.2.8 Firmware Installer with OTA updates
Stock US/International 2.3.2.7 Firmware Installer with OTA updates
Stock US/International 2.3.0.8 Firmware Installer
Recovery with OTA Fix for 2.3.0.8
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual method installation
Manual installation method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in first post.
On your terminal, go to the path where all the files were unzipped, or if you are running a Windows OS, just run terminal_cmd.bat and you are good to go.
How to Unbrick your watch
If your device is bricked, stuck at initial Amazfit logo, and no adb connection with PC, you have to reboot your watch into fastboot mode using the button and USB plug trick with this tutorial, and then you can run UNBRICK_US.bat to the root of the stock Firmware folder with all the other files, and run it.
Or you can install the firmware using manual commands and starting at Point 3.
OTA Installation
Download OTA installer from Post #1 and if you are running a Windows PC, run terminal_cmd.bat, or any other command/terminal window on your PC in the root of the unzipped folder.
Copy the update to the watch
Code:
[COLOR="Blue"]adb push update.zip /sdcard
[/COLOR]
And launch the update
Code:
[COLOR="blue"]adb reboot update[/COLOR]
Wait to the end of the update, and when the watch reboots delete the update file
Code:
[COLOR="blue"]adb shell rm /sdcard/update.zip[/COLOR]
Firmware installation
On your terminal, go to the path where all the Firmware files were unzipped.
You can copy and paste all needed commands.
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the old modded recovery
Code:
[COLOR="blue"]fastboot boot recovery-mod.img[/COLOR]
or the new modded recovery
Code:
[COLOR="blue"]fastboot boot recovery-mod[B][COLOR="red"]2[/COLOR][/B].img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.426s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.303s
5. Wait until you get a triangle with an exclamation mark in your watch
6. Copy the files to the watch (it may take up to a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
adb push boot.img /data/media/0/
7546 KB/s (9437184 bytes in 1.221s)
adb push system.img.gz /data/media/0/
7194 KB/s (228153632 bytes in 30.969s)
adb push md5s.txt /data/media/0/
88 KB/s (91 bytes in 0.001s)
adb push flash_rom.sh /data/media/0/
297 KB/s (458 bytes in 0.001s)
7. Start Firmware installation (it may take up to 2 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.953804 seconds, 9.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 89.945101 seconds, 9.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to English language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US[/COLOR]
Stock Recovery and Bootloader installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot old temporal root
Code:
[COLOR="blue"]fastboot boot boot-US-adb-root.img[/COLOR]
or new temporal root
Code:
[COLOR="blue"]fastboot boot boot[B][COLOR="Red"]2[/COLOR][/B]-US-adb-root.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.206s
13. Copy stock Recovery and Bootloader files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/[/COLOR]
[COLOR="red"]adb push u-boot-with-spl-mbr-gpt.bin /data/media/0/[/COLOR]
Output (or similar)
Code:
[100%] /data/media/0/install_recovery.sh
[100%] /data/media/0/recovery.img
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.461221 seconds, 6.5MB/s
Done. OTA updates should now work.
15. Flash Bootloader
Code:
[COLOR="red"]adb shell busybox dd if=/data/media/0/u-boot-with-spl-mbr-gpt.bin of=/dev/block/mmcblk0[/COLOR]
16 . Delete stock recovery installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img
[COLOR="red"]adb shell rm /data/media/0/u-boot-with-spl-mbr-gpt.bin[/COLOR]
[/COLOR]
17. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
18. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Wipe davik/cache
Code:
[COLOR="blue"]adb shell reboot bootloader
fastboot erase cache
fastboot reboot[/COLOR]
Do a Factory Reset (You will lose all the data in your watch. Unpair the watch from Amazfit app while doing this?
Code:
[COLOR="Blue"]adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot reboot[/COLOR]
Mio2
Mio2
Does this mean I can fully transform my Chinese version A1609 to be like English A1619?
wittanny said:
Does this mean I can fully transform my Chinese version A1609 to be like English A1619?
Click to expand...
Click to collapse
Yes. Even the model number changes.
MrLadoodle said:
Yes. Even the model number changes.
Click to expand...
Click to collapse
Excellent! Thanks for your hard work Saratoga!
I downloaded and installed yesterday from post on fb,are there any corrections in this today?
Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka
Hi 2.0.7.5 is actualy latest version of international ROM?
Followed all steps and went just perfect but the watch crashes after 10 good opetational seconds...
Did it with root ...
Did a factory reset ....
Always keep crashes
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
jordan41 said:
Followed all steps and went just perfect but the watch crashes after 10 good opetational seconds...
Did it with root ...
Did a factory reset ....
Always keep crashes
Click to expand...
Click to collapse
coming from STRATOSfied rom ...
masch1 said:
Hi 2.0.7.5 is actualy latest version of international ROM?
Click to expand...
Click to collapse
2.3.0.8
Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka
Do we need root for this installation? I do not see it in req but in other topic where is different way of installing root is needed.
jordan41 said:
Followed all steps and went just perfect but the watch crashes after 10 good opetational seconds...
Did it with root ...
Did a factory reset ....
Always keep crashes
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
coming from STRATOSfied rom ...
Click to expand...
Click to collapse
I would try restoring the origrinal firmwaer from here: https://forum.xda-developers.com/smartwatch/amazfit/rom-stratos-amazfit-sport-watch-2-t3746334
and reflash this rom again.
zmajdk said:
I would try restoring the origrinal firmwaer from here: https://forum.xda-developers.com/smartwatch/amazfit/rom-stratos-amazfit-sport-watch-2-t3746334
and reflash this rom again.
Click to expand...
Click to collapse
Thx mate i did try that too
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
jordan41 said:
Thx mate i did try that too
Click to expand...
Click to collapse
i ll try it again just cause i m despert ..
Thank you a lot for possibility to use stock English firmware with OTA.
I have a questions:
1. Does anybody succeed with this FW (there is only one post with non functional FW)
2. I do have a lot of recorded sport activities (Chinese FW and Android APP). Does FW change cause lost of my recorded training?
THX
dolezelt said:
Thank you a lot for possibility to use stock English firmware with OTA.
I have a questions:
1. Does anybody succeed with this FW (there is only one post with non functional FW)
2. I do have a lot of recorded sport activities (Chinese FW and Android APP). Does FW change cause lost of my recorded training?
THX
Click to expand...
Click to collapse
I flashed my watch with this FW and it's working fine so far.
I lost all my records.
jordan41 said:
Thx mate i did try that too
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
i ll try it again just cause i m despert ..
Click to expand...
Click to collapse
I'm coming from stratos 1.0 and the way I flashed this ROM is:
I copied the files into ADB folder and executing flash.bat while watch is rebooting.
Actually I didn't experience any misbehavior
Thanks for sharing But language change not possible. how to choose turkish language
Works here, must use the app from the Google Playstore.
worked fine thanks
Nojahoda said:
worked fine thanks
Click to expand...
Click to collapse
Here too, thanks. Hoping the next OTA Update will run.