Related
OK Guys and Gals, Here is what is going on with the radio issue. No Matter WHAT radio combos you may be using. As some of you may know by my earlier posts I live in a huge 4G network and never get anything, but 4G and (3G only for a min on boot) This is why I didn't have ANY issue's until I got curious and wanted to try something. On our tbolts, if you try to make a call while in 3G the 3G will drop out until the call is over. I went back to froyo, got pissed and went strait back to GB (doesn't matter what Rom as all the dev have clearly stated) when I did go back to GB things were tight as usual. worked like a charm. I used it as I normally would and everything was fine. upon a self induced restart, before my phone had a chance to obtain 4G (still in 3G) I decided to make a test call to see if the 3G would drop. It didn't. Quickly after I ended the call the phone booted in to bootloader. Thank God I had removed the GB RUU because I don't have a card reader to remove the RUU. I forgot to mention I do have the latest Rom Mgr and was able to get into recovery and simply reboot. After that reboot I would get to my home screen, but this time the 3G only would come up and then reboot. Time after time of rebooting I tried other things such as toggle radio to just grab 4G, then the phone rebooted again! upon the next full boot I quickly moved the original froyo radio strait to the sd card. And yet another reboot. This time I got a Rom Mgr error and noticed that Rom mgr was no longer flashed!!! I flashed it real quick because I knew another reboot was on its way. Rom mgr flashed and I told it to boot in to recovery. Thank **** I flashed Rom manager because if not I would be in continuous boots like the unfortunate others. Once in recovery I Realized that I had told my phone to go in to recovery via Rom mgr. and if I did a restore, the phone would have booted back up with my froyo rom but with the GB radio! so I told CWR to just reboot so I could tell the phone to go into recovery via the pwr restart option (thus not restarting after I flashed my froyo recovery) Once recovery of my froyo rom was complete I used ADB to reboot bootloader and SUCCESS! Bottom line you can not make a call while on 3G with any of the current GB radios, you gotta be quick, Make sure ROM mgr is actually flashed!!!! and hopefully can dump the froyo radio on to your SD card before an inevitable reboot happens! and have some ADB knowledge. I'm certain this is whats going on! People make a call while in 3G and its all down hill from there. So dont bother with telling radio settings to stick with one band. Once this happens, there is no turning back. Any questions PM me. I'm glad I tried this out before Vaca tomorrow with a FUBAR Tbolt
Hope this helps developers somehow. Good luck!
Also check a couple quotes from the development thread. Remember I'm going on vacation n won't be able to reply to many comments. Maybe just share your experience. Thank you
Sent from my ADR6400L using XDA Premium App
The people with the reboots can't get to Rom manager or recovery or anything. It reboots even if you try to gget in Clockwork.
I live in a 3g only area and make calls all the time on 3g. I have myine set to cdma auto so its always on 3g and mine hasn't done it yet. I'm on the gb radio
Sent from my ADR6400L using Tapatalk
smalltownbird said:
I live in a 3g only area and make calls all the time on 3g. I have myine set to cdma auto so its always on 3g and mine hasn't done it yet. I'm on the gb radio
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Yes this is true because your phone doesn't try to toggle to the 4g lte radio
Sent from my ADR6400L using XDA Premium App
corenojoe said:
The people with the reboots can't get to Rom manager or recovery or anything. It reboots even if you try to gget in Clockwork.
Click to expand...
Click to collapse
They can't get into rom Mgr because they didn't notice rom manager needed reflashed right before first reboot.
Sent from my ADR6400L using XDA Premium App
I live in a 4G area, was running GB Bamf rom. Made plenty of calls on 3G and on 4G lte. Never had this happen.
dopediculous said:
They can't get into rom Mgr because they didn't notice rom manager needed reflashed right before first reboot.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
refresh my memory, my poor old brain is on overload from all the brick posts....
Aren't the "bricked" phones also unable to stay in hboot for more than a few seconds without rebooting? If so, then what the OP is stating is NOT the same thing others reported because he states he could reflash the radio, suggesting a stable hboot/bootloader.
Seems like if you've got a stable hboot, you're not truy bricked, as the first post here shows....
bp328i said:
Ask me how I know
Click to expand...
Click to collapse
If you have a bricked device please go post in the stickied thread in app/dev.
Oh and OP - Paragraphs are a good thing. Just sayin...
bp328i said:
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
Click to expand...
Click to collapse
I ment while in rom Mgr to make sure cwr is actually flashed. Mine was then after reboot I noticed cwr was no longer there. In rom Mgr it just said what the current cwr would be if I choose to flash it. If people miss this after a stupid reboot, the next reboot may not be so kind...
Sent from my ADR6400L using XDA Premium App
bp328i said:
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
Click to expand...
Click to collapse
In fewer words that's exactly what I was saying. Seems like he thinks Rom Manager is recovery.
distortedloop said:
refresh my memory, my poor old brain is on overload from all the brick posts....
Aren't the "bricked" phones also unable to stay in hboot for more than a few seconds without rebooting? If so, then what the OP is stating is NOT the same thing others reported because he states he could reflash the radio, suggesting a stable hboot/bootloader.
Seems like if you've got a stable hboot, you're not truy bricked, as the first post here shows....
Click to expand...
Click to collapse
Mine was a TRUE bricked phone but my bootloader stilled would stay on. The bootloader screen was the only thing that would not bootloop. I was able to flash the stock RUU and stock bootloader and it still would not go past the splash screen.
funkybside said:
If you have a bricked device please go post in the stickied thread in app/dev.
Oh and OP - Paragraphs are a good thing. Just sayin...
Click to expand...
Click to collapse
Mine was bricked last Saturday, I don't have the phone anymore. It's been sent off for repair. Lucky me gets to rock my DInc for the next 2 - 3 weeks, DAMN 3G is slow.
dopediculous said:
I ment while in rom Mgr to make sure cwr is actually flashed. Mine was then after reboot I noticed cwr was no longer there. In rom Mgr it just said what the current cwr would be if I choose to flash it. If people miss this after a stupid reboot, the next reboot may not be so kind...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Your phone will still reboot without a recovery. There was an issue awhile back when I had my OG Droid with ROM Manager wiping out recovery. People would try to boot into recovery to fix something and oops no recovery.
You can flash a recovery image via adb.
bp328i said:
Your phone will still reboot without a recovery. There was an issue awhile back when I had my OG Droid with ROM Manager wiping out recovery. People would try to boot into recovery to fix something and oops no recovery.
You can flash a recovery image via adb.
Click to expand...
Click to collapse
yeah, that was annoying. Believe that's when they told everyone to check the "erase recovery" option in the Rom Manager settings and that seemed to help.
PJnc284 said:
yeah, that was annoying. Believe that's when they told everyone to check the "erase recovery" option in the Rom Manager settings and that seemed to help.
Click to expand...
Click to collapse
Really funny thing was that was going on right when the Froyo leak came out for the OG Droid and the first ROM I flashed I hated. So when I went to flash my nan-droid there was no recovery and I did not know about the issue so I ended up sbf'ing back to stock and rerooting again.
I have seen a bootloop on a phone that was not running GB or rooted. A guy I work with brought me his phone a few weeks ago and wanted me to let him use my battery to boot his phone. When I put my battery in and saw what it was doing i booted it into Hboot (of course S-on) so I couldn't do much for him. Of course the Verizon Tech's weren't much help to him either, but they did send him a CLN Device. You can pass this along to jcase as I don't have enough posts to be able to post in the DEV forum yet. I read and rarely post unless I believe I have something useful to add.
I've seen devs mention to flash a radio from Hboot and Fast boot before. Are these terms synonymous? Fast boot is accessed from Hboot correct? I've flashed a radio a few times, but never understood the terminology. A PD98IMG is always flashed the same way from what I understand.
More or less correct. HBoot flashing is done with the PD98IMG.zip on the SDcard. PD98IMG.zip can contain any number of images to be flashed. Fastboot flashing is done using the fastboot.exe and can flash a single image.
Gene Poole said:
More or less correct. HBoot flashing is done with the PD98IMG.zip on the SDcard. PD98IMG.zip can contain any number of images to be flashed. Fastboot flashing is done using the fastboot.exe and can flash a single image.
Click to expand...
Click to collapse
I've never quite understood what the advantage is to fastboot flashing. Then again, I've never truly understood fastboot in general.
Something I definitely need to do more reading on.
I've tried several times, and several methods to flash my radio to the 12.54.60.25_26.09.04.11_M2 radio img. And nothing seems to be working. My best guess is its user error. I'm a noob and trying to learn how to flash my radio. I currently have the 12.39.30.19P-26.06.04_M with the TPGB-Ninja_0618 ROM and [email protected] #28 kernel.
I've done the method where i go into adb to access bootloader, then i flash the radio.img then reboot the phone and that doesnt work. I've tried running the radio.img though CWM and that didn't work.
If I power off my phone and then hold power and -vol down to get into the bootloader it automatically will go into hboot and start to run through the PD98IMG.zip. I'm wondering.
Do I need that .zip folder on my sdcard forever or can I get rid of it?
Also, can I just switch out radio.img in the PD98IMG.zip with the new radio.img?
Can I do the above question without having all the other .img 's in the .zip folder?
I've done some research, but haven't found my answers, or was able to fix my problem.
So hopefully someone can help me.
Please be gentle with me, I'm new to this type of thing, but a fast learner.
Thanks in advance
shugga101 said:
I've tried several times, and several methods to flash my radio to the 12.54.60.25_26.09.04.11_M2 radio img. And nothing seems to be working. My best guess is its user error. I'm a noob and trying to learn how to flash my radio. I currently have the0 12.39.30.19P-26.06.04_M with the TPGB-Ninja_0618 ROM and [email protected] #28 kernel.
I've done the method where i go into adb to access bootloader, then i flash the radio.img then reboot the phone and that doesnt work. I've tried running the radio.img though CWM and that didn't work.
If I power off my phone and then hold power and -vol down to get into the bootloader it automatically will go into hboot and start to run through the PD98IMG.zip. I'm wondering.
Do I need that .zip folder on my sdcard forever or can I get rid of it?
Also, can I just switch out radio.img in the PD98IMG.zip with the new radio.img?
Can I do the above question without having all the other .img 's in the .zip folder?
I've done some research, but haven't found my answers, or was able to fix my problem.
So hopefully someone can help me.
Please be gentle with me, I'm new to this type of thing, but a fast learner.
Thanks in advance
Click to expand...
Click to collapse
Assuming the PD98IMG.zip containing the radio flashes properly, you can remove it afterwards.
Have you checked out the inspire only radio thread in the dev section, yet?
There's already a ready-to-flash PD98IMG.zip for the radio you want to flash on that thread.
Download it from that thread, verify the MD5 checksum, plop it in the root directory of your SD card, reboot into hboot/bootloader, once it finds the PD98IMG.zip, confirm the update, and away you go.
Ok I'll try that as soon as I get to my computer. Thanks for the reply and I'll let you know how it goes.
Sent from my Inspire 4G using XDA App
shugga101 said:
Ok I'll try that as soon as I get to my computer. Thanks for the reply and I'll let you know how it goes.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Just don't forget to check that MD5. I have had incomplete (meaning...BAD) radio downloads on a solid WiFi connection, so it DOES happen from time to time.
Scott_S said:
Just don't forget to check that MD5. I have had incomplete (meaning...BAD) radio downloads on a solid WiFi connection, so it DOES happen from time to time.
Click to expand...
Click to collapse
I was able to flash the radio, but all that work for nothing. I actually got worse data. But then again I could of done something wrong again.
shugga101 said:
I was able to flash the radio, but all that work for nothing. I actually got worse data. But then again I could of done something wrong again.
Click to expand...
Click to collapse
Couple of things. 1) Be sure to give the radio long enough to "warm up"...I'ave had it take several hours after flashing before I started getting decent speeds from a radio I know works. 2) It is usually recommended to keep a copy of your radio flash on your SD card in case you need it (GPS fail, etc., ) so you can reflash if you are away from a PC, but not keep it in the root of your SD. It's very possible to end up in a continuous boot loop until you somehow either get the file off your root (SD card reader) or fool the phone into thinking it isn't there by pulling the SD card when you pull the battery to recover (I've only heard the last trick works)...
shugga101 said:
I was able to flash the radio, but all that work for nothing. I actually got worse data. But then again I could of done something wrong again.
Click to expand...
Click to collapse
You've also made sure you have the appropriate RIL for the new radio you flashed, correct? That radio thread also has the RILs + info about them, as well.
Also try rebooting more than once after flashing a radio/ril, just for good measure.
When I first flashed the 04_11_M2 radio, I had only rebooted once, as a result of the flashing process. Once my phone was done loading up, I received my first call with it, the caller couldn't hear me, but I could hear them. Caller tried calling back. Same thing. I decided to give it another flash and reboot. I called that person back, and it was working, never experienced that since.
Coincidence? Who knows? But radios are weird, quirky things that seem to need a little "voodoo" type flashing/rebooting to kick them in, I suspect.
Well I think I found out why I'm getting these speeds. My radio has a "P" and not a "U" like in meiguoguizi's sig. I have the same radio as that (number wise) but he has a "U" and not a "P".
The radios that I can flash have an "x" in that place so won't that just mean it will switch to whatever letter my data is running on?
I think I found out why I am having this problem.
I can flash the radio.
I can flash the RIL.
But I have a "P" where the "U" is supposed to be to represent the HSUPA speeds.
If thats the the reason then I don't know.
shugga101 said:
Well I think I found out why I'm getting these speeds. My radio has a "P" and not a "U" like in meiguoguizi's sig. I have the same radio as that (number wise) but he has a "U" and not a "P".
The radios that I can flash have an "x" in that place so won't that just mean it will switch to whatever letter my data is runningo on?
Click to expand...
Click to collapse
I think that U/P thing is determined by one of the settings in the build.prop file. I know it's been discussed before, I just don't recall the details. If you visit the "editing the build.prop file" thread in the dev section, or possibly amongst the comments in the inspire radio thread, I think you might find the specifics in one of those places.
Or browse through henrybravo's posts, I think I remember him explaining it to someone.
Bottom line is that you have the same radio, it's just a setting that's determining the connection type and as a result, that letter changes, depending on that setting.
LeeDroid
Today I flashed the 09.04.11_M2 that is suggested on for LeeDroid 3.2.1 and now I have lost all notification sounds, lockscreen sounds, and keyboard sound feedbacks. Can anyone help?
blippy said:
Today I flashed the 09.04.11_M2 that is suggested on for LeeDroid 3.2.1 and now I have lost all notification sounds, lockscreen sounds, and keyboard sound feedbacks. Can anyone help?
Click to expand...
Click to collapse
First, try another re-flash of the radio.
I did a full wipe and restore and got all the sounds back. Reloaded the RIL and everything works fine.
Sent from my Desire HD using XDA App
Yes the x is a placeholder (remember your algebra).
Open he's right. You have to flash the Riley that goes with the radio and then reboot twice. Make sure you are using the best radio for your Rome.
Sent from my Desire HD using XDA App
Pick_A_Name said:
Yes the x is a placeholder (remember your algebra).
Open he's right. You have to flash the Riley that goes with the radio and then reboot twice. Make sure you are using the best radio for your Rome.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Lol. Autocorrect really has the hots for you.
Lol sorry I was on my mobile and left too much to swift key X. I'll proof read next time!
Pick_A_Name said:
Yes the x is a placeholder (remember your algebra).
Open he's right. You have to flash the Riley that goes with the radio and then reboot twice. Make sure you are using the best radio for your Rome.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Rileys and Romes....I can dig it
this has gotton significantly worse....is there any fix to this? Im currently stock. Does rooting fix? plz help
This is due to the radio on your phone, it's really bad in up here in Canada from what I have read, if you root your phone and use KB3 it will quit doing that, at lease it has stopped on both of my phones, seems it only happens in bad service areas.
What search button bug?
I got my Nexus from Canada and had the same problem.
Like the other dude said, rooting and flashing a ROM is the only way around it. You won't have any problems after that.
Sent from my MB860 using XDA App
well i like the stock rom on the nexus do you think i could root and then just disable the search button to do nothing? ALso, i'd love to do a new radio but i screwed up my first phone that i had once by doing something wrong and now i have somehwat of a fear of flashing radios.
JGAGNON10 said:
well i like the stock rom on the nexus do you think i could root and then just disable the search button to do nothing? ALso, i'd love to do a new radio but i screwed up my first phone that i had once by doing something wrong and now i have somehwat of a fear of flashing radios.
Click to expand...
Click to collapse
Can't disable that button, the radio is fairly safe to flash on this phone. I do it lots, best thing to do is download the radio, and get the md5 hash and if that matches you're golden.
Sent from my *****'n Nexus S.
Oh ya, when you root you don't have to change from your stock rom.
Sent from my *****'n Nexus S.
ok i plan on rooting tonight....and i guess ill do the radio.... im a total noob at this so can you point me in a very dumbed down version on how to flash the radio and also which radio to flash? Any help is greatly appreciated
http://forum.xda-developers.com/showpost.php?p=14564429&postcount=1
[RADIO/GUIDE] Radio JK1, KB1, KB2, KB3, KD1 and UCKD1
You want to get kb3 that one seems to fix it. You will flash it with clockwork after you root.
Sent from my *****'n Nexus S.
Edit, link didn't work out from the app.
ok so just to be very clear, first i root the phone (no new rom). Then i just put the zip file onto the root of the sd card, and go into fast boot or whatever its called, select from sd and flash it? is it as simple as that?
JGAGNON10 said:
ok so just to be very clear, first i root the phone (no new rom). Then i just put the zip file onto the root of the sd card, and go into fast boot or whatever its called, select from sd and flash it? is it as simple as that?
Click to expand...
Click to collapse
You will unlock it with adb, install clockwork mod, then su to root it, then yes, just put the radio on your sdcard and flash it through clockwork mod. Make sure you know the model of your phone to, it's under battery.
This is the md5 hash I get for the KB3 radio under the "Radio for I9020a/I9020T/I9023" heading.
4e9c9cf4d6470be800e00f8508b9c175 Radio Nexus S [XXKB3].zip
Just to double check if your paranoid, download the Radio and a md5 checker and if your numbers match mine your good.
see what you just said there confused the hell outta me lol....what do u mean flash radio with the clockwork mod? And those numbers im not sure what that meant
JGAGNON10 said:
see what you just said there confused the hell outta me lol....what do u mean flash radio with the clockwork mod? And those numbers im not sure what that meant
Click to expand...
Click to collapse
Read the stickies.
Quick primer:
After you get root, you can replace the recovery partition of your phone with clockworkmod. That's the "flash recovery" part. This gives you a pre-boot working environment that lets you flash ZIP files (ROMs, kernels, boot animations, radio images, etc), make backups, wipe data, etc. Using clockwork recovery you can flash a new radio firmware which apparently fixes the problem.
JGAGNON10 said:
see what you just said there confused the hell outta me lol....what do u mean flash radio with the clockwork mod? And those numbers im not sure what that meant
Click to expand...
Click to collapse
Clockwork Mod is the recovery you will install when you go to root your device, the numbers is the md5 hash, when you download a file you can check the md5 to see if it is corrupt in any way.
umm ok i rooted via one click root mechanism....how do i apply zip from sd card now? i dl'd rom manager and flashed clockwork mod. Now what
Shut down your phone, hold up volume and press and hold power button until you see a screen with your phone info, then use volume key to select recovery and hit power button to select it. You should be in clock work then, go to install zip from sd card
Sent from my *****'n Nexus S.
I hate to be the bearer of bad news, but rooting and/or flashing a radio will not solve this issue.
What you are describing is a known issue and it is a hardware defect. The touch buttons sometimes incorrectly register a long-press and execute long-press behavior. It affects different buttons on different phones. On phones where the search button is affected, you see long-press behavior of voice search opening. On my phone, back button is affected, so I see long-press of back button behavior. It seems to stop after ten seconds. And sometimes home button is affected, and I see the "recent apps" screen appear.
You can read about the issue here:
http://www.google.com/support/forum/p/Google+Mobile/thread?hl=en&tid=49e8ca84071d51a4
http://www.google.com/support/forum/p/Google+Mobile/thread?hl=en&tid=455215ff8747658b
Maybe you should do some more reading. The radio will fix it.
Hence my two fixed button freaking phones.
Sent from my *****'n Nexus S.
radio flashed and problem solved thanks for ur help guys
So here's the situation. I've been running NoSensi 1.0.4 ROM w/o problems for the past month but all of a sudden tonight my phone started to freeze up. I would take the battery out and turn it back on but after a few minutes the phone would freeze up again. So I decided to try to flash the new version on NoSensi (1.0.8) and the first step was to flash the NoSensi_EXT4_Wipe and it was almost complete in CWM when it froze up and wouldn't respond. Waited a few more minutes to be sure it wasn't just taking a while so I took the battery out and went back into recovery. In CWM, I see the menu options but when I try to select install from SD, the CWM menu would reset every few seconds and leave me at the main screen.
So now I'm stuck with a phone that won't boot cause I don't have a proper ROM on and can't install a new ROM cause CWM is messed up.
Any ideas on how I can reinstall CWM or something?
First off, can you boot to hboot? And next do you have adb set up on your PC or Mac?
I'm gonna be honest with you, I can't really help you all the way but can give you the things you need to get started. And if anyone reads this and knows more about this please help thanks
Sent from my CM7 Nightly HTC Desire HD
Yes, I believe I can get into HBOOT, I get the white screen where the option of going into recovery of HBOOT. I do have adb on my PC, but don't know how to use it unless I have instructions.
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
bluizzo said:
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
Click to expand...
Click to collapse
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Got CWM back with this, thanks so much! I tried doing the same method that was mentioned in this thread http://forum.xda-developers.com/showthread.php?t=1019868 but kept having issues with CWM resetting every 2 seconds which didn't allow me to use it at all. Your file worked and am flashing a ROM on now. Hopefully the random freezing was just random so I'm just going to do a fresh install of a ROM
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Yay that's what I was looking for, thanks soo much
Sent from my CM7 Nightly HTC Desire HD
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
dtothesquare said:
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
Click to expand...
Click to collapse
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Gene Poole said:
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Click to expand...
Click to collapse
Cool, thanks for the tip, i'll try to get stock by on then call them up
So I'm trying to run the PD98IMG image in HBoot, but its not auto-running anymore. Any ideas on how to manually have it run?
- EDIT: Nvm, it was due to bad sdcard
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
So I tried reverting back to stock via the PD98IMG method with both the gingerbread and complete stock in the post you mentioned. Both them it updates fine but on the reboot it just hangs on the white htc screen. Any recommendations? Would HTC warranty if it's stuck like that?
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Gene Poole said:
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Click to expand...
Click to collapse
I figured as much. Oh well, going to miss the Inspire, really did like it except for that stupid battery door. Picked up a used captivate for cheap to hold me over until my next phone. Thanks for your help!
Missing CWM / No Recovery
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
ctownj30 said:
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
Click to expand...
Click to collapse
If you are sure you renamed it correctly (Windows didn't mangle the name with its stupid "hide extensions" feature) and you are S-OFF, then the only other thing it could be is a bad or weak SD Card. Do you have a spare to try?
I solved this. Figured it was not reading my SD cards so I reformatted one (FAT32), redid everything, and was able to re-flash CWM. Bizarre, since the same card has been used successfully several times on this phone.
I bought this phone off ebay and I got two batteries. I am wondering if it is just me butt the seller said the battery was a month old and this thing won't last 3 hours off normal continuous use.and sometimes it just shuts off without giveing me a battery message, of any kind (when im doing something battery intensive)
Also before I knew about the chip issues I flashed and all.I used the method on unlockr.com and when I reached the part to get s off the root.sh wouldn't give me s off so some where in the comments I found a g free script ran it in the terminal emulater in the placer of root.sh and then returned to unlocker and continued to flash with visionary.apk and all is well. Flashed a few roms but im itching to flash like hell as that's, what I'm use to, so is it a case where the chip gets worse everytime I flash or can it go any time? Does it have to go?
I have read the posts and just need a little more clarity.
RUDE COMMENTS ARE NOT WELCOMED
sent from my doomed chip HTC glacier or mytouch 4g
xanda143 said:
I bought this phone off ebay and I got two batteries. I am wondering if it is just me butt the seller said the battery was a month old and this thing won't last 3 hours off normal continuous use.and sometimes it just shuts off without giveing me a battery message, of any kind (when im doing something battery intensive)
Also before I knew about the chip issues I flashed and all.I used the method on unlockr.com and when I reached the part to get s off the root.sh wouldn't give me s off so some where in the comments I found a g free script ran it in the terminal emulater in the placer of root.sh and then returned to unlocker and continued to flash with visionary.apk and all is well. Flashed a few roms but im itching to flash like hell as that's, what I'm use to, so is it a case where the chip gets worse everytime I flash or can it go any time? Does it have to go?
I have read the posts and just need a little more clarity.
RUDE COMMENTS ARE NOT WELCOMED
sent from my doomed chip HTC glacier or mytouch 4g
Click to expand...
Click to collapse
If the chip dies there will be likely be no warning. It will simply fail. Most don't. There are a lot of us with the "bad" eMMC that have flashed hundreds or even thousands of times.
I would flash a new ROM and compare battery life and behavior.
estallings15 said:
If the chip dies there will be likely be no warning. It will simply fail. Most don't. There are a lot of us with the "bad" eMMC that have flashed hundreds or even thousands of times.
I would flash a new ROM and compare battery life and behavior.
Click to expand...
Click to collapse
Ok I'm feeling a but more comfy now.and obviously I won't blame you should something go wrong. Thanks.makes no sense living in fear might as well enjoy it while it lasts
sent from my doomed chip HTC glacier or mytouch 4g
xanda143 said:
Ok I'm feeling a but more comfy now.and obviously I won't blame you should something go wrong. Thanks.makes no sense living in fear might as well enjoy it while it lasts
sent from my doomed chip HTC glacier or mytouch 4g
Click to expand...
Click to collapse
If your on stock battery will probably suck. It did for me
Sent from my HTC myTouch 4g using xda app-developers app
N_otori0us_ said:
If your on stock battery will probably suck. It did for me
Sent from my HTC myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
yeah i notied the huge diffrence when i switched to the viper rom........haveing a little trouble finding a compatible kernel that will give me smartass v2 tho.
quick question does a nandroid backup also backup the kernel that i was on when i made the backup?
crap i made a mistake and flashed a wrong kernel(fusion dragon and now the phone dosnt want to boot into recovery). i think the kernel was for the one S i didnt notice that. Anyway i know androids so am not worried about anything except my emmc chip can anyone give me the fastbood instructions to flash the various things on the glacier or are they the same for all phones also. a kernel that i can flash the will work with this viper rom would be nice.
i was trying fastboot flash zip rom.zip and that fails.
was really trying to avoid haveing to flash a PDM15.img but it as that would erase my ext4 recovery which i figure isnt working because the kernel i flashed was not for the phone and being touch based is messed up. so anyone knoe the fastboot commands to flash a rom in its zip form
xanda143 said:
crap i made a mistake and flashed a wrong kernel(fusion dragon and now the phone dosnt want to boot into recovery). i think the kernel was for the one S i didnt notice that. Anyway i know androids so am not worried about anything except my emmc chip can anyone give me the fastbood instructions to flash the various things on the glacier or are they the same for all phones also. a kernel that i can flash the will work with this viper rom would be nice.
i was trying fastboot flash zip rom.zip and that fails.
was really trying to avoid haveing to flash a PDM15.img but it as that would erase my ext4 recovery which i figure isnt working because the kernel i flashed was not for the phone and being touch based is messed up. so anyone knoe the fastboot commands to flash a rom in its zip form
Click to expand...
Click to collapse
Download the 4ext recovery image and
fastboot flash recovery recovery.img
Then boot into recovery and try flashing the zips. If you can't find the recovery.img, cwm images are available. You can easily switch back to 4ext later.
estallings15 said:
Download the 4ext recovery image and
fastboot flash recovery recovery.img
Then boot into recovery and try flashing the zips. If you can't find the recovery.img, cwm images are available. You can easily switch back to 4ext later.
Click to expand...
Click to collapse
i already have fastboot flash zip PD5IMG.zip and it worked ok and gave me back clockwork and official sesnse but should flashing an incompatible kernel damaged my recovery? seems flawedish seeing as i always saw recovery mode as my safe heaven. being its a touch recovery i can understand tho. if i had not flashed a eng bootloader i probly would have been screwed now. well lesson learned any info on a kernel that can work with the viper rom android 4.04 sense?
xanda143 said:
i already have fastboot flash zip PD5IMG.zip and it worked ok and gave me back clockwork and official sesnse but should flashing an incompatible kernel damaged my recovery? seems flawedish seeing as i always saw recovery mode as my safe heaven. being its a touch recovery i can understand tho. if i had not flashed a eng bootloader i probly would have been screwed now. well lesson learned any info on a kernel that can work with the viper rom android 4.04 sense?
Click to expand...
Click to collapse
Not sure about the kernel. I can tell you that different devices have different partition setups. The bootloader, system, recovery, etc. don't reside on the same partitions on every device. In fact, doing what you did can cause a hard brick on many devices.
what kernal did you use?
kkm323 said:
what kernal did you use?
Click to expand...
Click to collapse
The kernel wasn't for this phone so he got messed.
Sent from my myTouch 4g using xda app-developers app