Database Info

How I rooted my Thunderbolt 2.11.605.9

I got a new Thunderbolt and it came with 2.11.605.9 on it and would not downgrade no matter what I tried.
All these instructions and links came from several different posts on various forums.
This is the combination of things that worked for me to gain root access to the device.
The information and links I take no credit for.
Hope this helps someone as it has helped me.
I did not loose my data with this.
The text in purple are links to needed files, just put http:// in front of them.
Unlock the bootloader
htcdev.com/bootloader
Install Clockwork
• Get fastboot and adb tool for windows here: forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076
• Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537331
• Obtain clockworkmod recovery:
• HTC Thunderbolt/Mecha cwm-4.0.1.4-mecha.img: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
• md5 : 7990c4d2a5967c0e2c694ba75a65b99d
• Move the recovery.img above to the same directory/folder/map as fastboot and navigate there with an open cmd prompt (WIN) or terminal (LINUX).
• Put the phone is Fastboot USB mode
Type adb devices and press enter. This should output your phones serial number
Type adb reboot bootloader and press enter. This will boot you into the fastboot screen (white with colored letters)
• Type fastboot flash recovery recovery_name.img replacing recover_name with the name of the file you wish to flash and press enter. <<< from a command line (use root for Linux- sudo ./fastboot flash recovery recovery_name.img)
Install the su package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.
9. You're rooted!
Install Superuser from the market.
Install SuperManager from the market.
Install Busybox from the market.
Install Terminal Emulator from the market.
You can flash ROMs in the same manner the SU package was flashed.
If you want to edit / change system files you can su then remount the FS to rw with the following command within terminal or adb shell :
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system

snaganalf said:
I got a new Thunderbolt and it came with 2.11.605.9 on it and would not downgrade no matter what I tried.
All these instructions and links came from several different posts on various forums.
This is the combination of things that worked for me to gain root access to the device.
The information and links I take no credit for.
Hope this helps someone as it has helped me.
I did not loose my data with this.
The text in purple are links to needed files, just put http:// in front of them.
Unlock the bootloader
htcdev.com/bootloader
Install Clockwork
• Get fastboot and adb tool for windows here: forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076
• Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537331
• Obtain clockworkmod recovery:
• HTC Thunderbolt/Mecha cwm-4.0.1.4-mecha.img: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
• md5 : 7990c4d2a5967c0e2c694ba75a65b99d
• Move the recovery.img above to the same directory/folder/map as fastboot and navigate there with an open cmd prompt (WIN) or terminal (LINUX).
• Put the phone is Fastboot USB mode
Type adb devices and press enter. This should output your phones serial number
Type adb reboot bootloader and press enter. This will boot you into the fastboot screen (white with colored letters)
• Type fastboot flash recovery recovery_name.img replacing recover_name with the name of the file you wish to flash and press enter. <<< from a command line (use root for Linux- sudo ./fastboot flash recovery recovery_name.img)
Install the su package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.
9. You're rooted!
Install Superuser from the market.
Install SuperManager from the market.
Install Busybox from the market.
Install Terminal Emulator from the market.
You can flash ROMs in the same manner the SU package was flashed.
If you want to edit / change system files you can su then remount the FS to rw with the following command within terminal or adb shell :
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App

i used these steps and I still have s on. When I tried to flash a new rom it gets stuck at the htc boot screen. Any help would be great!

I think I would use the downgrade to .5 then revolutionary from there..
something like this http://forum.xda-developers.com/showthread.php?t=1401959

z71kris said:
I think I would use the downgrade to .5 then revolutionary from there..
something like this http://forum.xda-developers.com/showthread.php?t=1401959
Click to expand...
Click to collapse
I tried this just now but when it goes through the integrity check it does not give me the option to update.

Yes, if you can downgrade at all do it that way. It's much simpler. If you aren't familiar with linux the above will be a hassle for you.
Reason being is, you have to remount the file system to read write every time you want to make a change. It resets to read only on reboot. Thus the s-on.

the weird thing is I already have a rooted devices cause I have the cwm recover still loaded on my device. Just can not flash anything over it. Im on windows 7 right now but I dual boot my laptop with linux mint.

I haven't tried to flash a ROM yet. I just wanted access to some system files so I could edit them.
But according to the post I got the Clockwork info from the below steps should work to flash ROMs.
1. Copy <ROMname>.zip (where <ROMname> is the name of the ROM zip file) to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "<ROMname>.zip"
6. Then select "Yes - install <ROMname>.zip" to confirm
7. Then go back
8. Then reboot.
I don't know however if the ROM has to be signed.

need a hero
I followed this guide and every other guide to root my phone. I could not downgrade the way the other guides told me to the 2.11.605.5 at all. I followed this guide and when i was in the bootloader i did the whole fastboot flash and it worked but now my phone still says s-on (strange thing is that I have the clockwork recovery). I can flash any rom but nothing will take and I either go into bootloop or will not boot past splash screen. I need a true hero to save the day. It is my only phone and means of communication.

Did you get SU and busybox installed?

I'm not sure, I can't boot in any rom so if it was in the su.zip this guide linked me to yes, if not i didn't. Could this be the problem? Can I fix it through h-boot or recovery?

The method I used will allow root access but does not give you s-off.
I'm still looking for what has to be done for that.
apparently you have to have s-off in order to flash a ROM.

I was able to flash skyraider and now have my phone up and running. I updated superuser, installed Rom manager and flashed clockwork recovery. My phone still says s-on and will not boot any bamf 3.5 roms or the eternity rom, so I'm still kinda confused as to why. I would love to have a sense 3.5 Rom but I'm stumped...

That is strange, being able to flash one ROM but not others.
I still think it's got to do with the s-on/s-off.
Supposedly ICS is coming for the T-Bolt soon.
I'm hoping it won't be locked down like 2.11.605.9 is.

i rooted as soon as rooting was available, no downgrading or anything, it was easy as pie. js

Have you tried going to revolutionary's site after the OP method and try to get s-off... HTC method will not give you s-off & is not a true rooting tool..

Big thanks to the OP for putting this together!
This was the only way for me to gain root on a factory flashed 605.9 phone.
EDIT: i'm a linux user so i thought i would share what i did to get root. it's basically what the OP did with a linux twist.
1) Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537 331
2) Extract the zip to your home directory.
3) open a terminal and issue the following command: sudo chmod 777 fastboot adb
4) Unlock the bootloader using this site: htcdev.com/bootloader
5) you will need to register/login to use the unlocking features of this site.
6) once logged in follow the "unlock device" links to get to the instructions. use these instructions to put the phone into fastboot mode and connect it to the computer. you can ignore the rest of the instructions as most of them are for windows. just click through until you get to the part about submitting an "unlock token".
7) with the phone in fastboot mode and connected to the computer issue the following command in a terminal: sudo ./fastboot oem get_identifier_token
8) copy this token into the submit box and edit to make it look similar to the example on the same page. submit the token and you'll get an email with a file "Unlock_code.bin"
9) save "Unlock_code.bin" to your home folder then issue the command: sudo ./fastboot flash unlocktoken Unlock_code.bin
10) download clockwork recovery to your home folder from here: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
11) issue the command: sudo ./fastboot flash recovery cwm-4.0.1.4-mecha.img
12) Download and install the superuser package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.

s off??
mechanizedmedic said:
Big thanks to the OP for putting this together!
This was the only way for me to gain root on a factory flashed 605.9 phone.
EDIT: i'm a linux user so i thought i would share what i did to get root. it's basically what the OP did with a linux twist.
1) Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537 331
2) Extract the zip to your home directory.
3) open a terminal and issue the following command: sudo chmod 777 fastboot adb
4) Unlock the bootloader using this site: htcdev.com/bootloader
5) you will need to register/login to use the unlocking features of this site.
6) once logged in follow the "unlock device" links to get to the instructions. use these instructions to put the phone into fastboot mode and connect it to the computer. you can ignore the rest of the instructions as most of them are for windows. just click through until you get to the part about submitting an "unlock token".
7) with the phone in fastboot mode and connected to the computer issue the following command in a terminal: sudo ./fastboot oem get_identifier_token
8) copy this token into the submit box and edit to make it look similar to the example on the same page. submit the token and you'll get an email with a file "Unlock_code.bin"
9) save "Unlock_code.bin" to your home folder then issue the command: sudo ./fastboot flash unlocktoken Unlock_code.bin
10) download clockwork recovery to your home folder from here: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
11) issue the command: sudo ./fastboot flash recovery cwm-4.0.1.4-mecha.img
12) Download and install the superuser package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.
Click to expand...
Click to collapse
will this get s off? I dont think it does I did this with windows 7 and it didnt seaem to work

I think this is solved
topdogle1 said:
will this get s off? I dont think it does I did this with windows 7 and it didnt seaem to work
Click to expand...
Click to collapse
There is a thread about not having to downgrade that I was able to use to get s off in the Thunderbolt forums. search "Downgrade to get S-off is now unneccessary":laugh:

LaBlondeJames said:
There is a thread about not having to downgrade that I was able to use to get s off in the Thunderbolt forums. search "Downgrade to get S-off is now unneccessary":laugh:
Click to expand...
Click to collapse
This post HTCDev unlocks, but sadly does not S-OFF.
tool in sig but if you did this and unlocked you will have to wipe data to use it. (email me for instructions)

[Guide/Tutorial][11/14/12] Lost Root ? after an update or new ROM ?

Have You Lost Root? - Can't find or reinstall su (su binary) ?
Issue:
Your Transformer or other device is unlocked and rooted, you have a custom recovery like ClockworkMod installed and you flash a rom or an update and when done you find you have partial root or no root at all.
Some apps that have previously been granted superuser permission may load while others, including superuser, super su, busybox, Voodoo, CWM say you don't have root, you are missing the su binary file.
When you run Root Checker it might look something like this link.
SOUND FAMILIAR?
Most likely the flashed ROM or update erased the \system\bin\su and system\xbin\su files and didn't replace them.
Since CWM requires the su binary file to get root access to restore from my nandroid I had to use fastboot to get into recovery.I went to my SDK drectory, sub directory platform-tools where fastboot resides..
If you do not have an SDK directory just download SDK installer from [url]http://developer.android.com/sdk/index.html[/url] to C:\android-sdk\platform-tools
Once the SDK Manager comes up put a check in Tools (this will put a checkmark in the two daughter files) Remove any other checkmarks..Hit the Install Packages bar at the bottom.
This platform-tools folder has fastboot.exe command and is the folder you will work from. You can also copy all the files you want to push into this directory but for now we will concentrate on our issue..
Connect your device to your PC, then turn off your device and boot into fastboot mode on your device.
If you don't know how:
hold down volume down and power button until you see white text on the screen, let go both buttons, use the volume down button to switch the highlight to the USB icon (this is fastboot mode), now hit the volume up button twice.
On your PC open command prompt and navigate to the fastboot directory which is C:\android-sdk\platform-tools
Once you there type the following:
fastboot -i 0x0B05 flash recovery recovery.img (check the specific recovery.img file that you have. It could be recovery-jb.img or recovery.blob etc).
Once the process is done type the following:
fastboot -i 0x0B05 reboot
your device will reboot.and can now boot into recovery.
Turn your device off and re-boot into (clockworkmod) CWM recovery
(hold down volume down and power button until you see white text on the screen, let go both buttons, now hit the volume up button twice.)
You want to hit wipe cache partition. When done hit advanced then wipe dalvik cache then go back.
Now hit backup and restore. Once there hit advanced restore from internal sdcard (where you put your nandroid) Then highlight the most recent date
In Advanced Restore hilight Restore system
Once done you can exit out (go back) to reboot system now
Once device boot up find and open superuser app, then download "root checker" from the market and verify that you have root.
RECAP:
Connect device to PC and boot device into fastboot
On your PC open command prompt and cd to C:\android-sdk\platform-tools
type
fastboot -i 0x0B05 flash recovery recovery-jb.img (.img file exactly as it is in platform-tools) hit enter
when process is done, at the prompt type
fastboot -i 0x0B05 reboot (your device will reboot).
Turn your device off and re-boot into CWM recovery and wipe cache and dalvik cache
go to advanced restore and only Restore system
go back to reboot system now
Once device boot up open superuser app, then "root checker" and verify that you have root.
Enjoy

Need help preparing Xoom for official updates

Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?

You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.

Wow, what a detailed guide
Thank you sir

No problem!
Let me know how it goes, hopefully shouldn't have any problems.

Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:

alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again

Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!

alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!

Help, Moto g won't boot up any rom

I unlock the g bootloader got it to root I have the latest cwm recovery been trying different ones also, but some how when I try to install any rom that's out there it won't boot up it only stays on the boot screen . Any ideas

Me too
I have this problem too.

Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.

forgotter said:
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
Click to expand...
Click to collapse
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem

chente323 said:
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
Click to expand...
Click to collapse
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.

forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
This is the same thing a friend told me to do we did it had no luck Did it 2 times just in case I dint do it right the first time

Moto g not booting up.
I hope you have an unlocked boot loader.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC rename it to "CM.zip" and extract the contents to adb folder (adb folder should be in C drive i.e. C:/adb ). You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push C:/adb\system /system/"
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push C:/adb\boot.img /data/"(to verify whether /data is writable or not)
"fastboot push C:/adb\boot.img /cache/"(to verify whether /cache is writable or not)
"fastboot push C:/adb\CM.zip /data/media/0/"(to push the CM11rom to sdcard to flash it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data. Then go to wipe and wipe /data and /sdcard and then again push CM.zip to /data/media/0/. If you don't see this error, then choose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11.zip or you can flash stock firmware through mfastboot.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.

forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Thanks I will give it a try tomorrow since it's wife phone I don't have it w me now. I'll get back at u let u know if it work

forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
Hi forgotter! I have the same problem... won't boot with any ROM. I've followed your instructions but stil stucked on the boot logo. I will try the second method you provided now, hope that works :crying:

@notnowjohn
Didn't know why first method didn't worked for you but the second one would definitely work. If you get any error then reply to me, and yes in my second method post by mistake there are some extra space added after full stop (.) e.g. in boot. img (it is boot.img ) do please avoid that.

forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone

notnowjohn said:
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
Click to expand...
Click to collapse
Don't worry your phone is fine.
Whenever adb shows m mismatched partition it's fine and usual.
I understand your problem now, I just think if I your device now , I would have repaired it within minutes. Never mind, follow the below steps .
Download the philz recovery to your PC, flash it through fastboot on your phone. Then go to recovery on your phone immediately and choose wipe-wipe data and sdcard. And then flash the stock firmware through mfastboot or install any ROM through recovery.

Anyone report which step what must i do to solve this prob

sinkadorable said:
Anyone report which step what must i do to solve this prob
Click to expand...
Click to collapse
Read post #7 on page 1.

I cant push system to device. What tools must be i have?

If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.

pluiz halp!
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:

jamiethomaswhite said:
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
Click to expand...
Click to collapse
Plug the phone to wall charger and leave it to charge for the whole night, the next when you'd restart the phone it should boot up. Sometimes the phone discharged itself to such a level that it didn't have enough juice left to show the battery charging status even.
After that follow instructions from post #7 on page 1 and paste all output commands you see. Well, the phone should boot up.

forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:

sinkadorable said:
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
Click to expand...
Click to collapse
Mismatched partition size is usual , no need to worry about that. What do you mean by UBL warning message? And yes, after you flash recovery, enter in recovery mode and wipe data and sdcard and then flash any ROM from fastboot.
And if you get into an error or solution doesn't work then post your problem but detailed so I can get to the main cause of the problem.

[RECOVERY][e2nam] TWRP 2.8.5.0 touch recovery LG MS395

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
DOWNLOAD:
TWRP Builds
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Latest Windows adb drivers required for sideload
HERE
Latest Linux adb drivers required for sideload compiled from android source
HERE
To install unzip and open terminal in root of folder
Code:
sudo cp adb fastboot /usr/bin

Installation
You must be rooted first follow the guide here
This can be flashed with several methods
1.) Flashify
Choose the name of the recovery image you want to flash
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) Fastboot (Must be enabled first)
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Run the following code to zero out laf:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
To flash recovery copy openrecovery-twrp-2.8.5.0-e2nam.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery openrecovery-twrp-2.8.5.0-e2nam.img
To boot into recovery
Code:
fastboot.exe boot openrecovery-twrp-2.8.5.0-e2nam.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push openrecovery-twrp-2.8.5.0-e2nam.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/openrecovery-twrp-2.8.5.0-e2nam.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery

Thanks for this. Will give it a try after work today. Hopefully unlocking won't give a noob like me any trouble.

I would recommend just putting the recovery on laf
Code:
fastboot flash laf recovery.img
We don't have button combo and it makes booting into recovery easier if you don't have access to the system or a PC by allowing you to boot into recovery the same way you boot into download mode.

Thank you!
Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
This works. No problems. :laugh:

Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
I can't seem to get the into fastboot. I have Minimal adb and Fastboot installed, put the recovery image that folder, but my phone just reboots normal no how I tell fastboot to do it..recovery, download, etc. Don't understand this, could it be causing this "fastboot (Only works if you chose to keep fastboot mode in the linked guide) "

Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
Step 2 didn't have the adb in the code and I was copy and pasting and could get it to work. Finally figured it out. I know it's a rookie thing with me and this was the first time I used fastboot. Working now and have TWRP. Thanks!!

I was able to get TWRP on using fastboot but I don't understand this- "2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide) "
Are you referring to having the recovery.img file the same location as fastbook.exe or does this mean something else?
Thanks

I'm a noobie with a question. Fortunately I was able to root and install twrp with flashfy app. Down the road if I brick my phone, how can I recover? Is there button combo on the f60 for twrp? what is fastboot?
Sent from my Z970 using Tapatalk

I am new myself and will let Unjustified explain Fastboot, although I did use that method to flash TWRP, I don't want to give you bad advice. With that said, I have Xposed Framework installed and also Gravity Box KK. Gravity box has many cool customizations and one is you can change the options you get when you reboot your phone. One the choices is reboot into recovery. Hit that and you will boot up into TWRP.
If that doesn't work for you, there is an app called Quick Boot in the play store that does the same thing as far as different choices for rebooting. Fastboot you would need to connect to you PC/Laptop and know the commands to boot into recovery, again any further details I l;eave to others that know more.
Hope this helps some.
---------- Post added at 07:20 AM ---------- Previous post was at 07:09 AM ----------
smilesintears77 said:
I'm a noobie with a question. Fortunately I was able to root and install twrp with flashfy app. Down the road if I brick my phone, how can I recover? Is there button combo on the f60 for twrp? what is fastboot?
Sent from my Z970 using Tapatalk
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2317790. You can read in that thread for more info on ADB and fastboot. This was a little easier for me then just using the commands posted above where you would execute them with CMD prompt from your PC, just make sure you are going to the root folder where the adb.exe and fastboot.exe are located. I was doing that wrong when I was trying to root at first. My choice not to use Flashify was strictly because I wanted to learn more, so please wait for others to chime in who know more then I.

Our phone has no button combo to reach recovery.
You usually would be able to use the factory reset button combo and then cancel to recovery but all I get is hardware cursor mode. If someone else has achieved these results then disregard the below message. :
If you would like to reach recovery from power off, then we will either need a modified aboot, or you can flash recovery over laf (download mode).
Code:
fastboot flash laf recovery.img
As for xposed, get g3tweaksbox from play store. It used to be a paid app but works flawlessly.

bichofelix said:
Our phone has no button combo to reach recovery.
You usually would be able to use the factory reset button combo and then cancel to recovery but all I get is hardware cursor mode. If someone else has achieved these results then disregard the below message. :
If you would like to reach recovery from power off, then we will either need a modified aboot, or you can flash recovery over laf (download mode).
Code:
fastboot flash laf recovery.img
As for xposed, get g3tweaksbox from play store. It used to be a paid app but works flawlessly.
Click to expand...
Click to collapse
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.

TWRP Backup
Question regarding making my first back up in TWRP. I know how to do it, just wanted input on a couple of thing so I have a good back up for if/when I mess something up. As of now, my back up I made has several apps (including system) disabled via @gatesjunior Debloater. I also have Xposed installed and Greenify and Gravity Box Modules installed.
Would I be better to put things back to stock and make a back up of the phone as it was when I bought (except root) or would a backup like I have to good enough to restore from.
Thanks again for all the help, especially on my stupid questions. LOL

lowender62 said:
Question regarding making my first back up in TWRP. I know how to do it, just wanted input on a couple of thing so I have a good back up for if/when I mess something up. As of now, my back up I made has several apps (including system) disabled via @gatesjunior Debloater. I also have Xposed installed and Greenify and Gravity Box Modules installed.
Would I be better to put things back to stock and make a back up of the phone as it was when I bought (except root) or would a backup like I have to good enough to restore from.
Thanks again for all the help, especially on my stupid questions. LOL
Click to expand...
Click to collapse
As long as what you backup is currently usable you should be fine.
Unjustified Dev said:
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.
Click to expand...
Click to collapse
Actually that did work. I was pressing vol+/-.
So to reiterate for others, to reach recovery you hold power & vol- until you see the lg logo, then release and immediately press and hold power again until factory reset comes up. Press yes then yes and bam.
Also, have you started a github for this device, yet?

bichofelix said:
As long as what you backup is currently usable you should be fine.
Actually that did work. I was pressing vol+/-.
So to reiterate for others, to reach recovery you hold power & vol- until you see the lg logo, then release and immediately press and hold power again until factory reset comes up. Press yes then yes and bam.
Also, have you started a github for this device, yet?
Click to expand...
Click to collapse
Thanks for the info on my backup. It does work fine and is they way I like it, so I will just keep it. On the reboot to recovery I tried that and got a different screen with mode off, mode on, etc but didn't see factory reset. Highlight was Mode Off and I moved up and selected mode on. Now when I try it boots up normally. Anyway I can set it back to Mode off like it was?
Thanks for your help!!

Unjustified Dev said:
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.
Click to expand...
Click to collapse
Yes! this was what I was looking for! Thank you.
Sent from my Z970 using Tapatalk

lowender62 said:
Thanks for the info on my backup. It does work fine and is they way I like it, so I will just keep it. On the reboot to recovery I tried that and got a different screen with mode off, mode on, etc but didn't see factory reset. Highlight was Mode Off and I moved up and selected mode on. Now when I try it boots up normally. Anyway I can set it back to Mode off like it was?
Thanks for your help!!
Click to expand...
Click to collapse
Same way you get into factory reset except instead of vol- you hold both volume buttons.

bichofelix said:
Also, have you started a github for this device, yet?
Click to expand...
Click to collapse
Only for recovery our device is e2nam I won't push a full device tree until I'm booting cyanogenmod
https://github.com/Teamregular

bichofelix said:
Same way you get into factory reset except instead of vol- you hold both volume buttons.
Click to expand...
Click to collapse
Ok got it and I think it may have just been me doing something wrong. Got home from work and tried it way you described a few posts back and I booted into TWRP. It's working Thanks