Related
Hello!
I recently purchased a HTC Desire HD through a carrier in Australia after being a nokia dumbphone owner for my "connected life". I have done some reading into the Custom ROM scene and I am loving the potential benefits and modifications that are possible with them, however being new to Android, new to Smartphones and new to Custom Roms I am to say the least a little confused.
I decided this carrier added bloatware just has to go and after a little reading I like the idea of LeeDrOiD HD v1.2.
I have attempted to follow the instructions in the Leedroid HD thread.
http://forum.xda-developers.com/showthread.php?t=842802
Which tells me i Need to flash.
http://forum.xda-developers.com/showthread.php?t=842819
Which in turn tells "You will need the ENG HBOOT installed on your device to flash this recovery!"
and of course I could not find any details on what ENG HBOOT is let alone how to install it.
How deep does the rabbit hole go Alice? The multiple tears are becoming confusing and complicated and I am wondering if this is just a LeeDroid thing, or are these steps necessary for all custom roms? Or just the Desire HD. I am fairly confident with the safety of replacing a rom but the more steps by more people are adding uncertainty in the safety of the whole procedure and of course raising the probability of an under informed and maybe slightly reckless newby to brick a perfectly acceptable phone.
Is anyone able to reccomend a resource to better acquaint a Newby with this new territory? Is thier a more comprehensive guide to installing LeeDroid or "Rom-ing" an android phone.
Hi,
Give me a few minutes to pull together a few guides for you.
This Guide with Video is very helpful at performing all the little tasks that allow you to flash custom ROMs.
In short the ENG HBOOT allows the flashing of an unsigned recovery "Clockwork Mod", which then allows you to flash custom ROMs. Flashing the ENG HBOOT is a one time process, once you have done it there is no need to do it again.
Just a few questions,
1). Do you have a Stock HTC Unbranded & Unlocked ROM or a Carrier Branded ROM?
2). Have you rooted you DHD yet?
This is the way I personally went about the whole process, its a guide that zexbig posted and can be found HERE
Summary:
1) Download Paul's Visionary+ tool (I have used version r12) (google removed this app from market) so You will have to download it from Paul's website.
This tools enables root and removes new HTC protection.
2) Install engineering version of HBOOT to get S-Off (HTC bootloader, something like BIOS for Your PC)
This step is optional and it's not required in order to flash custom ROM's on Your DHD but gives You more freedom with Your device.
3) Install custom recovery image (recovery is special program which is invoked from HBOOT
in order to flash ROM onto Your device.
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/ht...ne-click-root/ or download it from here http://forum.xda-developers.com/atta...3&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Time for next step!
2) Install engineering version of HBOOT to get S-Off
2.1) Download sfjuocekr DHD script for flashing HBOOT from here
http://forum.xda-developers.com/showthread.php?t=835746
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory.
(I have run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
2.3) Run Terminal Emulator
2.4) Type su
2.5) Type "sh /sdcard/DHD/check
(Please be aware that You have to type "sh" in front of command)
2.6) If everything went OK type
sh /sdcard/DHD/backup
2.7) If this also went OK proceed with
sh /sdcard/DHD/hboot
This command will install engineering hboot which have S-Off turned off.
3) Install custom recovery image
3.1) Since ROM manager now officially support's Desire HD, we will use it to download and install custom clockwork image.
3.2) Run android market app on Your DHD and download and install ROM Manager app from market.
3.3) Download and install ROM manager.
3.4) Run ROM manager and select first option (Flash ClockWorkMod Recovery).
3.5) Wait until ROM Manager say's that installation went successfully (Current version of ClockWorkMod is 2.5.1.3)
3.6) After installation tap in Rom manager option Reboot into Recovery to test that everything went well.
3.7) DHD should reboot in clockwork recovery manager.
Click to expand...
Click to collapse
-Visionary is now v14+, not 12 as posted.
If you have any problems, just let us know.
Quick Response thanks!
It is unfortunatly a Carrier Branded rom. Full of widgets that are just links to webpages. What is even worse is I bought my phone through a company who leases lines off the carrier so because I am technically not with the carrier I can't use their aps even if i wanted to.
I believe I have temp rooted it so far. I have downloaded VISIONary +
Epic.. Thank you kindly. I am in the process.
I don't understand why carriers have to ruin the whole "Android Experience" by bundling awful apps that nobody wants, otherwise they would of downloaded them themselves.
The last guide I posted is the one I used. Once you have followed all of the steps then your in a position to flash a custom ROM. If you are planning to overclock or underclock then you will also need to find a suitable "Kernel" to flash with your ROM. Most ROMs do come complete with a custom kernel but that may not be the best for your particular needs.
Once bit of advice. Always, always a backup of your ROM before you flash anything else.
Flashing custom ROMs is easy once the above steps are complete.
1). Download your chosen ROM.
1a). Optional Download your chosen Kernel.
2). Transfer ROM (+ Kernel) to your SD Card, place in the root of the card.
3). Boot into Recovery. Power off (Ensure HTC Fast Boot is disabled), Power on whilst holding VOL DOWN, using volume keys select Recovery, press power to enter.
4). Create Backup, backup and restore > backup.
5). Wipe All Data including cache
6). Install .zip from SD Card, Select the correct ROM zip and confirm.
7). Optional, repeat with Kernel, if necessary.
8). Reboot.
9). Bask in glory, you have conquered your smartphone.
Again, if you want more info feel free to ask. We all had to learn once, or twice.
For Clarification on HBOOT loading.
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory.
(I have run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
I do want to be viewing the Android device as a disk drive?
Secondly Do I create a folder on the SD card in the root directory called DHD and then drop the 3 files contained in the Zip file into that folder?
Example
Root Directory
>.data
>Alarms
>Android
>bugreports
>DCIM
>DHD --Newly created folder
>>DHD-dumb --dragged and dropped
>>DHD-smart --dragged and dropped
RTFM.txt --dragged and dropped
>downloads
etc..
Yes you do want to view it as a disk drive.
You are also correct with the folders.
SDCard/DHD/ - place files here -
Ok my description failed.
Instead of the folders listed above
">>DHD-dumb --dragged and dropped
>>DHD-smart --dragged and dropped
RTFM.txt --dragged and dropped"
should I be taking the contents of (smart or dumb?) and placing that in the DHD created directory?
obviously the commands in the terminal dont correspond to having the files in a sub folder. I appologise for you having to answer obvious questions however I am a little weary of bricking.
I'd rather you post a question and get it answered before you post a problem and have an expensive paperweight.
Take the "DHD-smart" folder from wherever you extracted it, place that on your SD Card, then rename that folder to just "DHD".
Excellent. All Is working as planned. I'm in the process of D/L ing Leedroid rom.
Thanks for your help again.
I'll post back once I have things up and rolling.
No problem at all.
Just remember to make a backup from within "Recovery", it will save you one day.
I appologise I forgot to Post back.
Everything is running sweetly now, absolutley no bugs with the Root or new LeeRoid rom.
Thanks again for your help.
Daft Templar said:
I appologise I forgot to Post back.
Everything is running sweetly now, absolutley no bugs with the Root or new LeeRoid rom.
Thanks again for your help.
Click to expand...
Click to collapse
Welcome to the ranks of Android hackers. Health warning: flashing is addictive.
Sent from my performance enhanced Desire HD.
Yes it is
Sent from my Desire HD using XDA App
I do not know why you say this...
MOD EDIT: Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
***EDIT***
I have also tried on a HK 3g xoom (which shows MZ601 in MTP but MZ602 in fastboot). It works without any problem, and internal storage preserved untouched.
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
eddielo said:
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
Click to expand...
Click to collapse
How do you flash cwm if your device if locked? Also the purpose of the rooted boot.img is to allow you to mount your device for adb commands.
Sent from my PG86100 using Tapatalk
yeah no offense but this sounds a little sketch... I see you make a quote at the bottom asking people to report success if they try... I personally would not try this.
Unlocking and rooting is really not that hard and not very time consuming using current methods
Of course, for installing CWM, you have to unlock your device by using "fastboot oem unlock", but that will not brick your device anyway.
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Also, for the current rooting methods, it is not 100% work on some device (like the HK 3g version, which reported missing of internal storage after rooting with currently available method), I would like to see if this work on that.
Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
eddielo said:
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Click to expand...
Click to collapse
I think you missed my point. Rooted boot.img isn't used for rooting. Its used for adb commands like adb remount. Say i want to adb push a file to my xoom, ls a directory on my xoom, or adb rename system files. Those are all reason you need the rooted boot.img.
Sorry, this is not a rooting method. All what this is doing is flashing su, busybox and Superuser.apk.
There is more to rooting a device than this. You also need an insecure boot image.
I am sorry if I do not catch the real meaning of rooting a device.
What I think of rooting is to let my device, starting from everything stock, untouched, to a state that applications that need root, like Titanium backup or root explorer, works without problem.
I have tried on my two devices with this method, titanium backup works perfectly, root explorer can remount the system partition to rw and can successfully copy files and delete files from that.
The insecure boot.img image, as far as I know, provides everyone to use "adb remount" and make changes to the system directory. But my method do not need adb in copying the binaries and chmod them. You may call it flashing, but after that, su works without problem.
Please, try it first. If you think it is not a method of rooting, I am sorry about that.
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
roughneckboren said:
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Rooting has nothing to do with installing a rom. To install a rom, you just need to unlock and fastboot flash CWM. This guide in noway helps you flash a rom.
alias_neo said:
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
Click to expand...
Click to collapse
Without an rooted boot.img your recovery will get wiped out every time you boot the OS.
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
silvinoa said:
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
Click to expand...
Click to collapse
Yes and NO...
Yes this method will allow you to run titanium backup. But to use this method you have to unlock, which erases everything.
Forum:
If this specific question is in another thread, please forgive me and redirect me.
If not, any instruction would be greatly appreciated.
Equipment:
Visual Land, Prestige 7
Model # VL - 107
ICS 4.0.3
Baseband 1.0
Kernel 3.0.8+
Build # 86F5-D1-H1-MO1-1718.20120327
Objective:
To create a backup/recovery img/dump of the existing stock ROM, without having to add "clockwork", "cynogen", etc...
Software on Hand:
Windows 7
Livesuit 1.09
Virtualbox
Ubuntu via Virtual Machine
Please detail everything and speak to me as if I were a little child...
Thanks in advance!
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Can this be done with ADB?
ruscan.calin said:
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Click to expand...
Click to collapse
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
gth826a said:
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
Click to expand...
Click to collapse
I understand now this is a tablet so it's common problem for some
well you have to find a way to root device to get access to system files then use a rom dumping tool just take a look here or here
nobody can tell you for sure how to do that this is device specific I do not know to much about that particular tablet just try
I just got this tablet today, and it's rooted out of the box.
Not sure if that helps you, but I wanted to contribute if I could.
[signature]
Recovery for Galaxy Ace 2 - i8160
Hi,
Any chance of a simple recovery for the Galaxy Ace2 i8160 ?
VL107 Update Down To 4.0.3/4.0.4
Hello,
I've been trying to figure out how to change my VL-107's OS, and a Recognized Contributor pointed me to this thread.
I've downloaded LiveSuit, but I can't figure out how to make it work. If at all possible, I need two things: an .img file for 4.0.3 or 4.0.4, and instructions on how to apply this update via command prompt or a program that utilizes command prompt.
I have Windows 8.1, my VL-107 (Visual Land Prestige 7), and LiveSuit (which I'd really rather not use).
The only experience I have in flashing involved using command prompt, and I'm much more comfortable doing this than relying on a program to do everything "behind the scenes". Otherwise, I would also be willing to put an .img file on my tablet's "SD card" and apply the update through Recovery mode.
Okay, ive been doing my research, and I lasted aprox. 4-5 days and its sadly to know but this phone (HTC Evo Design 4G / Kingdom / Hero S) doesnt have that much of fame. But I was crazy trying and trying alot of methods trying to root my phone, but just couldnt. I was about to give up, until I found a Guide, and made it possible for me to root the phone, so I decided to share this guide to you guys, to who ever has a HTC Evo Design 4G / Kingdom / Hero S. Credits go to LOLINTERNET who wrote this guide. :good:
Ok, here we go. :laugh:
In order to root your Evo Design you'll need to unlock your bootloader, flash recovery, flash su binary, and install superuser and busybox. In this guide I will try to explain these steps as simply as I can. My goal is for it to be thorough enough that anyone that reads it can root their phone and enjoy the full benefits of this nifty little phone.
First and foremost, you will need to install the Java SE Development Kit. You won't use this directly in any way, but you need it in order to install the Android SDK.
Click Here To Download SDK
After installing the Java JDK, you will have to install the Android SDK which contains two tools that are essential to gaining root. They are adb (Android Debug Bridge) and fastboot. These tools are used to send files to your phone from a Windows command prompt. You will need these tools to unlock your bootloader and flash recovery.
Click Here to Download Android SDK
Instructions on installing the SDK
How to add packages to the SDK
Once you have the Java JDK and the Android SDK installed you will need to install the proper drivers for your phone. This one is pretty straightforward and necessary for your phone to be recognized while plugged into your computer. After you have the HTC drivers installed you can begin the fun parts, but first you will need a few things. :good:
HTC Drivers CREDITS TO: CNexus
You will need a recovery.img. 2fast4u88's unofficial ClockWorkMod Recovery version 5.0.2.7 and 5.0.2.8 are the only two recoveries I have used since I got my Evo Design. Many thanks to him for putting in so much work to get this device where it is today.
Download Recovery
Also, you'll need su binary version 3.0.3.2 efghi. This is the actual file that will root your device. It is a flashable .zip file that you save to your sdcard and flash in recovery. You'll be amazed at how easy this step is.
Download for su binary version 3.0.3.2 efghi
Download for su binary version 3.0.7 efghi
3.0.3.2 binary is for Gingerbread and 3.0.7 is for ICS
The superuser app is like the control center for apps that request root permissions after you're finally rooted. You will need to install this app and then Busybox, both of which can be found in the Google Play Store. After installing the Busybox app you will need to actually install busybox. The app itself is basically an installer for Linux applets that are required by root apps such as Titanium Backup and Root Explorer among many others.
Now that you have a basic overview of what it is you will be doing and the files need to do it, the only thing left is to actually perform these steps and root your device. So, lets do this!
1. Unlock your bootloader at htcdev.com. You will need to sign up and you will be warned that unlocking your bootloader will void your warranty. Once you've followed all instructions at the website an unlock token will be emailed to you. DO NOT DELETE THIS FILE. You can place it in the platform tools folder of the Android SDK and use fastboot in command prompt to relock and unlock your bootloader whenever you like. Also, anytime you unlock your bootloader all data will be wiped so be sure you sync all your contacts and backup other information first before performing this step.
2. After unlocking your bootloader you will need to flash a recovery.img. The manual way to flash recovery is to place the downloaded recovery.img for 2fast4u88's unofficial ClockWorkMod recovery port of version 5.0.2.7 in the platform-tools folder of the Android SDK. Power down your phone but be sure that Fast Boot in Power under the settings menu is unchecked or it will just reboot normally instead of into bootloader (also called hboot) like you want. After it's been powered down for a minute or two, press and hold Volume down then press and hold the power button. When the white HTC splash screen appears you can let go. Scroll down with the volume down button and select fastboot by pressing power. Plug your phone into your computer and open a command prompt, then run these commands without quotations.
"cd C:\android\platform-tools" (This is where adb and fastboot live. It may be different for you depending on where you installed the SDK. I always suggest installing it to the root of your C: drive.)
"fastboot flash recovery recovery.img"
Should only take a few seconds, then you have yourself a recovery partition and you can proceed to the next step after rebooting. Yay!
3. Next, we're going to flash the su binary in recovery. First, you'll need to place it on your sdcard. Doesn't matter where exactly just as long as you can find it. I would suggest the root of your sd just to make things easier on yourself. After you have the su binary zip saved to your sdcard power off your phone and boot into hboot. Now, I can't remember which, but either hboot or fastboot will have an option to boot into Recovery. Once you're booted into recovery, select "install zip from sdcard," then "choose zip from sdcard." Scroll down and find the su binary then select it. Pressing the Up Vol button will take you directly to the end if you don't want to scroll all the way through. After selecting the su binary zip select "yes" to flash. It's a small file, so it won't take long. When it's done select "reboot to system" and we'll move on to the next step because you just rooted your phone.
4. But, you're not done yet. You need to install the superuser app and the busybox app in that order. This is the easy part because both apps are free in the Play Store. Install Superuser, then Busybox. You shouldn't have to interact with the Superuser app, but if you want to set an automatic response to apps that request root you can open it and go to Preferences. Scroll down and you should see a few options. I have mine set to automatically grant su permission to apps that request it because I have no reason not to lol. I also unchecked the option to receive a notification every time an app is granted root permission because that junk just gets annoying. Next, after you install the Busybox app, you'll need to actually install Busybox. The app is merely an installer for the actual Busybox applets that govern root apps. The app should open automatically after you install it. You should see it in your notification bar. Open it up and follow the prompts. When you're done, reboot your phone.
5. Check If you have rooted your phone successfully, download Root Checker on Play Store.
6. Congratulations! You should now have a rooted Evo Design 4G. Enjoy. I hope this guide is both complete and comprehensive enough that everyone can enjoy the benefits of having a rooted device, but if I've missed something or if you have any questions whatsoever, please post them here and I will do my best to answer them in a timely manner. I hope you enjoy rooting your device, but please be careful. You now have administrator privileges, so use them wisely. I would highly suggest installing Quick Boot from the Play Store so that you can boot into recovery easily without having to go through hboot. I would also suggest using your newly installed app that requires root access to boot into recovery and make a backup. If anything should ever happen to your phone's system and data you will have a backup and can restore it to that state. Again, I hope you enjoy. I apologize for this being such a lengthy guide, but hopefully you understand the wonderful world of Android a little better for having read it. :good:
*EXTRA* 7. I recommend doing a backup via recovery of your phone, because this phone doesnt seem to have any roms or any stock roms etc, so i recommend making a backup, but dont worry, ill try to make a backup ROM so there could be one on the internet, because I searched and could find one! :s
Great post Julio. I saw this post somewhere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
maikalwolf said:
Great post Juan. I saw this post somewere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
Click to expand...
Click to collapse
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
re you follow up question
julio626 said:
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
Click to expand...
Click to collapse
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
maikalwolf said:
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
Click to expand...
Click to collapse
Thanks man!
Gracias Julio
It was quite tedious to be honest. But reading your guide and this one how-to-unlock-the-bootloader-of-any-htc-device en cultofandroid I finally was able to root my phone. Thank you so much!
Amazing
This is the best guide I have ever found. It was fluid and easy to understand for me. Just went from my JB IPhone 5 (cellular happened to break). now i have this phone lol (but its so slow and useless I decided to root and it was an unbelievable pain.. nothing worked). Then I found your guide which is fantastic, completely like no other. I am very impressed with it and just wanted to say THANK YOU!!!!!! :good:
So Close PLEASE can you help.
I followed this guide about a year ago & got to the image you see linked h**p://i.imgur.com/zfle9n7.jpg To be blunt I do not recall where I left off in the rooting process except to say I'm dead ended. Where did my efforts go wrong and what do I need to do in order to finally get this rooted? Also please tell me what bearing info in this thread: h**p://forums.androidcentral.com/htc-evo-design-4g/142434-s-off-s.html may have on my results. THANK YOU
Hey everyone,
I really have a problem!
I somehow destroyed my software, by trying to do an partition on my own.
I found a solution for my problem in another forum, but I really don't understand how to do it.
This is the solution/answer:
_______________________________________________________________
Yes, this is a big problem.
Had one same incident before, and my technical colleague came up with a solution. You can only fix this by flashing your phone:
For GURU's only!. The alternative is to use the windows flasher tool
1)Download the original image ww.fairphone.com/downloads/softw...-07-31.zip
1)
unzip the file
2)
enable usb debugging
4)
push EBR1 on the phone
adb push Fairphone_1.6_Cherry_FUSE_Image_31-07-2014/EBR1 /mnt/sdcard/
5) (become root)
adb shell
6) (override the partition inforation)
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot info recovery and wipe data
reboot recovery
and wipe//format
Hope this helps
_______________________________________________________________
I have two problems. First of all I don't undertand every step and secondly the first link (ww.fairphone.com/downloads/softw...-07-31.zip) is no longer available.
Is there an other solution do flash my fairphone and revert the partition ???
Werft said:
Hey everyone,
I really have a problem!
I somehow destroyed my software, by trying to do an partition on my own.
I found a solution for my problem in another forum, but I really don't understand how to do it.
This is the solution/answer:
_______________________________________________________________
Yes, this is a big problem.
Had one same incident before, and my technical colleague came up with a solution. You can only fix this by flashing your phone:
For GURU's only!. The alternative is to use the windows flasher tool
1)Download the original image ww.fairphone.com/downloads/softw...-07-31.zip
1)
unzip the file
2)
enable usb debugging
4)
push EBR1 on the phone
adb push Fairphone_1.6_Cherry_FUSE_Image_31-07-2014/EBR1 /mnt/sdcard/
5) (become root)
adb shell
6) (override the partition inforation)
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot info recovery and wipe data
reboot recovery
and wipe//format
Hope this helps
_______________________________________________________________
I have two problems. First of all I don't undertand every step and secondly the first link (ww.fairphone.com/downloads/softw...-07-31.zip) is no longer available.
Is there an other solution do flash my fairphone and revert the partition ???
Click to expand...
Click to collapse
Does this link sove your second porblem? http://storage.googleapis.com/update-v1_6/FP1_Fairphone_OS_1G13G_v1_6_OTA_2014-07-31.zip
Have you tried a factory reset? https://forum.fairphone.com/t/how-to-perform-a-hard-reset-on-my-fairphone/209
Where do you run into problems while following the instructions -any specific steps?
Cheers!
I'm not sure what your exact problem is, and what the state of the phone is, or what operating system you're running on the computer that you're using to fix the phone. That being said, if it is completely bricked, the instructions on the wiki may be of help: http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_restore_Fairphone_if_you_totally_bricked_it . This is the alternative mentioned in the post you quote - if you feel uncomfortable using adb, this may be easier (though I have not tried it myself). You will need the image binaries for your model that are available at the bottom of the page here: https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-. This is the same file as you need in step1 of the instructions you posted. The update to version 1.8 was postponed because of problems for some users, so you may want to stick to the 1.6 binaries.