Hi,
I have a Telus Fascinate (T959D) that I've flashed with Darky's 10.0 "Final".
I've read countless threads that tell me NOT to flash bootloaders to this phone, but we were adventurous (I don't own the device, a friend does) and wanted to try the latest Darky on it since it was working beautifully on my GT-I9000M.
Sadly, Darky's ROM requires a different bootloader, and it comes from an I9000.
After following the guide to install Darky, it effectively puts an I9000 bootloader, kernel, and ROM on the phone. (Shame on me, I know).
OK, so the problems are:
1.) No way to get into download mode or recovery mode without booting completely and issuing a 'reboot download' or 'reboot recovery' from a su terminal (or adb)
2.) The home and search softkeys act like left and right instead
There are other Darky related bugs, but not important to this discussion.
My question is: What is the safest/most reliable way to go back to stock Fascinate, bootloader and all? At this point since we don't have access to download mode without the phone booting properly, we don't want to flash anything else unless it's going to give us download mode back.
I've read the guides on going back to stock, but they all say you needed to have flashed a certain Telus ROM before going custom, and I don't know what exactly this phone had on it for sure. My friend says it was whatever was the latest update from Telus, but he hasn't plugged it into Kies in a while so I couldn't confirm for sure.
The idea here is to go back to stock then flash a custom kernel and possible a different modem to help with battery life and signal problems, and possibly some custom roms that don't require changing the bootloader.
Any insight would be greatly appreciated. If any additional info is needed, I'll provide it.
Hey just curious if you ever solved this problem as i currently have the exact same problem with a different Rom it won't allow me to boot into recovery and cwm won't recover my nandroid
Hi all,
I'm stuck. So first i wanted to root my GT-I9100G. I'm newbie in things such as "rooting", "oc'ing" an android device.. Ok so I've been changed only kernel from stock to lucifr 1.6uv. I did it with Odin, then i installed SU_busybox with CWM and yea.. Now i have a "yellow triangle" when i boot up my phone he he.. I did not changed the ROM. But then i concluded that my phone became very unstable and now i want to PERMANENTLY remove superuser, cwm and all the stuff witch came with custom kernel. I want to get back my device stock and clear again but i don't know how to... And yeah, when i connect my phone to kies, it shows i have available a new update from XXLA1 (witch i have right now) to XXLB1 and when i press update it does not do anything. Wata f? Maybe the problem is because i don't have a stock kernel? Help me please.
Im newbie here. Thanks.
Well I was running stock 404(i9020t) rooted with matrix kernel, and trying to prepare for jb ota in a few days I decided to go back to stock thinking having a non stock kernel, I would miss out on jb ota. So I proceeded to flash what I thought was my stock image for my phone (i9020t) but it turns out it was for (i9020a). After I realized that wasn't the correct image I halted my process. I'm currently on stock 404(i9020a),but my bootloader is still unlocked. So my question is 1. Will this affect me getting jb ota 2. If not will the ota correct my phone baseline 3. What steps should I take to achieve the stock 404 for my specific phone? I've read through multiple posts so I'm guessing I need some simple explanation. Thanks in advance.
Mod plz remove. I solved my problem. thx.
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
Good day to all, ya'll have changed things a bit it appears since my last visit. Okay I don't know what is going on as I have flashed hundreds of ROM's without issue and this morning Im seeming to have all kinds of issues. Sprint Galaxy S4 rooted and Flashed for Straight talk network. I am having some kinds of problems and am not able to flash any custom ROM's. Ive tried flashing GPE 4.4.4 and Super S4 ROM and Im getting a Footers Wrong error, error #7 and Signature not verified error and then it will reboot back to the stock firmware. So being my bright self that I am I toggled the signature deal in Clockworkmod and flashed it again and the phone rebooted and started up in GPE, but I could not get a data signal nor would it allow me to even turn on the wif-fi. and now Ive got it bricked and hooked up to odin. Any suggestions, comments, beatings or there of the likes. lol thanks guys yall are great.
Custom ROM Issues
Okay good day once again....Okay the phone has booted up completely and with GPE 4.4.4 or what I assume is GPE. I have no service to the device what so ever, but it does saying preparing network in the task bar and has been saying that for 20 minutes now, I still can not turn on Wifi. When I go to about device it says the following Software Version - Unknown Hardware Version - nothing Android Version 4.4.2 Baseband Version- unknown Kernal Version 3.4.0-216929 [email protected]#1 Wed Jul 9 09:03:50 2014 Build Number - SuperS4-1.5(which means it isn't GPE it is Super S4 ROM, which is cool especially since one of your guys I think built it) and everything else their looks normal to me. So any feed back on this post please. I have to be at work in a few hours and can not do without a phone ....
Hello...! I have some questions to you.... Do you try to flash a custom rom from recovery right....?
And it says "status 7 error"?
I think the reason for this is that you are trying to flash a rom that does not match with your phone or it's not singed...! For example you are trying to flash a rom for Samsung Galaxy S 4 GT-I9500...
Difficulty installing a custom ROM on samsung galaxy S4. Pls help
Pls am having difficulty installing a custom ROM on my Samsung galaxy S4 GT-i9500 Verizon. I have already installed a custom recovery(clockworkMod 6.0.4.7) and the phone is rooted. But each time i try to boot into recovery mode this is where am stuck. i cant seem to find the custom ROM i want to flash i mean the zip file cant be seen and its already donwloaded in my phone. I have some custom ROMS already in my phone for flashing but i cant seem to see the zip file in recovery mode. I took a screenshot so you can tell me what the problem is. Thanks