[Q&A] [ROM+kernel][WIP] [4.4.4][CM11][OS2SD][f2fs][EXPERIMENTAL]bigsuperROM-thunderc
Q&A for [ROM+kernel][WIP] [4.4.4][CM11][OS2SD][f2fs][EXPERIMENTAL]bigsuperROM-thunderc-4.4.4
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+kernel][WIP] [4.4.4][CM11][OS2SD][f2fs][EXPERIMENTAL]bigsuperROM-thunderc-4.4.4. 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!
Confused
I downloaded the original skinbark and thunderc for internal ROM and wanted to switch to the OS2SD but im not sure which TWRP and which ROM to use. You mentioned to use the new TWRP which one is that, the one called TWRP2.8.0.0 or the one that is OS2SD friendly? And also is the one labelled internal a normal build?
EDIT: I got the internal version working with the TWRP 2.8.0.0 and so apparently that is for the internal storage but now im wondering how to get the OS2SD version working. i have tried directly flashing with both recoveries and its not working.
EDIT2: E: Error executing updater binary; is what i get when trying with the OS2SD friendly recovery and the other one just says failed and neither is able to mount /data or /cache (I get an error). Am I missing a step or something?
twrp 2.8, and if you haven't, you'll have to partition the sd card with twrp for os2sd.
don't zero out the swap partition even if you're not going to use it, set system at least 512-768 and data whatever you like, reccomend 1024.
it'll wipe your regular sd partition while setting up the os2sd partitions, so back it up first on pc.
advise the ext4 version, has less issues than f2fs. that kernel's a little glitchy.
Just flashed this on my LS670. I flashed trwp 2.8 rebooted into recovery and then flashed the internal ROM, Sprint fix, gapps. Upon reboot, the screen goes black after the lg logo and never recovers. When I try to go back into recovery nothing displays even though it's actually in recovery. I can hit the power button and the backlight goes out. I can't fix it because I can't see it. What now?
Sent from my SM-N910T using XDA Premium 4 mobile app
Almost forgot. A few years back I remember that there were revisions of these phones that had a different chipset and I remember having to flash a special version of recovery or the display wouldn't work. Am I SOL with this ROM and recovery?
Sent from my SM-N910T using XDA Premium 4 mobile app
i_guana said:
Almost forgot. A few years back I remember that there were revisions of these phones that had a different chipset and I remember having to flash a special version of recovery or the display wouldn't work. Am I SOL with this ROM and recovery?
Sent from my SM-N910T usi XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is newer than the old kernel issue.
I suspect is not actually booting into recovery. Think the internal updater script is nnot flashing the boot.img which will leave you not booting if the ext partitions are formatted.
bigsupersquid said:
This is newer than the old kernel issue.
I suspect is not actually booting into recovery. Think the internal updater script is nnot flashing the boot.img which will leave you not booting if the ext partitions are formatted.
Click to expand...
Click to collapse
Well, it shows the LG logo briefly. It also is booting into TWRP when I do the 3 button boot because I can turn the backlight on/off with the power button. There is just no display. I booted into recovery 3 times before I flashed the ROM and it was working fine. Only after flashing this ROM did the LCD go black. How can I fix this? Flash with a PC? Which method should I use?
Sent from my SM-N910T using XDA Premium 4 mobile app
Was able to get into recovery with visible screen. Reflashed ROM again but still same result. Fired up the Android SDK and found the problem (extracted from Android SDK Device Monitor log-cat):
11-03 20:56:05.189: E/libgenlock(2954): genlock_wait: handle is invalid
11-03 20:56:05.189: E/Adreno200-EGLSUB(2954): GetBackBuffer() genlock_wait failed
11-03 20:56:05.189: E/Adreno200-ES20(2954): <gl2_surface_swap:41>: GL_OUT_OF_MEMORY
11-03 20:56:05.189: E/Adreno200-EGL(2954): <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC
11-03 20:56:05.209: E/Adreno200-ES11(2954): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY
11-03 20:56:05.219: E/Adreno200-ES11(2954): <qglDrvAPI_glTexSubImage2D:2055>: GL_OUT_OF_MEMORY
11-03 20:56:05.219: D/libgenlock(2954): Invalid gralloc handle (at 0xfda4c0): ver(12/12) ints(6/12) fds(1/2) magic(----/gmsm)
This keeps looping endlessly.
i_guana said:
Almost forgot. A few years back I remember that there were revisions of these phones that had a different chipset and I remember having to flash a special version of recovery or the display wouldn't work. Am I SOL with this ROM and recovery?
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i_guana said:
Was able to get into recovery with visible screen. Reflashed ROM again but still same result. Fired up the Android SDK and found the problem (extracted from Android SDK Device Monitor log-cat):
11-03 20:56:05.189: E/libgenlock(2954): genlock_wait: handle is invalid
11-03 20:56:05.189: E/Adreno200-EGLSUB(2954): GetBackBuffer() genlock_wait failed
11-03 20:56:05.189: E/Adreno200-ES20(2954): <gl2_surface_swap:41>: GL_OUT_OF_MEMORY
11-03 20:56:05.189: E/Adreno200-EGL(2954): <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC
11-03 20:56:05.209: E/Adreno200-ES11(2954): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY
11-03 20:56:05.219: E/Adreno200-ES11(2954): <qglDrvAPI_glTexSubImage2D:2055>: GL_OUT_OF_MEMORY
11-03 20:56:05.219: D/libgenlock(2954): Invalid gralloc handle (at 0xfda4c0): ver(12/12) ints(6/12) fds(1/2) magic(----/gmsm)
This keeps looping endlessly.
Click to expand...
Click to collapse
Is possible that the newest twrp isn't flashing correctly.
But from comments on ac forum where this is more active, I'm fairly sure the boot.img isn't getting written from the internal zip.
You can extract it (boot.img) to sdcard, and use twrp terminal to flash it...
Advanced > terminal command, navigate to sdcard.
Type
flash_image boot /sdcard/boot.img
Then reboot system and see if it starts up.
i_guana said:
Well, it shows the LG logo briefly. It also is booting into TWRP when I do the 3 button boot because I can turn the backlight on/off with the power button. There is just no display. I booted into recovery 3 times before I flashed the ROM and it was working fine. Only after flashing this ROM did the LCD go black. How can I fix this? Flash with a PC? Which method should I use?
Click to expand...
Click to collapse
I'm running into this same problem, except for me the ROM boots fine after installing alone, but as soon as I install the Sprint fix it just sits at the black screen. Please advise.
UPDATE: So, I downloaded Sprint fix.zip from AndroidCentral and it seems to work... well, sort of... it boots now, BUT isn't connecting to Sprint's network.
UPDATE2: Just for anyone else having this issue, I was on ZVJ when I installed this ROM, so I applied the ZVD to ZVJ patch found on forums.androidcentral.com /lg-optimus-s-rooting-roms-hacks/195081-patch-s-zvj-zvd-zvd-zvj-flashable-zips-optimus-s.html (sorry, I'm new and can't post links), and it is connecting up now.
Black screen won't boot
Partition sd card with twrp
Format /data and /system to f2fs
Wipe data,cache,dalvik
I have no file errors. I tried both builds..No GO
I can install my old crygen mod 7 works, but com.android processes don't work. Maybe I need to install old Gapps
Any Ideas why this build won't work?
Everything says success, except the os never loads I gave it 20 mins, doesn't work for Optimus V
It is pretty frustrating spent the whole day getting the file structure functional only to find out it wont load! Thanks for your work maybe we need a better guide. I will try searching some more
Little Hints
Setting up an old Optimus S for my dad because his HTC EVO bit the big one.
First off I used what I had on hand -- a class 4 8GB card -- I prefer class 10 ones.... but had to get something quick from what I had before I wanted to commit any extra money to this.
I had the Optimus S rooted and on ZVJ already running thekraven 10.1 from some time in the past and the Xionia recovery.
Activated the device with Freedompop (aka sprint MVNO) but then of course I have to get the thing to accept that --- so time to search for a ZVJ stockish rooted rom to get the thing activated..... I had an old copy of gRom 2.2 on my sd card, but I hunted out a copy of DanteRom -- which doesn't install properly under TWRP 2.8.0.0 even in Internal mode..... I had to use the "flash_image recovery xionia_cwma_recovery.img" to get back -- looks like it didn't swap the /data and /system so there was not enough room to install DanteRom or gRom 2.2 --- so simple -- reinstall TWRP from inside Xionia (which swapped /data and /system back) , then from inside TWRP put xionia_cwma back on (terminal command line)..... DanteRom won, and I had to do the ##7....# and enter the MSL to rest the MDN, etc to factory, then reboot and update profile and update PRL --- WIN!!!
Now to get this all active on this rom because I so wanted the os2sd function --
Back to TWRP 2.8.0.0 special version from the other thread -- then I got greedy -- set Partitions on SD in TWRP: System 1536, Swap 768, Data 2048 -- Leaving around 4GB as "internal SD Card".
Found when trying to flash the 20140930 ext4 that it would do the black screen thing... and I don't know if it is just me but I found that if I did a Switch to internal, wipe all but SD, then switch to OS2SD, wipe all but SD, then Install Rom, followed by gps conf, followed by sprint fix, followed by Skinny Gapps new, followed by ZVD to ZVJ rom patch (thanks) it would boot..... and had service --- no service with out that ZVD to ZVJ rom patch --- so thanks fellow poster for that tid bit. -- Boot still does LG logo and then a full 14 seconds of black screen before cyanogen mod spinny logo comes up -- and then like 5 min so be patient.
I then tried the same thing with the newer 201411 ext4 -- but that did the black screen thing -- even tried the "flash_image boot boot.img" -- but couldn't get love -- at this point its a class 10 card and wash rinse repeat with what worked until Dad can afford a new phone!!!
gfdos.sys said:
Setting up an old Optimus S for my dad because his HTC EVO bit the big one.
First off I used what I had on hand -- a class 4 8GB card -- I prefer class 10 ones.... but had to get something quick from what I had before I wanted to commit any extra money to this.
I had the Optimus S rooted and on ZVJ already running thekraven 10.1 from some time in the past and the Xionia recovery.
Activated the device with Freedompop (aka sprint MVNO) but then of course I have to get the thing to accept that --- so time to search for a ZVJ stockish rooted rom to get the thing activated..... I had an old copy of gRom 2.2 on my sd card, but I hunted out a copy of DanteRom -- which doesn't install properly under TWRP 2.8.0.0 even in Internal mode..... I had to use the "flash_image recovery xionia_cwma_recovery.img" to get back -- looks like it didn't swap the /data and /system so there was not enough room to install DanteRom or gRom 2.2 --- so simple -- reinstall TWRP from inside Xionia (which swapped /data and /system back) , then from inside TWRP put xionia_cwma back on (terminal command line)..... DanteRom won, and I had to do the ##7....# and enter the MSL to rest the MDN, etc to factory, then reboot and update profile and update PRL --- WIN!!!
Now to get this all active on this rom because I so wanted the os2sd function --
Back to TWRP 2.8.0.0 special version from the other thread -- then I got greedy -- set Partitions on SD in TWRP: System 1536, Swap 768, Data 2048 -- Leaving around 4GB as "internal SD Card".
Found when trying to flash the 20140930 ext4 that it would do the black screen thing... and I don't know if it is just me but I found that if I did a Switch to internal, wipe all but SD, then switch to OS2SD, wipe all but SD, then Install Rom, followed by gps conf, followed by sprint fix, followed by Skinny Gapps new, followed by ZVD to ZVJ rom patch (thanks) it would boot..... and had service --- no service with out that ZVD to ZVJ rom patch --- so thanks fellow poster for that tid bit. -- Boot still does LG logo and then a full 14 seconds of black screen before cyanogen mod spinny logo comes up -- and then like 5 min so be patient.
I then tried the same thing with the newer 201411 ext4 -- but that did the black screen thing -- even tried the "flash_image boot boot.img" -- but couldn't get love -- at this point its a class 10 card and wash rinse repeat with what worked until Dad can afford a new phone!!!
Click to expand...
Click to collapse
thanks for the info.
I've been away from this device for a while and the rom even longer.
I remember it had some real instability near the end of its run. older versions may be more stable. but may also need elder twrp too.
all the real discussion was over on android central as well. better documentation over there.
xda has been pretty dead in this forum for a long time.
Related
I've been running CM7 for a month or so and I started having some stability problems. So I decided to try DarkyRom.
I did everything like normal (used heimdall).
Upon boot it had an error.
Failed to mount /efs while applying multi-csc.
I'm dead in the water. I tried to flash back to stock. I get an error and thrown into samsung recovery. I can reboot from that and I boot to the gui with no radio. Phone info says "Unknown" Hardware and Baseband Version.
No. I did not backup any EFS (news to me). I do have access to the same model phone, my son has one he just uses as a fancy MP3 player (no phone/data plan).
Is there anything I can do? I did use the ADB Shell and ran "mount" to see if the EFS was mounted. It was a negative...
-MT
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
mainethoughts said:
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
Click to expand...
Click to collapse
First off,are you even on the right forum? Darky rom isn't built for this phone so it's not going to work.
Sent from my SCH-I500 using XDA App
Ugh...an unfortunate response. Yes...I'm on the right forum.
I did make a CWM backup from a couple weeks ago. Not sure if that helps.
mainethoughts said:
Ugh...an unfortunate response. Yes...I'm on the right forum.
Click to expand...
Click to collapse
Them why are you flashing roms from other forums/phones? Use odin and check repartition.
Sent from my SCH-I500 using XDA App
*hangs head* Admonishment accepted. I really don't know what I was thinking.
Here is my progress. I tried using Odin to just Re-partition. No go.
<ID:0/003> Can't open the specified file. (Line: 1455)
So then I downloaded stock EC10 (That was factory on my phone). I flashed that via Odin with "Success".
The same error as initially posted was on the phone. I rebooted from the stock recovery console and I was able to boot. 3g works. The hardware and baseband are now accurate. I'm getting a lot of force closes however. The twlauncher is constantly crashing.
So now the phone is semi-functional but there are still errors. (I was getting more forces than normal in CM7 that caused me to dive into this process in the first place).
I could be way off base but I'm thinking that possibly there is corruption (or wrong file system?) problems with the internal SD (I did format the External SD at the start of this).
I appreciate your help. Any suggestions from here?
-MT
Additional Note: Settings are not saved between reboots.
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
mainethoughts said:
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
Click to expand...
Click to collapse
Use the full odin restore package and make sure you use pit and pda files. Repartition must be checked. Wiping data might be a good idea as well.
Sent from my SCH-I500 using XDA App
I would odin the full mesmerize package EE19. http://forum.xda-developers.com/showthread.php?t=881064
That is what I have already done I believe. Followed instructions from:
http://forum.xda-developers.com/showthread.php?t=881064
-MT
If you've done that, then i'm at a loss. That usually is my solve-all solution... Sorry man.
Thank you much. Is it possible that I could have a faulty internal SD? I had suddenly started getting a lot of force closes in CM7. I guess I'm just wondering if I'm fighting two separate issues here. (My bonehead move vs. a real problem)
-MT
I think I'm FIXED!
I was finally (I don't know how) able to get Odin to Flash CWM 4 (The Blue one needed to install CM7).
I got ZERO errors in CWM. So I took the opportunity to clear caches, format data...I got destructive.
I then installed the CM7 Rom. -SUCCESS
Installed GAPPS - SUCCESS
I hope everything is OK at this point. I know CM7 is booting in about 20 seconds opposed to 5 minutes like it was before I decided to try to morph my phone into an I9000.
I actually saw the black screen with the little phone to PC icons at one point tonight. I think I came real close....
Thanks for your help!
PS: CONFIRMED mmcblk0p1 is mounted! (EFS, etc) PHEW!
I had this happen to me right after a Odin even did the rfs formatter tool exact same problems not saving settings upon reboot and it saying something along the lines of process.android.blah blah blah and double vibrate when booting before the fc anyhow I just reflashed miui to get cwm4 wiped everything reflashed cm7 no probs since
Sent from my SCH-I500 using XDA App
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes
Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?
yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)
baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links
The image was provided by Mr Rusty over on the P990 thread and i asked him if we can have an update..well he gladly helped out so don't forget to thank Mr Rusty over on his Thread..
I repacked and added a script that you will just run in order to flash this CWM version..(Thanks to Russ for the script)
From his Thread:
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
Click to expand...
Click to collapse
BIG Credits goes to Koush as well for his great work for innovating the CWM..
Get it Here: CWM 5.0.2.8 For P999 or from Here
Instructions on HOW to use/WHAT to do:(For Windows)
- Once you have downloaded the Package from the link Above..extract it to a Folder..
- Inside the folder all you have to do is look for the flash-recovery_xp.bat file..
- now turn your G2x OFF..
- remove the BATTERY and make sure your G2x is not connected to the PC via USB
- Press the VOLUME DOWN button together with the VOLUME UP..
- now CONNECT the USB Cable..
- If by all means Windows prompts for a new DEVICE you have to install the APX drivers from here(extract the package and manually install from this source)..
- Else if windows does not prompt OR you are already done installing the APX drivers you can now proceed on Running the flash-recovery_xp.bat by double clicking it..
- Choose 1 and Then press Enter..Wait for a few seconds till it prompts you that the FLASH was successful..IMHO you ought to wait another 5 more seconds after the prompt for not to have issues..
- After that Reboot into CWM by Pressing Power Button together with VOLUME DOWN til you see the LG Logo with waves..upon seeing that now release the buttons and wait for the CWM menu..
For Linux/Ubuntu Users:
- Download the Package
- Extract the folder somewhere
- Now turn your Phone OFF and DO NOT plug the USB cable yet..
- Now while Phone is OFF press VOLUME UP and DOWN together and now PLUG the USB cable in..keep them held together throughout the process..
- Run the Terminal and locate the Directory on where the Files are located..
- Type the ff:
Code:
chmod +x flash-recovery.sh
./flash-recovery.sh
- Once DONE you can now reboot..
FAQ:
Q: I am getting NVflash errors?
A: You might be on a BAD Cable or either way upon installing the drivers do a reboot..also DO THIS ON WINDOWS XP..on Windows 7 there are circumstances that the device is not recognized properly..also make SURE your unit is a P999 or P999DW(my unit is P999DW and touch WORKS!!) and not P990 or SU660..
Q: My device is not Recognized?
A: You have to download the APX drivers from one of the instructions above
Changelog: Github Source
Thanks and also vote for the page..
Seems the Chinese are on to this files too..lolz..
Thank you!! It flashed perfectly, no issues here.
Troy.
thegreenfamily04 said:
Thank you!! It flashed perfectly, no issues here.
Troy.
Click to expand...
Click to collapse
Glad it worked??
So internal and external mounting are all fine with this one?
Sent from my LG-P999 using xda premium
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Just flashed it with no problems , when are we getting the touch CWM? Now that will look sexy
thy for your work. coming from ClockworkMod 5.0.2.0 what are the differences / improvements? could someone explain please?
thanks in advance
Just an update: I flashed a MIUI rom (Look in my sig) used the "Nullifier 2.0" (Double wipe) and flashed the current Trinity Kernel all with no issues
Phone is running GREAT now! Thank you once again
Troy.
Волк said:
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Im getting a nvflash error when trying to install the new clockwork.
It says check apx driver and usb cable. The drivers are already installed so Im thinking its the usb cable, but not sure.
MWBehr said:
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Click to expand...
Click to collapse
the recovery's on a different partition, might make it a pain in the ass to access the touch drivers...
or he might just like the o2x more (everyone likes those Europeans more than us anymore)
Touch Recovery
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
mustangtim49 said:
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
Click to expand...
Click to collapse
It's all in the ram disk. Just swap out the vold.fstab in the ram disk. Recovery images are simply boot.imgs.
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
http://db.tt/rEpbpRfA here you go. Really interested on what you can do with it
Sent from my LG-P999 using Tapatalk
Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
that might work. Id try it out myself if i didn't f up my Linux install...
Nvidia graphics got the best of me there too
Sent from my LG-P999 using Tapatalk
Works as advertised! Thanks!
works great! thanks!
So, my idea worked? I'm not at home and since I'm a collision tech by trade, my boss don't like me playing with my phone. Volk, if you read this pm me and fill me in if you can. Thanks brother.
[email protected]
My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.
Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.
WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.
hello friends. have p509, 2.2 froyo, have rooted z4root, have cwm v5.0.2.0 installed. when I boot to recovery, I get the CWM menu, but no functionality - I can browse the top menu, but select any item and it misfires: [I get the logo].
The error msg is simply E:Bad boot message, "recovery"
the handset functions ok - boots fine, no issues that I can see.
Should I just overwrite this with a different recovery like amonRA or TWRP or should I flash the same cwm again?
Does CWM have a problem running from a 34GB SD Card? I searched my error and did not find on exact handset but on another and this was the implication, and a patch was offered for that handset, so I don't know if that is relevant here.
thanks for your guidance
c
cognus said:
hello friends. have p509, 2.2 froyo, have rooted z4root, have cwm v5.0.2.0 installed. when I boot to recovery, I get the CWM menu, but no functionality - I can browse the top menu, but select any item and it misfires: [I get the logo].
The error msg is simply E:Bad boot message, "recovery"
the handset functions ok - boots fine, no issues that I can see.
Should I just overwrite this with a different recovery like amonRA or TWRP or should I flash the same cwm again?
Does CWM have a problem running from a 34GB SD Card? I searched my error and did not find on exact handset but on another and this was the implication, and a patch was offered for that handset, so I don't know if that is relevant here.
thanks for your guidance
c
Click to expand...
Click to collapse
CWM 5.0.2.0 is buggy. I'd recommend changing to another recovery. I use a touch version on my P509, but it will only allow installation of P500 ROMs. There is a work-around for this tho. In the ROM is a file -> META-INF/com/google/android/updater-script. There is an 'assert' statement at the top of that script that can be edited to specify P509, or it can be removed all together. Of course, you can also use OOne ROM Editor to trim the ROM and remove the assert statement automatically.
The error message
E:Bad boot message, " recovery"
Click to expand...
Click to collapse
can be safely ignored. You'll get that every time you boot into recovery.
That error message means you dont have SD-ext. Ignore it.
Re-flash the recovery, cwm 5.0.2.0 is stable. Have you re-map your your hardware buttons?
If no.. try other keys.. menu button is to select.. when you see logo use power button.
Recovery is not related to your sd card size. 32GB is max our phone can support!!
FINALLY found a way to nuke CWM. I reloaded it a half dozen times but always the same outcome - zombie. thankfully did not brick.
finally found a GOOD correct instruction about flashing new recovery via LGMDP, added the partition file to the folder with Amon/thunderg and successfully got that one loaded. I can't count how many 'guides', tuts, steps, suggestions I read that never once mentioned the need for the partition.mbn file.
thanks for your responses, however.
rr0yy said:
That error message means you dont have SD-ext. Ignore it.
Re-flash the recovery, cwm 5.0.2.0 is stable. Have you re-map your your hardware buttons?
If no.. try other keys.. menu button is to select.. when you see logo use power button.
Recovery is not related to your sd card size. 32GB is max our phone can support!!
Click to expand...
Click to collapse
cognus said:
FINALLY found a way to nuke CWM. I reloaded it a half dozen times but always the same outcome - zombie. thankfully did not brick.
finally found a GOOD correct instruction about flashing new recovery via LGMDP, added the partition file to the folder with Amon/thunderg and successfully got that one loaded. I can't count how many 'guides', tuts, steps, suggestions I read that never once mentioned the need for the partition.mbn file.
thanks for your responses, however.
Click to expand...
Click to collapse
Glad you got it worked out. Requiring the partition.mbn is not a normal procedure around here. That's why it was never mentioned. I've flashed countless recoveries on the P509 which is identical to the P500 and then also on the P506. Apparently somehow your partition tables got screwed up.
wish I understood that better. I had the same issue with two different sd cards employed - everything else about the handset/rom etc all worked swell. never an issue... just the doggone CWM. I did notice on the small 2gb card that the optimus never would illuminate the Format option - I wiped it and wanted the handset to format but no option allowed. formatted it then with sdformat [win7].
the 32gb sandisk had been my main squeeze for a couple years on the p509
cognus said:
wish I understood that better. I had the same issue with two different sd cards employed - everything else about the handset/rom etc all worked swell. never an issue... just the doggone CWM. I did notice on the small 2gb card that the optimus never would illuminate the Format option - I wiped it and wanted the handset to format but no option allowed. formatted it then with sdformat [win7].
the 32gb sandisk had been my main squeeze for a couple years on the p509
Click to expand...
Click to collapse
Windows doesn't handle partitioning correctly for Linux file systems. Try this tool instead. I've never used it, although I do have it installed. It does come highly recommended.