Related
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
Hi there
So i tried to install Steve's Kernel, but my device is in Boot loop now... (my device is international, it has Physical home button....)
i did some search around and found this : http://forum.xda-developers.com/showthread.php?t=1531850
but i am not sure if this is the solution to my problem...
i can go to recovery mode and download mode by the way
so i am gonna assume i am not completely ruined....
Any ideas guys?
porkho biv9
after my first flash I was in the same situation as you. flashing the stock rom was the only solution.
But in my case it was no problem, because I had nothing important on the device. It was almost fresh out the box.
I've the experience, that doing a full wipe causes a higher possibility of getting bootloops. So I only clear the dalvik cache after flashing roms/kernels. If it boots -->everything is fine.
Do you have a backup? CWM or titanium backup?
Hi
Unfortunately i don't have any of those....
do you think that link i gave in the 1st post can be useful?
Thanks in advance....
Yes, I downloaded the .pit and .tar.md5 file and did everthing of these steps:
Flashing Time
1.3: If your device is bricked and you can go to download mode:
1.3.1: Download one of the roms (according to your device)
1.3.2: Open odin, take the .pit file and put the rom .tar.md5 in the PDA SECTION
1.3.3: Before flashing, ensure re-partition is checked.
1.3.4: Flash, when the flash is finished your device should reboot.
1.3.5: When you device reboots, you will be in recovery with red errors which are saying mostly of the time: Can't mount... To erase these errors, WIPE DATA.
1.3.6 Reboot and enjoy your restored device!
Click to expand...
Click to collapse
I had no backup too and tried everything. This (zaclimon's thread) was my last hope after 2 hours of searching and it worked.
Hey !
ah, did i read that right? Re-partition HAS TO BE CHECKED??
and do you recommend installing Steve's Kernel after i hopefully returned my device?
yes it has to be checked in this case.
I had terrasilent 1.1 and klassik rom for 2 days but I had a lot of freezes, so I flashed the stock rom 2.3.6 and steve's kernel because the main reason I wanted the SGP4.0 was the combination of wolfson DAC+wolfson+poweramp.
If you are happy with music only, than this is enough.
But now I'm using my device more often (GTA 3 is on sale right now) and flashed terrasilent v1.2 two days ago. Now I'm waiting for the next version of StratusROM and will give it a try. Because sometimes I am not completely satisfied with the performance (sometimes) and it often wakes up while deep sleep causing more battery drain than usual.
natkingcole said:
yes it has to be checked in this case.
I had terrasilent 1.1 and klassik rom for 2 days but I had a lot of freezes, so I flashed the stock rom 2.3.6 and steve's kernel because the main reason I wanted the SGP4.0 was the combination of wolfson DAC+wolfson+poweramp.
If you are happy with music only, than this is enough.
But now I'm using my device more often (GTA 3 is on sale right now) and flashed terrasilent v1.2 two days ago. Now I'm waiting for the next version of StratusROM and will give it a try. Because sometimes I am not completely satisfied with the performance (sometimes) and it often wakes up while deep sleep causing more battery drain than usual.
Click to expand...
Click to collapse
People were experiencing bootloops with steve's kernel. Right now I'm using the latest terrasilent with stratus and I don't have any bootloops. (and you can change to ext4 with terrasilent)
Hi there
you guys mind giving me link to that Transilblaba thing ?
Thanks in advance...
[Q] What kind of "loop" do i have? Happens with AOKP devil and glitch ICS and CM10
First I know the phone is not bricked. I can and have repeatedly ODINed to stock EH03, remembering to atlas and repartition as per droidstyle's guide. The problems begin when I go through the rest of the guide section 4, to get and ICS AOKP rom running. (This is staging for my question to be complete. Question at bottom.)
For whatever reason the phone was stuck to only boot into (red) recovery. I had the AOKP rom MS6-devil before and I think flashed another different devil kernel over that. The phone has been completely stable for months now. I tried data wipe/reset and wipe cache, and dalvik too. It still only rebooted to red recovery (sorry don't recall the exact version). This is when i decided to ODIN and start fresh.
Maybe some side questions. Is it ok to flash different devil kernels on the devil kernel rom? I assume yes but I just needed to run through my check list. When I ODINed back to stock did that automatically restore the phone to a stock kernel as well?
So the phone ODINs fine every time and ODINing cmw4 for CW7 and GB bootloaders too. (BTW when i flashed ICS rom several month back i dont think the guild had anything about ODINing bootloaders. Is this new?). 3 finger works and I'm in blue recovery 4, i wipe data and dalvik (I've done this more than 5 times some i also tried a cache wipe with same results).
What kind of boot loop is this?
I flash the ICS rom zip that i want and it starts but the status bar on the phone make a small amount of progress then goes black, reboots to the flash the Samsung logo then goes to some splash screen that shows Icy Glitch Kernel V14 if i try the AOKP M6 official, or a splash screen of Devil Kernel if i flash AOKP M6-devil or even with CM10 i see the splash screen of cyanogenmod. If i let the phone sit on the screens for a long while all i see is a continual booting to these splash screens.
I have mucked something up with the kernel and i thought ODIN would reset that each time. If I can know what kind of boot loop i face i can go to find the right threads or make a post in the right place to get this resolved.
Actually it's normal for that to happen, after you start the install it should reboot the phone to an updated recovery and continue the installation from there. At least that's what it did for me when coming from stock. How long did you wait? Are you getting any errors? If you're still using the stock sd card that could be your problem right there. Also, I highly recommend trying a JB rom, ICS is pretty stale at this point. AOKP just released JB Milestone 1
Good tips. I didn't know that's what it should look like. I was flashing for many hours and waited 20-30 minutes. The only happenings on screen were the splash screens flashing occasionally as if the phone were looping. Im guessing now that's normal in the flashing process. I've flashed the same roms before months ago and probably the process on screen I just forgot. Ill try again later when I have time and try some jb action and report back.
When going from stock to ics are you first flashing ths build 2? There are many versions of devil available some are built for ics and aome for jb only. It's important to know which one you are dashing cause the jb devil kernels have a specific partition layout needed to get jb to run on the fascinate. I could be wrong but anything higher than 1.5.xx is jb specific.
The devil rode a unicorn named jelly bean
forsakenone said:
When going from stock to ics are you first flashing ths build 2?
The devil rode a unicorn named jelly bean
Click to expand...
Click to collapse
You know I think that is it. I just blanked on doing that. I have build 1 and 2, b/c sometimes one works and one doesn't. I think I used 1 this time, but the first time I flashed ics i used build 2. Any way thanks. I am checkin out jb now too. cm10 is working great.
You didn't miss the step (to flash Build2 between EH03 & AOKP/CM10), the step was missing (temporarily) from the guide because some have found it to be unnecessary. I had the same bootloop as you when I didn't go through Build2 on the way to AOKP. Seems like the phone attempts to boot normally rather than into recovery to finish the installation of AOKP/CM10, and can't because it is midway through the installation. So did you state you had the problem when flashing CM10 as well? That's interesting, since some can skip going through Build2 and some can't. I thought maybe AOKP required it and CM10 did not... still trying to figure out what is different between phones that require it and those that don't.
Yeah I had it happen on cm10 too. I tried again but only flashed cm10 and no strange looping like I described. But I didn't flash any build before cm10.
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
l330n said:
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
Click to expand...
Click to collapse
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
captemo said:
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
Click to expand...
Click to collapse
Cool, thanks for the tips, ill try them once i get home in the morning from work.
I saw someone recommend twrp 2.6.1.0 (still hangs), at first I had 2.6.3.0 (newest i believe) and still kept hanging on splash
Do you know which uber kernal is the correct one for that rom or is it just the one included in newest pacman rom 4.3?
I may just try out carbon and revolt, seems like more people running those roms. I was messing with some of the color setting in PA and phone locked up on me and it was weird, had like a greenish screen that got brighter and brighter and brighter eventually i just shut it off, it was fine when i restarted. Im not too worried about changing the colors really, i was just tryin it out.
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!