Database Develop

[Q] Dell S10 Pro - Need help in Updating

Hi,
Sorry for posting in this as I couldnt find any thread for S10.
I have a S10 Pro with the following version of ROM installed.
Android 3.2
Build Version : 201107271412 (This is a strange as I couldnt find this in any other....)
Kernel Verrsion : 2.6.36.3-00055-gdb0a63d
Is it possible to update it to 569 or any custom ROM?
Thanks and Regards,
manakun

Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.

TheManii said:
Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.
Click to expand...
Click to collapse
Thanks for you prompt reply.
The OEM Version is GALLO1A155111
I havent used nvFlash but I shouldnt have problem using it. Will make a backup. I dont mind if it cannot be restored.
Awaiting your instructions.
Thanks,
manakun

I am yet to update S10.
Help appreciated.

Things you'll need to know:
How to use the command line
How to install drivers on windows
Windows vista or newer
Download usbNvidiaBootdriver.zip
Download NVflash.zip
Download 568 bootloader.bin
Put Device into APX mode
Hold down power and reset button
Install apx driver
Extract nvflash
Boot device into APX mode
Command to do so: "nvflash --bl <path to bootloader.bin> --go"
<path to bootloader.bin> is whereever you saved bootloader.bin to
Begin dumping each partition
Command to do so: "nvflash -r --read <N> <filename>"
<N>: number of partition to dump
Partition List - XDA wiki
Partitions we need to dump 551: 2, 3, 4, 6, 7, 8, 11
Filename is whatever you wish to name file, recommended to name them after their partition number, eg p2, p3, p4, etc
After you have it dumped please 7zip and upload somewhere
Updating to a different rom uses similar steps if you cannot use "check for updates" from inside rom
If you do not know how to use the command line, there are tutorials on the internet.
If you are using a x64 version of windows, you will need to put your device in "test signing mode" or "disable driver signature verification mode", there are also instructions on the internet.

Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.

manakun said:
Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.
Click to expand...
Click to collapse
Yes, try readimg here: http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide
Woops! This is for a S10 not S7!

the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear

TheManii said:
the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear
Click to expand...
Click to collapse
Thank you. I have entered into APX and able to get the content of the partition.
I have sent the uploaded link in PM.
I would appreciate if you guide me in flashing the official PKG.

Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.

TheManii said:
Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.
Click to expand...
Click to collapse
Thanks for the instructions. However I was not able to enter into recovery mode. Tried couple of times.
Advice appreciated.
BTW, is it possible to flash all the partitions manually using nvflash?

I assume you have a working recovery, you may need to be make sure the battery has enough charge.
I'm not positive, but the S10 might be like the S7 wherein it wont go into recovery mode if the battery is below 60%. Even if it is charged entering recovery takes multiple tries even if you're doing it correctly.
If you can boot into android, you can simply use adb.
Enable "android adb debugging" from settings, install the adb drivers (fastboot+adb.zip from the dev subforum) and do "adb reboot recovery" from the command line.
Adb.exe is included in the mentioned zip.
Then try again, if the recovery does not want to do a pkg update, i'll upload the 568 recovery and we can try after flashing that.
If that still doesnt work I'll keep providing more files until it does, i would like to avoid having the user (ie anyone else attempting to repeat this in the future) do a full flash.
I would strongly prefer figuring out the minimum steps needed to force update a S10, as fullflashes did far more damage then they helped for the S7 due to someone providing a fullflash including their device specific data and nuking dozens of devices that way.
Just as much I'm not sure you can flash bootloader.bin from nvflash on the S10, i've attempted it and it didnt stick. It could be user error and fastboot may be able to flash it, the rest should either be flashable or not relevent.
If it were not for the bootloader, I could simply provide 569 as an update.zip flashable with CWM/S10, but I dont know offhand if the 551 bootloader is compatable with 569 as it's android 3.1 vs 3.2.

I was able to reboot to recovery from adb.
I get "Version check not allow update" error when I try to update from 568/9 pkg file.
Is it possible for you send me the 568 recovery img? And would appreciate on guiding me on how to flash using nvflash.
BTW, The 551 I have is Android 3.2.

i will upload the 568/9 recs, if that still doesnt work ill upload 569 as an update zip and you can flash with cwm
edit:
568
bootloader.bin
recovery.img
569
bootloader.bin
recovery.img
to flash a recovery (or any file in general)
boot into apx mode
nvflash -r --download <N> <filename>
<N> is the partition number
<filename> is the path to the file being flashed
flash the 568 rec and try using the 569 rec, you can attempt to flash the bootloader if you wish.
Keep in mind that flashing the bl is seperate from using it to boot in step 1, that step only loads it into memory and is lost on reboot.
the partition numbers are in the wiki.
if none of these work i'll provide more files until it does

Thanks for the upload.
Didn't have any luck with 568/9 recovery.
Strange behaviour with S10...still getting the Version mismatch Error...
I have flashed Clockwork Mod 6.0.1.2 . Would really appreciate if you could upload the update.zip.
It should work with CWM(hopefully). Worst case scenario..should try manually flashing the required partitions.

I'll upload 569 as an update.zip, it wont help you for new released roms in the future, but who knows when dell will release another update.

Thank you. Thats alright. But I guess Dell wont be releasing another update for S10.

update-S10-Stock-569-1.zip
I do not have the original update script, though I believe I have a close approximation.
If there's any issue installing it let me know, you'll need either CWM or TWRP to install it, install those in the same manner as the stock recovery. Links are in the dev subforum, make sure you grab the S10 ones and not the S7 ones.

Thanks for the upload.
I have installed the CWM and flashed the zip as specified in the following link.
http://forum.xda-developers.com/showthread.php?t=1780133
However, the system doesnot load after the flash.
I get the Dell Logo and it doesnot boot.
Would appreciate your support.

Try these in order until something works:
Did you try fac resetting from CWM?
If that doesnt work, try flashing the 569 bootloader.bin again.
If that still doesnt work try flashing CM9mod (and fac resetting) (to see if anything boots)
If it still doesnt work after those, I'll upload an nvflash dump as a last resort
How far does the bootlogo go? Does it blink once? Does it go to the animated swirl?
Initial dell logo: cpu works
1st blink, to dell logo: kernel is loading
Animated swirl: android userland is loading

Rooting Problem

Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
EDIT: What I did from beginning was followed this video "How to Root the HTC One-FlamingArio"to the point where you try and flash the recovery fastboot. That didnt work so after trying to fix that I tried How To Root HTC One & Unlock Bootloader - Easiest & User Friendly- The smoking Android ( super boot a 1 click install) that made my bootloader screen turn to tampered. after that I tried One_M7_All-In-One_Kit_v1.
Note in all in one kit I did erase cache and standard recovery works fine, I've re-installed it may times.
Cant post links yet but I gave video names.
EDIT: when I do the cmd fastboot devices my device shows up when I do adb devices nothing shows up could this be part of the problem?
Thank you all for your help, I re-installed all the programs on my laptop and redid all the steps and it worked. Bye!

Try this in ABD fastboot erase cache then flash the recovery again i hope this helps:fingers-crossed:

What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps

Tonberry23 said:
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
Click to expand...
Click to collapse
Keep an eye on this thread http://forum.xda-developers.com/showthread.php?t=2302870
Many people are looking for the Telus RUU.
Can you still access standard recovery? If so try reverting to factory settings (all data will be lost) and try to boot.
If you can get it to boot you should have more luck in trying to root your device.
I know that I had some issue's trying to get root on my device. But once I got S-off with revone, I was able to install root no problem.
ArmedandDangerous said:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Click to expand...
Click to collapse
But I would agree, if you can post the steps you have taken so we know where the bottleneck is.
Hope this helps you out bud

Still need help

Tonberry23 said:
Still need help
Click to expand...
Click to collapse
Nice to see you sorted it

Assuming you have actually flashed a recovery image to your device, you will then need to push a ROM to your sd card so that you can flash it in recovery.
Just do the following:
1. I am guessing you have the HTC drivers installed on your PC.
2. Download the attached adb.zip and unzip it to a folder on your C drive and call the folder whatever you like.
3. Boot your device into recovery and plug it in to a powered USB port on your PC.
4. Navigate to the folder that you just created on your PC and copy your ROM zip into it. rename the ROM zip to 'rom.zip' to make life easy.
5. Inside the folder, press and hold the shift key and right click in a blank part of the window and select 'Open command window here' (screenshot attached).
6. Type 'adb push rom.zip /sdcard' (don't use the quote marks)
7. Press 'enter'
8. Once the zip has finished being pushed to your sdcard, you can reboot into recovery and then flash it as normal.
EDIT: That will teach me not to read to the very end of a post. I'll leave this here for someone else.

Got OTA update but stil in 4.4w1

Hello,
I have my G watch R for a week and because there was no update, i've tried to install it by myself after reading some posts on XDA.
I've tried that :
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot flash recovery filename.img)
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
All this works until the "sideload" part because ADB can't see my watch when it's on recovery mode.
So i have locked again the bootloader and i thought to give up, when yesterday, OTA arrived...
But it hasn't worked : a bar has loaded and it arrived on a red triangle with an exclamation mark, i've clicked on it and i had the recovery mode menu (reboot, install from adb, etc)
What can I do to make work this OTA ?
Thanx for help !

have you tried to flash the original recovery?

Yes, I've tried several times, I think that is why i can't update with OTA.
But is there a solution ? Is it possible to reinstall original recovery and will it solve my problem ?
Or must I install the update with ADB ? Because I still don't know how make the watch recognized when in recovery mode (not even recognized with a yellow triangle, like it was unplugged )

I had the same problem but with 4.4w.2 and I solved it flashing the stock recovery. unfortunately I can not find your recovery version, I would have linked. to manually update do not know ... I'm sorry. Find your recovery and flash it!

Thanx for your answer,
I thought to do that, but I neither have found 44w1 stock, i'm trying with 44w2 stock and it doesn't work.
I'll try to find 44w1 stock, thanx for confirmation about this way.

So, while I can't find 44w1 stock (i think nobody has uploaded it on the internet because nobody wants to put 44w1 on his watch ^^ ), I've tried TWRP Recovery
When I try to launch the 5.5.1 zip install , I have this error message on the watch in TWRP Recovery :
"this package is for device: lenok. this device is dory"
I've made some research and found that Dory is for G Watch and not for G Watch R, so what ?
I don't understand...
Anyway, if someone knows where to find 44w1 stock...

Did you enabled the debugging mode and gave permission for it on the watch?

sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!

Have a look here... http://4pda.ru/forum/lofiversion/index.php?t647135-20.html.
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.

Genna7 said:
Did you enabled the debugging mode and gave permission for it on the watch?
Click to expand...
Click to collapse
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
2k4ever said:
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Click to expand...
Click to collapse
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
dunjamon said:
Have a look here... *url*
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Click to expand...
Click to collapse
Thank you but i have all those images, I think I need 44w1 recovery and only this one
Thank you all

what happens if you just flash the 4.4w2 full image? I remember there being issues with the 4.4 recovery and I had to manually update to the 5.0.1 recovery before then upgrading further.
edit...what drivers are you using? I think you need the adb composite ones and not the normal adb ones.

I'm using the naked ones I think.
What image are you talking about ? System or recovery ?

Ze_Pend said:
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Click to expand...
Click to collapse
The OTA ones from my link.

Ze_Pend said:
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
Click to expand...
Click to collapse
flashing a recovery happens in fastboot mode, which requires an unlocked bootloader, but not enabling the debugging mode
sideloading however happens (once the recovery has been loaded) through ADB - and ADB requires the right drivers on your PC as well as the right tools/developer environment
try to connect your normally booted watch to your PC and run
PHP:
adb devices
if that lists your watch, you are good to go, otherwise ADB isn't set up properly

The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode.
That's what I said first

dunjamon said:
The OTA ones from my link.
Click to expand...
Click to collapse
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.

Ze_Pend said:
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Click to expand...
Click to collapse
Do you have the G Watch R (round) or the G Watch (Square)?

"The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode."
I had this problem too. When you're in recovery mode you have to open the windows device manager and windows should tell you something about an uninstalled driver. You need to right click this device and install the adb drivers.

Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...

Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!

It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.

Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T

weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error

Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...

What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.

Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!

[STOCK][M][TMO] Guide H811 20i & 20o Bootloader Unlock + Root + TWRP

Note : This guide is for H-81120-I & H-81120-O the latest update any firmware version below it will cause hard-brick so be careful before attempting anything, i wont be held responsible.
As a user with less knowledge about Commands and all, i was searching for answers by reading threads here and there and found my answers though some time tricky and sometimes easy.
Also in reading those threads i found many fellow members stumble upon resulting Soft bricks and in some cases a Hard brick or can say making their beloved G4 a paper weight.
So i thought i must put some really easy steps in order to clearly guide people like me who are too noob to understand the sophisticated developers steps.
Another reason for this Thread is also i saw many people asking about how to etc after updating to 20-O update for our H811 MM.
Few things to Prepare before Start
1- Properly Install Drivers for your H811 Variant of G4, cant find them Install LG Bridge.
2- Read the Whole thread before starting anything.
3- Confirm that all requirements are full filled and your variant is capable of everything mention in the OP.
4- Enable Developer Option then inside it enable OEM unlock and Usb debugging.
5- Always use Command prompt as Administrator.
6- Make a folder name G4 and paste all the file required for the unlocking in it for easy access and remembrance.
7- For Safer side after unlocking the bootloader boot into TWRP from fast boot and do not install TWRP.
8- Flash your SuperSU after that boot into android and see if all works.
9- Again Via Fastboot boot into TWRP make a backup of everything working fine. Boot into android.
0- Again same Via Fastboot boot into TWRP and now install your TWRP image via TWRP install function. So if by any means this is the culprit you can still revive your phone via your backup.
Attachments to Download
1- Adb Package can be found Here.
2- Download the latest TWRP.img 3.0+ from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Since downloading is complete now simply unzip the adb folder (containing fastboot by default) and paste both the TWRP image file and SUPERSU zip inside it.
Now Hold Shift and Open Command prompt here.
1- Input command to see if your device is visible in ADB.
Code:
adb devices
if you see your device and the status is off line then there will be a prompt on your G4 screen waiting for approval, accept it and input same command now all will be fine.
2- Now input below commands one by one. ( All credits to Autoprime )
Code:
adb reboot bootloader ( This will reboot your device to Fastboot mode )
fastboot oem unlock ( This will wipe all your data )
fastboot getvar unlocked ( This will check your bootloader status: Should be successful )
fastboot boot twrp-3.0.2-0-h811.img ( Phone boots TWRP ) Please put the full file name with .img extension or it wont work.
3- Now the Phone should be in TWRP install SuperSU from there which you have already pasted inside your external SD card.
4- Reboot to system and see if SuperSU is installed. In some cases First flash of SuperSU does not work if your case is same the again boot to Fastboot and from there boot into recovery, since your bootloader is unlocked no need to repeat the unlock OEM command.
5- Now for safer side follow the steps 7, 9, 0 mention in Preparation heading above.
Hopefully all will be in your favor.
Useful Links if you still fail
Kdz 20-O after download must be unzipped
H81120o_00_0613.kdz
LGUP Software:
( All credits to MicroMod777 )
Disclaimer: Nothing in this thread is my work, if i have missed any credit please do let me know i will add. I know several guides are available for same purpose so if any body finds it offending any rights can ask the moderators to remove this thread. The purpose only is to guide simple people like me to save their devices from getting bricked.

As by reading the thread many people are falling for permanent TWRP installation as its mention in the OP anyways for people not getting permanent Recovery follow below:
Boot to TWRP from fastboot Bootloader
When recovery comes up click Install >>>> then in the right below corner you ll see a tab for IMAGE >>> press it browse the recovery IMG which you stored in your SD card >>> swipe to flash >>> From asking where to install >>> select recovery >>> DONE.

SignatureBoy said:
Attachments to Download
1- Adb Package can be found Here.
2- Download the from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Click to expand...
Click to collapse
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.

DrakenFX said:
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
the ADB package i uploaded contains the Fastboot inside it
The thread clearly states it for 20-O

SignatureBoy said:
the ADB package i uploaded contains the Fastboot inside it
Click to expand...
Click to collapse
ok i meant the TWRP file needs to be in the same folder where Fastboot file is

DrakenFX said:
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
Click to expand...
Click to collapse
That is also mention if you read the first post,
Since downloading is complete now simply make a folder and put all files downloaded inside it unzip the adb folder and paste both the TWRP image file and SUPERSU zip inside it.
Click to expand...
Click to collapse

SignatureBoy said:
DrakenFX said:
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
The thread clearly states it for 20-O
Click to expand...
Click to collapse
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.

ApokrifX said:
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
Click to expand...
Click to collapse
yes it is for 20-O only

SignatureBoy said:
yes it is for 20-O only
Click to expand...
Click to collapse
Thanks for clarification. I’d change 1st post a bit:
Few things to Prepare before Start
0. LG G4 with 20o (stock) firmware.

When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
DanGarion said:
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
Click to expand...
Click to collapse
Nevermind, I forgot about OEM Unlock...

thanks for the write up

This is not specific to 20o. It's the same steps we've been using all along. Nothing new to see here.
Sent from my LG-H811 using XDA-Developers mobile app

problem with fastboot
Thanks you for helping:fingers-crossed:

problem with fastboot
Hi,
I am a newbie in xda. I am trying to root and install TWRP into my lg g4. I am using software version H81120o. I checked enable OEM unlock and USB debugging. I have downloaded lg driver though lg bridge and all the files from the post. However, I got two problem while installing the twrp-3.0.2-0-h811.img.
1st problem (stuck here and need to reboot also not showing h811 on "the list of devices attached" after typing command "adb reboot bootloader"):
C:\Windows\system32>adb devices
List of devices attached
LGH811xxxxxxxx device
C:\Windows\system32>adb reboot bootloader
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.012s
C:\Windows\system32>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
cannot load 'twrp-3.0.2-0-h811.img': No error
2. 2nd problem(stuck here and need to reboot):
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
< waiting for device >
I checked online this problem might do with driver not up to date. Under device manager, my lg g4 is recognized under android device with android bootloader interface.
What should I do now?
Thanks you for helping:fingers-crossed:

This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??

I did everything but can't seem to get TWRP installed

Thanks a lot for this write up. I have been trying for about 2 weeks to root my g4 and it worked finally, So many thanks to you

The Remedy said:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
Click to expand...
Click to collapse
same problem here but I just now got it working...sort of . I still can not make anything come up except the factory data reset when I use the phone volume and power button.
I thought it might be just that I wasn't coordinated enough so I downloaded this small app to do a recovery reboot.
After I installed the app and used it, I got the little android guy with his chest opened with the red triangle. I took out my battery, put it back in and booted my phone with the power button.
I then connected my phone to computer via usb and went back into adb and opened TWRP and installed the twrp-3.0.2-0-h811.img again but this time I looked around a little more first, and noticed a setting to either install in boot or recovery partition. I selected recovery partition (neither were selected) and installed it. Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.

I had the same issue but when u get into twrp make sure the IMG is in your SD card and to permanently have twrp installed go to home and press install.. Choose from image and install hope this helps
Sent from my LGLS992 using Tapatalk

fuzzy_ said:
same problem here but I just now got it working...sort of ................
Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
Click to expand...
Click to collapse
In regard to booting into TWRP recovery with just the power and vol buttons, I just read this on another thread:
It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
I tried this and it worked for me as well.
I had been there before and tried it and it did a factory reset after I had spent an hour or two tweaking my phone, I was not a happy person. This time I did feel almost positive I had TWRP installed correctly and did not have nearly as much time spent getting things set up like I want them on my phone...It was still scary pressing that reset button and yes button.
If you don't have TWRP (or maybe some other recovery) installed it will factory reset your phone. I just thought I would share this and what happened with me. Do it at your own risk.