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
Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.
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...
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Applejackson said:
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Click to expand...
Click to collapse
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Thanks for the reply.
devious_z said:
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Click to expand...
Click to collapse
Thanks for taking the time. I guess my main concern was with the bootloader and whether or not I had to upgrade it and possibly lock it accidentally, or if I could just stay with the bootloader I have now, which is actually VRUEMJB. Used the method outlined in the AllianceRom thread for flashing the ROM. Since I still have a virgin bootloader I didn't want to lock it. I think I'll just try flashing the ROM as I have it, after a wipe of course, and I can always flash a recovery backup if need be.
I did try looking through the info in the threads for the ROM, but there are thousands of pages on the original and 90+ in the [**UPDATED] Verizon DN3 thread. The ones that I have read through have some conflicting information, so this query is really just to eliminate any confusion on my part before changing anything I can't change back.
Update: Tried and failed.
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Applejackson said:
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Click to expand...
Click to collapse
I guess I would start with reinstalling the MJ9 firmware through odin, and then try the rom again. You mentioned you were actually on MJB earlier which doesn't sound right.
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