Q&A for [ROM][Player4][US/Intl] Cyanogenmod 11 for the Galaxy Player 4.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Question: CM11
Hi,
i tried to flash the cm11, but the flash didn´t start. Do i need root? I have the Steves Kernel, does this work with the CM11?
Thanks for reply.
Matthias
semmelbroessel said:
Hi,
i tried to flash the cm11, but the flash didn´t start. Do i need root? I have the Steves Kernel, does this work with the CM11?
Thanks for reply.
Matthias
Click to expand...
Click to collapse
Ok so first you need to use the terrasilent kernel. Then upon flashing the ROM, you need to wait 10 secs then you can force restart the device. After this, the installation process should continue on it's own. At the end. You will be rebooted a last time into CWM in which, you can flash the gapps if you want.
zaclimon said:
Ok so first you need to use the terrasilent kernel. Then upon flashing the ROM, you need to wait 10 secs then you can force restart the device. After this, the installation process should continue on it's own. At the end. You will be rebooted a last time into CWM in which, you can flash the gapps if you want.
Click to expand...
Click to collapse
THX, the Kernel flashing with odin? And then the rom by CWM? Correct? Do i need ROOT?
semmelbroessel said:
THX, the Kernel flashing with odin? And then the rom by CWM? Correct? Do i need ROOT?
Click to expand...
Click to collapse
Yeah, you flash the kernel with odin and then the rom with CWM. You don't need root to proceed with the installation of the rom.
Flashing Cyangenmod
What I don't understand is how to flash the zip. When going into recovery mode, the phone doesnt see it and I can't seem to use Odin because its the wrong file extension. So how do I do this?
msigalov said:
What I don't understand is how to flash the zip. When going into recovery mode, the phone doesnt see it and I can't seem to use Odin because its the wrong file extension. So how do I do this?
Click to expand...
Click to collapse
It's exactly the same procedure as the one on the beginning on the thread. Also be sure that the zip is in the internal memory of the device. (Not the external SD card, it won't be recognized otherwise)
Still not working
zaclimon said:
It's exactly the same procedure as the one on the beginning on the thread. Also be sure that the zip is in the internal memory of the device. (Not the external SD card, it won't be recognized otherwise)
Click to expand...
Click to collapse
So I booted into recovery, found the zip of the internal drive, and told it to install, but it cancels after a couple seconds saying that there is no space left on device, even though I factory reset it to ensure all the data was wiped.
have a stock Samsung Player 5.0 want to install Cyanogenmod11
new to an old thread, so much conflicting information, do i need to install cyanogenmod 9.0 first?
msigalov said:
So I booted into recovery, found the zip of the internal drive, and told it to install, but it cancels after a couple seconds saying that there is no space left on device, even though I factory reset it to ensure all the data was wiped.
Click to expand...
Click to collapse
Sorry for not having replying after so much time, I didn't get a notification and I don't visit the Q&A forum often so I couldn't see your reply. Do you still have this issue while installing CM11?
section128drunk said:
new to an old thread, so much conflicting information, do i need to install cyanogenmod 9.0 first?
Click to expand...
Click to collapse
As per the instruction on the CM11 thread:
Installation Instructions:
1. Reboot to recovery and make backup.
2. Do a full wipe.
3. Flash rom. You will see an error pop up. This is perfectly normal. Flash the rom again
4. Flash Gapps.
5. Flash US kernel if necessary
6. Have fun!
Click to expand...
Click to collapse
You don't need to install CM9 prior to install CM11. That said, at this time it is more recommended to install Carbon because it is updated and have more features than CM11. (like DT2W)
Reboots itself to recovery every once in a while
Great work on the new KitKat ROM. I have CM11 version 20141112 on my YP-G1 but I have one blaring issue.
I upgraded the ROM from 10.2 from the CyanogenMod Updates menu item in "About Phone", which booted it to recovery and I reflashed it twice again from there, wiping cache and data along the way. Afterwards, I flashed Gapps. Now it is installed and everything works and looks fine. However, now every few hours, the gadget would reboot itself into recovery with no error or anything. When I choose reboot from the recovery menu, the gadget would reboot to recovery again! I have to shut down, pull battery, then turn it on again so it would boot normally. So at least once a day I would be doing battery pulls on this thing just so it can boot normally.
Not sure if it's a common issue or is it because of my install method, maybe I forgot something?
Sad to hear that development might be discontinuing for this device. Seeing as I mainly use my smart devices for checking email, the only reason I stopped using it is because CM11 for some reason started locking up and draining the battery on a regular basis (although having it looked up to USB debugging and doing a logcat seems to keep it from ever locking up). Attached are two screen shots of the battery page taken while charging after two of those lockups in a single day (one mid day so I was able to catch it and reboot before the battery completely drained, the other overnight).
Any ideas what might be causing that? I just did a factory reset while flashing the new unofficial rom in recovery and flashed the minimal google apps so there's not much on there besides Google Chrome. The play services wake lock was fixed shortly before the first lock up by updating the Google Play Services.
Edit: After talking with zaclimon it seems like this is caused by something getting stuck in the system (presumably a bug with Google Play Services). Reverting back to stock, cleaning off the sdcard, and reinstalling CM seems to have solved the problem.
Related
Hi All,
Just got my S2 last week. Planning to move to CM7 this weekend. I have rooted the device and am on the Codeworkx kernel. I had a few questions:
1. Is there a problem while flashing via Odin if Debugging is not enabled (I think it is more of a OS feature which we haven't entered when in download mode, so shouldn't matter according to me.) ? I tried to disable debugging, and then went to download mode and Odin did detect the phone, but I did not try to flash anything so if anyone has tried that, your input is more than welcome.
2. The reason for above question is: What if I completely brick my phone (with debugging disabled) and no ROM .zip in the sd storage, how do I get the phone up and running ? I understand that I can flash kernels via Odin, but is it true for ROMs as well ?
3. What's the issue with ROM manager ? Is it recommended to stay away from it for S2 ? I have tried to do a Nandroid backup and it always takes me to the Android robot with a exclamation mark screen. Then I have to reboot and the backup magically restarts and completes successfully. Most people have suggested to use CWM recovery directly, so not sure if I should get rid of the ROM manager altogether.
That should be all for now. I have a jig ready by the way, so am not that worried about the process and plan to do a fair bit of reading before proceeding, however, the answers to above queries would be really great !
Thanks in advance,
Ish
I can answer some of your doubts.
I don't know if you can flash via odin in case you don't have the usb debuggin enabled so I'm not going to say anything about it.
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
ABout ROM manager, this is what I suggest you. The first time you flash CM7 don't use ROM Manager (I even tried using it with the codeworkx kernel with no luck). Now, once you are in CM7 it works perfectly and it's really helpful to flash nightlies withouth wiping data (I flash half the nightlies as they are realeased). So the first time you flash CM7 wipe everything (do a nandroid backup first), even wipe /system, /data, cache partition, dalvik cache, so you don't have any problems. THen install zip from sd card and when it finish install the zip file again (just two installs in a row no wiping in beween, trust me, the first time I tried I didn't do that and couldn't boot the phone).
Hope it helps.
EDIT: You can flash stock ROM via odin, there is a thread by infratech were this is explained and you have a list of downloable stock ROMS you can flash with Odin, these are region and carrier specific and you probably will get the one for your carrier. I found the stock ROM for my carrier and I'm from chile, you shouldn't have any problems with that. Well, good luck, CM7 is by far the best ROM I've flashed.
Oh another thing, go for the latest nightly since the battery life is incredibly improved over the RC (or was it stable?) version.
Thanks !
tomascunill said:
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
Click to expand...
Click to collapse
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
cheemais said:
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
Click to expand...
Click to collapse
Well good luck! Tell me if you get any problem.
First of all, I want to thank everyone working on the CM7, CM9, CM10, SGT7, TWRP, CWM projects for the Nook Tablet. I've really been enjoying trying different ROMs on my Nook Tablet.
I started with CM7, and it ran pretty well. I also tried the CM9 (NX-Fire?) port, and I liked it as well.
I have been using the SGT7+CM10+Cherry Picks and it has been fine up to the 27/9 release. I cannot run anything higher than this on my NT.
I have tried CWM (up to 6.0.1.2) and TWRP (up to 2.2.2.0) to flash the newer ROMS, but the ROMS will not boot. The screen blanks, and after a time, it goes back to the boot screen.
I also can't seem to use the CWM 6.0.1.5 or TWRP 2.3.1.1 from the SGT7+CM10 thread.
I know I have the 16GB Nook Tablet. I have repartitioned the userspace, as mentioned in other threads. I can't help but feel like I'm missing a step somewhere.
Presently, my NT is running TWRP 2.2.20 and SGT7+CM10+Cherry Picks 27/9. Any one have any hints? A thread on the boards I have missed? Any help would be appreciated.
Again, thanks for all the hard work!!
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Moved. Questions belong in the Q&A section.
Thanks
AvRS
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Thanks! I'll try that this weekend. I knew I was missing something.
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Sorry, but how does one manually update a recovery? I've tried flashing the newer TWRP from CWM as well (from an older version of CWM), and while the flash doesn't fail, it won't let me boot into TWRP, and the new CWM crashes before I can do anything. I've also tried flashing the recovery from fastboot, but I get a "bad boot magic" error when I try to boot.
Just flashed couple of days ago: pretty nice ROM
Besides annoying "SD card unmounting" problem I found that B&N Nook app does not work, it just keeps restarting, some error message shows up but goes away so quickly I can't read it. I wiped before I installed the ROM and reinstalling the app didn't help.
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
There is a search function on here...
Sent from my NOOK Tablet running CM10
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
The OP in the developers section has links to both CWM and TWRP for your use. Remember, SEARCH is your FRIEND!
play store/goomanager closing
First let me say this rom is awesome! I had no idea my nook could run this smoothly. The only problem I seem to have is that on the newest build(10/25) both playstore and goo manager will open then close. I have tried clearing the app cache, re flashing rom and gapps, full wipes then reflash. I also tried reflashing the newest gapps without success. The 10/12 build works with both play store and goo manager. I am using the 10/12 build now so no worries if it can't be fixed. Again thanks for the time and effort on an awesome rom:good:
edit: I am using the latest twrp for my recovery (also awesome). the tablet is the 16gb version
Same problem as OP, latest SGT7 not loading
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
jarvz said:
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
Click to expand...
Click to collapse
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
spurious_access said:
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
Click to expand...
Click to collapse
Yes I have repartitioned mine as well, so that must be it. I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
jarvz said:
I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
Click to expand...
Click to collapse
Yeah, I don't have the new touch firmware installed either. CWM worked fine, though TWRP didn't seem to work properly (maybe it needs the new touch firmware?).
Do you know if there is any mention of re-partitioning causing an issue? I looked in the rom dev thread but didn't notice anything. I guess one of us who are seeing this issue could post there to see if anyone knows what could be causing this.
I finally got it to work. My PC is running Ubuntu, so YMMV.
Here is what I did:
1. Used "gparted" to create 2GB FAT32 partition that is bootable.
2. Used the instructions in the this thread thread to create a bootable SD disk that boots into CWM 6.0.1.2.
3. CWM 6.0.1.5 just doesn't seem to work on my Nook Tablet. So, I downloaded CWM 6.0.1.3 from here
4. I downloaded the latest ROM here
5. Downloaded the latest gapps: here
6. Copied the CWM, ROM, and gapps to the SD disk.
7. Inserted the SD and booted the Nook Tablet.
8. On first boot, it boots to CWM 6.0.1.2, so I flashed the CWM 6.0.1.3, and rebooted.
9. This time it boots to Cyanoboot, so I entered the boot menu and selected EMMC Recovery.
10. From CWM 6.0.1.3, I formatted /storage, and did a factory wipe. (I didn't format /storage the first time, and the wireless would not come up.)
11. Installed ROM from SD card.
12. Installed gapps from SD card.
13. Rebooted, this time letting cyanoboot boot from EMMC.
14. Profit!
I haven't tried 6.0.1.4 to see if that would work.
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.
Q&A for [ROM][LP 5.X.X][fireball] PAC-man ROM [MODDED TWRP]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LP 5.X.X][fireball] PAC-man ROM [MODDED TWRP]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I want to know if this rom is for verizon or Sprint cos i have a verizon and it doesn't work for my phone. i need help pls.....
where I download the modded TWRP, since I can not find it anywhere, someone put the link?
It should be for Verizon. Make sure you are using the modded TWRP and modifying the partitions.
Sent from my Nexus 5 using XDA Free mobile app
Yommiie said:
I want to know if this rom is for verizon or Sprint cos i have a verizon and it doesn't work for my phone. i need help pls.....
Click to expand...
Click to collapse
It's for verizon, and if the signal isn't working you need to most likely update your radio baseband, which is in the OP of the ROM.
valva said:
where I download the modded TWRP, since I can not find it anywhere, someone put the link?
Click to expand...
Click to collapse
In OP of the ROM.
Installed the ROM a few days ago, and it is really good. Nice work on it. The only issues I have encountered:
Ringtone gets reset when the phone is rebooted. In addition, WiFi loses saved access points when the phone dies from low battery.
Bluetooth isn't able to connect to devices. The screen that asks for a PIN doesn't pop up and it says that the device had the wrong PIN.
Otherwise, everything else seems to work. I use this as a daily and the battery life seems fine as well as the general usability of it.
Android password
I went through all the hassle with unlocking the phone and installing this ROM was easy, but when it boots it shows me a prompt saying "To start Android, enter your password". I didn't have any before, so I'm not sure what it's about. However it'd accept any password with "Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt". It suggest to reset phone and if I push that button it reboots into some cycle showing recovery splash screen repeatedly. I can have it out of that cycle only with wiping the data in recovery.
What do I do wrong and more important, how could I fix it?
Thanks in advance.
_darkace said:
I went through all the hassle with unlocking the phone and installing this ROM was easy, but when it boots it shows me a prompt saying "To start Android, enter your password". I didn't have any before, so I'm not sure what it's about. However it'd accept any password with "Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt". It suggest to reset phone and if I push that button it reboots into some cycle showing recovery splash screen repeatedly. I can have it out of that cycle only with wiping the data in recovery.
What do I do wrong and more important, how could I fix it?
Thanks in advance.
Click to expand...
Click to collapse
Which recovery are you using? Also, did you do a clean flash or dirty? Did you encrypt your information before install? What exactly did you do, gotta know what steps you did.
Beeko said:
Which recovery are you using? Also, did you do a clean flash or dirty? Did you encrypt your information before install? What exactly did you do, gotta know what steps you did.
Click to expand...
Click to collapse
Thanks for answering.
Recovery: TWRP 2.8.5
Not sure what you mean by clean or dirty flash. I did cleanup data and system partition when flashed it first time. Then flashed second time without cleanup. Same result both times - password prompt.
I didn't do anything specific to encrypt any data.
The hardest part was to S-OFF it (BTW, it's still S-OFF - does it matters?) and get the root access to change the recovery. Used some script which styled to room brewing. Than I changed the file system according to instruction of first post in this topic. I guess because of that recovery couldn't see the images on internal storage, so I've put the images to external SD card. Than just rebooted to recovery and flashed both Android and Apps images in one run.
_darkace said:
Thanks for answering.
Recovery: TWRP 2.8.5
Not sure what you mean by clean or dirty flash. I did cleanup data and system partition when flashed it first time. Then flashed second time without cleanup. Same result both times - password prompt.
I didn't do anything specific to encrypt any data.
The hardest part was to S-OFF it (BTW, it's still S-OFF - does it matters?) and get the root access to change the recovery. Used some script which styled to room brewing. Than I changed the file system according to instruction of first post in this topic. I guess because of that recovery couldn't see the images on internal storage, so I've put the images to external SD card. Than just rebooted to recovery and flashed both Android and Apps images in one run.
Click to expand...
Click to collapse
Was is the recovery I posted in the OP of the ROM?
Beeko said:
Was is the recovery I posted in the OP of the ROM?
Click to expand...
Click to collapse
Yes, I downloaded it at the link given in the first post of the topic.
Very weird, I haven't a clue what the problem could be.
Apparently I either didn't format /data partition to ext4 or something changed it back to vfat. I reformatted it and it helped. At least I'm looking at "Optimizing app x of y" process which I haven't seen before. I guess it means that whatever was encrypted is not now.
Yea your /data and /cache can be either ext4 or f2fs. Other than that, you'll run into said issues.
New to all this
Hi, I have some questions.
1. Can I flash this Rom right from stock 4.0.4 or there are some prerequisites excluding the ones you have mentioned in the Rom thread?
2. If I have any problems while flashing or using this rom, how can I revert back to stock?
3. Is this Rom perfect for normal use? What are the bugs?
I would be very grateful if you answer and clear all my doubts.
daskofficial said:
Hi, I have some questions.
1. Can I flash this Rom right from stock 4.0.4 or there are some prerequisites excluding the ones you have mentioned in the Rom thread?
2. If I have any problems while flashing or using this rom, how can I revert back to stock?
3. Is this Rom perfect for normal use? What are the bugs?
I would be very grateful if you answer and clear all my doubts.
Click to expand...
Click to collapse
1. Yes, but there are definitely prereqs. You need to have S-OFF achieved, along with being on the latest baseband in my PAC-Rom OP and having the modified recovery to take advantage of the memory swap.
2. I don't really know, I achieved S-OFF and root years ago. I don't remember the steps, don't ask. But I'm pretty sure there's an RUU somewhere that you can revert to stock.
3. There are always bugs in any OS, regardless of it being from HTC or from me. I use it as my daily driver, I mean yes there's bugs but they're minor.
But please, remember you NEED S-OFF for all this to work. So I'd start there.
Agreed. My recommendation: achieve s-off first, then install a "standard" custom recovery - i.e. no partition swap, root (install superuser or SuperSU), then immediately do a full nandroid backup to your external SD card. Then, keep that full backup safe on your pc or elsewhere. Then, you'll be able to easily get back to "stock" if you don't like future ROMs by restoring partitions and restoring from the nandroid.
Once you have the base nandroid tucked away, then have fun trying multiple ROMs.
And, yes with s-off and an RUU, you can get back to bone stock, including s-on if you really wanted to. (but why?)
Sent from my Fireball using Xparent Blue Tapatalk MegaSuperb Pro
Can I flash the baseband firmware through twrp?
I flashed this rom and after that my phone has never charged to 100% it stops at 85%
Tried calibrations but didn't worked.
Is there any fix?
Can u reupload or provide link to ROM plz
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Hi, I am in the same boat. Stock standard international S3, but extremely slow. Ram usage on startup is 700mb.
Which rom would you guys suggest that is both stable (no bugs), and fast (using much less ram).
This is my everyday phone, I take a lot of photos, especially the camera should be functioning perfectly.
Any help would be much appreciated.
Edit: Last time I rooted and played around with these things were about 3-4 years ago with my Sony X10 mini. I am slowly getting back into it, reading up on the latest rooting apps etc.
@errolpl: Search in development subforum for 'aroma installer'. Usually these ROMs offer only system apps to choose. 3rd party user apps you'll have to install by your own. You can edit the header with edit-function.
@demozzracy: If you want full camera suport, I recommend NCS-ROM: based on last JB-firmware, but brilliant debloated. So slim, fast, battery friendly and all hardware working. I'm testing many LP-ROMs, but they are primarily newer, hardly better (for S3).
@rp158: Thank you!
I was extremely new just a few weeks back as well. I must say that my attempts on finding a solution for my slow S3 has been a rather hard and bumpy road.
To help you save some time, here is what I've gathered so far:
Last time I flashed phone firmware, a couple of years ago, it required a PC, a cable and some funky software.
Then when I flashed my S3 for the first time, about a year ago, I started out with Cyanogenmod and used their app+cable installer. I think this is still the easiest way to root the phone, and get started with custom roms. Even if you plan to use some other rom than Cyanogenmod.
When the phone is rooted you can install TWRP, simply done via an app on the appstore. TWRP is recovery firmware that can stay on the phone, even though you flash new roms. (The phone is divided into several separate sections, bootloader, recovery, actual system, and data area.... I don't even know much about it yet.) The important part is that it is extremely easy to flash new roms using this tool, and a micro SD-card.
Simply drop the rom zip file onto the card and flash them. (For some roms you need to flash some "GAPPS" as well. These are the google apps, like the play store etc. If you don't flash them you can't really use the phone for much.)
This is where the real problems start. Finding the right ROM.
The S3 is old, and only supported up to Jelly Bean for my 1GB international version, or Kitkat if you have one of the 2gb versions.
This has not stopped developers in providing both Kitkat and Lollipop to any version of the S3. However... as eager they are to provide the newest coolest features, just as lazy do they seem to be with their testing. (Sorry guys, but someone has to say it.)
So I've gone through some roms now... none of them really good.
The first Official Cyanogenmod I flashed half a year ago. I used this for almost a year.. but the camera would crash constantly, and the phone was not able to display video. For example movieclips on facebook.
Second ROM: Cyanogenmod has also stopped developing for the S3, so a few weeks back I switched to some unofficial version. It seemed to work... camera and video was ok, and everything had the nice Lollipop feel to it.
However MMS did not work. I could receive one and send one, next ones would require a reboot for them to work. The problem was brought up in the ROM Q/A tread, but the answer from the developer was: Sorry I don't use MMS so I don't really see a problem.
Third: Onto some next rom. This one was tagged STABLE. It was far from it. In fact it was even easier to discover that this rom had the same MMS problem. Because the message app would crash immediately when trying to send one.
4th attemt was the same rom, but a different kernel... still the same problem.
5th rom was Blisspop... Wau, this was beautiful! Cool webpage, Cool animations.... it was just too bad that the site is dead, and that the rom can't even run for 24 hours without the android keyboard crashing 25 times or so. Also Blisspop has OTA updates... the only problem is that it constantly says that there is a new version for the S3.. but the download fails. Apparently some bad change to the website caused this, and apparently this problem has been going on for 3 months without anyone bothering to fix it.
6th was Archidroid. The second to top ROM for the S3. It looks cool, and has many features... but just as other Lollipop ROMs, sending MMS's without error is not one of them....
I've really tried everything. People always says that the MMS problems are due to APN's not being set up correctly, doing some reboots etc.... but trust me... I've set them up so many times you wouldn't belive it.
7th. After reading this thread and rp158's recommendation of NCS-ROM I'm now running that one. Without a single thing being set up, I was able to send and receive MMS's right away.
However... now I'm stuck back at the ugly kitkat look, and Touch wiz.
tl;dr;
So what do I want to say with all this?
Get root and TWRP and start playing around with ROMs
Lollipop does not look like an option for the S3, at least not right now
Don't let yourself be fooled by nice webpages or [STABLE]-tags, or comments that say: "I've been running this since yesterday.. it's 100% stable!"
Timusius thanks a lot for that post.
Puts things in perspective.
As I said in my post, I am ok with the KitKat look, as long as it is stable, I am always on call at work, and cant afford constant phone crashes.
I am going to try the root/twrp to NCS rom in the next couple of days
@Timusius thank you for your post. You help me a lot!
S5 Sensation
errolpl said:
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Click to expand...
Click to collapse
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Cooldato said:
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Click to expand...
Click to collapse
How you install those rom?
Pixelzack said:
How you install those rom?
Click to expand...
Click to collapse
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Cooldato said:
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Click to expand...
Click to collapse
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Pixelzack said:
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Click to expand...
Click to collapse
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Cooldato said:
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Click to expand...
Click to collapse
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Pixelzack said:
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Click to expand...
Click to collapse
Sure, thats what i linked you above.
Cooldato said:
Sure, thats what i linked you above.
Click to expand...
Click to collapse
Hahaha Thanks dude for helping noob like me
Pixelzack said:
Hahaha Thanks dude for helping noob like me
Click to expand...
Click to collapse
No problem Feel free to poke me if u meet some troubles ^^
Cooldato said:
No problem Feel free to poke me if u meet some troubles ^^
Click to expand...
Click to collapse
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Pixelzack said:
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Click to expand...
Click to collapse
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Cooldato said:
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Click to expand...
Click to collapse
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Pixelzack said:
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Click to expand...
Click to collapse
yeah this means doing a "Factory reset", must be done throught Recovery mode, wipe data, wipe cache, wipe dalvik cache.
Put ROM on your SD card, then enter Recovery Mode by pressing Home + Volume UP + Power buttons and ull have smth like:
Install Zip -> Choose Zip from /Storage/Sdcard (External SDcard) , Search for ur ROM file and start flashing :X
Flash the SuperSu .zip file same way as flashing ROM.