Hi XDA Developers
I am new to this and to a Dell Streak 5 recently purchased through EBay. I am interested in solving two issues on my new phablet.
It works well when it is turned on and kept running. When it has been off for a time, say an hour or two it then won't switch on, the home, menu and back buttons light and it hangs. To restart I have to remove and replace the battery and press start again. The supplier has suggested a factory reset which hasn't cured the problem, and a reload of the OS. They have pointed me towards your site for a copy of the OS but the packages you have listed aren't shown for my build number. Is it possible to use one that you do have for build 15380?
Is this likely to cure my problem?
My second question is can I upgrade to Gingerbread?
Thank you for any help you can offer.
To answer your question about upgrades, yes you can upgrade to Gingerbread. Click on the links in my signature to be taken to the two latest custom Gingerbread ROMs. Flash one of them and call it a day. The stock ROM is buggy compared to the custom ROMs. The custom ROMs do have their quirks but in general are a better option as they have had fixes applied that are not found in the stock ROM.
To answer your other question, it's possible to use any ROM package on your device, with a caveat. The caveat is that Dell divided the world into regions. Dell stock ROMs come in three parts: baseband, recovery, and the system image. These three parts must all have the same region number or else the flash will fail. The good news is that I provide a tool that will install the appropriate baseband and recovery files, if you wish to use a particular stock ROM. That same tool will also allow for installing a custom recovery, which is needed to install a custom ROM. Just make sure to immediately boot into the recovery (hold down both volume keys and press power), otherwise the recovery you just flashed will be lost.
Thank you
Strephon Alkhalikoi said:
To answer your question about upgrades, yes you can upgrade to Gingerbread. Click on the links in my signature to be taken to the two latest custom Gingerbread ROMs. Flash one of them and call it a day. The stock ROM is buggy compared to the custom ROMs. The custom ROMs do have their quirks but in general are a better option as they have had fixes applied that are not found in the stock ROM.
To answer your other question, it's possible to use any ROM package on your device, with a caveat. The caveat is that Dell divided the world into regions. Dell stock ROMs come in three parts: baseband, recovery, and the system image. These three parts must all have the same region number or else the flash will fail. The good news is that I provide a tool that will install the appropriate baseband and recovery files, if you wish to use a particular stock ROM. That same tool will also allow for installing a custom recovery, which is needed to install a custom ROM. Just make sure to immediately boot into the recovery (hold down both volume keys and press power), otherwise the recovery you just flashed will be lost.
Click to expand...
Click to collapse
Many thanks Strephon for your advice. Is this likely to cure my "fault" do you think?
You'll have to try it and find out. I do know that on rare occasions, Traveller DSC, the custom ROM built from stock, may fail to wake from sleep mode, meaning you have to power off the device completely and then turn it on again. PsudoCream has an issue where it may spontaneously reboot. I've not been able to pin down the cause, though I do suspect it has to do with low memory.
Strephon Alkhalikoi said:
You'll have to try it and find out. I do know that on rare occasions, Traveller DSC, the custom ROM built from stock, may fail to wake from sleep mode, meaning you have to power off the device completely and then turn it on again. PsudoCream has an issue where it may spontaneously reboot. I've not been able to pin down the cause, though I do suspect it has to do with low memory.
Click to expand...
Click to collapse
Thank you again Strephon for your quick response. I know that I now need to study all the info about flashing very carefully to avoid bricking my new streak 5. Incidentally I bought it to use with XCSoar navigation for glider pilots as it is highly recommended by their developers. Having got it I am keen to maximise its capability!
Related
I installed "Eugene_2E_JK2_Froyo.tar.md5" on two of our Vibrants using odin. I have four strange anamolies that happened to both Vibrants as a result of this...
1) There is NO lock screen anymore.
2) The touch "home" and "search" keys are non-responsive.
3) Videos cannot be played.
4) The most disturbing is we cannot receive calls...but we can make them.
I currently have 2.2 froyo.uvjk2 installed on both vibrants.
As a result of these weird accurances, I tried installing several roms...such as Axura 204 and Onyx R42 Stock. I keep getting a signature error when the Vibrant boots in recovery mode. Do roms not work on 2.2?
I am using the current "One Click Lag Fix" and "Rom Manager".
What should I do to fix these Vibrants and why are the roms not working?
Any help would be greatly appreciated.
ams77 said:
I installed "Eugene_2E_JK2_Froyo.tar.md5" on two of our Vibrants using odin. I have four strange anamolies that happened to both Vibrants as a result of this...
1) There is NO lock screen anymore.
2) The touch "home" and "search" keys are non-responsive.
3) Videos cannot be played.
4) The most disturbing is we cannot receive calls...but we can make them.
I currently have 2.2 froyo.uvjk2 installed on both vibrants.
As a result of these weird accurances, I tried installing several roms...such as Axura 204 and Onyx R42 Stock. I keep getting a signature error when the Vibrant boots in recovery mode. Do roms not work on 2.2?
I am using the current "One Click Lag Fix" and "Rom Manager".
What should I do to fix these Vibrants and why are the roms not working?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
make sure and disable the lag fix, and try the reboot to recovery option in rom manager. (so that your in clockwork recovery and not samsungs)
then try flashing the new rom from there.
also you probably know this, but just to be sure: make sure your flashing rom zips and not odin style roms.
otherwise odin should work especially if you've done it before, but be sure to flash a 2.1 kernel if your going to a 2.1 rom
theres some guides for that, if you decide to go that direction I can give you a link.
firefly6240 said:
make sure and disable the lag fix, and try the reboot to recovery option in rom manager. (so that your in clockwork recovery and not samsungs)
then try flashing the new rom from there.
also you probably know this, but just to be sure: make sure your flashing rom zips and not odin style roms.
otherwise odin should work especially if you've done it before, but be sure to flash a 2.1 kernel if your going to a 2.1 rom
theres some guides for that, if you decide to go that direction I can give you a link.
Click to expand...
Click to collapse
Can you tell me what this means...how do I disable the lag fix? I am extremely new to android (one week), so can you tell me more about how to flash a kernel and what that means? Is Axura 204 and Onyx R42 Stock 2.1 roms? Do I have to downgrade back to 2.1 in order to run those roms? If so, I'll take you up on that offer for the link for directions.
Thanks for all the help...
ams77 said:
Can you tell me what this means...how do I disable the lag fix? I am extremely new to android (one week), so can you tell me more about how to flash a kernel and what that means? Is Axura 204 and Onyx R42 Stock 2.1 roms? Do I have to downgrade back to 2.1 in order to run those roms? If so, I'll take you up on that offer for the link for directions.
Thanks for all the help...
Click to expand...
Click to collapse
try looking here: http://forum.xda-developers.com/showthread.php?t=849028
that should have most of your questions answered, anything you need more specifics on just pm me again and I'll explain further.
wow. dude. this is weird.
this same problem happened on my gf's nexus one out of the blue last month. there was no way to fix it (searched the entire internets!) other than doing a factory reset.
so i did that and it worked for 2 weeks. then bam, same ****ing problem again.
reset again, it did it again that same week.
called HTC and got a new SLCD nexus one mailed out to us free of charge.
EXACT same problems though, those two buttons haptic feedback but do nothing, no lock screen, and phone calls go straight to voicemail.
Hello all, this is my first post (feel free to yell N00000b LOL) so I'll try to be right to the point since I just need advice on a couple of things to keep on going on my learning process (with the tutorial threads and guides).
I got my P500 off of the local eBay (I'm on Venezuela), it was a great deal for a unit with a couple of months of use (had original invoice) and the phone is really "like-new". The thing is that the guy who sold it to me is himself a modder (probably he's around here somewhere) so the phone is already rooted and it's running a custom ROM (and it's supposedly overclocked). As far as I can tell (by comparing the description and installed apps) the ROM that's installed is the one on this thread:
Light 2.2.2 ROM: http://forum.xda-developers.com/showthread.php?t=1018839
My about screen reports the following:
Model number: LG-P500
Android version: 2.2.2
Kernel version: 2.6.32.9 [email protected] #36 The Feb 10 23:04:17 2011
Build number: FRG83
Software version: V10h-FEB-23-2011
One thing that I should mention is that he deleted all data and apps that he had installed after flashing the custom ROM (or probably he just reflashed the custom ROM prior to giving me the phone), so there's no app for controlling CPU clock, Terminal, BusyBox, etc (I know I'll have to install those from the Market).
My specific questions are this:
1.- Should I have any special considerations on my learning process (with the tutorials and guides) since I'm not starting with a stock phone as most other users?. I want to get to the point of installing/testing other ROMS (it seems that the one on the phone is not one of the most populars around here)
2.- I've read some horror stories around most forums regarding the infamous "radio.img" file and how you can damage your phone data connection if you mess around with that file, but on the guides around here I don't see much mentions of that file. How can I prevent messing around with it?. Is that file part of the custom ROMs or what?. I should mention that my cell operator here in Venezuela is "Digitel", and they operate on the 900 Mhz band for GSM and 3G UMTS/HSDPA service (the other 2 operators here use 850 Mhz for 3G).
Thanks in advance for your advice
U don't need to be horrified with that radio image coz in our phone Ive never seen any update for that so basically u never need to mess with it.. go ahead and flash a gb rom maybe void.. with Franco's kernel.. and follow the steps provided in the respective threads..
Sent from my LG-P500 using XDA App
I wouldn't be concerned about the lack of default apps. You can get them pretty much everywhere here on the forums. Also, Light is not exactly the greatest rom available for the Optimus. I would highly recommend flashing Mik's CM7, but if you'd rather stick with something closer to stock then use Megatron.
Megatron was my first ROM, I ran it for several months. Then I switched to Void for a while, and then when Void was discontinued I waited til Miks CM7 was out of Alpha status and flashed it. Haven't gone back since.
Thanks for your replies... I was under the impression that the "radio.img" file had something to do with the specific radio frequencies that your operator uses for 3G, so if let's say your operator is 3G-900 Mhz and you flash a "radio.img" for an operator that's 3G-850 Mhz, then your phone will not connect to 3G anymore. My doubt is that I don't know if that infamous file can be accidentally flashed when you're installing new ROMS, or if that file is a different story and flashing ROMs does not mess with that file.
I just don't want to be stupid and start flashing ROMs without the proper precautions to avoid bricking my phone.
Hi guys... I got a response from a guy on another forum who told me that the precaution that I need to take is to always check the content of the .zip file of the ROM that I want to flash (looking inside without unzipping) and just confirm that there is no "radio.img" inside the zip. If the file is not there then I'm good to go. Is that right??
Now I need to move on into installing a Custom Recovery (he sold me the phone already rooted but with no custom recovery installed). AmonRA or ClockWorkMod??
Since you say the phone already runs a custom rom then that means you *may* have custom recovery if the guy hasn't removed it. As for the radio.img, no roms for the p500 mess with it.
Sent from my LG-P500 using XDA App
clockworkmod ...you can use rom manager (download from market) to install it......and try void# forever
You're definitely right on that mihir287... now that I'm understanding things a bit more it makes sense that the phone should have a Custom Recovery already installed since it's running a custom ROM. How can I test/check this??... just by using the key-combo to boot into recovery mode and see what happens?
In the case that he had removed the custom recovery what would happen if I attempt to boot into recovery mode?
If I want to go ahead and install ROM Manager to install ClockWorkMod... will that just replace any previous custom recovery (if it existed) and give me the new one?
(Sorry if I'm asking too many stupid questions )
There are no stupid questions as this is a unique case
Yes just turn off the phone and press home+vol down+power. Remember to keep this pressed till the phone boots onto recovery, or if there is no recovery the phone will boot normally.
If the guy has removed the recovery (i.e replaced it with stock recovery) then this combo will do a 'hard reset', which I think removes all apps so make sure to take a backup using titanium first.
And yes if you use rom manager and flash the recovery then it will replace any recovery you have. So I would say just use rom manager and flash recovery because if you already have recovery or not this method will flash you CWM recovery. Make sure to reboot once before using rom manager.
Sent from my LG-P500 using XDA App
After updating my O1 to Gingerbread two friends complained about receiving just half of the message right and the rest of it with squares/boxes, (at) or Chinese characters, this just happens after x characters, since they get short messages without problems. I think this just happened to them, I'm not sure. Others receive the whole message without any problem. I'm not sure if the problem is the Stock ROM, their cellphones or if I configured my cellphone wrong. Any ideas about what's wrong?
Ps: I'm so sorry about my English, it isn't so good.
hi Phoenix232,
there are seldom any problems like this in a newly updated firmware.
still try master reset.
If that doesn't helps i would recommend updating again.
Good luck.
I'm so sorry to ask this but what are the button combinations I need to press to do the master reset?(It's the same as hard reset I think?) I've been searching but I can't find the right buttons for the P500.
EDIT: Actually, I think I found out how to do it, it's HOME+Vol. Down+Power, but if I do this I get in Recovery Mode.
EDIT 2: Yep, it looks like I need to do this without any recovery installed. I'll try it later. Thanks.
Hello Phoenix232,
I have an O1 myself and I think that I can help you. Please answer my following questions:
1) Did you update to Stock firmware or are you using an CFW?
2) Wich version did you happen to have installed before gingerbread?
3) Which version came pre-installed in your device?
I guess that since you can boot to Recovery mode you are using a CFW, am I right? But if you remove the Recovery, did the Master Reset help?
BR
1) Stock
2)Stock Froyo ROM with Franco Kernel
3) Stock Froyo ROM
I just rooted it, installed recovery and installed franco's kernel. I removed the recovery, did the reset, but it's happening the same thing.
Im currently facing a similar issue, people telling me they simply didnt get my SMS.
Having this issue after installing a new rom.
With me they get half of the message and the other half is just squares or chinese characters.
Dear Phoenix232,
I think that that the best procedure for you is to first go back to original O1 Froyo ROM without mods or root, master reset, them perform the upgrade to official O1 GB and master reset again if you want to use a stock ROM with no mods. Please be warned that this procedure can kill your handset, and since you already rooted and changed kernels you probably voided your warranty so be extra careful with all that.
I haven't already upgraded my O1 since it is my primary work handset, can't risk loosing all my info, but I've done a very similar procedure with a Motorola Milestone and it was all OK (2.1 stock, 2.2 shadowmod, them back to stock 2.1 and finally stock 2.2). You just can't root and change kernels then try to upgrade directly to GB stock without first going 100% back to Froyo stock. (no root, stock kernel etc...). Manufacturers tend to taylor their Android OS upgrades based in the previous version so everything must be exactly the same as it was when you first purchased it for the upgrade to work correctly in the end.
Good Luck!
That makes sense. I'll try it right now and post the result asap. Thanks.
I got back to Fryo and the SMSs are working fine. I'm upgrading to gingerbread now.
Question: Can I root it after doing everything you wrote? Or it'll bug again?
Hi,
Issue: After system loads (I get to see launcher/sim unlock screen), couple of seconds later streak reboots. At the same time, leds swich off, than flash and reboot starts.
What I tried (almost all combinations of below points):
restore to factory settings
different roms: DSC v2.3, PCM7-Streak, Mokee OS, Longhorn 2.9.3, some ICS rom
custom recovery images: ClockworkMod 6.0.1.2, StreakMod 0.3.2.8
stock roms with corresponding recovery 366, 360, 369, 406, 407
user QDL tool from streakflash.zip/repairtool.zip do recover to Baseband GAUSB1A130500
booting without sim/SD cards
Things to note:
For flashing I have followed the procedure to wipe data, cache, dalvik, fix permissions, dell factory reset.
In the past I had not issues flashing DSC, PCM7-Streak and other roms.
When booting into service mode? (camera+power button, *#301# code) phone passed all tests (including Internal SD card).
Tests performed with two original dell batteries (one bought 8 months ago, barely used).
Batteries fully charged.
Same issue experienced with custom and stock roms.
The issue started after flashing one of the roms (DSC v2.0 probably).
To be honest I run out of ideas. Please tell me if I missed something?
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Strephon Alkhalikoi said:
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Click to expand...
Click to collapse
Thanks for advise.
I have tried starting with with 305 from repairtool.zip working my way up through 360, softbank and Olleh. Stopping at each step and flashing ClockworkMod + DSC. Same applies to any updates to each of mentioned custom roms.
The only thing that I know I could have checked better is the internal SD, just a moment ago found a neat way to get to the Internal SD - http://youtu.be/6w4AbtIGp8A. I might give it a try.
Hello , everyone... i recently purchased a Dell Streak 5 and like the phone ..but do not know how to update its Android software.my goal is to get a more up to date android firmare onto the device.i have initially tried the volume up/down /power on ..to acess the ..factory reset..the update from sd card ..and the screen calibration ..menu. and have pressed (camera button ) to highlight from SD card ..but it then goes to a page which outlines android recovery software..and has my baseband number next to it .
1. does that mean a recovery image for the dell streak 5 must be actually on the sdcard at that time eg. recovery.img or must it be installed /mounted ..i am unsure.
i apologise for a myriad of questions....
2. the update.pkg i understand these are region specific.
mine is baseband GAUSB1A110421-EU build 3883.
3. will other basebands work ?
the idea is i make small steps to slowly upgrade from 1.6 to improve the lifespan of the handset.
any basic help would be appreciated.
breaktx
Unfortunately, the fact you're still on Donut (Android 1.6) means that basic help is going to be impossible. The reason being that, if I recall correctly, to do the upgrade from Donut to a later version will require you to manually flash both a new baseband and a new recovery before you can even install a Froyo (Android 2.2.2) ROM. Since you have to flash a new baseband and new recovery anyway, you might as well skip the baby steps and go straight to a custom ROM.
I know that's not the answer you were expecting and I apologize, but it's the simple truth of the matter. In answer to your questions...
1. The recovery image is loaded into the Streak the same way the baseband files are, through the Streak's fastboot mode. While you should look in the Dell Streak wiki on XDA for instructions on how to manually flash the baseband and recovery, I have a tool that can automate the process so all you really have to worry about is installing the drivers, which should be possible using Dell's sync software.
What is stored on the MicroSD card are the actual ROM files. Dell provides them in a .pkg format compatible with the stock recovery. Custom ROMs are provided as .zip files which will not work in a stock recovery but will work in a custom one.
2. Dell ROM packages are region specific. The baseband files and the recovery are all region specific. These regions must match to be able to flash a stock ROM. In your case, going from Donut to Froyo is such a huge jump that the only way I recall to accomplish it is to manually flash the baseband files and stock recovery. It's not as dramatic going from Froyo to Gingerbread (Android 2.3.3), but manually flashing the baseband files and recovery is why I recommended in my opening paragraph to skip the baby steps. Since you're going to have to flash both baseband and recovery anyway you might as well go with a custom ROM rather than stock.
3. This question was partly answered in 2 above. It is possible to install a baseband from a different region than the recovery. As long as the region of the recovery matches the region of the ROM the ROM will install. However, when you boot the device, the OS kernel checks the firmware version of the baseband files to see if it matches what the kernel expects. If the versions do not match, your Home, Menu, and Back buttons will all flash every few seconds. This is an indicator of a baseband mismatch.
To resolve a baseband mismatch you would need to flash the correct baseband. The custom Gingerbread ROM I offer, its predecessor, and all the Cyanogenmod 7-based ROMs all have the baseband check disabled in the kernel, allowing any baseband to be flashed. For an easy example, take a look at my ROM or its predecessor and their "Flash Me Before Installing" packs. That pack will install the 366 baseband, while the ROM itself is 407. Ordinarily there would be an issue of flashing lights but the check was disabled in the kernel, so the flashing lights will not trigger.
Ref: Donut (android 1.6) help.
First and foremost thanks Strephon for the swift response as regards my dilema and an insight into the tasks i may have to do ,to achieve a more useable gui for my device. I sadly do not fully understand this "flashing " process as it is all totally new to me. All i can do is take onboard the points raised ,and take some time to read through the streak wiki.I must admit what you have outlined does actually sound promising with the baseband flashing and the custom rom . I have recently read of such tools as Fastboot ...Android -adb...clockworkmod recovery ..but it is tricky ..for eg .i get into fastboot mode ..connect to my pc ..open cmd ....and it all falls apart from there..as i try to navigate to where fastboot is situated but i fai as the command in the windows shell i cant do as of yet. I appreciate the last thing people need is a fellow user whingeing/whineing as i know it is possible to get a Custom rom onto said device ,but nevertheless must face up to its ...quite hard to get to grips with. As said prior Many thanks for a quite indepth response detailing what i may have to do ..to get a custom Rom to work on my Dell streak 5.in the future i may try the advice given ..with regards the baseband ..and rom ..aswell as the dell sync software.
sadly i am very limited on my knowledge of this subject ...for me the end goal is getting a nice os running on the device ..which has a pleasant interface.I am realistic ..yes the device is years old but it still has capability to be of use to me ..
once again thankyou for the reply/feedback
breaktx
Strephon Alkhalikoi said:
Unfortunately, the fact you're still on Donut (Android 1.6) means that basic help is going to be impossible. The reason being that, if I recall correctly, to do the upgrade from Donut to a later version will require you to manually flash both a new baseband and a new recovery before you can even install a Froyo (Android 2.2.2) ROM. Since you have to flash a new baseband and new recovery anyway, you might as well skip the baby steps and go straight to a custom ROM.
I know that's not the answer you were expecting and I apologize, but it's the simple truth of the matter. In answer to your questions...
1. The recovery image is loaded into the Streak the same way the baseband files are, through the Streak's fastboot mode. While you should look in the Dell Streak wiki on XDA for instructions on how to manually flash the baseband and recovery, I have a tool that can automate the process so all you really have to worry about is installing the drivers, which should be possible using Dell's sync software.
What is stored on the MicroSD card are the actual ROM files. Dell provides them in a .pkg format compatible with the stock recovery. Custom ROMs are provided as .zip files which will not work in a stock recovery but will work in a custom one.
2. Dell ROM packages are region specific. The baseband files and the recovery are all region specific. These regions must match to be able to flash a stock ROM. In your case, going from Donut to Froyo is such a huge jump that the only way I recall to accomplish it is to manually flash
the baseband files and stock recovery. It's not as dramatic going from Froyo to Gingerbread (Android 2.3.3), but manually flashing the baseband files and recovery is why I recommended in my opening paragraph to skip the baby steps. Since you're going to have to flash both baseband and recovery anyway you might as well go with a custom ROM rather than stock.
3. This question was partly answered in 2 above. It is possible to install a baseband from a different region than the recovery. As long as the region of the recovery matches the region of the ROM the ROM will install. However, when you boot the device, the OS kernel checks the firmware version of the baseband files to see if it matches what the kernel expects. If the versions do not match, your Home, Menu, and Back buttons will all flash every few seconds. This is an indicator of a baseband mismatch.
To resolve a baseband mismatch you would need to flash the correct baseband. The custom Gingerbread ROM I offer, its predecessor, and all the Cyanogenmod 7-based ROMs all have the baseband check disabled in the kernel, allowing any baseband to be flashed. For an easy example, take a look at my ROM or its predecessor and their "Flash Me Before Installing" packs. That pack will install the 366 baseband, while the ROM itself is 407. Ordinarily there would be an issue of flashing lights but the check was disabled in the kernel, so the flashing lights will not trigger.
Click to expand...
Click to collapse