Sorry to say but I'm parting ways with the LGOG. I bought myself a Nexus 4 instead now I need help solving a few issues before I sell it.
The guy who wan'ts to buy it has a few requests. He wants a pure google experience and the only rom that I think of is Vanilla Rootbox AOKP which is already flashed on the phone now and so far I think its the most stable roms for pure google for this phone. Every build I flashed I noticed that everytime the battery gets below 20% it won't charge anymore. No matter what outlet I stick the charger to. It will say " Connect to Charger" instead of charging.
I tried several chargers and same results. Only way I fix this is if I restore my nandroid back up and flashed an older build then update it with a new one.
I don't want this guy to buy the phone and call me back saying he can't charge his phone. This doesn't happen on stock rom and other roms I flashed. Only Rootbox. I've tried every other AOSP and Cyanogenmod roms for this phone. So far I don't like them. many bugs and some have weird pixel density. Rootbox would have been perfect if it weren't for that charging issue when battery drains low.
Also this guy knows about custom roms,but does not have an interest in even learning how to flash roms himself. He plans to use the rom forever.
If he wants to keep the same rom forever he needs it to be stock. No ifs, ands, or buts about it.
Sent via LG E970 with houstonn aokp 4.2.2
DeathmonkeyGTX said:
If he wants to keep the same rom forever he needs it to be stock. No ifs, ands, or buts about it.
Sent via LG E970 with houstonn aokp 4.2.2
Click to expand...
Click to collapse
So your using codefire X i heard its official now. i flashed it before,but the icons seem huge. Let me know how the rom is now. I would flash it right now,but I'm stuck at work.
I don't keep my signature updated. Presently I'm running the 5/21 build of CM by Shelnutt2 and it works fine, but in my extensive experience ROM's tend to gum up after months of use. If he wants rock-solid indefinite operation, then the answer is stock.
If dude won't take stock for an answer, I suggest loading it up with 5/21 CM, manually set 384mhz min freq and 1512 max freq in performance control, ondemand governor, and then make a nandroid of it.
After that, flash the stock 20j zip (not lgnpst), and make a nandroid and name it "STOCKROM" or something. Then if CM freaks out after some indeterminate quantity of time, then dude can boot to recovery and restore stock or the original CM10.1 that you loaded up in the first place.
DeathmonkeyGTX said:
I don't keep my signature updated. Presently I'm running the 5/21 build of CM by Shelnutt2 and it works fine, but in my extensive experience ROM's tend to gum up after months of use. If he wants rock-solid indefinite operation, then the answer is stock.
If dude won't take stock for an answer, I suggest loading it up with 5/21 CM, manually set 384mhz min freq and 1512 max freq in performance control, ondemand governor, and then make a nandroid of it.
After that, flash the stock 20j zip (not lgnpst), and make a nandroid and name it "STOCKROM" or something. Then if CM freaks out after some indeterminate quantity of time, then dude can boot to recovery and restore stock or the original CM10.1 that you loaded up in the first place.
Click to expand...
Click to collapse
Do you mind directing me to the rom thread of the 5/21 cm build. And all the ncessary zip files I need to back up . Thanks. I'll set those clock frequencies thanks for your help.
No. Go to shelnutt cm thread in original development section. First page, look for download link. When you click link, click top right of the page where it says next until you get page 4. Then around lower middle is 5-21-13.zip, although that's just part of the file name. Not spelling the whole thing out on my phone. Then google banks minimal gapps, download latest version. Flash them both in recovery after formatting everything but sd card.
After it boots, let it sit for a few minutes, then reboot to recovery. Tap "backup" and follow the prompts. When it's done, copy that backup to your pc.
Do the exact same for stock att jb zip in the android development section, except with it you don't need banks gapps. When you're done, restore the cm backup in recovery and copy the backup of stock rom to pc.
After all that, make sure the backups are on external sd card, and Dropbox them or burn a dvd of them to give to buyer. Just in case card fails or he has to format internal SD card
Then look for the stock att jb zip in
Sent via LG E970 with houstonn aokp 4.2.2
DeathmonkeyGTX said:
No. Go to shelnutt cm thread in original development section. First page, look for download link. When you click link, click top right of the page where it says next until you get page 4. Then around lower middle is 5-21-13.zip, although that's just part of the file name. Not spelling the whole thing out on my phone. Then google banks minimal gapps, download latest version. Flash them both in recovery after formatting everything but sd card.
After it boots, let it sit for a few minutes, then reboot to recovery. Tap "backup" and follow the prompts. When it's done, copy that backup to your pc.
Do the exact same for stock att jb zip in the android development section, except with it you don't need banks gapps. When you're done, restore the cm backup in recovery and copy the backup of stock rom to pc.
After all that, make sure the backups are on external sd card, and Dropbox them or burn a dvd of them to give to buyer. Just in case card fails or he has to format internal SD card
Then look for the stock att jb zip in
Sent via LG E970 with houstonn aokp 4.2.2
Click to expand...
Click to collapse
Thanks for your help man. Everything is running smoothly hopefully this buyer will appreciate it.
Z33type said:
Sorry to say but I'm parting ways with the LGOG. I bought myself a Nexus 4 instead now I need help solving a few issues before I sell it.
Click to expand...
Click to collapse
I ended up buying an N4 too. Went back to using the OG. N4 is in my drawer lol.
Sent from my LG-E970 using xda app-developers app
Related
I have lurked for a while looking for a thread that closely matches the path I have taken. I arrived here partly by the sequence of threads and instructions I read and what has worked for me so far. I am somewhat versed in installing different ROMs as I did so on my Incredible.
I would like to get to ICS. It just looks cool. I bricked once last night trying. I used Odin to get back to stock GB. Then got to where I am.
Details:
1. Use Odin to get to stock GB. (EH03 and Atlas _v2.2 pit) Reboot to stock GB.
2. Use Odin to push CWM4 fixed for CM7
3. Three finger to CWM4 and load salsaCM7_fascinate_02132012.zip
4. Install Gapps zip from CWM4
5. Use phone
Currently when I boot recovery from the three finger method I get CWM4 but it will not mount /data, /system, /cache, etc. If the device is booted and I reboot to recovery with the power button I get CWM5 and all files mount correctly.
Can I just load an ICS ROM from CWM5?
Do I need to start with build 2 or can I use 6.1 from here?
Or do I need to go back to stock EH03, load a plain CM7 and move forward that way?
I think I may have found an answer in Droidstyle's guide in section 4. I would have to go back to stock though to get CWM4 to work, then install THS build 1.
Do I have to do this or can I reboot into CWM5 recovery from the SalsaMOD CM7 and install an ICS ROM? Would I have to use an earlier build like 1 or 2 or can I go straight to 6?
You can go straight to ICS from CM7, and you can certainly try jumping straight to the latest build, but I always have had to install build 1 or 2 first and then the later build. When I went from CM7 to ICS, I was on a different CM7 rom, but you should be able to go to ICS without having to go all the way back to stock.
Another thing to keep in mind is NEVER to 3-finger into recovery once you've flashed an ICS rom, you'll end up bootlooped. I'd get into the habit of always rebooting recovery from the power menu.
Chuckles at the fact someone flashed salsa...
Ooh and Goodluck flashing
Sent from my SCH-I500 using xda premium
k_nivesout said:
You can go straight to ICS from CM7, and you can certainly try jumping straight to the latest build, but I always have had to install build 1 or 2 first and then the later build. When I went from CM7 to ICS, I was on a different CM7 rom, but you should be able to go to ICS without having to go all the way back to stock.
Another thing to keep in mind is NEVER to 3-finger into recovery once you've flashed an ICS rom, you'll end up bootlooped. I'd get into the habit of always rebooting recovery from the power menu.
Click to expand...
Click to collapse
Many thanks. I have both builds on my SD card at the moment. I did make the mistake of booting recovery from the three finger method. That's why I had to Odin all the way back to stock. I won't be doing that again.
neh4pres said:
Chuckles at the fact someone flashed salsa...
Ooh and Goodluck flashing
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Yeah yeah yeah... I saw that coming after reading several threads today.
It is actually working okay for me. I just like the look of the ICS ROMs. I think I am going to go with THS build 6.1 w/ Icy Glitch kernel like DroidStyle mentioned in another thread.
Also, I am going to try the 4G world and pick up a Charge this afternoon. Any thoughts on that device?
Oldtymehockey said:
Many thanks. I have both builds on my SD card at the moment. I did make the mistake of booting recovery from the three finger method. That's why I had to Odin all the way back to stock. I won't be doing that again.
Yeah yeah yeah... I saw that coming after reading several threads today.
It is actually working okay for me. I just like the look of the ICS ROMs. I think I am going to go with THS build 6.1 w/ Icy Glitch kernel like DroidStyle mentioned in another thread.
Also, I am going to try the 4G world and pick up a Charge this afternoon. Any thoughts on that device?
Click to expand...
Click to collapse
THS 6.1 and glitch v14 has been a great combo for me, I've never really had a more stable setup, even with overclocking. My uptime was around 120 hours before I finally got a freeze and a reboot but that probably wouldn't have even happened if I left the kernel settings default.
I can certainly see where 4g speeds would come in handy and look forward to upgrading to a 4g device when we get it in my area. I've gotta say though, the charge doesn't seem to be too popular among the modding community, I know there are a few roms around for it, but to my knowledge, they don't have working ICS. I was pretty happy with CM7/MIUI for a while and held off on switching full-time to ICS, but I can't really see myself going back now. Amazing performance and 4.0 is just a great upgrade for android in general, in addition to looking "cool". I've gotta think that going to a phone that's not as well supported rom/kernel wise, and without functional ICS would feel like sort of a downgrade, even with the charge's beautiful screen and LTE radio, but that's just me. Unless it's a screamin deal, I'd just hold out for a nexus.
Good move using Droidstyles guide ! FWIW....I have better luck with the THS 6.0 build.
Sent from my SCH-I500 using XDA App
The Fascinate is running ICS nicely thanks to DroidStyle. I did get the Charge. I did get it a hundo less than the going rate in my area. I need to go to 4G because I have been 'throttled' on 3G. It is a suxdonut but I am a data user so VZW punishes me.
I do need to get this Charge off stock but in the meantime at least I can bring up a web page in less than five minutes. My speeds were below 300k on 3G when I was 'throttled'.
I think my next step will be to learn some basic dev skills for these devices. I mean, if I can teach myself old school VBA I think I can fumble through some development. If I come up with something good, I will certainly share.
Just curious, how did you know that you were being throttled?
AOKP milestone 1 seems a lot better than the current build of cm10 on the Fascinate, so I would like to give AOKP a shot. However, the guides say to flash from a cm7 enabled CWM. If I'm on the latest nightly of CM10, would it be ok to just download the latest AOKP and flash it, or should i downgrade to cm7 then back to AOKP
No need to go back to CM7, but you should do a data wipe before switching for sure
I have read up and am quite experienced, especially with samsung flashing and Odin.
I will be flashing a coworkers verizon fascinate which is bone stock 2.3.5
to keep on subject with this thread I would like to go straight to a Jellybean ROM.
can I just... Odin the CWM recovery fixed for CM7, wipe data/cache/dalvik,etc. flash JB ROM & gapps?
Do I need GB bootloaders? shouldnt they already be there? Im not sure of his ext sd card speed class, but it is the stock 16gb ext sd. Will a low class(class 2) really cause so many problems I've read about?
Since I wont have a ton of time I would like to get to JB as quick as possible.
I will be backing up via GoBackup, will we run into trouble restoring? going from GB-->JB ?
also, just to be safe.. factory reset should not wipe the ext. removeable sd correct?
Thanks so much guys..
GT-P6200 user here .. Galaxy Tab Plus 7.0 3G Malaysia... waiting for Note 7! yeah baby!
chrisrotolo said:
I have read up and am quite experienced, especially with samsung flashing and Odin.
I will be flashing a coworkers verizon fascinate which is bone stock 2.3.5
to keep on subject with this thread I would like to go straight to a Jellybean ROM.
can I just... Odin the CWM recovery fixed for CM7, wipe data/cache/dalvik,etc. flash JB ROM & gapps?
Click to expand...
Click to collapse
Yep, although you should still flash the stock EH03 first just to be safe before flashing CWM
chrisrotolo said:
Do I need GB bootloaders? shouldnt they already be there?
Click to expand...
Click to collapse
You don't need them, and no, they won't necessarily be there. You can flash the bootloaders at a different time, but I think if you check 'bootloader update' in Odin while flashing EH03 it should do it (I have not tested this. I flashed them separately).
chrisrotolo said:
Im not sure of his ext sd card speed class, but it is the stock 16gb ext sd. Will a low class(class 2) really cause so many problems I've read about?
Click to expand...
Click to collapse
I don't know. I never had a problem with my stock sd card until I started flashing custom roms, and boom, all of a sudden it had problems mounting in CWM. If you want to play it safe, get a new sd card, because sometimes there aren't any warning signs (I got a 32GB class 10 for $30).
chrisrotolo said:
Since I wont have a ton of time I would like to get to JB as quick as possible.
I will be backing up via GoBackup, will we run into trouble restoring? going from GB-->JB ?
Click to expand...
Click to collapse
You shouldn't have a problem, but then again I've always used Titanium Backup. Never had an issue using TiBu, it's very fast and has a ton of options. Personally, I always do a full data wipe on almost every rom I flash and restore using TiBu and I'm good to go within 15 minutes.
chrisrotolo said:
also, just to be safe.. factory reset should not wipe the ext. removeable sd correct?
Click to expand...
Click to collapse
If you mean photos, music, etc. then no, it won't. One time when I did a reset it did wipe my music, but I think that was when I had my old sd card. My photos were never touched, though.
*USE DROIDSTYLE'S GUIDE*
big thanks @Crawshayi, I should probably use the alpha 2.2 .pit to Odin back stock right?
I thought I also saw a 2.2.2 pit and a v2.3 pit are these any better?
chrisrotolo said:
big thanks @Crawshayi, I should probably use the alpha 2.2 .pit to Odin back stock right?
I thought I also saw a 2.2.2 pit and a v2.3 pit are these any better?
Click to expand...
Click to collapse
Honestly I didn't even know there were different versions of that file, I've always used the 2.2 one from section 4 of droidstyle's guide and never run into any problems. The only purpose of that file (from my understanding) is just to re-partition so I don't think it matters all that much
From my understanding you don't need cwm 4 fixed for cm 7 to flash straight from stock to jb. Only when flashing ics roms. I have had to go back to stock a few times flashing aokp jb builds. And I always step up to jb like this. Odin cwm 4 fixed for cm 7-flash ths build 2- reboot -reboot into recovery vis power menu -flash aokp milestone 6(ics)- flash aokp jb build of choice. (me stone 1 just released). And then devil kernel of choice. Currently running devil 1.6.1. Never had any problems. Going this way. And I prefer to use go back up when restoring. It's slways done me right. Is this all necessary? Idk... But it works. Just sayin...
The devil rode a unicorn named jelly bean
forsakenone said:
From my understanding you don't need cwm 4 fixed for cm 7 to flash straight from stock to jb. Only when flashing ics roms. I have had to go back to stock a few times flashing aokp jb builds. And I always step up to jb like this. Odin cwm 4 fixed for cm 7-flash ths build 2- reboot -reboot into recovery vis power menu -flash aokp milestone 6(ics)- flash aokp jb build of choice. (me stone 1 just released). And then devil kernel of choice. Currently running devil 1.6.1. Never had any problems. Going this way. And I prefer to use go back up when restoring. It's slways done me right. Is this all necessary? Idk... But it works. Just sayin...
The devil rode a unicorn named jelly bean
Click to expand...
Click to collapse
This has been proven unnecessary, basically the new roms have scripts built in that will re-partition as needed thus removing any need to flash 'over' another rom first. I was the one who actually verified this in droidstyle's guide (check the last few pages) and he has updated the thread to reflect it. If it still makes you feel better to do so... well... rock on because I don't think it hurts anything, but I thought you should know it isn't required.
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.
My friend and I both have Fascinates. I got mine first, and just rooted the Gingerbread that came with it. I use it for medical purposes, and really needed something stable and reliable.
When my friend got hers, we decided to go for a more recent ROM, and chose GeeWiz 4.4.2 (Jellybean). It was real easy to install and didn't require anything special. It worked great for a little while, but as she added apps to it, it got real laggy and hard-crashed a fair amount.
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Since it's a blank canvas, and her experience with GeeWiz wasn't all that great, I figure it's a good time to try something else.
What do YOU recommend?
Here's her priorities:
1. Must be super stable.
2. Everything must work. Speakerphone, bluetooth, camera, video, microSD, you name it.
3. Not laggy.
4. Good battery life.
She really likes the Jellybean notifications, so she would prefer Jellybean or later.
I'm very interested in what the community recommends. :highfive:
the newest cm10.1 nightly was rock solid for me. helly bean 4.2.2 was good too. don't go beyond 4.2 if you want good stability, i don't think some basic things work in the cm11 builds yet (GPS and MMS are flaky)
oh also don't feel bad for running stock GB. i'm actually running it right now (rooted, lean kernel, and i gutted out the majority of samsung things)
---------- Post added at 11:04 PM ---------- Previous post was at 11:00 PM ----------
also, for future reference, any thread you post of similar connotation to this will probably get locked by a moderator and he'll say "oh try roms out for yourself blah blah blah"
so if that happens, don't say i jinxed it. also, i've had my fassy for around 6 months and i've tried literally everything under the sun for it.
I agree with sceptic on these ROM selections
rockpaperlizard said:
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Click to expand...
Click to collapse
I thought Geewiz was only made for the Fascinate? I have been trying the Geewiz rom, and so far the only time it became laggy was when I set the cpu Govenor to a power saving option. Otherwise it has actually been much faster booting up than the kitkat roms.
Sent from my GT-N5110 using xda premium
Okay, trying to get Hellybean working... but am stuck!
Thank you to everyone providing a reply so far. Please keep the suggestions coming. :highfive:
I am trying to install the recommended Hellybean 4.2, and am stuck.
The phone was stock Gingerbread, and then I installed the GeeWiz 4.4 ROM on it. Had some lagging and crashing, so now I'm trying to get Hellybean 4.2 on it, per recommendations of others.
So I downloaded the latest Hellybean 4.2 from the hellybean website. I then booted into recovery, and selected Update from Zip and and tried to install the Hellybean zip. I get a Status 7 error. Some sites said to try it 3 times. I tried it 5 times. No dice.
I can't find a Hellybean 4.2 Fascinate thread on XDA, so details are sparse. Am I blind?
Am I correct in understanding that Hellybean 4.2 includes the devil kernel? Or do I need to ODIN a different kernel first?
I installed ROM Manager to get the latest CWM Recovery, but it says the Fascinate is an "unknown device". There is no CWM Recovery installation file for the Fascinate listed on the Clockworkmod website. UGH! :crying:
Can anyone help? I can follow step by step instructions real well. :good:
Progress Update
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
rockpaperlizard said:
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
Click to expand...
Click to collapse
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
if any of my guide didn't help, just follow the thread i linked in step 2. it's a good comprehensive guide.
also never flash anything with ROM Manager, it's useless for this phone because the version of CWM on ROM Manager is really old. i've bricked my phone when trying it.
Getting closer!
skepticmisfit said:
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
Click to expand...
Click to collapse
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
rockpaperlizard said:
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
Click to expand...
Click to collapse
wipe data before installing helly. also i've never bothered with build.prop in Hellybean. it only references to EI20 for Voodoo Sound drivers. EI20 is the stock build for.. i believe the US Cellular Mezmerize (aka not the Verizon Fascinate). so don't screw with it
yes stock radio is good. EH03 is a good radio but if you want you can flash EC09, based off of a leak of GB. some people have good luck with it, i used to but i like EH03.
so.. i'm not sure if you can boot the phone into helly bean. it sounds like you were getting a lot of "status 7" errors, which i didn't ever get while trying to use helly. this may or may not be caused by the sd card. try a different card if possible. if you're bricked at this point just start over from EH03.
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Good advice!
skepticmisfit said:
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Click to expand...
Click to collapse
Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
rockpaperlizard said:
Hey, it's the girlfriend here. BF is out, so I was trying to get the right files gathered. Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
Click to expand...
Click to collapse
here you go: http://andromirror.com/file/1386
good luck!
Sooooo close...
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
rockpaperlizard said:
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
Click to expand...
Click to collapse
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
for windows
or an android one
like this one
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
its what you need to start with,, and then after you sign in to your account,, it will check to see what needs to be updated.
.
I tried the cm10 mentioned here. It does seem very nice. It appears to have more features than Geewiz also, along with a lot more ringtones.
Sent from my GT-N5110 using xda premium
Information
hhp_211 said:
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
.
Click to expand...
Click to collapse
Thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
hhp_211 said:
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
.
Click to expand...
Click to collapse
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
It's the blue CWM, forgot to mention that...
rockpaperlizard said:
Hi, GF here again. I'm new to all this, thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
Click to expand...
Click to collapse
whoa you're not supposed to have blue recovery after flashing a 4.x ROM (or MTD as we call it).
go to step 4 in this guide: http://forum.xda-developers.com/showthread.php?t=1238070
you're going to have to reflash EH03 in Odin before doing anything because your recovery is borked.
Got it!!
Finally got helly onto a phone! Ended up starting all over, and then just flashing to helly since had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
rockpaperlizard said:
GF here. We finally got helly onto the my phone! We ended up starting all over, and then just flashing to helly since we had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
Click to expand...
Click to collapse
that's weird that 3-finger into recovery is broken for you.. it wasn't for me. but whatever, as long as it works
I am about at my wits end...Rewind to two days ago...
Order of events:
1. Received my new S4 in the mail a few days ago to replace my old S3. I received the S4 fully updated with the NC5 OTA (yeah, I know, bad juju).
2. So I followed Surge's downgrade thread HERE and am now downgraded to the MK2 build, but with no sound and the telephone/calls app does not work.
3. I then downloaded GooManager and installed the OpenRecovery from TWRP, and it said it installed correctly. However, now I CANNOT GET INTO RECOVERY no matter how I try (via VolUp+Home+Power or via "Reboot into recovery" from the GooManager app). It just goes into Download mode with an error at the top in re that says "Could not do normal boot"
4. At this point the phone just boot loops into Download mode. Cannot go into recovery or the MK2 Rom. I then have to reflash the MK2 downgrade files in order (downgrade, system, cache) in order to get a working phone again and I have now probably done this at least 8 times. It is getting old.
So, I am curious what I need to do now. I have gone through the MK2 downgrade process multiple times and tried again to no avail. I also tried flashing the TWRP .Tar file (directly via Odin) but no luck also --- Is there like a super/clean ODIN file I can use that will also reset the recovery image on the phone? I feel that is my main problem, then I can fix the sound/phone problems after that.
This thing is 10x harder to get on CM than the S3 which I had running CM within 2 hours of ownership. I'd appreciate any help to get me back on path.
FYI - I can install Safestrap 3.71/3.72 and get into those fine, but if I want a chance of running CM I will need a Loki recovery right? If so, I just do not see how I am going to get there.
My ultimate goal is a clean rom, and I was so used to CM on my S3 that I'd hate to part with that, but if there is a Safestrap-friendly ROM that is very clean/similar, then I will take that any day. Ready to be done with this - easiest way out.
--edit--
Found this...can I just follow these steps or is that only for people still on MDK?? http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
crobs808 said:
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
Click to expand...
Click to collapse
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
crobs808 said:
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
Click to expand...
Click to collapse
only a handful, so not that hard to locate in dev forum. Until hashcode comes out with a safestrap for verizon that enables rom slot creation for custom rom installs on 4.4 base phones I know many of us are staying clear of kitkat.
good luck
So I have not used Safestrap since my Moto X days a few years back, and I am having problems installing a new ROM. Here are my steps, please tell me if things have changed because I got unexpected results.
1. While running stock NC5 (rooted+SS installed), copied custom ROM (SS-friendly FoxHound port by gigili) and SU over to my internal sdcard (do not have an external as I never needed one for the S3)
2. Booted into SS and created a ROM slot in rom-slot1
3. Gave it the nickname FoxHound
4. Selected that rom-slot to be active, then went into advanced Wipe, and did Data, Cache, System, Dalvik
5. Went back to the Install menu so I could install the new ROM but there were no files. Actually, I found out it wiped my StockRom slot even though I have made the rom-slot1 active. Why?
Anyway, now I am back to a wiped stock NC5 and have to do this all over again. Am I supposed to not do step 4 (wipe) after I create the ROM slot? and Am I supposed to just install the custom rom in the Stock slot?
Ugg forget it. I now tried flashing the custom ROM on the safe side without doing the WIPE step and just got a rom that looked identical to the stock except that DATA was broken. Forget this - I guess I just have to live with stock rooted, and modify/freeze apps.