Database Develop

[SCRIPT] GladRoot v4.3 (Bell 0.37.4, AT&T 1.26/1.52/1.57/1.83 Supported)

Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.​Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!​GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.​
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
​Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**​Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
​DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)​Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.​Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
​

I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?

Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results

So do this version allow sideloading?

awww yeahhh

PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.

plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload

After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?

drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?

drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?

Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?

shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?

s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.

drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.

Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).

Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?

PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.

tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?

Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...

when i run beforeupdate i get backup failed to execute properly
am i missing something?

[Q] Error when registering vs910.dll

I followed the LG Revo downgrade instructions pricisely but when attempting to register the vs910.dll after moving it to the newly created Models folder within C:\LG Electronics\LGNPST\ directory, I get the following error:
"The module vs910.dll was loaded but the call to DllRegisterServer failed with error code 0x80020009."
Can someone help?

Had same error on x64 bit system, I wasn't able to fix it though, I had to use a x32 version of windows on another computer. :/

From http://forum.xda-developers.com/showthread.php?t=1211295&page=2
open CMD with Admin privileges and then type
Code:
regsvr32.exe "C:\LG Electronics\LGNPST\Models\VS910.dll"
Click to expand...
Click to collapse
I was having the same problem, did this with no issues.

Code:
regsvr32.exe "C:\LG Electronics\LGNPST\Models\VS910.dll
Use the code i have posted, the one above has a typo. Make sure you check "run task with administrative privileges" in the "create new task" box as stated above.
Framework43 Had same error on x64 bit system, I wasn't able to fix it though, I had to use a x32 version of windows on another computer. :/
Click to expand...
Click to collapse
I got this to work on Windows 8 x64, so I don't think there is a problem with the type of Windows you have installed, but some problem somewhere else.

Thanks for the catch, I forgot they had the wrong code in the link. Fixed.

thank you
wow, that was awesome guys thanks so much, worked like a charm!!!
Now if someone could only figure out how to Root v6 so we don't have to do this downgrade nonsense....

I ran into the same issue, but started XP Mode on my Win7x64 tied in the usb port with the phone and everything went perfectly - rooted and installed Revolt mod in no time

follow up question
ok so now that I got that dll properly registered, I tried to root using Superoneclick but kept getting permission denied error so I did it manually through ADB and I think it worked, but after downloading SU and running it, it tells me I need to update my SU binary but whenever I try, the program crashes...help again!

I couldn't get the newest version of S1C to work, or the ABD method. It appeared to work in ABD, but would crash Superuser. I ended up using S1C v1.63 and it worked just fine for me.

Try using superoneclick version 1.7 and use the rageagainstthecage exploit if you're having issues with root. Make sure all antivirus is disabled before downloading and installing.
Go to clockwork recovery and do the "fix permissions" procedure. That might help, it did on a Thunderbolt today that had problems updating the su binary. Do rooted programs work?

dbeauch said:
ok so now that I got that dll properly registered, I tried to root using Superoneclick but kept getting permission denied error so I did it manually through ADB and I think it worked, but after downloading SU and running it, it tells me I need to update my SU binary but whenever I try, the program crashes...help again!
Click to expand...
Click to collapse
You can't use the latest version, you need version 1.7. Also, when you connect the phone to the computer, you need to pull down the notification menu and select "Internet Connection." USB Debugging will NOT start in "Mass Storage" or "Charge Only."

adrenaline_rush said:
Try using superoneclick version 1.7 and use the rageagainstthecage exploit if you're having issues with root. Make sure all antivirus is disabled before downloading and installing.
Go to clockwork recovery and do the "fix permissions" procedure. That might help, it did on a Thunderbolt today that had problems updating the su binary. Do rooted programs work?
Click to expand...
Click to collapse
I used S1C version 1.7 also - could not get it rooted otherwise. Also had to mess with the "Debugging Mode" to make it work - turn it off, then quickly turn back on when at Step 6. Once I did that, everything worked perfectly.

dbeauch said:
I followed the LG Revo downgrade instructions pricisely but when attempting to register the vs910.dll after moving it to the newly created Models folder within C:\LG Electronics\LGNPST\ directory, I get the following error:
"The module vs910.dll was loaded but the call to DllRegisterServer failed with error code 0x80020009."
Can someone help?
Click to expand...
Click to collapse
THIS IS BULLCRAP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!
CAN'T MOVE BACK TO 2.3.4 BECAUSE I CAN'T GET A DANG THING TO WORK. First, the components msi file wouldn't install because of some error code, plus i could never get VS810.dll to register. Even did research online, and found that people running 64 bit os were having trouble, so i used my 32 bit os computer BUT STILL DIDN'T WORK ... BEYOND USING A 32 BIT OS, I FOUND NO SOLUTION ON THE ENTIRE WORLD WIDE WEB TO GET THIS TO WORK!!!!!!!

wncoulte said:
THIS IS BULLCRAP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!
CAN'T MOVE BACK TO 2.3.4 BECAUSE I CAN'T GET A DANG THING TO WORK. First, the components msi file wouldn't install because of some error code, plus i could never get VS810.dll to register. Even did research online, and found that people running 64 bit os were having trouble, so i used my 32 bit os computer BUT STILL DIDN'T WORK ... BEYOND USING A 32 BIT OS, I FOUND NO SOLUTION ON THE ENTIRE WORLD WIDE WEB TO GET THIS TO WORK!!!!!!!
Click to expand...
Click to collapse
I had an issue getting the "VS910.dll" to register also. What worked for me was diabling the user account controls in windows. After you do that will have to restart your computer. Then it should register just fin
Sent from LG Revo Stock ZV8 Using XDA App

SnoeDogg said:
I had an issue getting the "VS910.dll" to register also. What worked for me was diabling the user account controls in windows. After you do that will have to restart your computer. Then it should register just fin
Sent from LG Revo Stock ZV8 Using XDA App
Click to expand...
Click to collapse
^^^^^
What he said... i just explained the process in another post in the developement section
Sent from my VS910 4G using XDA

kcarden said:
^^^^^
What he said... i just explained the process in another post in the developement section
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
how to do this in windows 8 please

dbeauch said:
I followed the LG Revo downgrade instructions pricisely but when attempting to register the vs910.dll after moving it to the newly created Models folder within C:\LG Electronics\LGNPST\ directory, I get the following error:
"The module vs910.dll was loaded but the call to DllRegisterServer failed with error code 0x80020009."
Can someone help?
Click to expand...
Click to collapse
Solution....
1. If you can not register this DLL, Go to safe mode on Windows 7 and register VS910.DLL.
IT works For me. 100%

Lenovo Ideapad K1 One-Click Root (Mostly)

First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Second, I take no credit for anything here except for writing the .bat file here used to do the work, as well as assembling the files as per the original post.
All credit goes to djmwj and his article found here:
http://rootzwiki.com/topic/8722-lenovo-ideapad-k1-rooting-guide-messy/
As the title states, it was very messy. The OP figured out how to make it go, but it was a bit fuzzy to follow. So, I thought I'd help folks out a bit and clean things up.
So, I took the instructions presented in the OP, and condensed them into one download with one .bat that does everything from start to finish, minus installing the respective drivers for ADB and NVFlash. However, the drivers are included in the download.
Instructions:
1. Extract K1Root.rar to the directory of your choosing.
2. Connect your tablet to your PC with the USB cable.
3. With your tablet off, press POWER+VOL_UP+VOL_DOWN until the screen turns on, but displays only black.
4. Windows should detect the device, but not install drivers.
5. Go into device manager, select the APX device, choose update drivers, and install the drivers from the aptly named NVFlash_Drivers folder.
6. Open up the NVFLASH_HOME folder and run the file K1Flash.bat
7. Make your desired choices when prompted, and enjoy.
Notes (PLEASE READ BEFORE USING):
THERE MAY BE BUGS! I used it on my own stuff before releasing, and all of the essential components work as they should, however, there may possibly be a minor hiccup somewhere in the script. This should not damage anything. If you have doubts, you're welcome to examine the .bat and check it for yourself.
Please be gentle. I am not a full-time developer. I just wrote this to help make the process simpler for people.
The OP suggests you download and read the partition table, and then name the backup files based on that. This script names the backup files based on the flash.cfg script referenced in the OP, which is what controls the flashes used anyway. So, there shouldn't be any irregularities, however, I can't speak for every device on the planet.
This does NOT use the latest OTA updates. The rooted files being flashed are the default ones from the original download. You can easily adapt this to any files generated from the latest OTA files by simply dropping them in the NVFLASH_HOME file.
To install the SU properly, you have to install ADB drivers midway through the script. There's probably a way around this, but I didn't find it to be too inconvenient.
The ADB drivers are also located in the NVFLASH_HOME folder. Just do like you did when installing drivers in step #5, but instead point to NVFLASH_HOME.
Um...um...
That should be it. Obviously, use at your own risk. Let me know if there are problems with the script, and I will fix them.
Oh, and party on, Wayne.
http://www.megaupload.com/?d=AG10XE25
EDIT:
Attached is an updated .bat file which fixes a few errors in the original script, plus adds more userability. Just extract to the NVFLASH_HOME folder and run.

digitalhigh said:
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Click to expand...
Click to collapse
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.

gallahad2000 said:
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
Click to expand...
Click to collapse
Wow. Yeah, I'm pretty sure the key used is just for the Ideapad. Thanks for pointing that out. My dumb a$$ must've blanked out and just used the group name when posting.
And just to be fair, the original poster does include everything needed to do stuff in windows as well - it's just very hard to discern from the post.

question
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.

jfkerekes said:
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
Click to expand...
Click to collapse
We need to be able to root and unlock the bootloader first.

Does the root method work on the 121211 update?
Or is there a way to flash back to the older firmware?

the OTA update 12 12 11.... seems to be update.zip style with no .img files inside. just loose files like normal rom updates. doesnt seeem like you can drop the files in as suggested. or i have the wrong OTA....
oh and is this for LINUX as the OP or work in windows too??

Hi, I was wondering, is this procedure works for the Lenovo ThinkPad 1838-25U? I'm thinking to buy it to give a test ride, i sold my Transformer 101 to buy the Prime but it seems like Asus is taking vacations on the delivery shipments. Is this a good tablet? or is better to wait for another version?

READ THE POST
IDEApad not THINKpad. no it wont work.

First of all- thank you so much for creating this script! I have been putting off rooting this device due to the "messy" nature of the original post.
I was hoping you could help me troubleshoot, I have tried both the new K1 root application and the original .bat file. I know the drivers are working because the script makes it as far as creating and formatting partitions and successfully pushes the bootlooder.bin but then:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
I've tried everything I can think of... any ideas?
Thanks again.

I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?

taiz said:
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
Click to expand...
Click to collapse
Yes you have to roll-back to 04 stock and then apply the OTA's

Backup of the stock lenovo .apks!
File 1:http://www.mediafire.com/?r7iskr3wrfx4u01
File 2:http://www.mediafire.com/?fymdv9e9kmj332s
File 3:http://www.mediafire.com/?w33k205ej4fpbcl
A big thanks to Khanning who was nice enough to walk me through the adb commands and bear with me when I couldn't get adb over usb to work.

This may fix your issues http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50

Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
It means you are not in APX mode. Read the PDF and follow the instructions for installing the APX drivers. This should fix your issues.http://forum.xda-developers.com/show...9&postcount=50

I just completed step 3 flashing the image went fine up to bootloader .bin sent successfully ...then it says
File not found recovery.img
Failed executing command 2147473647 Nverror 0x4
Command failure : create failed
Edit the link u posted is not working and the drivers are installed
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Click to expand...
Click to collapse
Glad to hear it worked for you.
TD

I recently got this device and looking for a way to root this device without having to roll back to the factory default rom and then having to update again using OTA.
Question, am I in luck, is that at all possible or do I have to really rollback and reinstall everything again?
Thanks!
Sent from my K1 using Tapatalk

Anyone have the root? Megaupload is down forever.

[Q] Boot loop and ADB push problems. Please help.

Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks

mothmansound said:
Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks
Click to expand...
Click to collapse
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.

Crossvxm said:
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.
Click to expand...
Click to collapse
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.

mothmansound said:
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.
Click to expand...
Click to collapse
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.

Crossvxm said:
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.
Click to expand...
Click to collapse
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.

mothmansound said:
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.
Click to expand...
Click to collapse
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.

Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.

Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.

I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.

mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Lol i misread that disregard the rest. What custom kernel are you trying to use? Remember each device is the same but also different. I had 2 LG G2s that would not double tap to wake, but would double tap to sleep. All the rest of them worked perfectly. Have also came across friends with G2s that wouldnt work

mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Best way is to flash the kernel in my signature. After you flash it, double tap to wake should be working automatically.

SO... This happened... Secure Boot Error Code 1003 MODIFIED!!!

So, I wanted to go back to stock, after trying multiple steps listed here in XDA-dev, and multiple youtube videos and webpages. I will list the erros bellow :
LgUP - "unknown device"... I been having issues with this software since I first attempt to run it. I tried on 2 different computers and have the same issue. Installed the DLL first (like many suggested ) then LGUP and nothing
Flashtools14 - I get the .kdz and attempt to do either "normal" or "CSE" . after comes another window, stating the progress, do not disconnect the phone .. blah blah. After going thru that it stops at 9 % and nothing happens.
After couple of weeks, I thought that if Relocking the bootloader i would be able to go into the "factory Reset" with out booting from TWRP and going back to stock..*stupid move*, and so I did... And here we are with error 1003 MODIFIED
I been looking for answers in order to fix this issue, but they go to the same path... using LGUP or FLASHtools in which both dont work with me
I have this phone
LG G4 H811 Tmobile
Now im trying to see if i can conver a KDZ into a TOT since that process I also know.
If somebody have another method please let me know!
I cant go into recovery since I keep getting the error. pretty much I have a paper weight.

An3ru said:
So, I wanted to go back to stock, after trying multiple steps listed here in XDA-dev, and multiple youtube videos and webpages. I will list the erros bellow :
LgUP - "unknown device"... I been having issues with this software since I first attempt to run it. I tried on 2 different computers and have the same issue. Installed the DLL first (like many suggested ) then LGUP and nothing
Flashtools14 - I get the .kdz and attempt to do either "normal" or "CSE" . after comes another window, stating the progress, do not disconnect the phone .. blah blah. After going thru that it stops at 9 % and nothing happens.
After couple of weeks, I thought that if Relocking the bootloader i would be able to go into the "factory Reset" with out booting from TWRP and going back to stock..*stupid move*, and so I did... And here we are with error 1003 MODIFIED
I been looking for answers in order to fix this issue, but they go to the same path... using LGUP or FLASHtools in which both dont work with me
I have this phone
LG G4 H811 Tmobile
Now im trying to see if i can conver a KDZ into a TOT since that process I also know.
If somebody have another method please let me know!
I cant go into recovery since I keep getting the error. pretty much I have a paper weight.
Click to expand...
Click to collapse
can you try this file place in c: programfiles /lge/lgup/model
ther error you got am not sure what it is this is for LGUP to recognize your phone.

raptorddd said:
can you try this file place in c: programfiles /lge/lgup/model
ther error you got am not sure what it is this is for LGUP to recognize your phone.
Click to expand...
Click to collapse
Hey Raptorddd
we read each other again, i did put those files in the C:/programFiles(x86)/LGelectronics/LGUP/model
Fire up LGUP and still have the same issue Model " uknonw " COM Ports [ COM41, GENESIS]

An3ru said:
Hey Raptorddd
we read each other again, i did put those files in the C:/programFiles(x86)/LGelectronics/LGUP/model
Fire up LGUP and still have the same issue Model " uknonw " COM Ports [ COM41, GENESIS]
Click to expand...
Click to collapse
have done a search with that specific error see if someone fix it. ?

raptorddd said:
have done a search with that specific error see if someone fix it. ?
Click to expand...
Click to collapse
Wich error you mean, the one in LGUP or The modified 1003?, Yes i have done research on both errors, but nothing seems to work.

An3ru said:
Wich error you mean, the one in LGUP or The modified 1003?, Yes i have done research on both errors, but nothing seems to work.
Click to expand...
Click to collapse
sorry i have no idea. maybe pos in thread go back to stock.

So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need any Linux or best would be if just using FWUL ( http://tinyurl.com/FWULatXDA ).
I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash (we need to know the path later e.g. /home/android/Downloads/)
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
[*]sudo python2 partitions.py --list
If this lists your partitions then we can proceed with flashing.
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzmanager.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
WARNING: by default the kdzmanager will not overwrite userdata (which would be like a factory reset) and I would recommend to leave it out always and better choose the LG factory reset menu (after flashing completed) if required. If you still want to flash it use --with-userdata as a parameter (can take a loooong time then btw).
bash kdzmanager.sh --flash extracteddz/
sfX
Sent from my LG-H815 using XDA Labs

steadfasterX said:
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need Linux or best would be if to just use FWUL ( http://tinyurl.com/FWULatXDA ). I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
First instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
sudo python2 partitions.py --list
If this lists your partitions then we can proceed with the flashing.
I have to go to now but will go on tomorrow with the rest of the instructions if you want to go this way..
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Sure man i will do this and try to instal linux or go into your guide. One questions, which version of linux i need !?. I did a quick read on your post, is quite alot information to take, but i will try it!!!
Edit. I was able to download virtual box with extensions. Plug in my lg g4 and make sure that it read it. Double click on LG laf (auth) - * there is no LG laf NG* - termina opens, open new terminal type first command, ask for password - password is different than the ones mentioned in the OP - error : Python2: cant open file 'auth.py' : [Errno 2]\ No such file or directory

An3ru said:
Sure man i will do this and try to instal linux or go into your guide. One questions, which version of linux i need !?. I did a quick read on your post, is quite alot information to take, but i will try it!!!
Edit. I was able to download virtual box with extensions. Plug in my lg g4 and make sure that it read it. Double click on LG laf (auth) - * there is no LG laf NG* - termina opens, open new terminal type first command, ask for password - password is different than the ones mentioned in the OP - error : Python2: cant open file 'auth.py' : [Errno 2]\ No such file or directory
Click to expand...
Click to collapse
use his FWUL dont use linux use that one he provided. also please hit the thanks buttonto my friend steadfsterx.. on lower part right hand side..:good:

raptorddd said:
use his FWUL dont use linux use that one he provided. also please hit the thanks buttonto my friend steadfsterx.. on lower part right hand side..:good:
Click to expand...
Click to collapse
Hey Raptorddd
yeah I use the program he suggest me, im just waiting on him, also thank you for the help! I appreciate it

An3ru said:
Hey Raptorddd
yeah I use the program he suggest me, im just waiting on him, also thank you for the help! I appreciate it
Click to expand...
Click to collapse
It seems you havent downloaded the latest FWUL version v2.0? In v1 there is no LG laf NG.. But we can use that FWUL version as well. it's just very very outdated
If you want to have the best FWUL experience use v2.0 and download the persistent mode version of FWUL (it's the ZIP) and read the FAQ to make the persistent mode available in VirtualBox!
This combo is fantastic
I come back in about 3 hours to complete the guide...
sfX
Sent from my LG-H815 using XDA Labs

steadfasterX said:
It seems you havent downloaded the latest FWUL version v2.0? In v1 there is no LG laf NG.. But we can use that FWUL version as well. it's just very very outdated
If you want to have the best FWUL experience use v2.0 and download the persistent mode version of FWUL (it's the ZIP) and read the FAQ to make the persistent mode available in VirtualBox!
This combo is fantastic
I come back in about 3 hours to complete the guide...
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Oh yeah, the main download server was a lil confusing but i was able to download it, i will be out. But i will be reading the FAQ and the new set of instructions!!!!

An3ru said:
Oh yeah, the main download server was a lil confusing but i was able to download it, i will be out. But i will be reading the FAQ and the new set of instructions!!!!
Click to expand...
Click to collapse
sorry for any confusion but thx for reporting. I have updated the OP to point to the new versions more clearly.
will come back asap
OK here you go: https://forum.xda-developers.com/showpost.php?p=73756863&postcount=7
let me know how it goes

steadfasterX said:
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need any Linux or best would be if just using FWUL ( http://tinyurl.com/FWULatXDA ).
I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash (we need to know the path later e.g. /home/android/Downloads/)
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
[*]sudo python2 partitions.py --list
If this lists your partitions then we can proceed with flashing.
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzextract.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
WARNING: by default the kdzmanager will not overwrite userdata (which would be like a factory reset) and I would recommend to leave it out always and better choose the LG factory reset menu (after flashing completed) if required. If you still want to flash it use --with-userdata as a parameter (can take a loooong time then btw).
bash kdzmanager.sh --flash extracteddz/
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Hey steadfasterX, I download version 2 of the FWUL and still have the same error. as Sudo not found. Am I doing something wrong?! o.o

An3ru said:
Hey steadfasterX, I download version 2 of the FWUL and still have the same error. as Sudo not found. Am I doing something wrong?! o.o
Click to expand...
Click to collapse
you double clicked "LG laf NG" icon ? in this terminal u have to type the auth command
consider to come into IRC instead (channel carbon-user on freenode)
or just by clicking this link: http://webchat.freenode.net/?channels=Carbon-user
sfX

Saw something a few posts back about virtualbox or vmware...
FWIW, Historically, virtualized Linux Guests don't do so well with USB. I've always had to install it natively or use a LiveUSB distro with persistence.

barcodelinux said:
Saw something a few posts back about virtualbox or vmware...
FWIW, Historically, virtualized Linux Guests don't do so well with USB. I've always had to install it natively or use a LiveUSB distro with persistence.
Click to expand...
Click to collapse
VirtualBox plus FWUL works like a charm.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzmanager.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
Click to expand...
Click to collapse
Your tool is far better than this one because your tool has extracted many such partitions of LG G4 H811 20o KDZ which that tool didn't. E.g. PERSISTENT, DEVINFO, MODEMST1, MODEMST2, DRM etc.

rizkhan999 said:
Your tool is far better than this one because your tool has extracted many such partitions of LG G4 H811 20o KDZ which that tool didn't. E.g. PERSISTENT, DEVINFO, MODEMST1, MODEMST2, DRM etc.
Click to expand...
Click to collapse
yea thx!!
and just checkout my new signature
.

steadfasterX said:
yea thx!!
and just checkout my new signature
Click to expand...
Click to collapse
Well. Yet another PhD thesis :good:. There is one thing that I couldn't understand though. At one place you mentioned that Hint: not wiping userdata can occur in a bootloop while at the other place you said WARNING: by default the kdzmanager will not overwrite userdata. Does it mean that flashing can cause bootloop if kdzmanager is used with default options?
Secondly, does it also support TOTs as LGUP does?