Verified Downgraded from ZVA to ZV6 with full root access
LS991 Sprint Only.
QUICK GUIDE & TESTING
(Please read the entire guide before trying anything.)
I nor anyone at XDA is responsible for anything that may happen to your device.
Simply, by taking incentive to change the stock setup provided by the manufacturer for your device; you assume all responsibility for anything that happens.
download LGUP
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
(Thanks to shakeyabooti)
download LS991ZV6_00.zip and extract to get .tot file with winrar/7zip or any other unzipping program
http://downloads.codefi.re/autoprime/LG/LG_G4/LS991/LS991ZV6/LS991ZV6_00.zip (or google/xda search for mirrors) (Thanks to autoprime)
download LGROOT
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
(Thanks to Unjustified Dev)
download LG Drivers
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (or google)
(Thanks to Unjustified Dev)
download rootedsystem.ls991.zip and extract to get .img file with winrar/7zip or any other unzipping program
http://forum.xda-developers.com/sprint-g4/general/zv6-root-success-t3205963/page3
(scroll down to parin11's post. #29 and thank you to both parin11 and mswlogo)
-install drivers
-enable oem unlock in developer settings
-plug device in as charge only, switch to mtp to verify drivers are working correctly, then disconnect
--if on mtp then switch to charge only to verify drivers are working correctly, then disconnect
-enable usb debugging
-reconnect and drivers auto install
-disconnect after 2 minutes.
--while you wait;
-for LGUP extract and install _dll version then the second msi.
-for LGROOT extract to a folder to keep things organized
-remove the back cover of your device and leave it off for access to battery pulls.
-power off device
-hold volume up key and plug in your device and keep holding the volume down key until it passes the screen that says download mode.
-open LGUP
-make sure UPGRADE is checked/has a little circle/bullet point
-click in the empty space directly to the right of where it says BIN with the checkmark
-3 dots will appear to the right of the program in the same row that says BIN; which is your browse option
-navigate to LS991ZV6_00.tot and select
-reconfirm your UPGRADE option is checked
-press start and allow the device to fully complete the process.
-your device will boot to the loading screen right before showing the android desktop and "freeze"
-In most if not all new flash scenarios; your device will not boot up until a factory restore and clear cache is done.
-To do this you must simply remove the battery and usb cable from your device AFTER it has hung on the logo for about 3 minutes / 180 seconds.
(Most new devices average a first time boot of up to 150 seconds maximum to be considered fully "loaded")
-With the battery and cable removed; hold the power and volume DOWN button together at the same time.
-insert the battery while holding these buttons together and just wait while holding them and you will see it says booting into recovery.
-once your in the recovery you use the power key to select and the volume keys to navigate.
-navigate to factory restore/reset hit the power button, navigate to "yes" out of all the "no's" and hit the power button again
-it will say its complete and either ask you to go back reboot or return to menu. RETURN TO THE MENU, do not boot up yet.
-Once returned to the main menu you will see it says clear cache. Select and press yes and now you can select reboot; or return to menu then reboot.
Your device will be on ZV6 stock and fully booted after this.
Now this is where it gets kind of odd because my device never actually loaded the rootedsystemls991.img file nor did I run a root script
when attempting to flash it with the steps listed in the other root guides BUT i followed this guide from step one to step 9 (and outlined continuing through the guide)
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
this allowed all the necessary rooting files to be in the places necessary to execute the root but I did one extra step
I did an adb.exe push rootedsystem.ls991.img /data/local/tmp command as well while the device was on the home screen.
This was so I could basically emulate the command listed by |Unjustified Dev| as it also states to do in the ZV5 guide.
So this is what I did,
-After my device booted up and loaded to the home screen on stock zv6, I opened the LGROOT folder
-held shift and clicked "open command prompt here"
-when cmd opened I ran the following command
adb.exe devices
This allowed me to see that my device was connected to the PC with its generated serial number.
-then i ran the following command
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
-After this I applied the command to push the .img file to the same location. This was the "emulated command" I spoke of.
adb.exe push rootedsystem.LS991.ZV6.img /data/local/tmp
-I then added the .img file directly to the Internal Storage / Stock Phone MTP storage
-Afterwards I simply powered off my device, removed the usb cable, held the volume up button, then plugged it back in still holding the volume button until
the text download mode was gone again; and no this is not a timing thing im just saying that again incase anyone forgot how to get into download mode. lol.
-I then ran the ports.bat file included in LGROOT to find the COM port drivers.
-Followed up with this command
Send_Command.exe \\.\COM8 (<--Replace number here with the COM port listed for the "DIAG" portion of the device.)
-Now, still in download mode I executed this command about three times with no avail.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
(Which by the way I had the file in both the MTP side of root and in the data/local/tmp)
or you could change it to /data/local/tmp/ like
dd if=/data/local/tmp/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This would possibly solve the issue I was having. So you would have root now.
THIS PART REQUIRES TESTING.
BUT continue reading you'll be shocked.
sidenote:
They state that all you have to do is put the .img file into the root of your Internal Storage / Stock Phone MTP storage
and run the command in download mode but this failed when I tried to execute it.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
The command above was the command they listed to be able to restore the device from stock to stock with root access. Please note I tried this command while the phone was turned on in debugging with enable oem unlock on, while in download mode and while in recovery mode all with debugging and enable oem unlock checked with either no response / device detected, or attempts causing the command prompt to show the # symbol after a few seconds of executing the line above which shouldn't happen,
since the size of the file is 4GB... The ENTIRE SYSTEM PARITION. -_-. There is a considerable amount of hangtime here is what I'm saying.
If the dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0 command worked for you then great, boot up and enjoy root! BUT.
For those who didnt have luck doing so with the command that failed me above, for some odd reason after pushing both the SuperSU bundle and the entire .img file to /data/local/tmp/ with the files in the internal storage /data/media/0/ as well
trying to only execute the command for the .img (/media/0/ not /local/tmp/) | (not the "fixed" command") and NOT for the SuperSU
eg.
-This was for the image which was the only one I used. (USED)
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This was for root only which I did not touch. (NOT USED)
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
-This caused the device to simply show the # sign almost immediately as I spoke of above.
-I typed in LEAVE and the device booted back up.
-The odd thing I'm speaking about is when I turned the device back on it showed that SuperSU was installed and was requesting to be "updated".
-I chose normal and it asked for a reboot. Rebooted started back up and it asked for root access when I clicked on it.
-Granted and successful.
-Went to the playstore.
-It said update next to SuperSU which was even odder.
-Clicked it and updated it and it got the latest version, asked for one more reboot, started back up, then I opened the app. Everything was normal.
-Downloaded root checker basic, titanium backup, and greenify immediately.
All passed with flying colors.
-There is an error that pops up in titanium backup regarding adding underscores or slashes into modified file directories for backup purposes assumed but
opening greenify ended up picking up this issue and requesting to fix it.
Why not right?
-Heh. It worked.
I have never experienced this type of latency within programming so this is extremely odd and without executing the SuperSU script command or,
a sucessful flash of the .img it just seems too odd, but; there you have it! All of the mods / developers working on this device I would like to hear
your insight on this.
So you have two options. Follow what I did or test the command with /data/local/tmp/ and try your luck flashing stock with root again or just run the root script on stock instead of trying to flash from stock to stock rooted.
Thank you and enjoy your root!
P.S. I didn't end up experiencing this issue since it works perfectly but in the event that SuperSU does not install after trying to flash the .img and getting
the 2 second delay with the # sign appearing immediately and rebooting after 3 attempts I would have personally tested the original adb SuperSU script command recommended for the ZV5 users
which was listed above and is
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
And for the love of your device. Don't try to update your device from an older version using this method. Ayeeeyiyiy
I will re-test what I stated and make a completely organized guide and video for everyone.
I just wanted to let you all know now to assist the entire community in understanding this device's root process a little more.
Will this work with brand new phone?
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
wow, thanks!
Thanks for all your hard work. This phone has been one of my best and the only thing missing has been root, etc. Chewing over your instructions and thoughts. My confidence level is not quite there to pull the trigger, but i'm getting close. Hoping this is a promising method for those of us on Sprint ZVA. I will continue to do research and watch this thread. Thanks so much for your time, tips and expertise.
brpaaron said:
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
As long as its not been updated to zvb. Antirollback implemented on zvb
Still running zv6
I am still running zv6 and never updated. Do I need to update to downgrade to root or can I just skip to after the downgrade?
i am running zv9 i can not stock zv6
I have ZVC can i downgrade to ZV6?
LG G4 LS991.
LG G3 D850 ROM Fulmics 6.6
Recovery TWRP v2.8.7.0 bumped
LS991 ZVD
Hi there does anyone know whether or not it will work on the ls991 zvd update??? Sprint variant
Ls 991 ZVD
Will this method work on ls991 zvd i havent found anything on it
Expo6810 said:
Will this method work on ls991 zvd i havent found anything on it
Click to expand...
Click to collapse
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
TheMadScientist420 said:
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
Click to expand...
Click to collapse
Is there anything i can do for my zvd
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as far as i know. nothing
new root methods and tweaks come out everyday.
all the good devs as far as i know have stopped developing g4 and moved on due to the locked bootloader d other issues
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
a root method has been exposed on the g5
intime it may come for the g4 also but not adapted rite now
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
Right now i have ZVC software version can i downgrade zv6????
hawzsth said:
Right now i have ZVC software version can i downgrade zv6????
Click to expand...
Click to collapse
no u will brick
TheMadScientist420 said:
no u will brick
Click to expand...
Click to collapse
its already brick any solution...... now its show 9008 no power on ...
hawzsth said:
its already brick any solution...... now its show 9008 no power on ...
Click to expand...
Click to collapse
octoplus box with jtags the only fix
thats a hardbrick
---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as of rite now no
If I downgrade my zva will it allow me to sim unlock it
Somebody know if can downgrade ZVI to another version
Pls any update on locked bootloader?
Thank you!
Just learned here enough. Thank you!
I just head through UsU thread after reading this; Respectively thanks for the post again! ??
Related
Here is a small AutoHotkey script for getting your bricked phone back in the game in less than 10 minutes. Today I noticed that my dear phone spent more time being bricked than alive. This all due to failed overclocking trials with next Nova kernel version. And even if I already managed to get my phone up in half an hour or so it still involved a lot of manual work which was disturbing my parallel tasks. Considering the fact that my endeavours with OC are still half way there I decided to automate my life a little. I chose AutoHotkey because it allowed easy interaction with LG Update tool.
Here are the files you'll need:
Code:
161 792 adb.exe
96 256 AdbWinApi.dll
585 731 psneuter
6 291 456 recovery.img
1 534 unbrick.ahk
238 968 158 V10A_00.kdz
adb.exe and AdbWinApi.dll are taken from Android SDK, psneuter is from SuperOneClick, recovery.img I dumped from my phone mmcblk0p4 partition, unbrick.ahk is the script I wrote (you'll need to install AutoHotkey to run it), and V10A_00.kdz is LG KDZ. I did not try newer KDZ versions as my goal here was only to get recovery up and running to be able to flash CyanogenMod and continue from there. The script presumes that you already have LG USB drivers and B2C Client installed.
And here's the script itself:
Code:
; start LG Update tool (presumably installed at %ProgramData%\LGMOBILEAX\B2C_Client\)
Progress, m zh0, Starting LG S/W Update...
Run, %ProgramData%\LGMOBILEAX\B2C_Client\LGUserCSTool.exe userid=QM;usertype=B2C;region=K;country=KR;branch=KR;csemergency=F;language=KR;startstep=1;mode=TRUE;url=%A_ScriptDir%\V10A_00.kdz;binversion=V10A_00;localurl=%A_ScriptDir%\V10A_00.kdz;localver=V10A_00;usernd=Y;fileclass=CSE
WinWait, Select Country
Control, ChooseString, Diff, ComboBox1
Control, ChooseString, English, ComboBox2
Send {Enter}
WinWait, LG S/W Update
; wait for update to finish
ControlGetText, s, Edit4, LG S/W Update
Progress, m zh0, Waiting for LG S/W Update to finish...
While InStr(s, "Found(2004, 100)") = 0 {
Sleep 100
ControlGetText, s, Edit4, LG S/W Update
}
Process, Close, LGUserCSTool.exe
; at this point the phone should be rebooting
Progress, m zh0, Wait for the phone to reboot and turn on USB debugging to continue.
RunWait, adb.exe kill-server
RunWait, adb.exe -d wait-for-device
; get temporary root and flash recovery
Progress, m zh0, Rooting...
RunWait, adb.exe -d push recovery.img /data/local/tmp/
RunWait, adb.exe -d push psneuter /data/local/tmp/
RunWait, adb.exe -d shell "chmod 0755 /data/local/tmp/psneuter"
Run, adb.exe -d shell /data/local/tmp/psneuter,,,pid
Sleep 3000
WinKill, %pid%
RunWait, adb.exe kill-server
RunWait, adb.exe shell "dd if=/data/local/tmp/recovery.img of=/dev/block/mmcblk0p4"
Progress, OFF
RunWait, adb.exe reboot recovery
MsgBox, The phone is rebooting into recovery now and we're done here.
Just boot your phone to software update mode and execute unbrick.ahk. It'll perform the following tasks:
Executes LG Update tool, waits for it to finish, and kills it then
Waits for you to enable USB debugging
Roots the shell with psneuter, flashes and reboots to recovery
From this moment on you can already continue inside recovery to restore your backup or flash CM and so on. This and enabling USB debugging are the only user interactions, everything else is automated with the script.
I hope someone will find it useful beside me as well. Do not fear experimenting with stuff and bricking the phone - unbricking is as easy as running a single script. This is a huge timesaver if you're planning to do this in hourly basis
I've almost always got bootloop with my experiment for bluetooth-audio, but still have nandroid backup and working recovery button
Thanks for your hardwork, aprold
Count me in! I don't know how many times I bricked/unbricked my phone (poor thing). Thanks for dedicating such time.
does it perform a hard reset ?
Thanks a lot aprold, i happen to brick my phone averagely 2-3 times a week. Will surely follow this method with next brick. Perhaps for the first time i 'm eager to see my OB bricked.... may your nova v12 test version give that chance.
Fantastic work, thanks!
Ilko said:
does it perform a hard reset ?
Click to expand...
Click to collapse
What do you mean by that? Wiping data? This is actually a good idea as you'd have to do this in recovery anyway. I'll add it next time I'm bricking my phone
Please add the archive with all files.
aprold said:
What do you mean by that? Wiping data? This is actually a good idea as you'd have to do this in recovery anyway. I'll add it next time I'm bricking my phone
Click to expand...
Click to collapse
I mean the reset process which is performed when r&d test tool is used. in some cases this is the only way to unbrick
Please add the archive with all files.
My phone is in black screen with 4 button blinking. Can't get into Software Update mode. what should I do?
Wrong place to post that. Read the unbricking thread. Do you mean you can't access software upgrade mode by plugin your usb with the battery removed? Did you try with adb?
Worked for me!! Only with V10A_00!!
I also made your script executable with AHK Compiler.
Problems:
- "Different country" and "English" are not automatically selected...
- LGUserCSTool remains at 4% ... but ...it still works
- After the phone reboot, I had to kill LGUserCSTool program with task manager..
- tried with v10i and the script didn't work
But the final result is the one I expect!
Ideeas:
- can V10A firmware been stripped down to the bones in order to speed up the process? maybe a fake firmware?!?
- What has to be changed in order to flash another (any) firmware version, besides V10a, obtaining the desired firmware installed... and rooted in the same time.... Maybe it can be done including installing some user apps... huh?
Please post the files
Since recovery phone via lgb2c doesn't worked at all,so I just have to try this BUT no files are included!! Please post it ASAP before my parents caught my phone bricked....
Does it matter from which rom the recovery.img is coming from? If not, do you mind me uploading the whole package? Nice tutorial anyway
One thing I just noticed, the script uses the wrong path to the LG software in german XP version, as it seems.
The path isn't called D:\Dokumente und Einstellungen\All Users\Application Data\LGMOBILEAX\B2C_Client
but D:\Dokumente und Einstellungen\All Users\Anwendungsdaten\LGMOBILEAX\B2C_Client
maybe also different in other languages...
but I simply searched the file and replaced the line, just wanna inform you, if anyone else reports problems
-edit-
-removed-
-edit2-
Is it possible to revert from v20x to v10x like this? Or will it brick the phone?
-edit3-
can really noone answer my question?
Still waiting for an answer... noone who tried it?
Nice one , I will try on next Brick. I already unbricked my OB by Smart Flash almost 5 times.
Package
Just created a full package to do exacly the same as explained in the first post.
Read the included README!!.txt first!
Download: http://d-h.st/mUM
Does this work to Root v20b?
when i start unbrick.exe this error show
HELLO TO ALL…..
By 3xeno-
This procedure works only on devices that are S-OFF'ed with Revolutionary or have their bootloaders unlocked with HTCDev. Also, its perfectly usable on Linux as well.
I OPEN THIS THREAD SO THAT ANY NOOB WHO WANTS TO FLASH RADIO OR CLOCKWORKMOD RECOVERY VIA HIS LAPTOP.
MANY NOOB FACE PROBLEM WHEN THEIR GPS DOSEN’T WORK AFTER FLASHING MAINLY CM7.THIS CAN BE RECTIFIED BY REFLASHING LATEST RADIO.
I ALSO FACED AND EVEN WHEN I WAS FIRST TRYING TO INSTALL CUSTOM ROM MY PHONE HANGED ON WHILE INSTALLING BECAUSE OF CWM.I RE-INSTALL/RE-FLASHED VIA LAPTOP AND VOILA!!!I WAS USING CM7.THIS METHOD IS A HARD PUSH ONE METHOD,SO
I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE TO YOUR MOBILE,BRICKING OR YOUR MOBILE REFLECTING YOUR RED ANGRY FACE IMAGE IN IT’S SUPER BLACK SCREEN AFTER PRESSING POWER ON BUTTON.THIS WILL 99% DOSEN’T BRICK BUT I DON’T GUARANTEE OF 1% BECAUSE OF YOUR BAD LUCK.ENJOY!!!!
THIS IS NOT MY INVENTION FIRST OF ALL.
A SIMPLE STEP USED FOR FLASHING RADIO AND CWM(PRIMARILY),many more things can be flashed, via laptop/desktop(only windows)
WHAT YOU NEED:
1. HTC SUITE
2.ADB FILES(Including Fastboot)
3.ANDROID USB DRIVERS
4.USB CABLE
5.FULLY CHARGED MOBILE
7.windows 7
PROCEDURE FOR INSTALLING ANDROID USB DRIVER:-
1.turn off your mobile,press vol.down+power button.
2.now from hboot(the screen that comes with 3 android) select fastboot using vol. down button and press power button.
3.after step 2 connect your mobile to your laptop having WINDOWS 7
4.now in your laptop open device manager and from there u will see android mobile(something starting with android) with a ! in yellow triangle.
5.right click on that and select update driver.
6.a dialogue box will appear and from there select the folder where u had saved android usb driver.
VOILA!Your device is ready to be used in fastboot mode.
PROCEDURE TO INSTALL RADIO:-
1.save ADB files,radio,cwm and fastbbot files in one folder where u will remember. For e.g- I save on c drive folder naming android.(android is a folder name where my radio.img,cwm.img and ADB files are copy pasted)
2.[IMP.]open command using option RUN AS ADMINISTRATOR.
3.now write cd/
C:\cd android\
C:\android\fastboot flash radio radio.img
U will be done
4. for cwm:
C:\android\fastboot flash recovery recovery.img
(remember to rename CWM file to recovery.img)
Any version of cwm and radio can be flashed via this method.
IF I HELPED PRESS THANKS BUTTON.
DOWNLOAD:-
latest radio-http://www.mediafire.com/?70kd4654129q6um
android usb driver-http://www.mediafire.com/?3tt3zfadg64usi1
latest CWM-http://www.mediafire.com/?4pn88xkpawg8b8b
Download fastboot files from njec21 post(4 post,thanks man for uploading file)
Really Ankurcul was this really necessary? There are many existing guides already for this,all you have done is add laptop in. Hope this does indeed help someone but like I said many existing guides already.
Regards Slymobi.
MANCHESTER together UNITED forever
Mother of all caps lock.
Also, ADB=/= fastboot.
If you instruct them to just download the ADB files, they wont get faatboot along with it.
@slymobi if u search general q&a section half of the noobs generally question about gps issue nad then over and over again we have to tell them what procedure to adopt.
it's just simple to open a single thread so that in future as per you so many threads of just one question can be reduced....
@njec21-bro just calm down....i don't wanna rude with u.....so mind ur words otherwise pm me any comments u want to give....don't make this thread bad for noobs that they won't try this and keep questioning about simple things
I'm didn't mean to be rude, I just think you abused caps lock a bit.
My second point still stand though.
How you're saying it right now is that they just need to download ADB, which doesn't include fastboot.exe, which is needed for your guide.
Link to fastboot:
http://android-roms.googlecode.com/files/fastboot-win32.zip
k...that's was a mistake that i didn't included fastboot and thanks for that njec....
+1 respect man...
You might want to add to the guide that this procedure works only on devices that are S-OFF'ed with Revolutionary or have their bootloaders unlocked with HTCDev. Also, its perfectly usable on Linux as well.
Will try this
I will try and i will press the thanks button, if it works....
---------- Post added at 12:53 PM ---------- Previous post was at 12:16 PM ----------
It will be nice if u add the flashing of KERNAL...
You might want to reduce your caps usage, it seems as though you're shouting, and this should go in the general section.
Sent from my Wildfire using Tapatalk 2 Beta-5
thanks 3xeno....
@usaff22-it's not shouting bt just want things clear that person reading it will read carefully.anything wont work will disguise this guide in which there is no point.what problem i faced and what i see in general sections about same gps issues i wrote.
i don't see any point in posting it in q&a section.
@balaedge- i'll look forward to it....same lame excuse college work....
hey,i tried this method but when i try to install recovery.img it is written status malformed 1 bytes...maybe i am noob but i didn;t find an answer in google) can you help me?)
dreamkill3r said:
hey,i tried this method but when i try to install recovery.img it is written status malformed 1 bytes...maybe i am noob but i didn;t find an answer in google) can you help me?)
Click to expand...
Click to collapse
Did you try re-downloading the recovery?
yes,i redownloaded it,i even tryed another image and the same problem :/ i observed in the last time that i cannot change my cwm even with the app(droid explorer) which i used always for changing it....i something wrong with my phone?
see,from my side recovery is clean as the same recovery iam using....
what exact procedure did u adopted....
did u run command as an admin??
Ankurcul said:
see,from my side recovery is clean as the same recovery iam using....
what exact procedure did u adopted....
did u run command as an admin??
Click to expand...
Click to collapse
yes,and it runs as system32 :/
@dreamkill3r-open cmd from system32 folder and run as admin.
connect ur mobile in debugging mode... and write command as
c:\android\adb devices
see what it says
Ankurcul said:
@dreamkill3r-open cmd from system32 folder and run as admin.
connect ur mobile in debugging mode... and write command as
c:\android\adb devices
see what it says
Click to expand...
Click to collapse
i tried some methods to write this comand,but every time it s written that it is a wrong command
Before you do adb devices do this:
in cmd type in "cd [adb.exe location]" Replace [adb.exe location] with the place you have adb.exe.
i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Lista of devices attached
SH159PY02094 device
and i have one more problem(in this case i only ask for help if someone can help me) in the last time,my phone can just stop working and i need to take off the battery for reboot it,the combination Power Button+Volume Down+Trackball doesn;t work :/ what can be the problem of my issues?
Whats up guys, Rydah here again. Here I present you guys with a stock rooted H81110N system image. This is for those who want root but cannot get TWRP to flash prior to root using MicroMod777's "One Click TWRP" tool. I unfortunately was one who couldn't get TWRP to flash before rooting and needed root before doing so but was able to flash TWRP after rooting via my system image.
Requirements:
An H811 Device
Already On The 10N Base
LG Drivers (Found Here)
A Windows PC
Send_Command Tools (Found Here)
Instructions:
Unzip The Send_Command Tools
Move The Rooted System Image Into The Root Of Your SD Card
Place Your Device Into Download Mode. (Shut Down Your Device. Once Off Holf Vol-Up + Plug In USB Cable)
Go Into Your Send_Command Tool Folder. Once your inside the send_command folder, hold Shift+Right Click and select "Open Command Window Here."
Type in: Send_Command.exe \\.\COM# (Replace the "#" with your devices actual COM number. To find this out, open Window's Device Manager (With your device plugged in) and find it under Ports
Type in: id
You should now have a "#" in the command window.
Type in (Or copy and paste this in): dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
It'll take a few minutes but a successful flash should bring you to another "#" prompt.
Type in: LEAVE
Enjoy
Downloads:
Stock Rooted 10N System Image
MD5: 847cdaf5adaf1b58945e473e8507f8c6
Additional information and clearer instructions can be found here. Same steps and procedures but with a different flash command.
Hope this was useful to some.
Enjoy,
Rydah
Hey. Thanks for doing this.
Should the "if" in the Send_command string point to the folder on the windows computer? It looks like it's pointing to the root of the internal storage as it's written there?
does not seem to work for me. I type in the last command and i get the # right away and reboot the phone and nothing has changed.
It worked for me after I had copied the system image to the root of the internal storage I believe because that command points there. Also, you have to be in Download mode for this to work in case you weren't aware!
custommsp said:
It worked for me after I had copied the system image to the root of the internal storage I believe because that command points there. Also, you have to be in Download mode for this to work in case you weren't aware!
Click to expand...
Click to collapse
i had the file on my sd card. ill move it to internal storage and try again.
and it worked lol thanks
Thank you, it works! Add this step; your phone must be in download mode.
Wooops lol I'll fix instructions
Sent From My LG G4
Rydah805 said:
Wooops lol I'll fix instructions
Sent From My LG G4
Click to expand...
Click to collapse
Did you ever fix the instructions?
YES!
Right. So instructions are not fixed yet. However, as mentioned, placing the image file on root on internal storage and putting phone in download mode gets the job done. Place phone in download mode by holding 'up volume' while plugging in cable and continue to hold until you see it tell you its in the download mode.
You must be on stock N build first?
Sent from my LG-H811 using Tapatalk
aaronrw said:
You must be on stock N build first?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
This system image does not include the 10N bootstack, so yes, you should be on stock N first.
Hey just a few tips
if you already have Android SDK or otherwise an instance of adb.exe installed, you should temporarily uninstall it, so that the adb.exe that is packaged with Send_Command doesn't conflict.
I copied the rootedsystem.img to my phone, used Send_Command, checked my id, and then used the dd command. There is no progress bar on the computer screen, and the progress bar on the phone screen does not move. Do not panic, this is normal.
Updated instructions and added MD5 for download in O.P.
is rootedsystem.img really 4.2g?
Rooted!
Holy Guacamole - this works amazingly well. Thanks much rydah
donbudafuko said:
is rootedsystem.img really 4.2g?
Click to expand...
Click to collapse
Yup... ?
docfreed said:
Holy Guacamole - this works amazingly well. Thanks much rydah
Click to expand...
Click to collapse
Of course. ?
Sent From My LG G4
I like this method best. Thank you!
Thanks for giving us an easy root method.
Sent from my LG-H811
worked perfect. thanks
with this method, will It come with a recovery? and if no, how can it be installed??
Background
Okay so the glass on my 2013 Moto X broke on September 27th I ordered a new one and while changing it I accidentally broke the digitizer so I disconnected the digitizer and the phone turned on while my digitizer with disconnected then i had no way of turning it off while my digitizer was disconnected the phone started to vibrate every 3 seconds until the battery died... so I was forced to switch over to my Nexus 6 because at the time that was my backup phone because I love the performance of my Moto X.. now a few months later yesterday to be exact my new digitizer arrived and I brought my Moto X back to life powers on and performs just fine
Problem
My wrist twitch to activate camera doesn't work
My dual chop to activate led doesn't work
Whenever I make a phone call or receive a phone call my screen turns off automatically but the phone call works just fine once the phone call has ended my screen does not turn back on I have to reboot the phone to turn on the display again
Phone info
2013 moto x on 5.1.1 stock rom locked bootloader rooted using crashes method with ultra slim root
any help or tip is greatly appreciated
Maybe, but it really depends what's actually wrong. The Moto has a TI MSP430 chip that handles all that 'motion, wave-to-wake, chop-chop' stuff and it's loaded from a /firmware folder or partition (have forgotten at this point). @masterifla figured out which files it was on 4.4.4 & 5.1 that got uploaded to the 430 and wrote a .zip file to change from 4.4.4's "wave to wake" to 5.1 "chop chop" or vice versa. I fixed some little bug in it, and stuck the working .zips up in this post although they may be elsewhere as well: (so :: these zips contain the firmware that actually does the wave-to-wake stuff and can be 'recovery-flashed')
http://forum.xda-developers.com/showpost.php?p=63616790&postcount=17
At least if that works, you'll know that it was the firmware for that chip, and if not, it might actually be the 430 chip(which you can see in the teardown). The post by me and anything by masterifla should be pretty well explained.
Cheers.
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
BADDINOROX99 said:
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
Click to expand...
Click to collapse
There still might be a way. I keep trying to have people get this to work, but I'm not sure of the outcome yet, so give it try if you like: Here's some steps:
1) Locked bootloader / no root means mostly that you can't write system, but I'm pretty sure you should be able to temporarily boot into a PC-based copy of twrp. Once in twrp (for one time say) you are root, and you have access to anything on your gizmo. In theory, you should be able to mount system read-write and change something in the file system.
2) Get the correct copy of twrp and adb (from dev forum for this box) and put it on a PC with fastboot in the same folder. To make this easy, called twrp "twrp.img" and call "fastboot" or "mfastboot" fastboot.exe (I am for some reason assuming you've got a PC, not a mac or linux, but the ideas are similar.
3) quick explain of the files in the .zip from above ^^ : 8 files prefixed by MSP that are located when on the moto in /system/etc/firmware. Unzip them and stick them in that same folder.
4) Tricky part : (I think) : reboot into the twrp.img on your PC by getting your device into fastboot / bootloader mode: (so .. volume-up&down&power keys all held down for ~10 seconds perhaps, then if you've gotten it right (it's touchy), you'll be in the bootloader where it has a small tiny text list of stuff like "continue, recovery, etc).
5) you're good with the phone if you've made it here: now on the PC from that folder, type in "fastboot boot twrp.img" and good luck. If it works, your phone will be in TWRP with root access. If not, I don't know another option at the moment.
6) Probably the rest is most easily done from the PC command (or shell) window where the files are. Since your device is in the bootloader and awaiting further instruction, you should be able to use adb to talk to recovery now. so carry on:
7) (get the files from your PC (the MSP prefixed ones) onto the device, so first remount system r/w):
Code:
a) "adb remount" // supposedly should remount system toggling the read attribute to write
b) "adb push msp* /system/etc/firmware/" // copies files to device unless I've got syntax wrong, try one at a time if doesn't work.
c) "adb shell ls -al /system/etc/firmware/" // list all files, and post them back here to see if it even worked.
d) "adb remount" // system partition back to normal ro state.
d) "adb reboot" // moment of truth, a reboot.
8) after things settle post-reboot, check out "wave-to-wake" , camera twist, etc. This works on 4.4.4 or 5.1 (if this other stuff above works).
Note: I could be way off on my idea that rebooting into recovery will give you enough functionality to do this, but I'm not sure what other choices you've got without being able to root. I guess another thing I'm wondering about is why you wouldn't be able to root the phone from recovery regardless of how you booted into it. You still can't unlock bootloader, but I'm not clear on what difference it makes at the moment.
Good luck. It's a "hail mary" pass.
thanks I got my stuff working again ? I screwed up in the file install part freaked out and reflashed stock and rerooted so everything is good now once again thanks
For some Urbane users, for whatever the reason may have been, they were unable to install the 1.5 OTA, the "dead" android continued to come up. This guide assumes that you have Minimal ADB and Fastboot installed on your computer, a guide that includes how to set your computer up for this is found HERE. This guide also assumes your watch is already on ADB debugging, etc, etc, else follow the previously mentioned guide.
READ ENTIRE GUIDE BEFORE YOU START. NEEDLESS TO SAY YOU'RE TRYING THIS AT YOUR OWN RISK..
Files needed:
- System
- Boot
- Recovery
(these are for 6.01 version, and can be found HERE with the 5.01 version).
- 1.5 update zip found HERE
1 - Connect your watch's charger to your PC and set your watch on the charger.
2- Open Minimal ADB and Fastboot, and type:
Code:
adb devices
and hit enter
3- If properly connected you should see something similar to "504KPJP00XXXX8 device".
4- Now type in:
Code:
adb reboot bootloader
and hit enter. The watch should reboot into the bootloader.
5- While in bootloader type:
Code:
fastboot flash system
and drag the System file you downloaded earlier to the Minimal ADB and Fastboot window, and hit enter.
6- When it's done installing type in:
Code:
fastboot reboot
and hit enter.
7 - Repeat steps 1-6 for EACH of the other two files: Boot and Recovery files you downloaded. Keep in mind that EACH TIME when you get to step 5 you must type in:
Code:
fastboot flash boot
for the Boot file, and
Code:
fastboot flash recovery
for the Recovery file respectively and drag their respective files to the window. So, to recap, do steps 1-6 for Boot, and 1-6 for Recovery. Got it? Good.
8- Get into bootloader mode again (see steps 2-4). Using the left and right (< >) arrows in bootloader screen on your watch look for "Recovery Mode" and hit the (o) option.
9- Now you will see the good ol' "dead" android. Fear not, touch the screen and you should get some options. Sliding your finger up or down scroll to "Mount /system", and swipe left or right.
10- Now slide down to "Apply update from ADB" and slide left or right to get into ADB sideload mode.
11- Once in sideload mode go to Minimal ADB and Fastboot window and type in:
Code:
adb sideload
AND drag the 1.5 update zip file you downloaded onto the screen, THEN hit enter.
12- If done properly the Minimal ADB and Fastboot window will start showing you some progress and so will the watch. wait until it's done. When it's done reboot your watch. Be advised it will take a little bit to power on, be patient!
You're all done!
Now you can go back and install TWRP, root, etc..
I want to point out that 1 or many of the above steps may not be necessary but this is exactly what I did to successfully flash the update. No wiping, no factory reset was necessary.
Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.
caughtmountain said:
Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.
Click to expand...
Click to collapse
Here. By the way what's so bad about 2.0?
How do I update to M1D65H (the last aw 1.5 update) ?
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
cubandanger05 said:
Here. By the way what's so bad about 2.0?
Click to expand...
Click to collapse
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?
razebond said:
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?
Click to expand...
Click to collapse
I believe so, yes.
Have installed updatedisabler.apk on both phone and watch (watch is rooted) both come up with "Check your watch to find the application". Still get nags about updating?
Has anyone got this to work?
updatedisabler is not working, somebody knows how to uninstall it?
First, it's slow and buggy. Google Assistant takes several seconds to load before you can speak to it, sometimes so long the screen times out before you can speak your command. I always get a notification vibration, but rarely get the notification card, destroying the most useful smart feature of the watch, and instead of cards peaking, I always have a full screen card of whatever song or podcast I'm listening to, that is persistent and blocks my watch face, destroying the most useful feature of not smart watches (since I can't see the time). But, those apps run on the watch natively by default, so if I try to start playing music or podcasts it can only playback locally from the watch, not start the playback on the phone. Do disturb on the watch is also now separate from dnd on the phone, which means when going into meetings I have to silence both independently. In short, what's wrong with aw2? Everything! Oh, and my battery just says 50% all the time since the update. Totally garbage.
Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.
Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.
mexiken said:
Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.
Click to expand...
Click to collapse
Yes, your bootloader needs to be unlocked
RunNgun42 said:
Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.
Click to expand...
Click to collapse
If you're on stock 1.3 you should be able to flash the update following the adb sideload steps
Hi guys. I tried to follow the steps, but the "adb sideload" part is not working. The watch presents an error: "can't mount /system". Any tips? Is there any 1.5 full rom out there?
[fixed]