Related
Hey everyone! I hate to take up another thread but i like to be as sure as possible when it comes to messing with ODIN, since from what i understand that is where most people have likely bricked their phone.
Currently im running sonofskywalkers 2.3 rom i believe with DI01. I want to update to the newest one, which from what i understand means i need to upgrade to DL09.
My question is they say not to flash 01 stuff to over 09, so do i need to completely revert back to stock to push the new stuff since the rom i am running currently is for 01. Or am i safe to go ahead and update the radio and stuff, and boot up and get into rom manager to download the newest rom?
Thanks for your patience community and quick and helpful responses.
You are fine flashing over what you have, the issues mainly come up when you don't flash all the parts together (ROM, kernel, modem).
As far as Odin goes, as long as you use the PDA function, and not the PHONE function, you will be fine.
Edit: BTW, are you running a voodoo kernel? If so, that needs to be disabled before proceeding
For one, make sure voodoo is disabled if its on your kernal. If thats okay, then I would just odin this and then try to find a root method that would work. Or instead of rooting your stock, just flash a rooted rom onto your phone after the full odin.
BTW if you do want to keep stock, know that it can be a pain to get root to work. For some people it can be annoyingly hard, while others are able to use something simple such as the one click root. I was able to get one click to work, but it varies. If something goes wrong, you can always just re-odin the full package again.
I thought i might add here that you mentioned reading not to flash di01 stuff over dl09.
What that means is after you odin the dl09 upgrade you should no longer flash roms, kernels, themes and such that are not dl09. Flashing a di01 kernel would not work once you upgrade to dl09.
Hope this helps.
Have fun
Sent from my dl09 fascinate through xda app.
OK I have spent about 2 weeks now looking through roms, kernels, root methods etc etc.
I have come to one conclusion. IT SUCKS owning a Verizon tab on this forum.
Most of the guides are accurate, but often miss one little detail that anyone who knows this stuff would think "duh" about, but a noob will miss, and end up reflashing stock from heimdall 10 times over because of.
Long story short, I would like to see a Verizon guide here on the development section that is kept up to date and has proper links to working roms as well as IDIOT PROOF walk throughs.
I would be willing to do this, or someone else can, I do not care. I will edit this very post so that it can serve said purpose if it gets made a sticky, or added to a sticky thread.
In this spirit I will later edit this post but I have a few questions/requests first.
1. I have never had the need to host files for large numbers. I use my own server to host things, but I know I cannot do that for this. Can someone PM me with what would be the best method to host files for people (IE It seems one service somewhere will add links through direct downloads, Megaupdload, Rapidshare etc at the same time).
2. Correct me if I am wrong. Heimdall seems to be the best root method. Heimdall + the ec02 files = the most stable and fully robust and stable rom for the VSTG (Verizon SGT).
3. The Verizon SGT Bootstrapper will convert to Ext4 and add CWM, but results in a broken camera and rotation, the latter of which I have a fix for, but not the camera. Dos any other way of adding CWM work better?
4. Sprint has a completely working update to GB, that works on the VSGT as well, minus radio function. I read somewhere what steps had to be taken to get the 3g radio working as well, but have since not been able to find it. If someone who reads this knows, could you please post or PM me where to begin fixing the radio on the sprint rom to work with the VSGT?
Morkai Almandragon said:
3. The Verizon SGT Bootstrapper will convert to Ext4 and add CWM, but results in a broken camera and rotation, the latter of which I have a fix for, but not the camera.
Click to expand...
Click to collapse
Please tell me how you fixed the rotation? I can deal with no camera, the one in my phone is better anyway.
I am not the greatest help in the world....but have a VSGT and will help where i can.
Sent from my SCH-I510 using XDA Premium App
mnpolock said:
I am not the greatest help in the world....but have a VSGT and will help where i can.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8
There is the thread that will fix the rotation bug... Now if I can get the camera working... LoL
Oditius said:
http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8
There is the thread that will fix the rotation bug... Now if I can get the camera working... LoL
Click to expand...
Click to collapse
Do not run a kernel that requires Ext4 and both work perfectly.
IE use Heimdall and install the ec02 firmware, then stop. Everything seems to work, without any fix required.
Morkai Almandragon said:
Do not run a kernel that requires Ext4 and both work perfectly.
IE use Heimdall and install the ec02 firmware, then stop. Everything seems to work, without any fix required.
Click to expand...
Click to collapse
Man, I wish I spoke french... Because that is what the above looks like to me. My camera doesn't work, and I didn't do anything but root it, and install that Verizon Bootstrapper. Well at least the rotation works, still don't know what to do about the camera.
I used the verizon bootstrapper after restoring to completely stock ec02 and rooting with super one click. Then used heimdall to flash psirens kernel and then flash psirens rc 2.5. From here http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw
and my camera and rotation work great after replacing the sensors.so file to fix rotation. Currently I am overclocked to 1.4ghz with voltage control and all is running flawlessly and fast.
ticklemegavin said:
I used the verizon bootstrapper after restoring to completely stock ec02 and rooting with super one click. Then used heimdall to flash psirens kernel and then flash psirens rc 2.5. From here http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw
and my camera and rotation work great after replacing the sensors.so file to fix rotation. Currently I am overclocked to 1.4ghz with voltage control and all is running flawlessly and fast.
Click to expand...
Click to collapse
How exactly did you install the kernel and rom? can you post a step by step
?
Morkai Almandragon said:
How exactly did you install the kernel and rom? can you post a step by step
?
Click to expand...
Click to collapse
Step by step and with links on everything that you need. Written so easy to understand so a person with no experience can knock it off with no problem.
Me, I'm on a stock but rooted VSGT, and I'm fine with it really. Only thing I do wish for is a 2.3 update from VZW. I don't care about OC'ing, Tab is very snappy enough for me and battery life is very good.
I looked into flashing the Sprint update but thought against it because I need 3g.
Recently got a Nexus S4G and running MIUI on it, and boy, I wish we could get a MIUI port on our tab. Those guys are just dang good and crazy.
Sent from my SCH-I800 using Tapatalk
Ok here is what I did.
1. Get the stock un-rooted un-updated firmware from here http://forum.xda-developers.com/showthread.php?t=1136587&highlight=verizon
2. Follow this guide to flash the files you got in step 1 http://forum.xda-developers.com/showthread.php?t=967175&highlight=verizon+stock+firmware
3. After you have flashed back to stock and booted up into android then update through android to ec02.
4. Download super one click from here http://forum.xda-developers.com/showthread.php?t=803682 and follow the instructions on that page.
5. You now should be rooted. Now download the verizon bootstrapper off the market and run it.
6. After that has completed download the rom/kernal and follow the instructions on this page http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw.
7. Alright now you should be rooted with a custom kernal and rom installed your camera should work. If your rotation doesn't work then get the sensors.default.so from here http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8 and follow the guide.
That's exactly what I did and my camera/rotation work fine.
If you want to overclock use voltage control from the market.
So, I have to go back to square one, where I started. and do everything all over again?
The use SOC to root it.
Then run the program that knocked out my camera/rotation again.
So I will be right back where I am now.
Then I have to update the kernel.
Then install a new rom.
And it should work.
OK, thanks...
Never mind, if I go back to square one, I will just stop and not go any farther. My GT was fast enough without doing all that. So I will wait, maybe someone will come up with a fix for the camera that was as easy to fix as the rotation. I don't video chat and my Mesmerize has a better camera and easier to use.
Yes that is what i did after trying to flash a voodoo kernel and getting stuck at the Samsung logo many times. I flashed back to stock and started over. Not sure when the camera started working in the process, I had checked after everything was installed. Also im not sure if psirens rom even flashed or not because everything looked exactly the same and still had the Verizon bloatware installed which I just removed with titanium backup. Im not sure if i have ext4 or not would there be a way to check?
The thing is I never flashed the voodoo kernel. I rooted the GT last week. Yesterday I was reading around, obviously not as well or completely as I should have. But I was going to flash a new rom and it stated I had to do the Bootstrapped first. So I downloaded it and that was when all heck broke loose. I read later on in the thread that the camera stopped working and so did the rotation. Well the rotation had a fix, but the camera doesn't. Oh well, I will keep looking, maybe if I just start at #6 because that is where I stopped.
ok What I am finding is this. Flashing the EC02 files through Heimdall result in a rooted Froyo rom that runs stable and decent, but without CWM.
You can then use the Verizon Bootstrapper on the market which flashes a new kernel that includes CWM. The new kernel breaks the camera and rotation though. Flash the better than life kernel and camera is fixed, followed by the rotation fix and you are now back to close to stock with root, and CWM...
Here is where I lose my way though. The Psirens rom looks JUST like the EC02 Heimdall install I have. I will post the files I am using once I get a host I am happy with.
Morkai Almandragon said:
ok What I am finding is this. Flashing the EC02 files through Heimdall result in a rooted Froyo rom that runs stable and decent, but without CWM.
You can then use the Verizon Bootstrapper on the market which flashes a new kernel that includes CWM. The new kernel breaks the camera and rotation though. Flash the better than life kernel and camera is fixed, followed by the rotation fix and you are now back to close to stock with root, and CWM...
Here is where I lose my way though. The Psirens rom looks JUST like the EC02 Heimdall install I have. I will post the files I am using once I get a host I am happy with.
Click to expand...
Click to collapse
This is exactly what I think except that the ec02 files I linked will take you back to full unrooted stock where as the files from the tutorial for flashing ec02 I linked will leave it rooted but with stock ec02. I also cannot tell a difference between stock ec02 and psirens ec02 they look exactly the same. I almost wonder if cwm is not flashing the rom correctly. But even if it didn't you get a stable ec02 experience with a overclockable kernel which is all I was really looking for in the first place. I also could not get the voodoo kernal to work period I flashed it several times and always got stuck at the samsung screen on boot. My tab is much faster now and im pretty happy with it. Now if we could just get a stable gingerbread or maybe even honeycomb ill be all over that.
http://forum.xda-developers.com/showthread.php?t=1178414
Just saw this after my last post, looks like we will have gingerbread with working 3g (which I require) very soon. So we should be seeing some performance improvements whenever we get gingerbread.
If you guys want a stock ROM, converted to ext4, just ODIN Boushh's kernel then (if you're on the newest VZW update EC02) replace the file in that thread that fixes auto rotation.
Coolsaber57 said:
If you guys want a stock ROM, converted to ext4, just ODIN Boushh's kernel then (if you're on the newest VZW update EC02) replace the file in that thread that fixes auto rotation.
Click to expand...
Click to collapse
Boushh's kernel will not work for me I always get stuck at the samsung boot screen. Im flashing with heimdall though because I only use linux and i do not think there is a version of odin for linux.
Really odd timing for this one, for me personally anyway. I finally gave up waiting yesterday and tried to install CM7 and bricked my phone. Panicked for a while, then finally figured out forcing download mode with VOLUP+VOLDOWN, connected to USB, while inserting the battery!
Anyway... it's now on Kies for Telus Fascinate. I was hoping this would finally fix GPS, but it's somehow made it completely unusable for me. 0 satellites after several minutes of looking.
Firmware version 2-3-3
Baseband version 2-6-35-7-T959TLKG2
Kernel version 2-6-35-7-T959TLKG2
sj0829-kwon-SEP-08 #2
Build number GINGERBREAD-LKG2
^^^ had to replace decimals with hyphens to appease the "no links posted by newbies" forum rule.
Also, superoneclick can't root this one. Other options?
UPDATE: Root instructions here - [Telus Only][How-To] Root your Fascinate Gingerbread 2.3.3 T959TLKG2
tenthousandfeet said:
Also, superoneclick can't root this one. Other options?
Click to expand...
Click to collapse
I tried flashing Semaphore 1.5 - which is an i9000 kernel for stock JVR - and it wouldn't boot. Went back to LKG2 un-rooted for now.
I'm tempted to try CF-root for the i9000s, but given my recent bricking(s) I'm a bit tired of flashing back to 2.2. Anyone else care to try?
Though it wouldn't necessarily help with root - do you suppose zacharias.maladroit's Neo kernel would work with stock Gingerbread? Supposedly for CM7, but Gingerbread seems close enough.
tenthousandfeet said:
I'm tempted to try CF-root for the i9000s, but given my recent bricking(s) I'm a bit tired of flashing back to 2.2. Anyone else care to try?
Though it wouldn't necessarily help with root - do you suppose zacharias.maladroit's Neo kernel would work with stock Gingerbread? Supposedly for CM7, but Gingerbread seems close enough.
Click to expand...
Click to collapse
so did u try it after?
Trying to root my Girlfriends phone, unfortunately, the gingerbreak exploit has been closed and the 3e recovery won't install unsigned ZIP files.
None of the custom kernels flashable through odin are going to work properly either. you will either end up with an unbootable device, or wonky buttons.
I'm not going to try anything until an odin flashable of the stock kernel is available.
Things like this make me glad I moved my personal phone to the the Nexus lineup.
I guess we wait for the next exploit to be found
Most people who try to install this are getting errors as soon as kies tries to update the phone, where it instantly shuts down and reports numerous signature errors.
Add that you can't root and I think it's borked all around. Thanks for nothing Telus.
harjon said:
Most people who try to install this are getting errors as soon as kies tries, where it instantly shuts down and reports numerous signature errors.
I think it's borked all around. Thanks for nothing Telus.
Click to expand...
Click to collapse
why blame Telus? It is samsungs fault.
Sent from my Nexus S
harjon said:
Most people who try to install this are getting errors as soon as kies tries to update the phone, where it instantly shuts down and reports numerous signature errors.
Add that you can't root and I think it's borked all around. Thanks for nothing Telus.
Click to expand...
Click to collapse
I installed this update yesterday with no problems. Then I tried a rooted i9000 kernel which didn't work, so I had to flash back to 2.2 and update AGAIN via Kies. No problems.
Matridom said:
None of the custom kernels flashable through odin are going to work properly either. you will either end up with an unbootable device, or wonky buttons.
I'm not going to try anything until an odin flashable of the stock kernel is available.
Click to expand...
Click to collapse
The CF-root kernel link I posted earlier should theoretically work, as long as it's bootable. The kernel applies root, which remains even if another kernel is flashed. If it's bootable with wonky buttons then we could then flash another kernel to fix the button mappings. The problem, of course, is that there are no 2.3.3 kernels for the Telus Fascinate, except zacharias.maladroit's Platypus Neo (linked above) which is designed for CM7/MIUI and may or may not play nice with stock Gingerbread.
As I said, I'm sick of reflashing to stock with no backup, so I'm opting out of trying this route. Anyone more adventurous care to give it a try?
tenthousandfeet said:
Really odd timing for this one, for me personally anyway. I finally gave up waiting yesterday and tried to install CM7.
Click to expand...
Click to collapse
Thats hilarious, I installed CM7 yesterday as well. I'm about to Odin back to stock and then update to see how this is. CM7 is a little bit to buggy for me atm.
Does this mean anything for verizon fascinate users?
uzumaki82 said:
Does this mean anything for verizon fascinate users?
Click to expand...
Click to collapse
Nope.
Sent from my Nexus S
Cool. Quick question, does an update through Kies do the Kernel and ROM together? And will a currently installed custom Kernel mess with the update? Thanks!
IronStomach said:
Cool. Quick question, does an update through Kies do the Kernel and ROM together? And will a currently installed custom Kernel mess with the update? Thanks!
Click to expand...
Click to collapse
Yes, the update will overwrite the current rom and firmware. As to your current kernel messing with the update, it depends, I used the stock kernel w/ voodoo and I could update. First I disabled lagfix and root just to be safe.
MrManiacNF said:
Yes, the update will overwrite the current rom and firmware. As to your current kernel messing with the update, it depends, I used the stock kernel w/ voodoo and I could update. First I disabled lagfix and root just to be safe.
Click to expand...
Click to collapse
You disable voodoo and unroot the phone before making the upgrade?
How did you disabled the voodoo and unroot the phone?
johnelway said:
You disable voodoo and unroot the phone before making the upgrade?
How did you disabled the voodoo and unroot the phone?
Click to expand...
Click to collapse
Boot into clockwork recovery (VOLUP+VOLDOWN held while powering on) and there will be a menu for Voodoo with an option to disable. It's probably a good idea to disable it, as everything I've read seems to indicate that new roms with voodoo enable may create problems.
As for root - I can't see that having any effect on flashing a Kies update, but there is an option in superoneclick to unroot.
tenthousandfeet said:
Boot into clockwork recovery (VOLUP+VOLDOWN held while powering on) and there will be a menu for Voodoo with an option to disable. It's probably a good idea to disable it, as everything I've read seems to indicate that new roms with voodoo enable may create problems.
As for root - I can't see that having any effect on flashing a Kies update, but there is an option in superoneclick to unroot.
Click to expand...
Click to collapse
I reflashed back to the stock 2.2 Kernel/ROM just to be safe, and so far the update's great, way faster than before even without Voodoo enabled.
Others are reporting issues with trying to root on 2.3 so I would leave it rooted.
tenthousandfeet said:
Boot into clockwork recovery (VOLUP+VOLDOWN held while powering on) and there will be a menu for Voodoo with an option to disable. It's probably a good idea to disable it, as everything I've read seems to indicate that new roms with voodoo enable may create problems.
As for root - I can't see that having any effect on flashing a Kies update, but there is an option in superoneclick to unroot.
Click to expand...
Click to collapse
Sent from my SGH-T959D using XDA App
I have 2.3 stock rooted, useing the speedmod kernel/stock kernel method on here. I ain't had any problems at all.
As for the speed of the rom, I agree. Its double the speed of froyo, and there is no voodoo. So I can't wait till there is a voodoo or somthing available, I would maybe have to tie it down.
Maniac
Does having a custom recovery mean your bootloader is unlocked? I have TRWP installed, in download mode it says samsung offical yada yada.
The boot loader is not unlocked. Do some more reading about your phone before you start doing something with your custom recovery. Many people have bricked their phones because they did not understand what they were doing. There is a lot of good advice here. Look for threads by axman, adamoutler,beerdriod, to name a few. They'll keep you out of trouble. Just some friendly advice
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
The boot loader is not unlocked. Do some more reading about your phone before you start doing something with your custom recovery. Many people have bricked their phones because they did not understand what they were doing. There is a lot of good advice here. Look for threads by axman, adamoutler,beerdriod, to name a few. They'll keep you out of trouble. Just some friendly advice
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
AdePower said:
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2292157
AdePower said:
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
Click to expand...
Click to collapse
The post above has a great link for you to research.
Basically, having a custom recovery means that you can flash roms that have had the loki patch applied to them or you can flash roms from similar hardware then flash a kernel that has been loki patched, or you can flash a rom from similar hardware using a recovery that has auto loki, or you can flash a rom from similar hardware and follow that by flashing loki-doki.zip.
Plenty of options, but if you have to ask, you shouldn't be flashing, Read the link above and everything else you can about loki and the att i337. Making a mistake with a brand new cellphone can be costly so research is imperative.
Not trying to discourage you from trying a custom rom, just trying to let you know that there's a lot of information you should have first.
acruxksa said:
The post above has a great link for you to research.
Basically, having a custom recovery means that you can flash roms that have had the loki patch applied to them or you can flash roms from similar hardware then flash a kernel that has been loki patched, or you can flash a rom from similar hardware using a recovery that has auto loki, or you can flash a rom from similar hardware and follow that by flashing loki-doki.zip.
Plenty of options, but if you have to ask, you shouldn't be flashing, Read the link above and everything else you can about loki and the att i337. Making a mistake with a brand new cellphone can be costly so research is imperative.
Not trying to discourage you from trying a custom rom, just trying to let you know that there's a lot of information you should have first.
Click to expand...
Click to collapse
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
AdePower said:
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
Click to expand...
Click to collapse
Once you get the hang of it, it's not that difficult. It's just slightly different than flashing with an unlocked boot loader. The main difference it that whatever you flash has to have a kernel with the loki patch applied before rebooting out of recovery. The patch can be applied to the roms kernel before you flash, it can be applied to the roms kernel by the recovery you use to flash, it can be applied by flashing a loki patched kernel after flashing the rom, or it can be applied by flashing loki-doki after flashing the rom.
The roms come from identical snapdragon 600 equipped S4's, not the octa-core models and you apply the loki patch as needed with one of the methods above.
essentially it's an extra step in the process with several different places you can put it.
If you've flashed other roms, it won't take too much reading before you get the hang of it, but it's still best to put a little time into research before pulling the trigger.
acruxksa said:
Once you get the hang of it, it's not that difficult. It's just slightly different than flashing with an unlocked boot loader. The main difference it that whatever you flash has to have a kernel with the loki patch applied before rebooting out of recovery. The patch can be applied to the roms kernel before you flash, it can be applied to the roms kernel by the recovery you use to flash, it can be applied by flashing a loki patched kernel after flashing the rom, or it can be applied by flashing loki-doki after flashing the rom.
The roms come from identical snapdragon 600 equipped S4's, not the octa-core models and you apply the loki patch as needed with one of the methods above.
essentially it's an extra step in the process with several different places you can put it.
If you've flashed other roms, it won't take too much reading before you get the hang of it, but it's still best to put a little time into research before pulling the trigger.
Click to expand...
Click to collapse
So the best option would be the recovery that applies the patch automatically correct?
AdePower said:
So the best option would be the recovery that applies the patch automatically correct?
Click to expand...
Click to collapse
It is the easiest way yes.
AdePower said:
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
Click to expand...
Click to collapse
It is easier than the HD2, I had that phone, and it was a nightmare to flash, it is not confusing, I give a STEP BY STEP in my guide, how easy is it...
5 step flash process...I don't get it, HOW HARD CAN IT BE?
here is an example...
1 - get a bowl
2 - open the box of cereal
3 - pour cereal in bowl
4 - add milk to cereal
5 - eat cereal and enjoy
it is NO DIFFERENT than that. If you can do that, you can flash roms.
go here, if you can't do this, then you need to keep your phone stock forever.
http://forum.xda-developers.com/showthread.php?t=2295557
I will help you, although, I can't flash it for you, you must pay attention.
good luck sir.
TheAxman said:
It is easier than the HD2, I had that phone, and it was a nightmare to flash, it is not confusing, I give a STEP BY STEP in my guide, how easy is it...
5 step flash process...I don't get it, HOW HARD CAN IT BE?
here is an example...
1 - get a bowl
2 - open the box of cereal
3 - pour cereal in bowl
4 - add milk to cereal
5 - eat cereal and enjoy
it is NO DIFFERENT than that. If you can do that, you can flash roms.
...
Click to expand...
Click to collapse
I've tried this, but all I get is cereal. I've repeated it exactly as written like 15 times and I think I going to be sick.
I am confused to why everyone has this problem, it is crazy. I am like you, it is embedded into my brain, my wife had to wake me up one time, because she said I kept saying flash it, flash it, over and over. Oh well.
I have seen some people, they don't like going through all the posts to find an answer, back in my early days they included a new feature called BOOKMARKS...I ask myself, what does that do...hmm it takes me to places that I have been before, that dare I say...dare dare.. explain what to do so I could reference back.
Not a Dev, but not a Noob, either. Formerly had a SGH-i897 Galaxy S for 3 years and flashed like crazy on it, while transitioning from Eclair to Froyo to Gingerbread to ICS to Jellybean, mostly using the fine offerings from the AOCP Collective folks. While familiar with Odin, CWM was my usual go-to utility.
Upgraded recently to a SGH-i337 Galaxy S4. Must have owned it for two, maybe three hours, before I rooted it with MotoChopper. This allowed me to re-install Titanium Backup. I left it as merely rooted, while I read up on CWM and some new-fangled thing called TWRP, which I wanted to get installed before casting about for a new ROM. (At the time, AOCP did not have an offering here, or it would have been a no-brainer for me.)
One morning, I turned on the phone and noticed it was doing an OTA update. . . . . . . . .
Mildly curious, I logged onto XDA to read what the community thought about the update, only to discover that I had missed all the dire warnings by a day and my (now) version I337UCUAMF3 ROM had it's boot-loaders locked from a blown Q-Fuse, courtesy of Samsung and AT&T.
Took me a week before I found the rooting solution from jortex, but thankfully, I'm now rooted again.
This background now leads to my questions:
I have ROM Manager Premium (from previous purchase) but have not installed it.
I was aware on my previous SGH-i897 that mixing the Gingerbread and Jellybean boot loaders was like, a Bad Thing when flashing ROMs and would promptly brick the phone.
Does CWM require the ability to load from a boot loader?
I know it creates an update.zip file to restore the original ROM, and usually does so by using whatever ROM is installed at the time.
So wouldn't it just create an update based on the I337UCUAMF3 ROM?
Even if I can't flash new ROMs (unless or until somebody comes up with a Q-Fuse Fix) couldn't I at least have all the recovery and .zip flashing of apps and cache clearing menu choices available to me from CWM?
Or would the act of just installing CWM on a I337UCUAMF3 ROM immediately brick my phone?
In Other Words, how close can I dance to the water's edge?
Been to the ROM Manager web site and they claim I can do any thing at any time.
(Easy for them to say: It ain't THEIR phones!)
Been searching these threads and can't come up with anything explicitly stating yea or nay.
So far, I have been happy enough with the TW stock ROM, but I always felt better being able to boot to recovery to fix things, on those few occasions I got just a leeeeeetle too close to the Bleeding Edge!
What is the consensus out there?
Will CWM 6.0.3.6 bork a I337UCUAMF3? Yes or no?
Would appreciate any thoughts that might enlighten me! :fingers-crossed:
It sure could brick the phone, the only thing you can do at the moment is root. I have seen a couple people try running a recovery on it, and it required a jtag service to restore the device.
Be careful.
TheAxman said:
It sure could brick the phone, the only thing you can do at the moment is root. I have seen a couple people try running a recovery on it, and it required a jtag service to restore the device.
Be careful.
Click to expand...
Click to collapse
Appreciate the response!
This phone is far different from the Captivate. There is no flashing anything on MF3. Basically you are waiting for a work around if that is even possible.
Sent from my SGH-I337 using xda premium