[SOLVED] 3G/H doesn't work right - myTouch 4G Q&A, Help & Troubleshooting

So I've had this issue for about a week now. Seemingly randomly, my 3G/H stopped working right. It would not get a downlink connection at all. The up arrow lights, but down arrow does not. I have had a very similar problem before on my G2, but it was because I was not on the right data plan. T-mo assures me I am on the right plan now, but I am having the issue on my MT4G. I am on RoyalGinger 2.0 right now, but have also used Evil's Sense 3.0 ROM with the same result. Putting my SIM into another phone makes the issue go away. And when I switch to 2G, the phone works fine, the down arrow lights up like normal. SO basically, right now my phone ONLY works in 2G mode. Anyone ever heard of this on the MT4G? I have heard chatter about this being like a weird known issue, but no one else I know has this issue, and my SIM in another phone works fine. Do you think if I loaded the stock ROM and unrooted it would reset or something? I do not have a warranty since I bought this on CL and this is making me crazy.

what radio are you on, and also are you doing a full wipe and clear cache/dalvik?
Sent from my 3.0 Glacier

I don't know where to look to find out exactly what "radio" I am using. But here is what is in my About Phone section. If the radio info is someplace else, please let me know where I can find it.
As for whether I do a full wipe, absolutely. I do wipe data, wipe cache, wipe dalvik cache, format system, format data, format cache and even accidentally format SD card once... That blew actually.... Cause I didn't have a backup and I lost all my backups and pics and such.... Anyway, if you can glean any info from this, let me know. If I need to get you more info, let me know. Thanks for the reply.
Edit: Dumbass moment... Sorry, I just realized I knew where to find my radio info. Serious brain fart. Here's what my bootloader says:
GLACIER PVT ENG S-OFF
HBOOT-0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14

Try updating the radio for fusion rom, you can get in the stickies for android development. The newer radio is 26.09.04.26, and use hboot to install update or adb.
Place .zip on sd/root
Sent from my UD Glacier

Wow dude.. I updated to the latest radio and I see 4G again and so far it seems to be working. That is fantastic, you get a thanks from me. I appreciate it. If it goes out in a day or so I will report back, but I hope this fix stays a fix. THANKS!

No problem man, glad it work
Sent from my 3.0 sense Glacier

Just a friendly suggestion, when marking a thread as [SOLVED] you should post the solution to your problem in the OP. Glad you got everything worked out.

Related

Can't load custom roms anymore

I hope that this isn't a repost, I've searched quite a bit but nothing is exactly like what i'm experiencing.
Here's what happened, i'll try and make this short and to the point.
Got my new evo, rooted it using unrevoked 3 and got root access.
Loaded a few custom roms, no problem, finally settled on Calkulin's EViO rom. Everything was working great, 4G was perfect, blah blah blah, buddy with an evo told me that Cyanogen was the poo and that I had to flash to that as it was the best ever.
I download Cyanogen 6.1.2 from cyanogen's forum and proceeded to flash it to my phone after doing a nand backup on my current rom. I forgot to back up my RSA keys (didn't even know i had to in the first place) and after cyanogen loaded, I read the thread that states that flashing cyanogen make screw up your wimp key and that you should backup your RSA keys (crap!) before loading cyanogen. Well after reading this and freaking out, I went back into recovery, wiped everything, and loaded the recovery img of the last rom I was running on my evo.
Now my 4G doesn't work in calkulin (posted a thread about that a couple days ago), and I'm not able to load any rooms except for backups, a fresh copy of calkulin, and a fresh copy of cyanogen 6.1.2.
When i try to load a new rom (warm 2.2 for example), it'll load, but when i go and reboot, it'll sit at the white HTC EVO screen forever .. nothing will change until I pull the battery out and start the phone back into recovery. I can reload one of my old backup images and everything works fine again.
I've cleared all the memory, delvik cache, everything. I even formatted my SD card after backing it up and loading just the roms on there. that didn't help either.
Any help would be fantastic .. I'm completely floored as to why I can't load anymore rooms.
Also, i want my wimax back!
wow.. sorry.. i hope someone can help you.
but I would think, you have to call sprint. they may have the wimax info for your phone.. and how to put it back.
for my knownledge... how do you get the information RSA keys and wimax info.. so I can backup mine?
Here's how to backup your RSA keys
http://androidforums.com/evo-4g-all-things-root/248586-question-how-backup-wimax-rsa-keys.html
And issue is resolved.
amon recover > clockwork
4G is working now too. wewt.
thanks..
that is great you got it done.
I dont use clockwork.
dizzle247 said:
I hope that this isn't a repost, I've searched quite a bit but nothing is exactly like what i'm experiencing.
Here's what happened, i'll try and make this short and to the point.
Got my new evo, rooted it using unrevoked 3 and got root access.
Loaded a few custom roms, no problem, finally settled on Calkulin's EViO rom. Everything was working great, 4G was perfect, blah blah blah, buddy with an evo told me that Cyanogen was the poo and that I had to flash to that as it was the best ever.
I download Cyanogen 6.1.2 from cyanogen's forum and proceeded to flash it to my phone after doing a nand backup on my current rom. I forgot to back up my RSA keys (didn't even know i had to in the first place) and after cyanogen loaded, I read the thread that states that flashing cyanogen make screw up your wimp key and that you should backup your RSA keys (crap!) before loading cyanogen. Well after reading this and freaking out, I went back into recovery, wiped everything, and loaded the recovery img of the last rom I was running on my evo.
Now my 4G doesn't work in calkulin (posted a thread about that a couple days ago), and I'm not able to load any rooms except for backups, a fresh copy of calkulin, and a fresh copy of cyanogen 6.1.2.
When i try to load a new rom (warm 2.2 for example), it'll load, but when i go and reboot, it'll sit at the white HTC EVO screen forever .. nothing will change until I pull the battery out and start the phone back into recovery. I can reload one of my old backup images and everything works fine again.
I've cleared all the memory, delvik cache, everything. I even formatted my SD card after backing it up and loading just the roms on there. that didn't help either.
Any help would be fantastic .. I'm completely floored as to why I can't load anymore rooms.
Also, i want my wimax back!
Click to expand...
Click to collapse
dizzle247 said:
Here's how to backup your RSA keys
http://androidforums.com/evo-4g-all-things-root/248586-question-how-backup-wimax-rsa-keys.html
And issue is resolved.
amon recover > clockwork
4G is working now too. wewt.
Click to expand...
Click to collapse
Glad you got it working bro. Just for everyone that is new who may read this thread Cyanogen DOES NOT break your 4G keys. Older versions of Clockworkmod Recovery will. Follow the how to backup your RSA keys before doing Anything with the EVO.
Just because 4G is not yet included in Cyanogen Rom's does not mean it breaks your 4g. In fact, thanks to some of our dedicated and smart devs there is an actual Alpha of CM 6.1.2 with 4g and from what I hear it works pretty damn good.
Anyway I just wanted to clear that up because I would not want anyone to think that CM Rom's break your 4G. I am sure the OP meant Clockworkmod Recovery, but said CM in a rush to try to figure out his problem.
housry23 said:
Glad you got it working bro. Just for everyone that is new who may read this thread Cyanogen DOES NOT break your 4G keys. Older versions of Clockworkmod Recovery will. Follow the how to backup your RSA keys before doing Anything with the EVO.
Just because 4G is not yet included in Cyanogen Rom's does not mean it breaks your 4g. In fact, thanks to some of our dedicated and smart devs there is an actual Alpha of CM 6.1.2 with 4g and from what I hear it works pretty damn good.
Anyway I just wanted to clear that up because I would not want anyone to think that CM Rom's break your 4G. I am sure the OP meant Clockworkmod Recovery, but said CM in a rush to try to figure out his problem.
Click to expand...
Click to collapse
thanks for clearing that up .. I'm not sure exactly what I read as I glanced over it and freaked out because I didn't want to ruin my wimax keys .. so thanks for the clarification.
I've been trying to install the 6.1.2 with wimax but I keep getting hung up on the white evo screen, as well as others .. I'm tempted to install CM7 and forget about 4G for the time being as I know toast will get it up and running in the upcoming months.
Hopefully someone can figure out the reason as to why the wimax alpha is hanging at the htc evo screen after installing the kernal.

More boot loops, not like the others

Ive got the following on the HBOOT screen
GLACIER PVT ENG S-OFF
HBOOT=0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Clockwork v3.0.0.6 (using this method http://forum.xda-dev...ad.php?t=944681 )
Okay so with that for reference, I'd like to find out why I can't flash CM7 without the blue Andy bootloop. I understand that a fresh install takes time to load, I gave it 30mins before a battery pull, I then returned the battery, hit the top power button and let that sit for another 20. Before I flashed the ROM (through recovery) I made the following wipes in this order; wipe data/factory reset and then wipe cache partition. I've flashed other ROMs that have flashed without issue (Ice Glacier 1.1.6 themed and Royal MIUI) but, lets face it CM owns. Any help would be appreciated. Thank you for reading this.
DHSdrone said:
Lets face it CM owns.
Click to expand...
Click to collapse
No, Sense owns.
With that out of the way, the only thing I can think of is a corrupt download. Try re-downloading the zip to your PC and copying it to your SD. My other thought was a bad recovery, but since you've successfully flashed other ROMs, that doesn't seem likely.
you didn't wipe dalvik in advanced, do that and bootloop will stop...
darinmc said:
you didn't wipe dalvik in advanced, do that and bootloop will stop...
Click to expand...
Click to collapse
Little known fact, if you wipe data, you already wiped dalvik.
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Mmmhmm, the only thing it could be is bad download or some other mysterious gremlin lol
Sent from my HTC Glacier using XDA Premium App
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Well then I retract my statement...
when you say bad or corrupted download I assume your talking about the recovery. I thought the same as well, Ive tried both versions of what was posted as the correct, best, and or easiest method of clockworkmod recovery. Im not sure if both versions were in fact the same recovery.img but they both worked for the roms Ive flashed except for cm (nightly 29, cm7-rc2, rc3,and rc4). The fact tjat I cant get this to work, only makes me want it more.
DHSdrone said:
when you say bad or corrupted download I assume your talking about the recovery.
Click to expand...
Click to collapse
No, I mean the CM7 download. The actual ZIP file that you flash.
As far as recovery versions, only 3.0.0.5 and 3.0.0.6 can flash CM7.
Ive tried flashing several different versions of cm7, starting with rc-2 through rom manager. When that gave me my first boot loop I went back to the method I was more familiar with. With trying the different versions I don't see how they were all currupt or broken downloads. I haven't tried any of the cm froyo roms yet.
As far as my earlier statement of "cm owns" I mean no disrespect of any of the other rom developers (including those that did work properly the first time). Ive just came from the G1 and cm is the only rom I ran. Sense may be the best way to go, it's not something Ive given much consideration or time.
I have had the same issue except mine seems to be all 2.3 (Gingerbread) based roms, they all go to bootloop. I have no problem however flashing any of the 2.2 based roms. I also have cwm 3.0.0.6
I had the same issue everytime with different nightly releases. After wiping everything and formatting boot and system still would do it. I found if you wipe then install cm7 only the phone boots fine then reboot setup wifi if your using it the go back into recovery install gapps and it works fine.
Sent from Teh retardarded duc using XDA Premium App
Im unable to get a full boot. After reading several similar sorties I've always turned off all wireless radios. Will post a logcat later today.
Ok so was able to get mine to Boot completely Finally!!! I am somewhat of anoob so sorry if it seems confusing.
1.From recovery wipe data/ factory
2. Wipe cache
3.Advanced > wipe dalvik
4.Mounts>format boot
5.Mounts>format system
6.Advanced> partion SD card (I believe I used 256) No swap partition(dont know if it matters)
7.Mount USB and transfer cm7 and Gapps
8.Flashed cm7 only not apps.
9.Reboot phone (should boot all the way up)
10.Go back to recovery and flash Gapps
11.Reboot phone
My phone booted up very quickly. I hope this helps anyone else out there with the same issue
no more loop da loops
After searching google, and then to various forums, and finally giving up and posting to 2 separate forums, Ive come to say THANK YOU !!! You are all evil geniuses of the highest degree and I bask in your greatness. Ive been overlooking one thing, that is the "if things go bad, try the sd-card format" well I did and it worked. Now that the derp has left my head, and the panic has subsided I can see now that my problem was in fact like many others, and the answers were right in front of me. Again thanks for being patient and coming together as a community to help me out.

Evo 4G stuck in hboot

EVO 4G rooted with Unrevoked. Right now I can only boot into bootloader and fastboot. There is no ROM and It will not let me load ROM or recovery from fastboot or sdcard. I can fumble around fastboot and adb but most of the time I get an error.
sending 'recovery' (209 KB)...
OKAY [ 0.273s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.274s​
Here is the bootloader info:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041F
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00​
Any help greatly appreciated! If I am in the wrong place, very sorry
Which recovery are you trying to flash and how?? via PC36IMG?
Thanks for the reply!!! recovery-RA-supersonic-v2.3.img. and update-cm-7.1.0-Supersonic-signed.zip I tried both as pc36img from HBoot and via fast boot. neither worked. I also tried to install to change boot.img via fastboot. same message.
Look for the Amon Ra thread in the Development section, grab the PC36IMG.zip Make sure that it's named exactly like that and flash that in Hboot. That should give you recovery.
i wish there was odin for htc devices
Will try that again first thing in the a.m. Been working on it all day and the brain is mush! I'll post the result as soon as I'm done. Thanks!
Sent from my PG86100 using XDA App
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
That was what happened to me sorta. I have been flashing that phone since November of last year. Something must have hiccuped during the last flash process because I have never had that happen before. This is my first possible brick and I am really pissed that I can't figure it out!!! Arrrgg! Off to start over with the new Amon RA recovery! Wish me luck!
johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
Well this happened to me once, what i did was i put on my sd card any other rom (i was using cm7 nightlies so i put another nightly in) and then i wiped cache and flashed it, however it might also help if from this link http://forum.xda-developers.com/showthread.php?t=1295702 you get the format all zip and use that to wipe everything. once you have flashed another rom and your phone turns on wait a little bit and then try once again to flash the first rom you were trying to flash.
[email protected] said:
That was what happened to me sorta. I have been flashing that phone since November of last year. Something must have hiccuped during the last flash process because I have never had that happen before. This is my first possible brick and I am really pissed that I can't figure it out!!! Arrrgg! Off to start over with the new Amon RA recovery! Wish me luck!
Click to expand...
Click to collapse
can you go to the recovery? if you can try to do what i told johnnyboy1409
HipKat said:
Look for the Amon Ra thread in the Development section, grab the PC36IMG.zip Make sure that it's named exactly like that and flash that in Hboot. That should give you recovery.
Click to expand...
Click to collapse
Holy Cannoli!! Ok that .zip worked for the recovery (I tried several different downloads!) Now I have to see if I can copy an image. Wish me luck!
Thanks for the info. I totally though the phone was bricked. Actually the phone would load in HBoot and Fastboot but I couldn't get a recovery on or a ROM. In other words there was no ROM to boot to. In addition to that, wether I tried from SD card or fastboot, I couldn't get any .img, .zip etc to install. So here I was with an HBoot - S-off and no way to get a recovery or ROM on the puppy. I am still working on this and still jammed up but the recovery gives me hope. Please stick around in case I have a meltdown. (hasn't happened yet but I can feel it getting closer!) LOL
Stick around for the detail of what I did If I can get this ROM onboard! Maybe this will help someone else.
Success!!! I have a recovery and a ROM!
Here are the details...First I believe my SD card was/is corrupted. I am still using it and I formatted it several times but I think something was squirrely which is now fixed. Second, the Amon Ra PC36IMG.zip that I downloaded at : http://forum.xda-developers.com/showthread.php?t=705026&highlight=recovery
worked awesome to get a working recovery via HBoot and SD Card. Next, I used the new recovery to load my ROM. and Voila a working phone.
Moral of the story, Check the SD card, USB drivers, and file downloads for corruption. I think one or all of these played a part in my crash.
@ Johnboy this is an excellent group of developers and members here at XDA, I have been flashing both Winmo and Android for a long time but can always rely on the forums to bring me back to center when I crash and burn! Thanks everyone for your help.
You should try wiping everything but your SDcard: option and flashing a ROM first and see what happens
HipKat said:
You should try wiping everything but your SDcard: option and flashing a ROM first and see what happens
Click to expand...
Click to collapse
That's Funny, I just did that and everything is fine. I just reloaded the ROM and looks like something just got corrupted and all I needed was a little help from my friends to figure things out
[email protected] said:
Success!!! I have a recovery and a ROM!
Here are the details...First I believe my SD card was/is corrupted. I am still using it and I formatted it several times but I think something was squirrely which is now fixed. Second, the Amon Ra PC36IMG.zip that I downloaded at : http://forum.xda-developers.com/showthread.php?t=705026&highlight=recovery
worked awesome to get a working recovery via HBoot and SD Card. Next, I used the new recovery to load my ROM. and Voila a working phone.
Moral of the story, Check the SD card, USB drivers, and file downloads for corruption. I think one or all of these played a part in my crash.
@ Johnboy this is an excellent group of developers and members here at XDA, I have been flashing both Winmo and Android for a long time but can always rely on the forums to bring me back to center when I crash and burn! Thanks everyone for your help.
Click to expand...
Click to collapse
np ^_^ hope i helped, whenever i think my phone has an issue booting or something i just automatically assume that it's fixable, i haven't had my phone die on me yet and i'm not planning on it... *cough cough* Screw Apple *cough cough*
johnnyboy1409 said:
i am having a similar problem. nothing will put my phone into recovery. I even went to sprint and the guy there had rooted 2 of his phones and he couldnt help me.
-Revolutionary-
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.0808
i have been rooted for a while and i have changed ROMS many times. but the other day i flashed fresh evo and my phone wouldnt reboot and i thought i screwed it up but then after a minute it came on. realized that ROM wasnt what i wanted and i flashed myn warm 2.2 and it rebooted just fine but when my phone turned on, it just kept initializing and didnt end up running. then i realized i didnt flash the radio and wimax updater it came with. so i went into recovery and wiped everything then reflashed the rom and radio wimax and it just froze in the white htc evo 4g screen. getting to hboot and bootloader works fine but freezes when i try to go to recovery.
if i didnt make sense or said something stupid i apologize!! i am a 4 month noob. any help is appreciated!! thanks!!
Click to expand...
Click to collapse
Johnnyboy1409 Did you ever get this fixed?
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
johnnyboy1409 said:
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
Click to expand...
Click to collapse
when you go to boot loader and it loads, it then should ask if you want to update splash - hit no, then to reboot - hit no, then you should be able to go one down and hit recovery. do you get those options?
I get those options but when I click recovery it goes to the white htc Evo 4g screen and stays there no matter how long I wait.
johnnyboy1409 said:
No it won't let me go into recovery to flash anything. All I need is a trick to get into recovery and I can wipe everything then perform a nandroid restore. I already have had the pc36img.zip on the root of the zip. It is copied correctly but idk if I spelled it right on here cuz I'm on my girlfriends phone and can't remember it.everytime I boot into hboot that zip updates but doesn't help...
Click to expand...
Click to collapse
I know I sound like a broken record but try formatting your SD card or using a different known good card and also use the link in my post above to re-download the pc36img.zip Amon RA Recovery. Then you know all the components are "clean and without erro". Then you can start to figure out the problem.

[Q] Stuck on Boot logo after updating radio

Hi
I am currently on DARKSIDE CM7.2.0 rc1 and was experiencing quick battery loss during calls. So I decided to update the radio but after following the instructions and flashing few radios I am still stuck on boot logo.
Following are details of Bootloader
GLACIER PVT ENG S-OFF
HBOOT-0.85.2007
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,12:44:14
I tried following radios
http://www.androidinsomnia.com/r-and-r/
Download: 12.28b.60.140e_26.03.02.26 - T-Mobile MyTouch 4G
Download: 12.58.60.25_26.11.04.03
Download: 12.62.60.27_26.13.04.19
Can anybody suggest how to fix this. I hope I haven't bricked the phone.
Thanks.
Flash 2.2.1 PD15IMG.zip. If you get a failed-PU update, you're bricked.
Issue fixed
Actually after the Radio update some how access to cache partition was not available. I booted in to recovery from ADB and got an alert regarding formatting cache.
So to be on safer side I formatted all partition except SD and restored it from my ROM backup.
For past 30 mins my heart was in my mouth and I was already planning to buy Galaxy S3 but I guess Glacier is quite robust and with such a wonderful developer community it has a long way to go.
Thanks for responding.
archangel25 said:
Actually after the Radio update some how access to cache partition was not available. I booted in to recovery from ADB and got an alert regarding formatting cache.
So to be on safer side I formatted all partition except SD and restored it from my ROM backup.
For past 30 mins my heart was in my mouth and I was already planning to buy Galaxy S3 but I guess Glacier is quite robust and with such a wonderful developer community it has a long way to go.
Thanks for responding.
Click to expand...
Click to collapse
Ok good you fixed it! And you posted how in the response right? It might be helpful to people in the future.

[Q] peer review request

So, I'm new to this forum but this isn't the first device I've ever liberated from the carrier's limitations. I've had this Glacier/MyTouch 4G since it was new. It is my primary phone until I upgrade early next year. It's long out of warranty and started giving me a few problems not long ago (which I found was a failing micro SD card).
After recovering it from that I decided to change it from the stock T-Mobile version 2.3.4 and did the firmware downgrade to root it using the gfree and visionary method.
All was successful with no problems thanks to this forum. By the way a big THANK YOU FOR THAT! :good:
I now have the engineering bootloader, and am running cyanogenmod 7.2.0 stable at present although my goal is to find a stable ICS or possibly JB ROM for it if possible.
The bootloader reads as follows:
Glacier PVT ENG S-OFF
HBOOT-0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,12:44:14
My question is, what else do I need to consider doing prior to looking at other ROMs and eventually settling for something permanently?
I'm not unhappy with cyanogenMod 7.2.0 (although I may try the newer nightly) but I would like to get to at least ICS.
I read something about updating the RADIO but am not sure if that's necessary or not. Perhaps someone could guide me based on the above info. If there is any other updates I've missed along the way on this project, pointing that out is also greatly appreciated.
I noticed immediately that the Google Play Store, etc. wasn't there when I installed cyanogenMod and got that update in, so all that is working quite well at this point.
Again, thank you forum for your excellent instructions that worked flawlessly for me on the first try and got me to this point. I have gone through and hit the thanks button on all the threads I used.
A couple things, they aren't really necessary, more of precautions.
1) Do a nandroid of your current rom
2) Before you flash the new rom, do a FULL wipe, this means data, system, cache, dalvik yada yada
3) get 4EXT recovery, it really is a time saver
Get 4ext recovery and have a pretty good sized microsd. The radio is more of an experiment on your own time thing, if you're curious to see if there are any improvements then flash away, but if you don't care, then you'll be fine on stock radio.
Oh, and make sure you have everything you need prior to flashing a ROM such as gapps and additional files like newer kernels and fixes
Sent from my LG E960
Thanks for the responses. I've been doing backup/restore using ClockworkMod Recovery and I noticed it came already installed on CyanogenMod.
I've gotten familiar with the interface so Is that one okay vs. the ones mentioned or should I switch?
As far as the Radio, I read up on it and downloaded the various ones to try so I'm fairly confident I can accomplish that if need be.
From what I read, I understand I should travel around to my usual locations and see what my signal is like, and also watch my battery life to see which works best if I decide to experiment with Radio options. Having used T-Mobile for so many years I already know all the areas I travel to and have good signal or none at all (way too many with little or none at all).
I know prior to rooting I was getting solid 4G in my home. I ran speedtest this morning and am seeing between 4622-5722kbps down and 1605kbps up. I think that's not too bad although I notice the icon fluctuates between 3G and HSPA frequently, where with the stock phone it was consistently 4G (as far as the icon displayed anyway).
I'm using an 8GB microSD card and occasionally I'm going to connect it to a computer and copy those backups off to other storage, just in case.
Icon means nothing (or actually, the stock lies and 3G/H are telling the real connection state). The connection is the same.
Jack_R1 said:
Icon means nothing (or actually, the stock lies and 3G/H are telling the real connection state). The connection is the same.
Click to expand...
Click to collapse
That's pretty much what I thought too, especially based on my speedtest results. I know from years of experience with T-Mobile that they stretch the truth on not only data speeds but also network coverage maps which like in the Pirates of the Caribbean movies are more "guidelines" than anything else.
However, since I do see that constant fluctuation between the 3G/H icons so frequently, experimenting with the different radios might be worthwhile.
Thanks for your response.
1600RoadStar said:
Thanks for the responses. I've been doing backup/restore using ClockworkMod Recovery and I noticed it came already installed on CyanogenMod.
I've gotten familiar with the interface so Is that one okay vs. the ones mentioned or should I switch?
As far as the Radio, I read up on it and downloaded the various ones to try so I'm fairly confident I can accomplish that if need be.
From what I read, I understand I should travel around to my usual locations and see what my signal is like, and also watch my battery life to see which works best if I decide to experiment with Radio options. Having used T-Mobile for so many years I already know all the areas I travel to and have good signal or none at all (way too many with little or none at all).
I know prior to rooting I was getting solid 4G in my home. I ran speedtest this morning and am seeing between 4622-5722kbps down and 1605kbps up. I think that's not too bad although I notice the icon fluctuates between 3G and HSPA frequently, where with the stock phone it was consistently 4G (as far as the icon displayed anyway).
I'm using an 8GB microSD card and occasionally I'm going to connect it to a computer and copy those backups off to other storage, just in case.
Click to expand...
Click to collapse
About recovery, i would say that you are better off switching, 4EXT gets the job done faster and its known to produce less problems when flashing the roms. Its completely optional but its highly recommended plus it only takes a couple minutes of your time.
Point taken, thank you.
Sent from my A500 using xda app-developers app
THEindian said:
About recovery, i would say that you are better off switching, 4EXT gets the job done faster and its known to produce less problems when flashing the roms. Its completely optional but its highly recommended plus it only takes a couple minutes of your time.
Click to expand...
Click to collapse
I did install and am using nandroid and I'd like to ask a question regarding using 4EXT instead of CWM recovery.
I'm now using the most recent cyanogenmod nightly and I see that like the previous version it has CWM recovery pre-installed. Looking at it in the apps list it allows uninstalling updates only, and not complete removal. Is installing 4EXT going to interfere with that or am I safe to do it because it will then be the default custom recovery? Or is there something else I'll need to accomplish to remove CWM recovery first?
Apologies for the beginner questions I'm sure these are but I haven't been able to find a thread clearly explaining this aspect.
1600RoadStar said:
I did install and am using nandroid and I'd like to ask a question regarding using 4EXT instead of CWM recovery.
I'm now using the most recent cyanogenmod nightly and I see that like the previous version it has CWM recovery pre-installed. Looking at it in the apps list it allows uninstalling updates only, and not complete removal. Is installing 4EXT going to interfere with that or am I safe to do it because it will then be the default custom recovery? Or is there something else I'll need to accomplish to remove CWM recovery first?
Apologies for the beginner questions I'm sure these are but I haven't been able to find a thread clearly explaining this aspect.
Click to expand...
Click to collapse
I'm guessing you mean ROM Manager?
CWM is the official recovery of Cyanogenmod. However, 4EXT Recovery works very well. I've had zero issues using it with ROM Manager. Never, I repeat, never install a ROM using the menu in ROM Manager. ALWAYS reboot to recovery and do it manually.
Sent from my Nexus 4 using xda app-developers app
1600RoadStar said:
However, since I do see that constant fluctuation between the 3G/H icons so frequently, experimenting with the different radios might be worthwhile.
Thanks for your response.
Click to expand...
Click to collapse
When there is a data transfer of any kind, HSPA connection is negotiated and you see H.
When the phone is idle and doesn't transmit anything, you see 3G.
Perfectly normal.
You're welcome.
1600RoadStar said:
I did install and am using nandroid and I'd like to ask a question regarding using 4EXT instead of CWM recovery.
I'm now using the most recent cyanogenmod nightly and I see that like the previous version it has CWM recovery pre-installed. Looking at it in the apps list it allows uninstalling updates only, and not complete removal. Is installing 4EXT going to interfere with that or am I safe to do it because it will then be the default custom recovery? Or is there something else I'll need to accomplish to remove CWM recovery first?
Apologies for the beginner questions I'm sure these are but I haven't been able to find a thread clearly explaining this aspect.
Click to expand...
Click to collapse
All you've got to do is install 4ext. Madmaxx made it easy to go from cwm to 4ext, all of my backups stayed intact after I made the switch a while back.
Sent from my SGH-T999 using xda app-developers app
Jack_R1 said:
When there is a data transfer of any kind, HSPA connection is negotiated and you see H.
When the phone is idle and doesn't transmit anything, you see 3G.
Perfectly normal.
You're welcome.
Click to expand...
Click to collapse
Makes sense. My plan is to leave the current radio alone. :good:
Synthetic.Nightmare said:
All you've got to do is install 4ext. Madmaxx made it easy to go from cwm to 4ext, all of my backups stayed intact after I made the switch a while back.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Awesome, thank you. I was reading about your ROM earlier today, the positive remarks of it convinced me it'll be the one I try next as I'm looking for an ICS daily driver although I'm entirely happy with my current cyanogenmod installation.
estallings15 said:
I'm guessing you mean ROM Manager?
CWM is the official recovery of Cyanogenmod. However, 4EXT Recovery works very well. I've had zero issues using it with ROM Manager. Never, I repeat, never install a ROM using the menu in ROM Manager. ALWAYS reboot to recovery and do it manually.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is what I meant. I'm still getting some of the names and terminology confused. I have used ROM manager to install the ROMs I've tried so far but will discontinue that.
Well, it's been a few weeks since I started on this adventure and it hasn't been a very smooth ride. I went from stock GB to CyanogenMod 7.2.0 stable to cm-7-20121007 nightly to SyNthetic_aospX to cm10.1 unofficial and back to SyNthetic_aospX which I finally settled on as my daily driver.
My goal was to get the phone to a very stable and reliable ICS or JB ROM that I could use until I upgrade in another month. During the installing of one ROM I got the dreaded
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/last_log
E: cant open /cache/last_log
errors that I posted in this thread: http://forum.xda-developers.com/showthread.php?t=2063057&page=24.
After that I was able to recover it by reinstalling Froyo using PD15IMG.zip and rerooting using visionary and recovery manager to reinstall SyNthetic_aospX.
That worked well for awhile until one morning I woke up and went to take my phone off the charger and found it to be shut off and unresponsive.
I pulled the battery and got it into recovery and when rebooting got the dreaded
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/last_log
E: cant open /cache/last_log
again.
I had nandroid backups but they all failed when attempting them with the same error messages as above.
Finally, after many attempts I was able to get the phone back to stock GB using the PD15IMG.zip.
The phone is back to stock except for apparently still having S=OFF
The bootloader now reads as follows:
GLACIER PVT SHIP S-OFF
HBOOT-0.89.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
Jul 15 2011, 16:45:17
Not sure what to do now, if anything. I really can't afford the time to tinker with the phone any more not knowing if I'll have additional problems with a different ROM. It is my primary phone and although I'd like root back to get rid of the unnecessary apps I don't want to risk errors or bricking.
And so the saga continues...
After awhile running the stock gingerbread once again the phone began locking up and shutting down the other day. When this began happening the first time I thought it was a bad SD card but that seems to have eliminated itself as the problem now. This time I'm thinking the battery may be the culprit.
Right before it happened I saw a message appear that said the SD card had been mounted read only. The phone was sitting untouched when it happened.
I was once again able to reinstall stock Froyo, gain root with visionary and get 4EXT recovery installed so now I'm running the debloated and rooted stock GB on it (I never lost permanent S-OFF so it was easy).
Still saw:
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/last_log
E: cant open /cache/last_log
but 4EXT recovery seemed to handle it better than Recovery Manager did so eventually the custom ROM worked.
I read it thread and saw u were using cm7.2 before. For me with that version of cm7 it was not stable, kept getting signal drops. I think its due to the fact that its based on gb 2.3.7 as well is cm7.1.
If u want a rock solid cm7, then flash cm7.0.3 no problems there just doesn't have as much options as the later. I also use it with Holo launcher which is an ics/jb aosp themed launcher for gb
Cm7.0.3 is gb 2.3.3
Sent from my HTC Mytouch 4g using xda app-developers app
If you have time, you might want to get familiar with adb to root your phone using computer commands. I've read people have had better success permanently rooting their device that way.
elmagnificado said:
If you have time, you might want to get familiar with adb to root your phone using computer commands. I've read people have had better success permanently rooting their device that way.
Click to expand...
Click to collapse
That's what I did, using the gfree and visionary method which requires ADB.
(http://forum.xda-developers.com/showthread.php?t=858996)

Categories

Resources