Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Kari458 said:
Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
Click to expand...
Click to collapse
Yup
cyril279 said:
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Click to expand...
Click to collapse
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
I've raged on this device a time or three myself, I promise.
The most abnormal part of each of your posts is the battery involvement. You shouldn't have to touch the battery at all for recovery mode, download mode, or flashing, so I would guess that you're up against dirty or failing charge port, a near-dead or failing OEM battery, or similar issue which made your flashing journey more troublesome than it should have been.
There are several posts [like this one] about troubles using i9100 batteries. They fit and function, but exhibit undesirable charging issues, which consequently tend to get blamed on some other aspect of the device.
The symptoms of a dirty or failing charge port also commonly mis-direct users to blame firmware, batteries, and everything-else.
-Cyril
Kari458 said:
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
Click to expand...
Click to collapse
Related
Hello, sorry if this has already been answered but I did look around at similar scenarios and it seems to me that using odin to flash the stock kernel should fix it but on my device, however, it doesn't fix my problem. I beleive what I did was select update firmware from .zip in clockwork on accident. Idk if this is what you consider a "boot loop" because it doesnt restart it just sits there at the black galaxy s2 screen. Any insight would be great. I hate to have to buy a new one as it is quite alot of money. Like I said, sorry if this is already answered but after looking around for hours I still hve had no luck. Thanks in advance, Alex
Can you get into recovery (volume up+home+power) or download mode (volume down+home+power)?
I can get in to download and recovery mode both
The outlook is promising then. Without knowing what you've flashed, it's impossible to say what damage you've done, but if you don't mind losing your data, you can certainly get back to a working state by following [READ THIS] Got a Boot Loop? Don't post a New Thread!.
Before going down that route though, if you do want to keep your data, let us know what you flashed as it might be recoverable (maybe you just flashed the wrong kernel).
I can't say for sure what i flashed but I can say that i either flashed with an update or updated with a kernel??? sound right??? idk. the data isnt near as important to me as the 680 dollars my carrier will charge me for a new s2. Right now im using a junk alcatel tribe and im going through galaxy withdrawls.
Well before flashing anything else, make sure you definitely have an I9100, not some other variant (I notice you mentioned dollars). If you have a different model, you're in the wrong forums and might make things worse by following advice for the I9100.
I was pretty sure that it is the I9100 but i took the battery out and double checked. it IS the I9100
also for what it's worth when going into recovery(stock version) right after the text reading updating application it gives me an error in red. (E:install_application_for_customer:Can't unmount /preload copy application failed) and after the (Appling [yes it really spells it appling] Multi-CSC) it says Can't access to '/system/csc/TTT/system/'. However, the line after it says that it says Successfully applied multi-CSC
My first attempt to get back to a working phone without losing data would be to flash a stock kernel then, have you tried that?
Ok.. done.. but it still sits at the galaxy screen except now it has the triange due to the custom firmware
If that hasn't got you up and running then it's probably time to bite the bullet and follow the instructions from the boot loop thread linked above (which will also remove the triangle).
Maybe you can answer another question for me. When in recovery mode it says apply update from sdcard... why does it say that when it doesnt actually read from the sdcard? i have checked with the sdcard both in and out and the file directory in the recovery mode doesnt change. is it calling the usb storage an sd card?
ok when flashing a stock rom do i use the phone option in odin or the pda still
If you're flashing a stock rom from [ROM+Guide]Official i9100 Firmwares KG, KH1/2/3/4, KI1/2/3/4/8, KJ1/2 Download, then just follow the instructions from there (but usually PDA).
:'( Still wont boot.
What does happen, did any steps fail, any error messages?
Everything went smooth with no errors. No steps failed. Sitting at the boot screen is all it does though
Did you definitely wipe user data? (step 3). The final step of that thread is to try flashing a ROM which wipes, such as (non-stock) VillainROM 1.1.
well... yes i definitely wiped the user data and it was successfull when doing so. I didnt try the villian rom just because I thought that it was an optional thing but i will def. try it now that you bring it up. and hey, i really appreciate the help no matter what the outcome
(VillainROM 1.1 - XWKE7 base) I'm a UHKG7..... is this going to be a problem? just something i noticed and thought I would ask before going ahead
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
http://forum.xda-developers.com/showthread.php?t=1313659
Branded? Unbranded?
There is only one variant of the I777 - AT&T Branded. Anything in the Development forum for the I777 will work on an I777.
It's not like the I9100 with a bunch of minor subvariants.
drmorbo said:
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
Click to expand...
Click to collapse
Are you able to reboot the phone in recovery using ADB?
Its gotten to the point where nothing I try works. I managed to get cm7 installed and it got stuck in a boot loop. Flashed back to the stripped down version again. Everything that could go wrong has. For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Thanks again
defeated
drmorbo said:
For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Click to expand...
Click to collapse
Which you can't find? Someone posted the link to my return to stock guide in post #2 of this thread.
If you return to complete stock using Entropy512's Return/Unbrick to stock package, you will regain the AT&T boot logo instead of any custom boot logo. The phone will be just like it was when you first took it out of the box.
If you want the stock ROM plus root, Entropy has a package for that also. Just flash one of his packages with Odin, or use the One-Click downloaders for his package that are linked in my guides.
Update: You can also download all of these from my Download Repository.
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
drmorbo said:
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
Click to expand...
Click to collapse
That might affect it but I highly doubt it.
So do you have any idea what could have caused it? I tried searching the forums but I couldn't find somebody with a similar problem.
Where exactly does it say your phone is I9100?
It shows "Samsung galaxy s II I9100" before the at&t load screen.
drmorbo said:
It shows "Samsung galaxy s II I9100" before the at&t load screen.
Click to expand...
Click to collapse
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Entropy512 said:
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Click to expand...
Click to collapse
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
drmorbo said:
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
Click to expand...
Click to collapse
The return-to-stock-with-root shouldn't touch bootloaders - but it should have restored a stock kernel. IF you're getting the "yellow triangle" I9100 boot screen, the last thing flashed with Odin/Heimdall was NOT a stock kernel.
There is no yellow triangle. I used the exe from the link in the first response in this forum. In any case I'll throw a picture of the phone while turned off but charging tonight. The display issues aren't grave but they are noticeable and annoying. Do you know of an app that allows you adjust graphical/display settings? Maybe it would suffice.
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
drmorbo said:
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
Click to expand...
Click to collapse
AT&T version is missing screen tuning unless you run a custom ROM that readds it like Serendipity VIII or Unnamed.
Okay cool. So I used the one click with root and the wifi is broken and it won't let me do an OTA. however I had previously used the one click without root and I was able to OTA and that solved the broken wifi. What would be the easiest way to fix the wifi?
Flash cwm>factory restore/wipe (I don't have cwm and I remember the cyanogen wiki way to get cwm messed up my soft buttons--two didn't work anymore)
Or
Flash the 12/21 dd kernel (I did originally try this route. However Odin didn't recognize the kernel. I even repackaged I with just zImage. Still nothing.)
Thank You again Entropy
DrMorbo
Sounds like there is something broken about the oneclick... Try flashing the return-to-stock package with Heimdall. Heimdall also lets you flash kernel zImages without packaging into a tar.
However Heimdall needs its own driver mojo on Windows - I can't really help you with this, I've flashed a device from Windows only once, and that was the Tab 10.1 because Heimdall won't talk to it.
Nevermind. I tried the update a third time. It decided to work (48 hours later). Everything works. Wifi works. The screen is better (I used voodoo screen tuning to greatly diminish the black crush and red saturation. I can finally customize my phone now. Any nifty apps you know of Entropy? (Regular or root needed)
Thank you again Entropy,
DrMorbo
Not my first time to root and install a custom rom on other phone, but this phone isn't treating me well.
So I followed the root guides to root the phone.
Downloaded an insecure kernel for i9100. Although, oddly enough, I bought this phone 2nd hand, and when I went to the "about" part for the kernel look up before tried to root it, the kernel info just contained ICS3.?? (forgot) and the date. There was no four or five letter kernel code like I've been seeing. But according to cnet (one of many rooting tutorials), the kernel version doesn't matter as you can change the kernel anytime, or after rooting in this case.
So I installed Kies to get the Samsung drivers installed. Done.
Restarted phone to download mode (volume down, home, power)
Started Odin 3 v1.83
Phone was recognized. Click the 2 boxes (Auto reboot and F. Rest Time).
Clicked PDA, loaded up an insecure kernel.
Status went through OK, ended up with "Pass!"
Phone automatically restarted.
Now the problem. It restarts, shows the Samsung Galaxy S2 logo with the big triangle underneath it, and thats it. Never leaves this screen. I thought maybe it's a kernel problem, so I tried several different insecure kernels, all with no change. I have no idea how to find what kernel was the original one that came with this phone. Would using Odin with the original secure kernel (or even insecure) solve this problem? Otherwise, what else can I do? My note 2 was stolen so I bought this s2 second hand until I can scrape up enough money for a note 2 again, but the damn thing won't even boot up now. :crying:
How can I get this working again, even to have it stock again I'd be fine (though obviously putting on a custom room with root would be best).
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
TheATHEiST said:
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
Click to expand...
Click to collapse
There wasn't much to try, at least as far as my noob self knows about. I tried flashing 6 other kernels I found, merely taking guesses at which might possibly be the Chinese s2 one, I remember from flashing other phones that i had to look for Z or D in the kernel ID. But all of them just led to the same problem of not booting past the logo screen.
Besides just trying to start it up as normal (which doesn't work) and starting it up in download (by holding down vol+home+power), what others ways can I start it up? I don't know how to boot into recovery, and I didn't know I can flash a rom without first rooting it, which I haven't done yet because it's still stuck in start-up.
Searching enough xda threads and just googling seems show a pretty large consensus supporting the existance of a China i9100, plus I see them everywhere (as well as s3, s4, and notes), so I'm 99% sure they are an official and semi-large market for them here (after iPhones unfortunately). But even still, that doesn't help me locate the original kernel.
Under the battery, is says this:
Samsung WCDMA
Model #: GT-I9100
CMIIT ID: 2011CP2751
Do these help? So is any of the steps I did wrong, or can you otherwise point me in the right direction? Appreciate the help.
Don't post your IMEI (or your SN for that matter).
MistahBungle said:
Don't post your IMEI (or your SN for that matter).
Click to expand...
Click to collapse
Thanks for the tip MistahBungle. Edited out.
Hate to say it, but found more help on youtube... Found a guide that walked me through replacing all the files (not just kernel) in Odin that got it back up and running. I'll follow the xda guides again and hopefully it'll work this time... Thanks anyways...
I'm in a bit of a tight situation over here. My mom's phone was having issues, so she wanted me to fix it before I left to visit my grandparents. I found a stock ROM for the phone (GT-i9100 International) and flashed it, but the phone always got stuck on the "Samsung Galaxy SII GT-I9100" boot screen (occasionally it would show the "O2" screen, as it was a ROM for Ireland). I tried a different ROM (can't remember what country it was), and I'm still stuck with the same problem. This time no O2 screen though. I've downloaded my ROMs through sammobile.com and I'm using ODIN v1.83.
The label under the battery reads:
Model: GT-I9100
SSN: -I9100GSMH
What ROM should I use and where can I get it? I found this thread with a link to the ROM for the international version, but Hotfile has been shut down, so I can't download it.
Sorry if I could've found the answer with a few more hours of searching, but I've got less than 24 hours to find a fix and I was hoping that someone else could help me. Thanks a lot!
EDIT: I'm in the U.S., if that matters.
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Any region?
MistahBungle said:
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Click to expand...
Click to collapse
Should any region work to get the phone up and running? I just need to get it back up so that I can root it and flash CM10. Thanks.
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
MistahBungle said:
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
Click to expand...
Click to collapse
Is 4.1.2 OK, or should I go for 4.0.3 or below?
Doesn't matter, take your pick.
More info on problem
I tried installing two other ROMs (from androidfirmwares.net), one 4.1.2 and one 2.3.6. The 4.1.2 didn't get me anywhere, but after I flashed 2.3.6 the phone said the assert check failed. GT-i9100 is on the list of what it checked for. (I've never had any luck with the assert checks on any of my Samsung phones: GS Captivate, GSII Skyrocket, or AT&T GSIII. I've always had to remove the check in my update script.) I attached a picture.
EDIT: Since the attachment doesn't seem to be working, here's a Dropbox link.
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
MistahBungle said:
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
Click to expand...
Click to collapse
My process:
Open ODIN v3.09
Plug in the phone, already in download mode.
Click the AP button and load my .tar.md5.
Click Start.
Wait for it to finish, leaving the phone untouched on the table.
I just tried another USB cable, but to no avail. I've also tried unplugging the phone right after it reboots and ODIN says "PASS!", but no luck there either. I just tried another ROM that just finished downloading and it's giving me a similar getprop() error. At the bottom of the output in red it says:
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I don't think there's any way for me to edit the update script, as the tar contains a bunch of filesystem images. Even if it was easy to edit it would ruin the checksum verification.
Check out the picture on Dropbox here.
What are you trying to do in Android recovery ? Given what your stated aim is - get a stock rom on the phone, re-root it, put custom rom on, you shouldn't be using Android (I.E stock) recovery at any stage.
The process should be:-
*Flash stock rom with Odin in download mode (I.E phone off - home/vol down/power, not home/vol up/power)
*Root phone with whatever method
*Flash custom rom with CWRecovery, which you'll get once you root the phone
So....You need to go step by step. Start with flashing the stock rom with Odin, and try to boot the phone normally/make sure that was successful before doing the next two steps. Look for Hopper8's 'Odin troubleshooting' guide if you're having trouble getting a successful Odin flash.
Once you've done that, root the phone & make sure you have CWRecovery working, then flash the custom rom.
The phone boots to the recovery screen after it finishes flashing with ODIN. I put it into download mode, run ODIN, and then it that error screen comes up on the next reboot.
Try flashing the three part firmware linked to in Hopper's thread first (this will wipe the phone). I can't help but think we're missing some info re: what's been done to the phone previously here if the phone is booting into recovery mode after being Odin flashed. It shouldn't do that. After an Odin flash/pass the phone should boot normally, assuming it's not a case of the NAND being corrupted (it probably wouldn't boot into recovery if that was the case/you'd be left with constant bootloop)
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
MistahBungle said:
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
Click to expand...
Click to collapse
At the top of the download mode screen it says "PRODUCT NAME: GT-i9100". I don't know any other way to tell besides this and the sticker on the back. There are no carrier markings anywhere, and this phone was purchased because it had an FM radio, which only the international version had.
And assuming by "Hopper's thread" you mean this one, I can't because the files are no longer available.
In that case, you're stuck with the other suggestions to try in his thread & continuing to flash stock roms until you get a properly successful flash I.E phone boots/works normally. There might be something really obvious here being missed, but because we're not there with you/don't have the phone in front of us it might be difficult to work out.
It's working!
Yay, I got it to work! I flashed a custom kernel (jeboo), which allowed me to get into CWM. From there I sideloaded CM10 and now it's up and running! Only I still have a problem with internal storage... (That was the problem I was trying to fix originally.) Would the next thing to try to fix that be flashing a PIT file? If so, any tips for doing that?
I'm going to put off trying to fix that problem and do it when I get back. For now it works as a phone, and that's what's most important to her anyway. Thanks for your help MistahBungle.
Solved!
For anyone else who comes across this thread, I was able to solve my problem permanently by flashing a new PIT file. I found the correct PIT files for the GT-i9100 in this XDA thread. It seemed my partitions had become messed up long ago, as the phone had been showing a 2GB /data partition and only a 2GB internal SD card partition (which should've been closer to 12GB) for some time.
I choose a 4GB data partition (since I was running low on /data space last time). Oddly enough, booting the stock ROM after flashing the PIT only showed a 2GB data partition. Once I flashed CM10 it showed as 4GB though.
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
dsteinschneider said:
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
Click to expand...
Click to collapse
If you're looking for a newer phone that lets you unlock the bootloader, you might want to check out last year's Nexus 6 or the newer Moto X Pure Edition. The Nexus 6P from Huawei also looks nice and I'm keeping an eye on it as my next potential phone. The Nexus 5x from LG should also have a boo that can be unlocked.
-----------
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
I'm thinking that you're probably getting confused with needing to flash Beanstown106’s modified MJ9 firmware (which doesn't return the phone to stock or contain the 4.3 bootloader). See one of my previous posts ( http://forum.xda-developers.com/showthread.php?p=58541771 ), which discusses a similar issue and has a link on how to flash the stock recovery back onto the phone if you'd like to try that rather than restoring the phone back to stock 4.1.2.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
I usually remove my Sim card when restoring to stock 4.1.2... just to ensure I don't accidentally take an OTA update before I get it rooted again. (You can skip the initial phone Setup screen with the method in this YouTube video - https://youtu.be/qekEpn1Bufc ). It says it's for the S3 but works on the Note II as well. Once you get back into the phone and enable USB debugging in Developer options, you should be able to run Casual again. The phone doesn't have to be activated or on wifi to do this.
Once Casual is successful, it's safe to put the Sim card back in because I don't believe an OTA can install successfully with a custom recovery installed.
Good luck.
mattnmag said:
I
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
Click to expand...
Click to collapse
All the ROM's and tools are from threads here so pretty sure I'm using Bean's modified MJ9. I was on Beans 4.3 for over a year before I went to the Alliance ROM.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
Click to expand...
Click to collapse
4.1.2 sounds like a better idea - I have that also.
Thanks your advice here is just what I was looking for in my effort to get this phone running again.
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
dsteinschneider said:
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
Click to expand...
Click to collapse
I don't know if a USB jig would help the computer recognize the phone again.
Since you tried 3 different computers and still couldn't get it recognized... I'm wondering if something got fubared when you Odin flashed the VRLJB stock Rom. So when you go to Device Manager in the computer, the computer doesn't even show anything connected at all?
I don't know that it would be worth the time, but (on the computer that last worked for your phone), you could try uninstalling the Samsung Drivers, and then use a program like DevManView to totally uninstall all Android related drivers. Restart the computer afterwards and then reinstall the Samsung USB Drivers (from here: http://www.samsung.com/us/support/owners/product/SCH-I605) . Then connect your phone back to the computer in Download Mode to see if it will reinstall the drivers and recognize it.
If the computer still doesn't recognize the phone after all that, then I'm out of ideas.
I'll try the devmanview driver cleanup (love nirsoft utils!) and install the driver in your link on the orginal pc which I use for flashing ROMs. If that doesn't work I'm going to look into sending it out to a JTag guy although they claim if you can get into download mode after they perform their magic that they were successful.
Went with the LG G4 which I'm very happy with. As far as getting the Note 2 running again I've been thinking l might buy a used Verizon Galaxy Note 2 motherboard on ebay rather than sinking a lot of time into trying to... should I say "unbrick" it.
If you ran casual first, it will not connect to the samsung driver, until you uninstall the USB services from the device manager, and then run find new hardware.
But maybe this will not help considering you already tried 3 machines?
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
dsteinschneider said:
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
Click to expand...
Click to collapse
Right, it was in the Adam Antler video, for casual. Once you use the casual on USB, the samsung driver will not work until you uninstall and reinstall USB system.
I can get almost 3 days out of a phone battery with little or no use. The one I am using could make it a day and 1/2, but I charge that one every night because I do not need and down time just in case.
I am using the nightly build, 12.1-20151222 12/22/15, I am not sure how the other builds are, or even the stable build for that matter?