Related
Have HardSPL installed on phone. Got phone on eBay - has very few hours. Came with a Rom that displayed TEST ONLY which was WM5. GSM radio worked, Bluetooth worked and Wifi worked. Tried installing shipped HTC WM6 Rom - did it through ActiveSync - should have used MSD card. - Rom installed though everything was ok but didn't install a SIM card to test phone - used it as PDA and WIFI for a week no freezes. Now this morning wanted to switch phones over and inserted SIM - saw NO GSM on boot - never really noticed it before.
Checked in ABOUT section to see if a radio was loaded - comes up blank. Read some things about NO GSM errors - got a little nervous - so I thought I'd reflash entire ROM tonight with SD.
Followed directions and get into update process and it seems to freeze at GSM with progress bar at about 15% - for about 30 minutes.
Removed battery and it boots to TRICOLOR. (I freeked out at this point)
Put a HardSPLv7 on SD card and did the above - update was successful
Phone boots up to OS still with no GSM
Tried the update process again with the same ROM - still has problems and never gets past the same point as before. Will try another ROM but I'm a little doubtful. If I can recover it back again will try just upgrading radio to see if it makes a difference.
ANY SUGGESTIONS or is the hardware fried?
Thanks.
OK, think it may be back and I was able to reflash using a wm6 stock HTC ROM. Think either my original flash of the same ROM was bad - downloaded a new file and flashed with the SD - originally did it via ActiveSync.
To get it to work I did a couple of hardspl reflashes and got into the OS. DID a couple of hard resets and magically GSM appeared. Turned phone off and then NO GSM appeared again. Did the hard reset again - came back. Not taking anything for granted put in a SD card and reflashed. Held my breath and for some reason it did a complete flash and never really hung up for more than a minute or two. Soft reset - GSM was there. Turned phone off and on a few times and its still there. Phone now finds the GSM radio much faster than before. Can make and receive calls (does wake out of sleep) - signal strength is same on my other Cingular 2125. Will try out tomorrow and see how it goes. Either the reflash does it or something is loose in the hardware but if it works a few hours tonight it should be good.
Will be a little hesitant to reflash after this but will see after a stress test.
Hold both softkeys and hold the power button
You can also hold both softkeys and put the stylus into the reset hole. Tell me if that works.
Initially no. When I attempted to flash the HTC Factory Rom it froze. Prior to that I did a couple of hard resets using the two softkeys and reset pin. With the resets couldn't get the GSM radio to turn on. Tried the ROM flash but it froze (about 1/10 of the way) - so I basically OS bricked it by removing the battery when it was at this stage. Got to the bootloader screen. Tried to flash OS again with SD card - still froze. SO I thought reflash HardSPL and the OS magically appeared and did the steps above.
After a couple of hours - call made, turned off and restarted device no problems still have GSM radio. Can receive a call when in standby. May try to do another hard reset and see if it still works after a day or so of testing phone but I want to try it for a few days by turning it on and off and making and receiving calls. If I can do another hard reset and everything works I think it was just a bad initial flash through ActiveSync. May get bold and flash another ROM as a test.
Since the phone worked with the TEST OS when I got it I think the only factor is the WM6 flash that I did. More than likely the hardware is OK but only time will tell.
I don't believe you will recover your radio rom now as you interrupted the flash. It generally takes 30 MINUTES to flash a complete rom. You stopped it during the radio rom flash, BIG MISTAKE....
If you can find the SHIPPED STOCK ROM or the original radio rom then you might have a small chance at recovery, we're talking about you winning the lottery 10 times in a row chance...
If you try to flash anything but the original radio rom then you can kiss the phone functionality goodbye....
Good luck finding the right roms...
Cheers...
Its not bricked. In my post said I did a full recovery and its working with the stock HTC WM6 ROM with the HTC radio. I can receive and make calls. Able to ActiveSync with the PC and have hard reset a few times just to make sure all is well. I believe there is still a hardware problem - either a loose connection inside or something else is going on but I think its definately hardware. When the stylus is out of the holder EVERYTHING works fine - have a signal - can sync - can charge it - no issues. If I put the stylus in part way no problem - push it in all the way during a call it will still say connected yet will hear nothing and can't disconnect. Pressing end has no effect yet the phone will still function - just the in call symbol stays and the green led still flashes.
Turn it fully off and back on with stylus out - shows GSM radio code and phone will now work.
Have to check the service manual to see if the stylus holder when the stylus is inserted pushes on anything vital. Can't imagine thats it. But so far with the stylus out everything is ok. Will attempt to use it tomorrow see if thats it.
Know it sounds stupid but thats what I'm observing so far. Its late here see what happens tomorrow
Thing is running and can use the phone (no static, three bars) but last night had a few no GSM messages during a cold boot. Ran it all night and it seems to be working - booted a couple of times, charged it, sync'd it and actually put the stylus in (don't know if thats the problem) and still working. May be a loose connection that is currently ok but who knows when it will stop working. Other possibility is heat or a failing radio. Could also be battery but thats doubtful. Could have messed up the stack during the initial flash so I'll see over the next few days. This one is starting to drive me a little crazy because it works then for no reason it will stop then resume after a hard reset or reset. Could also just be the version of the ROM I'm using but it came from the repository on XDA-Developers. Just rebooted it when I was typing this and it still finds GSM radio.
Tried it for a day and I think the radio is fried. Started out finding GSM then when driving around with my Bluetooth heard a bleep which indicates loss of signal - saw it hunting then it finds the signal. During a call for about 3 minutes just drops call and on the screen the dialer won't let you disconnect the call.
Rebooted got the NO GSM message - eventually found it - briefly then NO GSM again.
Tonight opened it up and reseated and cleaned motherboard contacts including radio. After hard reset got GSM again - briefly. Then no GSM
Tried upgrading and downgrading radio via SD card - no go would only hang up Tried complete with OS - same thing. Tried through ActiveSync method SSPL and got same.
So I think the phone is pretty much not really a phone - can still boot into OS. May try some more but I think its definately a motherboard issue. Shouldn't be that hard to flash and the GSM should at least be stable.
When I bought it on eBay and first turned it on saw a TEST ONLY message on boot with a WM5 Rom. The seller was a little vague just said it freezes sometimes. Got it cheaply thankfully so I'll keep hunting around for another unless someone has a suggestion?
The Radio seems to be the touchiest part of the Hermes. When it fails theres nothing that seems to be able to fix it. Look for another cheap Hermes. At the very least you will have spare parts.
how weird is this I have just gone through just the same problem and took a day to sort it out . ok here is what I did in the end . now what you need is any official rom pref wm5 . I can send you a link if needed to the one I used ... now try flash it from the pc it will stop at 12 percent ....... now take battery out and boot in bootloader mode .... now flash any rom that's wm6 etc .... devise will restart .... now take battery out and re boot it may take two or three boots to get it working prop without the no gsm error but trust me it will boot . when its booted up flash the original wm5 shipped rom run through the rom sequence and when its waiting to flash saying zero percent manualy put your phone in bootloader and wait 30 odd min tadaaaaa phone is now perfect ... now flash any rom you like as the radio is fixed . its something to do with the 12 percent bit it hangs on .??!!! sorry its long and complicated but I have my hermes back to life through doing it ................... let me know how you get on bud. if needed 07832999919 uk . so its 0447832999919 oh I have hard spl 1.40 spl 1.1 or something lol can't remember . anyway good luck
Ok, think I initially really messed up my flash and the WM6 which was the official HTC version may have been corrupted but showed full flash. When I tried again I would also get the 12% even with a SD flash. So I tried flashing just a RADIO ROM which did complete. The NO GSM message still would pop up maybe 50% and not necessarily everytime.
When to MTTY.EXE and did a bad block check - no problems
In MTTY did a FORMAT/CLEAR.
Left everything alone and again reflashed just the RADIO - things seemed to be better - less NO GSM.
Tonight - just before you posted I successfully did a complete reflash with the HTC WM6 rom with Radio 1.48. Very surprised it worked this time - no hangups except during the GSM part which only stopped a minute or two.
Complete reflash in about 10-12 minutes with the SD card method.
SO far things are working - tried a reboot a few times and now radio is found every try. Will try for a few hours and try again tomorrow.
What I did have is a white screen/with image once - it was cleared by just pressing briefly the power button. So it may be heat related - don't know.
Keep me posted in this thread whats going on and I'll do the same.
What ROM WM5 did you flash to get yours to work?
Spoke too soon! Put in a sim card - powered up and it worked. Tried making test call and it worked. Tried again and it showed dialer and dialing and never connected. Could not use the dialer to hang up. Also showed drop in network. Tried turning phone radio off in dialer and back on - showed !X. With the phone off hook image at the top bar. Tried again - same thing. Expected to see no GSM when power cycled and it did show NO GSM.
Right now its working even after a few power cycles but honestly I think the successful flashes may be due to the GSM radio being found. If it doesn't find the radio and you attempt to flash thats why it hangs. If you phone works for a few days or day I'd be very surprised. The real test is to try it when moving from tower location to tower location. Thats where I noticed the radio was acting up. With a bluetooth headset it will beep indicating a drop in carrier. When its doing this the radio isn't working properly and can't lock on to a signal
If your phone does work PLEASE post what you did and what files were flashed.
For my phone I think its heat related. Possibly the heat from the circuitry is opening up or stressing out a component causing it to fail. I really think my motherboard is faulty and reading on the HERMES this isn't that uncommon. Being that the phone has so little hours I think it must have been a return or factory reject.
More than likely I'll have to purchase another phone needing a screen or one thats in poor shape to salvage the motherboard and attempt to put it in my case since the housing and screen are pristine with little to no use. I've been told that any 8525 motherboard will work but I doubt it since the Dpad is different and I have a front video camera.
No, ANY Hermes mainboard will work... Hermes are identical internally, even the 8525 is able to use the front camera, it just isn't included in that model.
Cheers...
Thanks, makes my life easier!
ok mate i used htc orig rom by orange uk google the words,,,, orange spv m3100 update ummm ok hang on il grab the link for you ...
http://www.orange.co.uk/business/downloads/SPV_M3100_ROMUpdate_1007.exe then flash hard spl then update your rom to whatever you like ,,, hope this helps buddy
Might try it tonight but I really think I need a new mainboard. I am able to flash only when it finds the GSM and I think any hangups are due to the GSM radio circuity failing or some strange power flux on the motherboard. I am having strange multiple freezes/slowdowns as well as NO GSM errors. Tried a WM5 and WM6 specific for my HERM200 and no change. When it works it will work and make and receive calls but after a while without a load but under load - multiple calls, running excel or other things the radio will drop or it will attempt a call, not connect and will not let me hang up. No software update will fix this issue - it has to be hardware.
If I have successfully done base HTC ROM flashes - complete with radio phone should theoretically work. I have to face reality with this one which although looks pristine is a lemon and have to buy a working beat up 8525 and try the motherboard as long as the seller assures that the phone can make and receive calls without problems.
Also have other issues with screen fadeout which I know is tied to the dPad controller - but I can live with that for a while and I have a source for a part replacement and can try a quick fix to verify its just the dPad.
You got lucky so far - but if you try to use the phone all day running multiple programs or CPU intensive tasks your radio still may fail. You could also try upgrading the ROM again to something that is MFG and see if it takes.
It is possible to flash the OS without flashing the radio, It will be a cooked rom but they're better in most respects than a stock rom. Faster, leaner with all the bloatware removed.
No software change is going to fix this. Its not a software bug its a flaw in the hardware. Can't flash a radio Rom - thats a chip problem. Its basically a low level format and write to eprom. Thats pretty basic. Also making and receiving calls is also pretty basic. The dialer has been around for a while and is pretty stable.
Yesterday my battery died half way through playing a game (not entirely unexpected, I'd been playing on my phone quite a bit that day and it still lasted 22-23 hours), I connected the charger that came with the phone and left it to charge while I got on with some uni work.
The phone vibrated to tell me the charge was complete so I disconnected the charger and turned the phone on as usual. After the samsung galaxy S2 splash screen, the screen lock appears and when I move it there are several error messages saying that various applications have had to stop (the main one seems to be TwLauncher but when I force close it, many others also force close). This continues for several seconds until the phone decides to restart itself and repeats the process ad infinitum until I can shut down the phone (I can manage this by not trying to get rid of the screen lock and just holding the power button until the menu appears).
I've had this phone a week (one of those days being today where it did not work at all) so it's still well within the return period but I was wondering if there is an obvious fix that I'm missing.
If not, I'll be ringing Samsung on Monday (I have coursework due for friday so I'll be devoting my samsung office hours time to that) and if they can't give me an easy fix I'll be ringing the place I bought it from and asking for an exchange.
So, has anyone else had similar issues and managed a simple fix?
Bump, I take it everyone else's phone is working then?
Giving this another bump in the hopes there's someone with a simple solution.
I don't want to have send my phone off and wait for the place to get stock.
there have been 2 firmware releases from samsung in the last couple of days, i assume you are running the latest firmware?
I can't even get the phone to stay on long enough for Kies to recognise it. It keeps restarting. Even when it was working I couldn't get Kies to work with it properly (I couldn't copy the contacts from the phone to the computer).
It's running the firmware it came with, but I can't check which version it is.
I was going to try flashing the new firmware via ODIN but I've been busy with coursework. Is this likely to solve the issue or will I just be giving the retailers ammo to reject my return?
go into recovery and do a factory reset
psp888 said:
go into recovery and do a factory reset
Click to expand...
Click to collapse
this is what I was looking for.
after googling, this sorted it out.
I just assumed download mode was the only other non-normal mode.
Thanks
Basic FAQs on the SGS1 forum mostly apply to SGS2 .Worth a look there before Google .
jje
All those with the SXS on AT&T, have you guys upgraded to ICS via PCC? I got the message last week that the update was available, but I'm curious to know if all-mighty AT&T is going to somehow recognize our devices because of ICS?
Any issues that you have encountered?
I've read some of the positives, so I just want to make sure that it's going to work properly.
Thanks!
Haven't had any issues. Tethering still working as well for me without a message from AT&T.
Thanks, I just wanted to make sure that I'm not going to run into any issues when I upgrade...just a bit paranoid is all since this is my first Android phone
Just finished the upgrade to ICS (Build number 6.1.A.0.452).
When it asked to plug in the phone while holding down the down volume key, it didn't do anything. I unplugged it and tried again and then it started the upgrade process. It probably took about 10-15 minutes to complete and another 2-5 minutes for the initial boot up of the phone.
I noticed that everything was kept in tact (contacts, call logs, wireless ap, downloaded apps, etc) so that was a good thing.
So far, everything is working as it should.
I logged in to AT&T's OLAM and it is showing as an unknown device...for the moment. I'll check again later.
Hi;
I apologies in advance for the long thread, but I want other users to notice the symptoms I faced maybe someone else will benefit from it.important parts are marked in blue
MY galaxy s3 is only 4 months old....I got tempted by rooting and getting all -other- features such as fast recharging, sound hack, trying new roms before they are officially released...etc
anyhow, my phone's troubles showed strange symptoms quite shortly after the second rom being installed....
at first I was not fully aware of the required rooting steps, until I use the galaxy toolbox that rooted my phone easily for me...
then I started noticing the phone would start and everything but noticed (root user notices) take time to show up after boot, it would take approx. 1min then they will show very fast...after that everything is normal so i figured the processor is a little bit loaded...
few weeks later I started using CWM's backup &restore feature , noticed that when I go back to the official Rom, it lags, a lot! , I have to restart the phone at some points because it will stop responding...I started checking processor load and was surprised to see normal non harmful rates...so I forced apps to be closed once I exit them.
few roms and flashings later, the phone started restarting it self randomly,like an old car heating up, it would restart few times then get back to normal state....this would happen whenever i try to change anything in the rom (CM10+nightlies build)
few days ago, whenever the phone received or made a notification sound, I would pick it up and find it turned off! I turned on again and use it normally , no issues....after this happening for 2 times, the phone just died ...PIT partition is non-readable/writable anymore :crying:
I noticed the night this thing happened that, when I restored the rom, it took a longer time, and something was not found but the rom booted normally....
now my phone is in service and they are overloaded with service-warranty requests, so they haven't checked it yet (it has been there for 3-4 days)..I used traingle away on the current rom, no flash counter appears and the binary is official, but the rom appears as custom
notes:
*from the beginning, every step I made was a trial and error to me, I tried rooting once (manually) and I didn't figure it out,until i saw the toolbox that made it easy,,,the first root was amazing, but I rooted again after rom crashed and seems I used a different root that started all that trouble.
*All the mentioned above I believe were symptoms, that I didn't care about since the phone was acting normally after those occurring..I think I should've spotted them earlier.
*There have been 2 overheating incidents, one happened when I forgot the phone in my pants and by mistake i ticked "load new videos from subscriptions in youtube and the phone sucked up around 3gbs that day...it was really really hot when I got back to it.....the other one was when I went to sleep few days ago, I put it under my pillow, woke up with the phone overheated and restarting continuously "might've been doing this all overnight!"
*I insisted -although it was clearly troublesome to my phone- on installing Siyah kernal on every rom "always the latest one", sometimes the phone would keep restarting and I would have to restore a previous rom, sometimes it would go without issues, this happened more oftentimes during the last few weeks and CM10 nightlies offers dialy updates and I had to flash siyah back after every update...now I'm writing it and feeling stupid!
*Official JB roms caused the phone to hang a lot, so I kept using CM10+siyah kernel till the last moment.
now, what I would like to know is:
1- why does that chip get affected?? I never flashed a 3/4 part rom, just using CWM....
2- I decided (if) the phone gets fixed on warranty, to not to root again, I'm having a million guesses as the reason why this happened, including the fast recharging, the continuous flashings and testing (although all are stable roms, only official and CM10 roms), the overheating incidents....etc....I would like to know what you guys think.
If you had read the faqs and guides first you would not have the trouble .
Like
at first I was not fully aware of the required rooting steps
from the beginning, every step I made was a trial and error to me
I tried rooting once (manually) and I didn't figure it out,
>> basic CF Root is simple as it gets .
jje
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
BladedYouth said:
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
Click to expand...
Click to collapse
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Tonyco1 said:
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Click to expand...
Click to collapse
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
BladedYouth said:
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
Click to expand...
Click to collapse
Yes just browse this forum but only section about Windows Phone 7 Development and Hacking. You will find DFT exclamation of how to install HSPL. In mine it was very easy because I not receive Country ID fail my phone was buy in Europe. If you receive Country ID error you need to proceed with goldcard it is explained there but first proceed without goldcard if it work it is very easy. Also when you proceed SPL2.05 it is not clear in the topic but you need to be in bootloader so you should start your phone with VolUp and VolDn keys pushed this is not explained in the topic and I waist a lot of time till figured out. After that just download one of the 7.8 ROMs here in Radar section and write it down. Also download new radio and use some RUU to put it on the phone before the ROM other wise the phone can not boot. Try and after that if you have problems write down here.
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
BladedYouth said:
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
Click to expand...
Click to collapse
OK but you need to but some custom ROM my phone turn back on when I put custom ROM a lot of features and works really good.