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
Related
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
First of all, I apologise if this is the wrong forum to post this on. I'm not new to the Custom ROM scene, having come from my HTC Desire. However, the SGS2 is my first Samsung product, and hence a few of the terms are rather confusing to me, and I hope this'll help somebody else as well besides me.
1. Why are there so many different kernels? KF1? KF2? XXKF1? XXKF2? What're the differences? Can I flash a KF1 kernel into a phone that already has KF2?
2. What's the difference between an i9100 and an i9100T? Can I flash a kernel designed for an i9100 into an i9100T phone?
3. What do the different shipped modems mean (from http://forum.xda-developers.com/showthread.php?t=1131950)? How are they relevant when I'm choosing which ROM to flash into my phone?
4. What's a HIDSWVER and why are we collecting it (from http://forum.xda-developers.com/showthread.php?t=1089874)?
You know there's a Q&A section right?
(agreed that this should be moved to the Q&A section of the forum!)
Hi I'm in the same situation as you, I was just preparing a similar question but will add it to yours, perhaps there are more HTC (Desire) converts coming that might be interested in this kind of FAQ
My SGSII was bought unbranded with the following software PDA:XWKE7 - PHONE: XXKE4 - CSC: UXKD3 - Build date: 5/18 KST 2011 and it is only 5 days old so I don't want to ruin it just yet
I've flashed an insecure kernel that was the same as the kernel that my SGSII had originally (PDA:XWKE7) with Odin following the instruction in this post
http://forum.xda-developers.com/showthread.php?t=1125414
It took me a few tries before I saw that I had to install Samsung's KIES program first, I know it is in the instructions but it could be shown a little clearer imho.
And I've flashed a secure kernel (same version) back so that there's no more yellow triangle.
Now for the questions:
I don't seem to have the CWM recovery, what do I have to do for that?
With what I've done will I still be able to get the Samsung updates, it currently says "This version cannot be updated"? (I may not really want that)
I now actually still have the same phone that I bought, how do I go about actually upgrading, can I just install (using Odin) the latest of all 3 things (PDA,PHONE,CSC) or do I need something for that or should I match certain things like some version of PDA only goes with some version of PHONE.
Can I flash new things just using the phone, it looks like everything has to be done with Odin, on the HTC phones I found it more comfortable to flash on the phone itself (no risk of computer crashing or cable disconnecting...)
PDA is kernel PHONE presumably is modem, what is CSC?
Edit2: found some of the info here:
found here http://forum.xda-developers.com/showthread.php?t=1075278
but still not clear on CWM, and what can be flashed and when.
Edit: Perhaps I just need CWM so that I can start experimenting once I have a nandroid backup, I've found this [KERNEL] ClockworkMod Recovery 4.0.0.5 // Initramfs Template for Devs but it is not really clear if that will install a new kernel (which one?) or only CWM, can I install that on my phone, it doesn't seem to root ... questions ... questions ...
inb4 http://www.youtube.com/watch?v=JmvCpR45LKA
soupiejr said:
4. What's a HIDSWVER and why are we collecting it (from http://forum.xda-developers.com/showthread.php?t=1089874)?
Click to expand...
Click to collapse
I seem to have a HIDSWVER that had not been reported yet, I posted it in that thread.
I9100XWKE7/I9100LUXKD3/I9100XXKE4/I9100XWKE7 - Belgium unbranded
Product code GT-I9100LKALUX
I got CWM here
http://forum.xda-developers.com/showthread.php?t=1103399
I jumped the gun even though it is a XEU version and my phone has LUX, doing a nandroid now, will feel a lot safer when that is working
The thing that still eludes me is that most posts like that talk about having the correct firmware but then how can I upgrade or do I have to do that at once kernel+firmware?
BelgianAtheist said:
I got CWM here
http://forum.xda-developers.com/showthread.php?t=1103399
The thing that still eludes me is that most posts like that talk about having the correct firmware but then how can I upgrade or do I have to do that at once kernel+firmware?
Click to expand...
Click to collapse
You generally flash both kernel and firmware at the same time, either via ODIN, or CWM (depending on what you are doing).
Kernels ship with ROMs. So the KF2 ROM has the KF2 kernel with it.
BelgianAtheist said:
(agreed that this should be moved to the Q&A section of the forum!)
Now for the questions:
I don't seem to have the CWM recovery, what do I have to do for that?
With what I've done will I still be able to get the Samsung updates, it currently says "This version cannot be updated"? (I may not really want that)
I now actually still have the same phone that I bought, how do I go about actually upgrading, can I just install (using Odin) the latest of all 3 things (PDA,PHONE,CSC) or do I need something for that or should I match certain things like some version of PDA only goes with some version of PHONE.
Can I flash new things just using the phone, it looks like everything has to be done with Odin, on the HTC phones I found it more comfortable to flash on the phone itself (no risk of computer crashing or cable disconnecting...)
PDA is kernel PHONE presumably is modem, what is CSC?
Click to expand...
Click to collapse
Hi, i am comming from HTC Desire, like you.
I will try to answer your questions, but be aware some of my answers may be inaccurate because of lack of expertise.
1) you have to use the CF-Root kernel, appropriate to your ROM version (e.g. KE7 CF-Root kernel with a PDA:XWKE7) to have CWM.
Please notice, that CWM on Samsung phone is much like ROM Manager on HTC Desire (a "normal" Android application, not a bootmanager extension !)
To get rid of the yellow triangle while using the CF-Root kernel a workaround is needed ( i havent tried this yet):
1.1 - flash CF-Root (Odin)
1.2 - flash original kernel back (Odin), i mean KERNEL (8MB) and not the whole ROM (500MB)
1.3 - flash the zimage file inside of the CF-Root *.tar file ( unclear how, through CWM ???)
2) you can still flash official Samsung updates after flashing a custom ROM or kernel. Just use Odin instead of Kies. You can get the official Samsung firmwares here: http://forum.xda-developers.com/showthread.php?t=1075278
3.) I would recommend to flash only the PDA (depending or a ROM, that you choose) or a complete official ROM containing all three parts (PDA+CSC+RADIO).
I wouldnt flash the CSC, as it apparently contains regional settings (e.g. dutch/french menus in case of Belgium).
I am not sure whether all RADIOs work flawlessly with all the PDAs ... Usually ROM cooker shold take care of this. I would recommend to use a RADIO for your region (if not recommended otherwise by ROM cooker).
4.) I recommend to flash using Odin, because its firmware independent. By my opinion Samsungs way is the more secure, because you don't need to flash the bootmanager ! You can fall bak to official firmware, or reflash again, any time using the original bootmanager + Odin. Flashing bootmager on HTC Desire was the most risky operation (fail = bricked phone). S-OFF isn't needed for Samsung too.
5.) by my opinion:
PDA = ROM (kernel+software)
PHONE = modem
CSC = regional settings (localized menus)
i second this remark
Awesome, thanks clovek1 that cleared up quite a few things.
1)
I seem to have CWM at boot now much like on my Desire, is that a new thing for SGSII?
2)
Ok, so if I want to go to that KF3 that everyone is posting about and hopefully not have the AOS bug anymore (the battery is not at all what I expected, in a bad way with) than I can go to that link you posted and choose one of the XWKF3 fw's, and since I would rather not have anything french or dutch I could use the XEU one, regardless of what pda, phone or csc I have?
That will probably erase the phone memory (apps etc) right as it is an upgrade to Android 2.3.4?
Thanks again for the explanations, very interesting post
BelgianAtheist said:
Awesome, thanks clovek1 that cleared up quite a few things.
1)
I seem to have CWM at boot now much like on my Desire, is that a new thing for SGSII?
No predates to SGS 1
2)
Ok, so if I want to go to that KF3 that everyone is posting about and hopefully not have the AOS bug anymore (the battery is not at all what I expected, in a bad way with) than I can go to that link you posted and choose one of the XWKF3 fw's, and since I would rather not have anything french or dutch I could use the XEU one, regardless of what pda, phone or csc I have?
yes XEU choose language after install .
That will probably erase the phone memory (apps etc) right as it is an upgrade to Android 2.3.4?
No 2.3.4 is yet to be released by Samsung .
KF3 = 2.3.3
KG1 = 2.3.4 leaked rom probably test version NOT released by Samsung
KG2 = 2.3.3 last release Saudi Arabia i believe a Samsung release .
jje
Click to expand...
Click to collapse
JJEgan said:
BelgianAtheist said:
That will probably erase the phone memory (apps etc) right as it is an upgrade to Android 2.3.4?
Click to expand...
Click to collapse
No 2.3.4 is yet to be released by Samsung .
KF3 = 2.3.3
KG1 = 2.3.4 leaked rom probably test version NOT released by Samsung
KG2 = 2.3.3 last release Saudi Arabia i believe a Samsung release .
jje
Click to expand...
Click to collapse
Sorry for maybe asking the obvious but did you mean "No, it will not erase the phone memory" or just "No, it is not an upgrade" (or No to both)?
BelgianAtheist said:
Awesome, thanks clovek1 that cleared up quite a few things.
1)
I seem to have CWM at boot now much like on my Desire, is that a new thing for SGSII?
2)
Ok, so if I want to go to that KF3 that everyone is posting about and hopefully not have the AOS bug anymore (the battery is not at all what I expected, in a bad way with) than I can go to that link you posted and choose one of the XWKF3 fw's, and since I would rather not have anything french or dutch I could use the XEU one, regardless of what pda, phone or csc I have?
That will probably erase the phone memory (apps etc) right as it is an upgrade to Android 2.3.4?
Thanks again for the explanations, very interesting post
Click to expand...
Click to collapse
1.) you CAN'T boot into CWM on SGS II like on HTC Desire. CWM is not a part of bootmager, but CWM is just an application.
CWM on SGS II is like ROM Manager on HTC Desire.
This means, you can enter the CWM only by
- starting the CWM application(or ROM Manager on HTC Desire)
- choosing reboot into CWM (puts CWM application to CACHE, reboots)
- waiting until the CWM starts from CACHE (temporary stored)
if you however try to manually enter the bootloader mode, you end up with the Samsungs stock bootmanager (and Odin).
This means, the CWM isn't usable on Samsung phones as the last instance for help, in case of destroyed ROM. Because with a destroyed ROM (PDA) you cant push the CWM into CACHE and force the phone to boot with CWM.
You can only use the bootloader, which isn't altered by the CWM in any way (on HTC Desire, HTC Desire the bootloader is replaced by a custom bootloader, which includes CWM).
Therefore CWM on Samsung makes no sense for me (nobody can't use CWM to flash a new ROM, if the current ROM isn't working). The only partially usable feature of CWM is the Nandroid (which works in a quite limited way, as it doesnt restore RADIO or CSC).
2.) i do remember flashing new ROMs (only PDA) on SGS II without having to reinstall applications (mainly Stock ROMs and Lightning ROMs, which seems to be compatible regarding applications).
I do recommend a Nandroid (through CWM) + Titanium backup in any case, before installing a new ROM. you can return to previous state later (but not as easily, as i would expect from Nandroid ...).
Hi everyone,
I was able to recover my phone on the weekend after trying my hand for the first time using FlashTool on the weekend. I understand now how putting .ftf files in the firmware folders work (please don't laugh at how non-technical I am with this - I am a Windows system admin by day - I just don't have a lot of under the hood experience with Android). I understand how to flash the .ftf files onto my handset.
I flashed on Saturday, in a means to recover my phone a whole bundled package (I got it from: http://forum.xda-developers.com/showthread.php?t=1192152&highlight=) It's essentially the stock 2.3.3 ROM and it has Baseband 2.1.71 prebundled.
The downside is that I can't install Xrecovery now because my phone isn't rooted now and I don't want to go through the process of using ADB to use gingerbreak.
Is there a 2.3.3+ ROM including BB 2.1.71 and xRecovery ftf bundle out there?
That thread is the pre-rooted 2.3.3 with recovery. Not sure what else you could want.
Try entering recovery when you turn the handset on and pressing the volume down key when you see the white Sony Ericsson text
Okay thanks. I've always entered recovery by going thru by pushing the back button (not volume down). Let me try it. I'll get back to you in a minute.
Ya pressing the volume down didn't get me into recovery. I've also tried installing xrecovery the usual way of downloading busy box, allowing non market apps, using a file mgr to open the xrecovery installer but it fails because the device isn't rooted. I can't su on a terminal emulator either so I don't think this rom i flashed is rooted.
It completely wiped my phone and installed 2.3.3 and 2.1.71 baseband (which is what I want) but now I want it to be rooted so I can play around with more ROMs.
Ok, I remember from when this first came out, you need to flash 2.1 firmware and root it, install xrecovery and then follow the procedure in that thread you posted. That should give you the pre-rooted and pre-installed xrecovery.
It's okay, If I'm going to do that much work I might just use the Android debug bridge (ADB) to install Gingerbreak. No big deal..
2.3.3 stock is a very nice improvement over 2.1 from what I remember. I used FreeX10 2.2 and it was nice as well (but I felt the UI looked a little dated). 2.3.3 stock looks and feels great, but I want even better battery life and better perfomane I know some of the custom ROMs can offer me.
I like the CM7 based 2.3.5 ROM I've seen on this site, and I wanna try 2.3 Free X10 from zdhiu.
Fair enough, I'm using the CM7 FXP rom and its flying. Battery life is pretty much the same as I was getting from SE firmware too.
Awesome!
So just to clarify the usual procedure:
You get your device rooted and xRecovery installed by whatever means. Since my X10 is a clean slate with just 2.3.3 on it with baseband 2.1.71, I will need to use Gingerbreak to root and subsequently install xRecovery.
Then put the .zip for the ROM on the SD card, flash it using xRecovery
Then remove battery, reboot, then using flashtool, flash the baseband and firmware?
I've only been using Android for a few months, and just learned about using custom ROMs in the past 6 weeks or so. I've learned a lot since then lol.
Sounds pretty much right to me if your bootloader is locked.
Okay, great. I really am learning more and more. I'm in IT myself for work, but phone hacking was never really my forte until just recently.
I like the type of flashing that I did in FlashTool with the current ROM I'm running from that previous post.
It was the baseband and firmware and ROM all bundled. I know FlashTool lets you make bundles too.. I find that easier than flashing the ROM in xRecovery and then flashing the firmware and baseband second.
What do you think?
I've found that installing the rom in xrecovery is good as I can make a full backup first and then flash the zip.
I always tend to flash the baseband and/or firmware first, but thats personal choice.
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Dresden21 said:
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Click to expand...
Click to collapse
Let me clarify...
1. ROMs are in zip packages, and are to be flashed using xRecovery.
2. Firmwares are in ftf bundles, which are flashed through flashtool.
3. If you want root and xRecovery on 2.3 follow aZuZu's post on rooting and xRecovery.
4. If you want to unlock the bootloader follow the_laser's thread
Dresden21 said:
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Click to expand...
Click to collapse
You need to downgrade baseband so you can root.
Check here buddy....http://forum.xda-developers.com/showthread.php?t=1196808
then you can install xrec and install your rom. Might want to read this: http://forum.xda-developers.com/showthread.php?t=1254087
then this: http://forum.xda-developers.com/showthread.php?t=1278318
all very simple procedures.. good luck!
But I'm a bit (really) confused about a lot of things regarding this process. I've been reading for a week now and barely getting anywhere.
So first, a little history.
I'm running a stock vibrant, Froyo.UVKB5, 2.6.32.9 kernel, never been rooted.
Now, one of the main reasons for my upgrade is the loss of wifi connectivity. For some reason I can no longer connect to most ISP's or WIFI hotspots, especially my own.
Now, here's the kicker; I don't have a data package on my service so I am dependent on wifi only. Now that I can't get wifi, I'm not sure if I can get all the files I need to do this upgrade. I'm hoping this upgrade will reconnect me to wifi.
Reading through the Wiki for rooting (http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959), it says I am to use Superuser AND binary, is this correct?
I've found a boatload of Superuser files one the ClockworkMod ROM Manager website, ... which one do I use, there's no explanation?
And I understand I need to install SuperSU AFTER I have it rooted.?.
Regarding an updated OS, from the questions and remarks on this post (http://forum.xda-developers.com/showthread.php?t=1900763), I need both a kernel AND a rom? But other threads I've read say the kernel is in the ROM. Does this mean that CyanogenMod's CM7.2.0 is kernel only and doesn't get you anywhere?
Also from this thread, suggestions were made to upgrade to one kernel, then a rom, then to another kernel and rom, and finally to the kernel and rom the user wants. Why is this necessary?
I have many more questions but they branch off depending on answers to these fundamental questions here.
So, if there's anyone with enough patience and willing to hold my hand through this process, I would greatly appreciate it.
And I need to go cancel my monthly paid warranty fee on this old phone too.
ROMs typically include a kernel in their update zip. CyanogenMod is a ROM and as such includes our own kernel when you install it. Be aware of the 911 issues before upgrading your os to a custom rom.
Sent from my Galaxy Nexus using xda premium
To install Clockworkmod, if you are using Android 2.2 Froyo, go here: http://forum.xda-developers.com/showthread.php?t=833423
Run the "3e_recovery_installer" from your computer with the phone connected and USB debugging mode enabled. Then boot into stock recovery (Hold VOL+ and VOL- and POWER with the phone off, release when you see the logo) and flash the "update.zip" twice. It will boot into a green CWM that temporarily exist until you turn off the phone, beware that this temp CWM only let you flash zips from your Vibrant internal storage, it will not recognize your microSD.
Note: If you are using Eclair 2.1, you should be able flash the update.zip directly without the "3e recovery installer".
You can either flash root from CWM, or download a rom like SlimBean and flash it directly. When you flash a custom rom, it will install a newer version of CWM first (because the older version of CWM will not be able to flash the rom) and the phone will reboot. Take off the battery and put it back, boot into recovery again to see the new version of CWM, then you can install the custom rom again fully this time. Generally you should do a "wipe data and cache" before installing a rom, but sometimes, you might also need to go to "mount and storage" and format the /system folder before you can flash a new rom successfully. This can help avoid system files from your old Android installation to exist and merge with the new rom installation. However, the /system folder is where most of the OS important files are locate so without it the phone won't boot, so you need to have a custom rom in the phone (or microSD) to flash after you format it.
That should pretty much cover most of it. If you ever run into problems you can always use ODIN to recover the phone to factory stock. In fact, if you want to stay with stock and just want your WiFi to get fixed, its probably better to simply do an ODIN recovery (or a factory reset) first, before looking at custom roms.
Most of what I just said is covered in this sticky: http://forum.xda-developers.com/showthread.php?t=849028
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!