Database Develop

[GUIDE] Return to stock using FXZ for Linux/OS X

Here's a guide on how to restore to stock using the FXZ for OS X/Linux users.
1. Download one of the following fastboot binaries: fastboot-OSX or fastboot-linux and rename it to just "fastboot"
2. Download the FXZ and untar it anywhere.
3. Plug in your phone to your computer (preferably a back USB port if you're on a desktop, don't use a front USB port if possible) and shut it down (leave it plugged in).
4. Hold down the vol-down button on the rocker and boot the phone up, it should boot into AP Fastboot Flash Mode and it should say "OK to Program".
5. Run the following commands in terminal
Code:
./path/to/fastboot flash system /path/to/system.img
./path/to/fastboot flash boot /path/to/boot.img
./path/to/fastboot flash recovery /path/to/recovery.img
./path/to/fastboot -w
6. Shut off the phone by pressing the power button.
7. Boot back up and you should be back to stock!

Thanks for posting this for us linux users. Hopefully I won't have to use it any time soon haha

I keep gettiing permission denied when entering the first command. Any suggestions? Thanks

Will this run without a Bionic attached? I'm just trying to get everything set up and run it to make sure it starts...

dscottjr81 said:
I keep gettiing permission denied when entering the first command ./fastboot flash system system.img. Any suggestions? Thanks
Click to expand...
Click to collapse
BUMP...........

have you tried sudo?

Has anyone had any success with this yet?

1KDS said:
Has anyone had any success with this yet?
Click to expand...
Click to collapse
I am doing it right now. There are some issues. Without sudo, you'll get permission denied. With sudo, you'll get "./fastboot: command not found". After changing fastboot to be executable without sudo, you'll get "./fastboot: cannot execute binary file". With sudo, you'll get "./fastboot: 3: Syntax error: "(" unexpected"...so short story, this does not work properly yet
---------- Post added at 03:37 PM ---------- Previous post was at 03:24 PM ----------
1KDS said:
Has anyone had any success with this yet?
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1279825
There is a one click Linux/Mac return to stock and root method there and it works. Hope that helps. It is extremely easy!

Bionic Restorer for Linux/Mac
OK, I'm finished with the new MotoRooter for Mac/Linux - naming it BionicRestorer because it's completely different. Right now it's in my Dropbox Folder, still no where to put it - lol.
Here's the link to BionicRestorer.zip
For Mac and Linux people - it's BionicRestorer v1.0
A way to flashboot restore your Bionic to 5.5.893
Download it, unzip it, cd into the BionicRestorer directory and type ./BionicRestorer.sh to run it. Mac folks can double click on the Mac-BionicRestorer.command file in that directory.
Linux People - this is solid, I've run it on LinuxMint (Ubuntu) and Scientific Linux (Redhat) and it worked everytime without a glitch.
Mac People - This is tempermental on the Mac, I've tried it on 3 different
Mac's and it worked sporadically on a Macbook Air running 10.7.2, didn't work on the iMac at all running 10.7.2,
and worked consistently on a Macbook running 10.6.8. Use at your OWN RISK!!!! If it hangs, all I
can is - try it again, or, run Linux, or, use RSDlite on Windows.
I can say that it worked consistently on a Macbook running 10.6.8
Option 3 (restore system, boot, recovery seems to work well on a Mac, but,
NOTE that these files are from v5.5.893! If you select option 3 you had better have flashed or updated to that version perviously, or, it will most likely bootloop when it finishes.
Note - This does NOT contain the actual files needed for flashing,
just the brains to flash them. You will need to download the zipfile
VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml.zip from
http://rootzwiki.com...893-fxz-leaked/
then unzip it into the BionicRestorer directory.
Once it is extracted there should be a directory named:
VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml
which contains all the files needed to do a flash restore.
And the menu looks like this:
BionicRestorer.sh (1.0) by crpeck
1. Restore a Bionic to 5.5.893 - NOT FOR 5.9.901 BIONICS!
-restores EVERYTHING to official 5.5.893
-wipes data
2. Restore a 5.9.901 Bionic to 5.5.893
-restores EVERYTHING EXCEPT for the cdt.bin to 5.5.893
-cdt.bin is restored using the 5.9.901 file
-wipes data
** YOU SHOULD ONLY USE THIS IF YOU ARE OR HAVE BEEN ON 5.9.901 **
3. Minimal Restore of system, boot, and recovery only
-restores ONLY the system,boot and recovery to official 5.5.893,
4. Root and ForeverRoot a non-rooted Bionic
-roots and installs the ForeverRoot hack
5. Copy 5.9.901 update file to sdcard
-this copies the unoffical 5.9.901 update file to your sdcard
chances are, your Bionic will bug you to do an update when it see's it
there, you can usually force it via the 'Check for Updates' screen.
6. Verify MD5sums of the flash image files (you should do this at least once)
7. Help - More detailed Information
q. Quit
NOTE: Selections 1-3 do NOT root the phone! Run 4 after running them.
By Your Command (1-7,q):
I took the .xml file from the VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml.zip and re-wrote it into shell scripts (i also took out the piece in there that erases the internal sdcard - who wants to lose that - lol). There is a considerably amount of error-checking as well, but, I'm sure I missed something (which will result in v 1.1).
I encourage you to look through the scripts, feel free to modify and make it better! This may be the last release of this from me, as work is replacing my Bionic with a gnex in the near future - gonna miss the Bionic, it's been a fun learning tool.
Enjoy....
Oh - look at the 00_README_1ST.txt file - it's similar to this writeup, and, select the help option for more detailed information.

I've have to give this a try. I keep forgetting I have Ubuntu(dual-boot) on this thing. Heh

i'm running SafeStrap 3.11 and wiped my safe partition in a late night flashing frenzy. is it possible to flash certain partition images to restore the stock ROM without loosing SafeStrap?

mechanizedmedic said:
i'm running SafeStrap 3.11 and wiped my safe partition in a late night flashing frenzy. is it possible to flash certain partition images to restore the stock ROM without loosing SafeStrap?
Click to expand...
Click to collapse
Flash system.IMG
fastboot flash system /path/to/system.img
fastboot flash boot path/to/boot.img
Any other partition you might want to flash flashing recovery partition will erase safe strap might lose safestrP after flashing system you will lose root regardless

[ROOT][CWM] Root Nexus 4 & Install Official ClockworkMod Recovery

I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.

Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.

Checked...thanks. =) Added the links.

stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied

jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.

BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.

HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.

I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.

Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.

I installed after ota
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.

when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?

Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2

Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.

After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!

quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?

Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)

0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.

HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?

[WIP] [REQUEST] Misc partition dumps

Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.

Edit: nvm
Here is the dump. Thanks for your work.

KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.

KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?

I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.

KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command

I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....

KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"

Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method

KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.

Glad I could help. Now folks have less things to worry about when they decide to root

KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.

efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.

KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).

For science

KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.

osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.

Tools to take OTA for Sprint M8/Get Back to Stock

FOR SPRINT M8 NON-H/K MODELS ONLY​
Well everyone I'm here to bring you a little tool set i use to take official OTAs.I am not a dev nor do I take credit for the work. This is mainly just a collection of things I used to get OFFICIAL OTA updates. I've used this on 2 Sprint m8's with STOCK Hboots so I am sure this will work. Please feel free to share this with others JUST GIVE CREDIT WHERE IT IS DUE.
To start off there are some requirements...
S-OFF is needed
STOCK HBOOT
HTC One M8 (Sprint non-Harmon Kardon)
UNLOCKED Bootloader (If you are LOCKED and rooted PLEASE use UNLOCK Bootloader method included in zip. DO NOT use HTCDEV to unlock... Your internal storage will be wiped if you do. YOU HAVE BEEN WARNED
MAKE SURE TO UNLOCK BOOTLOADER before doing any of this (instructions are included in zip)
1. Copy the stock nand to backup folder in twrp
2. Make a backup of your setup
3. Restore the stock nand provided
4. Flash stock recovery provided
5. Boot up and do all otas up to latest
6. Flash custom recovery
7. Restore your backup
8. Flash modified firmware
9. Lock bootloader
10. Flash asdp for hk mod.zip in ruu mode (same as flashing FIRMWARE) if audio is not working in htc music
Locking-Unlocking & Remove Tampered flag
***NEED TO BE S-OFF!!***
TO LOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***LOCKED***
TO UNLOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***UNLOCKED***
TO REMOVE ***TAMPERED*** text
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should not see ***TAMPERED***
Flashing Firmware
IN HBOOT MODE
1. Label the file to exactly 0P6BIMG.zip
2. Put zip in root of external SD card
3. Boot into HBOOT to flash (bootloader should detect zip automatically and prompt you to flash)
IN FASTBOOT MODE
1. Boot device into FASTBOOT mode (device should show FASTBOOT USB)
2. Put the firmware file to be flashed in the folder with fastboot.
3. Open a command prompt from the folder where fastboot is located.
4. Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 0P6BIMG_M8WHL_x.xx.xxx.x_firmware.zip (the name of the zip should match the name of the file you're flashing)
5. Once complete, you can fastboot reboot or fastboot reboot-bootloader depending on what you want to do next. If you choose bootloader, you can confirm that your radio is now updated to the one from the file you flashed
Links needed ...
For Locking and Unlocking bootloader (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Removing Tampered Flag (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Modified Firmware
I'd like to give thanks to the people that have made this possible
if i forget someone I'm sorry send me a pm I'll add you to the list
Team420 for taking me in showing me the basics
BADSEED for allowing me to break so many test roms lol
BD619 for hooking me up with adb files
scotty1223 for making those awesome guides
Captain_Throwback for providing the collection of firmware ... Oh yeah and the TWRP recovery
TEAMWIN for making TWRP in the 1st place
HTC for making such an awesome phone
DISCLAIMER: I AM IN NO WAY HELD LIABLE FOR DAMAGES MADE TO YOUR PHONE OR IF YOUR DEVICE TRANSFORMS INTO A DECEPTICON CAUSING WORLD DESTRUCTION...YOU ARE FOLLOWING AND FLASHING THIS AT YOUR OWN RISK

DOWNLOADS​
Main Link on Mega HERE
Mirror Link on AFH HERE

And this as well

Hi,
Added to FAQ Guide Q15

Nice work Miggs:thumbup:
Sent from my HTC M8

Great work Bro, very helpful. Thank you

Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8

Magnum_Enforcer said:
Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8
Click to expand...
Click to collapse
GOOD CATCH!! THANKS ... That was actually how this idea came about lol

Good work Miggsr!

Need stock apps to take OTA
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.

Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
Why not just keep a backup of the latest stock rom on your sdcard?

BD619 said:
Why not just keep a backup of the latest stock rom on your sdcard?
Click to expand...
Click to collapse
Or look in the first post of this thread for stock backups:
http://forum.xda-developers.com/showthread.php?t=2736048
Sent from my HTC M8

Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
in my zip i have included a STOCK backup made with TWRP that is also included in the zip it has ALL stock apps that you may be looking for to make things easier just copy that folder to your TWRP backup folder whether its on your internal sd or external sd restore that and boot up

Tring to upgrade "dirty"
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?

Piroman024 said:
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?
Click to expand...
Click to collapse
okay with the first half of what you said... i have not had an ota check for apps... when removing google plus you probably left a second apk that works with it hence your error message. if you are looking to be able to take an official ota you should NOT be rooted. honesty if you meet ALL REQUIREMENTS i listed then just follow the guide you should be fine. the backup i have there is based on initial rom that came with the device. so you will have to do 3 ota updates to be exact. i made it that way out of personal preference. now for the second half of your post ... as i mentioned i am not a dev unfortunately i can not answer that question for you... slightly above my pay grade. not to put you on the spot either i'd like to keep thread on topic in OP.

so Harmon Kardon edition can not be unroot?

hhhstonehhh said:
so Harmon Kardon edition can not be unroot?
Click to expand...
Click to collapse
Sure it can...same steps just use HK files

BD619 said:
Sure it can...same steps just use HK files
Click to expand...
Click to collapse
I could not have said it any better lol

Great Tut Miggs !!!

cbrown245 said:
Great Tut Miggs !!!
Click to expand...
Click to collapse
thanks CB i just making things easier for others

[GUIDE] LG L90 D415 (US - Lollipop) - Install TWRP

My terrible video guide to follow: http://youtu.be/1UkPPqfz3kE (really really bad video guide that i just winged but it explains the basics of what you need and what you do)
Here's the textual guide:
Requirements:
1. Rooted Lollipop D415 - http://forum.xda-developers.com/lg-l90/general/guide-root-lg-l90-running-d41510e-t3072568
2. Terminal App (Must have SuperUser Enabled to work)
3. twrp.img - https://drive.google.com/file/d/0B08SrD985jkQMko3LTFZRFpZdG8/view?usp=sharing
4. Unlocked Bootloader (Supposedly) http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
(Hopefully those are all)
Steps:
1. Turn on the phone (no brainer)
2. Ensure your phone is rooted
2.5. Put twrp.img into /sdcard
3. Go to your terminal app and type in this command (WITH SU): dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
It should take a few seconds before it gives out a little output saying so and so was transferred.
4. Type in 'reboot recovery' with SU and you should boot right into a fresh custom recovery.
I do not take credit for any of the stuff made here. I just made the guide, not the .img, or the apps. Just the guide.
(TWRP on KitKat 4.4: http://forum.xda-developers.com/lg-l90/general/video-guide-installing-twrp-custom-t2975417)
Disclaimer: I do not take responsibility for damage done to your phone. You do this at your own risk.

TWRP will not flash no matter what flash tool I use, I'll flash the img. & boot to recovery but no TWRP. Any suggestions?
Sent from my LG-D415 using XDA Premium 4 mobile app

GENIUS!
Sadcamp said:
My terrible video guide to follow: http://youtu.be/1UkPPqfz3kE (really really bad video guide that i just winged but it explains the basics of what you need and what you do)
Here's the textual guide:
Requirements:
1. Rooted Lollipop D415 - http://forum.xda-developers.com/lg-l90/general/guide-root-lg-l90-running-d41510e-t3072568
2. Terminal App (Must have SuperUser Enabled to work)
3. twrp.img - https://drive.google.com/file/d/0B08SrD985jkQMko3LTFZRFpZdG8/view?usp=sharing
4. Unlocked Bootloader (Supposedly) http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
(Hopefully those are all)
Steps:
1. Turn on the phone (no brainer)
2. Ensure your phone is rooted
2.5. Put twrp.img into /sdcard
3. Go to your terminal app and type in this command (WITH SU): dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
It should take a few seconds before it gives out a little output saying so and so was transferred.
4. Type in 'reboot recovery' with SU and you should boot right into a fresh custom recovery.
I do not take credit for any of the stuff made here. I just made the guide, not the .img, or the apps. Just the guide.
(TWRP on KitKat 4.4: http://forum.xda-developers.com/lg-l90/general/video-guide-installing-twrp-custom-t2975417)
Disclaimer: I do not take responsibility for damage done to your phone. You do this at your own risk.
Click to expand...
Click to collapse
You my friend are a freaking genius! this saved my D415 and I was so worried. It works just awesome!
Thanks once again!

stevenDROID said:
TWRP will not flash no matter what flash tool I use, I'll flash the img. & boot to recovery but no TWRP. Any suggestions?
Sent from my LG-D415 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Extremely sorry for my late reply, but
are you sure you have not tried the terminal app i suggested in the video?

I used flashify. No computer. From stock to cm 13 in 10 minutes. Lol. This is one of my many fun hack phones all budget. My note 5 is staying unrooted

Another really simple way is a rooted device and LG L90 utilities app. Search XDA it's made by member shinobisoft
Wonderful app. Doesn't work on 6.0 & 6.0.1

TWRP version
Can I use another (recent) version of TWRP or this way is just functional with the linked twrp.img?

AlexJSK said:
Can I use another (recent) version of TWRP or this way is just functional with the linked twrp.img?
Click to expand...
Click to collapse
Any TWRP in IMG format should work. Just mke sure you have a D415 since it has a partition map that's is different from other models and this tutorial uses an adb command that is suitable to D415 only.

Need help i put in the command exactly as posted "dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17" and it keeps giving an error that it doesn't exist i did move the file to the sdcard after installing it but still same thing. The fileyou linked once downloaded actually downloads as "0B08SrD985jkQMko3LTFZRFpZdG8.bat" should i replace the twrp.img line with this name or rename the file to twrp.img or what? Im confused as im trying to learn but not fluent in this process.
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
xxlcountryguy83 said:
Need help i put in the command exactly as posted "dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17" and it keeps giving an error that it doesn't exist i did move the file to the sdcard after installing it but still same thing. The fileyou linked once downloaded actually downloads as "0B08SrD985jkQMko3LTFZRFpZdG8.bat" should i replace the twrp.img line with this name or rename the file to twrp.img or what? Im confused as im trying to learn but not fluent in this process.
Click to expand...
Click to collapse
0B08SrD985jkQMko3LTFZRFpZdG8.bin sorry it downloads as .bin not .bat

xxlcountryguy83 said:
Need help i put in the command exactly as posted "dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17" and it keeps giving an error that it doesn't exist i did move the file to the sdcard after installing it but still same thing. The fileyou linked once downloaded actually downloads as "0B08SrD985jkQMko3LTFZRFpZdG8.bat" should i replace the twrp.img line with this name or rename the file to twrp.img or what? Im confused as im trying to learn but not fluent in this process.
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
0B08SrD985jkQMko3LTFZRFpZdG8.bin sorry it downloads as .bin not .bat
Click to expand...
Click to collapse
Are you still on KitKat? If you are already rooted, and probably are, you can use an app like Hashr or Flashfy to flash recovery, both free from Play Store. I haven't tested the file but I recommend that you flash img only, double check the download procedure, there are many ads that lead to wrong downloaded files...