Database Info

[Q] My CWM 3.x.x.x backup doesn't work : SGS2

Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.

download cwm 2.5.x.x its better

[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?

OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm

Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!

You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.

Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App

Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.

I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.

[ROM][SGH-S730M] Stock deodexed + rooted + overclocked

This is a DEV thread, this is not yet working
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked

problem
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...

problem
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
[/URL]
Click to expand...
Click to collapse
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...

E signature verification keeps failing

bil4554lel said:
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...
Click to expand...
Click to collapse
Not sure, haven't tried to install this yet, BUT when in recovery, given you have a custom recovery installed, you shouldn't be trying to "apply update from zip" you should be selecting "install from zip". If you are using a stock recovery, you won't be able to flash a ROM. You need to flash a custom recovery such as twrp or cwm using Odin from a PC.
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
I have this old gem of a phone and have been looking forever for a custom ROM. Don't know where you pulled the stock from as I've been trying to dump it off the phone unsuccessfully to mod with Android kitchen. I'll flash this and update with my results

I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8

atmu5fear said:
I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8
Click to expand...
Click to collapse
Hi, i get too the same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?

Bibounet said:
Hi, i get it too, and same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?
Click to expand...
Click to collapse
I'm definitely interested in developing a custom ROM for this phone. I bought this phone nearly two years ago, and although I have since upgraded, I seem to always have use it as a back up when my t989 has issues. I know there is a ton of demand for a custom ROM for this phone. I was reading a bunch about META-INF folders and Android kitchen for developing a ROM without having a current base to work with. I'll look into it a bunch more throughout the week, this weekend etc. See if I can get a flashable zip after deodexing and overclocking using the thread the OP of this one used. I read on another forum, after googling "cwm status 255" that this has to do with the updated-binary file in the META-INF folder. The suggestion that worked for the op of that thread was to take the updated-binary file from another flashable zip (for the same phone) and use it to replace the updated-binary file in the zip giving the 255 error. So I took the file from the deodexing zip for this phone and replaced it, not expecting it work, but just to see. Cwm no longer gives the 255 code, but still aborts the installation, with no code given. So it seems this very well could be a start.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem

atmu5fear said:
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem
Click to expand...
Click to collapse
That may very well be it, I'm gonna change it and reupload
Check back in a bit. Appreciate the help

I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role

I just threw together a flashable zip of this rom quickly on android kitchen. I used the META-INF folder from the thread I previously linked to. It's been deodexed and rooted, but I didn't bother with the overclock. Once we can get a flashable zip that works, i figure we'll go from there. I'm going to flash it to the phone now, and see if it will complete and boot.
I'm getting a status 0 error code. I'm going to rebuild without converting to edify. Will update

Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.

Bibounet said:
Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.
Click to expand...
Click to collapse
The overclock is built into the kernel, clocks it from 800mhz to 1000mhz, any one who wants to run it without the higher clock, can just use any CPU control app and set the max to 800.
Without modding the kernel you actually can't overclock past 800mhz using any CPU control app.
---------- Post added at 03:28 AM ---------- Previous post was at 03:20 AM ----------
Restl3ss said:
I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role
Click to expand...
Click to collapse
The Tab 3 runs on intel and the discover runs on ARM.
From everything I can find this is definitely the problem. Although just replacing the binary itself, and rebuilding hasn't seemed to accomplish anything other than no longer giving the error code. Just aborts. I've read your updater-script and none of the ui messages show up or anything from within that script during install.

@Restl3ss I swapped out the binary from another flashable zip for the same phone, from within the kitchen using your flashable zip. Kept your updater script and other than that the only other change was I zipaligned. I rebuilt it, flashed it. The install doesn't abort, and completed. But none of your ui code from script appears during install, and nothing actually installed to the phone, it just boots straight into recovery. Since I have no idea how to decipher what I'm reading in the binary using notepad++, I'll leave it to your expertise to sort out the rest. I'm only just getting into this developing bit and so far have reached my limit of what I can help you with, as far as getting a base to flash and install successfully. I tried to get a report using adb logcat after it kept booting into recovery but the log remained empty.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."

Joel-Tang said:
just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."
Click to expand...
Click to collapse
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

atmu5fear said:
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz

Restl3ss said:
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz
Click to expand...
Click to collapse
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

atmu5fear said:
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the more information you can get me the better, thanks a ton for the help

[Q] Installation failed CM 10.2 on HTC Google Nexus One

My first post Hurray!
Hi guys.
I want to install Android 4.3 to my HTC Google Nexus One. I followed this post.
I installed everything needed and when I try to install the update I get the following results:
Formatting System
Installing CM 10.2
Setting symlinks and premissions...
Setting symlinks...
Setting permissions..
set_perm: some changed failed
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have Fastboot access to the phone when connected via USB to my Windows 7 laptop.
I am using recovery versions 5.0.2.0 for my Google Nexus One phone.
Flashing ROM: CM 10.2 Rom for the N1
How can I solve this issue, need your help. Thanks in advance. :cyclops:
Other things I've tried: Flashing the rom from boot.img from the zipped file via fastload
I also checked for assert command in the script file but there aren't any.

IdanShechter said:
My first post Hurray!
Hi guys.
I want to install Android 4.3 to my HTC Google Nexus One. I followed this post.
I installed everything needed and when I try to install the update I get the following results:
I have Fastboot access to the phone when connected via USB to my Windows 7 laptop.
I am using recovery versions 5.0.2.0 for my Google Nexus One phone.
Flashing ROM: CM 10.2 Rom for the N1
How can I solve this issue, need your help. Thanks in advance. :cyclops:
Other things I've tried: Flashing the rom from boot.img from the zipped file via fastload
I also checked for assert command in the script file but there aren't any.
Click to expand...
Click to collapse
might need to get a higher vesion of CWM. otherwise google Status 7 error

Hi,
Which version is recommended, the highest that is compatible. According to the ROM manager page of clockworkmod, this is the only one available for the nexus one.

IdanShechter said:
Hi,
Which version is recommended, the highest that is compatible. According to the ROM manager page of clockworkmod, this is the only one available for the nexus one.
Click to expand...
Click to collapse
you would have to get a ported (non offical: should work just as fine as offical but there could be some other added stuff.) version since you want Cm 10.2 5.x.x.x should work but just to be on the safe side you should try getting 6.0.4.5. should only have to download a zip of whatever you find and flash it in your current recovery.

Trozzul said:
you would have to get a ported (non offical: should work just as fine as offical but there could be some other added stuff.) version since you want Cm 10.2 5.x.x.x should work but just to be on the safe side you should try getting 6.0.4.5. should only have to download a zip of whatever you find and flash it in your current recovery.
Click to expand...
Click to collapse
I get Image Update Error when updating the 6.0.4.5 version. I've chosen on for another device because there isn't any 6.0.4.5 version for Nexus One.

I checked the free available space. In the SD Card I've have plenty (more than 2GB), but /system has 0% available. This might cause the flash to fail. Is there any option to free up space before I flash the ROM?
Update: even after formatting the system directory I still get the same error, this it not the problem so it seems.

IdanShechter said:
I checked the free available space. In the SD Card I've have plenty (more than 2GB), but /system has 0% available. This might cause the flash to fail. Is there any option to free up space before I flash the ROM?
Update: even after formatting the system directory I still get the same error, this it not the problem so it seems.
Click to expand...
Click to collapse
your gonna have to ask the nexus ones offical Q&A then http://forum.xda-developers.com/nexus-one/help if i right with this problem you have to do something specifically and differently for every device so just ask the pros on your device first.

IdanShechter said:
My first post Hurray!
Hi guys.
I want to install Android 4.3 to my HTC Google Nexus One. I followed this post.
I installed everything needed and when I try to install the update I get the following results:
I have Fastboot access to the phone when connected via USB to my Windows 7 laptop.
I am using recovery versions 5.0.2.0 for my Google Nexus One phone.
Flashing ROM: CM 10.2 Rom for the N1
How can I solve this issue, need your help. Thanks in advance. :cyclops:
Other things I've tried: Flashing the rom from boot.img from the zipped file via fastload
I also checked for assert command in the script file but there aren't any.
Click to expand...
Click to collapse
Status 7 error comes due to system folder being full.. I m not a nexus one user and its a common problem..
Open the rom zip of your file delete some apps from system/app then flash the rom..
This will solve your status 7 error..

[Q&A] [ROM+kernel][WIP] [4.4.4][CM11][OS2SD][f2fs][EXPERIMENTAL]bigsuperROM-thunderc

[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.

[STOCK][TWRP BACKUP][UPDATE] AT&T H910_10L Stock Recovery, Boot, and System Image

Below are links to full backups that can be restored in TWRP for the H910 after the Dirty Santa exploit. This is useful for restoring a bad install once you have access to TWRP. I will outline three methods for install below that will help in putting back the TWRP backups, a good method for installing it, and a few suggestions I have from restoring my device about 10 times now. So without further ado.
UPDATE: I bricked my device and had to send it off for repair (turns out I can't just flash US996 firmware for funsies) I received my phone back with the still rootable OTA 10L and yesterday I rooted it again and uploaded the new firmware. So if you're an AT&T user who wants the second latest update (10M dropped 04-15 but it isn't rootable as far as I know) then you can grab this and run it along with the stock kernel I made a backup of. I'll update the links below to reflect this. Stock 10L kernel located in tips section. Not flashable, you must extract and install as image and immediately install SuperSU 2.79 or greater or your device won't boot!
How to Install and Restore Stock Images and Boot (Kernel) Image
1.) DOWNLOAD - https://www.androidfilehost.com/?fid=673368273298948069 (Updated to 10L) download the file and verify the MD5sum of the zip matches the file you downloaded. (System image link for devs posted at the bottom)
1a) Download the latest SuperSU 2.79 flashable zip from here: http://www.supersu.com/download
2.) EXTRACT --This is not a flashable zip-- extract the zip file wherever you would like so that it can be copied to the device
3.) COPY - The extracted folder to TWRP > BACKUPS > (paste here) on either the MicroSD card (preferable) or internal storage (This will be wiped when you format data)
4.) REBOOT TO RECOVERY - Once the folders are copied to the backup directory you can reboot to TWRP to begin the restore process.
5.) WIPE - This is getting two sections in order to account for two situations
5a) MICROSD - If you have a MicroSD card and copied the restore files to it wipe everything: Data, Cache, Dalvik/ART, Internal Storage, and System.
5b) INTERNAL STORAGE - If you don't have a MicroSD card installed only wipe the following: Data, Cache, Dalvik/ART, and System.
6.) REBOOT TO RECOVERY - Once you have wiped everything, especially if you wiped internal storage, you should reboot TWRP before you start the restore process
7.) RESTORE - Back in TWRP Choose Restore from the main menu and if you can't see your restore file choose "Select Storage" at the bottom and inside that folder uncheck RECOVERY unless you want to overwrite TWRP (which I recommend against).
7a) I would recommend checking the box "Enable MD5 Verification of Backup Files" which is a little slower but ensures a good restoration
8.) SWIPE - Swipe to begin the operation and it will alert you upon completion. You will need a very large amount of space on your card to do it since the system image is split into 3 packages
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo.
10.) REBOOT TO SYSTEM - The phone will reboot itself! Don't panic, this is part of the standard rooting procedure. Now, see tips at the bottom for best performance.
TIPS!
- This is the 10L update stock kernel made during dirty santa method. This kernel has all features working minus the static on boot being gone, but Wifi calling, comfort view, FM radio, etc are fixed using this kernel. https://www.androidfilehost.com/?fid=817550096634762281 (You must flash SuperSU 2.79 or greater after flashing this kernel before you reboot! Not Flashable, must extract)
- To use the above kernel, download his ROM and extract the boot.img file from that archive. Save it to your device, boot to TWRP, choose Install, Install Image, and click the boot.img file. Then choose the checkbox for "boot" and swipe to flash. Really important to install SuperSU again after installing the custom kernel.
- Boot-up static can be cleared by allowing phone to boot to screen off, placing it face down to turn of second screen, and then flipping it back over. Static will be gone until next boot.
- Using fstrim after wiping in TWRP is good for increasing flash drive performance. Go to TWRP > Advanced > Terminal and type fstrim -v /data/
- You can do fstrim on /system and /cache as well to get all three partitions running clean
- Some of the AT&T apps that you can remove with TiBu are tied to bootup. Be careful what you remove if you like to get past the AT&T logo.
- The button combo to get into TWRP from powered off is Vol Down + Power until the LG Logo appears then let go of power and immediately press power again.
- That button combo boots you to a screen asking it you want to wipe your device. Answering 'yes' to both questions boots you to TWRP.
10L System Image Link for ROM creation (In TWRP emmc format): https://www.androidfilehost.com/?fid=745425885120724506
THANKS!
Google - Because, Android
@me2151 for the unlock and root method (and bricking his phone for us; sorry that happened to your device)
@glitschi667 for the work he did on Dirty Santa with me2151
@jcadduono for getting TWRP ready for us despite not having a V20 at all
@Tilde88 for compiling the kernel sources and creating an excellent ROM for all rooted variants of the device!
@EMSpilot for the debug phone!
@elliwigy for helping everyone troubleshoot and test everything recently
If I forgot you, and believe me a lot of people deserve to be here, let me know and I'll add you

9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. [/QUOTE] What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?

jreed3786 said:
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
Click to expand...
Click to collapse
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.

AlkaliV2 said:
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
Click to expand...
Click to collapse
Shoot...I think I followed your instructions in Tilde88's thread....and hit reboot instead of flashing his kernel. I then went back in to TWRP to reflash the entire thing...and the kernel...and I was given crap about encryption. Then, that's when the bootloop started. Right now, I'm sitting on TWRP. I've tried flashing everything, per instructions....but I guess, what I'm asking, is...since I'm on TWRP...and it's bootlooping because of encryption...what would you personally do? Shoot...I'll pay ya if you can fix this! LOL. I just really never dealt with the encryption thing until this phone...never really had problems till now.
---------- Post added at 09:28 AM ---------- Previous post was at 09:12 AM ----------
FLASHED EXACTLY THE WAY YOU DID (WITHOUT THE REBOOTING TO RECOVERY IN THE OP)...NOW, IT GETS TO STATIC, THEN LG SCREEN, REBOOTS ONCE TO STATIC THEN BOOTS UP!!! YAY!!! :good::highfive:
I guess there's no need to REBOOT TO RECOVERY if a person faces encryption issues and is trying to fix their phone. Even after decrypting, I came up with issues. Now let's see if this this asks for my PIN on reboot. THAT was another issue!
IT WORKED!!! THANKS! I'LL now try to go back into TWRP and flash the Tilde's boot.img

So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:

jreed3786 said:
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
Click to expand...
Click to collapse
Nothing like some good news to start the day. I wanted to let you know that the reason this worked is that it is essentially a dirty flash that replaces the stock kernel and adds his ROM tweaks into my stock system. So once it had booted and you flashed over it you were able to keep the stock files needed to get screen off Google Now working while adding his audio tweaks and build.prop because they overwrite the stock files. Since my stock files are odexed and his are not I'm not sure how well all your system files will function since they've been overwritten but if you have no issues then no harm, no foul.
I'm glad this got sorted and to anyone else if you follow this guide and you have any confusion about the instructions just do an @AlkaliV2 and I will do my best to help and I will also fix up the guide so that it is less confusing. Just let me know.

Stuck again....in TWRP.
Delete please

Same issue
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.

Great step by step instructions. Thanks!

sikiro said:
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Click to expand...
Click to collapse
Try booting into your bootloader (fastboot) and type:
fastboot erase misc
fastboot erase cache
fastboot erase fota
fastboot reboot
See if that helps you at all. Make sure you have a valid ROM flashed correctly though.

im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?

prlatorre said:
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
Click to expand...
Click to collapse
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.

ajairola said:
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
Click to expand...
Click to collapse
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd

prlatorre said:
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
Click to expand...
Click to collapse
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?

how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.

truwrxtacy said:
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
Click to expand...
Click to collapse
You cant all you can do is factory reset on stock

jerrycoffman45 said:
You cant all you can do is factory reset on stock
Click to expand...
Click to collapse
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).

Manbot27 said:
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Click to expand...
Click to collapse
right now the root method for the h910 does not allow you to go back to stock

My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
AlkaliV2 said:
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
Click to expand...
Click to collapse
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.

cwis said:
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
Click to expand...
Click to collapse
If you create a backup of anything on the Microsd card before you attempt to put the folder in it, it will create the directories for you and all you have to do is copy and paste at that point.