Related
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 am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:
Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks
I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?
I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)
Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.
Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.
Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun
touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.
Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.
Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app
Hi, first post here so please mind my ignorance. I recently rooted my Sprint HTC One m7 and installed the latest TWRP recovery. Since I found out that I have no /system write permissions and I wanted to use apps like the Xposed framework, I decided to flash a custom kernel which disabled the protections, because I didn't feel the need to get a new ROM. So, I am running the stock Sense 6 ROM on 4.4.2 with the stock kernel 3.4.10-gf22c859 and S-On. I tried to flash flar2's ElementalX 14.12 for Sprint. I created a nandroid backup and cleared my cache and dalvik. Then I flashed the kernel, and the install went fine. It said it was successful, and once again I cleared the cache and dalvik. I rebooted my device, and it started up, updating all the apps. and I rebooted the device again like the installer had said to. However, when I tried using the new features like logo2menu nothing happened. I checked what my kernel was in the settings, and it had not changed. The only thing that did change on my phone was the fact that all of my paid apps said they had not been installed, and when I did try to install them, I would get an error saying my SD card did not give them permission to do so (or something similar to that, I don't remember the exact message). I thought that it was a problem with the kernel, so I restored to the nandroid, and flashed the Kangaroo kernel the same way I did with ElementalX. Once again, the set up process went fine. When I booted my device, I was greeted with the same results as before. Apps updated, kernel didn't change, paid apps gone. I am really confused with what is going on. I feel like I am missing something obvious (This is my first time installing a kernel on an Android device). Any help would be greatly appreciated! Thanks is advance.
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
NotReallyKnown said:
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
Click to expand...
Click to collapse
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
simms22 said:
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
Click to expand...
Click to collapse
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
NotReallyKnown said:
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
Click to expand...
Click to collapse
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
simms22 said:
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
Click to expand...
Click to collapse
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
NotReallyKnown said:
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
Click to expand...
Click to collapse
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
simms22 said:
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
Click to expand...
Click to collapse
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
NotReallyKnown said:
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
Click to expand...
Click to collapse
because most follow older "proper" ways to flash software. and the proper way to flash, and to make sure all is working as should, is to clean flash. dirty flashing can cause issues, but its issues that are usually fixable. the problem is that most dont know that, or how to fix. 99.99% of issues caused by dirty flashing are caused by corrupt or incompatible data. where a data clearing for that particular app will usually fix. anyways, roms based on the same sourcw, and not far from what you are running, you can dirty flash. roms that have a different base than what you are running, you should factory reset first.
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
wangdaning said:
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
Click to expand...
Click to collapse
issues from dirty flashing do not appear weeks later, dirty flashing issues show up right away. all dirty flashing issues are caused by data, whether corrupt or incompatible. other issues are blamed on dirty flashes, but arent the real cause. issues like app fc's are the most common, and very fixable. the only issues that arent fixable are when you dirtt flash two completely different roms that are based on different sources, or different android versions. i have dirty flashed every single thing ive flashed onto my n5, since december, no issues. the only issue i had dirty flashing my n5 was dirty flashing L over rastakat. and the issue was minor. everything worked great except the status bar didnt go down all the way. why did it mess uo? because of incompatible data from rastakat with the new status bar code in L.
You are correct Simms, but it must be noted that you dirty flash the same version, for dirty flash to work. If just updating a rom it is usually fine, but if they have made a major change then it is not.
Have no tales to tell of my N5, but my Samcrap S3 (cracked the screen and she died, then I bought this bad boy ) had issues that would appear later. Maybe due to the dirty flash. Who knows, that is why I mentioned a clean flash rules that out.
Anyway, backing up everything leads to a carefree life!
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.