Develop Bugs

[Update-Only] nfx-update-kindle-6.2.2 - 1/18/2012

UPDATE ONLY from 6.2.1 to 6.2.2
Just for clarification this is not a complete rom this is only an Update
AND THIS IS ONLY IF YOU HAVE 6.2.1, not CM
Ok I have packaged up the 6.2.2 update with only the files changed or modified removed and added from 6.2.1
Included in this is:
unsecure boot image
busybox
su binary
and su apk
This is for anyone with root and TWRP already installed and still on 6.2.1
this will not format system it will just update the need files.
So all added apps will remain and all data will be intact.
Install and wipe dalvik and cache, then reboot
Download Update 6.2.2
Files updated, added or removed
Code:
sed
boot.img
cert_swap.sed
build.prop
amazonmp3-unsigned.apk
AmazonVenezia.apk
ATVAndroidClient.apk
Cloud9-unsigned.apk - removed
Cloud9-release-unsigned.apk - added
Cloud9SystemBrowserProvider-unsigned.apk
com.amazon.dcp.apk
CSApp-unsigned.apk
Email.apk
Facebook.apk
KindleForOtter.apk
Launcher.apk
MarketIntentProxy.apk
MyAccount-unsigned.apk
OOBE-unsigned.apk
OTASilentInstall.apk
OtterAppManager.apk
OtterTutorial.apk
Superuser.apk
SystemUI.apk
Windowshop.apk
applypatch_static
check_prereq
debuggerd
dhcpcd
dnsmasq
fsck_msdos
hostap
idme
iptables
linker
logwrapper
memmgr_test
ping
PrintBootTime
racoon
recovery
run-as
sdcard
sh
SkLibTiJpeg_Test
su
tiap_cu
tiap_loader
updater
wlan_cu
wlan_loader
wpa_supplicant
gateMPApp.out
nameServerApp.out
Kindle_Users_Guide.prc
otacerts.zip
framework-res.apk
am.jar
android.policy.jar
android.test.runner.jar
bmgr.jar
bouncycastle.jar
com.android.location.provider.jar
core-junit.jar
core.jar
ext.jar
framework.jar
idme.jar
ime.jar
input.jar
javax.obex.jar
monkey.jar
pm.jar
services.jar
sqlite-jdbc.jar
svc.jar
libaudiomodemgeneric.so
libc.so
libskia.so
libwebcore.so
busybox
Hope this helps, Enjoy!
NOOB Guide posted by
rorogio said:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: use only if you have KF version 6.2.1 already rooted, or you may brick your KF!
These are the steps I have done to use this update. They worked 100% for me, BUT I am not responsible if you make mistakes on the road or brick your KF.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1. Connect KF to PC
2.1 Unzip Kindle_Fire_Utility_v0.9.2 (find it with Google)
(- If you haven't installed the ADB drivers yet, in Kindle Fire Utility folder find and start "install_drivers.bat"
- If you haven't rooted yet, in Kindle Fire Utility folder find and start "run.bat", choose option "3" (install permanent rot with superuser) and do all the steps to root KF
- Close "run.bat" window)
2.2 In Kindle Fire Utility folder find and start "run.bat"
3. In the new opened window choose option "5" (to install TWRP)
4. Wait for TWRP to be downloaded, and wait all the other steps to be accomplished by the script to install it
5. Restart KF (still connected to PC)
6. Copy nfx-update-kindle-6.2.2.zip on the KF
7. Disconnect KF from PC
8. Reboot your device into TWRP by shutting down the tablet, then pressing the power button when you see a yellow triangle with a fire icon in the center. Press power button until light turn orange. TWRP 2.0 recovery will be loaded then.
9. At this point it’s a good idea to create a backup of your system using TWRP 2.0's backup option. You can then restore later if you need to. (You need about 1.2 GB on "sdcard" folder to be free for the backup)
10. Wipe [dalvik-cache] and [cache]:
Select Cache then Wipe cache.
Select Dalvik-Cache then Wipe dalvik-cache.
11. Go back to Home.
Select Install.
Navigate and select your nfx-update-kindle-6.2.2.zip.
Select "Flash" button after that.
After installed, select Reboot System.
12. After some 5-12min you should be running 6.2.2 updated from 6.2.1.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: use only if you have KF version 6.2.1 already rooted, or you may brick your KF!
These are the steps I have done to use this update. They worked 100% for me, BUT I am not responsible if you make mistakes on the road or brick your KF.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse

Can somebody tell a "noob" how i have to install this update?
I have root and TWRP installed allready on KF 6.2.1.
Thanks a lot

LilaLurch said:
Can somebody tell a "noob" how i have to install this update?
I have root and TWRP installed allready on KF 6.2.1.
Thanks a lot
Click to expand...
Click to collapse
copy to sdcard and install with twrp - wipe dalvik/cache - reboot
give it some time at first start
works like a charme !

Will updating to this stop the OTA update from installing?
Sent from my SGH-T989 using xda premium

This works like a charm, thanks!

So cool. Thanks. Just flashed this and my kindle is updated to 6.2.2 with root and without having to do any app restoration work.

Yeah this worked like a charm with everything working so far
Sent from my Kindle Fire using xda premium

Worked for me, I put IntersectRaven's kernel in the zip together with my modified build.prop.

is this the 6.2.2 firmware rooted, right?

Yes the only difference is this just updates what needs to be updated to comply with 6.2.2. Instead of formatting/ installing the entire system structure.
Thus eliminating the need to have to install all your apps and settings to what they where previously.

Worked great thanks.
Sent from my Kindle Fire using Tapatalk

Ummm since it didn't really say in your post. Should this only be used on stock root? I just tried it on root running CM7, and it has now been sitting at the kindle fire logo for a while. Not sure what that is about... might want to be a little more clear and update the OP if users running custom roms should not update this.
Or maybe mine is semi bricked... I will check in a bit. It has been sitting at the kindle fire logo for about 10 minutes now. Will give it another 10 minutes, since you didn't say how long it should take but I read in your other thread about 6.2.1 where it should take about 5 min.
I will update post with result... so far not looking good.

Works great! thanks!

Hmmm, I can still get to twrp, checked bootmode and still on normal but always just sits at the kindle fire logo after firefirefire... Not sure why it is even displaying the kindle fire logo.
Going to attempt to install a restore.
Ok restored a CM7 backup so assuming that got rid of the 6.2.2 if it even installed...

bowenac said:
Hmmm, I can still get to twrp, checked bootmode and still on normal but always just sits at the kindle fire logo after firefirefire... Not sure why it is even displaying the kindle fire logo.
Going to attempt to install a restore.
Ok restored a CM7 backup so assuming that got rid of the 6.2.2 if it even installed...
Click to expand...
Click to collapse
I believe this requires 6.2.1 to work, as it doesn't have the full /system partition.
http://forum.xda-developers.com/showthread.php?t=1451747 This update has the full /system partition, use that if you want to switch back to a pre-rooted 6.2.2 stock rom.

I am still on 6.2.0, can I use this to update? Thanks!
KS

Works !!! Thanks.
But I think there's something missing on the script, it is when setting the permission for su, it should be 06755 not 6755 ...

To anyone that has installed this - does there auto-rotate work for them
Sent from my Kindle Fire using xda premium
Edit > fixed

Keyser.Soze said:
I am still on 6.2.0, can I use this to update? Thanks!
KS
Click to expand...
Click to collapse
No you would need to be on 6.2.1 first, then update with this. I have a update for 6.2 to 6.21 also found here. use that first.
GT5830 said:
Works !!! Thanks.
But I think there's something missing on the script, it is when setting the permission for su, it should be 06755 not 6755 ...
Click to expand...
Click to collapse
I will take a look at this, thanks for the info
trapdogg said:
To anyone that has installed this - does there auto-rotate work for them
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Well my wife has been using it all day and I asked her if she has seen this issue, she said she has not had a problem with rotation at all.
Try wiping dalvik and cache again and see if this corrects the issue.

bowenac said:
Hmmm, I can still get to twrp, checked bootmode and still on normal but always just sits at the kindle fire logo after firefirefire... Not sure why it is even displaying the kindle fire logo.
Going to attempt to install a restore.
Ok restored a CM7 backup so assuming that got rid of the 6.2.2 if it even installed...
Click to expand...
Click to collapse
The file he posted is only an update from 6.2.1 to 6.2.2.

[Q] Odd Root Access Results

I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?

dferrey said:
I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?
Click to expand...
Click to collapse
I have seen this happen before that you can retain some permissions with certain apps but not really remain rooted its a 50/50 shot its odd but not totally uncommon results. Generally it has something to do with apps that had su permissions prior to the update adding new su permissions don't usually occur after

I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.

Sometimes it won't push the files if they already exsist

I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.

dferrey said:
I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.
Click to expand...
Click to collapse
No its always worked like a charm for me maybe go to the market and install su from there to see if that doesn't change its strange though that prime is still detecting it. This method only works on rooted stock from what I have seen. Each time delete backup when you restore root. You can also give a shot at fixing permissions. I believe that ota rootkeeper ask for permissions to maybe at some point it was denied and it stuck.uninstall ota and reinstall hope you get er fixed

dferrey said:
I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.
Click to expand...
Click to collapse
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
Note: I have never been a superuser on this kindle before, this is my first attempt at rooting - but the 2nd try at rooting is throwing the above error. I can see the file renamed as check_rooted.bak in the dir but cant rename with ES_FileExplorer utility as I dont have write permissions
TIA

harbinger13 said:
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
TIA
Click to expand...
Click to collapse
Download root checker from the market its free if you like make sure you gift the developer a buck
---------- Post added at 02:51 AM ---------- Previous post was at 02:48 AM ----------
When I used kfu the last time it took 2 times to stick don't try much until you know its rooted and you have twrp installed and fff boot loader and have made a backup you can restore if something goes gunny.
---------- Post added at 03:02 AM ---------- Previous post was at 02:51 AM ----------
If you have done everything right it should reboot a couple of times the last thing you will see is twrp screen with a big reboot button click reboot and your done you will then see the fff splash screen of the boot loader it should eventually boot into the os
---------- Post added at 03:10 AM ---------- Previous post was at 03:02 AM ----------
The same rules apply for 6.3.1 watch nat3mil do it http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US

[Q] Need some help. Erased my phone clean.

Let me make this short for you guys.
I was running carbon rom then decided to try CM 10.1 only because I am a romholic. CM was giving me small quirks so I tried to restore my carbon rom but for some odd reason it wouldnt go pass the samsung logo after it restored successfully. After trying to restore a few times over and over it just decided it was now going to fail. So I tried to go back to CM but now that also failed. So now I was trying to mount usb storage through TWRP but for some odd reason there's no way to do this. After trying to figure out wth was going on I finally made the biggest mistake of completely erasing my internal SD.
So now I am basically in TWRP 2.4.4.0 with no way to access usb storage and not knowing what I should do next.
Please help your fellow romholic

you'll probably have to boot into download mode and use odin to get back to stock and start over.

^^^^^^^^^ That's what you're going to have to do.
There is a way to do ADB sideload through TWRP but you have to edit some files and the Odin method is a lot easier in my opinion. If you want to use ADB Sideload follow my instructions on this thread: http://forum.xda-developers.com/showpost.php?p=39849970&postcount=10. That shows you how to get ADB to recognize your phone in Recovery mode and then the adb sideload command will work.

Odin keep failing. It look like everything is going good then it will get to "get PIT for mapping" stay there for about 7 minutes then fail. I cant believe this:crying:

I would suggest you try my method with ADB sideload, do you know how to use ADB?

Im not familiar with ADB. Any help would be much appreciated.
I got to finding those two lines,
USB\VID_18D1&PID_D001&MI_01
USB\VID_18D1&PID_D001&REV_0228&MI_01
then I got lost.
It says I have to paste those two lines under
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
but I am a little lost there.

Here is the guide for setting up ADB: http://forum.xda-developers.com/showthread.php?p=9936674
If you already have done that, then you should navigate to the directory I listed which is where the android_winusb.inf file is, this is the file you edit

sevenpioverthree said:
Here is the guide for setting up ADB: http://forum.xda-developers.com/showthread.php?p=9936674
If you already have done that, then you should navigate to the directory I listed which is where the android_winusb.inf file is, this is the file you edit
Click to expand...
Click to collapse
Thanks for the help. I finally got odin to work after trying a dozen times. This definitely scared me a bit for a minute lol. The only downside now is that I lost about 2 weeks worth of data from my phone since that was my last backup point. Now I know how important back up can be.
Now back to this rooting..if I can remember:silly:

CyberGmonster said:
Let me make this short for you guys.
I was running carbon rom then decided to try CM 10.1 only because I am a romholic. CM was giving me small quirks so I tried to restore my carbon rom but for some odd reason it wouldnt go pass the samsung logo after it restored successfully. After trying to restore a few times over and over it just decided it was now going to fail. So I tried to go back to CM but now that also failed. So now I was trying to mount usb storage through TWRP but for some odd reason there's no way to do this. After trying to figure out wth was going on I finally made the biggest mistake of completely erasing my internal SD.
So now I am basically in TWRP 2.4.4.0 with no way to access usb storage and not knowing what I should do next.
Please help your fellow romholic
Click to expand...
Click to collapse
delete this / I replied after the fact....sorry.

Sucessfully flashed 98.18.78 recovery into Locked 98.30.1

I understand it is currently not possible to unlock a Razr M with 98.18.94 or 98.30.1 OTA. Never the less, I had been trying to restore a previous VooDoo root that I deleted before the last OTA. Through the experimenting, I screwed up the flash on my phone, and recovering it, I found something that might be interesting.
As others pointed out, downgrading does not work. Flashboot gives various errors. When I screwed up my file system, I was able to flash from 98.18.94 (which I had) to 98.30.1 (which was the only download I could find) using RSD Lite. I was lucky it worked. And since I have been able to experiment and keep flashing 98.30.1 over and over.
I would like to report that in my experiments, I noticed an interesting fact about the recovery.img:
I am able to flash stock 98.18.78 recovery to my phone running 98.30.1.
I have verified the recovery.img contents are not the same, according to a WinMerge file compare, they are ~10% the same
When I try to flash twrp or cwm recovery, the only fastboot error is to the effect "wrong partition size".
The size of .78 and 98.30.1 recovery are the same, 10,485,760 bytes
On the other hand, if I try to flash the .78 system.img fastboot, or use RSD lite to flash .78, I see different security related errors on the phone's fastboot screen- none of which mention partition size. Of course, this is related to the Locked Bootloader I have.
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Right now my Razr M has gone from 98.18.94 to 98.30.1 with a 98.18.78 recovery. And I'm working ok.
I am not a professional Android Dev. But I am going to do the research and try to modify a cwm type recovery to match the size of a Moto recovery, and see what happens.
I invite anyone with real experience to contribute.
Bryan

bryanwieg said:
What did you say?
Click to expand...
Click to collapse
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.

aviwdoowks said:
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
Click to expand...
Click to collapse
I have already found that if I take the OTA recovery and unpackbootimg and then mkbootimg without changing anything.. it recompiles down to aprox 5mb, which is different than the size it started from Moto.
So I am looking at if the size is set in how the img is compiled.

30.1 and .94 are the same updates, just different system versions. As for the other stuff, I'm not even sure what to say. I'm with Avi on this, I definitely would like to see what a dev has to say.

New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004

aviwdoowks said:
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
Click to expand...
Click to collapse
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.

bryanwieg said:
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
Click to expand...
Click to collapse
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.

aviwdoowks said:
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
Click to expand...
Click to collapse
Well, you'r right on the money. I appended data to a CWM recovery the same as Moto did to thiers, including the certificate at the end.
I didn't get a partition size error this time, but I did get a 'Failed to hab check for recovery'.
Granted, I didn't manage to place the 'empty data' at the same point in the file as the stock roms did. Other than that, it must be the certificate.

bryanwieg said:
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Click to expand...
Click to collapse
No, because it first checks the size (or whether it's a valid image at all) and if the size is correct, it checks the signature.

I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.

Really glad to see someone is still trying to find some sort of exploit for this device in it's updated state, it seemed like everyone had completely given up on it. My girlfriend recently grabbed a used Razr M to use for a while but it's fully updated, and I would love to be able to root it for her. I'll be following this thread to see if anything comes of this recovery downgrading

I'm pretty sure you can edit the props from what I can remember.
Sent from my XT907 using xda app-developers app

bryanwieg said:
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Click to expand...
Click to collapse
You can use root eplorer free to extract the single img from the 404 or 411 xml.zips
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Here http://sbf.droid-developers.org/phone.php?device=8
---------- Post added at 10:48 AM ---------- Previous post was at 10:44 AM ----------
The razr hd (2), atrix hd, photon Q all use a recovery w/ same key. Git to work man!

Re:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.

815turbo said:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
Click to expand...
Click to collapse
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.

I am willing to try it out. Win 7 64bit... pass me needed staf to flash it
Sent from my XT907 using xda app-developers app

please do
815turbo said:
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
Click to expand...
Click to collapse
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".

benya274 said:
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
Click to expand...
Click to collapse
I'll post it in just a few minutes. I will also post the required commands and we'll be backing up current recovery. If it fails, it should be no problem to restore your backed up recovery.
Download TWRP image on your phone from: titanroms.com/upload/rec.img
Please get to an adb prompt and run these commands:
su
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak2.img
Please ensure that both copies are 10MB. The dd command should end by saying "10485760 Bytes Copied" on all of the "dd" commands.
Now, you should have two backups of the recovery partition and the TWRP Image you downloaded from here all on your sdcard.
You can follow with these commands AFTER your backup has completed.
cp /sdcard/Download/rec.img /sdcard/rec.img
dd if=/sdcard/rec.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=twrprecbak.img
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.bak
reboot recovery
In the event of a failed attempt at this you can run the following from adb:
su
cd /sdcard/
dd if=/sdcard/recbak1.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give me a holler if you don't understand this well. Good luck, guys.

I am gonna try it out tomorrow,i dont have time to do it tonight cause i need to go to work. My pc on work does not have internet connection I will keep u guys posted on any progress.
Sent from my XT907 using xda app-developers app

Just wanted to say I flashed the old ICS recovery to mine using fastboot commands but it didn't get me very far though.if I then try and flash the corresponding blur zip from recovery it just says invalid signature. Was trying to find a way to downgrade so I could get rooted..
Sent from my XT907 using Tapatalk

Step by Step guides on rooting / un-rooting the T-mobile LG G5 (MM 6.0.1)

Hello everyone,
Here are some step by step guides for those of you who need detailed instructions for rooting and un-rooting the T-mobile LG G5.
The guides are short and to the point and are meant to be followed one after the other (STEP#1 --> STEP#2 --> STEP#3).
For the step#3 guide, you must choose one out of the three available guides below:
Guides:
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_1
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_2
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Re-install_STEP_3 <------ If you want to re-install stock MM 6.0.1 with root
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Upgrade_only_STEP_3 <------ If you want to root current stock MM 6.0.1
Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 <------ If you want to have stock MM 6.0.1 only (no root, use this if you want to return the phone or sell it)
They will walk you through:
Downloading and Installing the necessary drivers / tools
Unlocking your bootloader
Flashing the stock .kdz file
Flashing the rooted .TOT file
Using TWRP to gain root status
I assume the following:
You are using a Microsoft Windows operating system (Windows 7 or above)
You understand that all data on your phone will be deleted
You understand that your warranty is now gone
You understand that YOU MUST follow the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
You understand that YOU MUST follow the steps in the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
Your phone's USB PC Connection (mode your phone is in when connected to your PC) is on File Transfer mode. ADB and Fastboot commands to the device WILL NOT work if device is not on this mode
You read the Useful tips & information for the T-mobile LG G5 post
You read the Changelog + News & Additions post
***Un-root***​
If you want to "un-root" your device (go back to default stock) use the Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 guide.
(Keep in mind that this WILL DELETE all data on the phone)
***Disclaimer***​
I take no responsibility in what you do to your phone
The step-by-step guides in this thread were made with the assumption that you will strictly follow them one after the other.
(If you don't, YOU WILL brick your phone!)
If you run into an problem, verify that you have correctly completed all the steps for each guide before posting to this thread. Most problems come from guides / steps that were skipped.
If possible use a laptop that is fully charged and plugged in to an outlet instead of a regular PC (unless it has a UPS attached to it) just in case you lose power during the flashing process.
(If you use a regular PC without a UPS attached to it and you lose power during the flashing process, YOU WILL brick your phone!)
I would like to thank the following people for making all of this possible:
tungkick
wolfu11
arjuna_
Your work and dedication does not go unnoticed, thank you. I would also like to thank anyone else not mentioned here that allowed the rest of us to get root on our beloved LG G5 phones. The android community is awesome!!!
Sections:
Post#1: Main introduction & Files
Post#2: Useful tips & information for the T-mobile LG G5
Post#3: Changelog + New & Additions
Please leave a thank you if you find any of this helpful

**Useful tips & information for the T-mobile LG G5**​
How to install xposed: (Keep in mind that versions will change over time)
Download the latest xposed framework currently (xposed-v85-sdk23-arm64.zip):
- Go to the following web address: http://dl-xda.xposed.info/framework/
- Click on the sdk23 link
- Click on the arm64 link
- Download the latest xposed zip file currently xposed-v85-sdk23-arm64.zip
Download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk):
- Go to the following web address (xda thread): http://forum.xda-developers.com/showthread.php?t=3034811
- Scroll down to the "Attached Files" section and download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk)
Copy both files to the SD-CARD of your phone
Restart your phone into TWRP
Click on the INSTALL button
Flash the xposed framework file (xposed-v85-sdk23-arm64.zip)
Restart your phone and let it start normally
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and make sure there is a check mark next to Unknown Sources option
Open a file manager
Go to the location of the xposed apk
Install the xposed installer .apk file (xposed Installer 3.0 Alpha 4 apk)
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and remove the check mark next to Unknown Sources option
Start the xposed app
How to enter download mode
Power off the phone
Press and hold the VOLUME UP key
Connect the phone while holding the VOLUME UP key to your PC (use a USB-C cable)
Keep holding the VOLUME UP key until you boot into download mode
How to fix the Fastboot device driver issue (no devices detected)
Visit the following website and follow the instructions: Manually installing Android ADB USB Driver

**Changelog + News & Additions**​
Changelog (for the guides only):
7.16.16 - All guides have been updated to reflect the new 10d .kdz and .tot files. All links to tools, .kdz, and .tot files have been updated as well.
News & Additions:
7.16.16 - Multiple updates
A modified H83010d rooted .tot file has been released (thanks to Tungkick & wolfu11)
Guides are safe to use again. All links in all the guides have been updated to reflect the new H83010d files
If TWRP is not showing the internal storage but only the external SD-card take a look at post 24
7.9.16 - There is a new firmware update (H83010d) for the LG G5 (T-mobile) which is not compatible with firmware (H83010a) the .TOT files used in this thread have
If you upgrade to this new firmware, you will lose root.
There is no current way to get root on the new H83010d firmware unless the modified .TOT / KDZ files are released with TWRP included
There is an anti-rollback feature in the LG G5 (t-mobile) phone that prevents you from flashing back the H83010a firmware after you upgrade to the H83010d firmware. Attempting to do this WILL BRICK your phone!
Do not attempt to use the guides which are using H8301a .tot / kdz files if you have updated to H8301d. I will be updating the guides as soon as the H83010d modified .tot / kdz files come out.
5.29.16 - LG G5 & LG V10 possible driver issue: First reported on Post#6
If you own an LG V10 and have used your PC to root it, you most likely installed drivers, tools, and or files specific for the V10. What this means is that you may have to uninstall those drivers, tools, and or files prior to installing anything to be used for rooting the G5. This does not include the ADB program which can work for both.

i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:

mallman said:
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
Click to expand...
Click to collapse
Thank you.

Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
Two questions:
1) Does this automatically encrypt the phone? After flashing both the no verity and the SU it boots in to "encrypting" with no other option. I have not had this happen with any other device. Did I mess something up?
2) The password at the beginning of TWRP is requested every time, even after flashing the no verity zip. What did I do wrong?
Click to expand...
Click to collapse
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.

skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Thank you for your input skyfox99. Your solution to the issues you faced will help others avoid them. You made me think of something I did not anticipate which is what happens when you attempt to root your G5 using the same PC you used to root a V10. I am definitely adding a service announcement to the Changelog (post#3) to address this possible issue.

When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help

bigchuq said:
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
Click to expand...
Click to collapse
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Your internal storage gets wiped. That's why they weren't there.

mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No I was not, I'll give it a shot. Thanks

mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine

snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!

thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.

mikeyinid said:
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No, I copied after wipe so they were there. Computer recognized them and so does file manager.
jun19inf said:
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
Click to expand...
Click to collapse
TWRP has trouble mounting.
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
There is a TWRP bootloop set of instructions in another thread, run those commands and see if it resolves it, maybe?
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
I had to reflash no verity a few times, before installing SU. There seems to be a problem with TWRP.
Sent from my LG-H830 using Tapatalk

I didn't have any of the issues you guys are reporting in this thread. TWRP sees both internal storage and SD card. And has since I originally rooted.

Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app

shaneg79 said:
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.

jun19inf said:
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
Click to expand...
Click to collapse
It's ok I found out it doesn't affect it thanks for your answer.
Sent from my LG-H830 using XDA-Developers mobile app

I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??

rebelde80 said:
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
Click to expand...
Click to collapse
It's a very weird problem and unfortunately the only thing I can think off is that TWRP might not be compatible with the SD-Card you are using.