[Q] What would you do? - Galaxy S II Q&A, Help & Troubleshooting

Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.

Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.

Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.

Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.

FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA

Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5

if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.

Read the links in my signature
Sent from my GT-I9100 using XDA

I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.

Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.

FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..

@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q

I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.

...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone

It had finished a while before that. I was selecting a new font when it died.

You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2

@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.

Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium

@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.

Related

Questions from a Vibrant newb

Hello, all!
I've purchased a vibrant for my wife over the weekend (i'm on sensation), and have several questions.
The guy i bought it from did a hard-reset supposedly, and said that it reverted it back to the stock android build. Seemed weird, but the first thing i did was update it via kies mini to the froyo build. It's been working fine, except for the camera started messing up last night. Going into black screens, showing "camera failed" errors. It also takes some time (2-3 secs of black screen) to process a picture after it has been taken. I don't remember it doing that on the stock build. I did update it to the latest firmware.
Should i root the phone and flash a different rom? (which rom would you recommend?) A short google search revealed a lot of people having slow-downs after the froyo update.
Appreciate your help!
just to follow-up. wife's been having problems with the music player app hanging, then the phone shut down while she was installing something.... i'm going to wipe everything first to see if it helps any, but will end up rooting it and flashing something else, most likely.
Before rooting make sure you odin back to stock 2.1. That should het rid of the problems
Sent from my SGH-T959 using xda premium
Definitely do what the above poster suggested. Go to the development section and get the AIO toolbox. It has everything you need to get back to stock and get you rooted. If your looking for a good stable rom I'd recommend bi-winning v3. Good luck.
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
RussianBear said:
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
Click to expand...
Click to collapse
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
dseldown said:
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
Click to expand...
Click to collapse
Wow, didn't know this. Will delete kies asap. btw, this rom that i've flashed has a custom kernel (bionix? + voodoo). i did a backup of the stock rom via recovery. do i need to flash the stock kernel first before rolling back to stock?
hereeny said:
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
Click to expand...
Click to collapse
thank you, will check it out!
Project-V is a Great 2.2 ROM, I made a few themes for it too: Blar and WP7 Style

Can't update stock rom, "Communication Failed" from Software Update

I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Are you rooted? And why update to 2.3.6 uckk6? Its got a few really bad bugs.
Sent from my SGH-I777 using XDA App
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If*
Sent from my SGH-I777 using XDA App
Thank you for your helpful information.
Sent from my SAMSUNG-SGH-I777 using XDA
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
jcracken said:
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
Click to expand...
Click to collapse
Might give it a try. Trouble is, not having a rooted phone and going back to stock means I lose all applications and data with them. Eh. Thanks
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Phalanx7621 said:
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I already did this except for rooting about 3 weeks ago. From what you're saying, if I root my phone from its current state I should be able to receive OTA updates? I'm willing to root just to see but I don't see how that would fix the "communication failed" errors for updates.
Sent from my SAMSUNG-SGH-I777 using XDA
FYI I have a rooted stock ROM, and I'm having difficulty doing an OTA update also. Different error (mine is "interrupted" after reboot). I posted it here because it seemed more related to that thread and I had other Q's about the process.
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
LiLChris06 said:
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
Click to expand...
Click to collapse
I don't think you understand. First of all, in no way am I in panic mode. Secondly, my phone is a few updates behind since I just recently brought it back to stock from CM7. All I am trying to do is bring it up to date.
Sent from my SAMSUNG-SGH-I777 using XDA
ota issue
You might want to check the (Guide)How to flash custom binaries.....on this forum. Creepycrawly has posted a reply towards the end of the thread that might be helpful. Believe its on one of the last two pages.
As has been said many times in other threads, even on a stock ROM if you have rooted and removed even one item of bloatware or made any other mods you will not be able to download an OTA update.
I have not rooted my phone. And as I said earlier, I restored my phone to complete stock meaning no bloatware has been removed. I'm still at a loss for what to do
Sent from my SAMSUNG-SGH-I777 using XDA
You were on CM9 (in a later post you say CM7), but you went back to stock UCKH7. Now you are unable to update over the air to UCKK6. You are mainly interested in having the phone ready to receive the update over the air to ICS, whenever that occurs. You have not rooted the phone since you returned to stock but you are willing to try root if it will help the update happen. You were also concerned about loosing apps and their data since you are not rooted. I recapped all this because on stock you should be able to run the update. To help you solve the problem, need to know all the facts.
I've done the following, although it has been several months ago, about a week or two after UCKK6 first released. From running a custom rom, I did a wipe data/factory reset, flashed stock UCKH7 plus root, and ran the over the air update to UCKK6 successfully, retaining root on UCKK6. I just did this to test it out, so after completing the test, I used my nandroid backup to return to the custom rom I was on.
I would assume that you did a wipe data/factory reset either before or after you flashed back to stock? If not, there could be traces left over that could interfere with the update process. I'm not sure if there could be traces left even after a wipe data/factory reset, but the Cyanogen Mod file structure is so very different than stock that it wouldn't be inconceivable.
Next, I would wonder how soon after flashing back to stock you tried to run the update, and if not immediately, what action could have possibly placed or removed files that would intefere with the process.
I'm pretty certain that if you were to wipe data/factory reset with a format and then flash stock again, and then try to run the update immediately, it would succeed. So there has to be something in the file system preventing it. You may not find it easy to correct that something manually. You may just have to do a wipe data/factory reset, and maybe a format, and then start all over with a fresh install.
Of course, that is the reason for rooting first. Root, then back up everything with titanium backup, SMS backup, export contacts, etc. and save all that to your computer. Then you can restore stuff after.
Thanks creepy,
I'm in the process of doing what you said. I rooted my phone, backed up everything I thought needs to be backed up and flashed the stock rom (2.3.4 kernel version 2.6.35.7 baseband version I777UCKH7). I still need to do a factory format in order to see if that will fix the update problem.
Question. Is the firmware version(s) above the latest AT&T software? According to Kies, it is. But I am reading other places that the latest software is android 2.3.6.
Did exactly as creepy stated. Brought the phone back to stock software and did a factory reset. Without ANY customization and as soon as the phone booted up, I did the software update and had the same thing, "Communication failed" (says there is an update available but servers are busy).
I give up.
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
creepyncrawly said:
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
Click to expand...
Click to collapse
From what I've been reading on AT&T forums (http://forums.att.com/t5/Samsung/Sa...2-3-6-OTA-update-now-live/td-p/2996495/page/3) I don't think so. I've been trying every combination I can think of to make this thing work but I honestly have no idea. I was extremely surprised when I brought the phone back to complete stock and no root and still couldn't get the update.
If ICS ever comes to AT&T GS2, I'll wait a month or so to keep trying then I might resort to going to an AT&T store to get a replacement. Who knows

[Q] Newcomer here, be nice! CWM related

Hey all,
I just received my i777 and I'm impressed. Coming from a sgs4g seems like a huge improvement, though the devices look physically the same LOL (with the i777 being a bit on the larger side).
Anyways, I've been flashing roms for about a year now with my sgs4g. The forums for the sgs4g had very detailed instructions when flashing, instructions like, what to do if coming from stock, but on this forum ppl just assume you have CWM installed.
What I want is a safe way to upgrade to, let's say, phone bricker. I've noticed that all roms are installed through CWM, and all OP say is "make sure CWM is installed", but there's no mention whatsoever on how to install CWM on this phone.
Maybe i'm complicating things a little bit. On my previous phone, Rom Manager downloaded from market was a NO NO because it'd brick it. So we had to flash a modded CWM via odin made specifically for our phones. Maybe for this phone installing rom manager is all that is needed? yes? OK, found the FAQ. no ROM manager.
Also, somehow this phone came rooted... I bought it new from a store but the unlocked version since I live outside USA.
So, if I'm not mistaken, I should just install rom manager, select my phone from the list, flash CWM recovery and flash away roms on the dev section. Am I correct? I don't want to brick my phone
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
I bought the full version of mobile ODIN. makes life a little simpler when flashing, in my opinion. It's worth the few bucks.
eep2378 said:
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
Click to expand...
Click to collapse
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
mikeflash said:
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
Click to expand...
Click to collapse
You don't need pro version, lite version will do just fine. Are you sure you're rooted? You have superuser app? Whether you're rooted or not look here(if you are rooted look at #3 : http://forum.xda-developers.com/showthread.php?t=1311081
Check out this thread, was my experience and I'm running PhoneBricker just fine!
However, backup your apps before flashing and factory reset, wipe cache and dalvik after (possibly before as well) and you should be fine! Will root then you can flash away.
Clay
Sent from my SGH-I777 using XDA
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Well, I flashed my phone last night. Used mobile odin for flashing a kernel (siyah) to get CWM, then flashed phone bricker via CWM like I used to do on my old phone. Everything went smooth.
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
creepyncrawly said:
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Click to expand...
Click to collapse
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
If that's the case, then I'm not too worried about flash count because I live outside US, and my AT&T phone wouldn't get warranty over here, but I'll definitely look into that, to check where my counter is at and to check if resetting it back to 0 is still possible.
I'll be checking up on the links you provided.
Thanks a lot.
mikeflash said:
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
Click to expand...
Click to collapse
It is a true ICS rom. Samsung didn't do a lot of cosmetic changes when they moved the S2 to ICS though...most changes are under the hood.
If you want something that looks and feels more like true ICS, you should consider trying either CM9 or AOKP. They are both based on Google's source code, nothing Touchwiz about them.
Or if you'd rather stick with what you have, you can always try different launchers. I'm running ICS, but I use Go Launcher and it runs beautifully.
mikeflash said:
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
Click to expand...
Click to collapse
That is mostly correct. You're right about the purpose of the flash counter, but it actually counts how many times you flash kernels, not roms. And even then, it only increments if you flash a kernel via Odin in download mode. Flashing a kernel in Mobile Odin or CWM doesn't touch the counter.
Incrementing the flash counter also places that possibly annoying yellow triangle on bootup on your phone. Since you're on ICS, you can just use triangle away app from play store (free version is on here somewhere) to get rid of it, though I'm not sure if that'll fix the whole secondary bootloaders thing (probably not). I think it'd be worth it to fix that just so you don't run into anymore problems later if you decide to change something, especially since after the fixes you can just nandroid back to your current setup, but it's not essential and completely up to you.
Sent from my Samsung SGH-I777 using XDA
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Phalanx, did you not read the Title?
It says be nice!
crawls back into hole
Sent from my SGH-I777 using XDA
Phalanx7621 said:
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend.
To sum up for OP
1. Strongly suggest NOT to use ROM Manager on any custom ROMs unless you are surely running CyanogenMod ROM.
2. Check the "About phone" to see if it is true ICS or ICS-theme GB.

[Q] Rom help needed

I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
weati said:
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
Click to expand...
Click to collapse
Are you following the instructions as stated in the op?
Sent from my SGH-I777 running AOKP
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
No
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Phalanx7621 said:
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
Click to expand...
Click to collapse
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
And because this phone isn't other phones, you can't use rom manager with it. It's a nono. And there is a sticky about it. And many threads. And posts. Warning about it.
thanks
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Butchr said:
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
Click to expand...
Click to collapse
weati said:
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Click to expand...
Click to collapse
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
mattdm said:
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
Click to expand...
Click to collapse
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
1. Kies generally only works with stock unrooted phones. Use Odin instead.
2. The phone has no "inability to take a new rom" if you do it the right way.
3. Apparently you don't know pretty well what you're doing.
4. The i9100 works exactly the same way as the i777, and if you try to use Rom Manager on it, you'll end up with the same result: a phone that won't boot.
5. AT&T will unlock an i777 for you if you ask them.
6. Just read the damn stickies, particularly this one and this one.
This thread is full of win.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
You resolved the problem by buying the unbranded version of the exact same phone?
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
So u paid 70 dollars to unlock a phone. Great hope it was worth it. Because like others have said they are identical.
Sent from my SGH-I777 running AOKP

Updating crazyness.

I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!

Categories

Resources