So im looking at the instructions here: http://forum.xda-developers.com/showthread.php?t=1029436 and i have a few questions.
I suggests that you follow those steps to the T to avoid boot loops, but if already have red CWM and an eb01 build can i just flash the kernel and rom then odin the radio? I shouldnt have to follow the whole odin back to eb01 stock, flash cwm, etc should i?
And if i dont odin the new ec01 radio am i going to have any problems? Other than my cell reception not being as good as it could be of course
Short answer is probably.
You can follow any steps that you choose, but if things go wrong, and you go asking for help, everyone will tell you to start over and follow the directions. If you read through that thread, you'll see that a lot of people took different paths and had mixed results. Personally, I followed Gizmo's directions and had zero issues. I hadn't done a full wipe in ages, so I figured that I was due.
I'd recommend doing a backup and give it a try. Worst case is you start back with the full wipe. I'd do the radio as people tend to have issues when mixing ROM's with wrong radios (like texting wierdness).
A question you say?
Anyway, you can try to do anything you want. The instructions are there for a reason. Some people had issues when flashing EC01 with other kernels and setups. So, this is a tested and nearly guaranteed way for it to work without further hassles or troubleshooting.
You can try to flash it as is....and if it doesn't work you can always Odin back and then follow the steps. Your phone isn't going to blow up or anything if that's what you are asking.
EDIT: Got ninja'd but yeah. Worst case is it doesn't work, you Odin back to EB01, and then follow the steps.
thanks a bunch. im just going to try to flash the kernel/rom first. worst comes to worst i just have to follow those directions anyways so i guess there isnt anything to lose.
Related
What is the best Kernel to use for this package, I was thinking TW Kernel 0327-2, which seems to be a fav of everyone in the thread. What are your thoughts on this and who is willing to walk me through my first root, to get this up and running? I am willing to Paypal some cash to anyone who successfully gets me up and running with my new phone(with a successful root). My Fascinate will be here in a few hours, new, so it will be fresh for a root. I'd rather not risk bricking it on its first day in existence.
Thanks in advance.
If you're going to be rooting I would first read up a little bit more on the whole subject of rooting and flashing. To make sure you're really committed to this.
I would start here and read this over a few times.
http://forum.xda-developers.com/showthread.php?t=948722
This is an EB01 Walk through (which still applies to EC10 and so forth)
One thing I have learned is that it is nearly impossible to brick your phone. You will soft brick it, many many many time because we are all curious and skip steps because we are excited.
The only thing to really remember is to NOT FLASH CWR (clock work recovery) 3.x.x. There are to many issues and incompatibilities at the moment with it. Unless the dev of your ROM says explicitly to use the new CWR, do not install or use it.
Go be brave and try it for yourself first, we are all here to help you get it back
Thanks, man. Will try. What Kernel are you using? Nameless V4 doesnt have one built in.
jt's 0408 (-25 undervolt) isn't a bad place to start. I'm on imnuts -50, which most phones should be able to handle (but not all).
Hey, im new here, and completely new to the whole "custom rom flashing" thing.
I would like to get into rooting my phone and then installing a custom rom like resurrection for example, but I have a couple of questions.
1. Do I need an SD card in my phone, to be able to root my phone/install custom roms? or can I just use the phones internal 16gb memory?
2. Would someone be kind enough to point me to a guide to rooting/installing custom roms for complete newbies like myself? I have searched the forums, but theres so many threads about different stuff, like clockworkmod/odin/cyanogenmod etc, my head is completely boggled. I just don't know where to begin with any of it.
Cheers.
1) No.
2) Everything you need to know is in the Stickies.
MistahBungle said:
1) No.
2) Everything you need to know is in the Stickies.
Click to expand...
Click to collapse
1. No you cant root without an SD card? or No you don't need an SD card? elaborate please.
2. Nothing in that thread helps someone like me who is totally new. I don't know what any of it means. Surely there is a simple guide that explains exactly how to root your phone, without linking you to 7 other threads in the process? That's all I've found up until now.
This requires sdcard
http://forum.xda-developers.com/showthread.php?t=1501719
This doesn't
http://forum.xda-developers.com/showthread.php?t=1103399
Thanks, thats what I was looking for.
One more thing, just so I dont make a mistake, could you tell me which kernel to download? my kernel version is 3.0.15-I9100BVLPB-CL310231
cheers.
Read the bit in bold read which says 'Help ! Which file do I use ?'. This short section answers your question exactly.
ok well i tried CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5-PROPER.zip and my phone no longer boots....
tried CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5.zip and I get the same thing, so im stuck now. great.
I can get into CWM recovery, but I have no idea how to copy the rom I want to use onto the phone when its in recovery mode. This is something that is just not explained anywhere
help?
Right. In order of importance:-
1) No bumping threads within 37 minutes. Not cool. This is not your personal tech support forum.
2) You're having problems. Why ? Who knows. We're not there looking over your shoulder so we have no idea exactly what you did. I suspect you're having problems because you are in too much of a hurry/took shortcuts & didn't do what was suggested immediately after your OP.
3) However...Given the situation you find yourself in, I recommend you do one of two things:-
A) If you are absolutely sure you have CWM Recovery & not Android recovery (I say this because if your phone isn't booting normally, that normally means the flash didn't work & normally CWM wouldn't be successfully installed either), follow whatever instructions the rom you're wanting to flash has.
Every single rom on here has flashing instructions, normally on the first post on the first page of the thread on here devoted to the rom. If you can't be bothered reading those, I can't help you.
or
B) Go to Samfirmware.com. Search for the firmware that was on your phone before you tried to root it. Download this firmware. Flash the firmware you download following the instructions here. If you also end up with a .dll file, bin it. You don't need it. This will give you a clean install of stock. From there, I strongly suggest you read the CFRoot thread very carefully before you attempt to root your phone again. I also strongly recommend you read the Stickies linked to above, so you have some sort of understanding around what's what with this phone.
If you don't, being a betting man, I'll wager there's a fair chance you'll find yourself in the situation you currently find yourself in again (best case scenario), or worst case you'll end up with a 135gm paperweight as many people have on here over the past few days.
It's all up to you now. Your phone's destiny is in your hands.
Thanks for the reply, much appreciated.
Sorry for bumping, I panicked a little when my phone wouldnt boot. I just expected it to work because I have done things like this in the past and never had problems. Im a pretty tech savvy person really, im just new to android.
I wish it was as simple as reading one thread, but there are dozens of different threads on how to root this phone, and different methods, its extremely confusing.
Im downloading the stock kernel now (300+mb for some reason, and its going to take over an hour to download)
Once I get my phone back to normal, I'll read through some more threads and try and get a better understanding on how to root my phone.
I had it rooted properly as the recovery mode stated CWM in the corner, I think the issue I had was not being able to copy the rom I wanted to use, onto the phone, because I dont have an SD card.
Anyway, thanks for the help, and fingers crossed I can at least get my phone to boot again.
Man, I've never come across anything so complicated in all my life lol.
Edit: Sorted! Flashed back to original kernel and its working as it was before I started. Thanks very much for your help mate, and at least now I know how to restore my phone if I mess it up again in the future.
just thought I would update this thread and say I finally accomplished what I wanted.
Incase anyone is wondering, this is what I did:
Restored my phone back to factory settings/firmware/kernel
Booted the phone up, and copied my rom of choice to the internal memory via USB connection, and enabled debug mode.
restarted in download mode and flashed cf-root kernel (ended up with bootloop)
went ahead and installed the rom via clockwork recovery (creating a backup first)
The phone now boots into the rom im using (Resurrection Remix)
So if anyone is a little worried by getting the bootloop (but can still get into clockwork recovery) try flashing your required rom. Your phone may boot fine with new rom anyway. Mine did.
Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.
Hello. I'm new here but, had an android for a couple years now. I have the tmobile samsung vibrant running 2.2 froyo. Can anyone tell me in detail how to install ICS on my phone? To be honest, I do not understand all the talk about odin and all that stuff. So if you can explain as if it were ICS for to Vibrant For Dummies that would be great lol. Explain in laymens terms please. Thanks
Peppino
Guess I'll post this again: http://m.youtube.com/watch?v=wMQQDpqVNBk
Everything in that video is not all correct. There are some specific parts that are left out.
OP, I understand you want to simplest way to go from 2.2 ->4.0 but in reality, you need to eventually know how to use Odin, or when you get stuck at a bootloop or your CWR gets corrupted, your next thread will be "Help, I brivked my phone".
Check my signature for the How to install ICS and above all, you need to read, read and then read some more (case in point, this was already answered here Trouble with my vibrant...).
Good luck and if you have any questions, use the search function and/or Google, as this phone has been around a long time and most questions have already been solved. If not, then just ask.
hi, It is always better to go ICS from the beginning.. which solves many problems. So in order to go back to stock you should use ODIN. It is very easy ONLY thing is DONT DISCONNECT USB connectivity while the process is running.
After that you will need some things.
ICS ROM to flash (try ICZen which works great )
GB Bootloader
CM7
update.zip (CWM) which can be found in woody's signature. [Installing ICS ROMs; A Vibrant Step-by-Step]
Once you are in stock 1st flash GB Bootloader through ODIN (DO NOT do anything until it is flashed)
then flash CM7 (GB ROM b/c its suggested to go ICS from GB rather than from 2.1)
then flash ICS ROM on top of it. initial boot will take up more time.
voilaa..!!!
Always do full wipe (data,cache,dalvik) in between flashes.
there are many ICS ROMs available .. READ instructions carefully.
Note: these steps are taken from threads I referred and followed by me.
LINKS
Click to expand...
Click to collapse
ODIN : http://forum.xda-developers.com/showthread.php?t=734475&highlight=odin
Bootloaders : http://forum.xda-developers.com/showthread.php?t=1117990&highlight=odin
ICZen : http://rootzwiki.com/topic/21742-romimm76i-iczen-185-fistful-of-zen-7-12-12-deficient-development/
edit: FYI it is better to uncheck auto reboot when flashing GB Bootloaders. and also I didn't checked re-partition when flashing to stock via ODIN
tc and all the best
I've been having some issues with constant reboots and phone signal strength after installing ICS. I have tried both methods (fastboot flashes and CWM flash) and still have the same problems.
Unfortunately, I'm a newbie, and was an idiot and did not create a backup.
I would like to be able to revert to the last stable official Gingerbread. Any recommendations on version to revert to? I'm been searching here for hours, and every time I think I find a good thread on how to do this, the links to the files are all dead.
Can someone please steer me in the right direction.
Also, again, I am willingly admitting that I'm an idiot for not making the backup in the first place. I saw that so many people were having no issues at all, so I assumed I would not either.
Thanks.
slim26 said:
I've been having some issues with constant reboots and phone signal strength after installing ICS. I have tried both methods (fastboot flashes and CWM flash) and still have the same problems.
Unfortunately, I'm a newbie, and was an idiot and did not create a backup.
I would like to be able to revert to the last stable official Gingerbread. Any recommendations on version to revert to? I'm been searching here for hours, and every time I think I find a good thread on how to do this, the links to the files are all dead.
Can someone please steer me in the right direction.
Also, again, I am willingly admitting that I'm an idiot for not making the backup in the first place. I saw that so many people were having no issues at all, so I assumed I would not either.
Thanks.
Click to expand...
Click to collapse
I recommend you the ROMs NottachTrix, it has Aroma installer and lets you configure it to your own taste. Guess this one is the best, if not you could go with a stock GB, search for fruitcakes (don't like them because the bloatware).
I'm assuming that you already have or know how to install a recovery. If it's not the case, let me know and I'll help you.
Thanks. I have CWM loaded so I shouldn't have an issue.
I think I would have the best luck with a stock ROM for now. The problem is finding a stock unlocked ROM for GB that still has a valid link. 90% of the links I'm coming across here including fruitcakes are all dead links.
http://samcripp.com/files/
you can find fruitcakes here. works from your phone or computer.
be sure to thank Sam Cripp for hosting the files for us. and the project in the first place.
Thanks. I was able to restore back to GB, but unfortunately still have the same signal strength issues.
have you tried to flash a new radio? there are plenty of radios on that website as well.