Related
Because of my stupid mistakes of making my SD card failed the first time, I found a way to actually downgrade the system using HBoot mode even if you have a new HBoot system (i.e. Official Chinese version, Carrier Locked version, etc).
First thing to do, is to download the 2.73.405.5 official WWE RUU package (the exe);
Then, run that wizard, and while the wizard's program is running, search in your PC's %userprofile% folder, and look for "rom.zip"
Rename that rom.zip to HEROIMG.zip.
Put that file into your MicroSD card's root folder. Do not modify its contents.
put that SD card into your phone.
While the card is in, hboot the device (vol down + power).
it will pop up the HBOOT mode of the device. It will now check for a few files if they exist on your SD card. (HERODIAG.zip, etc)
in the last check, it will look for HEROIMG.zip, and tries to load it. Once the loading bar is complete on the top right side of the device, it will ask you to press home to continue the upgrade, or press other key to escape it. (i am not 100% sure if those are the keys, but you can read english so figure that part out).
Once the flashing is done (remember, this method will wipe everything. including radio, recovery, system, data, cache), you will now have a complete original ROM on your system. From there, use InstantRoot or any other rooting exploit, to root your device, put Cyanogen's recovery there, and start upgrading into custom roms!
Let me know if this method works or not. it worked on 3 of my friend's HTCs.
/* p.s. however i still have my unresolved issue about the SD card slot and USB device not recognized issue. */
Nope, I tried that before and it fails the CID check.
Guiness in a can? BRILLIANT!
yea, everyone has been jumping through their butts trying to figure out how to make goldcards and bypasses... why not just use hboot like htc probally uses it? Duh! Thanks for this!
edit..... oh snap....
does not work for me!
Once the loading bar is complete on the top right side of the device
go back to hboot...
and nothing to do
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Otiginal IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Original IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Thank you, you are the man!
Thank you so much, i was about to eat my phone. it is htc hero and it worked. thank you so much...
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
kendong2 said:
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
Click to expand...
Click to collapse
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
anon2122 said:
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
Click to expand...
Click to collapse
Might be worth a test to do self signed ?
Jesterz said:
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Click to expand...
Click to collapse
hi, i have the same problem and my cid is in in the list.
what could be the problem?
How the hell did you came up with that?
It worked perfectly! Cannot thank you enough.
You're the man.
been looking for this for nearly a week.
got my wife a new phone and want to store it original, but couldnt get back to stock,all cid fails.
with this version no cid fail and stock htc hero again.
thanks, you tha man.
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.
Alright, so, I guess I'm not the only person having issues with the current versions of ICS, which is kinda comforting. If you can't update your SU binary in an ICS rom because your SU app tell you you're not S-Off, that means the bootloader partition was somehow damaged and forgot you're S-Off, so here's a detailed guide of what I did to get my phone up and running again.
This is also a great guide to help fix any stability problems your phone is having in general.
If you just need to unroot to send the phone back to Verizon or to sell it to someone, stop after step 17 and reading everything after it, but before step 18.
***WARNING***
If you do not follow these directions perfectly, you have a chance of damaging your phone. Part of this process involves flashing hboot manually through ADB, which is dangerous. PLEASE PAY SPECIFIC ATTENTION TO THAT SECTION OF THIS GUIDE. If you don't, your phone is going to be a very depressing paperweight.
IF AT ANY TIME YOUR PHONE TRIES TO ACCEPT AN OTA YOU NEED TO DENY IT! Because of how the Revolutionary Team's S-Off Tool works, we need to be in Froyo to flash hboot manually. An OTA will only get in the way!
Make sure your phone has a decent amount of battery (More than 50%) and keep it plugged in whenever you boot to hboot to be safe. If your phone powers off or dies when flashing a PG32IMG.zip, BAD BAD BAD things will happen!
I am also not responsible for anything that happens to your phone. If you're rooted and S-Off, you already know the dangers, so be smart!
Before I get started though, I have some people to credit, as their tools are used in this guide.
Thanks to:
notluK for his Unroot Guide on Android Central. Pretty much all of this guide is a direct kang/plagiarization from him, with minor changes due to file hosting fiascos.
CLSShortFuse for his SuperOneClick tool
The Revolutionary Team for their S-Off Tool
The unrEVOked Team for hosting the HTC Fastboot drivers
I think that's it... now, for your bacon.
NOTE: I do not have the original md5 sums for these files, so don't ask. Just download over a reliable connection (NOT ON YOUR PHONE!).
Pre-Requisites:
HTC Fastboot Drivers
Android SDK
Froyo (2.2.1) PG32IMG.zip
Gingerbread (2.3.3) PG32IMG.zip
Super SU ZIP from here
And a significant amount of time and patience
Okay... here goes. Please make sure to keep all of the above files on your PC to be safe. They are always good to have in case your phone goes screwy.
1. Download and install the Android SDK, install the HTC drivers and then reboot your PC. (If your SDK is fully functional and you already have the Fastboot drivers installed, just skip this step.)
2. Put the Froyo RUU zip on the root of your SD card and rename it to PG32IMG.zip (if Windows is hiding your file extensions, don't add the .zip to the end).
3. Boot your phone into the Bootloader (Vol Down + Power while off)
4. Press Vol Up to accept the update
5. Reboot phone when done (It may power off to a black screen instead of actually rebooting. Don't panic, just turn the phone on like you normally would ) When it's done booting, delete the PG32IMG.zip from the SD.
6. Check your OS version under Menu>Settings>About Phone>Software Information. Verify your OS version as 2.2.1.
7. Enable USB Debugging under Menu>Settings>Applications>Development
8. Plug in your phone and run the SuperOneClick root tool. When it asks if you want Busybox installed, say Yes. This is important, as you will need Busybox to verify the md5 of the hboot image you are about to flash to your phone manually.
9. Reboot your phone
10. Find the Froyo PG32IMG.zip on your computer and find the hboot_0.97.0000_336906.nb0 file inside. Extract it and put it in the platform-tools folder of your SDK.
11. Make sure your phone is still plugged in and then open your Command Prompt/Terminal and cd to your SDK's platform-tools folder, and follow the adb commands below, with your phone still plugged in, of course!
EXAMPLE: This is where mine is, yours may be different, so check!
Code:
cd C:\android\platform-tools\
Once that's done, continue:
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
12. Now, do:
Code:
adb shell
su
/system/xbin/busybox md5sum /data/local/hboot_0.97.0000_336906.nb0
If your answer is not affe3dc9abe9d3a8c8bb3ba0ee5176ac, stop now and reboot your phone, then start over again at step 11.
***WARNING***
If you skip this step, you're a big, dumb idiot. This next step involves flashing something to what is probably the most important partition on your phone. If you mess this up, no one can help you, and your phone is permanent brick.
13. If the md5sums match, continue:
Code:
adb shell dd if=/data/local/hboot_0.97.0000_336906.nb0 of=/dev/block/mmcblk0p18
14. Verify the partition's md5sum to be extra-safe. If it's not exactly the same as the original md5 above, DO NOT REBOOT YOUR PHONE! Just start at step 11 again.
Code:
adb shell /system/xbin/busybox md5sum /dev/block/mmcblk0p18
15. Go into your Settings and disable Fast Boot (I don't remember where this is on the 2.2.1 firmware, so look around until you find it). Now, put the 2.3.3 PG32IMG.zip on the root of your SD and boot into hboot like you did before (Vol Down + Power while off).
16. Press Vol Up to accept the update.
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
18. Run Revolutionary like you did before and accept the installation of ClockworkMod recovery (It'll be an old version, but that's okay).
19. Put the SuperUser zip from earlier on your SD and flash it like normal. (Backup first if you want to have a backup of factory stock unrooted)
20. Profit!
At this point, your phone is now at root 2.3.3 stock and S-Off again! Update your ClockworkMod recovery (or use 4ext, which I like a lot), make a backup (PLEASE, MAKE A BACKUP!) and then flash the rom of your choice, probably an ICS one.
Feel free to update your radio and stuff too. Things should be working much better than before.
And, to be safe, never OC past 1.3ghz. You shouldn't ever need to anyway, and it can break things, which means you'll have to do this all over again. Overclocking too high and my phone overheating is how I got into this situation in the first place, so I'm not just blowing hot air here. (Haha, get it? )
If anybody has any questions (please, don't bombard me with them ), feel free to post here and I'll do my best to respond in a helpful and timely manner.
If this helped you, click the "Thanks" button, or I'ma find you!
Happy flashing!
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
RegnierD said:
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
Click to expand...
Click to collapse
Links are definitely bad. Any chance you still have the files?
I found the Froyo RUU, but I still need the latest Gingerbread RUU.
This helps a lot thanks
Reg, could update the links for the Froyo and GB RUU's? Thanks!
I'll post new links sometime today, guys.
RegnierD said:
I'll post new links sometime today, guys.
Click to expand...
Click to collapse
Thanks you!!
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Does anyone have the 2.3.3 stock kernel? I tried another and now wifi won't enable
nevermind!... lol
my phone isn't charging (read that many users have had problems with the charging port on this phone), i just unrooted and s-off'ed. i'm on froyo now. should i download 2.3.3? where can i get it and would that be enough to get a new phone under warranty? or do i need to have the latest OTA 2.3.4? thanks in advance and i apologize for all the questions
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
Now stickied
If I helped, give thanks, if you please.
........Death before dishonor........
hokieputter said:
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Click to expand...
Click to collapse
which one should i download if i just want the stock 2.3.3 so that i can return my phone for warranty? thanks.
The links are bad. I need the two PG32IMG files... My phone is not fairing well =/
S-On
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
smayer85 said:
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
Click to expand...
Click to collapse
RegnierD said:
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
Click to expand...
Click to collapse
Reading helps.
I cannot get android SDK to install, it says "Java SE Development Kit (JDK) not found. Error: Failed to find Java version for 'C:\Windows\system32\java.exe': [2] The system cannot find the file specified." I have went and tried to install the java it says to but that won't work either. Should I uninstall any java I have installed and try then? My phone bootloops everytime i restart causing me to factory reset it so I need to get a replacement. Thank you.
Edit: Got the java to install after deleting and also have android SDK installing all the stuff now.
New issue, sorry for so many questions im kind of a noob, but when i try to adb root it says something about not able to in production. Does it affect me that my sdk folder in on a seperate HDD from c:\? I'm gonna try to redo it now and hopefully have this working this afternoon. Also, cmd will not let me cd to my SDK folder.
Mount error
When I enter the remount command an error is returned stating: adb remount failed: unknown error: 0
Anyone have any ideas how to resolve this?
Thanks
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.