I have a bricked MT4G and I discovered that if I remove the battery, hold Vol+ and Vol-, then connect USB, I get 5 vibe pulses and a Qualcomm MSM device detected in Windows.
I assume this is the serial loader? Any idea what we can use this for?
Copying over the radio firmware?
I tried to hold Vol+ and Vol- with no battery and then plugging in USB, however, nothing came up. Are you doing something different?
from the sound of it, thats the modem chipset. how exactly did you brick your phone?
I was trying to restore everything to stock so I could return it. Finally got a LCD-SO-C2 with a centered FFC. The power button is still mushy, but at least it works.
Undoing the super CID by restoring the part7backup.bin is what did it. I got a write error and then a message that the bin file had 2049 records instead of 2048. By the time this message showed up, the damage was done. No idea how that happened.
I am not too worried about it; from what I have read, several people have returned hacked and bricked devices without any trouble. They are not going to have much luck looking at the bootloader status at this rate.
Hopefully they rewrite the whole eMMC once they see it won't boot.
I just tested with the working device I have here, and it will not respond to this method. The phone must have to be in a bad state for it to work.
Dunno what that mode is, but I can do the same on mine.
Seems like the modem interface...
Not sure what is required to get the phone up in this mode. The one that this works on is a Taiwan phone, the other is Chinese. Other than the Taiwan phone having the Sharp screen, I don't know what else would be different.
Do you still have the engineering bootloader?
I bet that's it. I haven't done that to the new device yet, for obvious reasons.
I pretty much just run Cyanogen.
Well if you plan on flashing any roms it might be worth it for you to flash the engineering bootloader. It can help prevent perma bricking
Sent from my HTC Glacier using XDA App
imabrokendownload said:
Well if you plan on flashing any roms it might be worth it for you to flash the engineering bootloader. It can help prevent perma bricking
How do you do that
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
If you rooted with visionary you have it if you don't I think it may be stickied or it's somewhere here
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
If you rooted with visionary you have it if you don't I think it may be stickied or it's somewhere here
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
WRONG.
For the hundredth time, VISIONary does nothing besides give you temproot and permroot and you have to run a script while temprooted in order to do the permroot. It does not do ANYTHING like flash the engineering bootloader. Think about it: the bootloader is device-specific, and VISIONary was originally built for the HTC Vision, aka T-mobile G2. If what you are suggesting is true, then it would be trying to flash a bootloader for the Vision on your Glacier, which surely can't be a good thing.
You have the engineering bootloader if you did either of the following:
1. Used the root.sh script to get S-OFF, such as by following the guide on theunlockr.com (although I've heard some people have used a version that doesn't flash the engineering bootloader).
2. You flashed it manually using terminal emulator. Instructions for this can be found in the gfree thread (and probably in other places).
If you don't have it yet, there's a download link and instructions in grankin's true permroot thread stickied at the top of this forum. Make sure you type that command properly, and do an md5sum on the hboot file to make sure you didn't get a bad download.
In any case, I too am curious about this discovery and welcome an explanation from someone in the know.
jdkoren said:
You have the engineering bootloader if you did either of the following:
1. Used the root.sh script to get S-OFF, such as by following the guide on theunlockr.com (although I've heard some people have used a version that doesn't flash the engineering bootloader).
2. You flashed it manually using terminal emulator. Instructions for this can be found in the gfree thread (and probably in other places).
If you don't have it yet, there's a download link and instructions in grankin's true permroot thread stickied at the top of this forum. Make sure you type that command properly, and do an md5sum on the hboot file to make sure you didn't get a bad download.
In any case, I too am curious about this discovery and welcome an explanation from someone in the know.
Click to expand...
Click to collapse
No actually RIGHT the visionary METHOD uses those steps you listed. I'm sorry if I didn't include the word 'method' but I've used it in posts plenty of times before and its been understood.
Sent from my HTC Glacier using XDA Premium App
G8351427 said:
Seems like the modem interface...
Not sure what is required to get the phone up in this mode. The one that this works on is a Taiwan phone, the other is Chinese. Other than the Taiwan phone having the Sharp screen, I don't know what else would be different.
Click to expand...
Click to collapse
Hey man this may sound dumb but when it appears in the device list can you get adb to somehow recognize it?
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
No actually RIGHT the visionary METHOD uses those steps you listed. I'm sorry if I didn't include the word 'method' but I've used it in posts plenty of times before and its been understood.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
This is still wrong because VISIONary is used regardless of whether you are doing the root.sh method or the gfree method. Of those two, only root.sh will flash the engineering bootloader; gfree will not. Your post is understood by people who already know what they're doing, but there are plenty of n00bs and non-technical people who are showing up on these forums, and posts like yours can cause confusion for them. For the sake of those who don't know all of this yet, it's worth clarifying which method you are talking about.
Posting to confirm that it worked with my device, although it said the drivers did not install properly.
Related
I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.
ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery
ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery
Anyone? Bueller?
cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.
This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.
so i got the promotion to get a free g2 but heres a few questions im thinking that it will come with the latest rom can i root it ive been looking through a ton of guides and im confused what should i do. which method work to gain perma root
cudahy_boy said:
so i got the promotion to get a free g2 but heres a few questions im thinking that it will come with the latest rom can i root it ive been looking through a ton of guides and im confused what should i do. which method work to gain perma root
Click to expand...
Click to collapse
It may come with the latest ROM but I more suspect that it will come with the original (shipped) ROM and immediately receive the OTA update. The good news is that there are no issues rooting even if you have the OTA applied (I think some of the rooting guides assume you do) so I would go ahead and apply the OTA if prompted. This is different than the Desire Z where the latest updates can make rooting more complicated.
The most widely recommended method of obtaining permanent root is the "gfree" method, it will permanently root your phone and at the same time will SIM unlock it as well as set the CID so you could load whatever carrier ROM you might want to.
The only issue most people seem to have with using the gfree method is getting ADB up and running and talking to your G2. Using ADB isn't (as far as I know) strictly necessary to make gfree work but it's easiest and all the guides (that I've seen) have you use ADB.
Here is the section of the wiki showing you how to use gfree to root your phone: http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
For instructions for getting ADB up and running I would look here:
http://forum.xda-developers.com/showthread.php?t=865685
Check out unlockr.com on rooting g2. They use the Visionary method. Took me only couple mins.
Sent from my HTC Vision using XDA App
GhostZini said:
Check out unlockr.com on rooting g2. They use the Visionary method. Took me only couple mins.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Could you please stop telling people to use the VISIONary method!? That method has a risk of putting the user's phone into a boot loop! Please know you what your talking about before attempting to help some one, it can make the difference of bricking a phone and rooting a phone. Rage and GFree DOES NOT have a risk of putting your phone in a boot loop. Out of all the people that have messed up their phone, EVERY ONE of them that I have seen has used the VISIONary method. I'm not trying to be mean, but please be more careful when giving advice. I know your just trying to help, and I respect you for that but please do no tell some one to do the VISIONary method.
Sorry mate, I had no clue bout that. I had no loop but i see your point
Sent from my HTC Vision using XDA App
nevermind about my quesiton lol
Thanks for this question, it answered mine so I didn't have to ask. Will be using g-free way shortly.
OK before i get SEARCH.. I did and here is what i have looked at so far (i am 3+ hours into my search)...
http://forum.xda-developers.com/showthread.php?t=838484
http://forum.xda-developers.com/showthread.php?t=842495
http://forum.xda-developers.com/showthread.php?t=905261
ANd a few others that link back to one of those 3.
This is not my phone. I am helping my buddy who attempted to perma-root his phone using Visionary+ 14. I have an evo, and several other android phones and understand the basics of ADB and how to do most this stuff.
After he applied the patch, we are stuck on the white HTC screen. The problem is, it does NOT have the ENG SPL, we are still s-ON and still have stock recovery.
Here is what i have attempted so far:
download and tried to have it reload PC10IMG.zip - Got an error that said the version i was trying to install was older than the one i already had. I downloaded the latest one i could find.
Since i can get into the stock recovery, i downloaded and tried to use update.zip to reinstall things correctly, but that didnt work. It didnt error out and looked like it installed correctly, but still just stuck at the white HTC screen.
I cannot access ADB (at least any way that i know how).
Yes, i have the correct USB drivers installed and ADB is working as i have accessed it for other phones.
Here is the phone stats:
VISION PVT SHIP S-ON
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_m
eMMC-boot
Sep 2 2010, 17:59:38
I cannot find the right RUU to give that a try either. I have found a few that MIGHT be right, but i dont want to mess it up more by flashing the wrong thing (if this would even help.. i dunno)
ANY HELP WOULD BE REALLY APPRECIATED!!!!
Anyone?? Help????
frettfreak said:
this is why people post in the dev forum when they arent supposed to.... cause NOTHING happens if you post in q&a...
Anyone?? Help????
Click to expand...
Click to collapse
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
ianmcquinn said:
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
Good point!! Sorry.. just a little anxious. Dont want to tell him his phone is bricked....
Also... maybe no one responded cause i am a tard.... its s-ON still, not S-OFF
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Sorry for the confusion and pushy-ness and thanks for your help!
frettfreak said:
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Click to expand...
Click to collapse
Well, like I said before, this is the type of semi-brick that people seem to be stuck in when Visionary fails and I haven't seen a working solution. When I said to leave it at the HTC screen, it was just something mentioned in the how to recover semi-brick thread you linked to in the original post. Unfortunately, if that didn't work, you might by out of options.
EDIT: And oh, I forgot to mention about fastboot. Although it might seem like fastboot detects the phone properly, you cannot actually use it to flash anything unless you have the engineering HBOOT, so that doesn't help any.
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
lainvalenajr said:
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hmmm how do I do that? Is there a different way other than adb? I will check again but pretty sure I don't have adb access (I think this is what the eng spl does but I am just guessing here) does fastboot allow Me to do anything like that?
Basically what it says in the title. I have a Desire HD with Android 2.3.5 installed, and I want to flash Cyanogenmod 7.1 (With google apps) to it. I've had a good look at all the resources available and I think I know what I need to do, I'm a little apprehensive though as I'm new to this so would somebody mind checking the resources I have found to see if I have the right steps?
First of all I've checked in About Phone -> Software Information and found that my Software Number is 3.12.405.1. So from what I've read this means I'll have to downgrade my firmware before I can root.
That lead me to this guide: Here
If I follow that guide carefully as well as this one here, I will end up with a phone that has firmware 1.32, is rooted, has Radio S-OFF and also has clockworkmod recovery installed.
From there, I can then follow this guide here to install the latest version of Cyanogenmod either using Recovery, or the ROM manager. Simple, right?
Does this sound about right? Or am I missing something incredibly obvious that will break my phone, or make life a lot easier?
Any help would be greatly appreciated, thanks!
Sounds good to me although you could try this http://forum.xda-developers.com/showthread.php?t=952352
One click root and s-off once you follow everything and have the right setup to run the tool. Very easy and quick.
Sent from my HTC Desire HD A9191 using xda premium
yvibes said:
Sounds good to me although you could try this http://forum.xda-developers.com/showthread.php?t=952352
One click root and s-off once you follow everything and have the right setup to run the tool. Very easy and quick.
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
Thanks! That looks good, although I'm not very confident about this little warning.
Doing this WILL severely degrade bootloader performance on Inspires (and likely DHDs) and causes issues trying to install RUUs. In other words, it WILL jam you up. (Note: Issue now confirmed on later DHDs - ignore at your own risk).
Click to expand...
Click to collapse
Am I reading this correctly, following this method WILL degrade my bootloader performance? Or will that only happen if I perform the hack incorrectly?
You are reading it wrong. What has happens especially with us inspire users(American dhd) is that if your phone was shipped with gb, installing the Eng bootloader(Eng soff) causes issues. Makes the phone take 15 min to boot. Its possible to fix but its a long pita. I only seen a couple people with dhd have this issue so and others not.
Regular soff is all you need, just you can't use fastboot to flash say radios, its done in a different way
marsdta said:
You are reading it wrong. What has happens especially with us inspire users(American dhd) is that if your phone was shipped with gb, installing the Eng bootloader(Eng soff) causes issues. Makes the phone take 15 min to boot. Its possible to fix but its a long pita. I only seen a couple people with dhd have this issue so and others not.
Regular soff is all you need, just you can't use fastboot to flash say radios, its done in a different way
Click to expand...
Click to collapse
Yup exactly that
Sent from my HTC Desire HD A9191 using xda premium
Just follow these his guide and video, works perfectly. www.xda-developers.com/android/how-to-root-the-htc-desire-hd/
The only difference is that after instead of flashing the rom suggested you can flash cm 7.1 www.download.cyanogenmod.com/?type=stable&device=ace
No risks no problems with bootloader.
So I've recently gotten my Desire Z rooted, and I'm trying to install a custom ROM.
However Clockwork keeps telling me that my phone is not rooted, ("You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su"".
Even so my phone has SU installed as well as busybox. How do I need to go about fixing this?
Thank you for any help!
first of all what method did you follow to gain root?
also do any other rooted apps work? setcpu, titanium, adfree ?
I used the HTCdev method to unlock my bootloader then I used the Fre3vo exploit and pushed the superuser and busybox apks and installed them both.
Titanium does not work either.
I believe in order to get the su to work you have to actually flash it as a .zip the first time. Also, do you have s.off? That htcdev.com method is horse crap if you ask me, though it will get you unlocked.
Sent from my HTC Vision using xda premium
It managed to get my bootloader unlocked.
But no I don't have S-off. Would having flashed it from a .zip changed anything else?
Also I can flash ClockWorkRecovery without even a little bit of an Issue.
well s-off means no root, follow the wiki, downgrade and then root.
the htc unlocked bootloader is just a stepping stone leading to nowhere
probably the most you will get out of it is confirming your g2 is void of warranty with htc
so follow the wiki, it isnt to hard and you will be much happier than trying to cheat your way into root!
good luck!
Alright, well thanks for your help fellas!
no problem, just make sure you read the wiki first and understand it, if not search the threads and im sure someone has had the same question. but over all it takes from 30min for the experienced up to 2hrs if your lost the whole time. leave the appropriate amount of time and youll be a happy camper soon enough!
http://forum.xda-developers.com/showthread.php?t=1453066
This is the thread you need to follow if you have already used htcdev method. You will have to relock bootloader, then downgrade, then root and s.off.
Also, if you have any further problems talk to that nipqer, he is really good.
Sent from my HTC Vision using xda premium
mrbmg said:
http://forum.xda-developers.com/showthread.php?t=1453066
This is the thread you need to follow if you have already used htcdev method. You will have to relock bootloader, then downgrade, then root and s.off.
Also, if you have any further problems talk to that nipqer, he is really good.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
This was the guide I followed and it just seems to be against me!
EDIT: Never mind! Finally got it to work! I now have custom ROMs again! Thanks for all the help!
If you join that irc channel, all those guys are on there and will walk you through it step by step.
Sent from my HTC Vision using xda premium
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
follow this guide, since you have "the official HTC unlocked bootloader" which as i said before is almost worthless (not complaining to you but to htc) i believe you need to do a few things first before you can downgrade, you need to be at froyo for this method to work, dont have time to search for you right now but im sure you'll find the appropriate steps to take if you search a little
HTC Unlock only lets you flash ROMs through fastboot. As already mentioned, it doesn't give you root, S-Off, and you can't flash straight from ROM Manager or recovery.