Related
I have my galaxy s3 i535 rooted and CWM... Everything went smooth... I have made my backups...
However, whenever I flash a new rom, I get stuck in boot loop. Have to keep going back to my backup since it is the only thing I can get to work.
The latest is the AOKP Milestone 6 rom. It says it will boot loop twice and then kick in. Mine isn't.
Anyone have any ideas that might help?
Thanks
Hello there,
I was tired of my phone (Samsung Galaxy 3 GT-I5800) and wanted to do something with it. I found out its possible to install different systems on it, so i did. I tested CM10 with succes, but i wanted something different, i downloaded AOKP (in the meantime i flashed I5800XWJPD and I5801DXJPC ## from samfirmware, which were ****). So now i have couple bugs i can't solve:
When i boot my phone it says "GT - I5801" not "GT - I5800" as it should, i have no idea why.
AOKP bootloops (intro animation starts - ding white screen for 5 seconds or so, and loop), but eventually boots
Home button doesnt works in AOKP
AOKP doesnt reads SIM card (probably because of bootloop)
I used Odin Multi Downloader v4.252, apollo_0531.ops file, and said ROMs. Oh and i rooted it, or at least i think i did
Just flash another ROM. Your phone should work as usual.
Sent from my GT-I5800
try froyo roms m12., kisad's, purumod., or stock roms.. everything works in good shape
fraunos said:
Hello there,
I was tired of my phone (Samsung Galaxy 3 GT-I5800) and wanted to do something with it. I found out its possible to install different systems on it, so i did. I tested CM10 with succes, but i wanted something different, i downloaded AOKP (in the meantime i flashed I5800XWJPD and I5801DXJPC ## from samfirmware, which were ****). So now i have couple bugs i can't solve:
When i boot my phone it says "GT - I5801" not "GT - I5800" as it should, i have no idea why.
AOKP bootloops (intro animation starts - ding white screen for 5 seconds or so, and loop), but eventually boots
Home button doesnt works in AOKP
AOKP doesnt reads SIM card (probably because of bootloop)
I used Odin Multi Downloader v4.252, apollo_0531.ops file, and said ROMs. Oh and i rooted it, or at least i think i did
Click to expand...
Click to collapse
^
You are getting GT - i5801 instead of GT- i5800 because you flashed a .TAR file that had a bootloader. Never ever flash a rom that contains bootloader in it! Most of the stock rom's in samfirmware contains bootloader in them, so I highly recommend you not to flash such roms!
What you're getting is not a bootloop, but just a minor bug. You can fix that by simply downloading any custom bootanimation and then pushing it to /system/media. You can find tons of them in the "Themes and Apps" sub-forum.
No clue, maybe reflashing should solve the problem.
You probably have Pin Lock in place. Simply disable it and your SIM should be working fine after that.
I'll try different ROMs, cause i tried reflashing AOKP and it always has that white screen bug. Thanks for answers, i'll try different things, hope it'll work.
Edit: Ok i disabled boot animation in options and it works now, but still home button doesnt work and i found out that usb connection doesnt work too, i searched the forums for the solution, but i cant find that MTF option or how it was called..
EDIT2: Okay, everything's fine by now what i've done is i downloaded rom from samfirmware, double checking it has bootloader for 5800, installed it, and then did the same with M12. Thanks for help!
A few more things you should know before I get into it. First off, this is my mother's phone, and about two days ago, she went to unplug and use her SGS4G after it had been charging overnight, and it wouldn't respond to the Power/Lock Button (It appeared simply stuck). So, naturally, she did a battery pull on it, and tried to turn it back on. After she hit the Power Button though, the Splash came up like it normally does, except instead of progressing with booting, the screen went black for a second and then went back to the Splash and it did/does this indefinitely (An obvious sign of a Bootloop).
Now. What doesn't make sense to me is that this was running the Stock ROM (I don't know if it was Froyo or Gingerbread), yet this still happened. I haven't tampered with the Phone at all, and my mother isn't too fond of the idea of Rooting, so unless the previous owner (Yes, it is a used phone) tampered with it and then restored it to Stock, then I have no idea.
Things I have tried:
Heimdall One-Click For Dummies (With and Without flashing Bootloaders)
Juls317's Noob Guide's "Potential Problems" section (With both Heimdall and ODIN)
A few Kernels (bhundven's Kernel, drhonk's KG4 Kernel)
sygee's ODIN/Heimdall Flashable ROM
hailthetheif's Step by Step Rooting Thread
Also, after I flash anything, whether it be with ODIN or Hiemdall Suite, or Hiemdall's One-Click, if I leave the phone plugged into the computer afterward, it will go to the Splash Screen and then to the Battery Screen (Which doesn't work, it just freezes with the Loading Wheel) and it'll Bootloop with the Battery Screen. If I unplug it after Flashing, it goes back to the classic Splash Bootloop that has been happening since Day 1. It doesn't even get past the Kernel.
I know that at least the Kernel and the Bootloaders can be Flashed however, by how they act on the Device. For example, if I flash certain Gingerbread Bootloaders, I can only get into Download Mode with PWR + VOL-, whereas on the Froyo Bootloader (Includes Stock), you use VOL+ + VOL-. With the Kernel, for example, if I flash a TeamAcid Kernel, their Logo comes up on the Splash Screen, but it still does the Splash Bootloop no matter what.
One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.
One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.
Pull the battery, hold power& both volumes, drop the battery back in. Should bring you to recovery (gb, not sure, can't remember froyo same or not). Wipe data & cache etc.
On the heimdell, awesome threads that you quoted. Follow directions and it should get you there. Kj6.. you may have to flash it twice to get the bootloaders for gb(it's setup that way so you can't fubar it without trying really hard). You would have to check the load boot loader box on second flash.
I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot
LiangChi said:
I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot
Click to expand...
Click to collapse
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.
Able to get in to recovery and wipe? Wipe data & caches. Got cwm? Which one click? Eilleo(sorry for the spelling) put out a one click that was to be used as stepping stone to ics only.
WinterPhoenix96 said:
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.
Click to expand...
Click to collapse
I'm honestly not to sure if a Froyo ROM for Heimdall exists. I do believe seeing one for Odin, though. Not sure if that link is still alive. I'll see if I can find it again.
We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.
lumin30 said:
We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.
Click to expand...
Click to collapse
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.
Stuck on Froyo
LiangChi said:
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.
Click to expand...
Click to collapse
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!
You have so much info here... let's see what we can figure out.
grovernyc said:
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
Ok... when you flash the "stock" rom... have you tried to wipe cache, data etc???
Are you letting it boot up before appling any of the kernels??
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Try wiping data and such, still bootlooping??
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!
Click to expand...
Click to collapse
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.
Dirty Flashing
Champ - I think you might be on to something...haven't read about dirty flashing but it sounds right. I have been wiping data and caches (even tired reformatting system with a few roms). I do remember running into problems trying to following a few instructions sets that asked to disable the voodoo lagfix - hit option it just doesn't disable. After hitting disable see below Voodoo lagfix is actually: enabled next boot: disabled but even if I reboot back to CWM it is still enabled.
I might try the Odin Gremlin remover again. I was just getting frustrated after several days of failed upgrades. Second opinion on if it might be hardware/memory vs user error. I really didn't understand why even Kies (which everyone disparages) upgrade from stock Froyo also caused same loop.
champ1919 said:
You have so much info here... let's see what we can figure out.
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.
Click to expand...
Click to collapse
Retry the gremlim remover. Redownload it incase of a bad download.
Lumin30 has a good guide in his signature for the heimdall one clicks.
I use Odin, I have used his one clicks without problems though.
http://forum.xda-developers.com/showthread.php?t=1470716
Sent from my SGH-T959V using xda app-developers app
So after all these black screen issues, I want to try and find a connection for those getting it. So, please answer the poll and if you got the black screen post the following info (example shown)
Phone model and version: MB865 ATT
ROM before attempted install: Stock ICS
Ever used a previous version of CM10: No
things tried to fix: back to stock, old version fisrt, etc.
any thing else you think might be helpful
Phone model: MB865 international (Claro, Argentina)
Rom: Stock ICS HongKong/Taiwan
CM10 before: Yes
Tried to fix: No, it worked the first time
I can't read all the answers in the rom thread, but, if i flash the rom and the gapps at the same times, i'll get the black screen. And, if you flash the rom, start your phone, use it and then flash gapps from cm recovery, then it have to work. Maybe it was coincidence, but in several phones it worked.
Phone model - MB865 Asia retail
ROM before installation - Stock ICS
Used previous version of cm10 ( you mean cm10.1?) - Used cm10 before , and now 3 different versions of cm10.1. ( the one before kexec and 2 kexec versions)
Black screen issue - No issue at boot. Boots properly everytime. Gives me black screen at random times like after a call, or while charging. I got it around 2-3 times, pulled the battery and rebooted.
After using the ROM for some days ( it's been a week now), no black screen issue.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
I haven't experienced the black screen problem but any how
Phone model and version: MB865 ATT
ROM before attempted install: CM10
Ever used a previous version of CM10: Yes,CM10
things tried to fix: Didn't have to try.Have rebooted atleast 10 times since and still haven't got the black screen.
brianmoyano said:
but, if i flash the rom and the gapps at the same times, i'll get the black screen. And, if you flash the rom, start your phone, use it and then flash gapps from cm recovery, then it have to work. Maybe it was coincidence, but in several phones it worked.
Click to expand...
Click to collapse
I flashed the ROM and the gapps together without rebooting and haven't experienced the black screen problem.
Sent from my MB865 using xda premium
deveshmanish said:
I flashed the ROM and the gapps together without rebooting and haven't experienced the black screen problem.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yea, me too. But, the guys who has the black screen problem, they solved it with that.
---------- Post added at 04:07 AM ---------- Previous post was at 04:06 AM ----------
PS: Did someone tried with another gapps?
Model : AT&T mb865
Rom before install : SCV7 leak#1 based
Previous CM :yes
Things i have tried to solve ; none
It black screened me right after coming out of deepsleep , like other posts before mine, i rebooted my phone several times without having to battery pull , this is my booting secuense : first is moto logo, then white screen (2 seconds) then black screen (2 seconds) then cm bootanimation idk if it might help at all
Sent from the gray stuff inside my skull
Phone model and version: MB865 ATT
ROM before attempted install: CM10 (original not CM10.1)
Ever used a previous version of CM10: Yes
things tried to fix: Tried flashing with last version (3/28 build) of kexec and the latest version (4/3 build). With Gapps and without Gapps. Tried installing the CM10 Rom, booting into this rom, and then flashing the Kexec. Tried different slots System 3 and System 6. Before you ask I have modified the Rom according to instructions provided for BMM. Nothing works. The only thing unusual maybe that this phone was a replacement for my original Atrix2 after the original phone was hard bricked. This version also is factory clocked at 1.0Ghz and 4 clock stages vs. the original 5. I am not sure if this is an indication of different hardware. I think it's definitely a hardware difference causing the black screen as some of the other posts indicate plenty of people having success booting Kexec version with ATT Atrix2/MB865.
Model: ATT MB865
Cm b4 : yes
Stock rom : ics
Flash process: I flash the rom and gappps together in bmm recovery.
I use the converted kexec thru bmm. I get 1st boot success and the subsequent boots as black screen, or at least that is what I thought. I have went and let it simmer and found out that it my take a minute but... Looky there it booted. I went and used the converted 4/2 version ti upgrade and hadto reboot 2 times to get it to fly. Gotta love the silky smooth feeling. I have a radio problem that acts up so that throws another kink in it.
Atrix 2/ ATT /Bmm
1. Stock 4.0.4
2. Miui
3. PA 3.1.5 4.2.2
4. CMPA 4.1.2
5. Kexec 4.2.2
My stock ICS clock speed is 1.2 gigahertz. I also require through the performance mod down to 1.0 gigahertz and it is booted every time that I have power down first. I have it installed in slot 6
Phone model and version: MB865 Retail
ROM before attempted install: Stock ICS, PA3+, cm10.1, miui (tried with all).
Ever used a previous version of CM10: Yes.
things tried to fix: back to stock, different devtrees (other devices', different region, the ones of ME versions, flashing different devtrees to device using fast boot and combinations, my own as well), different display drivers, and quite a lot more. None have helped (so far).
You may also want to include the stock ICS max clock speed, if it ever booted up (even once) if it did boot up, was it with bmm or stock CyanogenDefy.
Stock ICS max clock speed :1.2 GHz
Ever booted up: Yes about 6 times. Completely random. Booted up with both bmm and CyanogenDefy recovery.
UPDATE: AAAND out of nowhere it boots up again. No idea how or why this time. BTW, its a fresh install in bmm slot 3. Took logs of last_kmsg, kmsg and dmseg. Any one wants anything else before the phone reboots and this rom may or may not come up?
Sent from my MB865 using Tapatalk 2
Phone model: ME865 (HKTWN)
Rom: 4.0.4. ME HKTWN ICS (translated to Hungarian language + implement some battery saving scripts)
CM10 before: No
Tried to fix: No, it worked the first time
Everything works fine, but the HDMI not working . I flash backmy own rom which is based on the JB Leak 2 (transleted it too).
Phone model - MB865 Asia retail
ROM before installation - Stock ICS searet
Used previous version of cm10: No.
Black screen issue - No issue at boot. Boots properly everytime. Noticed black screen only one time when one of application I worked (do not remember exacrly what app it was) with became frozen and I received a call at the same moment. I am not sure about call, i haven't heard ringing and haven't seen any caller id, only icon of conversation in notification bar. I turned off screen and tried to turn it on but without success. It was only possible to light buttons. Hardware reboot solved the problem.
Hey guys just wanted to make one thing clear, the black screen issue being discussed here is something that occurs even before the boot animation. Just after the M logo. Whatever happens after the cyanogenmod boot animation is ROM related. You get a black screen implies you can't even get to the boot animation.
Sent from my MB865 using Tapatalk 2
Phone: MB865 ATT
ROM before: stock ICS
When I first installed the first kevec update I got the black screen couple of time then I read about undoing the default 1.2ghz oc so I went ahead and did that, set it to 1.0 GHz set it on boot and it fixed my problem. I updated my A2 to the last update doing a clean installation and I have not experience any black screen so far.
Sent from my MB865 using Tapatalk 2
Phone model and version: MB865 ATT
ROM before attempted install: PA 2.57.3
Ever used a previous version of CM10: Yes
Things tried to fix: None
Installed CM 10.1 like the instructions. Kept getting black screens, and pressed power+vol up+vol down to reboot, but continued to get the black screen. Got super annoyed so I restored the backup I made before installing CM 10.1.
Ravi did u try to reduce clock speed as well.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
amynjimmy said:
Ravi did u try to reduce clock speed as well.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
Click to expand...
Click to collapse
If you are talking about the contents 2 posts above, that dosent even make a difference. I mean, when you are on one rom, change max clock speed and set it on boot, its only for that rom. And the max clock speed changes after the phone boots up and the app like setcpu changes it. But all that happens after the phone boots up. If it is even related to max clock speed, the only way to do that is to make changes in kernel.
Sent from my MB865 using Tapatalk 2
If I mess up and reboot u will always get a black screen. If I battery pull after that, it will boot after an undermanned amount of time. I even got some weird blue screen at some point thus morning and my phone started heating up. Finally battery pulled and got back into kexec again. Any method I have tried to get past black screen without battery pull yields more black screen. Power off will boot every time. What changes are made when booting between the 2. It is weird that we all get different results. I cannot even reproduce the same 2 times in the row unless I power down first.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
Phone model and version: MB865 ATT
ROM before attempted install: MIUI for ATT
Ever used a previous version of CM10: Yes before MIUI
things tried to fix: Reflash and multiple battery pulls.
I've actually gotten pretty good at pulling and booting since I've done it so many times. On average it take me between 20-30min to get the phone back up after a black screen. I've had several random reboots at the worst times and without skipping a beat a get to pulling and booting (can't be good for the battery).
Phone model: MB865 Indian Atrix2
ROM: Was initially in JB leak. FXZ to ICS Asia Retail version 4.0.4 to flash CM10.1
Previously had CM 10 before moving to PA.
Tried a couple of battery pulls but it did not boot. I flashed back the ICS 4.0.4 Asia Retail version to restore to a working phone.
~
Sayantan
Well the black screen seeks to be only because of the display driver.. Nothing to do with kexec. I changed some drivers and some of the previous errors were no more..
Sent from my MB865 using Tapatalk 2
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help I can't seem to find a working link for CWM-UXKG3-rooted-de-odexed-update-v2.zip maybe if I install the cwm the light neon blue screen will go away?
crayzze said:
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1613523
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
crayzze said:
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
Click to expand...
Click to collapse
rainbow screen on recovery = no gb bootloaders
blue screen on phone ...maybe bad cable connection or corrosion at contact
you might have to open it and check the connections
Working and tested CWM 1.2 ghz
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Fullmetal Jun said:
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Click to expand...
Click to collapse
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
crayzze said:
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
Click to expand...
Click to collapse
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Help!
qkster said:
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Click to expand...
Click to collapse
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol... My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear... my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
crayzze said:
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol...
Click to expand...
Click to collapse
no big deal..same phone..same hardware..different version of firmware..it's the APN for providers that makes the difference
crayzze said:
My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear.
Click to expand...
Click to collapse
yes..you are right. Rogers came with 2.3.3 not 2.3.4 as I previously stated.
the earlier versions of gb came with Carrier IQ that track users. It was taken out later.
I doubt Installing 2.3.6 or ICS or JB will cause any prob with the phone. I suspect your phone may have some hardware issues.
After the first flash, the os (esp ICS or JB) may need time to build cache and dalvik..sometimes it may take a few minutes. Blue or distorted screen, however, is not typical from my experience.
crayzze said:
my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
Click to expand...
Click to collapse
IMO, it doesn't matter how you get to CM10.2. Rooting is just one method. The idea is to get insecure recovery...ie..cwm.
from stock rom, you can odin or heimdall a custom kernel without rooting. boot into recovery and flash what you want.
it doesn't matter if its rogers or att. same phone..same hardware. years ago, it only mattered when a user had to return or exchange the phone for warranty...after the warranty period ended..it's not a big deal.
flash away at any method you want. it doesn't make any difference in my mind. get some practice..the infuse has many restore methods via odin or heimdall
rooting gives one access to the root directory
insecure kernel or custom recovery allows one to flash firmware without manufacturer signature