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)

Automatic boot into CWM

Sorry for my English.
I have a problem. I try to install some custom ROMs on my Asus Transformer TF101G, and it works fine, but now, when i try to boot system after install, CWM automatic start, and i can't boot the system. Someone know what is problem, and how i can solve it?

ivance95 said:
Sorry for my English.
I have a problem. I try to install some custom ROMs on my Asus Transformer TF101G, and it works fine, but now, when i try to boot system after install, CWM automatic start, and i can't boot the system. Someone know what is problem, and how i can solve it?
Click to expand...
Click to collapse
Did you install CWM recovery with ROM Manager?
If you did here's your problems/solutions
http://forum.xda-developers.com/showthread.php?t=1530337

I've also found that you don't have to flash a new recovery (it's recommended though)
Once it is booted up into recovery, plug it into your computer, open up a command prompt and change directory to where you have adb installed. For me, I type the command
cd c:/android-sdk/platform-tools
Once I type that and press enter I'm in the folder where adb is installed and I can access adb commands. Type in:
adb shell
then press enter, you should see a little # sign
Type in:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
and press enter.
Make sure you exit the shell by typing:
exit
then press enter.
Now you can reboot using adb by typing:
adb reboot
press enter.
This is important, do not reboot using the CWM "reboot device" otherwise you'll just boot up to CWM recovery again.
Forewarning though, if you don't boot a new recovery image, next time your device restarts it will boot loop into CWM recovery again, unless you redo these steps, or follow the thread the previous poster linked and install a new recovery image.

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!

How To Guide [TUTORIAL][ROOT] Install TWRP and Rooting Lenovo Phab Plus [PB1-770M] 5.0.2

How to root :
1. First, u must install USB drivers for lenovo phab plus and activated USB Debugging mode
LenovoUsbDriver_v1.0.12.zip
2. Copy Lenovo_PB1-770M_TWRP-2.8.7.7_by_SevenMaxs.zip into internal SD
Lenovo_PB1-770M_TWRP-2.8.7.7_by_SevenMaxs.zip
3. Install Temporary TWRP Recovery :
Connect You Device to PC >> Extract TWRP-2.8.7.7_PB1-770M.7z >> Open the .bat file and wait the processes until you entered TWRP.
TWRP-2.8.7.7_PB1-770M.7z
If you can't read the .bat text instruction, here is the translation :
echo 1. Press and hold the volume up button on the unit
echo 2. Press the Enter key on the keyboard of your PC
echo 3. after the appearance logitipa TWRP release the volume
4. After entered TWRP flash Lenovo_PB1-770M_TWRP-2.8.7.7_by_SevenMaxs.zip
5. Install superSU.zip u can search in XDA forum thread and your PHAB PLUS rooted permanently..
Credits to : sevenmaxs from lenovo russian forums
Do this at your own risk, dont forget to backup your system before doing this...

Xposed Install Lenovo Phab Plus [PB1-770M] 5.0.2 Pb1-770M_151111
If u want to install xposed
View Rovo89's Thread and download xposed-v79-sdk21-arm64
Don't forget to backup your data before flashing. :good: :good: :good: :good: :good:

Thank you. I was desperately searching the internet for it.
But I have a problem in flashing. It gives me an error: "E: can't mount/ sdcard". Any suggestions?
Thanks

Ahmedstony said:
Thank you. I was desperately searching the internet for it.
But I have a problem in flashing. It gives me an error: "E: can't mount/ sdcard". Any suggestions?
Thanks
Click to expand...
Click to collapse
When did the error occur? When u get into twrp the first time?

Yes, and I tried wiping cache and factory settings. Is the sdcard bricked? Any suggestions?
The phone is really great, but there're no custom roms or rooting options
Thanks

Errors when running .bat file?
Thanks for your post as I am keen to root my Phab Plus.
I followed your instructions however I received the following errors when I ran the .bat file:
rm: /sdcard/TWRP/theme: No such file or directory
and ....
< waiting for device >
target reported max download size of 268435456 bytes
sending 'recovery' (30862 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 4.254s
Can you please help me as I really want it to work? Thank you.

pdamaxxda said:
Thanks for your post as I am keen to root my Phab Plus.
I followed your instructions however I received the following errors when I ran the .bat file:
rm: /sdcard/TWRP/theme: No such file or directory
and ....
< waiting for device >
target reported max download size of 268435456 bytes
sending 'recovery' (30862 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 4.254s
Can you please help me as I really want it to work? Thank you.
Click to expand...
Click to collapse
Did u have activated usb debugging mode?

will it work with Vibe P1a42?
both having same chipset

Immanuelwijaya said:
Did u have activated usb debugging mode?
Click to expand...
Click to collapse
Yes I had usb debugging on

Android Version ??
pdamaxxda said:
Yes I had usb debugging on
Click to expand...
Click to collapse
did your android version same with me? maybe this is the problem...
i dont know whats wrong. because this method succeed in my device..
check this..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You can try it..
Jagadish-ravi said:
will it work with Vibe P1a42?
both having same chipset
Click to expand...
Click to collapse
i dont know it will work or no. but u can try it
if no error when u ran .bat file and u can enter TWRP after .bat proccess is done maybe it work withh Vibe P1a42.

Immanuelwijaya said:
did your android version same with me? maybe this is the problem...
i dont know whats wrong. because this method succeed in my device..
check this..
Click to expand...
Click to collapse
Yes I have the same model and version as you.
Actually tonight I received a system update to PB1-770M_S000169_151229_ROW however after updating it has the same problem when I try the .bat file.
I am wondering if my bootloader is locked. I bought it last month at the Singapore airport and perhaps their models are locked. How can I check if my bootloader is locked?

Jagadish-ravi said:
will it work with Vibe P1a42?
both having same chipset
Click to expand...
Click to collapse
pdamaxxda said:
Yes I have the same model and version as you.
Actually tonight I received a system update to PB1-770M_S000169_151229_ROW however after updating it has the same problem when I try the .bat file.
I am wondering if my bootloader is locked. I bought it last month at the Singapore airport and perhaps their models are locked. How can I check if my bootloader is locked?
Click to expand...
Click to collapse
U can try this :
1. Set up ADB and Fastboot on your computer. You can download the full Android SDK from here, or get the quick ADB and fastboot installer from here. For Mac or Linux OS, click here.
2. Install USB Drivers on your computer.
Installation Instructions
Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging.
Now connect your device to PC and accept the RSA Authentication prompt. Now open a command prompt or terminal window. Do this by holding shift key on your keyboard and right-click on an empty space and select “Open command window here” option to launch a command prompt window. Verify connectivity issuing the following command in cmd:
adb devices
Boot into the bootloader or fastboot mode. To do so, you can also issue the following code, while connected to the PC.
adb reboot bootloader
Now, as the Phab Plus isn’t recognized as a fastboot device, you will have to specify the OEM id. It is 0x2b4c meaning, any fastboot command must be suffixed with the following code.
-i 0x2b4c
Now this is important. We will proceed to unlock the bootloader. To do this, issue the following command. Choose yes on the device screen if prompted.
fastboot -i 0x2b4c oem get-device-info
If you see a message like (bootloader) Device unlocked: true, then reboot to bootloader
Bootloader on your device should now be unlocked. Reboot your device normally or issue the following command”
And start open the .bat file again :fingers-crossed:

Immanuelwijaya said:
U can try this :
1. Set up ADB and Fastboot on your computer. You can download the full Android SDK from here, or get the quick ADB and fastboot installer from here. For Mac or Linux OS, click here.
2. Install USB Drivers on your computer.
Installation Instructions
Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging.
Now connect your device to PC and accept the RSA Authentication prompt. Now open a command prompt or terminal window. Do this by holding shift key on your keyboard and right-click on an empty space and select “Open command window here” option to launch a command prompt window. Verify connectivity issuing the following command in cmd:
adb devices
Boot into the bootloader or fastboot mode. To do so, you can also issue the following code, while connected to the PC.
adb reboot bootloader
Now, as the Phab Plus isn’t recognized as a fastboot device, you will have to specify the OEM id. It is 0x2b4c meaning, any fastboot command must be suffixed with the following code.
-i 0x2b4c
Now this is important. We will proceed to unlock the bootloader. To do this, issue the following command. Choose yes on the device screen if prompted.
fastboot -i 0x2b4c oem get-device-info
If you see a message like (bootloader) Device unlocked: true, then reboot to bootloader
Bootloader on your device should now be unlocked. Reboot your device normally or issue the following command”
And start open the .bat file again :fingers-crossed:
Click to expand...
Click to collapse
Thanks so much for your help. I tried your suggestion on 2 separate computers (both W10) and got an error after typing; fastboot -i 0x2b4c oem get-device-info
However I tried a 3rd computer (running W8.1) and ran your .bat file again and it worked. I now have TWRP and root and I am now installing my favourite root apps such App Ops, Firewall and Hibernation Manager. I don't know why my 2 main computers had errors. I installed the correct ADB driver and used your files however there must have been some old drivers affecting the flash.
Anyway my new Phab Plus is now rooted and I very happy. Thanks so much for your assistance. I really appreciate it as it made me realize I should try another PC.

stock recovery
does anyone have a backup of the stock recovery?
system is nagging to install updates but TWRP cant apply OTA
cheers!

Trying on the PB1-770N_160701_PRC
Immanuelwijaya said:
I was sucessfuly rooting my lenovo Phab Plus.
This is work for lenovo Phab Plus running PB1-770M_150829 Software Version (Android 5.0.2)
How to root :
1. First, u must install USB drivers for lenovo phab plus and activated USB Debugging mode
LenovoUsbDriver_v1.0.12.zip
2. Copy Lenovo_PB1-770M_TWRP-2.8.7.7_by_SevenMaxs.zip into internal SD
Lenovo_PB1-770M_TWRP-2.8.7.7_by_SevenMaxs.zip
2. Install Temporary TWRP Recovery :
Connect You Device to PC >> Extract TWRP-2.8.7.7_PB1-770M.7z >> Open the .bat file and wait the processes
TWRP-2.8.7.7_PB1-770M.7z
3. After complete that. Enter recovery mode and flash Lenovo_PB1-770M_TWRP-2.8.7.7_by_SevenMaxs.zip
4. Install superSU.zip u can search in XDA forum thread and your PHAB PLUS rooted permanently..
Do this at your own risk, dont forget to backup your system.
Click to expand...
Click to collapse
This is the Chinese version. When I run your bat file, I get success message (at least that is how I do interpret it), but the characters displayed make the echoes unreadable for me (wonder whether it has to do with the phone being Chinese).
This what I see (snapshot from UltraEdit of your bat file - the saem I do see when I run the bat file):
echo.
tools\adb devices
echo.
echo “¤*«¥*¨¥ áâ*àëå ä*©«®¢ (¥á«¨ ®*¨ ¥áâì!)
echo.
tools\adb shell rm -r /sdcard/TWRP/theme
echo.
echo ¥à¥§*£à㧪* ¢ Bootloader
echo.
tools\adb reboot bootloader
echo.
echo “áâ**®¢ª* Recovery
echo.
tools\fastboot -i 0x17ef flash recovery img\twrp.img
echo.
echo „«ï §*¯ãáª* TWRP:
echo 1. §*¦¬¨â¥ ¨ 㤥ন¢*©â¥ ª*®¯ªã 㢥«¨ç¥*¨ï £à®¬ª®á⨠** ãáâனá⢥
echo 2. **¦¬¨â¥ ª«*¢¨èã Enter ** ª«*¢¨*âãॠ¢*襣® Š
echo 3. ¯®á«¥ ¯®ï¢«¥*¨ï «®£¨â¨¯* TWRP ®â¯ãáâ¨â¥ ª*®¯ªã £à®¬ª®áâ¨
pause > NUL
echo.
echo ¥à¥§*£à㧪* ¢ TWRP!
echo.
tools\fastboot reboot
echo.
echo „«ï ¢ë室* ¨§ ª®¬**¤*®© áâப¨ **¦¬¨â¥ «î¡ãî ª*®¯ªã.
pause > NUL
Any ideas why I can't read your echoes?
Could you copy them into this thread, so I can decipher what I am supposed to see?
Thanks
mrtvoj

mrtvoj said:
This is the Chinese version. When I run your bat file, I get success message (at least that is how I do interpret it), but the characters displayed make the echoes unreadable for me (wonder whether it has to do with the phone being Chinese).
This what I see (snapshot from UltraEdit of your bat file - the saem I do see when I run the bat file):
echo.
tools\adb devices
echo.
echo “¤*«¥*¨¥ áâ*àëå ä*©«®¢ (¥á«¨ ®*¨ ¥áâì!)
echo.
tools\adb shell rm -r /sdcard/TWRP/theme
echo.
echo ¥à¥§*£à㧪* ¢ Bootloader
echo.
tools\adb reboot bootloader
echo.
echo “áâ**®¢ª* Recovery
echo.
tools\fastboot -i 0x17ef flash recovery img\twrp.img
echo.
echo „«ï §*¯ãáª* TWRP:
echo 1. §*¦¬¨â¥ ¨ 㤥ন¢*©â¥ ª*®¯ªã 㢥«¨ç¥*¨ï £à®¬ª®á⨠** ãáâனá⢥
echo 2. **¦¬¨â¥ ª«*¢¨èã Enter ** ª«*¢¨*âãॠ¢*襣® Š
echo 3. ¯®á«¥ ¯®ï¢«¥*¨ï «®£¨â¨¯* TWRP ®â¯ãáâ¨â¥ ª*®¯ªã £à®¬ª®áâ¨
pause > NUL
echo.
echo ¥à¥§*£à㧪* ¢ TWRP!
echo.
tools\fastboot reboot
echo.
echo „«ï ¢ë室* ¨§ ª®¬**¤*®© áâப¨ **¦¬¨â¥ «î¡ãî ª*®¯ªã.
pause > NUL
Any ideas why I can't read your echoes?
Could you copy them into this thread, so I can decipher what I am supposed to see?
Thanks
mrtvoj
Click to expand...
Click to collapse
echo off
echo.
Determination echo device
echo.
tools \ adb devices
echo.
echo Delete old files (if they exist ! )
echo.
tools \ adb shell rm -r / sdcard / TWRP / theme
echo.
Restart echo in Bootloader
echo.
tools \ adb reboot bootloader
echo.
echo Installing Recovery
echo.
tools \ fastboot -i 0x17ef flash recovery img \ twrp.img
echo.
echo To start TWRP:
echo 1. Press and hold the volume up button on the unit
echo 2. Press the Enter key on the keyboard of your PC
echo 3. after the appearance logitipa TWRP release the volume
pause> NUL
echo.
Restart echo in TWRP!
echo.
tools \ fastboot reboot
echo.
echo To exit from the command line , press any button .
pause> NUL

It is so nice that some one rooted Lenovo Phab PLUS, i was waiting for so long to get this. Now i want to get to home as fast as i can, and check if it works
Only problem i just get OTA that was around 30MB, i don't know could i root this device or not now.
Does any one know how to make Lenovo phab plus only in landscape mode, with no additional program like rotation lock ? Because it need to boot before it can rotate screen

This is what i get, and no mater what i press, i can't instal update via recovery. it says footer is wrong

It helped thanks.
Immanuelwijaya said:
echo off
echo.
Determination echo device
echo.
tools \ adb devices
echo.
echo Delete old files (if they exist ! )
echo.
tools \ adb shell rm -r / sdcard / TWRP / theme
echo.
Restart echo in Bootloader
echo.
tools \ adb reboot bootloader
echo.
echo Installing Recovery
echo.
tools \ fastboot -i 0x17ef flash recovery img \ twrp.img
echo.
echo To start TWRP:
echo 1. Press and hold the volume up button on the unit
echo 2. Press the Enter key on the keyboard of your PC
echo 3. after the appearance logitipa TWRP release the volume
pause> NUL
echo.
Restart echo in TWRP!
echo.
tools \ fastboot reboot
echo.
echo To exit from the command line , press any button .
pause> NUL
Click to expand...
Click to collapse
It worked thanks a lot for quick response.
mrtvoj

How to root android device with factory disabled fastboot

Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.

Trunks614 said:
Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.
Click to expand...
Click to collapse
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.

Droidriven said:
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.
Click to expand...
Click to collapse
Is there possibly any app or other method that doesn't involve unlocking bootloader to root android nougat? Kingroot and kingoroot have been ineffective so far.

It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.

jwoegerbauer said:
It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.
Click to expand...
Click to collapse
I have a ported twrp ready to flash but I'm hesitant because I heard flashing a recovery while bootloader is locked could bork the device. Flashing twrp seems to be the only step now to root the phone, should I give it a try or avoid the risk?

My POV: TWRP isn't needed at all to root a device's Android.

jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
I needed the twrp to flash magisk. Is there some other method to root an android 7 device that doesn't involve twrp or unlocking bootloader?

I already told you a method: no more to say by me ...

jwoegerbauer said:
I told a method: no more to say by me ...
Click to expand...
Click to collapse
Please put me through or post the link to the method.

1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot

jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.

jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
Thank you. I tried this, unfortunately I got a "device not found" error even though "adb devices" did.

Droidriven said:
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.
Click to expand...
Click to collapse
I'm really confused ...
With no line in this thread it was mentioned / suggested / recommended to install a temporary root.
I kindly ask you to stop hopping into a thread and post off-topic content. TIA

@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.

jwoegerbauer said:
@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.
Click to expand...
Click to collapse
Will "apply update from SD card" work the same way?

jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
SuperSU is a deprecated project, that is why and how Magisk came to prominence. Anyone still using SuperSU is taking a real chance of compromising the security of their device at the system level. If SuperSU is used to gain root, it is highly recommended to convert to Magisk root after gaining root via SuperSU.

i have the same problem, zte A5 2019 fastboot disabled, by the way you can try mtk easy-su