Ok, so I flashed JT's Vanilla gingerbread rom using CWR 4 and everything seemed fine. I then flashed B Boy Blizzard theme and everthing ran fine for about twenty mintes, then I got what I thought was the sleep of death (only when I pressed the sleep button). I pulled the battery and powered the phone back on. The phone booted into recovery and I got and error 7 cache recovery unable to mount message. I really like what little of the rom I saw and the theme. I sure at this point I'll have to Odin back to stock as I can't do a recovery either (same error message). What I'd like to know is this just a problem I'm having or is there something wrong with the rom or theme? Please advise. Thx in advance.
I have had alot of problems with that rom aswell...not really sure whats going on. Sometimes the rom will install with cwm 4 other times it just boot loops. I have tried every install method for that rom and nothing yet seems reliable. I have no problems flashing other roms, so idk... just chillin with powerwash right now until the bugs get worked out w/ VGB(hopefully).
All of his themes (at this moment) are based on 080211 v2 VGB. And between v2 and v3 there were framework and other apk changes i.e. settings. So flashing that theme on top of v3 will surely lead to issues. Just reflash rom. And make sure the theme you try only says for v3.
good day.
Also, you wont boot into the right recovery using the 3 finger method. you need to use adb or the reboot options
Related
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
kim2rock said:
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
Click to expand...
Click to collapse
Download might have been corrupted or you flashed SC and then flashed the theme without rebooting in between.
Thanks jonesya13!
I'm pretty sure I rebooted in between, but I will try to re-download the file and then flash the theme again as you suggested.
This happened to me on both the 3.1 & 3.1.2 with superclean 2.9.2. I booted fully into superclean as well before flashing the theme after a cache/dalvik wipe. Battery pull worked both times. Rebooted normally after that.
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
kim2rock said:
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
Click to expand...
Click to collapse
I had the menu and home button problem as well, ended up flashing, I think the EC10 kernal, and it fixed that problem for me.
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
kim2rock said:
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
Click to expand...
Click to collapse
You might as well as update to jt's ec10. BLN + Sound + Color.. Epiiiic
Just wipe cache/dalvik
Rocking Frankenclean 2.9.2 Voodoo/EC10+Sound+BLN+Color/Nitro Ultra Honeycomb v3.1/XDA Premium
xHoLyx,
What might be some advantages of jt's EC10 over regular EB01, in your opinion? I'm not too familiar with kernel replacement, so reading relevant posts might take some time. thx!
I tried 2.2 out a few weeks ago and decided I couldn't live without Voodoo Sound and BLN so I decided to wait it out. Obviously we have these enhancements available for Froyo now, so I made the jump to JT's initial EC10 release.
Everything worked fine, I just didn't feel that "snappiness" I had before. I thought maybe it had something to do with being undervolted (even though only slightly.) I saw that there were some problems with imnuts initial kernals he posted and waited to flash the updated (fixed) link for 0328_imnuts_sv_voodoo.zip. I flashed last night, booted up, and played around for a little bit and everything was working great. I had it plugged in to charge overnight. That brings me to my issue...
I woke up this morning, reached over to turn my phone on and I got NOTHING. No boot, samsung, lights, nada...I thought "****, I really bricked my phone now." I tried booting into recovery using the 3-button combo, plugging it in my computer to try download mode, plugging my charger in different outlets,etc...The phone seemed like there was no sign of life. I was ready to head to Verizon before work then decided to plug in my car charger for ****s and giggles and sure enough...IT WORKED! It started charging and I turned the phone on. Now I am at work and the phone seems to be working just fine...I even have the usb plugged in my computer and it is charging now (The same one that didn't work this morning.) This has never happened to me before and it was pretty scary. I have had to ODIN before, but I was worried that wasn't even an option. Thanks god everything SEEMS to be working fine right now, though that made me a little concerned.
Do anyone have ANY idea what might have happened!? Thanks in advance.
EDIT: After a couple hours, I saw my battery start to wig out. It went from being at like 34% to flashing the "low battery" warning. It then turned off and did the exact same thing. I had to go out to use my car charger to get into recovery. I wiped cache/dalvik cach, and re-installed SC. Not sure if it's kernal/ROM/Theme with 3rd party battery supprt...
Voodoo'd Samsung Fascinate
Kernal: 0328_imnuts_sv_voodoo
ROM: Superclean 2.9.2
Theme: Nitro's Ultimate Honeycomb v3.1.2
Hi guys,
I am new to the XDA forums so forgive me if this is really stupid or if someone has posted the same problems. I searched for an answer but couldn't seem to find someone with my problem. Forgive me if this is long. I just want to make sure you guys know all the details so we can figure out what went wrong.
I recently flashed the Evil Fascination 3.6 Rom from a modified stock version of ED04 (debloated/debinged). I believe that my version of CWM recovery was 2.5.1 or something like that (w/ voodoo lagfix). I am pretty new to the Android world but I do believe I did everything correctly. I wiped Cache and Dalvik Cache and Data multiple times and made nandroid backups etc.
I flashed the Rom with no problems and everything worked just fine. I was trying out Regina 3D launcher at the time (I regularly use Launcher Pro), and for some reason it seemed a little slow to load up (I figured it had to do with it being the first time with the new rom). I kept having loadup problems with the launcher so I uninstalled it and went back to Launcher Pro. Launcher Pro even seemed like it was acting weird but I didn't take much notice to it.
Now yesterday I downloaded the OTB 1.6 Touchwiz kernel. Everything I've read said it was compatable with Evil Fascination. I tried to flash it from CWM recovery and it didn't work. My phone stayed stuck on the Evil Fascination boot up screen and finally I just popped the battery out. I went back into CWM and just wiped everything and reflashed Evil Fascination. It seemed to work fine with Launcher Pro (again a little glitchy at times, but I took no notice really).
I again tried to flash the OTB 1.6 kernel. This time instead of doing it from the recovery I downloaded an app called SGS kernel flasher. I did what it said and it flashed the kernel for me with no boot up problems like CWM did. I rebooted and then booted into CWM to check it and it was changed from version 2.5.1 (voodoo) to 3.2.0.0.otb. I figured this meant that the kernel flash was sucessful. I went to reboot my phone and when the home screen came on it was a froyo style launcher with only 2 or three icons on the page. I pressed the app drawer and none of my apps showed up that were on my sd card. finally i pressed the home button and it asked for which launcher to choose : LauncherPro or the default and I chose LauncherPro. My regular setup appeared and my apps were in the app drawer. I found it weird that my apps showed in LauncherPro but not in the default launcher.
Now with doing phone reboots my phone always goes to the default launcher with no apps from my sd card and I have to wait to press the home button for LauncherPro to appear. I set it as my default launcher but it never loads when my phone is rebooted.
I was just recently (within the last hour) doing regular things on my phone (texting, internet , email etc) ad all of a sudden I got the shut down boot animation from my rom and my phone turned off. I went to turn it back on and my phone stayed stuck on the boot screen again. Now you can figure what I did again. I went through and did everything over and reloaded the rom and kernel. I am still having the same problems with the launcher as I did before and I have no idea whats going on. I just want to avoid going through this again. Anyone have any idea what the heck is going on???
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
I'm also no expert but after running into constant force closes and random problems with launcherpro I decided to go with go launcher and its been a great switch for me.
Sent from my SCH-I500 using XDA Premium App
Hey guys, still no luck. I don't know what it is. I wish I knew more about hacking and doing all this kind of stuff
Try flashing a PBJ kernel!
can you get into CWM with the three finger salute?
[hold down the two volume buttons and the power until your phone reboots and you see samsung then let go]
See if you can mount as usb to get the kernel on there, if that doesnt work go to staples get a microsd card reader [under $15] and toss the pbj on your card then flash that.
When i was on EF and Comm Rom my phone didnt like the OTB kernels
Good Luck!
My recovery menu works fine and I can boot into it from the ROM without problem. My problem is that when I reboot the phone the ROM's default launcher is setup (and it is missing all of my apps) even though I set Launcher Pro as my default. I have to reset all my defaults in Launcher Pro every time my phone is turned off or rebooted. I would be on PB&J but I like to overclock my phone and PB&J doesn't support voltage control and I don't want to pay for and overclocking app.
efan450 said:
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
From what I've read many people have disagreements on whether 2.5 supports Edify or not....because a lot of people have success with it while others don't so I really don't know. Its never given me problems in the past. I actually had more problems with 3.X recoveries (It wouldn't allow me to make nandroid backups and other things that were essential) so I flashed 2.5 and it worked perfect (again I've read about people having the same problems with 3.0 versions of CWM).
Okay what I've found is that this has nothing to do with Launcher Pro. I downloaded He Launcher and when I reboot my phone everytime it asks me to pick a default launcher. And when I'm using He Launcher, none of the apps on my SD card show up in the app drawer (they don't show up in the default ROM launcher either, they only show up in launcher pro)
Efan450 I tried what you said and it worked! I odined a 3.X recovery and wiped everything oof my phone then flashed the ROM and kernel and everything is working perfectly now. Thank you very much!!!
Guyz I recently install jb v5 with phantom kernel. I had some problems with led,sound and battery.. I was charging the phone everyday..I install v4 but same any help?
Sent from my ST25i using xda premium
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Re
MagicMagicD said:
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Click to expand...
Click to collapse
Let me tell you exacly.. I had a problem with the phone .. About led so i decide to change the version and use v4 .. But i recharge it full and i had it on my desk w/o using it for 3 days. The battery was at 40 % and i use it only 1 time for 1 call .. Nothing more...
I flash the kernel wth flashtool. Wipe everything.Install Jb wipe cache and then use the phone. Wait for power off buttom then open again..
I don't know what is the recovery mode btw.. I search it but i didn't find something usefull .I still don't know if i will use Jb Unofficial yet...
I haven't tried v4 of that ROM but I can say for sure that the LED bar doesn't work very well on V5, at least nowhere near as well as DevSwift1's V3 ROM with the latest Phantom kernel.
It does seem to be quite good on battery though; I'm on 1 day, 12 hours uptime with 47% charge left, although I don't use it a whole lot to be fair -- mostly just for music during the day.
I guess you must have used a recovery to flash the ROM zip file... as in CWM (ClockWorkMod)? The Phantom kernel comes with one installed; 1.0.7 has CWM Touch whereas 1.1.0 (the latest version) has a non-Touch version.
The only thing I can suggest is that you try reflashing it again; I'll tell you exactly what I did...
Using Flashtool, put Phantom kernel 1.0.7 on the device and then go into CWM Touch by restarting the phone and repeatedly pressing the Volume Down button when you see the LED bar light up.
Once there do a wipe of data and cache and then go in to the advanced menu and wipe Dalvik cache too.
Next go back to the main CWM menu and flash the zip, then reboot and wait for the phone to start up (should take a while).
Once it has settled down restart it and let it start up again (should take less time)
Finally, use Flashtool to put the latest version of the Phantom kernel on, restart and you're done.
With all that said, I expect I'll be going back to V3 of DevSwift1's JB ROM this weekend as although it's not quite as smooth as pipi14's ROM, the LED bar does work a lot better and for me that is quite important.
Good luck, keep us informed how you got on.
A
Thanks a lot for the informations mate. You help me a lot . But i'm the only one who have this problem with led and battery?
What Jb version you suggest me to use? (link )
What kernel you suggest me to use ? (link)
Any other good apps who will help me ?
Again Thanks a lot .
Btw what is "recovery flash" . I read at pipi's site flash in recovery. What exactly is this?
I've personally tried two Jelly Bean roms:
DevSwift1's V3 ROM (it's now up to V4 which is based on an Xperia Go firmware and has lower-res graphics and some other issues compared to V3, which was ported from the Xperia P).
link
pipi14's V5 ROM (which you have tried and are currently using.)
link
As for kernels I've only used the one that came included with DevSwift1's V3 ROM and Phantom kernel's from v1.0.7 upwards. I know that a number of people have used the Experimental v8 kernel with success on JB but it looks to be more complicated than Phantom.
Experimental v8 kernel
Phantom kernel
From my own experience I will say that I think pipi14's V5 ROM is smoother but I can't get the LED bar working how I want and although it still had a few issues on DevSwift1's V3 ROM it was definitely better.
As far as apps go, it seems the fewer apps the better if you want to stick with JB on your Xperia U -- it doesn't have enough memory and the more apps you have running the worse it will be. Task killers will not help and will probably end up draining your battery more than they help.
A custom recovery is basically a low-level program that you can use to flash new kernels, ROM's and other things on to your phone. ClockWorkMod (CWM) is the most common but others are available. You must have used a recovery to flash JB to your phone before, and if you have a Phantom kernel it comes bundled with one. To get in to recovery mode you need to restart your phone and then press the Volume Down button when you see the boot logo (e.g. Phantom).
a
That's the reason why sony will not send the updates to official JB version .
I will not use Jb now . If they fix it about the bugs i will use . Thanks for the info mate
Btw i use something custom like tera check this http://forum.xda-developers.com/showthread.php?t=2141726&highlight=tera
It's nice based on the ICS w/o so much battery drain and leds bug. I suggest you use this .
Today I tried downloading multiple roms onto my HTC incredible 2. But each Rom I installed either looped on the HTC screen or wouldn't install. I tried Cm 10.0 , 10.1 and 7.2. Also I tried paranoid Rom and that also looped. Only roms that worked were the stock roms I downloaded. But only the stripped version of one stock Rom. When I tried the unstripped version which included rooted apps and tweaks the Rom worked fine with one exeption; the WiFi bugged out, constantly turns itself on and off and didn't recognize my WiFi. I rooted my incredible 2 through a website that had a full tutorial that made me unlock my phone through a key and using the command propmt to flash my phone. I'm not sure what I'm doing wrong. I clear everything including cache and davsik or whatever its called before I install the roms. I use the clockworkmod booter thing (holding power and volume down button). I clear everything then install from SD card. I just want jellybean 4.2.3 or anything above 2.3.4. If you guys need more details about my kernal or anything else just ask. I'm on my phone right now so I don't have all the info off the top of my head otherwise I would have written it down. If you guys could help that would be awesome. Thanks in advance!
i know you cleared everything but have tried formatting /system and /data
Here's a Stockish ROM for your N915P. This ROM has Knox, Sprint ItsOn, and secure storage removed. Nothing else was done to this ROM. I'm new to the Note Edge so I may upload patches to remove any other traces of Knox or ItsOn or optimizations I happen to find while making my own ROM.
Prereq: OG1 Baseband. Download it below.
Modified stock kernel (BeastMode Stock): Kernel modified to allow root by disabling "Root Restriction in defconfig"
Download
MD5: 75bd507e3b4296a128f1c0c48fd2359c
Version 1.1: Enabled many TCP Congestion options via defconfig. Added init.d ability via ramdisk.
Odex:
Download
MD5: 59d544ef6a4bc12d969f4efd9577d36d
DeOdex DEBLOATED:
Download
MD5: 00b5246b9c2074e7ff04f6af2bad1ec2
OG1 Baseband:
Download
MD5: 3bc88209d60117fb573e0f5a2e50f4e9
Patches and fixes:
None yet.
[size=+3]DeOdex note:[/size]
The first boot time for this DeOdex ROM is very long. Approximately 5-8 minutes. Your phone will get hot as the splash screen remains on the yellow Sprint boot animation. I recommend keeping your phone in a cool environment while this is happening. The heat, if not properly checked, can make boot times even longer as the system throttles speed in order to deal with the heat. This doesn't happen on the Odex version.
[size=+3]Install instructions:[/size]
-Are you currently on the OC8 bootloader and would like to stay on it?
--Simply flash the baseband with Odin, and the ROM.
-Are you on the update from OTA or flashed the OG1 TAR?
--Flash kernel only.
-Are you one of the unlucky ones to take the OTA and hose your system trying to root and are now on another ROM?
--Flash ROM only.
-Are you on any build after OC8 but not the current OG1?
--Flash the baseband and ROM. Bootloader is optional and not available in this thread as of yet.
Wiping is only necessary if you are coming from a different base, such as AOSP/CM. If you are coming from a touchwiz ROM, wiping isn't needed, but won't hurt.
Changelog:
9/5/15: Initial Release.
Kernel source code: Download
Thanks, will flash tomorrow.
Thank you so much freeza!! Patiently waiting for the deodexed version and for the baseband.
Added modified stock kernel v1.1 and baseband.
Freeza if I'm on 5.0.1 still just flashing the baseband may give me better service ? Technically...
Downloading now still waiting on the deodex will play with the stock to see how it is thanks
Ok, flashed rom, kernel, and modem. Took a while to boot but all is running well at the moment. Thanks for supporting our device!!
DeOdex uploading....
What What!!! By far the best developer on a Samsung!! Thank you so much for your hard work brother!! Real Talk, i still have your rom on my Note 3! It runs flawlessly!! XD
Get your DeOdex on, guys! ;D
Thanks so much for this!!! I love the separate edge screen and have no reason to "upgrade" to the Note 5
Thank you freeza NICE WORK WITH THE KERNEL
When I saw you had been requested to come help this phone achieve root I knew great things were going to come to those who waited. I've had other devices where you were there to help gain root and again you came through. I purposely didn't take the OG1 update because I knew in time this device wasn't going to be ignored. IMO it is the best NOTE device out there and it will be mine until they make a NOTE EDGE 2 (With SD card and removable battery). Thank you for the quick response and the hard work you do to make this happen.
Cant get either one of them to boot. Both the odex and the deodex wont boot, they both flash fine and then after the phone reboots it stays on the yellow sprint screen Maybe for up to a minute then reboots and it cycles that way. Never boots. I've tried not wiping/Factory restarting as well as wiping/Factory resetting. Have also tried formatting through TWRP to no avail. Have also tried flashing the kernel and wiping caches after flashing but Nothing is working. Have also flashed the baseband.
Im currently on OF6 if that should matter.
Edit: md5 Sums have also match up. Have downloaded both from my phone and a pc to no avail.
Edit 2: tried both TWRP 2.8.6.0 and 2.8.7.0. Also tried clockworkmod recovery and that didn't work either.
I had success but it took some time. I downloaded the deodexed debloated rom, the kernel, and the baseband. I had a method to how I wanted to do this and here is how i got there.
I was running OC8 rom rooted.
1. I odened the baseband tar file and rebooted. But unfortunately it bootlooped on the initial splash screen (note edge) so
2. I ran TWRP recovery and installed the kernel file. Rebooted phone and it ran fine. I looked at the settings about phone and saw that the baseband and the rom all said OG1 but i had not installed the rom yet. So i figure it was a trick to get the baseband to install. So
3. I went back into recovery. Wiped dalvik cache and regular cache and installed the new rom. It installed fine and i waited the length of time for the initial boot up. But this time as it was "Android is starting" it rebooted and got stuck on the sprint splash screen and kept randomally vibrating. Having the ability to remove the battery
4. Rebooted back into recovery, wiped everything including internal storage, and reinstalled the deodexed rom. It installed fine and went to the initial startup screen where it tries to initialize and it rebooted one time, back to the initialize screen but continued without a hitch.
I currently am running OG1 5.1.1. With root.
At times during setting up the phone it would randomally vibrate for no reason...short bursts...but it hasn't yet again rebooted, restarted, or crashed. It is faster from what i see. Probably because there are almost no google apps installed. I've had to install chrome, youtube, and maps. But all seems fine. My signal and speeds are the same so the baseband didn't do much to change that. But so far so good.
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
I did try to install over my odexed OC8 with this new rom but because there is so much different about the files that are installed IMO formatting the phone was the only way to get this to work.
---------- Post added at 12:16 PM ---------- Previous post was at 11:30 AM ----------
One final thing just in case it isn't known: when you wipe everything in TWRP, excluding external storage, you have to restart the recovery before trying to install a rom. It will say you have no OS installed, but you are restarting the recovery not booting a rom, so that's fine, but you do lose root status when wiping. So the next screen gives you the ability to gain root again, but you have to restart TWRP to do that. In the past i tried to figure out why installing after wiping didn't work, and 99% of the time it was because of that. I also don't like installing new roms over older roms (even if they are the same base (touchwiz to touchwiz)) because i feel I would spend more time troubleshooting why something isn't working instead of just starting over. I find less hassle doing it this way.
I odin baseband .tar file, than reboot it to recovery, and flash kernal and odex room at the same time, saw some red messages when kernel was flashing, than odex rom was next but it was successful when it was done. (I did not know if kernel falsh ok so i reflash kernel again) reboot to system and after the android system updated all its ok. No problems so far.
Oh and i inclided the supersu at the same time i flash kernel, odex rom and supersu.
1. Odin baseband tar file.
2. Flash kernel, odex rom and supersu.
3. Re-flash kernel.
4. Reboot to system and profit.
(Maybe i did un necessary steps, but its working. )
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Johnny Halo III said:
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Click to expand...
Click to collapse
Just starting to have random freezing. And not able to select my apps froms the edge screen, i can only scroll through it. Will remove all the app shorcuts and re-add tham again.
**update 1.
I removed all shorcuts from the edge screen and added them back, all work but some i have to select them a few times before they open.
Maybe i have to reflash, reset, clean and wipe.
**update 2.
Clean install of odex rom, and kernal 1.1.
No more lagg but the edge screen does not work properly. Not able to select and open some of the favorite app shorcuts.
**update 3.
Factory reset, cleaned and wype, odin sprint lollipop update (uf something), downloaded OG1 update. Installed all apps from scratch. And the edge screen does not work. I can scroll, side to side, up and down, but when i select an app it does not open it.
** update (last one)
Foud the code to test the phone hardware.
*#0*# on dial screen. Tested all and it came out good. But i notice that some how the edge screen its not as whide as it used to be ( like its more to the right of the phone) so where i use to touch to select an app its now more to the right emd of the edge, thats why i was able to scroll but not select the app.
Its all good now. Now second round of flashing.
Will give it another try at the room.
Thanks Freeza and sorry about the problems i had and hopefully did not cause anyone from not trying this great work pr yours.
I left all the problems i had so tje next person trying this room does not get discureged from trying. But allways fallow direction.
:thumbup:
** last update
After setting and resetting, flashing and un-flashing, rooting and un-rooting. I can finally wrote that all is good. Running latest lollipop 5.1.1 and freeza's new 1.1 kernel, I can reprt that all is smooth as butter.
Thanks for the hard work.
Thank you so much for your hard work Freeza! So glad I'm finally running 5.1.1 on this beast :]
The ROM is working pretty well, but I have noticed that every now and then, the phone will be rather laggy. Turning the screen off and on again seems to fix the issue, making me think that the processor is being throttled while the screen is off (good) but isn't being sped back up when the screen is turned on..sometimes.
It's not a huge deal, but I was wondering if anyone was experiencing the same thing.
No issues here.
Starting on OG1 had to flash bootloader, kernel, deodex rom and supersu to make it stick. Two days now and battery, signal and speed seem improved.
Thanks freeza!