Related
Well I USB bricked my Desire last night.
To make things worse I was only able to apply the SD Card workaround via fastboot.
After flashing the update.zip from the modaco fix I instantly went back to the stock rom using the fastboot RUU process, without actually checking if it solved all the problems...
I know I had it coming...
Before I ship the phone out for repairs - maybe someone here knows if there is a chance to unbrick without root (nor having HBOOT version that allows to use any other method of rooting other than Unrevoked)
Code:
HBOOT 0.93
European 2.10.405 OTA
Thanks in advance
a more detailed description would help:
does your phone boot?
do you have running clockworkmod recovery?
did you do a nandroid backup before touching the system?
what modaco fix? give a link.
did you use unrevoked? thats the default root tool nowadays.
can you go to hboot/fastboot when pressing vol down while pressing power on?
Use a goldcard, it will enable you to put an unrooted Rom there. It's always a good reset option.
Sent from my HTC Desire using XDA App
mad-murdock said:
a more detailed description would help:
does your phone boot?
do you have running clockworkmod recovery?
did you do a nandroid backup before touching the system?
what modaco fix? give a link.
did you use unrevoked? thats the default root tool nowadays.
can you go to hboot/fastboot when pressing vol down while pressing power on?
Click to expand...
Click to collapse
Hi,
- the phone boots ok - It has most of the symptoms from All you need to know about USB-Bricks thread, the SD card started to work after issuing:
Code:
fastboot oem enableqxdm 0
This is the output from the fastboot oem boot command
Code:
$ fastboot-mac oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__032
INFOsetting->cid::HTC__032
INFOserial number: HT057PL01634
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =430
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.09.05.30_2 androidboot.cid
INFO=HTC__032 androidboot.carrier=HTC-EastEurope androidboot.mid
INFO=PB9920000 androidboot.keycaps=qwerty androidboot.mode=norma
INFOl androidboot.serialno=HT057PL01634 androidboot.bootloader=0
INFO.93.0001 no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:697447 msec
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
- Sadly, I made a complete reflash using
Code:
fastboot rebootRUU;
fastboot flash zip rom.zip
... so no Clockwork recovery anymore
- Yes I have a nandroid backup but no means to put it back on the phone - the nandroid backup contains exactly the same rom I have now - just rooted
- As for the modaco fix I'm a new user I can't post external links, but it's the first link in this thread
- I did use the lastest Unrevoked3 (3.21) to root the phone
- I can use hboot / fastboot without problems but it's the stock 0.93.001 S-ON version.
Thanks
geejayoh said:
Use a goldcard, it will enable you to put an unrooted Rom there. It's always a good reset option.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I have an unbranded Desire so no need to use a GoldCard if I'm not mistaken.
Anyway if memory serves me right using the GoldCard / HBOOT / PB99IMG flashing, won't allow me neither to downgrade, nor to flash an unsigned rom.
An unsigned rooted rom or HBOOT downgraded do 0.80 could help me fix my problem - but with HBOOT 0.93 - dowgrading doesn't seem to be an option. I get a "Main Version Older" error when trying to downgrade, and flashing an unsigned rom is a no-no for all stock bootloaders as far as I know (I tried both HBOOT and recovery, both as expected fail at signature verification).
But thanks anyway
Whats the exact problem now? You restored rom.zip via ruu. So you got a stock firmware with stock hboot and stock recovery which can be unrevoked again?
Seams i am missing a detail ^^
Sent from my HTC Desire using Tapatalk
mad-murdock said:
Whats the exact problem now? You restored rom.zip via ruu. So you got a stock firmware with stock hboot and stock recovery which can be unrevoked again?
Seams i am missing a detail ^^
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
It seems to me you're missing the main issue not a detail
The main issue being a condition called "USB Brick" (well that's only half the truth, most of the main issue is me acting without thinking )
Please read the info thread on USB Bricks here, since you have a HTC Desire - it concerns you too. Good idea to backup the MISC partition if you plan to flash the phone again
Anyyyyway - as for my case:
I screwed up, flashed the stock firmware BEFORE checking if the applied USB brick fix solved my problems. So it's true I have stock firmware, stock hboot, stock recovery - but I also have no way to connect the phone to a computer via USB - because the flashing process updates the following partitions: system, recovery, boot but not the misc partition which is now corrupt, and its corruption is the cause of the USB brick...
USB Brick = no usb connection at all while booted to the Android OS
No usb connection = no usb debug mode
no usb debug mode = no unrevoked
The usb still works from HBOOT / FASTBOOT, so If you know of a way to start Unrevoked while the phone is in HBOOT / FASTBOOT - please enlighten me, because I couldn't do It.
Unrevoked only recognized the phone while it was in USB Debug mode, which it cannot enter now because of the USB Brick. When I connect the phone while in Fastboot USB mode or HBOOT USB mode Unrevoked just states "Waiting for device".
I don't think I am able to put this in any clearer way
Thanks
Ouch. Now i see. Didnt understand you at the start. Well, i had an usb brick myself after wiping the system. At least i had a modded hboot and recovery.
Now to your problem. Wierd situation, really. But if i remember right, flashing one of the ruu.Exe files should also fix misc. Then you have stock firmware with usb working. Cant link here in tapatalk, but those ruu file are a sticky in desire dev forum... tell me, if it worked...
Sent from my HTC Desire using Tapatalk
Solved!
I was able to successfully unbrick the phone
It wouldn't be possible without rageagainstthecage, All the people writing the tutorials on USB unbricking, QuickSSHd and the Terminal Emulator app. Thanks to the authors.
I'll try to sum things up for anyone interested:
The problem
Because of acting without thinking I ended up with a stock unrooted rom and a partial USB brick. To make things worse I accepted the OTA update, installing the oh so loved HBOOT 0.93.100 S-ON.
The Solution
After some reading about rageagainstthecage, PoC code on which the Unrevoked rooting solution is based I tried to run the exploit directly on the phone.
Without having access to adb I wasn't able to find a place to put the executable, as the /data/ directory is writable only by the system user and the system group, and most tutorials suggest to place the exploit somewhere inside that directory. But all the tutorials I found mentioned using adb push to put the file on the phone, which probably operates on the phone as system:system as it is capable of writing to the /data dir. I wasn't able to write there as I had the id of the Terminal Application
Since apps storing data seem to store er... data in /data/data I had a little breakthru. Becaue I couldn't find a free telnet solution I purchased the QuickSSHd from Android Market.
This allowed me to have write access to /data/data/<package_name>/home where I created a world readable (755) directory. I scp'd the rageagaintthecage, modified misc partition image and flash_image binary to the phones filesystem, and made them executable. I could've used the Terminal Apps <data dir>/shared_prefs directory (which would be a $$$ free solution, as the ssh was not free, but not expensive either) but I'm lazy and doing stuff from a PC keyboard is easier than from a touch keyboard.
Running the exploit and flash_image from inside a ssh session seemed like a good idea but the sshd died after running the exploit, and didn't want to start untill the phone was rebooted. So next time I just started the sshd and done the rest of the stuff from a Terminal Emulator (After preparing scripts for ease of execution, and dropboxing the paths for copy paste ). After running the exploit the Terminal Emulator app stopted working correctly (as expected) but after force closing it and running it again I was greeted with a # prompt
I flashed the misc partition with an image modified with my phones CID, rebooted and voila! USB brick gone
Now I just have to beat one thing into my empty head (in the manner of "stop, drop, and roll" firedrill mantra). STOP, READ and THINK - before flashing
g'night
mad-murdock said:
Ouch. Now i see. Didnt understand you at the start. Well, i had an usb brick myself after wiping the system. At least i had a modded hboot and recovery.
Now to your problem. Wierd situation, really. But if i remember right, flashing one of the ruu.Exe files should also fix misc. Then you have stock firmware with usb working. Cant link here in tapatalk, but those ruu file are a sticky in desire dev forum... tell me, if it worked...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Hi,
Just fyi because I was able to resolve my problem in the meantime.
Because I was foolish enough to install the OTA upgrade before it occured to me that the USB is not working, installing any RRU either in the official way (by running the exe) or by extracting the rom.zip from inside of the exe didn't work. The latest RRU was older then the firmware with OTA upgrade on my phone, and it didn't seem to allow me to downgrade.
ZIP way = Main Version Older error
EXE way = You have to install the correct firmware version or some other bla bla bla
Anyway I took a look inside the rom.zip extracted from the RRU.exe - there are img files of every partition, radio and hboot but no misc.
But thanks again anyway
How did you solve your tricky situation then?
Sent from my HTC Desire using Tapatalk
quanchi said:
I was able to successfully unbrick the phone
It wouldn't be possible without rageagainstthecage, All the people writing the tutorials on USB unbricking, QuickSSHd and the Terminal Emulator app. Thanks to the authors.
I'll try to sum things up for anyone interested:
The problem
Because of acting without thinking I ended up with a stock unrooted rom and a partial USB brick. To make things worse I accepted the OTA update, installing the oh so loved HBOOT 0.93.100 S-ON.
The Solution
After some reading about rageagainstthecage, PoC code on which the Unrevoked rooting solution is based I tried to run the exploit directly on the phone.
Without having access to adb I wasn't able to find a place to put the executable, as the /data/ directory is writable only by the system user and the system group, and most tutorials suggest to place the exploit somewhere inside that directory. But all the tutorials I found mentioned using adb push to put the file on the phone, which probably operates on the phone as system:system as it is capable of writing to the /data dir. I wasn't able to write there as I had the id of the Terminal Application
Since apps storing data seem to store er... data in /data/data I had a little breakthru. Becaue I couldn't find a free telnet solution I purchased the QuickSSHd from Android Market.
This allowed me to have write access to /data/data/<package_name>/home where I created a world readable (755) directory. I scp'd the rageagaintthecage, modified misc partition image and flash_image binary to the phones filesystem, and made them executable. I could've used the Terminal Apps <data dir>/shared_prefs directory (which would be a $$$ free solution, as the ssh was not free, but not expensive either) but I'm lazy and doing stuff from a PC keyboard is easier than from a touch keyboard.
Running the exploit and flash_image from inside a ssh session seemed like a good idea but the sshd died after running the exploit, and didn't want to start untill the phone was rebooted. So next time I just started the sshd and done the rest of the stuff from a Terminal Emulator (After preparing scripts for ease of execution, and dropboxing the paths for copy paste ). After running the exploit the Terminal Emulator app stopted working correctly (as expected) but after force closing it and running it again I was greeted with a # prompt
I flashed the misc partition with an image modified with my phones CID, rebooted and voila! USB brick gone
Now I just have to beat one thing into my empty head (in the manner of "stop, drop, and roll" firedrill mantra). STOP, READ and THINK - before flashing
g'night
Click to expand...
Click to collapse
Any chance of adding some links or actual information?
I've got exactly the same problem and you seem to have the solution.
Any chance of sharing?
Usb Brick !? This is an OLD thing I have this some Months ago. Never heard of someone who got it again! YOU did something wrong ;-)
Sure, he did something wrong.I managed this, too, when playing with a partition tool not designed for my system. Misc partition damaged, so a nice usb brick...
About the requested links : just use forum search for usb brick. First hit is your sticky solution
Sent from my S-OFF'd brain using teh internetz
CyberTech71 said:
Any chance of adding some links or actual information?
I've got exactly the same problem and you seem to have the solution.
Any chance of sharing?
Click to expand...
Click to collapse
I couldn't post external links, forum limitation for new users... Now I see I can so:
This is a specific situation - usb brick and totally stock rom, recovery and hboot. It's not required for people who have a modified recovery and a rooted rom. It's easy like 1-2-3.
Before doing anything else enable the Debug Mode in the Applications / Dev menu
1. Download the rageagainstthecage exploit from the authors site:
http://c-skills.blogspot.com/2010/08/please-hold-line.html
2. Download the flash_image and misc (mtd0.img) partition image from this thread.
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
Modify the mtd0.img according to your phones CID (how to get the CID also explained in the thread)
2. Download Android Terminal Emulator from the Market
3. Copy the exploit binary (rageagainstthecage-arm5.bin), the flash_image and modifed mtd0.img to the sdcard via an external card reader
4. Start the Terminal
5. Copy the files to the Terminal app data directory (the only place on the data partition you will have write access while running the Terminal), and make the binaries executable
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/shared_prefs/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/shared_prefs/mtd0.img
cd /data/data/jackpal.androidterm/shared_prefs/
chmod 755 rageagainstthecage-arm5.bin flash_image
6. Run the exploit
Code:
/data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
After the exploit exits/finishes there should be a short system freeze, followed by inablity to issue any command from the terminal (don't worry). Exit the Terminal by long pressing HOME and force close the Terminal app from the Application Manager
7. Start the terminal again, a root prompt should be visible
8. Flash the misc partition
Code:
cd /data/data/jackpal.androidterm/shared_prefs
./flash_image misc mtd0.img
9. Reboot
Done and done
Enjoy
PS. I suck at writing tutorials, but if the details are still hazy for you after reading this - better to service the phone, because you might end up bricking the device totally - cheers
quanchi said:
I was able to successfully unbrick the phone
It wouldn't be possible without rageagainstthecage, All the people writing the tutorials on USB unbricking, QuickSSHd and the Terminal Emulator app. Thanks to the authors.
I'll try to sum things up for anyone interested:
The problem
Because of acting without thinking I ended up with a stock unrooted rom and a partial USB brick. To make things worse I accepted the OTA update, installing the oh so loved HBOOT 0.93.100 S-ON.
The Solution
After some reading about rageagainstthecage, PoC code on which the Unrevoked rooting solution is based I tried to run the exploit directly on the phone.
Without having access to adb I wasn't able to find a place to put the executable, as the /data/ directory is writable only by the system user and the system group, and most tutorials suggest to place the exploit somewhere inside that directory. But all the tutorials I found mentioned using adb push to put the file on the phone, which probably operates on the phone as system:system as it is capable of writing to the /data dir. I wasn't able to write there as I had the id of the Terminal Application
Since apps storing data seem to store er... data in /data/data I had a little breakthru. Becaue I couldn't find a free telnet solution I purchased the QuickSSHd from Android Market.
This allowed me to have write access to /data/data/<package_name>/home where I created a world readable (755) directory. I scp'd the rageagaintthecage, modified misc partition image and flash_image binary to the phones filesystem, and made them executable. I could've used the Terminal Apps <data dir>/shared_prefs directory (which would be a $$$ free solution, as the ssh was not free, but not expensive either) but I'm lazy and doing stuff from a PC keyboard is easier than from a touch keyboard.
Running the exploit and flash_image from inside a ssh session seemed like a good idea but the sshd died after running the exploit, and didn't want to start untill the phone was rebooted. So next time I just started the sshd and done the rest of the stuff from a Terminal Emulator (After preparing scripts for ease of execution, and dropboxing the paths for copy paste ). After running the exploit the Terminal Emulator app stopted working correctly (as expected) but after force closing it and running it again I was greeted with a # prompt
I flashed the misc partition with an image modified with my phones CID, rebooted and voila! USB brick gone
Now I just have to beat one thing into my empty head (in the manner of "stop, drop, and roll" firedrill mantra). STOP, READ and THINK - before flashing
g'night
Click to expand...
Click to collapse
Hello
in you problem with USB bricks for unrooted HTC desire
I have the seam problem
please explain it to me
I copy the flash_image and mtd0.img to
\data\data in my device I only need to flash them to restore my device
when I try this command in terminal Eliminator
/data/data/flash_image misc /data/data/mtd0.img
It show me
error writing misc permission denied
help me please
I can't believe it, mate, finally this tutorial solved my usb (and bluetooth, and fm radio, and...) problem!!!!!
My Desire is unrooted, I've tried so many solution in the last 3 months but they all were useless.
I was starting to pack my phone for sending it to HTC Service when... tataaaa, I found your topic. Is on your if my wonderful Android powered phone got back fully functional.
Really, thank you for sharing your solution with us.
===========;-D
Francalberto
francalberto said:
I can't believe it, mate, finally this tutorial solved my usb (and bluetooth, and fm radio, and...) problem!!!!!
My Desire is unrooted, I've tried so many solution in the last 3 months but they all were useless.
I was starting to pack my phone for sending it to HTC Service when... tataaaa, I found your topic. Is on your if my wonderful Android powered phone got back fully functional.
Really, thank you for sharing your solution with us.
===========;-D
Francalberto
Click to expand...
Click to collapse
Good for you
All the credit goes to the people responsible for the tools used, I just put some things together.
Cheers
thank you very much
I really appreciate you effort you helped me so much
you are a brilliant man
thank you
Flashb, is your problem solved now?
Swyped with my S-OFF'd brain using teh internetz
Hi, all
i am new with android OS.
i have an htc desire Z which was semi-bricked, it keeps on htc logo. then i search this forum for unbrick the device, and i found this rom, PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
i tried to update the file, and the device is ok after the update proses.
but, after i tried to open an application (i.e message), i can't go back to home. when i touch the home icon on the screen, the vibrate is on, but the screen is still.
is there something missing in the update proses?
sorry if i'm doing double post with this thread.
thank you all.
Well the problem is that you flashed a stock G2 ROM on the DZ... I think
omarsalmin said:
Well the problem is that you flashed a stock G2 ROM on the DZ... I think
Click to expand...
Click to collapse
+1
I agree
Sent from my HTC Vision using XDA App
Oh, I see..
Then i should look for DZ one. Could anyone here give me the link of stock DZ rom?
My hboot screen display:
Vision PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 2 2010
Here's what you're going to need to do. You need to download Terminal Emulator from the Android Market (the one by Palevich I think) and follow these steps:
Download the G2TempRoot.rar file I have attached. It also includes a DesireZ bootloader.
Extract the files to your desktop.
Now, you're going to ROOT your poor device. Follow these steps.
1. Make sure you have your USB debugging enabled and plug-er-in.
2. Open a command shell. Type in "cd Desktop\G2TempRoot" without the quotes of course...
3. Type in the following commands followed by enter after each one.
Code:
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb push rage /data/local/tmp/rage
adb shell chmod 0755 /data/local/tmp/*
adb push wpthis\wpthis-pre-OTA.ko /sdcard/wpthis-pre-OTA.ko
adb push wpthis\wpthis-OTA.ko /sdcard/wpthis-OTA.ko
adb push desirezboot\hboot-dzship.img /sdcard/hboot-dzship.img
--- All commands from here out are typed into the phone using Terminal Emulator, not ADB ---
4. Open up the Terminal Emulator you just installed on your phone and type the following:
Code:
/data/local/tmp/rage
Let it finish. After you see "Forked #### childs" press the Menu button on your keyboard and then tap "Reset terminal" on the screen.
5. Open the Terminal Emulator again. This time it will force close. Close it. Now, open the Terminal Emulator again, this time you should have a root shell.
6. If you did not apply the OTA update, type this into your terminal screen:
Code:
insmod /sdcard/wpthis-pre-OTA.ko
and press enter. It should say something about "function not implemented". This is normal. If it says anything else, you probably applied the OTA, and you need to reboot and start this process from step 4, replacing wpthis-pre-OTA.ko in step 6 with wpthis-OTA.ko.
7. Now, you're going to type the following commands into your shell. Make sure you double check EACH and EVERY command before you hit enter. Screwing up the first one, specifically has a nasty habit of producing bricks.
Code:
dd if=/sdcard/hboot-dzship.img of=/dev/block/mmcblk0p18
/data/local/tmp/root
sync
8. Now you should be able to reboot your phone into fastboot (trackpad button+power) and reflash using a HTC DesireZ RUU. Sorry, I have none of these in my files. Look in the wiki here, I think there are a few posted up.
9. If the RUU can't detect your phone, don't close the utility, YET. Search for rom.zip on your computer, and it'll be the one located in your temp folder. It should be ~ 260MB. Copy it to a place on your desktop, rename it PC10IMG.zip, and copy it to the root of your SD card using either an adapter and a SD reader, or a working phone that has SD storage. Then it's just a matter of booting into the bootloader with the Vol down + Power combination. It should go through the checks, and ask you to update if all worked correctly.
-- My guess is you didn't apply SuperCID to your phone before flashing G2 ROM? --
Wow, thanks for the reply. Quite confused though.
Yes, maybe i didn't apply SuperCID before flashing.
How can i make sure that USB debugging has been enabled?
Wow, well I guess this confirms it's fine to flash a stock G2 ROM to a Desire Z !
Those buttons won't be working because of the key mapping. The G2 and DZ have different hardware keyboard, so different keyboard mappings. Those capacitive buttons on the phone are effectively linked to the hardware keyboard, so just need mapping differently. It's possible to change the mapping, but probably makes more sense (no pun intended lol) just to flash a DZ ROM.
You can find the original 1.34 European RUU at http://forum.xda-developers.com/showthread.php?t=822908
There is also a newe 1.72 version, but be careful, because right now the current rooting methods don't work on that one.
To enable USB debugging you need to go into Menu->Settings->Applications->Development
Actually, the bootloader may have detected an incorrect digitizer controller. There is a difference in both the version of the bootloader and the order in which the firmwares partitions are flashed. You may want to reflash the G2 firmware again without switching out the bootloader to see if this fixes your issue. If not, the problem may actually lie in the partition 7 which was modified to unlock your phone. Try a reflash of the G2 PC10IMG.zip without switching your bootloader back if you have your heart set on stock Android. Watch the screen while it is flashing to make sure everything flashes ok. One of the TP entries should get skipped. TP stands for touch panel in this case. An incorrect driver could well explain why your icons aren't working.
For anyone interested, I flashed my G2 to DZ and back with great success, but to load the DZ rom I had to switch bootloaders and flashing it back to G2 flashed twice due to the difference in partition order to make sure everything went through OK. You may also have a corrupt .zip file. Open up your PC10IMG.zip file up in an archiver and run a test to make sure nothing fails. If the zip is corrupt its gonna load a bad digitizer driver everytime and possibly screw up the ROM.
Okay, i'll try again.
@steviewevie, Thanks for sharing.
If i use RUU_Vision_HTC_WWE....exe with a DZ that has a G2 rom inside, there will be no problem with the device?
@deliberate187, I guess there is nothing wrong with the zip file i have, coz i got it from this forum, and when i extract it with winrar, it extracts all files completely withouit fails.
deliberate187 said:
Actually, the bootloader may have detected an incorrect digitizer controller. There is a difference in both the version of the bootloader and the order in which the firmwares partitions are flashed. You may want to reflash the G2 firmware again without switching out the bootloader to see if this fixes your issue. If not, the problem may actually lie in the partition 7 which was modified to unlock your phone. Try a reflash of the G2 PC10IMG.zip without switching your bootloader back if you have your heart set on stock Android. Watch the screen while it is flashing to make sure everything flashes ok. One of the TP entries should get skipped. TP stands for touch panel in this case. An incorrect driver could well explain why your icons aren't working.
For anyone interested, I flashed my G2 to DZ and back with great success, but to load the DZ rom I had to switch bootloaders and flashing it back to G2 flashed twice due to the difference in partition order to make sure everything went through OK. You may also have a corrupt .zip file. Open up your PC10IMG.zip file up in an archiver and run a test to make sure nothing fails. If the zip is corrupt its gonna load a bad digitizer driver everytime and possibly screw up the ROM.
Click to expand...
Click to collapse
Interesting info. So those TP things in the ROM are something to do with the touch panel ?
I could be wrong, but the TP files are Atmel firmwares. If I'm not mistaken Atmel is the manufacturer of the controller chips used in the touch panels on Android phones.
Sent from my T-Mobile G2 using XDA App
Sirs,
I believe I did the same, that is flashing a G2 ROM to a Desire Z phone.
Now I followed the instructions till I reached 8 and 9, I downloaded: RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe, tried it, it gave me this error on the PC:
"Error [156]: image error
The rom update utility cannot update your android phone.
Please get the correct rom update utility and try again."
Searched for rom.zip, changed its name to PC10IMG.zip, took the sd card out, copied the file, rebooted the phone, the bootloader didn't recognize the ROM.
This what flashed so fast on the screen:
"SD Checking ...
Loading ... [PC10DIAG.zip]
No image!
Loading ... [PC10DIAG.ngh]
No image or wrong image!
Loading ... [PC10IMG.zip]
Lack of heap!
Loading ... [PC10IMG.nbh]
No image or wrong image!"
I hope these info will help:
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 2 2010, 17:59:38
The mobile works, but none of the bottom icons do: Home, Menu, Back, and Search.
The keyboard isn't matching 100% specially with the special characters.
At boot, HTC signs appear, then "T mobile G2 with Google" appears short after, then the home screen.
Settings/About phone:
Model number: T-mobile G2
Android Version
2.2
Baseband Version
12.22.60.09.bU_26.02.01.15_M2
Kernel version
2.6.32.17-g814e0a1
[email protected]#1
Build number
1.19.531.1 CL255798 release-keys
I m lost as you may see!
I don't know what else I made wrong in addition to flashing the wrong ROM.
Hello,
I'm new to the forums, and have only just recently got a HTC Wildfire A3333 running 2.2.1.
I have tried to use " [GUIDE] Downgrade to HTC Froyo WWE for AlphaRevX (HBOOT 1.01.0001) " to downgrade the h boot as to start to gain root.
But when I have followed the instructions, it appears to complete ok, but when I reboot in to the system menu, it still shows as .002 hboot and does not install the rom supplied.
any help would be great
EDIT: IT TOLD ME I HAD SUCCESSFULLY CREATED GOLD CARD
GlennBrownie
same goes with me mate, i got the gold card and then i insert it, it all goes but when the cmd closes it still shows hboot 1.01.002
This happened to me on a Telstra wildfire (A3335). if you make it so the CMD window doesn’t close (I used an alternative shell) you will see that it actually gets some error before closing, which is why it doesn’t actually change the hboot.
I must have done it 20 times before I got it to work. I can't remember what I did differently the time I made it work, but it was something to do with which usb mode the phone was in for each step, and when I decided to change it from one mode to the other. Basically trying to make it so the phone wouldn’t say “preparing SD card” after I had made the goldcard.
Worst part was when I finally downgraded my Hboot, alphrev X still wouldn’t work for me. Continued to get the error of “Retrieving Caroline from certain doom...” and "mtd: not writing bad block at 0x00000000" I've since given up..
okays, thanks for the help, ill try that, but with alpharevx the problem they are tring to fix is the part where you need to restart into fastboot the second time, so in this case, ill give that a try. the thing is that im useing windows 7 enterprise, i have the hboot drivers all installed and etc, i used the intructions given to me and everyone else where you have to make the gold card. in that intruction it stated to put the sd card into the usb or sd port, the thing i did was switch my phone to mount the SD card and create it via there, i think the part where we all went wrong is unmounted it after we finished making the sd card. so try that, and with your problem i tghink you need to try and run the program in ADMIN mode (right click and run as admin) and then try and get the HBOOT drivers from Unrevoked installed. give that a try and hope it all works out
cheers
Well I managed to get step2.bat to run in a cmd so that it stayed open,
it came up with "FAILED <remote: 42 custom id check fail>".
when HTC booted in to bootloader it still showed same h.boot (.0002)
Please see attached screenshot.
Question!! / problem!!
GlennBrownie said:
Hello,
I'm new to the forums, and have only just recently got a HTC Wildfire A3333 running 2.2.1.
I have tried to use " [GUIDE] Downgrade to HTC Froyo WWE for AlphaRevX (HBOOT 1.01.0001) " to downgrade the h boot as to start to gain root.
But when I have followed the instructions, it appears to complete ok, but when I reboot in to the system menu, it still shows as .002 hboot and does not install the rom supplied.
any help would be great
GlennBrownie
Click to expand...
Click to collapse
my question is, when i run alpharevx, it asks me for the beta key, note that it doesnt show my device name or anything like how i did it before i downgraded, any ideas why? and does anyone have a beta key for me to use? because the one i got with my phone when i entered it in said it was incorrect, when before before i downgraded it worked perfectly fine (except the rotting part).
what Beta key, I dont recall one?
To get a new beta key just follow this link, click download and then enter your phone's SN.
http://alpharev.nl/x/beta/
GlennBrownie said:
Well I managed to get step2.bat to run in a cmd so that it stayed open,
it came up with "FAILED <remote: 42 custom id check fail>".
when HTC booted in to bootloader it still showed same h.boot (.0002)
Please see attached screenshot.
Click to expand...
Click to collapse
Make sure you properly created a working gold card. Retry with gold card.
Sent from my HTC Wildfire using XDA App
technolust109 said:
my question is, when i run alpharevx, it asks me for the beta key, note that it doesnt show my device name or anything like how i did it before i downgraded, any ideas why? and does anyone have a beta key for me to use? because the one i got with my phone when i entered it in said it was incorrect, when before before i downgraded it worked perfectly fine (except the rotting part).
Click to expand...
Click to collapse
If it doesn’t show your device properly just reboot your phone. Basically every time the program fails it won’t show your device properly until you reboot again (This will also fix the issue where it thinks you have the wrong beta key). People suggesting to go get a new beta key have no idea. Have they not noticed that it doesn’t matter which HBoot version you select on the site you still get the same key based on your serial number.
yes, i used mt wildfire SN and i use the code it gives me still getting the same problem,
nejc121 said:
To get a new beta key just follow this link, click download and then enter your phone's SN.
Click to expand...
Click to collapse
currently running windows so cannot download as windows version under review.
bharatgaddameedi said:
Make sure you properly created a working gold card. Retry with gold card.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
completed program and it had a pop up saying something like, "success, you now have a gold key"....
GlennBrownie said:
Well I managed to get step2.bat to run in a cmd so that it stayed open,
it came up with "FAILED <remote: 42 custom id check fail>".
when HTC booted in to bootloader it still showed same h.boot (.0002)
Please see attached screenshot.
Click to expand...
Click to collapse
in other words, your goldcard is not created correctly.
ieftm said:
in other words, your goldcard is not created correctly.
Click to expand...
Click to collapse
done it twice and it still come up with success message?
even did it through hex editor....
I tried to do it again to show screenshots.
firstly, I ran step one and it says "cannot stat" followed by file name and says "no such file or directory". see image1.jpg
I then checked the buzzdowngrade folder, and all files are there. see image4.jpg
I then attempted the goldcard, and I clicked get cid, and it loaded a CID with a lot of 0's in it so I dont think its showing correct CID, possibly hiding real CID?
image2.jpg
when I clicked patch MMC, it came up with an error message. see image3.jpg
Have you installed the HTC driver 3.0.0.007. If not, install it first before even going with step1.
And regarding step2, creating a working gold card is important. If you still get custom id errors, try with a different memory card. And run the gold card tool as administrator. And in that you will see mmc0 and mmc1 options. Try creating with the other if one fails.
Sent from my HTC Wildfire using XDA App
GlennBrownie said:
I tried to do it again to show screenshots.
firstly, I ran step one and it says "cannot stat" followed by file name and says "no such file or directory". see image1.jpg
I then checked the buzzdowngrade folder, and all files are there. see image4.jpg
I then attempted the goldcard, and I clicked get cid, and it loaded a CID with a lot of 0's in it so I dont think its showing correct CID, possibly hiding real CID?
image2.jpg
when I clicked patch MMC, it came up with an error message. see image3.jpg
Click to expand...
Click to collapse
Just downgraded and i think i know what is the problem.
You have to change the connection status from charge only to Mass storage
then click refresh and the memory card will be available.
HTC MMC : select you sd card.
And now patch.
right, got an update.
managed to succeed with the dmisc.img and others that failed - thanks to Mattyyey, cheers Matt
We then got to flashing the rom and it failed, any suggestions?
we recreated the gold card and formated the microSD card and patched and it told us that it had succeeded.
please see screenshot.
bharatgaddameedi said:
And regarding step2, creating a working gold card is important. If you still get custom id errors, try with a different memory card...........Try creating with the other if one fails.
Click to expand...
Click to collapse
its probably your fake SD card! I was able to run the commands in step 1 and 2 from the cmd, all but the final ROM flash. I think after we create it we should confirm its been put on the SD card via hex workshop.... I did think of this last night but I was getting tired and you dont have it installed. I suspect its just the goldcard isn't done, everything else works when typed manually into cmd.
Unless anyone else has another reason for the custom ID check failing?
MATTYYEY was correct, it was due to fake microSD card, completed gold card with authentic SD card and it worked.
Sent from my HTC Wildfire android 2.3.4 Cyanogen V7.1 ROM using XDA App, GREAT rom running perfect.
Hi folks,
Have been going round in circles trying to root and flash my mate's DHD. I've been reading various threads and trying various methods but to no avail.
His DHD was originally on Froyo 2.2 and he took the T-Mobile OTA update to 2.3 w/Sense 3.0 when it was rolled out. As I understand it, it must be downgraded back to 2.2 before we can get full root access?
I've installed SDK on my PC and have been able to push tacoroot and misc_version to the phone. However, when running tacoroot, it reboots to go into recovery and I get the red triangle with the exclamation mark. The phone won't boot into recovery manually either. I've already done a factory reset to see if that helped, but no joy.
What am I doing wrong? Should the phone be able to access recovery completely stock? I never had this much hassle with my Desire - can't believe the DHD is such a pain in the backside. He has the phone with him now (he needs it tomorrow) but we're going to re-attempt tomorrow afternoon.
Am I doing things in the right order? Why do I keep getting the red triangle when trying to go into recovery?
Your help would be much appreciated!
well, as far as i remember you need to downgrade to 1.32 specifically.
and another thing, have you tried using advanced hack kit? it is pretty much one click solution, but can be tricky if the pc it runs from is not compleatly clean.
Try this on an Ubuntoo live CD, http://forum.xda-developers.com/showthread.php?t=1259821
worked like a charm for me..
I'm running Windows and followed the Hack Kit instructions to the letter. We're making more progress than before, but have run into the following problem:
[Would you like to downgrade? y/n]y
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
1690 KB/s (259503624 bytes in 149.887s)
Setting up to temproot....
cannot open 'tools/bin/zergRush': No such file or directory
1707 KB/s (572752 bytes in 0.327s)
1204 KB/s (19240 bytes in 0.015s)
going for temproot using zergRush....
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Error opening input file.
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
/dev/block/mmcblk1: cannot open for write: Permission denied
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
If downgrade is successful, you may set up the phone and try to hack it again.
Once the downgrade is successful, press a key to return to the menu......
Otherwise, cut and paste the output to the screen into a text file for evaluatio
n.... then press a key.
Press any key to continue . . .
The phone checks in HBoot and then comes up with:
"Main Version is older!
Update Fail!
Press <power> to reboot"
Any ideas? I'm drawing a blank.
Edit: Although I don't think it's a Windows issue, I'm downloading the Ubuntu live disc and will try it with that.
You have a couple of issues from the output you posted. In the beginning it couldn't find the zergrush files to temp root. This leads me to believe it was a bad download of kit. Did you verify the md5 for file integrity? And the second was an error with the SD card. You might want to try a different one
Sent from my Inspire 4G using XDA
Checked the MD5 - came back fine. Have swapped the SD card for another one - formatted to FAT32 with nothing else on it.
Will re-run.
Still downloading the Ubuntu disc (!) so will try that in a mo if a re-run with a new SD card doesn't work.
Thanks for the input, much appreciated!
Edit: Exactly the same issue again. Will try it under Ubuntu.
Funkmeisterdude said:
Checked the MD5 - came back fine. Have swapped the SD card for another one - formatted to FAT32 with nothing else on it.
Will re-run.
Still downloading the Ubuntu disc (!) so will try that in a mo if a re-run with a new SD card doesn't work.
Thanks for the input, much appreciated!
Edit: Exactly the same issue again. Will try it under Ubuntu.
Click to expand...
Click to collapse
That doesn´t seem to be an sdcard issue. Download the Kit again and extract it all in the same folder...The cases experiencing your issue are mostly for missing files in the hack kit.
Look this in the code you pasted: "...cannot open 'tools/bin/zergRush': No such file or directory..."
glevitan said:
That doesn´t seem to be an sdcard issue. Download the Kit again and extract it all in the same folder...The cases experiencing your issue are mostly for missing files in the hack kit.
Look this in the code you pasted: "...cannot open 'tools/bin/zergRush': No such file or directory..."
Click to expand...
Click to collapse
I guessed the issue with the missing files but he said the md5 check out.
I mention the SD card because of the line of error writing to mmcblk1. After the line creating goldcard, but you spend more time helping out in the irc to know better than me
Sent from my Inspire 4G using XDA
marsdta said:
I guessed the issue with the missing files but he said the md5 check out.
I mention the SD card because of the line of error writing to mmcblk1. After the line creating goldcard, but you spend more time helping out in the irc to know better than me
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Yeah, those are the cases I have seem, but maybe something different comes out....it is hard to know without the whole information...
Thanks to everyone who offered ideas and support; I've finally managed to do it.
<hugesighofrelief>
Thanks again, also to the chaps and chappettes in the IRC support channel.
F
Marvelc Problem SolvingWe all have problems with our Marvelc, so why isn't there a guide for it? There is.
If you're having issues, check out my guide at http://teamblueridge.com/marvelc-problem-solving/ for how to fix the most common issues.
You don't have to live with a hard-to-manage Marvelc anymore.
Changelog:
May 24, 2012 10:12 PM EDT
Added a link to vbhtt's tutorial for solving different brick types.
July 19, 2012 8:04 AM EDT
Revised guide to say that all Marvelc HBOOTs can be S-OFF'd.
August 7, 2012 3:48 PM EDT
Revised to say how to fix <remote: not allowed>
Explain issues with Three-Vibe Brick
August 7, 2012 4:59 PM EDT
Link to guide on Team BlueRidge site.
Three Vibe Brick
So far, no 100% guaranteed method has been found to cure the infamous three-vibe brick. Your phone is presently in Qualcomm Diagnostics Mode
Click to expand...
Click to collapse
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
vbhtt said:
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
Click to expand...
Click to collapse
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
kalaker said:
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
Click to expand...
Click to collapse
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
vbhtt said:
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
Click to expand...
Click to collapse
Oh! I understand that! I was just trying to provide a common method that I had read. I understand you weren't saying I was wrong. I was actually about to add something about your tutorial, but I had another project I was working on.
Yes, my goal is that this can be a place to help most Marvelc users solve most of their problems with as many alternatives as possible while still being fairly noob-friendly.
Thank you for reminding me of your tutorial as it slipped my mind while I was writing this in the beginning!
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
CoLlisiionZz said:
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
Click to expand...
Click to collapse
What you need to do is download ClockWork Mod 5.0.2.8 from http://download.clockorkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.img and then rename it to recovery.img. If you're on Windows, put it into the same directory as your ADB and fastboot commands. Next, you'll need to put your phone in fast boot mode. Go into HBOOT and choose "Fastboot" by scrolling with the volume keys and selecting with the power key.
Connect your phone to your computer.
Next, depending on the OS of your computer, launch Command Prompt (Windows) or Terminal (Linux/Mac). Navigate to the directory with recovery.img. Now type: fastboot flash recovery recovery.img and then power off your phone when it's done.
Now boot into recovery. Go to HBOOT and choose recovery. Now, get on your computer and find a ROM that you like (something fairly stable). Download it. Find Simon's super wipe. Download it.
Connect your phone to your computer (if you removed it earlier).
In recovery, scroll to Mounts and Storage. Go to USB Connect or something similar (it will be near the bottom). Then on your computer, place your desired rom and the super wipe. Remove the phone from your computer and choose "Go back" on your phone. Go back to the main menu.
Backup.
Flash the super wipe. Then flash your ROM.
Go back to the main menu and reboot.
Sent from my NookColor using XDA
Great!! thanks this seems legit I will try this as soon as I get to my PC uhm I have windows btw and have no clue how to put the cwm into my adb / fastboot directory but I will search more about it when possible thanks for your help
Well, if you're on Windows, you should have a directory like C:\Android\ or something like that.
If you're on a Mac just do:
Code:
fastboot flash recovery /path/to/recovery.img
If you want to have the file anywhere on Windows, you still need to have fastboot somewhere and then do the same command I just typed above.
For more instructions, follow the instructions in the guide under "I can't flash a custom recovery"
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
CoLlisiionZz said:
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
Click to expand...
Click to collapse
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
kalaker said:
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
Click to expand...
Click to collapse
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
CoLlisiionZz said:
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
Click to expand...
Click to collapse
That's what you want. Move them into a folder at the root of your hard drive (C:\) called "Android". (C:\Android\)
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
CoLlisiionZz said:
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
Click to expand...
Click to collapse
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
kalaker said:
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
Click to expand...
Click to collapse
Okay that's what I kind of thought so I tried typing fastboot flash recovery recovery.img
and it says
error: cannot load 'recovery.img'
it is placed in the same directory as the tools are too.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
Okay nvm I tried something and it worked!!!
I went and re downloaded your CWM on your tutorial and deleted the one I renamed and didn't rename it this time just kept it the way it was I then tried flashing it and success I'm now going to reboot my hboot and see if it worked but also I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
CoLlisiionZz said:
Okay that's what I kind of thought so I tried typing I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1598143
I'm glad to hear you got it working!
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
insink71 said:
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
Right, a Goldcard (unless one is S-OFF or ENG) will be required. However, achieving a goldcard requires ADB access to your phone. (The Simple GoldCard tool reads a file in /proc/*/*/ I believe to get the CID required for goldcard.) Now, ADB access is quite difficult with a bricked phone as you cannot boot into Android (or recovery) and to get S-OFF you would need to borrow the HTC Wildfire S (it MUST be a Wildfire S) to get the goldcard required.
Even with what I just said, depending on how bad your phone is bricked (Flashing a GSM RUU, for example), you may have a 100% bricked radio, thus resulting in an entirely bricked HBOOT not allowing you flash a PG76IMG.zip.
Another idea I have is that the Marvel is a PG761**** for the model number, and an incorrect RUU is the most common brick for Marvelc. What may be an issue is that the Marvelc is a PG762**** model number. The current files we have for un-bricking are Marvelc, but the android-info.txt for modelid says PG762000, therefore a GSM HBOOT (especially a locked, RUU HBOOT) would not take that file as it is for Marvelc.
What I think would be necessary is: a goldcard + a PG76IMG.zip with a GSM android-info.txt, but Marvelc radio, ROM, HBOOT, etc.
This is my idea on how we may need to do this. However, as the GSM HBOOT cannot get S-OFF without XTC-Clip which we can't use due to a lack of SIM card slot.
To get a 100% working-in-all-methods 3-Vibe Brick Recovery Method, we are waiting for the people in the S-OFF thread to get a full software S-OFF. However, even with that, we may still have issues...
I have spent a lot of time thinking about this, actually. (I'm a planner; not a dev :crying: so I can't be of much help with the dev part.) However, if it ever becomes a Team BlueRidge project to fix this type of brick (or a project by any group) I will be happy to plan (but not test just yet).
Since now we're moving into a very difficult and not-so-noob-friendly as I am intending for this thread to be, it may be a good idea to either start a new brainstorming thread or to PM or IRC or something.
Anyway, those are my thoughts.