does any had try to restore a corrupted radio in the beetle device or how to made it u had the hp hw6515b and it had corrupted radio any suggestion?
Tried to but was unsuccessful, check the following page
http://blogs.unbolt.net/index.php/brinley/2007/07/31/ipaq_6515_dead_gsm_after_failed_firmware
Somepeople have suggested erasing the sectors housing the radio rom then reflashing the radio from from the above link. However noone has dared to try it.
Related
i have tried the SSPL and it works, i can flash the 3 roms i have found for the breeze
RUU_BREE100_1.13.251.2_1.06.00.10_QtekEUR_Ship_R3
RUU_BREE100_1.32.251.1_1.29.00.10_HTC
RUU_BREE100_1.34.251.1_1.38.00.10_HTCEUR_SHIP
but since i flashed the 1.38 radio rom without using this sspl. whenever i use the sspl i can only flash the rom not the radio. my phone is now stuck on the 1.38 radio which drops calls after about 30 mins and the battery life is really crap, i am on area where u get full 2g or 1 bar of 3g so its doing its trademark searching and killing the battery.
I have tried duttys tool with the radio extracted and put on the SD card and flashed but no joy.
my device is not SuperCID i just use the SSPL to bypass it.
anyone got any ideas how i can flash the 1.29 radio or for that fact any radio to phone instead of the rom?
i've read that many have tried 1.20 radio to solve a few problems but i have no idea how i can flash this. I have tried to make my own rom with the tools here but again they just flash the new OS living the radio 1.38.00.10. i am downloading RUU_Radinly_1.20.31.10.exe and will flash it if i knew how. SSPL just turns around and says invalid ID error 244. so its like the radio isn't designed for this device.
anyone got any idea ?
1.29 is even worse than 1.38... Missed calls in full GSM coverage (4 bars), horrible sound quality (either you or called party can't hear most of the conversation)... Don't even try it!
And concerning the problem not being able to flash new radio:
As I already wrote in this thread, flashing Radio ROM 1.29 (and above) also flashes new Radio Bootloader 0108 (different thing than Phone bootloader) which requires SPL 1.09 (or newer) to flash Radio ROMs.
Current SSPL for Breeze is based on some older SPL which, as you found out, isn't compatible. Until someone creates SSPL for Breeze based on SPL 1.09 or SPL 1.10, you're stuck just like me...
thanks very much for the post explaining it. i have read someone might make a new sspl with the new spl's in mind so as you said, we have to wait and i guess i will. i am however going to send my breeze back to HTC because of the constant dropping of calls whether it is 10seconds or 35 mins, it drops it without fail.
Hello.
First, sorry for my bad English (French guy).
I make a SD flash with a Rom, and something strange occurs: my radio rom version change to 1.16.00.00. I try (always SD flash) to change it with a newer, the process looks good (the download bar increase, the device reboot) but the radio rom version always the same. I try to change OS rom, no problem. I try to change SPL version, impossible: all process executed without error but at the next load of SPL (power-camera-reset) the version is always the same (1.30 Olipro).
I try with another computer (Win XP pro SP2) and with activSync, the problem was the same !
And I try with several rom version, idem.
So to be quick
OS ROM change: no problem
SPL change: impossible
Radio ROM change: impossible
If someone have an idea, I will be very happy
Bye
I find the solution !
Usually, I toogle in SPL mode manually.
The soluce for me was to downgrade the SPL (1.30 to 1.20 olipro) but let the RUU launch is own SPL.
And after, the SPL version was 1.20 and I can change ROM, Radio ROM etc...
[Mode happy ON]
Bye
Hi, can you post the procedure please? I have the same problem!!!
But your pda statup?
Thx
Roby
i don't understand how that is accomplished.
i have read through the trinity guide and that is what they recommended
My trinity has been flashed with 1.3oli and a custom rom but it hangs at the start up page.This makes the device disconnect from the USB.
so how do i let the RUU launch its own SPL?
It is supposed to make the device go into bootloader right? i cant access that since it is hanged
Advice please
Hi bigrockshow,
it is impossible, in this condition that rru launch its SSPL, and it is ipossible to use the method sspl.exe ....
I think that the only way is the splxploit but I don't find a sspl file to load on p3600 with splxploit
anyone have it?
I've exactly the same problem, oli 1.30, I can flash OS roms with no problem but I can't get a radio rom to go past 0%.
I've tried the spl exploit to boot into spl 1.07, I've tried going into the bootloader manually and I've tried letting the RUU load the SPL, no matter what I do I can't shift the radio from 1.16?
Any ideas?
mine is just wierd...
i used SPLxploit and the spl jumps to 3.03...
tried to flash hard SPL and its has error 270...
so i did SPLxploit again...
shows SPL 1.20 now
Tried to flash another rom and it still doesnt work..
did i miss something or is my dopod screwed...
You can't upgrade to the 1.56.70.11 Radio with Olipro 1.3. It looks like it's worked and gets to 100% on mine but doesn't actually change anything. I ended up using another HardSPL (can't remember the name now) to get the 1.56.70.11 Radio on there.
I looked for ages for a version of Olipro 1.2 but couldn't find one anywhere. Apparently it works ok with that version.
Sometimes these threads are really hard to follow when they get massive and the author updates the first posts and over writes stuff. I think they should all keep old stuff in there and just add too it instead of replacing information.
Hi all,
something goes wrong after flashed 1.56.70.11 on my phone, after logged into wm, there is no signal at all!!
I tried to downgrade to offical at&t firmware (GSM and ROM) but not work.
also tried to unlock radio by using cheetahunlocker, but athena unlocker always hangs at the last step.
anyone encountered similiar issue or know how to fix it?
ps. I have hard spl installed.
thank you!
==================Update 5/8 ==============
it looks like I flashed a corrupted radio firmware.... sigh...
even if I re-flash a correct radio firmware, it won't get back to work.
I am now going to send my treo back to repair
I encountered the similiar issue, I tried serveral ways to downgrade the radio including using mtty, but all did not work.
It's very neccessary to find a way to downgrade the radio to lower edition.
I am using Cyanogen 4.0.1.
I recently flashed the new radio and then flashed the HardSPL and ever since then I have not been able to scan for Wifi networks. That appears to be the only problem I am experiencing at the moment.
Any one else have similar issues, or know of how to fix this.
Thanks in advance.
The SPL doesn't have anything to do with wifi. What does the baseband say in about phone. wifi, 3g etc. are powered by the radio, try to reflash that. Also link to the new radio you flashed. Doesn't hurt to check the md5 of your download.
I would definitely start with reflashing the radio image from Haykuro's site. If you are going to continue to use Cyanogen's amazing ROM, I would NOT flash Haykuro's SPL. Stay with the HardSPL to reduce chance of bricking on accident.
evilkorn said:
The SPL doesn't have anything to do with wifi. What does the baseband say in about phone. wifi, 3g etc. are powered by the radio, try to reflash that. Also link to the new radio you flashed. Doesn't hurt to check the md5 of your download.
Click to expand...
Click to collapse
I flashed the radio from Haykuro's site, I re-flashed and I still do not get any wifi.
The wifi function will turn on fine but then when I try to scan for my network and it will display a message saying "unable to scan for wifi networks" and then the wifi function will turn itself off.
btw, I am now running CM 4.0.2
I'm running Cyanogen 4.0.1 with Haykuro's radio+HardSPL and wifi works find and everything else. wipe and reflash.
something similar happened to me on my tmobile dash.
i flashed the spl wrong or idk and then my wi-fi broke
People have had similar experiences with wifi on the xROM. Many people weren't able to get wifi up and running with HardSPL, but then upgraded to Haykuro's SPL and it started working fine.
I don't think this is mere coincidence... even though neither dev requires the newest SPL, it seems that wifi doesn't work without it.
For what it's worth, update your radio (I'm sure you're on the latest radio, but for posterity's sake, just do it again), then update to the new SPL, then reflash your ROM.
Report back... I'm guessing you'll be a happy camper.
I've never had a problem but i upgraded to hardspl before cyans newest roms. maybe something in their updates kills the functionality
you should have put the newest radio before you flashed a cupcake rom
Any updates antirock? If it's still not working after a wipe and reflash, I would recommend reflashing the newest radio and flashing Haykuro's SPL. Check my sig for more info.
uansari1 said:
Any updates antirock? If it's still not working after a wipe and reflash, I would recommend reflashing the newest radio and flashing Haykuro's SPL. Check my sig for more info.
Click to expand...
Click to collapse
Ok, here is what I did.
wiped and reflashed radio and it still didn't work.
So I reverted back to Cyanogen 4.0, reflashed radio, reflashed spl, wiped, reflashed CM 4.0.2...and now wifi is working.
However, the vibrate funciton on my soft keyboard doesn't work. I figure that it is the rom, but no one else seems to be having this problem in the CM 4.0.2 thread.
Thanks for all of your help!!
antirock said:
Ok, here is what I did.
wiped and reflashed radio and it still didn't work.
So I reverted back to Cyanogen 4.0, reflashed radio, reflashed spl, wiped, reflashed CM 4.0.2...and now wifi is working.
However, the vibrate funciton on my soft keyboard doesn't work. I figure that it is the rom, but no one else seems to be having this problem in the CM 4.0.2 thread.
Thanks for all of your help!!
Click to expand...
Click to collapse
So you're still on HardSPL? If others aren't having this problem, then try Haykuro's SPL if you meet the requirements.
I had two G1s for a while... one of them flashed to JACxROM fine, but on the other, wifi wouldn't work. They both had the same radio and HardSPL. Flashing Haykuro's SPL to that phone and suddenly everything worked fine.
I don't know why these phones are like that... maybe its some small difference with the actual hardware inside the phone, or the downloaded file you're trying to flash, or maybe whether or not you flash when there's a full moon. Your guess is as good as mine. Point is that MAYBE the newer SPL will work for you.
It's funny how wiping, uninstalling and reinstalling usually fixes everything.
hey.
Im almost sure i just bricked my g1, just need to be sure.
I was running Death SPL and the last official radio, and had gsm\umts network connection problems.
Decided to upgrade the radio to the last one that came out recently, i did, the problem seem to be better but it got worse in time.
downgraded the radio, and tried around 15 different roms, all tries with the same outcome.
so after a lot of trial and error, i decided to get back to one the the first radios available, but i was afraid it would brick my phone so i read carefully about it
I had a realy hard time finding something but i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
after reading that i downloaded a 1xxx radio and flashed via recovery...
result: stuck in the G1 screen...
My question: phone in the crapper right?
thanks for reading guys
mordockcs said:
i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
Click to expand...
Click to collapse
No, what they said is that it is OK to flash anything as long as you use FASTBOOT INSTEAD OF RECOVERY, and that FULL FASTBOOT (with this ability) depended on having a 1.33.2xxx SPL.
With an SPL and RADIO that are incompatible with each other, it is impossible to successfully boot the kernel. Following a flash-hboot or flash-radio, the system is set (via writing the command field in the MISC partition) to boot-recovery. When in boot-recovery, the phone IGNORES all user inputs. The incompatible radio/spl fails to boot-recovery, and you're bricked.
USING FASTBOOT INSTEAD prevents the misc partition from being set to boot-recovery by writing the SPL or RADIO directly. As a result, when you reboot, though it still won't be able to boot a kernel, IT WILL RESPOND TO USER INPUTS and bring you into FASTBOOT mode... from where it is possible to, again, flash radio or spl.
Your failure is a result of failure to read properly.
SPL/radio compatibility:
0.95.xxxx, 1.33.x003: compatible with 1.x or 2.x radios.
1.33.xxxx (except 1.33.x003): compatible with 2.x or 3.x radios.
No exceptions.
I always suggest using the 1.33.2003 SPL since DREAM should always use either a 1.x or 2.x radio (except robbers in canada, because they are bastards, but you can load those with a 2.x radio just fine). 1.33.2003 is the strongest engineering SPL available, and fully compatible with the proper radios. There is NO ADVANTAGE to any other SPL -- no, you don't need to change your SPL to reallocate storage space.... in fact, limiting yourself to SPL changes to do this will tend to waste a lot more space (15 MB more available than 1.33.2005 gives you).
lbcoder said:
Your failure is a result of failure to read properly.
Click to expand...
Click to collapse
no its not...im pretty sure about what i read...if i stumble on the thread again ill PM you to prove it.
i already have a touch HD on the way so no harm done, i wish this was all the harm in our world...
but anyway now that its dead...lets fix it!
is there a way around it? i hear about jtaging a lot but i have never seen a tutorial on the web...
any insight on that would be delightful...seriously
but hey lbcoder thanks for enlightening me i appreciate it, i really do...thanks man