Related
I just tried to flash the Telstra (Australia) SBF. No info comes up in file properties and it gives an instant 'failed flash' message.
I am a bit stuck- i can only flash the China Froyo and the GB Froyo, the only 'Fixed' SBF I can ever flash is the 2.2GB_NoCG_31_39.sbf -(Higgsy fix). The China rom is the first and only Froyo rom I flashed with the above fix.
1a. :I want to know why I cannot flash 'fixed SBF's' that come with JBoogie, ADXLmod, barebones etc roms.
1b :Why do I still have to use the 'Higgsy fix' 2.2GB_NoCG_31_39.sbf? It appears that I am somehow locked to it.
1c :Is it because of the Telstra rom I am on- with all rom flashing instructions, it is mentioned eg 'if you are on 2,21 or 2.34 fw etc- no reference is ever made to the 2.26 fw.
2: I want to know how flashing a rom without the corresponding SBF actually affects the operating of the rom- eg: I get random reboots, black screens, freezups=- is this likely an issue with the rom or because I cannot flash the fixed SBF.
3. Will restoring a Telstra nanodroid on top of the China Froyo SBF that I am running, then applying the fixed Telstra SBF that racca graciously provided make my Defy exactly like stock- or will there still be remnants of the China Froyo etc rattling around under the hood and potentially affecting stability and continuing to affect my ability to flash fixed SBF's as per Q 1 & 2.
4. Does anyone have a FullTelstra SBF that works unlike the one already posted on XDA.
I have tried renamimg and moving sbf to root folder as per a suggestion for 64 bit windows, though i am only on 32bit, it didn't work for me- 'start' is still greyed out in RSDLite..
I have also tried different rsdlite versions.
I welcome any other suggestions or questions.. At least I would like to know what is going on and how it affects my phone as I have spent hours and hours searching these and other forums and am none the wiser..
Cheers
Gavin
Accidental 2nd post-ignore.
what exactly are you trying to do?
i can't make much out of your long and pointless statements.
be specific about what you need, then maybe we can help.
all i can understand is that you might want the fixed sbf, so here it is.
http://mir.cr/6MJBVDCN
Thanks for that, pointless is a bit harsh though, long maybe- i was trying to give some background to prevent 'have you tried that, just do this- when it is clearly not applicable to my situation.
I will try to put it in point form.
I hope that is a bit clearer, but it is a complicated situation- there are alot of threads dancing around similar themes, but I cannot find specific answers to these questions- i can't see how I could provide less information without having 5 pages of people directing me to posts that I have already looked at but aren't applicable, so yes it is a bit long, but by doing this much misdirected effort is saved by myself and those helping.
Thanks again
Looking at my original post again, it was hard to see what I was asking, thanks racca.
I just restored the Telstra factory reset nanodroid- the start button was greyed out with the Telstra SBF , so i can't use it. Had to use the 'Higgsy fix' to get it to boot. Weird, i just don't understand it.
To be honest, with all the eventual issues with any rom i use, i would prefer to go back to stock (i will have to put up with the grey status bar, short battery life and no flash). I am tired of getting crashes at the most inopportune times.
Can't wait until the bootloader is fully cracked- I have put Gingervillain (CM7 base) on her Desire, which is much more stable than any rom when i was using it.
Update- it just won't boot now, have to reflash the China Froyo SBF, looks like I am stuck with daily @ 3x daily reboots, bluetooth that works 60% of the time, dropped calls etc....
Change SBF file name
Hey there,
I kinda have the same issues as you do, I think...
The RDS lite gave me an instant ROM-flash error when trying various SBF's. I simply renamed the file name to an SBF file name that was working, yes it got a little confusing... first I renamed the original working SBF to *.old.
Suddenly the flash process was working, I've renamed SBF-files on 4 different occasions in order to get it to work.
I'm not quite sure whether you have this issue or you have something different going on, but feel free to try it.
//Dave
Sounds like a plan, I will give it a go. Thanks.
Thanks Dave69 and Racca, i just renamed the TElstra fixed sbf to the higgsy fix; restored the stock nanodroid and flashed it and it worked. It at least gives me the confidence to flash others now, but will sit on this for a bit- don't have time for more tinkering this weekend.
Titanium wouldn't work with the Telstra rom- said it had restored apps, but wouldn't restore evn one.
Thankfully I got Barebones running, SBF and all. Looks great. Thanks guys.
I would still like to know what's going on though, I haven't tried the TElstra full SBF with the rename yet- it had a different issue than others- just failed. May try again later.
Sounds like you have the same problem as me, was on the telstra on. Not being careful enough I flashed a non downgradable 3.4.2_155-002 sbf. So now I can't downgrade back to the stock Telstra one. I have tried both nandroid backups and flashing the stock telstra sbf and neither work. so am stuck on this rom running JBoogie GingerBlur
Not compaining, for a blur rom it is quite fast, only thing is I can't downgrade back to telstra if the phone needs to be returned for anything.
Hope this helps.
Cheers.
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
superfastmonkey said:
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
Click to expand...
Click to collapse
ok, now where do i begin. i'll just say what i can think of instead of answering every single question.
sbf's contains various code groups as you may noticed while flashing it slipts into smaller pieces.
out of those, cg31&39 are non-downgradable and the pair of them must match. all other partitions on the phone are either not flashed by the sbf (e.g. bootloader/mbmloader, pds), useless (cdrom) or downgradable (kernel, recovery, lbl, devtree).
there are no hardware incompatibilities except the chinese ones, but if you don't update cg31(cdt) to match your /system(cg39) you might have some minor issues (i singles these out because they are not downgradable, of course you'll have issues if you don't match all other things).
you might have a chance fooling tel$tra by flashing the sbf i provided (stock 2.26.0) and restore the nandroid. it should be almost identical except you'll get busted when they try to do flash their service sbf.
the bottom line is,
1. if you flashed any sbf larger than 50MB it must have cg39 in it, and you can't downgrade.
2. you must use matching kernel/devtree with the system: the chinese ones will not be compatible with any other roms, you can't mix match froyo with eclair.
Thanks racca, it makes things a bit clearer. I didn't think I had flashed the GB rom, but I must have-it was 3 or 4 mths ago- it explains why I used the Higgsy fix...i think the China one came out very shortly after..
I should probably try flashing a 2.1 rom b4 restoring the telstra nano if I want stock-( with Telstra, we will have to wait until 3 mths + after the rest of the world gets Froyo for them to fill it to the brim with bloat ware..)..
It looks like the Higgsy fix didn't work for our devices anyway-i suspect my phone believes it is a 3.42 fw now.
In any case, I am relieved to have a way to flash the fixed sbf's now.. Barebones is very impressive, no hint of an issue, but need to run it for a week to really see.
Thanks.
I have a Telstra phone too and after a week of owning it back in January, I had already installed a 2.2 De-blurred ROM. I did have radio issues at first and also remember a non-stop reboot issue. I think it was the USB debugging somehow but I could be wrong.
Now I install new ROMs with ease when the need strikes me.
Are you able to flash the fixed sbfs for roms you install?
I've just put the CM7 rom on mine, best rom I've used. Also flashed a fixed rom with it.
Next thing i tried was restoring a nandroid backup of the default telstra rom, then flashed a fixed stock telstra sbf, this worked and was able to at least make the phone look like it was stock. Whether or not that would be enough if i had to send the phone in for repairs. Can only try if it needs to go in.
CM7 is by far the fastest rom I've tried. Only used for a day so far and no problems yet. Highly recommend this one.
Cheers
Sent from my MB525 using XDA App
I flashed the fixed sbf by renaming after restoring the telstra nano and it worked, but didn't run properly, I did it a couple of months ago with just the nano after having jboogies blurless ginger and it passed for warranty. Haven't tried renaming the full telstra sbf yet. I might over the long weekend.
Sent from my MB525 using XDA Premium App
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
samorgs said:
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
You'll be fine.
On a side note, it's ridiculous that Optus have official froyo already, Telstra due in July.
Sent from my MB525 using XDA Premium App
If you were impatient and flashed a leaked SBF like and still wants to get the official update, here is a shord guide for you. I examined the 6.36.0 sbf and the code groups for CG31 and CG39 are the same as the leaked froyos so i flashed it on my phone running CM7 and it booted After it i downloaded the OTA let it install and now i am on the official 2.2. I can change it with the CM7 anytime i want and if i have to take the phone to the service restore it to stock 2.2 So step by step
1. If you are on any leaked froyo download the latest us eclair sbf(JORDN_U3_6.36.0) from http://www.and-developers.com/sbf:defy
2. Boot into the stock recovery and wipe
3. Boot into the bootloader and install the SBF from point 1
4. Let the phone reboot then go throught the motorola blur registration then setup a wifi connection.
5. Download the OTA (settings->about) and if the download finished let it reboot and install the update.
6. Enjoy stock untouched 2.2 T mobile froyo
hi is this only for US people or will it work in UK as well?
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Does it supports 720p video recording!!
vick33 said:
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
What is the version number after the update?
Anyone can upload nandroid and sbf ?
It came out as OTA so no sbf available. Every version is the same as it was with the test update... it is android 2.2.1 34.4.9 they did not changed anything from the test update so i am not satisfied at all...
Sent from my MB525 using XDA App
Can i send in my defy for service with this rom?
Edit: I guess this rom is official. Read this thread. http://forum.xda-developers.com/showthread.php?t=1044980 .Cool stuff. Thanks for the heads up!
I tried flashing this and now my phone wont turn on i needed this so i can return it to T-Mobile with a stock ROM, but now my phone won't even turn on. Tried removing battery and putting back in, no matter how long i press the power button, it wont even turn on. help plz
On which rom were you before? Did you wiped before flashing the sbf? I have done it myself many times.
i was on CM7 and i wiped and flashed like u said. it might be my phone.
EDIT:
well nevermind, looks like the screen is fried. it seems to have flashed but the screen wont display anything cause when i plug it in to the computer, i hear the little beep and the LED notification appears, but no display.
you cant burn the screen like that. If it beeps then you are ok. You should try flashing the nordic sbf for example, fom it i have gone fortth and back to the us froyo the way i described.
so what should you do:
1remove your battery and while putting it back hold volume up.
2 start RSD lite and connact your phone
3 if it is connected flash the sbf.
If the PC does not sees the defy then your battery is flat. Charge it with an external or try mcgyver, you cant brick defy with flashing.
Will this work if you flashed the 2.2 OTA then used a custom froyo ROM. I basically want to take this phone back to stock.
I thought we couldn't downgrade.
Sent from my MB525 using Tapatalk
i was on nordic when i did the things i written. Got back the official now i have done it from other custom roms like CM7, but wipe in the stock recovery before trying it. I dont have any problem but seems like someone had so be careful.
I'll give it a shot because my nandroid restore is buggy.
Will post results.
Sent from my MB525 using Tapatalk
It would be interesting if it wont work for you. Cg-s for the us eclair are same as for the froyos
Sent from my MB525 using XDA App
Finally a way for US users to return to FULL STOCK regardless of firmware
It worked!!!
I was on barbones 1.5.1 then went to a backup nandroid version of my original stock rooted. Was kind of buggy so I decided to try this
1. Wiped everything using the stock recovery
2. Bootloader and flashed nordic 2.2.2 and "skipped" the automated setup until the phone desktop appeared then waited until RSD said the phone "passed".
3.Wiped everything using the stock recovery again
4. Bootloader and flashed 2.1 JORDN_U3_6.36.0 then pressed "start" at the motoblur screen and waited until RSD said the phone "passed".
5. I then entered my motoblur info and "skipped" everything until I was at the android desktop. After syncing was finished (waited about 5 min) I proceeded to "Download the OTA (settings->about->system updates) and after the download finishes let it reboot to install the update"
Thanks "vick33" nice find!
Note:
I could not update the kindle app without it giving me unsigned package errors. My solution was to root and uninstall the oem kindle app.
Then unroot and perform a factory reset. The oem kindle app did not restore and I was able to install the latest kindle without errors.
No other issues have been found.
*** CONFIRMERD TO WORK ***Another solution maybe to update the kindle app prior to updating the phone to 2.2 via OTA. Possible the better way to go considering it does not require rooting or removal of a system installed bloatware.
i mean the screen doesnt show anything. screen is black, idk whats wrong with it. im not saying the sbf had anything to do with it, just saying the screen went out. i just turned it in anyways, so ill be getting a new one soon.
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
Inherited a Droid Charge running GummyCharged 2.1 from my housemate.
I want to switch to Eclipse 2.0. I know in order to run FP1 builds, you need to run stock kernel if you want wifi. Except, I also noticed that the PBJ kernel recently fixed the wifi issue.
I'm under the impression you're told to revert to stock, run OTA update, then flash your FP1 ROM so you have the latest stock kernel.
Or is there more to it than the kernel?
I'd rather skip the revert/flash/etc/etc, I updated to the latest CWM, made a backup, factory restored, wiped cache/dalvik, flashed ROM, flashed kernel, rebooted, everything seems fine (wifi working no issues). But... that doesn't mean that it is.
EDIT: Yeah, my baseband in About Phone shows i510.06 V.EE4 SCH-I510.EE1, which is what it was before. Can I get just the baseband?
Thanks!
By the way, I don't care about carrier signal at all, this phone got wet and no longer accepts SIM cards. The other functions still work, so I'm using it on wifi and I'm trying to re-purpose the device to be a portable offline GPS for hiking. But I did read that FP1 gets better GPS locks, which is part of why I want to run it.
U cant get the fp1 upgrade on a cstom rom. U have to go back to stock n get the ota upgrade. I suggest usin titanium to back up ur stuff then flash what u want. Stock fp1 or pjb 5/24 r both good, but u gta get back to factory first.
Sent from my SCH-I510 using XDA
Actually, I figured "what you do do well" and I decided to follow the suggested directions. I used ODIN, restored to stock EP4... and couldn't get past the main screen. Can't read SIM cards, so can't get past the activate screen. I then flashed back an FP1 rom, the latest PBJ kernel, and [attempted] to use the EP4 to FP1 patch, which hung and failed.
It looks like if I want to get my baseband to FP1, I'll have to jump through hoops (maybe flashing a stock EP4 pre-rooted ROM from ODIN? maybe?) Regardless, since the CDMA antenna in this thing is useless anyway, I'm just gonna skip it.
Thank you for your reply!
Well, now that you have borked your phone a bit, go and download the EP4 ODIN package and flash it (in ODIN or SamsungPST). Might not be a bad idea to flash the PIT while you're at it. You'll probably have to flash CWM, and then PBJ from within CWM (stock kernel overwrites it) Then go and try flashing your ROM of choice again (cough *tweaked* cough), either in ODIN (with the respective package) or CWM. (again with the proper package).
http://www.imnuts.org/odin-packages/
Sent from my SCH-I510 using xda premium
thanks kvswim, that's pretty much exactly what I did yesterday. I'm even running Tweaked 2.1
It's too bad, I really prefer the theme of Eclipse, but I just couldn't handle the lack of TSM Parts.
Hi,
I need some help. I am an XDA lurker and have learned a ton. I am mostly aware of the usual fixes for these things, but I can not return to any other ROM than a CM10. CM10 data and camera are not working great, even though I LOVE this ROM and LOVE these developers, I can't use it yet.
Firtst, my backups are gone, I know, I know. But they are gone. I tried flashing NoSympothy and invisibleK,s stock ROMs but I get frozen at the Galaxy SIII screen everytime.I have tried all the usual system wiping drills, cache, data, etc... Formatted everything. I have downloaded from multiple sources. It seems like it doesn't like ICS now?
I am rooted and UNLOCKED! Woohoo, thanks Adam!!!!!
Any suggestions?
Recoverys to CM10 work. New flashes to CM10 work. But no stock image or stock rom?
rude53 said:
Hi,
I need some help. I am an XDA lurker and have learned a ton. I am mostly aware of the usual fixes for these things, but I can not return to any other ROM than a CM10. CM10 data and camera are not working great, even though I LOVE this ROM and LOVE these developers, I can't use it yet.
Firtst, my backups are gone, I know, I know. But they are gone. I tried flashing NoSympothy and invisibleK,s stock ROMs but I get frozen at the Galaxy SIII screen everytime.I have tried all the usual system wiping drills, cache, data, etc... Formatted everything. I have downloaded from multiple sources. It seems like it doesn't like ICS now?
I am rooted and UNLOCKED! Woohoo, thanks Adam!!!!!
Any suggestions?
Recoverys to CM10 work. New flashes to CM10 work. But no stock image or stock rom?
Click to expand...
Click to collapse
You have to flash the stock kernel as well as the ROM. Try flashing the Synergy latest nightly build it includes a custom kernel as long as your bootloader is unlocked.
Thanks,
I had a feeling it was something with the kernel. I wasn't sure what was included though. I think I tried to get synergy from here on my phone and it just kept opening new windows instead of downloading. I will grab the just the kernel from somewhere and let you know. I'll update in an hour or so. Thanks for the next few steps to try. Much appreciated!
That was it THANKS!!!
adclem said:
You have to flash the stock kernel as well as the ROM. Try flashing the Synergy latest nightly build it includes a custom kernel as long as your bootloader is unlocked.
Click to expand...
Click to collapse
Stock ROMs include the stock kernel. They will work as a one flash wonder. Your issue more sounds recovery based. Which recovery from which app were you using? It more sounds lime maybe you're still on a kexec recovery which is why you couldn't flash stock but synergy latest worked (or something of the sort, maybe other way around)
Sent from my Galaxy S3 using Tapatalk 2