Related
I'm attempting to root my HTC Desire, but having some problems.
I am following the guide here: theunlockr .com /2010/06/07/how-to-root-the-htc-desire/ but I haven't made a goldcard because my device is unbranded. Perhaps this is where I went wrong?
Everything seemed to be going fine until: 7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish.
The command prompt flashes briefly, but I took a screenshot and the error was 'device not found'
I'm really not sure what to do at this point..
Thanks!
Flaphal said:
I'm attempting to root my HTC Desire, but having some problems.
I am following the guide here: theunlockr .com /2010/06/07/how-to-root-the-htc-desire/ but I haven't made a goldcard because my device is unbranded. Perhaps this is where I went wrong?
Everything seemed to be going fine until: 7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish.
The command prompt flashes briefly, but I took a screenshot and the error was 'device not found'
I'm really not sure what to do at this point..
Thanks!
Click to expand...
Click to collapse
Have you got HTC Sync installed? This is not a goldcard error as that would be Custom ID Error
Did step 1 complete correctly?
There is no step 2 anymore on modaco's method
try following this guide as it is the original post by Paul and all others are just copy/paste's (or bad rewritten) guides
I do have HTC Sync installed, yes.
Step1 did appear to complete correctly, but at one point I spotted the word FAILED in command prompt, but they everything continued apparently at normal.
My phone is currently at the recovery screen with the ! is it safe to pull the battery? It isn't responding to the power button.
The FAILED error was something like.. 42 device id check fail
Yeah if you are at the red triangle then you can pull the battery..
I'd use the guide on modaco. It's foolproof and very easy to follow.
Yes, it's safe to pull out battery.
I had the same problem with step 2, then I've found out the modaco method without step 2, and it worked out fine.
I would do the rooting under Linux!I had enough trouble with it under windows (maybe because of x64).
Sent from my HTC Desire using XDA App
reason for "device not found" is missing drivers for bootloader mode.
believe me, its much more easier to root your device under Linux liveCD, than cheating with drivers for windows.
good luck
The riskfree method on modaco works perfectly. I unrooted by using a stock ruu earlier to remove unrevoked, and use the riskfree method to root again. It's easy and painless on win7 64bit.
I think the step one didn't complete properly for the OP anyway as he said he seen an error at that stage.
Ok, using the riskfree modaco method now. Everything fine until installing update from SD card. E: failed to verify whole-file signature. Esignature verification failed. Installation aborted.
Is this due to not using a goldcard? I tried to make one but it kept saying it the card was damaged and needed formatting each time.
Edit. also the email I get in the goldcard creation process has the subject 'Your generated G1 goldcard' I'm not sure why it says G1? but the gold card process doesn't work and says I need to format the disk for it to be usable.
In the first posts you said your device is unbranded. So why did you made a goldcard? It's not necessary
Also make sure to use the files as you can download in the Modaco thread I posted in post #5
I think I must have misunderstood what unbranded meant. Or maybe it was just a coincidence, but it worked once I used the goldcard.
The phone came from T Mobile, but lacks and T Mobile branding on the case or any T Mobile apps.
Then it's proberly branded, you can verify by the ROM version (search the forum for it). I don't think it can harm to use a goldcard with a non-branded device anyway (correct me if i'm wrong).
Also try to download the files from the Modaco forum again (and don't rename any files)
If that doesn't work, take a look at these search results. I can remember I had the same problem as you have, dunno exactly what solved it, but these search results def. helped me
I've noticed a few posters on here are from N.Ireland and was wondering if any of you would root my phone? For a fee of course?
I'm a complete noob at this, I've spent the last four days reading guides and I just can't get it to work. Can get the tinycore linux working on my macbook but can never get past entering this in the terminal:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/desire After I press return here I get an error.
So I've now thrown in the towel and was hoping a local Android geek could help me out lol
Cheers
Joe
Are you using the TinyCore Live-CD from the MoDaCo guide or the r4 one posted by craigcrawford? the latter had an edited TinyCore build made which was slightly different to the normal one originally posted...
Have a read of this guide, by craigcrawford, never fails to work (so long as you download the right Live-CD - check your HBOOT and download accordingly):
http://android.modaco.com/content/h...sire-easy-rooting-guide-with-tiny-core-linux/
Thanks for the reply, yeah thats the one I'm using. Could it be my tinycore setup? I can't get it to boot from CD so setup a virtual machine on my macbook and ran tinycore through that.
Sorry if that doesn't make sense, I'm a complete noob at all this
Not being an Apple man I don't know if you can boot a Live-CD using a Mac but shouldn't see why not!
Also don't see why a VM wouldn't work but again I've always used a PC and it boots fine so might wanna see if you can borrow a Windows laptop and use that (or, if you're ever in Liverpool, come see me and I'll do it)
Ok going to try it again, I had already installed Linux VM before I downloaded the r4 and didn't know there was Tinycore ISO included with it.
So I've setup a new VM with the ISO from craigcrawford and I'm going to try it one last time. Just want to check something before I start, my phone is unbranded so I'm not using a goldcard do I need to put the rootedupdate.zip on the SD card before i start?
joe_998 said:
Ok going to try it again, I had already installed Linux VM before I downloaded the r4 and didn't know there was Tinycore ISO included with it.
So I've setup a new VM with the ISO from craigcrawford and I'm going to try it one last time. Just want to check something before I start, my phone is unbranded so I'm not using a goldcard do I need to put the rootedupdate.zip on the SD card before i start?
Click to expand...
Click to collapse
Correct, no Goldcard required. Should take about 10 mins all in (did for me on a W7 x4 Ultimate-based machine). Good luck!!
Cheers Eddy, here goes! I'll post how it goes!
Ok getting a bit further into it. Says rebooting into bootloader... FAILED
but then says Step 1 complete and gives instructions on how to continue.
I'm confused
Uploaded with ImageShack.us
Forgot to add, my phone didn't do reboot nor did the screen change at all
Yeah thats not working correctly...something's not right, be it running through a VM or otherwise...
I'd say it might be worth asking advice on (or taking a look at) the rooting guide on MoDaCo as more people there can help (and it works from within a Mac natively)
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/
Ok Eddy thanks for your help mate.
Going to phone round a few repair shops in belfast and see if they can do it! It's really started to p*ss me off now!
Would they want to do it, though? I doubt they'd want to potentially brick your phone and have to buy you a new one
What HBOOT are you running on btw?
Well I know of one shop that jailbroke a friends iphone so I'm going to try them to see if they'll give it a go!
I'm running HBOOT 0.80
Right, here's a little guide for a Mac:
- First, download THIS and extract it on to the Mac equivalent of the Desktop
- Copy the 'update.zip' to your SD card - do NOT rename it
- Now open a Terminal window (go to Applications>Utilities, double click 'Terminal' icon) and change directory to the extracted folder. Turn your phone on holding down the back button and you should be in the FASTBOOT screen. Plug your phone into the Mac and it should then read FASTBOOT USB
- In the terminal window type './step1-mac.sh' (without ') and when it finishes it will take you back to the FASTBOOT screen. Press the power button and it will change from FASTBOOT to HBOOT USB
- Select 'Recovery' and when at the screen with the red ! hold vol up and press the power key.
- Select 'wipe data/factory reset' and once complete select 'apply:update.zip' and once this is done reboot the device and you should be rooted
"Now open a Terminal window and cd to the extracted folder"
Eddy I haven't a clue how to open a terminal window and cd to the extracted folder, thats why I was trying the Tinycore guide.
Sorry for being such a noob
*Updated guide above
Don't know what else to put as I'm a Windows man, never used a Mac
Ok think I understand that. Just waiting on the r6 to finish downloading then I'm going to have another crack at it!
Thanks for putting that together Eddy, much appreciated.
Joe, if you are still stuck I should be able to help you out tomorrow free of charge. I think your bootloader is the same version as mine (can't remember off hand) so I still have the files on my netbook to do it, or at least should have.
Still can't get it to work.
Kerso, I'll take you up on that mate, Where abouts are you?
Eddy, thanks very much for your help mate
I am a Mac user but rooting is loads easier on a Windows machine, had mine rooted in no time using a XP based PC.
To open a Terminal window, just click on the magnifying glass search icon type in Terminal and it will appear in the list of matches, just double click it.
CD = change directory in the terminal, that's all. ie CD to the directory where you downloaded the folder it to.
Trouble I had was that OSX was unzipping the downloaded file on completion, I'm not sure how to stop it doing that.
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder
In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.
im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally
drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.
how did you get it too work???
simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2
I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.
nothing is working out for me this is not fun
same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.
yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that
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.