Database Info

Elaboration on "how to root"

I think this thread can eventually turn into a sticky. I am going to ask all the common / newbie questions relating to the post by toast that is quoted below. Please contribute clear answers in the thread and I'll include them here at the top:
Q: What does RUU stand for?
A: ROM Upgrade Utility. It is used when a new ROM is available by your carrier. Don't use this since it will nullify your root.
Q: Where can I find photos of the root process?
A: Right Here, thanks to pingpongboss
Q: Where can I find the details and download locations of the custom roms available?
A: ???
Q: What is a custom recovery?
A: ???
Q: What is a recovery partition?
A: ????
Q: What things are we not able to do since we don't have the ability to
toastcfh said:
Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
Click to expand...
Click to collapse
A:
1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot.
2) ???
Q: What are all those code snipbits?
A: ??
Q: What is the point of the "recovery instructions"?
A: ??
toastcfh said:
HOW TO ROOT YOUR HTC EVO
DO NOT USE A RUU FROM SPRINT IF U WANNA MAINTAIN ROOT. WAIT FOR ME OR SOMEONE HERE TO MAKE A ROOT UPDATE.ZIP.
Major thanx for those who helped:
keishou (for the rooted build. without it none of this would be possible)
maejrep (for testing and modding a recovery for the EVO)
Flipz (for hosting the files)
Paul (for his recovery work on the desire and legend)
Amon_RA (for his recovery source on github)
WHAT THIS ROOT METHOD WILL DO:
- wipe all of your data so brace for that. backup or what not
- Allow you to flash custom roms
- Boot into a custom recovery
- Write to system, boot and recovery partitions through recovery
WHAT THIS ROOT METHOD SADLY WONT ENABLE YOU TO DO:
- Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
THINGS YOU WILL NEED:
download files below:
- PC36IMG.zip
- evorecovery
INSTUCTIONS FOR ROOTING:
- Put the PC36IMG.zip on the root of your sdcard
Code:
adb push PC36IMG.zip /sdcard
- Power off the phone
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
RECOVERY INSTRUCTIONS:
- Extract the evorecovery.zip to your desktop
- plug your phone into a usb port on your desktop
- In a shell:
Code:
adb reboot recovery
- this will reboot your EVO into recovery mode. at this point turn your attention to the directory u extracted the evorecovery.zip to.
Code:
For Windows XP ~~> Run recovery-windows.bat
For Vista and Windows 7 do it as Admin
- in a shell do:
Code:
For Linux ~~> ./recovery-linux.sh
- at this point turn your attention to the phone and navigate to create a Nandriod Backup. you can now flash custom roms, write, and make changes to system.
- to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard.
RECOVERY NAVIGATION:
-
Code:
Volume up/down moves through the list and Power selects.
RECOVERY SOURCE:
- http://github.com/jhansche/amonra_bootable_recovery/tree/supersonic
Code:
git clone git://github.com/jhansche/amonra_bootable_recovery.git
git checkout supersonic
Click to expand...
Click to collapse

Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html

pingpongboss said:
Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html
Click to expand...
Click to collapse
Phenomenal. Added to the original post. Could you please help with some of the other questions if possible?
Thanks

forumsid987 said:
Phenomenal. Added to the original post. Could you please help with some of the other questions if possible?
Thanks
Click to expand...
Click to collapse
Where to find custom roms: in this subforum xD
the rest of the questions I don't know how to answer correctly. Custom recovery lets you flash custom roms and make nandroid backups?

forumsid987 said:
Q: Where can I find the details and download locations of the custom roms available?
A: ???
Q: What is a custom recovery?
A: ???
Q: What is a recovery partition?
A: ????
Q: What things are we not able to do since we don't have the ability to
A:
1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot.
2) ???
Q: What are all those code snipbits?
A: ??
Q: What is the point of the "recovery instructions"?
A: ??
Click to expand...
Click to collapse
In order top to bottom:
As they become available you will find them in this forum. I will release a fresh rom for evo once I can test on my own device. It will be posted here, as well as at http://geekfor.me like always.
The green and black screen that you see that lets you flash a custom rom and create a nandroid backup, that is a custom recovery. The problem is because of NAND protection we can't currently flash that recovery and have it stick. That's why you have to run the bat/sh script each time, to load it manually.
It's the partition that the recovery resides on (the part of the internal storage memory).
Aside from not writing to system while booted (which was answered already) all that means is that instead of being able to boot directly in to the custom recovery view power button + home button or volume down, you need to run that script to get in to recovery. That's the only thing not being able to load the custom recovery means.
Code snipbits?
Um, because how else would you know how to get in to recovery so that you can flash a rom / create a backup / etc??

Is there any chance of fixing that recovery issue? Having to run the script to access it each time is going to get old fast.
-------------------------------------
Sent via the XDA Tapatalk App

In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?

maybe change the thread title to FAQ on how to root rather than elaboration, might attract more attention.
i was going to answer the questions which haven't been answered but flipzmode did a great job and the 1st post hasn't been updated. once the 1st post has been updated i'll check back and add more detailed if there is anything left to help with!
MrDSL said:
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?
Click to expand...
Click to collapse
good question, this would be good to add to the guide above.
the shell on windows 7 means the command prompt. never used win 7 but on win xp and vista, start->run->cmd
and it pops open the command prompt, navigate to where you extracted the zip file contents to, cd c:\evo-root\ . then run the .bat file by typing recovery-windows.bat .
on linux the terminal interface is called a shell because it actually brings up a shell binary, /bin/sh or /bin/bash . google these binaries for more detailed information. on windows the shell, is basically the command line which is now emulated in windows, where back in the days of DOS it was the actual system with windows loaded on top as a GUI...
sorry prob too much information!

Is there an alternative to reboot recovery that does not require ADB?

forceOnature said:
Is there an alternative to reboot recovery that does not require ADB?
Click to expand...
Click to collapse
an alternative way to reboot into recovery without using adb?
boot into the bootloader and select recovery? use the quick boot GUI to reboot directly into recovery? use connectbot and connect localhost, type reboot recovery?
you'll be needing ADB for a good chunk of the custom recovery process in order to load this Froyo ROM.
adb isnt too bad, just dive in and we're all here to help!

MrDSL said:
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?
Click to expand...
Click to collapse
Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator".
If you don't need to run as admin, you can do
Start -> type cmd -> Enter
and it'll come up.

adb driver for windows 7
http://depositfiles.com/en/files/yd61xorii

Anyone have some solid "Adb on Mac" instructions? LIke how to get it going on a mac... Just switched from PC... Thanks

a5ehren said:
Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator".
If you don't need to run as admin, you can do
Start -> type cmd -> Enter
and it'll come up.
Click to expand...
Click to collapse
I believe Start -> type cmd -> Shift+Enter will run as admin also.

JustinChase said:
I believe Start -> type cmd -> Shift+Enter will run as admin also.
Click to expand...
Click to collapse
Simply put im on a mac and a windows at the same time.. I cannot get the bat to run correctly I see it run but it looks like a fc and then it closes.. On the mac I get asked for this..
sudo: ./adb-mac: command not found
sudo: ./adb-mac: command not found
new-host:~ GodDriven$ sudo: ./adb-mac: command not found
Please help?

Bootloop after Trickdroid tweaks

Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer

Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either

Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.

j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.

Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked

Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"

rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed

Sorry,
I posted before your edit showed up--

Glad to hear.

steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.

[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted

For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.

So if I got this right if I have busybox already I only have to do is step 7.

Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium

Step 4, a quicker way: adb shell su , get you into shell as root right away

AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.

Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?

AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.

Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.

AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.

Updated with a link to another good tutorial about pushing ROMs to the phone

Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.

Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.

AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!

AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium

$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps

Dude add S3 stock recovery please.

Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.

AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.

Pantech Element TWRP Recovery and Stock Rooted Roms

This is TWRP recovery and Stock rooted roms for the ICS firmware on the tablet.
These will only work if you currently have ICS running on your tablet. If you still have honeycomb then do the upgrade first.
Nothing was added or removed from the stock roms besides root and busybox.
Only bug with TWRP is that you can't mount sdcard in recovery. Just use adb push.
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Thanks:
attn1 - gave me some help since I am new to pantech devices
Dees_troy - for TWRP code obviously
Tassadar - for his rotation code for twrp. Without this it wouldn't have been possible

Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
Downloads

just in case i need another

Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)

mavblues said:
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
Click to expand...
Click to collapse
On the computer. your command prompt should be at wherever you put twrprecovery.img file is. So for example you put twrprecovery.img at the root of c:, your command prompt should read c:/ .....
Sent from my M7 using xda premium

Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA

mavblues said:
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
Click to expand...
Click to collapse
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium

jmztaylor said:
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Got it - working great!

I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?

dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium

dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Did you check "USB debugging" on the tablet?
Also, I had to set USB connection on the tablet to the last choice "PC Data Mode".
Hope it helps.

jmztaylor said:
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4

dagadu said:
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
Click to expand...
Click to collapse
Anytime when the tablet is not plugged in. This will make the computer automatically install anything needed for the tablet and you won't have issues with fastboot or adb anymore
Sent from my M7 using xda premium

jmztaylor said:
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Click to expand...
Click to collapse
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.

1806 said:
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
Click to expand...
Click to collapse
Actually it's similar steps; however, yours is more like 1-click root
Anyway, I tried everything all above, but it didn't solve my problem, then I found the solution from other website
I just want to share in case others are stuck in fastboot mode like me:
1. When your tablet screen is on fastboot mode (white), go to device manager on your pc
2. Right click on Android > Update driver
3. Click on Browse driver
4. Choose Let me pick manually from my pc list
5. Choose Android phone and pick the first list there. It should be "Android ADB..."
6. Install and fastboot continued
if you can't find Android ADB from your pc list, then you should unplug device then install PC Suite.
here's the old tuts: youtube com/watch?v=UHRonVzBMsI
Hopefully it helps others and thank you very much for all your help!

Delete!

Finally! and a question
Finally a recovery for the element! Rhanks to the OP. Now I am less afraid to tinker with my tablet.
Question: The most important thing right now that I'd like to do is move the folder /data/data from the internal storage, to the internal SD card. This is stopping me from using Google Magazines and Google music, since their data is being stored there, and it shares space with actual applications. 1GB is not that much space for APPS, Dalvik Cache and APPs' data when you add magazines, and when google starts caching Music and Chrome data there. I currently only have 300MB left before I install Music and magazines. And that is AFTER I've used app2sd on all apps that can be moved. How do I do this?
I have tried simply creating a Link using "ln - s /mnt/sdcard/data /data/data" once I copied/moved the contents of the directory, which sort of works initially, but it will not work after a reboot. It actually stops my tablet from booting. (again, thanks to the OP for the recovery).
right now, I am just doing an "ln" on the specific folder inside the /data/data folder, but it acts weird when I use Titanium Backup to restore data
-> Android noob <-

Installing TWRP went smooth as silk. With twrprecovery.zip on you micro sdcard and Element connected with usb cable and USB debuuging checked 1.Just copy twrprecovery.img into your sdk folder/ platform-tools and also have a copy of cmd.exe from windows in the platform-tools folder. 2. Start cmd.exe and type or copy & paste command reboot bootloader 3. Then on white screen(fastboot) type or paste command fastboot boot twrprecovery.img 4. When you boot into TWRP install twrprecovery.zip.....As you rebbot system TWRP should ask if you want Supersu installed and swipe to install. Once rebooted install supersu from the Play store and open Supersu to update SU file all should be good
Thanks for the info and files. I know I'm a little late on this Tablet but picked it up cheap and with ATT 4G it goes along with my devices. The orginial owner hadn't even installed ICS and she wasn't even aware of an update. She now owns an Apple :laugh::laugh:device LOL

I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?

marcustaz said:
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
Click to expand...
Click to collapse
Yes good deal, got mine last month on Craigslist for $70.00 and works really well. The owner hadn't even updated to 4.0 or even knew how. It is a good tablet and have rooted it. I think its development is pretty well dead as not many sold. Only thing bad about it is the Element reads 2nd partition instead of 1st as most android devices do, so harder to use link2sd or folder mount as they both use 2nd partition.
Sent from my PantechP4100 using XDA Premium 4 mobile app

[Resolved] [Q] [UNBRICK] Chuwi vi8 stuck on boot, build.prop issue!

This is my first post here, i never registered and posted so far because im aware that my english sucks and my skill are really poor.
But now this is my last chance to recover my new tablet (2 days lifetime!)
I will try to explain the problem in the best way possible.
I have a Chuwi vi8 dual boot, and i needed root access to fix the sd card write restriction of 4.4.
After some search i was able to root it. Then i screwed up when i edited the build.prop to change the dpi from 160 to 200. I have touched the permission not knowing it would screw up the boot.
Now my chuwi is stuck on the android boot logo.
Im able to enter the recovery mode (power + volume -)
In the recovery menu (stock recovery menu) i have the following option:
reboot droidboot
reboot
recovery
power off
and this message in the lower part of the screen:
FASTBOOT INIT...
E:installer device ignored
E:failed to mount device '/dev/block/sda1 as installer partition using fs_type..
E:installed device ignored
E:installed device ignored
E:No valid installer medium found
FASTBOOT CMD waiting...
Then i enter recovery:
reboot system now:
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from internal storage
offcourse wiping everything doesnt solve the problem as the issue is in build.prop
then i try to use ADB:
i have the driver of this device installed in windows, im sure that USB debug was on on the device.
I tested various version of ADB from my pc but no one was able to let me use the vairous command (pull,push etc etc)
Im only able to "ADB devices" and see the name of the device + sideload, any other command will result in error: closed
Im trying to find someone whit a working build.prop, but while doing that i really like to try to pull,edit and push back mine.
I dont even know if there is a way to manual boot windows and try to do something from that side because i dont know if there is a manual way to boot into that.
Any help is appreciated, and again please forgive me if my first post is like this.
Thank you

Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!

arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
Hi,
Sorry for bothering, I have the same tablet, and would like to root it. Can you help me in this with a link to the right method or something? The reason is the same, to use the sdcard normally, and maybe ntfs.
Thank you in advance!

asteck said:
Hi,
Sorry for bothering, I have the same tablet, and would like to root it. Can you help me in this with a link to the right method or something? The reason is the same, to use the sdcard normally, and maybe ntfs.
Thank you in advance!
Click to expand...
Click to collapse
Hi,
Finally no need for help, made it with KingoRoot.

asteck said:
Hi,
Finally no need for help, made it with KingoRoot.
Click to expand...
Click to collapse
Hey there
I am trying to root my chuwi vi8 dual boot too
Could use some help
I tried KingoRoot but it does not work
Please help me

arkh01droid said:
This is my first post here, i never registered and posted so far because im aware that my english sucks and my skill are really poor.
But now this is my last chance to recover my new tablet (2 days lifetime!)
I will try to explain the problem in the best way possible.
I have a Chuwi vi8 dual boot, and i needed root access to fix the sd card write restriction of 4.4.
After some search i was able to root it. Then i screwed up when i edited the build.prop to change the dpi from 160 to 200. I have touched the permission not knowing it would screw up the boot.
Now my chuwi is stuck on the android boot logo.
Im able to enter the recovery mode (power + volume -)
In the recovery menu (stock recovery menu) i have the following option:
reboot droidboot
reboot
recovery
power off
and this message in the lower part of the screen:
FASTBOOT INIT...
E:installer device ignored
E:failed to mount device '/dev/block/sda1 as installer partition using fs_type..
E:installed device ignored
E:installed device ignored
E:No valid installer medium found
FASTBOOT CMD waiting...
Then i enter recovery:
reboot system now:
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from internal storage
offcourse wiping everything doesnt solve the problem as the issue is in build.prop
then i try to use ADB:
i have the driver of this device installed in windows, im sure that USB debug was on on the device.
I tested various version of ADB from my pc but no one was able to let me use the vairous command (pull,push etc etc)
Im only able to "ADB devices" and see the name of the device + sideload, any other command will result in error: closed
Im trying to find someone whit a working build.prop, but while doing that i really like to try to pull,edit and push back mine.
I dont even know if there is a way to manual boot windows and try to do something from that side because i dont know if there is a manual way to boot into that.
Any help is appreciated, and again please forgive me if my first post is like this.
Thank you
Click to expand...
Click to collapse
Hi man could you please tell me how to root this device
Does shifting the dpi make a difference?
Thanks in advance

[email protected] said:
Hi man could you please tell me how to root this device
Does shifting the dpi make a difference?
Thanks in advance
Click to expand...
Click to collapse
Changing DPI is for display scaling, but on your device hard editing the build.prop makes the device not booting!
Make sure to enable "USB debugging" before you try to root your device.
If Kingo still fails, you can try iROOT (former VRoot)

LS.xD said:
Changing DPI is for display scaling, but on your device hard editing the build.prop makes the device not booting!
Make sure to enable "USB debugging" before you try to root your device.
If Kingo still fails, you can try
Click to expand...
Click to collapse
Thanks a lot
Iroot did the trick
But I am unable to use the microsdcard tried link2sd
Partitioned the card for linking but link2sd cannot mount the ext3 partition

[email protected] said:
Thanks a lot
Iroot did the trick
But I am unable to use the microsdcard tried link2sd
Partitioned the card for linking but link2sd cannot mount the ext3 partition
Click to expand...
Click to collapse
Make sure that both partitions are "primary" 1. Partition "fat32" 2. Partition ext4 (MUST BE PRIMARY NOT LOGICAL!!!)

Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL ?
Ok this is what've done to my vi8 tablet [emoji111]
A. Root
1. Install pdanet+ from pdanet.co, when it asking to choose phone manufacturer
choose "Others" then it will waiting your tablet to connect
2. Before you connect the tablet make sure that you have the developer menu enabled so you can make usb debugging mode enabled, then connect your tablet.. Wait until the device installation finish, then it will asking to choose after installation... Choose usb mode ignore other option then press finish, then you'll see that your device connected the taskbar
3. Install KingoRoot, launch it, wait until the KingoRoot appear on the tablet, on the computer choose remove root, wait till it succeeded
4. Install iRoot (VRoot), launch it, then root it... On the tablet you'll see a blue lion logo written Superuser
5. If you don't mind with Chinese root app then rooting finish on step 4, but if you do you can replace the root using another root app, in my case I use SuperSU from chainfire.
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL ?
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
C. Link2SD
1. Prepare the micro SD partition (I'm using mini tool partition), 1st Partition is FAT32 (Primary), 2nd Partition is ext4 (Primary and make it active)
2. Download/Install Link2SD from play store
3. Choose ext4 wait until it success and ask for reboot, then reboot.
Credit goes to... I forgot [emoji33]
Sorry for my bad English [emoji1] [emoji1] [emoji1]

resize patition
Hi is it possible resize android partition and use more space on windows partition? is it possible installing only windows or only android?
thanks

Possible...

Can anyone please provide me a copy of the recovery.img file for the Android partition?

god damn it
DhaniBaho said:
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL
Ok this is what've done to my vi8 tablet [emoji111]
A. Root
1. Install pdanet+ from pdanet.co, when it asking to choose phone manufacturer
choose "Others" then it will waiting your tablet to connect
2. Before you connect the tablet make sure that you have the developer menu enabled so you can make usb debugging mode enabled, then connect your tablet.. Wait until the device installation finish, then it will asking to choose after installation... Choose usb mode ignore other option then press finish, then you'll see that your device connected the taskbar
3. Install KingoRoot, launch it, wait until the KingoRoot appear on the tablet, on the computer choose remove root, wait till it succeeded
4. Install iRoot (VRoot), launch it, then root it... On the tablet you'll see a blue lion logo written Superuser
5. If you don't mind with Chinese root app then rooting finish on step 4, but if you do you can replace the root using another root app, in my case I use SuperSU from chainfire.
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
C. Link2SD
1. Prepare the micro SD partition (I'm using mini tool partition), 1st Partition is FAT32 (Primary), 2nd Partition is ext4 (Primary and make it active)
2. Download/Install Link2SD from play store
3. Choose ext4 wait until it success and ask for reboot, then reboot.
Credit goes to... I forgot [emoji33]
Sorry for my bad English [emoji1] [emoji1] [emoji1]
Click to expand...
Click to collapse
ok my dear friend, I change the app_process to app_process.xposed-bak and then no more root, so no more rename, so have a brick, can u help me please?
---------- Post added at 01:25 AM ---------- Previous post was at 01:09 AM ----------
arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
frieeeeeend please tell me the tool to do that, please please !!!!!!

gomexpeed said:
ok my dear friend, I change the app_process to app_process.xposed-bak and then no more root, so no more rename, so have a brick, can u help me please?
---------- Post added at 01:25 AM ---------- Previous post was at 01:09 AM ----------
frieeeeeend please tell me the tool to do that, please please !!!!!!
Click to expand...
Click to collapse
Hi,
There is several tool for this, personaly I'm using this one:
Paragon ExtFS for Windows
It is free for personal usage.

I wan to buy this tablet and install xposed and xmultiwindow on it... does it work? is it easy to factory reset the android rom if something goes wrong?

DhaniBaho said:
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
Sorry for my bad English [emoji1] [emoji1] [emoji1]
Click to expand...
Click to collapse
Hi, looking at the above and had a question. That seems like a longer process than on "normal" devices, ie the Terminal Emulator steps. What is the purpose of those steps? Does this mean I will have to repeat this any time I upgrade Xposed? I am curious as to why it differs from a normal install on a rooted device.

arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
what did you install in windows to mount and browse android partition. Thanks

bindassever said:
what did you install in windows to mount and browse android partition. Thanks
Click to expand...
Click to collapse
Try this... http://www.paragon-software.com/home/extfs-windows/
Sent using D-Vi8™

hi
I am moderator of a Chinese tablet french site http://tablette-chinoise.net/chuwi-serie-vi-f240
If you have problems with this tablet and want to help no worries
I perceives that there is still a new bios and also another version of android in Vi8 Dual OS since 201504
Let me explain how I came to realize
s / n q32g22150304xxx
bios D86JUBNR01
you can not install on GooglePlay, or manually
Foursquare Google+ and many other applications
s / n q32g22150401xxx
bios D86JHBNR01
Foursquare Google+ OK !
here installation possible also the splash screen before botanimation android was different
but the person who has met with problems with the windows has to reinstall Android repartitioning
My question is the following
Which link the new bios D86JHBNR01 and new ANDROID !!!
Who has the upper android version 20150123
Check your build.prop please
keep me informed