I had a problem when entering the command promts, on the first computer I tried. I would freeze the computer. After switching to a new computer everything worked okay, except I couldn't flash the last radio zip. Nevertheless I was able able to complete the process and use revolutionary. Got MROM installed and everything appears to be working fine. No idea why my computer was freezing during the tacoroot process.
Windows OS running - HTC drivers properly installed ?? Antivirus & firewall temporary disabled (as it could be blocking access) ??
Check MD5's for the various files downloaded ? Usin the OEM micro-usb cable or generic (unlikely, but just check to eliminate it) and try using a different usb port to run the installation? Outdated Android toolkits/adb loaded & need to be renewed to latest ones?
More specifics would help - any error or pop-up messages or logs ??
(BTW, I just used tacoroot earlier this week to "rescue" a semi-bricked DI2 after RUU, rooted it again (adb - manually) with S-Off and the device is good as new, back on a custom Sense rom again after calling into VZW first (complicated story ...)
You don't flash the radio. you put the file on your sd card with a specific name, can't recall it but lots of references to it, you'll find it no problem, and then you go into the bootloader. It'll automatically install the new radio. don't forget to wipe, and change the file name.
Jasonp0 said:
You don't flash the radio. you put the file on your sd card with a specific name, can't recall it but lots of references to it, you'll find it no problem, and then you go into the bootloader. It'll automatically install the new radio. don't forget to wipe, and change the file name.
Click to expand...
Click to collapse
PG32IMG.zip is what it needs to be named, and when he says wipe you need to wipe dalvik cache and cache... o yeah, and after your done and booted hp make sure to use a file manager and delete the file off your sd card or it will try to keep reinstalling it
Sent from my Incredible 2 using xda app-developers app
Related
Hey,
I just updated to the 1.21... generic stock rom and since im on orange its network locked the phone. Ive looked around and it seems that flashing an older radio will sort this problem out. So i have the older radio but when i try to connect to the phone using the recovery-windows.bat file, it keeps saying "error: device not found"
I can confirm i HAVE installed the USB driver via the android sdk and rebooted my computer. The device is not rooted though
Is the lack of root the issue here or should it still be able to connect?
Thanks for your help
gyro11 said:
Hey,
I just updated to the 1.21... generic stock rom and since im on orange its network locked the phone. Ive looked around and it seems that flashing an older radio will sort this problem out. So i have the older radio but when i try to connect to the phone using the recovery-windows.bat file, it keeps saying "error: device not found"
I can confirm i HAVE installed the USB driver via the android sdk and rebooted my computer. The device is not rooted though
Is the lack of root the issue here or should it still be able to connect?
Thanks for your help
Click to expand...
Click to collapse
Yep, you definately need root access to update your Radio version.
but will not having root stop the recovery-windows.bat file even recognising the phones attached to the pc?
Yes but this is also happening because you have not yet created a Gold Card, which will unlock your CID and Device ID. Create the Gold Card first and then root your phone.
-------------------------------------
Sent via the XDA Tapatalk App
The Gold Card is needed because you have a branded phone.
-------------------------------------
Sent via the XDA Tapatalk App
im pretty sure i already turned my sdcard into a gold card. ill try rooting first then have another look at the gold card
gyro11 said:
im pretty sure i already turned my sdcard into a gold card. ill try rooting first then have another look at the gold card
Click to expand...
Click to collapse
Yes, that is precisely what you must do. Not only do you need to create a Gold Card because of your branded handset, but you also have to root it to have write access to the system partition. Once you do this, you will then be able to flash any compatible ROMs with problems.
argh, this is being a nightmare...i have redone the goldcard and am trying to do the root, but when i type the (linux) command cd /mnt/cdrom/root it says "cant cd to /mnt/cdrom/root
when i do a ls of the directory it says the folders there are boot and desire
please help, its unusable unless i can root this and get the new radio in there
gyro11 said:
argh, this is being a nightmare...i have redone the goldcard and am trying to do the root, but when i type the (linux) command cd /mnt/cdrom/root it says "cant cd to /mnt/cdrom/root
when i do a ls of the directory it says the folders there are boot and desire
please help, its unusable unless i can root this and get the new radio in there
Click to expand...
Click to collapse
To root, try this guide instead, it's pretty straightforward:
http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
You flash the Radio zip file via Recovery the same way you would do when flashing a ROM.
ok, it turns out the usb lead just wasnt being consistantly connected for some reason. Ive managed to sort this out and managed to flash the new rom. However, now i have a new problem but i will put this as a new post as its different to what ive written before in this thread
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'm using the GingerVillain rom, but I was wondering is there a way I can make my device S-OFF whilst using this ROM?
Also I was wondering why my Orange 3G/H signal is so rubbish, it nearly always ends up being on G internet? Anyone else have this problem?
I'm trying to install CWM 3.0.0.5 from recovery, it comes up in the new colours after installing, but on the next reboot it's back to the old one? Do I need to root again with unrevoked using the 3.0.0.5 zip file?
Also is there any was I can run alpharev without having to burn to a CD? I've tried running a virtual box but no luck?
Thanks for reading hope somebody can help.
Jamie94 said:
1. I'm trying to install CWM 3.0.0.5 from recovery, it comes up in the new colours after installing, but on the next reboot it's back to the old one? Do I need to root again with unrevoked using the 3.0.0.5 zip file?
2. Also is there any was I can run alpharev without having to burn to a CD? I've tried running a virtual box but no luck?
Click to expand...
Click to collapse
1. This is because the rom manager doesnt support CWM 3.0.0.5 yet but only: 2.5.x.x
2. The CD option is 100% working and it is quick and almost safe imo.
Jamie94 said:
Also is there any was I can run alpharev without having to burn to a CD? I've tried running a virtual box but no luck?
Click to expand...
Click to collapse
You can burn it on pendrive as bootable usb drive, or use VM like Parallels Desktop (i used it, and worked fine)
I used virtual box, but I had to load specific drivers, and follow alternate instructions. A total PITA, but it works.
I only used UnRevoked because I forgot which other program I used for my previous phone. Afterwards, I now have an app called zysploit running all the time ((((
Moscow Desire said:
I used virtual box, but I had to load specific drivers, and follow alternate instructions. A total PITA, but it works.
I only used UnRevoked because I forgot which other program I used for my previous phone. Afterwards, I now have an app called zysploit running all the time ((((
Click to expand...
Click to collapse
Mind helping me out a bit?
I download a package called "universal usb installer 1.8" Do a search for it. Now, listen up.
As far as I can remember, after extracting, I had to tell Device Manager to install the driver specifically, Not browse for them. Because windows will always look for a signed driver. I had to ignore the normal message that it wasn't signed.
If I'm not mistaken, you need to load the Android Bootloader interface (with phone plugged in, USB debugging enabled)
This "should" allow unrevoked to interface with the phone.
Got the device today, and already came with the bootloader unlocked and S-On...but every method I've tried just doesn't work - even temporary root.
Here's the info on the phone:
-T-Mobile Wildfire S (Marvel PVT) running 2.3.5
-Firmware - 2.17.531.1
-HBOOT - 1.08.0099
Any driver files I've seen are either dead links or "not available in my country" (I'm in the USA), but I'm almost positive I have the appropriate drivers on my Win7 64-bit install, since anything I've had to do on my G2 was problem-free.
Here's what I've tried, all in both "charge only" and "HTC sync" mode, with HTC sync disabled/not running on the PC:
-SuperOneClick - freezes at step #7
-Gingerbreak - endlessly "works" and never accomplishes anything
-Flashing anything via the bootloader fails, either due to not being the "right" image (picks up and starts loading/installing, but then it seems like the file is corrupt and it's aborted - and I've tried multiple files/versions) or failing due to some Model ID mismatch or something
-Flashing a recovery through fastboot (from this thread: http://forum.xda-developers.com/showthread.php?t=1503393) seems to have bricked my recovery
-Anything else in that guide (basically anything zergRush) fails to copy anything over to /system or /sbin or whatever even though it says it successfully rooted at the end
-The temporary root procedure gives me some random error about drivers in the middle of the process and fails
I'm at my wits end here - I just don't know what I'm doing wrong, if anything. If I had known the Wildfire S would be such a PITA just to root, I probably wouldn't have gotten it and saved up for something else...at least I still have my G2 =/
Check that only one instance of ADB is running (in task manager).
try installing Busybox and Superuser from the market first then trying one of the other methods again
inconn said:
Check that only one instance of ADB is running (in task manager).
Click to expand...
Click to collapse
I went and killed it after each time in order to be able to delete the files, that wasn't it.
Nicknoxx said:
try installing Busybox and Superuser from the market first then trying one of the other methods again
Click to expand...
Click to collapse
Tried that too, didn't work.
Ended up doing a full reset because it refused to mount the SD card on my PC at some point, and tried this method:
http://forum.xda-developers.com/showpost.php?p=22178267&postcount=128
And managed to get it rooted that way. Much more inclined to keep my new WFS now
I have tmobile us and all I did was install cwm recovery and flashed a root.zip file. You can pm me if you need the file.
Sent from my HTC Wildfire S using xda premium
I know this thread's been dead for a couple months, but I didn't see that it was resolved...did you turn usb debugging on?
You need that on to root these phones...
Edit : NVM, I should have read a little bit more. Please disregard.
hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse