Android OS Forum banner
521 - 540 of 558 Posts

·
Registered
Joined
·
9 Posts
I can't tell you, but it sounds like your device uses the initramfs system which I do not know how to build for. It does support the RFS filesystem and should now support BML - though I have no way to personally test it.
Ok I managed to flash it via ODIN, had to rename it to recovery.img and tar it. But when I went to try it out I ended up on the stock recovery... flashing went ok so I don't know what could have happened
 

·
Premium Member
Joined
·
223 Posts
Discussion Starter · #524 ·

·
Registered
Joined
·
6 Posts
Sprint Optimus S. Unable to find the 2.1.3 thunderg recovery zip, downloaded 2.1.4 thunderg recovery zip. Zip will not flash, unsigned. Bypassed sig verification, zip corrupted. Re-downloaded and same. Extracted flash_image and RZR.img and put on root of SD card. ADB shell:

Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system<br />
# cat /sdcard/flash_image > /system/bin/flash_image<br />
# chmod 755 /system/bin/flash_image<br />
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak<br />
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system<br />
# flash_image recovery /sdcard/RZR.img<br />
# reboot recovery
ADB terminal log:

Code:
Microsoft Windows [Version 6.1.7601]<br />
Copyright © 2009 Microsoft Corporation.  All rights reserved.<br />
<br />
C:\Users\Pat>adb shell<br />
* daemon not running. starting it now on port 5037 *<br />
* daemon started successfully *<br />
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system<br />
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system<br />
# cat /sdcard/flash_image > /system/bin/flash_image<br />
cat /sdcard/flash_image > /system/bin/flash_image<br />
# chmod 755 /system/bin/flash_image<br />
chmod 755 /system/bin/flash_image<br />
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak<br />
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak<br />
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory<br />
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system<br />
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system<br />
# flash_image recovery /sdcard/RZR.img<br />
flash_image recovery /sdcard/RZR.img<br />
flashing recovery from /sdcard/RZR.img<br />
mtd: successfully wrote block at 6299400000000<br />
mtd: successfully wrote block at 6299400020000<br />
mtd: successfully wrote block at 6299400040000<br />
mtd: successfully wrote block at 6299400060000<br />
mtd: successfully wrote block at 6299400080000<br />
mtd: successfully wrote block at 62994000a0000<br />
mtd: successfully wrote block at 62994000c0000<br />
mtd: successfully wrote block at 62994000e0000<br />
mtd: successfully wrote block at 6299400100000<br />
mtd: successfully wrote block at 6299400120000<br />
mtd: successfully wrote block at 6299400140000<br />
mtd: successfully wrote block at 6299400160000<br />
mtd: successfully wrote block at 6299400180000<br />
mtd: successfully wrote block at 62994001a0000<br />
mtd: successfully wrote block at 62994001c0000<br />
mtd: successfully wrote block at 62994001e0000<br />
mtd: successfully wrote block at 6299400200000<br />
mtd: successfully wrote block at 6299400220000<br />
mtd: successfully wrote block at 6299400240000<br />
mtd: successfully wrote block at 6299400260000<br />
mtd: successfully wrote block at 6299400280000<br />
mtd: successfully wrote block at 62994002a0000<br />
mtd: successfully wrote block at 62994002c0000<br />
mtd: successfully wrote block at 62994002e0000<br />
mtd: successfully wrote block at 6299400300000<br />
mtd: successfully wrote block at 6299400320000<br />
mtd: successfully wrote block at 6299400340000<br />
mtd: successfully wrote block at 6299400360000<br />
mtd: successfully wrote block at 6299400380000<br />
mtd: successfully wrote block at 62994003a0000<br />
mtd: successfully wrote block at 62994003c0000<br />
mtd: successfully wrote block at 62994003e0000<br />
mtd: successfully wrote block at 6299400400000<br />
mtd: successfully wrote block at 6299400000000<br />
# reboot recovery<br />
reboot recovery<br />
<br />
C:\Users\Pat>adb shell<br />
error: device not found
Rebooted to initial LG and stalled. Pulled battery and performed manual keypress recovery (home, vol up, pwr). Black screen and locked up. Pulled battery and booted to ROM, reflashed my old recovery (Xionia_cwma_12518.6.img). The old recovery writes to different blocks than yours:

Code:
<br />
# flash_image recovery /sdcard/xionia_cwma_12518.6.img<br />
flash_image recovery /sdcard/xionia_cwma_12518.6.img<br />
flashing recovery from /sdcard/xionia_cwma_12518.6.img<br />
mtd: successfully wrote block at b10c00000000<br />
mtd: successfully wrote block at b10c00020000<br />
mtd: successfully wrote block at b10c00040000<br />
mtd: successfully wrote block at b10c00060000<br />
mtd: successfully wrote block at b10c00080000<br />
mtd: successfully wrote block at b10c000a0000<br />
mtd: successfully wrote block at b10c000c0000<br />
mtd: successfully wrote block at b10c000e0000<br />
mtd: successfully wrote block at b10c00100000<br />
mtd: successfully wrote block at b10c00120000<br />
mtd: successfully wrote block at b10c00140000<br />
mtd: successfully wrote block at b10c00160000<br />
mtd: successfully wrote block at b10c00180000<br />
mtd: successfully wrote block at b10c001a0000<br />
mtd: successfully wrote block at b10c001c0000<br />
mtd: successfully wrote block at b10c001e0000<br />
mtd: successfully wrote block at b10c00200000<br />
mtd: successfully wrote block at b10c00220000<br />
mtd: successfully wrote block at b10c00240000<br />
mtd: successfully wrote block at b10c00260000<br />
mtd: successfully wrote block at b10c00280000<br />
mtd: successfully wrote block at b10c002a0000<br />
mtd: successfully wrote block at b10c002c0000<br />
mtd: successfully wrote block at b10c002e0000<br />
mtd: successfully wrote block at b10c00300000<br />
mtd: successfully wrote block at b10c00320000<br />
mtd: successfully wrote block at b10c00340000<br />
mtd: successfully wrote block at b10c00360000<br />
mtd: successfully wrote block at b10c00380000<br />
mtd: successfully wrote block at b10c003a0000<br />
mtd: successfully wrote block at b10c003c0000<br />
mtd: successfully wrote block at b10c003e0000<br />
mtd: successfully wrote block at b10c00400000<br />
mtd: successfully wrote block at b10c00420000<br />
mtd: successfully wrote block at b10c00440000<br />
mtd: successfully wrote block at b10c00460000<br />
mtd: successfully wrote block at b10c00480000<br />
mtd: successfully wrote block at b10c004a0000<br />
mtd: successfully wrote block at b10c00000000
I don't know if that has anything to do with anything at all.
 

·
Premium Member
Joined
·
223 Posts
Discussion Starter · #527 ·
Sprint Optimus S. Unable to find the 2.1.3 thunderg recovery zip, downloaded 2.1.4 thunderg recovery zip. Zip will not flash, unsigned. Bypassed sig verification, zip corrupted. Re-downloaded and same. Extracted flash_image and RZR.img and put on root of SD card. ADB shell:

Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system<br />
# cat /sdcard/flash_image > /system/bin/flash_image<br />
# chmod 755 /system/bin/flash_image<br />
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak<br />
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system<br />
# flash_image recovery /sdcard/RZR.img<br />
# reboot recovery
ADB terminal log:

Code:
Microsoft Windows [Version 6.1.7601]<br />
Copyright © 2009 Microsoft Corporation.  All rights reserved.<br />
<br />
C:\Users\Pat>adb shell<br />
* daemon not running. starting it now on port 5037 *<br />
* daemon started successfully *<br />
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system<br />
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system<br />
# cat /sdcard/flash_image > /system/bin/flash_image<br />
cat /sdcard/flash_image > /system/bin/flash_image<br />
# chmod 755 /system/bin/flash_image<br />
chmod 755 /system/bin/flash_image<br />
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak<br />
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak<br />
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory<br />
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system<br />
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system<br />
# flash_image recovery /sdcard/RZR.img<br />
flash_image recovery /sdcard/RZR.img<br />
flashing recovery from /sdcard/RZR.img<br />
mtd: successfully wrote block at 6299400000000<br />
mtd: successfully wrote block at 6299400020000<br />
mtd: successfully wrote block at 6299400040000<br />
mtd: successfully wrote block at 6299400060000<br />
mtd: successfully wrote block at 6299400080000<br />
mtd: successfully wrote block at 62994000a0000<br />
mtd: successfully wrote block at 62994000c0000<br />
mtd: successfully wrote block at 62994000e0000<br />
mtd: successfully wrote block at 6299400100000<br />
mtd: successfully wrote block at 6299400120000<br />
mtd: successfully wrote block at 6299400140000<br />
mtd: successfully wrote block at 6299400160000<br />
mtd: successfully wrote block at 6299400180000<br />
mtd: successfully wrote block at 62994001a0000<br />
mtd: successfully wrote block at 62994001c0000<br />
mtd: successfully wrote block at 62994001e0000<br />
mtd: successfully wrote block at 6299400200000<br />
mtd: successfully wrote block at 6299400220000<br />
mtd: successfully wrote block at 6299400240000<br />
mtd: successfully wrote block at 6299400260000<br />
mtd: successfully wrote block at 6299400280000<br />
mtd: successfully wrote block at 62994002a0000<br />
mtd: successfully wrote block at 62994002c0000<br />
mtd: successfully wrote block at 62994002e0000<br />
mtd: successfully wrote block at 6299400300000<br />
mtd: successfully wrote block at 6299400320000<br />
mtd: successfully wrote block at 6299400340000<br />
mtd: successfully wrote block at 6299400360000<br />
mtd: successfully wrote block at 6299400380000<br />
mtd: successfully wrote block at 62994003a0000<br />
mtd: successfully wrote block at 62994003c0000<br />
mtd: successfully wrote block at 62994003e0000<br />
mtd: successfully wrote block at 6299400400000<br />
mtd: successfully wrote block at 6299400000000<br />
# reboot recovery<br />
reboot recovery<br />
<br />
C:\Users\Pat>adb shell<br />
error: device not found
Rebooted to initial LG and stalled. Pulled battery and performed manual keypress recovery (home, vol up, pwr). Black screen and locked up. Pulled battery and booted to ROM, reflashed my old recovery (Xionia_cwma_12518.6.img). The old recovery writes to different blocks than yours:

Code:
<br />
# flash_image recovery /sdcard/xionia_cwma_12518.6.img<br />
flash_image recovery /sdcard/xionia_cwma_12518.6.img<br />
flashing recovery from /sdcard/xionia_cwma_12518.6.img<br />
mtd: successfully wrote block at b10c00000000<br />
mtd: successfully wrote block at b10c00020000<br />
mtd: successfully wrote block at b10c00040000<br />
mtd: successfully wrote block at b10c00060000<br />
mtd: successfully wrote block at b10c00080000<br />
mtd: successfully wrote block at b10c000a0000<br />
mtd: successfully wrote block at b10c000c0000<br />
mtd: successfully wrote block at b10c000e0000<br />
mtd: successfully wrote block at b10c00100000<br />
mtd: successfully wrote block at b10c00120000<br />
mtd: successfully wrote block at b10c00140000<br />
mtd: successfully wrote block at b10c00160000<br />
mtd: successfully wrote block at b10c00180000<br />
mtd: successfully wrote block at b10c001a0000<br />
mtd: successfully wrote block at b10c001c0000<br />
mtd: successfully wrote block at b10c001e0000<br />
mtd: successfully wrote block at b10c00200000<br />
mtd: successfully wrote block at b10c00220000<br />
mtd: successfully wrote block at b10c00240000<br />
mtd: successfully wrote block at b10c00260000<br />
mtd: successfully wrote block at b10c00280000<br />
mtd: successfully wrote block at b10c002a0000<br />
mtd: successfully wrote block at b10c002c0000<br />
mtd: successfully wrote block at b10c002e0000<br />
mtd: successfully wrote block at b10c00300000<br />
mtd: successfully wrote block at b10c00320000<br />
mtd: successfully wrote block at b10c00340000<br />
mtd: successfully wrote block at b10c00360000<br />
mtd: successfully wrote block at b10c00380000<br />
mtd: successfully wrote block at b10c003a0000<br />
mtd: successfully wrote block at b10c003c0000<br />
mtd: successfully wrote block at b10c003e0000<br />
mtd: successfully wrote block at b10c00400000<br />
mtd: successfully wrote block at b10c00420000<br />
mtd: successfully wrote block at b10c00440000<br />
mtd: successfully wrote block at b10c00460000<br />
mtd: successfully wrote block at b10c00480000<br />
mtd: successfully wrote block at b10c004a0000<br />
mtd: successfully wrote block at b10c00000000
I don't know if that has anything to do with anything at all.
try dd? not sure if it will make a difference, I'd just use flash_image in adb in clockwork and try it that way. Does the device has fastboot? you might try just fastboot boot'ing it to see if it even works
 

·
Registered
Joined
·
6 Posts
try dd? not sure if it will make a difference, I'd just use flash_image in adb in clockwork and try it that way. Does the device has fastboot? you might try just fastboot boot'ing it to see if it even works
OK, direct downloaded the image and zip. Recovery says zip is still broken but I was able to flash the image thru ADB. This time, it looks like it wrote on the same blocks that Xionia writes to, so I had hope. No joy.

So I started to look up "fastboot" and it appears that it doesn't work for the "S" series, even tho I have the proper ADB driver installed. Fastboot sticks at <waiting for device>. One thing I did learn today is that the part where my LG stops on boot is called "stuck in fastboot". This must be the reason why ROM Managers brick our phones (Optimus S's).

Oh well, it was a nice try. Thanks for your time!!
 

·
Premium Member
Joined
·
223 Posts
Discussion Starter · #529 ·
boot it and then when its running, or stuck at an LG screen, run ddms (in the android sdk), then try to capture the screen. I might be missing a custom graphics library and the recovery is unable to display. does adb devices detect anything when its stuck at the screen>?
 

·
Registered
Joined
·
6 Posts
boot it and then when its running, or stuck at an LG screen, run ddms (in the android sdk), then try to capture the screen. I might be missing a custom graphics library and the recovery is unable to display. does adb devices detect anything when its stuck at the screen>?
Code:
<br />
C:\Android\android-sdk\tools>ddms<br />
Error Loading Preferences<br />
06:08:05 E/ddms: shutting down due to uncaught exception<br />
06:08:05 E/ddms: Invalid thread access<br />
org.eclipse.swt.SWTException: Invalid thread access<br />
	    at org.eclipse.swt.SWT.error(Unknown Source)<br />
	    at org.eclipse.swt.SWT.error(Unknown Source)<br />
	    at org.eclipse.swt.SWT.error(Unknown Source)<br />
	    at org.eclipse.swt.widgets.Display.checkDisplay(Unknown Source)<br />
	    at org.eclipse.swt.widgets.Display.create(Unknown Source)<br />
	    at org.eclipse.swt.graphics.Device.<init>(Unknown Source)<br />
	    at org.eclipse.swt.widgets.Display.<init>(Unknown Source)<br />
	    at org.eclipse.swt.widgets.Display.<init>(Unknown Source)<br />
	    at com.android.ddms.UIThread.runUI(UIThread.java:426)<br />
	    at com.android.ddms.Main.main(Main.java:103)<br />
<br />
C:\Android\android-sdk\tools>adb devices<br />
List of devices attached<br />
<br />
<br />
C:\Android\android-sdk\tools>
This is what I get when I reboot. I can't screen capture on either the phone or on screencast. Screencast is stuck at the right before I reboot. I've tried both manual, keypress recovery and "adb reboot recovery". I have power, keys are lit, screen has backlighting but is displaying black.

curiousnoob said:
Optimus V recovery? :s
Messes up my hard keys. Swaps "back" and "menu".
 

·
Registered
Joined
·
6 Posts
I forgot to point out that my phone has a "special" graphics issue that some newer Optimuses have when LG changed LCDs. I ran into an issues once with graphic drivers and the older Radio/ROMs for my phone and had to use Screencast to see what was happening in recovery. This isn't the case, as my phone won't go into recovery.
 

·
Registered
Joined
·
6 Posts
OK, on the OP, the Optimus S is linked to the thunderg recovery. That's what's been wrong this entire time. I needed a thunderc recovery and found it with the Optimus V. It flashed and booted into recovery. The graphics driver is the old driver, so I had to use screencast, but it's there and it works.

Thanks RZR!!! And sorry for the confusion!!
 

·
Registered
Joined
·
60 Posts
Just wanted to say I just tried the latest 2.1.4 (from 12-18) and I was able to make a backup (I'm on an ICS ROM)

Thank you again.. IDK why I couldn't make backup's before, but for now everything seems fine
i was getting ready to post that i was running into this same issue and assumed that the latest 2.1.4 build (12-25) for the nexus s 4g was broken; however, it looks like this issue can be attributed to the specific rom you're running at the time you attempt to use rzr. or rather, to the build.prop file.

in my case, i'm running one of the alpha/beta ics roms by vhgomez36 in the xda forums. i had noticed that the nandroid backup would break throwing the following error message in the log:

Code:
mkdir: can't create directory '/sdcard/nandroid/IML74K<br />
-BDSA-20120105-1810': Invalid argument
it seemed that rzr was reading the build.prop file and grabbing the ro.build.id from it. viewing the error on screen, it appeared that the recovery was reading the the ID with an extra line break or at least a space and so rather than creating a folder without spaces (which I guess is a requirement) it was trying to create "/sdcard/nandroid/IML74K -BDSA-20120105-1810".

So, I started digging through the build.prop file from my ICS rom. Opened it up in Notepad++ and didn't see anything unusual. So I decided to compare it to a CM build.prop using WinMerge. And that's where I got a prompt from WinMerge that the carriage returns were different. CM uses a UNIX style carriage return. vhgomez36's rom used a Windows/Dos style carriage return. WinMerge (in the File menu) had an option for converting the file to UNIX style. I did so, pushed it back onto the phone, and Nandroid worked!

Sorry for being so wordy, but it was kind of fun troubleshooting this issue. RaidZero, hope it helps you either find a way to ignore the alternate carriage returns or build around them. I do enjoy your recovery. Thanks!

EDIT:
Oh and if this is something you think is a bug to report to the rom developer, just let me know.
 

·
Registered
Joined
·
60 Posts
i have another bug to report. the latest version 2.1.4 has a restore clockworkmod backup option. i've tried it a couple times now and it fails while unpacking. flies through unpacking the system.ext4.tar file and always hangs on the data.ext4.tar file. i've tried giving it a lot of time (more than 20 minutes) and it doesn't budge. thankfully, no changes are made to the phone's current os and so i'm still able to reboot into my working rom.
 

·
TechyGeek
Joined
·
37 Posts
You can add the LG Esteem to your list of working. Only things not working is being able to manually mount boot to wipe it manually, tho many phones are like this for some reason. And USB Mass Storage, all other functions seem to be working fine n already has a small fan base that like it.
 

·
Android Beginner
Joined
·
30 Posts
Hey Raid....whats the hap with the GNex and the D1...I still use your 2.0.3 on my Droid but I would love to have all the new toys to play with....And I really wish you had one for a GNex.
 

·
Registered
Joined
·
60 Posts
Just tried out the latest 2.1.4 for the ns4g (Jan 11) and see that nandroid still doesn't work if/when the build.prop file is saved in dos/windows format (using dos/windows carriage returns).

also (in case anyone else is interested, clockworkmod restore has been removed again).
 
521 - 540 of 558 Posts
Top