Related
Apologies if this has been discussed already, I've searched plenty but wasn't able to find this exact scenario.
I have a PG76120 that shipped with locked HBOOT 0.90 and S-ON. I set out with the goal of unlocking the bootloader via HTCDev. The update RUU for failed but I was able to flash the 2 zips separately through the bootloader.
After the rom_01 file (the one that contains radio 7.54.39.08M) I noticed HBOOT was reporting S-OFF so I decided to see what exactly I could do with it. I flashed CWM, made a nandroid, and tried a couple of 2.3.3 ROMs, none of which worked (I imagine because the bootloader was still locked).
I restored stock from nandroid and flashed rom_02 (the one that contains HBOOT 1.08.0099 and radio 7.53.39.03M) and unlocked the bootloader. Thiking that secu_flag is stored in the radio image and that since the rom_01 image reported as S-OFF it might have been unlocked) I then flashed rom_01 again. It didn't S-OFF but it did update the radio.
So: HBOOT 1.08.0099
Radio 7.54.39.08M
***UNLOCKED*** & S-ON with CWM as recovery.
At this point I gave up on the idea of having a custom ROM and decided to flash stock 2.3.5. I used http://forum.xda-developers.com/showthread.php?t=1485345 and flashed it via clockwork. This has caused my problems:
The first time I flashed I had an error a couple of people in the thread were having: phone wouldn't boot past first HTC screen when it went to CWM with "E:invalid command argument". I cleared data/cache/dalvik and reflashed which solved the problem, but has left me in the current situation:
Phone will not boot into recovery, or past initial HTC screen unless the USB cable is plugged in. It bootloops showing the HTC logo and a brief rumble.
If the cable is plugged in it will boot to the new rom and to recovery no trouble, but as soon as you take the cable out it resets and starts bootlooping.
If I put the cable in so that it progresses past the initial HTC screen, but then take it out before it completes launching it's fine, but as soon as the cable goes in it resets and starts bootlooping.
Neither the operating system nor recovery can mount the sdcard. HBOOT can detect update files on the sdcard.
Official RUUs will not flash, they say ERROR 155 (EDIT: RUU Security Fail! Update Fail!)
I also cannot pass them to HBOOT as PG76IMG (it detects the file but is dissatisfied with its contents and aborts).
I cannot flash them via fastboot (signature not found). I can flash CWM again just to make sure its not borked (and I've done that).
I cannot flash anything via recovery as it cannot see my sdcard.
WTF is going on here? :/
Thanks in advance for your assistance.
Update: I've managed to flash an official RUU by relocking HBOOT with
fastboot oem lock
And passing it as P67GIMG.zip on my Goldcard. The same strange rebooting behaviour continues! Is it possible that I have genuinely damaged its hardware?
Is there any possibility this has to do with a corrupt misc partition?
I was able to fix the sdcard issue with fastboot oem enableqxdm 0. The phone can see the sdcard but will not identify itself to the computer over USB. To get files onto it I need to bluetoothe them from my GS2.
If so, could someone please post their misc partition from a functioning 3G Marvel?
Thx
Hi guys, wonder if you can help me. I have a HTC Desire (GSM) and rooted it, removed UK O2 branding and putting Froyo (2.2) on it and a new radio and Clockwork Mod Recovery. I messed around - thought I’d bricked it following a dodgy flash, as couldn't boot, get into recovery or anything, with the phone looping at the HTC logo and powering on until I took the battery out.
Thought I’d look at it today and made progress, but still can’t get a RUU to install on it. I can get into Recovery menu via bootloader and I think the SDcard is a goldcard. Issues I have are:
• I can’t flash a RUU onto the phone from running the file through Windows, as I constantly get an Error 170 USB Connection error. I’ve tried reinstalling HTC Sync, trying different versions, tried a different USB cable and port. I’ve tried running HTC Sync as Admin, and in compatibility mode under XP SP 2 and updated the driver in Control Panel and it displays as “My HTC”, nothing works. I am running Windows 7 64 Bit.
• I tried putting the RUU onto the phone as a PB99IMG.zip file and running it through Recovery, but I get a message saying “bad file”
• As soon as I put a file onto the SD card, Ext3 then won’t mount with an error message and I have to repartition the SD card in Windows (Using Mini-tool Partition Wizard). The error I get is "can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!” I can fix it, but soon after it is fixed it reverts back to error it I add any files to root of the SD card to run through Recovery.
I just want to get the phone back working, whether it is branded or unbranded, and whatever RUU I can get working on it. Can anyone advise the steps I can take from here please?
My stats/versions are:
HBoot 0.93.0001
Radio 5.09.00.08
ClockworkMod Recovery v2.5.0.7
S=On
Thanks,
Stewart
Tried downloading the RUU again? I recommend to check md5sum afterwards.
Sent from Sandvold's ICS using Transparent XDA App
Thanks MatDroid, I've managed to get past the 171 error and now getting a 131 error, saying it is the incorrect ROM. Is there somewhere I can get confirmation of the correct ROM for my device and check MD5sum before loading?
I would look at putting on another recovery, something like 4ext touch. Google it, your current clockwork recovery is pretty dated. Look at a program called android flasher, and you will be able to flash a new recovery through that.
Once you get the new recovery working, there is an option to toggle USB storage in which you can put your custom from on the SD card. Once the custom from is on your SD card, flash it through recovery. Hopefully it should work
Sent from my HTC Desire using XDA App
you should really look at my guide, you don't flash RUU zip files through recovery.
just realised you are s- on so android flasher won't work. Therefore until you s-off your phone, as mattdroid said you may have a bad download for the ruu. Try downloading ruu again nd running the exe file
Sent from my HTC Desire using XDA App
bortak said:
you should really look at my guide, you don't flash RUU zip files through recovery.[/QUOTE
Yeah just realised that too sorry for the wrong information. he is only wanting a ruu which of course is not done through recovery with the exe file. Custom rom is a different story.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks guys I've figured it out and have now succesfully got the phone working.
Issues were:
I was trying to flash the wrong RUU (a 2.09 instead of 2.10) so when flashing it was rejecting as a lower version. Using the right RUU worked
My SDcard wasn't a goldcard - I thought it was but apparently not. I re-created the goldcard and it worked
I was trying to flash from the wrong place - instead of through FastBoot USB I was going into Clockwork Mod and loading files, mucking around with the mountings and things like that
All great now, so thanks again.
Stewart
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
nodnarb said:
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
Click to expand...
Click to collapse
Try this, reformat your sdcard fat32 with a pc. Then place only this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on the sd in no folders (Do not rename). Boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. I think your issue with the ruu before was that you were trying to flash an older version than you already have installed. If that dosent work try fastboot flashing cwm again, and see if it can mount the sd then.
Thread moved. Please post all questions here in the correct section of the forum.
Thanks
AvRS
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
shivaagarwal1 said:
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
You'll probably get better help in the Incredible S section. This is for just the plain olé Incredible.
Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.
That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.
Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?
double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...
I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?
double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.
double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe
Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.
Im stuck on rooting..
First when i try to install the HBOOT drivers it installs them as "HTC Serial Interface (COM4)" after the Android 1.0 thing (windows automaticly installs them and cannot abort that, and if i want to update it with the custom ones it says the current drivers are up-to-date.
So i dont have the "Android Bootloader Interface" option at the device manager.
Got the HTC Driver and HTC BMP USB drivers installed and removed HTC Sync.
Second, whatever Revoked version (i used 3.21-3.32, it keeps hanging on "waiting for Bootloader, make sure drivers are installed"
I've been repeating the process like 100x each step and still.
Additional info:
OS: Windows 7 64-Bit
Android 2.2.2 Original Stock (SoftwareNr: 2.29.405.15)
4GB SD Card (class 10)
Bravo PVT4 SHIP S-ON
HBOOT 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
Radio-5.11.50.26
Aug 10 2010, 17:52,18
I have used various methods from different forums none seem to work and i'm really clueless.
I've flashed Samsungs, Sony's, even MTK's flawlessly and this particular HTC device is a pain in the ass.
Ive used XDA guide: http://forum.xda-developers.com/showthread.php?t=1275632
and: http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
and: http://androidforums.com/desire-all...ked-windows-updated-11th-november-2011-a.html
and: http://androidforums.com/desire-all-things-root/503471-desire-all-things-root-guide.html
Is there anyone with a sollution because i really need more app space (or a bloatware free rom) and based on various comment on the sites mention didn't work as well as it should.
You'll want to gain s-off first before rooting. To do this you can use revolutionary.
First I'd suggest removing any drivers (and HTC sync) that you have already installed. Then setup adb/fastboot as it may be useful later. Finally install these fastboot drivers. Now to test if its being detected put the phone into the bootloader (turn off, then boot up using volume down + power). Next plug the phone into the computer via usb and open up a command prompt window. Run "fastboot devices" and the phones serial number should be shown. Let me know once you've done this.
Chromium said:
You'll want to gain s-off first before rooting. To do this you can use revolutionary.
First I'd suggest removing any drivers (and HTC sync) that you have already installed. Then setup adb/fastboot as it may be useful later. Finally install these fastboot drivers. Now to test if its being detected put the phone into the bootloader (turn off, then boot up using volume down + power). Next plug the phone into the computer via usb and open up a command prompt window. Run "fastboot devices" and the phones serial number should be shown. Let me know once you've done this.
Click to expand...
Click to collapse
Thanks i will try that and report back.
It would've been nice if any of those tutorials mentioned S-OFF needed before hand!
Edit: okay the phone is S-OFF, i will now proceed with the ADB thing but its downloading the SDK files as we speak...
@Chromium
Okay ive installed the adb files and set it all up. But i'm stuck on "fastboot devices" on the cmd command line saying it cannot find "fastboot devices"
If i run C:/adb fastboot devices i get a bunch of commands while the phone was booted into HBOOT (S-OFF ofc)
Also tried C:\adb\platform-tools>fastboot devices but nothing is shown
For some strange reason my device manager says SAMSUNG ANDROID PHONE > Android Bootloader Interface when i hit "Bootloader" in HBOOT (was testing this)
Ignoring the adb step: I rerun every step again but it's still stuck on "waiting for Bootloader, make sure drivers are installed" after running Unrevoked3
additional info:
Revolutionary S-OFF
HBOOT-6.93.1002
Edit: question; I installed Revolutionary CWM v4.0.1.4 through revolutionary after the S-OFF process (which is weird since installing a custom recovery needs root access).
Is it possible to install 'custom rooted roms' through "update from sdcard", without root access?
I ask before hand because i dont want to brick my phone..
I have done a backup in CWM, so i'm going to try and flash a rom...
Ok i succesfully flashed my htc with CM7.2 without rooting my htc in the first place.
I've been struggling with the rooting process for 2 days, but as i mentioned in my previous post i just flashed through revolutionarys CWM.
thank god!
(Even though your best ROM thread was closed, I did mention s-off and revolutionary and the guides...the ones you found are old)
You don't technically need root access to install custom recovery as you have found out.
You are already s-off, that's the hardest bit, rest is easy.
To root your existing ROM if you need to, flash superuser thru recovery
Don't know why fastboot devices didn't show, driver issue somewhere or not set up correctly.
Anyway if you can boot into the os, install 4ext recovery via app from 4ext,net.
Backup your sd card and use 4ext to partition your sdcard.
Then yes you can install a stock rooted ROM or any custom ROM of your choice, check for individual a2sd features or requirements
eddiehk6 said:
(Even though your best ROM thread was closed, I did mention s-off and revolutionary and the guides...the ones you found are old)
You don't technically need root access to install custom recovery as you have found out.
You are already s-off, that's the hardest bit, rest is easy.
To root your existing ROM if you need to, flash superuser thru recovery
Don't know why fastboot devices didn't show, driver issue somewhere or not set up correctly.
Anyway if you can boot into the os, install 4ext recovery via app from 4ext,net.
Backup your sd card and use 4ext to partition your sdcard.
Then yes you can install a stock rooted ROM or any custom ROM of your choice, check for individual a2sd features or requirements
Click to expand...
Click to collapse
I know and i've seen the link, but i started with the ROOT part from that website as i thought the S-OFF part came after the rooting process.
I just installed CM7.2 and everything worked fine.
I partitioned the SD card in the CWM menu but i didn't knew what size to pick so i went with 1024mb and 256mb cache.
Im glad cm works and my app space is 151mb however on first boot there was 148mn available and now after a reboot & googleplay store only 56mb is left????
Well atleast i can move apps to SD (i guess)
edit: I flashed Beanstalk 4.4 (release 4.5) with jmcclue's 250/5/182 hboot & 4EXT Recovery. Everything works perfect.
JMailuhu said:
I know and i've seen the link, but i started with the ROOT part from that website as i thought the S-OFF part came after the rooting process.
I just installed CM7.2 and everything worked fine.
I partitioned the SD card in the CWM menu but i didn't knew what size to pick so i went with 1024mb and 256mb cache.
Im glad cm works and my app space is 151mb however on first boot there was 148mn available and now after a reboot & googleplay store only 56mb is left????
Well atleast i can move apps to SD (i guess)
edit: I flashed Beanstalk 4.4 (release 4.5) with jmcclue's 250/5/182 hboot & 4EXT Recovery. Everything works perfect.
Click to expand...
Click to collapse
You've rushed into it without following instructions or understanding how things work................
- You shouldn't partition with cwm as it often makes badly aligned partitions (they don't work)
- You don't need to partition with cache as the ROM needs to be programmed use it, and has limited benefit anyway
- You're not actually using your partition if you don't flash an a2sd script or use an app to actually move things to the partition of the sdcard. Your 'move to sd' is moving part of the app to the original fat32 part of your sdcard, exactly the same as before you even rooted/s-off i.e no gain...
- You should have flashed a different hboot before you flashed the ROM as you're wasting space on /system, which is also why your seeing low memory already. Again you have exactly the same amount of internal space as before you rooted/s-off....
So....
- please flash 4ext recovery as instructed
- completely backup and re-partition your sdcard from scratch with that recovery, no swap or cache
- learn to flash cm7r2 hboot with fastboot, instructions in the earlier guide you found
- full wipe and reinstall cm7 ROM again
- flash a2sd script or use an app such as s2e to move future apps to your sd partition (sd-ext)
- Keep apps on internal to trick them to sd-ext, your memory won't necessarily appear expanded, but your partition is working
- install an app like DiskUsage to understand how all your memory is being used in the first place...
Seems a lot but you should have read and done this in the first place you can do it correctly now or run into trouble later when you have no idea why...
EDIT: only saw your edit after my initial reply.
Some of my points still stand...please at least understand how your memory is being used (DiskUsage)