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
Related
So I want to do the new sw update but can't because I deleted some stock apps so the checksum wouldn't match and a hard reset won't restore them I guess so I would flash a stock rom but am I right thinking there isn't one yet? So how can I get to an original rom and then update or maybe make the new update work?
D2G stock rom
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
@evil yeah im kind of in the same boat, let me know if srensber solution works for you.
I froze a bunch of apps with Titanium Backup and renamed some stuff with Root Explorer. I recently just re-named everything i changed back to the factory stuff (bak -> apk) but it still doesnt seem to do any good.
I did create a number of back ups using Rom manager but i cant seem to find out where they are located and how to restore them. hmm. Not sure what to do.
Ah i realize what ive done wrong ... i didnt know you had to have bootstrap installed along with clockwork recoveryy in order to make a backup hmm. Going to need a rom of stock d2g lol.
clockwork recovery installs a boot hijack, which might be the culpirt
srensber said:
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
Click to expand...
Click to collapse
I cant seem to find the download link anywhere... and after you loaded this rom did you try to update to 2.4.3 ?
If anyone else has any input about this please help!
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
boardsportsrule said:
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
Click to expand...
Click to collapse
Find the modem cognition uses that gives you the least problems. Are you flashing to stock before each ROM?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yep, back to stock & master cleared between(only once problems arised..back in the day I could just flash to what I wanted and never really had a problem. Went back to stock once when the new flash responded strangely.)
Looking at cognition, I get minimal information, I THINK it's stock radio/kernel..
http://forum.xda-developers.com/showthread.php?t=912657
Any one???
I would..check your usb plug/cable/port first..make sure it isn't bad and effecting your data transfer..Make sure your not plugged into a external port and plug into PC directly..
Re down load your roms and kernels again..keep them separate from what you have already used..
Flash back to stock..master clear delete all data on your internal and your data
Re-install everything over again..cause it sounds like something got corrupted along the way
Mac
Mac11700 said:
it sounds like something got corrupted along the way
Click to expand...
Click to collapse
Thats how I am leaning, but i dont think it's with the roms/kernels/radios i have downloaded...since I have tried so many damn copies that wouldn't make sense. also tried downloading directly to phone, eliminating the "3rd party" computer, and have used drop box in the past...
I have flashed to stock and master cleared, i could do it again, but i am tempted to go back to stock and try to exchange it for a new one due to either random shut-offs or GPS(both of which mine are effected by..) but i would like to avoid this hassle...
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
boardsportsrule said:
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
Click to expand...
Click to collapse
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
opcow said:
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
Click to expand...
Click to collapse
hopped back to Stock... Gonna run things here, see which problems arise, and go from there. Can you flash a different kernel onto the stock ROM? I'd assume you need a 2.1 kernel, and i don't think many are retrofitted to 2.1, but the KP1 modem is a good idea, ill let things pan out on stock and see what happens if/when i flash kp1 modem.
funny fact: fire fly made problems for me... it's based on rogers 2.2, same as cognition. that seemed odd to me.
I am sending my phone back into samsung for repair, and I want to bring it back to its stock condition. I have unlocked the bootloader, flashed CW recovery, and installed superuser with no problems, however cannot seem to figure how to go into reverse. I understand how to re-lock the bootloader. I have read on the forums through the countless amounts of people asking this. I am however trying to use the ROM for the GTJ61 build found from this thread http://forum.xda-developers.com/showthread.php?p=13478981 When I try to use Clockwork Recovery, and go to restore, it states there is a MD5 mismatch. Am I suppose to install from zip or update from SD with CWR, or should I try to flash everything back onto there? I do not know what to do. Am I even trying to use the right ROM? The GTJ61 build is the original build that came on my phone, but would another one work?
follow this thread http://forum.xda-developers.com/showthread.php?t=1033269
all you have to do is clear your data, flash the stock rom and stock recovery, and then lock the bootloader
Thank you very much. I figured it out. All I have to do now is destroy the evidence on my sd and seen my NS away.
I realize superuser is still alive and well after I did everything. How I would I get rid of it?
I just uninstalled it. it might have gotten restored when you logged in with your gmail account. did you wipe data and the cache with cwm before you flashed the rom?
edit: did the ots update to 2.3.4 install fine for you?
I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.
SleepyFox said:
I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.
Click to expand...
Click to collapse
I did mean ota lol. my bad. where'd you get a 2.3.4 rom from?
edit: if you used the 2.3.4 rom from the thread you posted, just be aware that it isn't official. i'm not sure if the link I posted has the official rom, but you can download OTA updates with it so I would assume that it's pretty damn official lol
I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?
SleepyFox said:
I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?
Click to expand...
Click to collapse
I don't know much about it either, but I would assume that you should put it on a stock rom if you're sending it back into samsung. I could be totally wrong though
I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.
SleepyFox said:
I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.
Click to expand...
Click to collapse
I would guess that superuser would be one of the first things they check for to see if you broke warranty. you could just uninstall it and wipe everything through cwm again to make sure it's gone
I managed to fix everything. I just was searching through the system folder of the 2.3.4 rom and to my surprise there was little old superuser. So I deleted the .apk and bin files. After that I restored the ROM. Fixed everything. The stress of sending in a phone with superuser is gone and I am back to being stocked
Two questions for you OP:
1. How do you have a warranty on a I9020A? Is it the subsidized version from Best Buy (i.e. "AT&T's sanctioned model")
2. Why do you need warranty repair? What broke?
Yes I got my phone from best buy. I just registered the imei with samsung and I am under the 1 year warranty. I have a problem with my battery draining 80% in 6 hours little to no use with all radios besides 2g turned off. I know that the NS has not so stellar battery life, but there is genuinely a problem with mine. It cannot even survive for half a day.
Hmm, I had that very issue with three past i9020a's (two from Amazon, one white one from Newegg). They were all the Rogers model, which is said to be identical to the one Best Buy is selling as a subsidized model.
I just bought another i9020a on eBay (no, I never learn) and hope to try some fancy methods to save on battery life (ROMs, etc). I also experienced VERY slow 3G with the i9020a on AT&T's 3G network here in the US. Like 300kbs download slow. I read that if you flash the radio to KB3 it gets very fast, like HSPA 3G should be.
I don't care about rooting and flashing because my phone will not have a warranty. I do, however, suspect that there is nothing wrong with your phone, rather the battery life is just random. One of the i9020a models I had drained a fresh charge in like 3 hrs of sitting idle w/full bars. The phone was burning hot. I restarted it, charged it up, and it lasted over 16 hrs the next time. Very erratic and strange, but that seems to be par for the course with the NS.
I would first see if the phones you bought were registered yet. You never know when you would need samsung to take care of something for you. The correct radio for the US ATT is UCKE1. You should be getting data speeds of about 3.3 megabits. My battery has been consistently low.
SleepyFox said:
The correct radio for the US ATT is UCKE1.
Click to expand...
Click to collapse
So that may explain what's different between the international (i.e. Canadian) I9020A and the "Best Buy" AT&T sanctioned I9020A...a different radio?
Is it possible to flash the KB1 radio of the Canadian I9020A to the AT&T friendly UCKE1 radio?
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Some notes:
I was the the newest CWM Recovery Version
I checked all the MD5 and they all aligned perfectly
Thanks for any help I receive, if you want to know something else about my phone data during this procedure, just let me know.
so you flashed back to.33 or .608 before you flash cm9?
Sent from my DROID2 GLOBAL using xda premium
odnanreh12 said:
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Click to expand...
Click to collapse
Hexen was made for 2.4.x stock firmware (Android 2.2 and the corresponding Motorola kernel).
All newer ROMs (CM7, CM9, Gummy, Apex, etc.) are based on 4.5.x. Update to 4.5.608 (preferably via SBF; do NOT accept any OTA updates once you're on 4.5.608) and proceed from there.
Ah thanks so much, I forgot that Android Firmware numbers had to match up, I will try again later tonight
forgot that Android Firmware numbers had to match up,
Click to expand...
Click to collapse
just fyi, not android firmware, moto's system version/firmware
Firmware must be watched
Sent from my GT-I9001 using xda premium
I have come to the conclusion that something is wrong with my phone. I have tried to install ICS....a lot. I am not exagerating when I say that I have tried every Odin install, and every ICS ROM that has more than a few positive results. Nothing will work. I am not new to flashing, I have had a Captivate, Inspire, Tab and have had no issues with those, even created a few themes and build.prop tweaks. I know what I am doing and I follow the OP instructions perfectly. The damn thing just wont take. I get the white Samsung screen, a black screen, a vibration, and a reboot. So at this point I think I am just going to stick with GB for right now and hope that either the offcial ICS update works (when available) or maybe 5.0 later this year.
Two weeks of try to make this work has run me ragged. Outside of the ICS issues though this is by far the best device I have had in terms of performance and reliablility.
Rant over.
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
icenight89 said:
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
Click to expand...
Click to collapse
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
mahausrath said:
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
Click to expand...
Click to collapse
I will give it a shot. I would really like to get back to ICS, I got so used to it on my other phones.
I have been using superuser, haven't had a problem yet from that.
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
^^^ this makes sense. Also I was asking about the note radio to advise u against it, or u may end up screwing up ur phone even worse, and have to make a visit to my corrupt efs fix thread lol.
hcyplr29 said:
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
Click to expand...
Click to collapse
I will try to get a different download, but I do not think that is it. The only reason I say that is because my phone had the exact same response for EVERY ROM I have download. They can't all be bad files. I have tried on two different PCs with three different USB cables. Good thought though, I have had bad downloads before. I am going to keep trying as the ROMs are updated and hope that I figure out what is going on, and hope that I can get the official update at some point. Then I will just root it and get rid of the bloat myself if I have to
I am going to stay away from the L5 radio, not worth the hassle.
On a side note, if installing a rom from the site, remember, most will work with the "base"
But need to reset/full boot before "updating".. dont just flash rom and flash update then reboot
I had a hard time with ICS as well with different problems, all I can say is it disproves the definition of insanity. Trying the same things over and over again will eventually make it work!
Hang in there, it's worth it. Whenever you do get the ODIN one click to work I highly recommend flashing Raider03's SMOOTHIE ROM. Awesome battery life and extremely "SMOOTH"! But be prepared for a few FCs and bugs with all of the ICS ROMS for now!