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
Related
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 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!
Good morning,
While not a noob to rooting or flashing (currently active on Galaxy tab 2 boards) I appear to have made a noob mistake, and even though I searched and read stickies, etc - still made the mistake.
I rooted the Rogers Infuse 4G using this thread http://forum.xda-developers.com/showthread.php?t=1197248 and it worked without issue.
Decided to try the enable lag fix option - deleted the voodoo file on the sd card, and rebooted the phone. Phone got stuck on SAMSUNG screen (unfortunately - did not notice that the volume was off on the phone) and I did not hear the "voice" telling me what was going on - so rebooted the phone by holding the power button until it rebooted.
Spent a couple of hours after that re-reading, and since I was able to get into download mode - was able to reflash stock package through odin. When the phone did finally reboot (thankfully, as this is my daughter's daily driver) I noticed there was already a voodoo file on the sd card, with another file inside named "logs" Just in case, I deleted that file, and added a new one called "disable-lagfix" as per the original instructions.
Just to be sure - went back and ran the rooting procedure, and can confirm that we have root.
From there, I decided to flash the 100% working CWM Recovery file through Rom Manager - found the details on this thread http://forum.xda-developers.com/showthread.php?t=1107881 and can confirm that after rebooting into recovery - the phone has CWM Version 2.5.1.2
The phone is currently fully functional, no issues with network or wifi, playstore, etc - but would like to know if anyone can confirm that we are good to go should we decide to upgrade to a custom rom. I've done so much reading - that the recovery version confuses me ( red or blue, etc). I realize that some of the threads are back from early to mid 2011 - so not sure if they are still completely valid - so am asking before proceeding.
Phone settings are the following:
Kernal 2.6.35.7-I997RUXKG3-CL366622
Build GB.UXKG3
Baseband I997RUXKG3
Firmware 2.3.3
CWM 2.5.1.2
Currently have the voodoo/disable-lagfix file on the sd card
If anyone has gotten this far into the thread - and can offer up some feedback or recommendations - it would be appreciated
Thanks in advance,
Bill
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
andros11 said:
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
Click to expand...
Click to collapse
Thanks for the reply - appreciate your time
Guess it's time to turn that volume up, delete the voodoo folder, and cross my fingers....
Just to confirm - do I delete the voodoo folder itself, or the disable-lagfix folder inside the voodoo folder only ?
Again, thanks
:good:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
andros11 said:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
First off andros11 - thank you so much for your time in replying to my issue.
My daughter has been looking over the development site - and,
as it stands right now, she has her mind set on the Dark Night Rom by VortexJunior.
Here is the link, if it helps http://forum.xda-developers.com/showthread.php?t=1662280
The install instructions, while relatively simple - and similar to what I am used to doing - but no mention of lagfix
Installation: From Gingerbread
1. Download Zip
2. Wipe Data/Factory Reset
3. Wipe Cache Partition
4. Flash
5. Reboot into recovery(Advanced>Reboot recovery)
6. Flash again
7.BAMM!
Thanks again for your time and replies,
Regards
Once on ICS I don't think you have to mind about lag-fix..
Also, I suggest you just reboot instead of rebooting into recovery. That often causes recovery bootloops.
When you reboot, the phone will hang at the kernel splash screen (this is normal). Just take out the battery, place it back in and boot into recovert with 3-finger combo (vol +, vol - and power, and let go when samsung logo pops up)
My personal suggestion is that you move on to JB. It performs much better, and mostly all development is now there.
Perfect - thanks
Am running CM 10.1 on my tablet, and love it
Will have my daughter research JB ROMs instead.....
Happy Holidays to you and your family
Regards,
sent from my GT-P3113 using Tapatalk 2
Lag fix??
I am confused.. what exactly is the lagg fix? My GF has a JB (one of phablet ROMS) installed and all the JB ROMS I have installed on this phone (and I think all ROMS besides JB) have had lagg problems. So I would really like to know how to fix this phone.
About that lagfix...
If I remember correctly voodoo lag fix was originally designed for the Galaxy S to change the file system it ran at to something that made the phone feel more responsive and access recourses quicker. It was ported to other ROMs so if a ROM includes it then you're ok to use it but I don't think you can just apply it to any JB ROM. Plus after using a GB ROM with this lagfix for some time, any 4.0 and above ROM I have used after that has been a LOT quicker in comparison. So I would probably look into the way you JB roms were installed maybe do a data wipe/factory wipe in CWM and reinstall the ROM from the beginning. What ROMs are you using exactly?
I've had my phone up and running on AOKP Milestone 1 and a custom kernel (can't remember the name now) for a few months now. I decided to replace the kernel with Lean Kernel since my phone's been crashing recently, and it was mentioned that the kernel could be the problem (this thread: http://forum.xda-developers.com/showthread.php?t=1842971&page=135).
After installing the kernel and wiping the cache/Dalvik cache, my phone rebooted but would not let me past the lockscreen. I then pulled the battery and attempted to reboot into recovery, but now my phone won't turn on at all. I'm currently charging my phone but no light is coming on, so kinda worried.
Any advice/solutions would be appreciated!
EDIT: I should also mention that if I pull the battery and put it back in, I get a "battery charging" symbol on the screen for a few seconds.
Download mode?
Sent from my SCH-I535 using Tapatalk 2
Did you install the proper LeanKernel? If you are on AOKP milestone 1 that is 4.1 based. The newest LeanKernel is 4.2 based. Could be the problem. There are also distinctions between AOSP and TouchWiz kernels. Do you know which version you flashed?
Regardless, if you can get into download mode like hank said, you should be ok.
Can't Boot into recovery with three button method?
Tried getting into download mode?
Well I feel dumb but after some searching around, people recommended just blowing on the battery contacts. This solved it, so case closed! Thanks for all of the advice though.
And yes, the lean kernel was for TouchWiz roms, which got me into this mess in the first place.
I recently bought my girlfriend a galaxy s II skyrocket. I own one myself. I updated my phone successfully and easily to jellybean through the official CM10. I am well aware of the different methods to install different custom roms to your phone. I received my girlfriend's phone with stock gingerbread. I proceeded to install the stock ice cream sandwich update to the phone through Odin. It was successful. I also installed ClockWorkMod recovery into her phone, the exact same one I had. I continued to attempt to install the same rom that I had on my phone, to my girlfriends phone, CM10. CWM said it was a successful installation after the careful 3x: Factory reset, Cache, Dalvik Cache. Upon rebooting of the phone however, the phone would fail to successfully turn on. It would stay in boot loop mode forever. One time I even left it for an hour and there it was, the boot screen I so dreadfully began to hate. I gave up on CM10, so i began to look for other prospects of a rom. I discovered slim bean. I installed it into my original phone to test it and found it to be of great quality. After I followed the exact same steps I followed to install slim bean to my original phone, to my girlfriends phone, the same result came about; boot loop. After about 20 tries, seriously, I tried to find yet another prospect of a rom. I also discovered another slimmer version of jelly bean for the Skyrocket. Even after the careful following of the steps, I encountered the same result; boot loop. I am beyond frustrated at this point at the fact that I am holding two phones exactly the same, yet when I attempt to install the rom, it only works on one of them. They are both Samsung Galaxy S II Skyrockets model numbers 1727. Both based off of At&t in the United States. One is white while the other one is black. If it makes any bit of a difference the phone I am having trouble with is white. I need help. I've tried everything with no success. I am trying to update this phone to jellybean but it does not seem to accept it, and I have no idea why
Re: [Q] Stuck on boot loop after several different jb roms
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I am not yet familiar with all the terms. It seems like jargon to me at times lol. TLDR Condense?
Re: [Q] Stuck on boot loop after several different jb roms
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've tried installing Official CM10.1 (from XDA) with boot loop result. I've tried installing unofficial 4.2.2 slimbean (from XDA) with boot loop result. I've tried installing Skyjellybean 4.1.2 update 11.4 (from XDA) with boot loop result, and finally I've tried installing Superlite CM10 JB 4.1.2 v8.0 (from XDA) with boot loop result as well. I am currently on stock Ice cream sandwich installed through Odin (links and all found from XDA)
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
lingowistico said:
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
Click to expand...
Click to collapse
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
That is good news, i'm glad it worked out for you. Good luck. :good:
Help
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Cisco408ca said:
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Click to expand...
Click to collapse
Use the latest recovery in your forum
Sent from my HTC One using Tapatalk 4