Related
I was in a hurry and upgraded my GF's Rogers Captivate to the leaked 2.2 ATT some time ago. It seems now that the backup I performed (via Titanium) was not the full backup I required and therefore I have no backup to revert to my Rogers stock 2.1.
Her phone is operational, it's an improvement from 2.1 Rogers stock but I've now realized that if the phone isn't actually mine to play with, its not worth playing with.
With Rogers 2.2 released there is indications that it fixes things that I/she would like resolved (mainly the SMS timestamp? and better GPS functionality?)
I would like to return to a normal state of Rogers 2.2 and then stop playing with her phone.
There is a thread here on how to return to Rogers 2.1 but it is large and has multiple solutions and warnings enough to make it seem like its not the easiest path to venture...
http://forum.xda-developers.com/showthread.php?t=846501
Then again there is other threads showing how to just simply flash to a Rogers 2.2 ROM....
http://forum.xda-developers.com/showthread.php?t=905655
Will there be disadvantages to taking what seems like the easy route and flashing simply to Rogers 2.2 without going through a convoluted process to revert and kies update to 2.2? Clearly I'm not fully competent regarding this and its difficult to get better when you don't yourself actually own an android phone (hence why I'm trying to bail). I just want to find the easiest way to essentially get out of the mistakes I've made, and make them as forgettable as possible. Any advice would be appreciated.
I don't see anything wrong with flashing straight to Rogers 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
I use Odin to flash stock 2.2 most simplistic way to do it. Saves you the hassle of having to deal with Kies.
I used the odin flashable file from here. No need to get the kernal/moden file it's already in the .tar
Do I need to save the APN settings or anything?
Assuming I have no interest in any personal data will flashing via odin the above mentioned I896UXJL1-HOMEBINARY.TAR bring me back completely to Rogers?
My APN settings and everything will be back to default rogers?
Will the AT&T symbol still be there on boot?
If I want to try a custom ROM in the future will I be able to do it from here, or will I need to flash to 2.1 or some other stock ROM?
I can't seem to install CWR in my current state, will this potentially change that?
Uc an use ODIN to flash back to 2.2 Rogers but I am afraid u will stll see At & T logo when u boot it up
There is a thread to replace that logo as well
The AT&T thing doesn't really bother me.
I left this problem and didn't deal with it because her phone was working fine and I would have rather not touched it. The problem now is that Rogers in Vancouver had some massive downtime a few days ago and now her phone refuses to run data. Voice is fine, I modified and played with the APN settings to no avail.
After testing the SIM and some other options it seems that I'm left with no other choice but to conclude that this is my fault and I guess going forward on flashing a stock 2.2 Rogers hopefully will resolve this.
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
Ok, major screw up on my part. Accidentally odined the ATT Captivate stock files to my Showcase. Needless to say, i had a brick for a while. I have managed to get the phone back into download mode and loaded the Mesmerize software. The phone can at least make calls now, but no data yet. Does ANYONE have ANY odin files for CS? Or any advice would be good too.
Check your PM.
Ok, got stock CS software running on the phone again, but I still have no 3g or 2g data connection. Any thoughts?
Nevermind. Just forgot to do *228. Long day today.
Any chance I could get a copy of Odin for Showcase? I have to go back to stock for warranty purposes? Thanks!
I know this is an old post, but I cant seem to find the Ntelos odin files for the showcase. anyone got them?
I have the same problem. I have an NTELOS Showcase and I accidently flashed Cellular South Odin on it. Phone can still make calls but its crippled. No 3G and its just crap! Not sure what to do. I just want it back to Stock NTELOS again
tecknogod said:
I have the same problem. I have an NTELOS Showcase and I accidently flashed Cellular South Odin on it. Phone can still make calls but its crippled. No 3G and its just crap! Not sure what to do. I just want it back to Stock NTELOS again
Click to expand...
Click to collapse
Having the same issue. I accidentally flashed US Cellular stock files on mine and now I have no 3G. There's no development support for Ntelos and no one seems to either know what to do or care to help.
This is for the generic showcase http://rootzwiki.com/topic/19968-odingeneric-showcase-ntelos-fa10ei20eh09/
CSPIRE Showcase
I am having trouble getting my sch-i500 back up and running. I had updated to ics aokp_fascinatemtd_build 28, but ran into the problem of it showing that i was on verizon towers. I downloaded and tried to odin a cspire modem but no help. also tried *228 before and after the modem file. I can get cwm4 fixed for cm7 to come up and also the download for odin screen, but none of the files i have downloaded will work. it gets to factoryfs and hangs up. I have downloaded almost all files from rootzwiki labeled for use with cspire. any help will be appreciated.
ok so i got my phone up and running, aokp ics. but it was showing verizon as my carrier. I downloaded the cspire ei20 modem file from rootzwiki, used odin with atlas2.2.2.pit, put the modem file under phone section as instructions on rootzwiki said, checked repartition and clear phone efs, now the phone will not turn on. I can still get to download and intend to redo the aokp when i get home this evening. but how do i get the modem for cspire to work?
Thought I'd ask this one.
I am a UK 3G xoom owner and learning flashing, rooting, adb quite quickly.
I have flashed the Telstra stock to try and update using Simba90s directions (separate thread) and recovered.
I have flashed the US Verizon stock image and recovered from that (sweating buckets).
I have reflashed the UK stock and am working perfectly again but without SD support or any 3.1 enhancements.
My question is, as I seem others have done it, can I flash the US WiFi images to my Xoom and update as usual? No other adaptions, just stock.
I know I will lose 3G but am not worried about that. I want to check functionality and reflash UK stock when update is ready.
Flashing the Verizon stock images caused the "Failed image LNX 0x0002 / RSD mode 2" and deep panic.
xoomtastic said:
Thought I'd ask this one.
I am a UK 3G xoom owner and learning flashing, rooting, adb quite quickly.
I have flashed the Telstra stock to try and update using Simba90s direction (separate thread) and recovered.
I have flashed the US Verizon stock image and recovered from that (sweating buckets).
I have reflashed the UK stock and am working perfectly again but with SD support or any 3.1 enhancements.
My question is, as I seem others have done it, can I flash the US WiFi images to my Xoom and update as usual? No other adaptions, just stock.
I know I will lose 3G but am not worried about that. I want to check functionality and reflash UK stock when update is ready.
Flashing the Verizon stock images caused the "Failed image LNX 0x0002 / RSD mode 2" and deep panic.
Click to expand...
Click to collapse
As I said in your other thread, once you have AU 3.1 on you can flash tiamat 1.1 and keep 3G. I have 3G with orange working just fine.
Lordao
I just ordered a recertified Verizon 3G Xoom, and I didn't think about the implications of it being a Verizon device. This is NOT upgraded to 4G LTE -- will the "Stingray" builds of the various ROMS still work? Is there any way to apply WIFI-only ROMS (including stock) if I don't care about the 3G working? Given the age of the device I really want to get Jelly Bean on it.
I will need to cancel this order ASAP if the answers to these questions turn out to be "no"...
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
trunzoc said:
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
Click to expand...
Click to collapse
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
magnafides said:
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
Click to expand...
Click to collapse
Thanks. I'm placing my order as soon as Wife says OK. If you don't mind, and if you remember, please send me a PM of how it goes with the flashing once to get yours.
Would love to coordinate what we do since there doesn;t seem like a whole lot of certainty exists about what we are trying to do.
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
magnafides said:
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
Click to expand...
Click to collapse
Any luck? I also have a Xoom 3G MZ600 on the way and could careless about 3G...
hasnt eos got jellybean roms for all versions of the xoom? 3g should work imo
Sent from my Xoom using XDA Premium App
I'm in the same boat and curious to see if anybody has any words of wisdom. I love my refurbed Xoom 3G but am eager to get JB on it. Any help is greatly appreciated.
FWIW everything I have heard/read seems to indicate that it is possible to flash WiFi only ROMs on the 3G Xoom, and apparently everything will work fine except for the 3G (naturally). I haven't taken the plunge yet myself, still running stock ICS.
Is there any word on whether the Verizon 3G Xoom will get Jelly Bean?
It can be done....
I purchased a used 3g Xoom around Apr 2012. After initially unlocking / rooting and installing a ROM (EOS) on my 3g Xoom, the 3G radio wasn't working so I started fresh. I locked the device and SBF'd the original Xoom firmware, then used the official over the air (OTA) upgrades to get back to stock ICS. I thought this might fix the 3g issue; it did nothing.
EOS Roms overclock the GPU by default, which caused problems with my (and my wife's Wifi version) Xoom. My only requirements for a ROM are stability, no clutter from dumb carrier installed applications, compatibility, and of course root access. I found a pre-rooted stock Jellybean rom, but it was for the Wifi Xoom. It worked great on my wife's though; and heard rumors that it could work with mine.
*SO*...I took a leap of faith and installed it. It works great. No 3g radio of course, but I gave up on trying to get that to work anyway...so if you don't care about losing your 3g , this will probably work for you. I don't think my 3g will ever work, but I suspect this won't ruin yours if it is currently working. Don't hold me to that; this is a risk.
Random notes and refresher info:
-you will need an SD card. I'm pretty sure the following instructions will only work if you use one.
-If at any point you get the android guy with an orange exclamation point during boot...it is probably ok, just let it sit there for a couple minutes. it should continue to boot into whatever ROM you are currently on. Make sure you enable usb debugging in settings after boot.
-to access RSD, Recovery, or Fastboot mode, press and hold your power button to start the Xoom booting. When you see the Motorola logo, wait a second then press the volume down button. Then you can use volume down again to cycle through your options, and use volume up to choose one.
-the exact differences between RSD / Fastboot and Recovery modes are beyond the scope of this post (and me) so just know that your Xoom can be modified using software on your PC via USB with RSD and Fastboot modes, and stock recovery can be replaced with modified versions to add more functionality. Recovery is used to do all sorts of things...flash Roms, mount drives, format, cleanup caches, etc.
***
General instructions. Just guidelines; you will probably need some previous experience with computers / rooting etc.
(If you are already unlocked, rooted, and have a replacement recovery, skip to the last step.)
1.) Follow this guide to prep your Xoom: (unlocking, rooting, and install CWM recovery)
http://www.xoomforums.com/forum/motorola-xoom-development/15179-how-rookie-rooting-flashing-unrooting-under-one-roof.html
Note: you may have heard of Lord AOI tool; it is supposedly designed to simply the above process. I found it didn't work well and was more difficult to use than good ol' adb commands. I recommend skipping it.
2.) OPTIONAL: Next, I recommend using the latest Rogue recovery. Just use standard CWM recovery to flash it. It is nice because it allows you to use the touchscreen to manipulate instead of having to use the hardware buttons (volume buttons are kind of a pain). See here: http://forum.xda-developers.com/showthread.php?t=1235170
3.) Finally, flash the pre-rooted stock Jellybean ROM. See here: http://forum.xda-developers.com/showthread.php?t=1796335
(here's the direct ROM link for those not needing instructions or extra info: http://www.mediafire.com/?7w5w65l66hgggo8 )
Good luck and let us know your results...