I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.
I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working. Here is my phone info:
> Model #
> SGH-I997
>
> Android
> 4.2.2
>
> Baseband version
> I997UCLB3
>
> Kernel version
> 2.6.35.7-I997UCLB3-CL9997492-g431d68f
>
> CPU
> ARMv7 Processor rev2 (v71)
>
> ChameleonOS version
> 0.7-20130426-unofficial-infuse4g
>
> Build date
> Fri Apr26 16:05:35 AST 2013
>
> Build number
> cos_infuse4g-userdebug 4.2.2JDQ39
> Cng.andros11.20130426 test-keys
robertmlangdon2 said:
I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working.
Click to expand...
Click to collapse
You mean to say you cannot boot into CWM recovery and flash a different ROM? Interesting. I have an HTC, and the steps to rooting it are in a different order... that after unlocking the bootloader, you install CWM, and then optionally root the stock ROM with the SuperUser package (those who don't do the last step are usually flashing a ROM instead of mucking around for another second with the stock OS).
SU shouldn't be needed for custom recovery. But maybe Chameleon does something weird like not give you a custom recovery you can boot into? If that's the case, you could pop the device into download mode and go back to stock with Odin, effectively starting from scratch.
still need help, thank you.
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
robertmlangdon2 said:
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
Click to expand...
Click to collapse
If you are unable to get into ClockWorkMod recovery (hold Vol-Up+Vol-Dn keys while pressing Pwr button) and have it do anything (so your wipe, install, gapps, dalvik - that process would be called flashing). Then I would Odin back to stock.
For this, you would need to get into download mode. IIRC (just sold my Infuse), it is (with the device fully turned off) hold both volume buttons in while inserting the micro usb cable (that is subsequently inserted into your PC). The ODIN program comes with the download packages (hopefully), so extract the whole package, and run that.
Odin should pick up the phone in the first column as "COMX" (e.g. "COM5"). You are good to flash. To the right, there are PHONE and PDA buttons, click on each, and select the corresponding file (that was also in the package) for each (so PHONE will have something like PHONE.tgz.md5). Once both files are loaded, make sure re-partition is UN-checked, and press Start (or Go, or whatever the action word is). This will take a few minutes, but the COMX column should highlight green with "SUCCESS" in the end.
That's all there is to it. The reason why I'm shying away from SuperOneClick is that it was designed for stock gingerbread/froyo, so it has the potential of breaking something. Hope this helps.
EDIT:
Alternatively, you could try pushing su to the device with adb (depends on how you lost root):
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
adb push su /system/xbin/
adb shell chmod 06755 /system/xbin/su
... with this file (extracted).
Source (with mount point changed)
new problem
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
robertmlangdon2 said:
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
Click to expand...
Click to collapse
I wouldn;t suggest another phoen is things are working well genrally. The problem could lie in the GApps package or the ROM itself. I use the PA Gapps package. If you are having rouble with that one, try from a different date. Just wipe dlavik in between to prevent any nastyness.
If it still persists, try another ROM, like Carbon.
tried installing the new gapps
So far, so good but I won't know for sure for a few days. I'll keep you up to date. Thank you
what version of android is carbon?
Do you have the link for carbon rom for Samsung infuse 4g? And what version of android is it? My phone runs better with those gapps but I am still getting the same problems. I will give it a try but if carbon doesn't work I am definitely going to have to just get another phone. So far I'm. 0-2 on custom roms for this phone. I thought cyanfox would of worked cause I got it off of xda, which really makes me think this phone has some sort of hardware problem but carbon has been around longer. So maybe it will work better.
Carbon is on XDA as well too, and it is based on CM 11 / Android 4.4 Kitkat:
http://forum.xda-developers.com/showthread.php?t=2137800
Hope this works for you... :fingers-crossed:
problems solved
It appears it was definitely a problem with the ROM. Phone has been operating 100% better. :victory: My cache needs to be cleared frequently and some minor problems with the Facebook back but when isn't there problems with Facebook lol. But as soon as I clean out the cache from my apps, everything is running like new again. I greatly appreciate your help. I can't thank you enough.
Was working great then more problems
Joel,
Carbon was running great for me but then all of a sudden android.process.acore has stopped kept popping up along with all sort of other things stopping then eventually GApps not working again. I have erased my contacts, Erased Media, unchecked all my Syncs, I have tried all sorts of other Gapps packages and even another ROM (cyanogen 11) and they work to begin with then the same problems keep coming back. Is it because I went from Gingerbread right to Kitkat? My phone hasn't worked for about a week now with me trying all different ways to fix it. Do I need to install Ice Cream Sandwich then Jellybean before going to Kitkat or do I just need to try even more GApps? I used to install new ROMs all the time but android has changed so much over the last couple years and when i had to get rid of my old phone and went back to my Infuse 4g the old ROM was just completely outdated and now I can't seem to get this right. The phone itself is still a great phone and I don't understand why I am having these issues. I factory reset, wipe cache, wipe dalvik, install new ROM, install GApps, wipe cache again, and wipe dalvik again. I usually don't wipe the cache or the dalvik until after the ROM and GApps install but just lately have been doing the extra wipe just in-case because nothing else is working. But that has failed too. You have been a great help so far and I can't seem to fix this on my own, so again I turn to you for help. Please help me figure this out.
robertmlangdon2 said:
Is it because I went from Gingerbread right to Kitkat?
Click to expand...
Click to collapse
It's possible. I mentioned this before somewhere, but this could be the after-effect of a small /datadata partition, which having a separate partition is standard in a KitKat ROM (at least for this phone). When it fills up, there's no telling what happens.
Both BeanStalk and CM11 have /datadata partition alternatives (the separate partition has been abandoned) built in. You may want to try one of those:
http://forum.xda-developers.com/showpost.php?p=55574460&postcount=3801
http://forum.xda-developers.com/showpost.php?p=56604749&postcount=593
Unfortunately I couldn't find something similar for Carbon.
Thank you!!!!!!
I hate to count my chickens before they're hatched but I truly believe that was the problem. Even Facebook works now. But I thought I had it fixed before then just under a week and it completely messed up and I couldn't even get it to work for a day after that. But it works now. I can't thank you enough. If you ever come across one for Carbon ROM please let me know. This is a good ROM but I liked Carbon better. Again, thank you Joel. :good::good:
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through evrything so far and I couldn't be more thankful. There may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through everything so far and I couldn't be more thankful. The phone might be fried and there may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
If you can get into Download Mode, I would Odin back to stock. Are you AT&T or Rogers? There are a couple recent threads in this forum with download links, although people have been having difficulties with finding the AT&T variety.
Unfortunately, that's all I can recommend. Good luck.
we'll see how this works out
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
robertmlangdon2 said:
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
Click to expand...
Click to collapse
Looks like you are all set for the files then.
I just PM'ed everyone who I've recommended those packages in the past. Hopefully I get a bite.
found a thread but need your help
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
robertmlangdon2 said:
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
Click to expand...
Click to collapse
I would recommend Option D for what you need, but AFAIK, the links on this page are dead.
If you go to the last page though, there is a link for Option C, which would work for your needs. Hope this helps.
I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
natboy said:
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
Click to expand...
Click to collapse
To make things clearer. Previous what ROM were you on? After your proclaimed (OTA), what was the ROM suppose to be?
I went from the Oneplus One CM 4.4.4 to the CM 5.1 OTA. Not sure why you're don't believe me..
I think I might have bad memory or flash or something at this point..
So since yesterday I've tried using the tutorials here to flash stock Kitkat with the same errors happening. When it boots up, I get a done of crashes on things like gapps and process.acore. I also tried flashing the stock Lollipop; both using the non fastboot and fastboot way. Every time wiping everything with all the same results. The only rom I've had some slight uptime with has been slimrom without gapps as there's not much running there. Once I add the gapps package to it, processes start crashing again.
Does anyone know of a memory/cpu/flash test I could try, or any other suggestions? Thank you.