Related
Hello Everyone,
I have in the last 3 or 4 days joined in the rooted party of phones. With the Stock 2.2 rooted ROM on my Incredible i have tried a number of Circle Battery mods without success.
Thanks to the people that did a walk through on nandroid backups and restores i have not completely broke my phone.
With the above being known i apologize to anyone that reads this and says to them self "IDIOT!!" but i have a few questions I'm hoping i can get some answers on from other people with Incredibles.
1. If I install a different ROM like Cyanogen or Uncommon Sense to get the Circle Battery mod working will i be able to get back to my stock 2.2 rooted ROM using the restore like i did before?
1a. Is doing the ROM update done just like installing a mod "recovery-->install from .zip-->choose .zip"?
2. Is the Stock 2.2 rooted ROM worth staying with?
2a. If not and Verizon comes out with 3.0 or whatever the next number is can i go back to the stock ROM?
3. Does anyone have any known working Circle Battery mods for the Incredible running stock 2.2 rooted? ((I'm looking for something like "Ultimate Online Theme Kitchen") (SCB with %, Version Z, Custom type, colors--> A.))
Thanks for anyone replying.
I'm no expert, but I believe the reason the battery mod doesn't work with your stock ROM is because in order for those types of customizations to work, your ROM must be de-odexed. This is pretty standard in most custom ROMs but is not the case with stock.
As for your questions:
kevinlferguson said:
1. If I install a different ROM like Cyanogen or Uncommon Sense to get the Circle Battery mod working will i be able to get back to my stock 2.2 rooted ROM using the restore like i did before?
Click to expand...
Click to collapse
Yes, but when you do the restore everything will go back to the way it was before you flashed the new ROM. You won't be able to restore and keep the battery icon. When you create a nandroid backup, it's essentially a complete snapshot inside and out of everything on your phone.
kevinlferguson said:
1a. Is doing the ROM update done just like installing a mod "recovery-->install from .zip-->choose .zip"?
Click to expand...
Click to collapse
Yes. Be sure to wipe data/cache when flashing a new ROM though, otherwise you will run into problems. Always have a nandroid backup before flashing anything new just in case!
kevinlferguson said:
2. Is the Stock 2.2 rooted ROM worth staying with?
Click to expand...
Click to collapse
It depends on what you are looking for. Many ROMs include additional features, performance tweaks and customization options not available with stock. I'd suggest trying a few out to see what fits your tastes. If you're looking for something similar to stock with all the junk removed and ability to add things like custom battery modifications, I would give Virtuous a try.
kevinlferguson said:
2a. If not and Verizon comes out with 3.0 or whatever the next number is can i go back to the stock ROM?
Click to expand...
Click to collapse
For the most part, I would just stay rooted, as you'll most likely be able to get an official 3.0 ROM leak before Verizon gets an OTA out anyway. However, there are ways to revert to stock and unroot your device if you really want to. A little searching of these forums can provide you with a guide on how to do this.[/QUOTE]
Sent from my Droid Incredible
Wow... thanks for the information XideXL i think i will try a few other ROMs like your suggest and just keep my nandroid backup on hand should anything go bad.
I'm having a fairly serious problem with my TF. On Friday, I installed ICS (via Rogue XM, the full version (not upgrade) from this thread: http://forum.xda-developers.com/showthread.php?t=1514658). In doing so, I cleared the cache, dalvik-cache and did a factory reset.
Everything works like a charm, except my computer is not seeing the transformer. I plug it into USB and nothing happens, neither on the computer nor on the transformer. No "plug and play" sound, no pop-up notification about USB debugging mode, nada. I tried on two different computers (both running Windows 7), so the TF is the common thread. My USB cable charges the TF just fine and I have access to APX (I have a B50 pad), so this seems like an ICS problem. Worked fine on Honeycomb.
Anyone with the same problem? Or, better yet, a solution?
Flash the ROM from this thread on top as a fix (no need for any wipe).
http://forum.xda-developers.com/showthread.php?t=1334673
baseballfanz said:
Flash the ROM from this thread on top as a fix (no need for any wipe).
http://forum.xda-developers.com/showthread.php?t=1334673
Click to expand...
Click to collapse
Are you suggesting I go back to Honeycomb, and then flash that ROM? I can't flash that ROM on top of ICS because it's an upgrade ROM.
evilmonkey1987 said:
Are you suggesting I go back to Honeycomb, and then flash that ROM? I can't flash that ROM on top of ICS because it's an upgrade ROM.
Click to expand...
Click to collapse
No, what ever version your on (US, WW, ect) jsut download the correct one for your region from that thread and flash on top of your full ICS ROM.
baseballfanz said:
No, what ever version your on (US, WW, ect) jsut download the correct one for your region from that thread and flash on top of your full ICS ROM.
Click to expand...
Click to collapse
OK, that worked like a champ and my computer can see the pad now. What was wrong with the original ROM that I flashed?
Thanks for your help!
I'm not sure what causes the difference, but the original rom you flashed was missing the bootloader or blob.EBT. Most roms don't included it, but perhaps something changed with ICS that needs it for USB?
Weird. Oh well, works now!
Hi
What is the best custom Rom with HC ? I want to remove ICS till it gets better.
I tried searching but id prefer advice before i start experimenting around, plz help
Thanx
I'm also looking for a Nvflash back to HC just before ver ICS came out .....anybody have it please.
Sent from my Transformer TF101
JohnM109R said:
I'm also looking for a Nvflash back to HC just before ver ICS came out .....anybody have it please.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Guys - even if it's an older version of Hneycomb in NVFlash format, it will still help...
Here is what I'd recommend (as it worked perfectly for me) - it 10 easy steps!
1. Download this stock Honeycomb image in NVFlash format. It's not the latest version of Honeycomb, but it really doesn't matter, becuase once you install and root it, you are just going to install CWM recovery and install a custom Honeycom ROM over top of it anyway (which IS based on the latest version of Honeycomb):
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
2. Download rootkit for above version of Honeycomb:
http://www.4shared.com/rar/-IYDraGZ/Brkroottoolkitv71.html?
3. Download CWM Recovery.
4. NVFlash the image downloaded in step 1.
5. Boot Honeycomb (skip all configurations!) and then root it using the rootkit downloaded in step 2.
6. After Honeycomb is rooted, install CWM Recovery downloaded in step 3.
7. Download Revolver 3.11 and 3.11.1 patch
8. Install Revolver 3.11 via CWM.
9. Install Revolver 3.11.1 patch via CWM.
10. Enjoy Honeycomb stability again!
Or something close to that....
EDIT: Added links to NVFlash'able ROM and root kit.
The problem with HC revolver was that it took to long to boot up. Prime ROM did not have the same problem.
sdfghi said:
The problem with HC revolver was that it took to long to boot up. Prime ROM did not have the same problem.
Click to expand...
Click to collapse
Why is the boot-time such a big deal? I never reboot my device (at least now that I'm not on ICS anymore!), so the boot-time is almost meaningless...
I guess if you turn your device off every time you use it, that would be a pain.
Probably the reason that Revolver takes longer is becuase of what it's doing at boot-time (optimatizations, etc)...
Sent from my Transformer TF101 using Tapatalk
If you are willing to root and flash custom roms, first try a custom ICS rom in combination with a custom kernel instead of going back to honeycomb.
A lot of people got good results by using guevor's latest kernel.
Yeah that's what I'm trying to decide cause I need my pad daily use with not to much reboota and sods
Sent from my HTC HD2 using xda premium
I have already rooted my TF and made ready for a custom rom, but it seems that there is a fix available
[Kernel] ICS test (OC, UV) (test13) V9.2.2.3
Between HC and ICS, I thing ICS is far better (except for the stability issues), so I will give this a shot first before downgrading to HC.
As per my question on this thread HC Revolver sounds as a choice to many XDA members, so plan B should be this one.
some issues
Is revolver more stable now? I could never get the vga adapter to work. or it simply not freezing. This was last november.
If you're willing to go through the trouble to downgrade, you may as well just flash guevors test kernel or the TastyMehIcs kernel (in my sig) to fix the ics problems. I've had no problems on ARHD/Megatron with tastymeh 1.0 at all.
Edit: just looked at my uptime (I don't ever turn off really) 232 hours since last turnoff. That's stable enough for me!
I wanna know what good HC ROMs are out there too.
SoD doesn't happen to me at all, but I'm sick of the graphical glitches that are present throughout the ICS ROMs. People say it's only when you press recents - not true for me. I get it pressing recents, browsing youtube, in the nvidia apps, playing games, sometimes at the home screen, settings menu, etc.
It's very brief, but at the frequency it occurs, it's annoying. I want to know if it's present in HC as well. When I was on HC I never noticed it, but my device was on HC for maybe a total of two hours, so idk. The screen rotation thing is kinda annoying to. You turn the device, screen goes black for like a second, then it does the rotation animation. Things like that bother me cause it's not like that on my phone, even when I run ICS on that and it's not even receiving an ICS update.
I2IEAILiiTY said:
I wanna know what good HC ROMs are out there too.
SoD doesn't happen to me at all, but I'm sick of the graphical glitches that are present throughout the ICS ROMs. People say it's only when you press recents - not true for me. I get it pressing recents, browsing youtube, in the nvidia apps, playing games, sometimes at the home screen, settings menu, etc.
It's very brief, but at the frequency it occurs, it's annoying. I want to know if it's present in HC as well. When I was on HC I never noticed it, but my device was on HC for maybe a total of two hours, so idk. The screen rotation thing is kinda annoying to. You turn the device, screen goes black for like a second, then it does the rotation animation. Things like that bother me cause it's not like that on my phone, even when I run ICS on that and it's not even receiving an ICS update.
Click to expand...
Click to collapse
Be patient - we're beta testing a beta release now (.24) and it seems that the graphical glitches are fixed (I KNOW the recent-apps "diagonal tearing" is fixed at least) - I've never noticed any other glitches, to be honest...
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
Guys - even if it's an older version of Hneycomb in NVFlash format, it will still help...
Here is what I'd recommend (as it worked perfectly for me) - it 10 easy steps!
1. Download this stock Honeycomb image in NVFlash format. It's not the latest version of Honeycomb, but it really doesn't matter, becuase once you install and root it, you are just going to install CWM recovery and install a custom Honeycom ROM over top of it anyway (which IS based on the latest version of Honeycomb):
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
2. Download rootkit for above version of Honeycomb:
http://www.4shared.com/rar/-IYDraGZ/Brkroottoolkitv71.html?
3. Download CWM Recovery.
4. NVFlash the image downloaded in step 1.
5. Boot Honeycomb (skip all configurations!) and then root it using the rootkit downloaded in step 2.
6. After Honeycomb is rooted, install CWM Recovery downloaded in step 3.
7. Download Revolver 3.11 and 3.11.1 patch
8. Install Revolver 3.11 via CWM.
9. Install Revolver 3.11.1 patch via CWM.
10. Enjoy Honeycomb stability again!
Or something close to that....
EDIT: Added links to NVFlash'able ROM and root kit.
Click to expand...
Click to collapse
I wouldn't trust a rootkit , especially one hosted on 4shared. Just saying. A link to the original post would be nice.
---------- Post added at 02:50 AM ---------- Previous post was at 02:48 AM ----------
jtrosky said:
Be patient - we're beta testing a beta release now (.24) and it seems that the graphical glitches are fixed (I KNOW the recent-apps "diagonal tearing" is fixed at least) - I've never noticed any other glitches, to be honest...
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I haven't noticed these issues on the ROMs I've tried. And revolver is by far the best HC based ROM.
Jamesyboy said:
I wouldn't trust a rootkit , especially one hosted on 4shared. Just saying. A link to the original post would be nice.
Click to expand...
Click to collapse
Actually, that 4shared link is the link from the original post - I just copied the link here... I've personally used it and it's fine...
Sent from my Transformer TF101 using Tapatalk 2
I2IEAILiiTY said:
I wanna know what good HC ROMs are out there too.
SoD doesn't happen to me at all, but I'm sick of the graphical glitches that are present throughout the ICS ROMs. People say it's only when you press recents - not true for me. I get it pressing recents, browsing youtube, in the nvidia apps, playing games, sometimes at the home screen, settings menu, etc.
It's very brief, but at the frequency it occurs, it's annoying. I want to know if it's present in HC as well. When I was on HC I never noticed it, but my device was on HC for maybe a total of two hours, so idk. The screen rotation thing is kinda annoying to. You turn the device, screen goes black for like a second, then it does the rotation animation. Things like that bother me cause it's not like that on my phone, even when I run ICS on that and it's not even receiving an ICS update.
Click to expand...
Click to collapse
Turns out a lot of my issues were eliminated by flashing revolver and the androidhd builds,.probably cause they're essentially the stock ICS build.
Sent from my Transformer TF101 using Tapatalk 2
Thanks for guide.
I just found out I have a b50, and tried NVFLASH of ICS... worked for maybe 2-3 hrs, thought there was hope... and now it just froze playing music.
If this thing cannot even play music without glitching, whats the point really at all?
If this HC downgrade (and stay there) doesn't work, I'm selling this ASAP.
You can revert to the ICS bootloader with the .30 firmware using the information here as a guide: http://forum.xda-developers.com/showthread.php?p=31217902#post31217902
More importantly the new bootloader allows you to boot stock TF300 JB so you can flash back to my ROM if you like. My ROM does NOT touch the bootloader.
Thanks goes to saltxyz for this find.
Mysticial ROM v1 for TF700 and TF300
Thanks and credit to scrosler for his base located here: http://forum.xda-developers.com/showthread.php?t=1881042
Thanks rdejager for his suggestions on kernel kitchens.
And thanks everyone who took the plunge and helped test out the TF300 JB firmware.
STOP
1. I am not responsible for any issues this may cause your device and won't be held for any soft-bricks, hard-bricks, boot loops, exploding pets or Resonance Cascades.
2. You MUST be using the JB bootloader for this ROM to work. (At least I think)
The Goods
Stock
Rooted - credit to scrosler
De-Odex'ed - credit to scrosler
Busybox - credit to scrosler
init.d support - credit to scrosler
Ext 4 optimizations - credit to scrosler
Unsecure boot.img
Battery tweaks
Re-enabled TruMedia and SRS3D
"Unlocked" ro.sf.lcd_density
ro.sf.lcd_density=160 by default
Re-enabled TF700 camera bitrates
What Works/Doesn't Work
What Works:
Camera
GPS
Wi-Fi
Just about everything else
What Doesn't Work:
Changing Brightness
Wi-Fi Direct
Download
Mirror 1: http://dl.dropbox.com/u/83380328/Mystical ROM v1.zip
Mirror 2: https://docs.google.com/open?id=0B9yTvRPDom4ta3JRVVJ1MDQyTDQ
MD5: B309D00CF9F2FE9618607DB16716C931
Installation
1. Power off your tablet
2. Download the ROM
3. Copy the ROM to your MicroSD card or Internal Storage
4. Insert the MicroSD card in your tablet
5. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
6. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
7. Perform a backup from Custom Recovery
8. Wipe EVERYTHING except MicroSD card and Internal Storage
9. From your recovery menu press Install and select the ROM
10. Wait until the install process ends and then restart your device
RECOMMENDED but Optional Steps:
Seriously wipe EVERYTHING but MicroSD and Internal Storage
F.A.Q.
JB seems to be laggy. Any suggestions?
Yes, Wipe!! Even if you've performed a Factory Data Reset or Wipe Data I HIGHLY recommend unlocking your bootloader, installing a Custom Recovery, wiping EVERYTHING and installing the firmware again; preferably using Method 3.
Is there any way to change the Brightness settings?
Yes, through Third Party Apps. The most popular seem to be Lux and Custom Brightness Settings
Are we "SOL" having the TF300 Bootloader when the Tf700 JB Firmware comes out?
Personally I'm not too worried about the bootloader.
Either the official JB for TF700 will have the same bootloader as for the TF300, or it will be a newer version that we'll be able to flash.
The bootloader doesn't seem to be looking for a device check or else the 300 loader wouldn't have installed on the 700.
It really only seems to be doing a sig check for OLDER firmwares, not NEWER.
Why don't we have an Official TF700 JB Firmware yet?
I don't know, ask ASUS. I'm as flabbergasted as you are. We've only found two issues so far!!
Reserved Also
Wow, getting a lot of good roms now, glad to see more stock options too!
Added to the directory...thinking about reflashing! But I just put CM10 on...
DPI Changer
Any way to change the DPI? If you just try to use a DPI changer the tablet won't reboot back up.
alanbradshaw said:
Any way to change the DPI? If you just try to use a DPI changer the tablet won't reboot back up.
Click to expand...
Click to collapse
Just edit the build.prop directly. I personally like Root Explorer for such tasks.
The line your looking for is "ro.sf.lcd_density=160". 240 is default and 200 seems to be a nice inbetween.
Sent from my EVO using xda premium
Just installed this and removed useless apps I don't need and its a lot smoother then just the TF300 build. And I love it Thanks for your work Finally got the idea its not a waste I installed the TF300 firmware XD
Thanks worked great. Used 240
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Are you finding anything on the brigtness controll btw in the kernel stuff?
If I have some spare time I will check it aswell though just wondering
rdejager said:
Are you finding anything on the brigtness controll btw in the kernel stuff?
If I have some spare time I will check it aswell though just wondering
Click to expand...
Click to collapse
Nothing yet.
Feel free to poke around, I certainly don't know it all and am not beyond help or suggestions.
Loving this ROM, nice job
Getting ready to flash this, is there any problems restoring previous TWR backups (JB or ICS) if needed or flashing another JB Rom that doesn't have the TF300 bootloader?
Yes when you flash a stock tf300 JB Rom it changes your bootloader In a way that is not reversible atm not even with a TWRP boot backup.
ICS bootloader based roms (like cm10) will boot but they will be laggy and the volume rocker will not work.
Sent from my GT-I9100 using xda app-developers app
amaury48 said:
Getting ready to flash this, is there any problems restoring previous TWR backups (JB or ICS) if needed or flashing another JB Rom that doesn't have the TF300 bootloader?
Click to expand...
Click to collapse
Lufterfischer said:
Yes when you flash a stock tf300 JB Rom it changes your bootloader In a way that is not reversible atm not even with a TWRP boot backup.
ICS bootloader based roms (like cm10) will boot but they will be laggy and the volume rocker will not work.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Will the JB roms work ok?
amaury48 said:
Will the JB roms work ok?
Click to expand...
Click to collapse
Well yes they will work but not exactly OK ( brightness always on max and thus high battery usage)
But it is important to realize that cm10 and the derivatives are jb based but use ics bootloaders so they do not work equally :
Its like this :
Tf300jb bootloader + tf300 stock jb roms = smooth but high brightness and high battery usage
tf300jb bootloader + tf700 custom roms (includes cm10 und derivatives) = very laggy and volume rocker not working
tf700 ics bootloader + tf700 custom roms (cm 10 and others) = awesome performance and almost everything working
The jb bootloader has a build in check that prevents any older bootloader from installing so there is no working way to downgrade from there
So at the moment it is not a good Idea to flash ANYTHING that uses a tf300 stock jb bootloader because once you did that there is no way to get a fully functional rom at the moment .
Lufterfischer said:
Well yes they will work but not exactly OK ( brightness always on max and thus high battery usage)
But it is important to realize that cm10 and the derivatives are jb based but use ics bootloaders so they do not work equally :
Its like this :
Tf300jb bootloader + tf300 stock jb roms = smooth but high brightness and high battery usage
tf300jb bootloader + tf700 custom roms (includes cm10 und derivatives) = very laggy and volume rocker not working
tf700 ics bootloader + tf700 custom roms (cm 10 and others) = awesome performance and almost everything working
The jb bootloader has a build in check that prevents any older bootloader from installing so there is no working way to downgrade from there
So at the moment it is not a good Idea to flash ANYTHING that uses a tf300 stock jb bootloader because once you did that there is no way to get a fully functional rom at the moment .
Click to expand...
Click to collapse
I restored a Baked Black Bean backup that I created just before installing the Mystic Rom and everything is working perfectly, auto brightness control and volume control. No lagging whatsoever. Could it be cause BBBv3 is a AOSP based ROM? Or was it the TWRP backup that I restored why I don't have any problems?
amaury48 said:
I restored a Baked Black Bean backup that I created just before installing the Mystic Rom and everything is working perfectly, auto brightness control and volume control. No lagging whatsoever. Could it be cause BBBv3 is a AOSP based ROM? Or was it the TWRP backup that I restored why I don't have any problems?
Click to expand...
Click to collapse
I don't know. When I first upgraded to JB from ICS my Brightness worked as well. After reflashing JB Brightness went away. Something seems to be left behind but looking at the configs and initrd it should work and I haven't been able to figure out what it's missing and I haven't been able to reproduce the error.
Could you possibly pull your /system so I can compare it to my ROM stock to see what's new or missing?
MysticMgcn said:
I don't know. When I first upgraded to JB from ICS my Brightness worked as well. After reflashing JB Brightness went away. Something seems to be left behind but looking at the configs and initrd it should work and I haven't been able to figure out what it's missing and I haven't been able to reproduce the error.
Could you possibly pull your /system so I can compare it to my ROM stock to see what's new or missing?
Click to expand...
Click to collapse
I'd be more than happy to do it but your gonna have to walk me thru that process, I'm not that savy with doing that kinda stuff...
is there any way to decrease the temp of the tablet???
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