Related
HI all,
I've flashed CWM5.5 from the recomended thread and installed Cyanogen 9 Alpha 1. Unfortunatly the phone seems to boot up but does never leave the boot animation screen (yes I've also flashed gapps after cyanogen).
Anyone can identify this pattern? On a normal device I could hook it up through a serial cable and try to debug the boot... Eventually how can I do that with a I8150?
Well, any help would be most welcome. I'm totally available for testing and I do have some experience with Linux even at a very low level/system space.
Install
Use CWM5.
Warning: Only use this recovery to flash CM9. Otherwise, you risk bricking your phone!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM9 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
read it thoroughly ...
1st you must flash update*.zip
2nd gapps*.zip
that just about it ....
what is your current kernel ?
That was pretty much it... I've restored not the original operator crap ROM, but instead the Value Pack ROM.
CyanogenMod9 seemed to install ok, but just looped and the phone didn't finished the boot. I'm not really sure on what happened. I'm just finishing restoring the stuff
I'm guessing you didn't wipe data/cache.
I did a factory reset, but sure, it might not have wiped the whole thing... Going to try again.
@argo68
True mate, the issue was not wiping the user cache. I've wiped the cache now from ClockWorkMod and it worked ok. Takes some time to boot compared to the stock samsung ROMs but it works fine
Anything you need tested ? I can most likely help.
I do have a problem with apps though, for example, GMAIL doesn't show the body of the message... as you can see on the screenshot, but I guess this is a app related issue maybe?
http://susepaste.org/images/39081870.png
After a reboot somehow it boots a bit faster and the gmail app is now displaying the body of the email and it seems a bit faster...
Good work, gonna ride this for a few days and see what happens.
@argo68
If you need beta testers, let me know. I'm off work this days but can't wait to get into my lab and check this stuff deeper
@argo68
he is arco68
just in case he takes offence, which I don't believe he would
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
ketheriel said:
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
Click to expand...
Click to collapse
reAdy for some BEAR ????
do you actually mean bear or beer ??
chocolemon said:
reAdy for some BEAR ????
do you actually mean bear or beer ??
Click to expand...
Click to collapse
Maybe it's the Nordic ascendance. They fight a bear with one hand while holding the beer with the other.
Hi I'm using this cyanogen mod for quite a few days now. The back side of the phone is always warm and the battery is drained very fast. Anyone have this similar problem?
I'm sure that I install the ROM correctly as i cleared everything on the phone with CWM 5.0.0.4 before and after. (Phone data / Cache Partition / Dalvik Cache / Battery Cache)
Any help would be appretiated
No such problem here. You should use an app to check what frequency the phone is running at in idle, and also how much load there is on the cpu.
Let me start of by saying I am a Noob. I have been learning about the root and custom ROM process for about three weeks now. I have succesfully flashed the latest PacMan ROM and the latest SlimBean ROM. Both times I have reverted back to my Stock ROM. Everytime I flash a new ROM using TWRP, I wipe the Cache, Davlik Cache, do a Factory Reset, and Wipe the ROM. This leads me to believe I getting a clean flash, and everything seems to go smooth with the install. I have no problems with the inital boot, and it usually happens pretty quick.
I understand that each custom ROM has some great new features, but it hasn't out weighed that the battery life and speed (responsiveness) is still better on the Stock ROM. Is the reason I am seeing this is because the ROM's I have tried are 4.2.2 versus the stock 4.1.1? Is there something obvious that I am missing? If it appears that I am flashing correctly, is there a ROM that is should try the will improve me battery life and speed?
Thank you!
a full wipe also includes format /system.
how long are you using these roms before flashing back or trying a new one? the software takes a little time to settle in so if you're hopping onto a new rom every few days, you may not see the best that each rom has to offer you.
xBeerdroiDx said:
a full wipe also includes format /system.
how long are you using these roms before flashing back or trying a new one? the software takes a little time to settle in so if you're hopping onto a new rom every few days, you may not see the best that each rom has to offer you.
Click to expand...
Click to collapse
Do I format the internal memory of in TWRP? After doing some that is TWRP still functional? I have been afraid to do that because when I think of formatting it wipes everything. My thinking was the phone wouldn't operate.
Can you walk me through it in TWRP?
Thanks!
Huskerjeff said:
Do I format the internal memory of in TWRP? After doing some that is TWRP still functional? I have been afraid to do that because when I think of formatting it wipes everything. My thinking was the phone wouldn't operate.
Can you walk me through it in TWRP?
Thanks!
Click to expand...
Click to collapse
as long as your recovery is current, you have a backup (nandroid) and you have the ROM/gapps zips on the device, you're good to format (wipe) system. that erases the OS and allows for a new, clean install.
make a backup (if you dont have one)
wipe data/factory reset
wipe cache
wipe dalvik
wipe system
flash rom
flash gapps (if required)
reboot
let device sit a few minutes and reboot again.
Theres more to it then just flashing and having a better running phone. If that was it everyone and their mother would do it. You need to learn about the system and ROM you are operating on and tweak the settings to optimal performance for your phone, and more importantly to your liking.
Every phone is different. If one rom works great on one persons phone it may not run so good on another persons. You have to learn and have enough know how to be able to set the phone up in a way that runs good for you. While it may be frustrating at times I guarantee if you take the time to try out a couple different roms for a couple days at least, and play around with the settings until you know what they all do and why they are there and how work for or against your goals you will end up with a phone that you enjoy using on all levels. Features, performance, looks, etc.
Hope this helps, and good luck finding your custom rom 'sweet spot'
Try AxisM RLS18 rom its a great rom with so many features to it.
xBeerdroiDx said:
as long as your recovery is current, you have a backup (nandroid) and you have the ROM/gapps zips on the device, you're good to format (wipe) system. that erases the OS and allows for a new, clean install.
make a backup (if you dont have one)
wipe data/factory reset
wipe cache
wipe dalvik
wipe system
flash rom
flash gapps (if required)
reboot
let device sit a few minutes and reboot again.
Click to expand...
Click to collapse
TeknoGodz said:
Theres more to it then just flashing and having a better running phone. If that was it everyone and their mother would do it. You need to learn about the system and ROM you are operating on and tweak the settings to optimal performance for your phone, and more importantly to your liking.
Every phone is different. If one rom works great on one persons phone it may not run so good on another persons. You have to learn and have enough know how to be able to set the phone up in a way that runs good for you. While it may be frustrating at times I guarantee if you take the time to try out a couple different roms for a couple days at least, and play around with the settings until you know what they all do and why they are there and how work for or against your goals you will end up with a phone that you enjoy using on all levels. Features, performance, looks, etc.
Hope this helps, and good luck finding your custom rom 'sweet spot'
Click to expand...
Click to collapse
Update: I searched for a ROM using a 3.0 Kernel and found one with great battery life reviews call "Sons of Android". I installed it using TWRP 2.4.4 with the directions quoted above, and everything is great execpt for two things.
First, I always seem to get mirrored data. There is a Emulated folder and an SDcard0 folder that appear to have the same data. I have searched in the forums and found that it is an issue, but havent seen a solution.
Second, Netflix is draining the battery twice as fast as the stock 4.1.1. Before I could watch 45 minutes with 10% of battery and now the same 45 minutes is taking 20-25% of battery. Is this a 4.2.2 problem. It has been a problem on all the ROM's I have tried.
I am going to stick with this ROM for a while beacuse other than netflix the battery life is good. Just about the same as my stock ROM.
Thank you for all of your help for the Noob.
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Anthonyl123 said:
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Switch ROMs.
Maybe your phone just doesn't play nice with the Hyperdrive ROM. Try out a new one, or do a clean install of it and see if that fixes it!
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Mr._Happy said:
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Click to expand...
Click to collapse
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
topherk said:
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
Click to expand...
Click to collapse
Ive done options 1 and 2 but here is what I have installed on my phone
When I ran the aroma installer I chose the option to run a full installation with the devs choice of mods and stuff etc. So I have the tw launcher installed along with the multiwindow mod and pretty much everything else.
Sent from my SPH-L710 using xda app-developers app
hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
danny_dv8 said:
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
Click to expand...
Click to collapse
What version of TWRP are you using? I heard 2.6 may have some issues?? Also, did you do proper wiping procedures, such as factory reset, cache wipe, dalvik cache wipe, etc before modding a new ROM? Which new ROM are you flashing, and did you flash a new radio with it?
danny_dv8 said:
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
Click to expand...
Click to collapse
First, what is it flashing procedure? I should be downloading rom to ur external/internal SD card, then boot to recovery and make a backup of data, boot, and system partitions, then wipe dalvik cache, system, data, and cache 3x each, then go back to main menu and choose install, find the rom and flash it, if aosp also flash gapps, then reboot, shouldn't be having any issues if u follow that procedure, and upon first reboot let the phone sit for around ten min or so to let everything settle, the first few days or so things will still be settling in so give it 3 full battery cycles before u start guaging performance, I'm on twrp 2.6 and never had an issue yet an I'm a flash addict, u could also try reverting to stock with Odin and then starting over, Odin give a more complete system wipe so u may have some corrupt files somewhere, but like I said if u follow that procedure u should be ok
Sent from my SGH-T989 using xda premium