~NOOB ALERT~
My G2 is bricked, and I'd like to know if its possible to fix. I have an sdcard reader and a Mac computer.
My G2 can boot into HBoot. When I select recovery, it takes me to the latest clockworkmod. I've tried every single option IN cwm to try and fix it, but it won't work. The recovery still allows me tl flash roms... but no matter WHAT rom I try it just boot loops.
My info:
Vision PVT Ship S-ON
HBOOT-0.82.000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 2 2010, 17:59:38
Someone PLEASE help me ):
wrong section
Sorry but I really need this fixed and ima noob to xda as well. My bad. Do you know what I can try?
Am guessing try to flash the new G2 2.3 update by football. You will lose being able to root though.
Also needs to moved to question section
Sent from my Htcclay's SuperCM7 G2 using XDA Premium App
Instead of freaking out, try to do some reading and gain a better understanding of what happened and what you can do to fix it. No one here is going to hold your hand. Sorry your phone got messed up, but it happens from time to time.
Search for a guide on how to root to S-OFF in HBoot. That's probably your only way of fixing your phone. You made the mistake trying to use root features while your phone is still S-ON. The reason why it boot loops when you're flashing roms is because you're not rooted, flashing roms is only for rooted phones with S-OFF.
1) Get your phone rooted with S-OFF by searching for a guide that roots the phone using HBoot. (Most likely you'll be using ADB on your Mac to root from HBoot. Look at the ADB for dummys guide stickied in the G2 Android Development section.)
2) After your phone shows S-OFF, flash a rom in recovery and reboot.
3) Your phone should work after that. If it doesn't, bring it to work for paper weight.
I think you can do this:
Download the rom from this thread, rename it to PC10IMG.zip and place it on the root of your SD card, reboot into bootloader, follow on screen instruction.
After this process is complete, you should boot into the latest leaked TMOUS rom.
Be aware that the rom above is not rooted, and I'm not sure if you can get s-off with the bootloader from that rom.
Or you can read the second sticky thread:
[REF] G2/Vision/DZ Links | Guides | Stickies | Recovery | Roms | Read before posting
You will find a lot of useful things there.
And I believe that your problem is already described and solved in the Q&A section.
Good luck!
Try this thread. You should do a search or read a little before posting in the wrong section. Good luck with your phone.
Related
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
andyharney said:
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
Click to expand...
Click to collapse
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well. Can I flash a ROM with just SHIP S-OFF? I don't want to flash any radios because I bricked my G1 about 4 million times when flashing radios.
It you run a 1.32 WWE RUU and revert back to stock you can then reapply ENG S-OFF. A bit of a ball ache I know.
Most ROMs will work just fine with SHIP S-OFF but ENG is usually preferred.
To flash a radio you need Radio S-OFF another beast entirely. However there is a very good too to do it with. No bricks so far and your DHD will then have super CID and be SIM unlocked.
didge3 said:
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well..
Click to expand...
Click to collapse
Just tick the "I have radio s-off" box and it becomes compatible with everything.
follow my guide in the sig and skip to eng s-off and radio s-off part, or skip to whatever comes next if you've already done them
Tried that, I get a "Connection Error", I have made sure its fully connected as "Disk Drive" and I allow the Super User request when I do it, but it still doesn't work, plus the radio tool just says "Incompatible kernel" - or something like that.
I mainly want to know, can I flash Android Revolution in my current situation, can I flash with just SHIP S-OFF and my current kernel, or do I have to go back to stock kernel, flash the ROM and then flash my kernel back?
and why should I have ENG S-OFF, if it makes a lot of difference I will give it ago, but I mainly want to just flash this ROM to see if it fixes my wifi issue and my camera doesn't drop so many frames! (known issue in 1.32, fixed in 1.7X)
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
jkoljo said:
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
Click to expand...
Click to collapse
I get the same as every other time, downloads the Easy S-OFF tool, "Pushing stuff to SD" Phone says "Unknown has been granted su access" and then the tool says "Error: Connection Problem!" - I get this every time, I have tried re-downloading this software every time, removing the "Unknown" in super user and then re-allowing it when it asks, I still get the same error...
Does it matter that I'm using Windows 7 64-bit?
EDIT: I think I've done it now, I downloaded the latest 2.3 SDK (I had 2.2) which updated my ADB drives, I didn't get the error this time, will boot into H-BOOT and check now.
Are you still using that disk drive mode? Because you should not.
THANKS
I have thanked everyones post, I can confirm my H-BOOT Now says PVT ENG S-OFF, one last thing, I'm all good to flash now? I can just put the ROM (sense version) on my SD card and flash it in CWM, with my current kernel, even though it will over write it with the one included for Android Revolution, I dont have to go back to stock kernel or anything first right?
Thanks again
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
didge3 said:
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
Click to expand...
Click to collapse
andyharney said:
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
Click to expand...
Click to collapse
Note the very first post "Clockword mod 3.0.0.6" so in answer, yes.
Your good to go then, happy flashing.
I can see that more is possible when you s-off but I need to know some things before I look at doing it:
Is it better to start from scratch: i.e unroot, re-root using unrevoked, THEN s-off my phone?
Will any AMOLED WWE RUU be good enough to unroot? (if its beter that i do)
For those of you reading this that have done it, which method do you reccomend? (Virtualbox, CD or whatever)
Thank you for any and all replies, I've already ruined one phone on my contract (i tried to OEM update after rooting stock rom :/) and i REEEEALLY don't wanna have to go thru that again. Honestly any and all tips other than answers to my questions are most welcome!
**Matty Matt**
Was your phone on Orange FW when you got it? If so, you'll need a gold card to flash a non-Orange RUU. If you're OK with this, use this one:
http://www.multiupload.com/LEJCW182AH
I'd say do a nandroid backup of what you've got, go back to stock and reroot then S-OFF and then restore your backup.
As for doing the S-OFF, burn it to a CD and boot PC from the CD
Matty Matt said:
I can see that more is possible when you s-off but I need to know some things before I look at doing it:
Is it better to start from scratch: i.e unroot, re-root using unrevoked, THEN s-off my phone?
Will any AMOLED WWE RUU be good enough to unroot? (if its beter that i do)
For those of you reading this that have done it, which method do you reccomend? (Virtualbox, CD or whatever)
Thank you for any and all replies, I've already ruined one phone on my contract (i tried to OEM update after rooting stock rom :/) and i REEEEALLY don't wanna have to go thru that again. Honestly any and all tips other than answers to my questions are most welcome!
**Matty Matt**
Click to expand...
Click to collapse
1) You won't need to unroot, I S-OFF'd when I was using Oxygen RC1 and it was unaffected.
2) Any WWE RUU should suffice, but you won't need to unroot.
3)CD is by far, far, far the easiest method.
thanks for that, and thanks for the link! I believe there's also a TUT on theunlockr.com that I found with some tips too.
EDIT: thanks Kalavere so at the moment it's CD: 2 USB and Virtualbox: 0 LOL
+1 for not unrooting. In fact have a read of this thread I posted when I was trying to s-off. Never did get to the bottom of it, but it seems something in rooting stock rom and creating a goldcard stopped me from doing it.
Once I flashed a custom rom it was fine!
http://forum.xda-developers.com/showthread.php?t=987739
Yes CD method for sure.
Interesting, so by the looks of things it would save me hassle by not un-rooting! right well I think i'm gonna give this a bash this weekend/tonight depending when i have more time. Keep the advice/experiences coming guys!
It's not the hassle, it's just I prefer to do things properly and I've never had any issues doing it from stock. As said, do a nandroid before you unroot and you'll be good to go back to the ROM you're currently using once you're all done
Here is a fool proof how-to guide from DicsoHero over a MoDaCo, he helped me S-OFF my Desire back in December, it might be of use to you.
DiscoHero said:
AlphaRev 1.5 How To Get S-OFF
I am writing this from memory as I S-OFFed my phone sometime ago but here is how to do it. No responsibility if you brick your phone. This process is dangerous and may brick your phone so if you do not have a good reason to do it or do not know what it is, don't do it! Your phone should be already rooted for this to work.
1. Go to http://alpharev.nl/
2. Download AlphaRev 1.5 HBOOT reflash utility (first download link on the page)
3. Burn to CD / put on USD Stick using UNetbootin / Create VM (CD is the preferred way to do it ... "safer")
4. Boot computer from CD/USB while the phone is DISCONNECTED!
5. When prompted connect phone to computer using USB cable and follow instructions. Phone doesn't have to be in fastboot or anything, the program will reboot your phone for you. There are three steps to the entire process. Once you press enter and aknowledge that the process may brick you phone ... go make tea/coffee as it will take 10-15 minutes. DO NOT DISCONNECT your phone from the computer under any circumstances UNLESS EXPLICITLY TOLD THAT IT IS OK TO DO SO or you WILL BRICK YOUR PHONE!
6. Eventually you will be prompted to press any key to shut down the computer, that your S-OFF was a success and that you can enjoy your phone to the fullest now. Your phone will be in fastboot mode (if I remember correctly or may be rebooted fully). To check if you have S-OFF boot into fastboot and it should say ***AlphaRev*** and your HBOOT should be 0.93.001 now as in the screenshots posted above. Your splash boot image would have also changed (Search XDA for how to change your splash1 as it is doable in a few easy steps with "any" image).
Voila, you have S-OFF. You ROM should remain as is (the process only replaces HBOOT) while your recovery may or may not be there.
Click to expand...
Click to collapse
go back to stock with a RUU.
i tried to S-OFF while running GingerVillain and it didnt work, i thought i bricked my phone since it went past -STEP 3 DONT PULL BATTERY OR YOU WILL BRICK THE DEVICE- and it stopped working so i pulled the battery
then went to stock and rooted and S-OFFed without any problems
well as other replies, don't need to unroot But makes sure that the stock rooted rom you are running the process S-Off is using the folder /data of your system so it's advice not use data2sd or whatever 2sd... more there
I used the usb boot, takes 5 minutes only, rooted stock rom 2.29...
Virtualbox is probably the safest method, but is does take a lot more setup
AmonRa 2.0.1 | PVT4 40000 S-Off Alpharev 1.8| HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.2 (A2SD) | HTC Desire A8181 | UOT Kitchen Mods
I first rooted my phone using revolutionary-0.4pre4.zip file to get the s-off and then flashing SuperUser su-2.3.6.3-efgh-signed.zip. This worked just fine. I've been ok with the stock rom so I haven't changed it. I wanted the new update when it came out and some threads said I needed to UNroot in order to update. Therefore I ran PC36IMGson.zip which hasn't help me either, but now my phone is back to s-on but seems to still be rooted (since Titanium Backup, Rom Manager, and SuperUser are still working fine).
Now, I'm done with it all and would like to flash some other rom But I can't get back to s-off! revolutionary thinks it's still set to s-off each time I run it, but the bootloader screen still says s-on. Unrevoked doesn't work either since my device is unsupported.
Any ideas???
I'm pretty new to all of this and have been trying to figure this on my own with XDA and youtube videos. So clear, step-by-step instructions is best, THANKS!!
My device:
Sprint Evo 4g
supersonic evt2-3 ship S-ON
hboot-6.17.0001
Radio-2.15.00.0808
Version 2.3.3
kernel 2.6.35.10-g13578ee
You dont need to unroot and grab the OTA update. Just flash the lastest stock rooted ROM. It comes packaged with the latest updates pushed by Sprint.
Edit: This thread is exactly the reason why mods have created stickies. Try putting forth some effort in looking for an answer yourself before creating a thread. You can do this by using the search feature or checking the thread that was an inch below the button you pushed to create this one.
http://forum.xda-developers.com/showthread.php?t=865204
Concordium said:
You dont need to unroot and grab the OTA update. Just flash the lastest stock rooted ROM. It comes packaged with the latest updates pushed by Sprint.
Edit: This thread is exactly the reason why mods have created stickies. Try putting forth some effort in looking for an answer yourself before creating a thread. You can do this by using the search feature or checking the thread that was an inch below the button you pushed to create this one.
http://forum.xda-developers.com/showthread.php?t=865204
Click to expand...
Click to collapse
Thank you Concordium, Please use the stickies to learn more about xda before you start asking questions. Also the search feature works wonders, much faster than trying to look through all 5,000+ pages in our dev section alone. Please please please use the tools already given to you.
tlp80 said:
I first rooted my phone using revolutionary-0.4pre4.zip file to get the s-off and then flashing SuperUser su-2.3.6.3-efgh-signed.zip. This worked just fine. I've been ok with the stock rom so I haven't changed it. I wanted the new update when it came out and some threads said I needed to UNroot in order to update. Therefore I ran PC36IMGson.zip which hasn't help me either, but now my phone is back to s-on but seems to still be rooted (since Titanium Backup, Rom Manager, and SuperUser are still working fine).
Now, I'm done with it all and would like to flash some other rom But I can't get back to s-off! revolutionary thinks it's still set to s-off each time I run it, but the bootloader screen still says s-on. Unrevoked doesn't work either since my device is unsupported.
Any ideas???
I'm pretty new to all of this and have been trying to figure this on my own with XDA and youtube videos. So clear, step-by-step instructions is best, THANKS!!
My device:
Sprint Evo 4g
supersonic evt2-3 ship S-ON
hboot-6.17.0001
Radio-2.15.00.0808
Version 2.3.3
kernel 2.6.35.10-g13578ee
Click to expand...
Click to collapse
Thanks for coming into my store. I'm glad we could fix that for ya. Remember to condition your battery and check out shipped-roms.com for the latest RUU's
Thanks
Ryan
(original post was in wildfire general section-- moved here on suggestion)
I wanted to root and flash my VM Wildfire S,but had some problems along the way.
Before I started the process, I had a LOCKED.
*** LOCKED ***
MARVEL C PVT SHIP S-ON RL
HBOOT- 1.10.0001
And, I have Android 2.3.4
I successfully unlocked the bootloader using HTC Dev site/process. I validated that I had (and still have) "UNLOCKED" on HBOOT screen.
Being a noob, I was really happy with this result. In fact, I was so happy, I wanted to continue on to Root the phone. Upon hours of search in xda, I found "One Root for WFS 1.5", read the thread, and even watched the youtube vid- man, it looked easy!
Unfortunately, all did not go well. See attachment to get idea of what happened..
I was softbrick until yesterday. I could get the HBOOT Menu, but when I try fastboot, I saw things like:
PG76DIA.zip
no image or wrong file
PG76DIA.nbh
no image or wrong file
I spent many hours looking through this forum and others on how to fix. I tried a couple of things, but this one worked (flashed Alquez's Unoffical 5.0.2.6 ClockworkMod recovery):
http://forum.xda-developers.com/show....php?t=1436501
I installed Rom Manager as suggested, but it wouldn't work ("an error occurred while trying to run privileged commands"). I am guessing that I am actually not rooted??
I am happy for now, but back to searching for next step, unless I can get a hint or two from this forum? please. I am guessing I need to root (any suggestions as to best one for vm wildfire s?) Can I still do this with the alquez's unofficial 5.0.2.6 cwm recovery?
I think you ROM is still not rooted. There any many root Applications present Try out. I personaly prefer htcsupertool utility, Since it helped to Root my WFS.
After Rooting process Is done.
You can check the status using Root Checker(a small app in Google market) to verify the root status.
After Rooting you can Flash ClockworkMod Recovery through Rom manager app.....
If you've got a custom recovery, try to find a root.zip somewhere on the forum, and install from recovery. That should root you.
-----------
"You can overclock as much as you want, your phone will always seem too slow."
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
griplegraple said:
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
Click to expand...
Click to collapse
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
musical_chairs said:
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
Click to expand...
Click to collapse
The first option above worked in my case. Phone is able to load up and seems to be working fine.
Thread moved. Please post all question threads here in Q&A in future.
Thanks
AvRS
Sent from my Nexus 4 using xda premium
griplegraple said:
Thanks for the reply. I will try the first option, but one thing I have noticed before is that when I use the adb method, I can't get "adb devices" command to work. It outputs "List of devices attached". In my device manager, I have ADB Interface ->HTC Bootloader with the android USB driver installed... Not sure if you can help on this.
Click to expand...
Click to collapse
That could be caused by having adb or the drivers improperly set up on your computer, or it could be because you didn't have USB debugging enabled in the phone's settings. You could try booting your phone into recovery and seeing if you can access it with adb from there if all else fails.