[RECOVERY][D855 ONLY][Experienced Users][Tethered] TWRP 2.7.1.3

[RECOVERY][D855 ONLY][Experienced Users][Tethered] TWRP 2.7.1.3 - G3 General

All credits to thecubed, autoprime, shelnutt2, everyone else.
Leak from here:
http://www.androidiani.com/forum/modding-lg-g3/417371-twrp-recovery-d855-only-tethered-avvio-da-fastboot.html
Click to expand...
Click to collapse
Hello everyone, I searched the internet today & stumpled upon this TWRP recovery accessible through adb fastboot. This is a Tethered TWRP bootloader, which means you need to be at a computer to open the recovery, (just like iPhone jailbreaking).
THIS DO ONLY WORK ON THE International D855 LG G3 Phone, DO NOT TRY IT ON OTHER VARIANTS/BRANDS!
YOU HAVE BEEN WARNED.
Confirmed working on D855p variant (Mexico version) by badtzo
However, this is not my work. This TWRP recovery comes from androidiani.com.
The following have been translated by Google:
Exclusive for androidiani.com
With pleasure that I want to share the first exclusive international REAL custom recovery , TWRP for the' appuntto and therefore the best, fully functional in all its features, and most importantly optimized for LG G3 with the latest release.
Thank Dees_Troy (TWRP Creator) for collaboration with myself (wolfgart).
Update: Now DPI Full Size. A full screen and with the 'option for backing up the EFS partition active
The below is a bootable recovery in fastboot mode then necessarily need the pc, at least until we have "liberated" the bootloader also the G3 so as to make it bootable from the phone itself.
Why it is still useful to use the TWRP recovery even being able to launch (for the moment) only from PC (fastboot)?
You can finally get your Nandroid Backup and keep it aside.
You can now restore the Nandroid Backup fact, returning to the state in which you want in seconds.
It finally has the chance to try many roms and more, tools, and Spippola the G3 and as much as you like, make sure that you can finally return to the state of your backup created as and when you like.
It finally has a file manager directly from recovery.
Click to expand...
Click to collapse
Steps before it all start:
All though, I HIGHLY RECOMMEND THAT YOU READ THE FAQ FIRST!
Download the package that contains adb , fastboot, and the work on the TWRP:
https://docs.google.com/uc?authuser=0&id=0B9YFzKYNIAlRS1Ntck1GZ0JCOHc&export=download
- Extract the package and place it on your desktop for convenience.
- Enable USB debugging on G3 and connect it to pc with cable. (Also screen-timer is good to have at 1/5min before it goes off)
- Start (inside the extracted directory) the file - 'cmd' .
First time usage (recommended to do!):
1. We now proceed to backup the original recovery in a way that we know it always will be possible to access, (on our PC). Run the following commands pressing Enter each line:
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img (recovery.img you'll find it in the root of sd card)
2. We now proceed to 'elimination of the recovery system and then get out of the mode adb:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
3. Now reboot into recovery (but in reality it will be now, our fastboot mode on phone):
Code:
adb reboot recovery
4. And now we make the much desired TWRP bootable on a G3, fully functional and operational:
Code:
fastboot boot d855.img
Subsequent usage: (when you already have a backup.)
Code:
adb reboot recovery
fastboot boot d855.img
Voila, you have the original TWRP on board.
This is tested on my own device (D855 with Version F & is rooted)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Best regards & all of luck too you all.
I will not be hold responsible for what happens to your device.
Do this at your own risk.

FAQ:
Q: Why does your first post contain so many QUOTES??
A: If some people should post a reply of the original post, it won't contain everything including pics & steps, which is annoying for other users to see all over again.
Q: Is this Tethered Recovery working on other variants/brands of the LG G3
A: NOOOOOOO! DON'T EVEN TRY!
Q: Will this have impact on future OTA updates ?
A: YES! 2 persons, have been stuck in fastboot mode!! Please reload the original recovery, before doing OTA FLASH!
Q: HEEEELP, stuck in FASTBOOT mode! Credits to @clandes #88
A: Put the back'd up recovery into the folder (or download it from the link below) and write
Also do read #93 credits to @Tectas - if you're still having trouble.
Code:
fastboot boot recovery.img
Q: How do I restore to the original recovery? Thanks to pRo_lama #7
A: You need to have backup and must be in root of sdcard aka internal memory. Then do the following:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Q: Can I boot into the TWRP recovery without a computer, maybe through buttons??
A: No you can't, that's what Tethered means.
Q: adb shell - don't work??
A: Ensure that your screen is on & you have trusted the computer, your trying to access your phone with! Also ensure that you are running the cmd from the folder!
Q: su - don't work??
A: You must have rooted your phone, before flashing this recovery else you can't give SuperSU to adb shell on your phone!
Q: Is it possible to theme TWRP?
A: No, not unless you know how to open up the .img & replace the pictures.
Q: Is it possible to root my after doing a CSE flash of a original rom?
A: adb should also be working in the Tethered TWRP recovery, so that should be possible (waiting for ppl, to confirm).
Q: Can I flash this - xxxxxxxxxx ??
A: This is new to all of us, so we can't answar that. You have to test it for yourself & give feedback afterwards.
Q: Will this have any effect on my battery usage?
A: Nop.
Q: Will I lose root after doing this?
A: Depends on what you are doing in the recovery?
Q: What's not working?
A: You tell me & I will write it here. :good:
Q: Do you have a link to the recovery? I accidently deleted it.
A:
LG G3 - 16GB Version:
Official V10F-GLOBAL-SI (16GB Italy): https://mega.co.nz/#!Yd91ALDA!C-cfGKhVCCi3SOJ6q3o-Lzy1Qe7q89afj98hrtoLY2M
Official V10G (16GB Italy): http://forum.xda-developers.com/showpost.php?p=54496418&postcount=80
LG G3 - 32GB Version
Official V10F (32GB Indian): http://www.4shared.com/file/MOn-Ji8-ba/recovery.html
Click to expand...
Click to collapse

Thanks for posting it here bud:thumbup:
I'll try to install it later on... Hopefully my win 8 allow me too lol
Sent from my LG-D855 using XDA Free mobile app

d855 only

hello00 said:
d855 only
Click to expand...
Click to collapse
I have now edited it with an First & Second attempt to clarify that you don't need to take a backup everytime.

danny_and_2 said:
I have now edited it with an First & Second attempt to clarify that you don't need to take a backup everytime.
Click to expand...
Click to collapse
This isn't official is it? I tried to find our phone on their website and it is not listed

Tested and it's working on my D855.
If you want to restore your original recovery use this commands (you need to have backup and must be in root of sdcard aka internal memory):
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

F4M0U569 said:
This isn't official is it? I tried to find our phone on their website and it is not listed
Click to expand...
Click to collapse
It isn't listed, because our bootloader isn't fully cracked yet. This tethering fix, should however let us do pretty much the same. :good:

pRo_lama said:
Tested and it's working on my D855.
If you want to restore your original recovery use this commands (you need to have backup and must be in root of sdcard aka internal memory):
Click to expand...
Click to collapse
Added to FAQ, thanks pRo_lama for clearing that up! :fingers-crossed: :good:

just to confirm ....we cannot enter this recovery through buttons ? we need to be at a pc with adb working i think

confirmed working on D855
I believe development on the G3 should begin soon

rraaka said:
just to confirm ....we cannot enter this recovery through buttons ? we need to be at a pc with adb working i think
Click to expand...
Click to collapse
As mentioned in the FAQ, yes you are 100% right. We can not access this through buttons YET.
sooti said:
confirmed working on D855
I believe development on the G3 should begin soon
Click to expand...
Click to collapse
Great to hear that you got it working!
Lets hope the devs, will have some more options open now!

danny_and_2 said:
As mentioned in the FAQ, yes you are 100% right. We can not access this through buttons YET.
Great to hear that you got it working!
Lets hope the devs, will have some more options open now!
Click to expand...
Click to collapse
As long as you can flash kernel + system, it should be possible to develop CM roms and so on,
Once the CM team adds the G3 device tree, I promise to bring roms such as 'beanstalk', 'AOSB and others to the G3 (I brought lots of them to the galaxy s2).
Its only a matter of time,
Keep in mind though that it will not be a permanent solution, since the bootloader is still locked, so once LG patches this, you will not be able to flash custom roms again

danny_and_2 said:
This is a Tethered TWRP bootloader, which means you need to be at a computer to open the recovery, (just like iPhone jailbreaking).
Click to expand...
Click to collapse
Works like a charm, thanks.
Since the phone is already hooked to the computer, is there a way to write the backup to the computer without first writing to sdcard ? (I have no space left on sdcard)

sooti said:
As long as you can flash kernel + system, it should be possible to develop CM roms and so on,
Once the CM team adds the G3 device tree, I promise to bring roms such as 'beanstalk', 'AOSB and others to the G3 (I brought lots of them to the galaxy s2).
Its only a matter of time,
Keep in mind though that it will not be a permanent solution, since the bootloader is still locked, so once LG patches this, you will not be able to flash custom roms again
Click to expand...
Click to collapse
Sounds good, I do only have knowledge about how it works for the S4, but it seems it's a bit more hardcore here at LG.
I know it's not a permanent solution, hopefully there's soon a backdoor there will open the locked bootloader. :good:
Yea, lets see what LG's move is next. Good thing we aren't forced to update, so we can just cancel the upcomming updates/OTA, until we are sure the tethered recovery works at the next version :victory:
MrTip said:
Works like a charm, thanks.
Since the phone is already hooked to the computer, is there a way to write the backup to the computer without first writing to sdcard ? (I have no space left on sdcard)
Click to expand...
Click to collapse
Unfortunately, I am not that sharp to linux dd commands, maybe @pRo_lama can help?

danny_and_2 said:
Unfortunately, I am not that sharp to linux dd commands, maybe @pRo_lama can help?
Click to expand...
Click to collapse
My wording lacks precision, english is not my first language.
I meant a nandroid backup. Performing twrp backup using usb cable to write files on the computer.

MrTip said:
I meant a nandroid backup. Performing twrp backup using usb cable to write files on the computer.
Click to expand...
Click to collapse
I'm not sure if this is possible in TWRP.

MrTip said:
My wording lacks precision, english is not my first language.
I meant a nandroid backup. Performing twrp backup using usb cable to write files on the computer.
Click to expand...
Click to collapse
pRo_lama said:
I'm not sure if is this possible in TWRP.
Click to expand...
Click to collapse
Seems like it is, however I would still perfer to do it directly to the sdcard & then transfer. Heres the link:
http://forum.xda-developers.com/showthread.php?t=2611099

danny_and_2 said:
Seems like it is, however I would still perfer to do it directly to the sdcard & then transfer. Heres the link:
http://forum.xda-developers.com/showthread.php?t=2611099
Click to expand...
Click to collapse
I meant directly in TWRP. I know that can be done with commands in ADB.

pRo_lama said:
I meant directly in TWRP. I know that can be done with commands in ADB.
Click to expand...
Click to collapse
Good question. It don't seem like it when I search on the internet.
A upcomming queston you might can help me answar:
Is it possible in this TWRP recovery to run the adb commands? If ppl forget to restore the original recovery & perform a CSE flash to a new version.
Can they run the adb commands in TWRP to ex. PurpleDrake Lite to acquire root?
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot

Related

[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)

GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
Download Android SDK release 13 click the file name android-sdk_r13-windows.zip (34 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Note: from SDK release 14 onward, Google removed the fastboot command, you'll have to maker the fastboot command yourself if you want to use the latest version of the SDK
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
droidmage said:
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!

NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
To simplify things with the Command Line, it's best to copy and paste the contents inside ..\android-sdk-windows\platform-tools to ..\android-sdk-windows\tools
that way you'll have all the necessary files in the same location to prevent errors
MIRROR:
since CW website seems to be down, here's a mirror for the Image file.
download the 7zip attachment, unzip and flash recovery.img (recovery-clockwork-5.0.2.0-crespo.img)

Good guide but i have a question,
didn't you miss the step about renaming the install-recovery.sh script
that reflash recovery if crc is wrong?

Thank you sir, I was hoping for a good step-by-step guide for us first-timers.

Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything

Cubfan185 said:
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
Click to expand...
Click to collapse
thank you, that was the idea.
many of the GUIDEs we have here are usually aimed at people that already knows what to do, which usually leaves out all the 1st time owners of the phone.

it's fairly simple, the instructions are as simple as this
http://forum.xda-developers.com/showthread.php?t=884097
and you can choose any stock ROM to flash back
sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse

Alright, just did it successfully. I had a few problems when installing the SDK and using fastboot. The recovery image must have been corrupt a few times for me. I had to take the battery out because it was stuck at the Google screen. My heart skipped a beat at that point, I didn't want to brick anything. Also had to put a required .dll file in the tools directory and the drivers were giving me problems, but got it all figured out. Thanks again.
Edit: Any reason why root required apps are saying they don't have root access?

Will Google definatly release a full restore firmware of the current ROMS, something simular to an HTC RUU, or is it just something we're hoping they'll do?

silly question... which fastboot binary did you use? the one from the htc developer site?

onicrom said:
silly question... which fastboot binary did you use? the one from the htc developer site?
Click to expand...
Click to collapse
it is included in the Android SDK 2.3 ... read the step by step guide again

Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.

AllGamer said:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
Click to expand...
Click to collapse
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again

sinatosk said:
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again
Click to expand...
Click to collapse
yes, i actually like it this way, it keeps your original safe

Titanium Backup and few other apps are why i ROOT the phone as well.
after you fastboot over the CW recovery image and rooted, were you able to install Super User?
there is another trick, you can Install Super User first from Market
then repeat the steps to fastboot the clock work recovery image and get root access
jvblack82 said:
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.
Click to expand...
Click to collapse

Followed the guide to a T as well and did not get root access. But unlocking the bootloader, installing the SDK and learning about fastboot and such was very helpful. Using that, I used the automated batch file posted in this topic http://forum.xda-developers.com/showthread.php?t=882333 and it worked.

What to do if my Device Manager showed Android 1.0?

ykphuah said:
What to do if my Device Manager showed Android 1.0?
Click to expand...
Click to collapse
you select the correct driver to install the ABD support or Bootloader support, depending in which screen you have the phone on
just review the step by step guide, it is mentioned there

sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.

knytphal said:
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
Click to expand...
Click to collapse
... yeah I know. Made a post earlier today about it in this thread...

How to root LG D802 with 220H firmware ?

Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !

Cst79 said:
Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !
Click to expand...
Click to collapse
Towelroot

azher98 said:
Towelroot
Click to expand...
Click to collapse
Doesn't work, it sais "phone is not supported". I understand that towelroot exploits a Linux kernel loophole that was patched around June 3.

Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906

6ril1 said:
Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906
Click to expand...
Click to collapse
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).

Cst79 said:
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).
Click to expand...
Click to collapse
It's very simple:
1) download ioroot:
http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip
2) extract datroot.zip from the archive just downloaded (from bts folder)
3) on the G2 enable dev option (Settings - About Phone. Then go to the bottom and you should see Build Number. This needs to be pressed a total of seven times. You should get a message at the fourth press. On the seventh, you'll get another message saying that Developer Options are unlocked.)
4) enable usb debug on the phone (Development Settings Enable USB Debugging)
5) plug the phone in usb with the pc and accept yhe RSA Fingerprint message.
6) reboot your phone in recovery with adb cmd (tape cmd: adb reboot recovery)
7) choose 'apply update from adb' in the phone recovery menu (navigate with vol down and valid with power)
8) in the pc tape cmd: adb sideload c:\datroot.zip
9) reboot et enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

6ril1 said:
It's very simple:
Click to expand...
Click to collapse
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !

Cst79 said:
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !
Click to expand...
Click to collapse
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.

6ril1 said:
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.
Click to expand...
Click to collapse
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !

Cst79 said:
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !
Click to expand...
Click to collapse
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.

6ril1 said:
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.
Click to expand...
Click to collapse
Hello,
No, my questions are not generic, I want to find out:
- How do I install CyanogenMod 12 after I root the phone.
- What are the steps to revert to 100% stock after I root the phone and install CM12; Can I just use the LG flash tool and flash the kdz with no complains from the LG software if I have CM12 installed ?
Thanks.

Do you loss data with this metod?
Thanks

One M9 unlocking rooting guide+Return To Stock

**** if you are looking for rooting your one m9 with android 6.0 , follow this simple guide of mine (http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354 ) ****
HELLO EVERYONE WITH A ONE M9
heres what you've got to do to unlock the monster in your device
1)unlock the bootloader
2)use a custom, more powerful recovery
3)root your phone
4)use a custom rom
you must have working adb and fastboot and htc drivers, if you dont know how to get these files, pls leave a reply.
Now We Will Learn 1,2,3,4
STEP 1:
NOTE:- YOU WILL LOSE YOUR DATA(Unless you have a dev edition htc onem9 , if u have one , skip step 1)
follow these steps:-
A]create a htc dev account here-https://www.htcdev.com/register/
B]go here , make sure ur logged in on htc dev website! -http://www.htcdev.com/bootloader/unlock-instructions/page-2
C] dont download anything ! from htc dev website.
D]connect ur phone to pc and enter download mode :- adb reboot download
E] type the following in cmd< fastboot oem get_identifier_token > look at the pictures on the web page, link in step B, as to how to mark and copy your token identifier code , then paste it in the space provided bellow.
you will get an email from htc dev with a file called Unlock_Code.bin
download it and in cmd type < fastboot flash unlocktoken Unlock_Code.bin>
now, use ur volume buttons to select unlock bootloader and press power button.
FACTORY RESET !
NOTE:- if you have problems following these steps , check out this bootloader unlocking video. im sure it will help you.
https://www.youtube.com/watch?v=Stl4A-ue5IE&app=desktop
DONE! bootloader unlocked
STEP 2:
Note: HTC one m9 is different from previous generation htc ones as it has a block based ota update system. in brief, any modification done to the system will result in an ota update faliure. keeping that in mind, follow my steps as it is
A] download the recovery.img here we are using a beta version of twrp.
http://forum.xda-developers.com/devdb/project/dl/?id=11987
after downloading, rename this file to twrp.img
Also download su bineries+ supersu (required for rooting later)
http://download.chainfire.eu/735/SuperSU/BETA-SuperSU-v2.48.zip?retrieve_file=1
put this file on ur sd card now!
B]go to download mode
type this adb command: adb reboot download
C]go to the directory where you have downloaded the recovery image
type in this fastboot command as soon as the phone is in download mode: fastboot flash recovery twrp.img
DONE!
STEP 3:
A]enter bootloader
B]enter recovery
C] TAKE A BACKUP. A COMPLETE BACKUP . MOST IMPORTANTLY <<<<SYSTEM>>>> DO NOT SKIP THIS STEP. THIS IS VVVVVVV IMP. IF U WANT TO TAKE AN OTA UPDATE EVER WITHOUT RUNNING ANY SORT OF RUU.
D]once thats done, go to advance->terminal and type this as it is:-
mount -t ext4 /dev/block/bootdevice/by-name/system /system
once this is done, go to mount and make sure system is selected.
now install the zip file i had asked you to download in the previous step.
DONE! You are rooted!
if You have forgotten to take a system backup, dont worry, you can find it here, you can flash it at the time of an ota,
https://www.androidfilehost.com/?fid=95916177934550813
STEP 4:
A]For a custom rom , download the customrom.zip file
browse the zip file and extract the file called boot.img
now , put the zip file on ur phone storage or sd-card.
boot to recovery and install the zip file. make sure to wipe cache,dalvik cache, system, and-secure before installing for a clean install, leave data as it is .
IF YOU ARE S-OFF, SKIP THIS STEP:-
B] reboot to download mode and type this fastboot command from the directory you unzipped your rom or extraced the boot.img:-
< fastboot flash boot boot.img>
reboot and enjoy your custom rom !
EXTRA SECTION (VVVVVV IMP)(TO TAKE AN OTA update)
if ever you get an ota update heres what you have to do . do not download it now. first follow these steps.
A)download stock recovery from here:-
https://www.androidfilehost.com/?fid=95916177934554373
rename it as recovery.img
B) download system.img from here ( only if you have not taken the system backup from twrp when in r/o state)
https://www.androidfilehost.com/?fid=95916177934550813
take only the system.emmc.win file from the twrp backup of the original system i had asked you to make before rooting your phone. if you dont have it? you will have to hunt for an ruu, well dont ask me how to do that .
put the system file and recovery.img and put the same folder. run cmd from that folder (right shift+right mouse click ->run command window here)
and type in
adb reboot download
fastboot flash system system.emmc.win / fastboot flash system system.img (depends if you are using a twrp backup or the system image you have downloaded from above)
fastboot flash recovery recovery.img
fastboot reboot
thats it. now download the ota update and once the installation is done, you will need to re-root. follow from step 2 again.
if you get a boot-loop, return to download mode, flash the twrp beta recovery and wipe cache and dalvik-cache. and then reboot , then go back to download mode and re-flash stock recovery.
hope ive helped you

sishirbaid said:
HELLO EVERYONE WITH A ONE M9
heres what you've got to do to unlock the monster in your device
Click to expand...
Click to collapse
Nice job ..thanks

Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now

Duncan1982 said:
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Click to expand...
Click to collapse
If you need help I can start a IRC chat with you. Maybe I can try to help. Let me know.

aooga said:
If you need help I can start a IRC chat with you. Maybe I can try to help. Let me know.
Click to expand...
Click to collapse
That is very much appreciated, I have gone through everything, all SDK stuff installed as per HTC dev but the command is like if the adb and fadtboot is not there on my com, but I have installed.
I will wait as my M8 was so so so easy to unlock, M9 is just a headache.
My computer is off for tonight, I honestly have a sore head with trying to figure it out.
Again your reply and offer of help is appreciated.
Thanks Again, but for tonight "I give up" lol

Haha headache cleared so attempted again from scratch now HTC dev is not allowing me in, reset password and nope saying my login details are incorrect which is Bs as its the one they sent.
I really do now believe my M9 cannot be unlocked lol

That's KARMA.. nothing can be done - everything depends thru which hole you penetrated into this world in the first place..
P.S. Try different web browser though..

jauhien said:
That's KARMA.. nothing can be done - everything depends thru which hole you penetrated into this world in the first place..
P.S. Try different web browser though..
Click to expand...
Click to collapse
Haha Karma indeed, no I'm just going to say F it and be happy with S-On & locked, I managed the all my 12 devices without issue, rooting and unlocking for some, bar the Z2 which was the same headache as this M9 of mine lol
Karma has spoken and I am listening lol

Hello. Great guide. My question is about step 3, system backup for future OTA. I rooted my phone a few days ago, when no all things were clear. So, i made before flashing custom ROM only system backup not a full backup. I have system.emmc.win file saved. can i use it or a full backup is mandatory? thank you.

I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )

Security555 said:
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Click to expand...
Click to collapse
Use TWRP 2.8.6.4

jauhien said:
Use TWRP 2.8.6.4
Click to expand...
Click to collapse
I do. TWRP 2.8.6.4, stock .15 rom

Use SuperSU v2.48 zip

jauhien said:
Use SuperSU v2.48 zip
Click to expand...
Click to collapse
Thanks! Installed 2.48 instead of 2.46 and everything is fine, I have root! Once again, thanks a lot! )

Duncan1982 said:
That is very much appreciated, I have gone through everything, all SDK stuff installed as per HTC dev but the command is like if the adb and fadtboot is not there on my com, but I have installed.
I will wait as my M8 was so so so easy to unlock, M9 is just a headache.
My computer is off for tonight, I honestly have a sore head with trying to figure it out.
Again your reply and offer of help is appreciated.
Thanks Again, but for tonight "I give up" lol
Click to expand...
Click to collapse
don't use google sdk for adb and fastboot! i would suggest this installation. Remember, install it system-wide.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Duncan1982 said:
Haha Karma indeed, no I'm just going to say F it and be happy with S-On & locked, I managed the all my 12 devices without issue, rooting and unlocking for some, bar the Z2 which was the same headache as this M9 of mine lol
Karma has spoken and I am listening lol
Click to expand...
Click to collapse
use chrome , access htcdev , select device not listed and follow the steps , if u want me to make the steps easier i shall post a reply, let me know
Duncan1982 said:
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Click to expand...
Click to collapse
Remember, install it system-wide.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
also , install htc sync manager,for htc drivers. may be the drivers are outdated , m9 being a new device.mine worked fine with the newest htc sync manager.
Security555 said:
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Click to expand...
Click to collapse
ill post the link to the newer supersu.

cclhuzhou said:
The other just reboots into boot loader with it still locked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
i dint get ur problem ?

Haha headache cleared so attempted again from scratch now HTC dev is not allowing me in, reset password and nope saying my login details are incorrect which is Bs as its the one they sent.
I really do now believe my M9 cannot be unlocked lol
Click to expand...
Click to collapse
create a new account ! simple
note- htc account and htcdev account are different

ioni2ioni said:
Hello. Great guide. My question is about step 3, system backup for future OTA. I rooted my phone a few days ago, when no all things were clear. So, i made before flashing custom ROM only system backup not a full backup. I have system.emmc.win file saved. can i use it or a full backup is mandatory? thank you.
Click to expand...
Click to collapse
Did u take a system backup using twrp beta? if so , ur safe else if u used twrp (not beta) then you have taken a backup of system with the changed checksum. you are in urgent need of a stock system backup. let me know, ill host it if u need
and ya, only system.emmc.win is good enough if backuped via twrp beta .let me know as to what exactly you did.

Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------
Duncan1982 said:
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
Click to expand...
Click to collapse
I want to add the creator of this thread is very helpful though and he offered to guide me through, I was stubborn and knew I could sus it out.

Duncan1982 said:
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------
I want to add the creator of this thread is very helpful though and he offered to guide me through, I was stubborn and knew I could sus it out.
Click to expand...
Click to collapse
Thankyou for that ,I appreciated. It just another thing, could you post the link to the YouTube video you followed ? Thanks

TWRP for Z3 compact ; Unlocked Bootloader - GUIDE

Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!

Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??

dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality

Clarification
Should I have to flash DRM Fix every time I flash TWRP?

andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to

i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.

epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?

panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks

epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!

To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
 @epiii_nephrine

panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:

epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.

After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.

smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again

I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.

panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.

ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!

panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.

ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions

Bricked Amazon Fire Stick 4K - Clarification Needed

Hi Guys,
So, I spend a few hours reading many posts regarding recovery of the Fire Stick 4K.
I'm in the infinite boot stage and trying to reset to the factory settings after Google Services fu*** up everything.
What I tried:
- adb connection from MacBook
- keyboard recovery
ADB Method Issues
When I connect via adb I get Device Unauthorized and don't really know what to do next. I tried to run fastboot but it stuck on Waiting for any device...
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Keyboard Method Issues
I tried the combination of Alt+I+PrintScr many times. None of the sources specifies if I should hold the buttons or keep pressing them on/off during the boot (eg 15x) or at which point I should start or finish pressing. So success here either.
I also tried to use remote but every source shows different buttons to press. Power + Volume Up, Middle Button + Arrow RIght etc.
What should I try next, I'm on OSX?

spyderdsn said:
What should I try next
Click to expand...
Click to collapse
Here is the unbrick thread.

Ok, so I need Windows PC to start with...any other options?

spyderdsn said:
Ok, so I need Windows PC to start with...any other options?
Click to expand...
Click to collapse
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck

brick00444 said:
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
Click to expand...
Click to collapse
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?

spyderdsn said:
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
Click to expand...
Click to collapse
I'm almost sure there is a factory rom posted here somewhere. Just use that instead of the rbox rom.

A good reminder to everyone, don't try anything with your device with debugging disabled.

spyderdsn said:
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
Click to expand...
Click to collapse
It isn't a cfw, but the stock recovery gets replaced during the unlock. Therefore the stock update app in fireOS won't work as expected, you need to use TWRP recovery and do all updates manually.

brick00444 said:
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
Click to expand...
Click to collapse
So the steps in other post are not exactly clear as I'm using the iso
HTML:
https://github.com/amonet-kamakiri/fireiso/releases
.
I run the ISO from USB stick on my MacBook and what do I do next I have two opinions Default & Load to Memory...do I have to have firesick connected at this point...with the foil in it? Is there any step by step for the ISO setup? Can I use MacBook to rin the ISO at all?
Thanks

spyderdsn said:
So the steps in other post are not exactly clear as I'm using the iso
HTML:
https://github.com/amonet-kamakiri/fireiso/releases
.
I run the ISO from USB stick on my MacBook and what do I do next I have two opinions Default & Load to Memory...do I have to have firesick connected at this point...with the foil in it? Is there any step by step for the ISO setup? Can I use MacBook to rin the ISO at all?
Thanks
Click to expand...
Click to collapse
I don't own a macbook but I would think you can because you have to boot to the usb stick and I just use the default option. Wait until you see the desktop. Then go to the internet and look up the unlock thread. You may need to have an ethernet cord plugged into your mac to access the internet (my wifi doesn't work in the iso).
1. Download kamakiri-mantis-v1.2.zip from the link in the original thread.
2. Extract the kamakiri-mantis-v1.2.zip somewhere you will remember. I extract to desktop.
3. Open the kamakiri-mantis-v1.2 folder and then open the kamakiri folder and right click inside that folder and choose open terminal.
4. enter this command in terminal " ./bootrom-step.sh " minus the quotes and click enter. It will say something to the effect of "waiting for device".
5. Short the correct point to the tin casing. It looks like you are shorting it correctly by your pic.
6. Connect the stick to your computer (while keeping it shorted).
7. The script should tell you to release the short and hit enter,. Just pull the tinfoil off the stick . Then click enter (after removing short).
It will take awhile to finish so if it looks like it stalled out give it time.
8. When it is finished enter the command : " ./fastboot-step.sh " and click enter.
9. It will now reboot into TWRP.
10. You can now install the rom. If you don't know how you can follow this guide "https://forum.xda-developers.com/fire-tv/orig-development/newbie-guide-how-to-unlock-bootloader-t4015273" .
Hopefully this helps you. Anyone can add to it or correct it if I missed or forgot something.

Thanks guys for the help. I managed to unbrick my Firestick 4K. and after brick00444 steps I followed this steps:
HTML:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Worth mentioning. Since I used Mac I downloaded https://unetbootin.github.io/ to do the fat32 bootable stick. The stick runs to the menu but is not able to load Linux. I had to find Windows 10 machine and use https://rufus.ie/ to install the iso and everything worked. All other steps I followed brick00444
My Firestick did not had enough space to push the room zip above so I used Adblink http://www.jocala.com/ to remove some apps.
One more question.
I decided not to block amazon update services via adb. At the moment I’m on Fire OS 6.2.7.1. and fire stick is downloading some updates. I only wanted to unbrick the device not root. Can I apply the update on the top of mantis? Would this work. I’m happy to have stock. At the moment download kind of stuck on downloading system components 70%.
Thanks for your help.

spyderdsn said:
One more question.
I decided not to block amazon update services via adb. At the moment I’m on Fire OS 6.2.7.1. and fire stick is downloading some updates. I only wanted to unbrick the device not root. Can I apply the update on the top of mantis? Would this work. I’m happy to have stock. At the moment download kind of stuck on downloading system components 70%.
Thanks for your help.
Click to expand...
Click to collapse
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.

Sus_i said:
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Click to expand...
Click to collapse
The sick has been updated now. The update took whole night and it has downloaded 1GB of stuff as my storage was very low at the time. Now I have the latest update and everything seems to work fine.

Sus_i said:
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Click to expand...
Click to collapse
Ok I noticed now when I power off the device and run again I get the recovery mode and reboot after that everything is fine until I power off the stick. What should I do to prevent this?

spyderdsn said:
Ok I noticed now when I power off the device and run again I get the recovery mode and reboot after that everything is fine until I power off the stick. What should I do to prevent this?
Click to expand...
Click to collapse
It's like I said, I guess there is a (partial or full) fireOS update pending
The OTA-update app downloads the update to /cache and place also some recovery commands for the stock recovery.
This is why your stick boots into recovery.
The stick will do that again and again and again, until the update is installed (won't work without the stock recovery).
Take a look on /cache with TWRP. There should be the latest update for your stick (it's a .bin file). In case it is a full update (~600MB in size), rename that file to zip and flash/install it with TWRP. Make sure you don't flash one of the smaller 'partial' updates (If there is a smaller update bin file, delete it... then the stick will download a full bin). After the install, wipe cache, reboot and your stick should be on the latest OS version. You have to do this erverytime you see that the stick boots into recovery
Another option, disable updates and keep the OS version on the stick (for now).
Code:
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
But for this option you need magisk installed...

Sus_i said:
It's like I said, I guess there is a (partial or full) fireOS update pending
The OTA-update app downloads the update to /cache and place also some recovery commands for the stock recovery.
This is why your stick boots into recovery.
The stick will do that again and again and again, until the update is installed (won't work without the stock recovery).
Take a look on /cache with TWRP. There should be the latest update for your stick (it's a .bin file). In case it is a full update (~600MB in size), rename that file to zip and flash/install it with TWRP. Make sure you don't flash one of the smaller 'partial' updates (If there is a smaller update bin file, delete it... then the stick will download a full bin). After the install, wipe cache, reboot and your stick should be on the latest OS version. You have to do this erverytime you see that the stick boots into recovery
Another option, disable updates and keep the OS version on the stick (for now).
Code:
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
But for this option you need magisk installed...
Click to expand...
Click to collapse
Actually you don't need Magisk to disable packages. Input disable-user after putting adb shell and the package can disable without root. Only works on Fire OS 6 and above

theflashfromthecw said:
Actually you don't need Magisk to disable packages. Input disable-user after putting adb shell and the package can disable without root. Only works on Fire OS 6 and above
Click to expand...
Click to collapse
Ok so if I understood this correctly. If I don’t bother with the updates for 1-2years. All I do is to delete the update files from the temp folder and prevent the updates by running this commands and I’m good to go.

spyderdsn said:
Ok so if I understood this correctly. If I don’t bother with the updates for 1-2years. All I do is to delete the update files from the temp folder and prevent the updates by running this commands and I’m good to go.
Click to expand...
Click to collapse
Yes and its all preferred to rename otacerts.zip to otacerts.zip.bak in TWRP by mounting the system as read write and hovering over to system/etc/security and you'll see otacerts.zip. The otacerts is certifying the update that's being rolled out properly and since you renamed it to .bak, you can no longer have it applying the update. It still will update but not apply it if you do end up keeping devicesoftwareota. Only disable the override and leave the rest alone for factory reset reasons because it needs the devicesoftwareota enabled to go through the wizard

theflashfromthecw said:
Yes and its all preferred to rename otacerts.zip to otacerts.zip.bak in TWRP by mounting the system as read write and hovering over to system/etc/security and you'll see otacerts.zip.
Click to expand...
Click to collapse
Personally, as soon as system modifications come to mind, I preffer a magisk install, just to avoid verity issues.
but renaming just one zip on system won't trigger dm-verity I guess!?

Sus_i said:
Personally, as soon as system modifications come to mind, I preffer a magisk install, just to avoid verity issues.
but renaming just one zip on system won't trigger dm-verity I guess!?
Click to expand...
Click to collapse
It won't. Fire TV devices don't have dm verify at all and it's safe to rename the zip however you want. Because of this, Amazon doesn't have oem unlock and a setting to enable it, there's no official way for the device to check for dm verify and because the bootloader unlock isn't modified to have its own recovery. I have an LG unlocked device that supports oem and after I unlock it, it tells me to relock the bootloader since the manufacturer allowed my device to be oem unlocked.

Database Users

welcome