Database Develop

can anyone help me please?

ive flashed to Android 1.6 Recovery Image. and my market doesnt work nor can i flash to anything else.. it will start the update and then abort.. is there anything i can do?

oh my goodness...wrong forum, were u trying 2 flash Cyanogens rom?

yes i was =( can you please direct me to the correct place to ask for help.. thanks in advance

the mods will move it soon, and did u not follow the directions in Cyanogens thread, [email protected] usually all u need

i somehow managed to skip a step .. and i really messed up =(

well idn cuz this has never happend to me, but try a wipe and try reflashing the recovery image, and the rom, but dont skip a step

Help has Arrived!
Cyan's 1.4 Pimped Out Recovery Image:http://forum.xda-developers.com/showthread.php?p=3915123
To install image: copy it to your sdcard and run:
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a “no space on device” error, try using fastboot and erasing first:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
Changes in 1.4:
* Flash ANY .zip from your SD – by krut0n
* New color scheme and images (background from a random wallpaper site, if it’s yours let me know)
* Fixes from Donut
* Updated nandroid-mobile.sh w/ network support from pensive
* Updated GNU Parted (ext4 support, etc)
TMO OTA DRC83 - US
-- Rooted Base - http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO-OTA-US-DRC83-Rooted_update.zip
----- v1.9.2 Expansion Pack - (10/4/2009)http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO_1.6_ExpPack_v1.9.2.zip
CM-4.1.99+
Install instructions from SimpleHelp:http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Install instructions for an HTC Dream/ADP1/G1:
1- Perform a Backup......nandroid, etc
2- Download:http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image.This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download Cyan's ROM. Posted Below
4- Mount your phone and place BOTH 1.6 Image and my ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
8- Apply sdcard:choose zip *Pick cm-4.1.99-signed.zip* from the list.
9- Reboot!
(v4.1.999 - almost-stable-beta version, updated 10/4):
Download:http://n0rp.chemlab.org/android/experimental/update-cm-4.1.999-signed.zip
Mirror1:http://android.phaseburn.net/mirrors/cyanogen/experimental/update-cm-4.1.999-signed.zip
MD5Sum: 7f8b377c5ded60e057140119ab2a3fbd
Audio Resources (unzip to your SD card):
Download:http://n0rp.chemlab.org/android/audio-resources.zip
MD5Sum:7340ba86ddd4fba918ef97601c675ef9
HTC Touch Input:http://forum.xda-developers.com/showthread.php?t=567294
Code Repository on Github:http://github.com/cyanogen
CHANGELOG
---- v4.1.999
* BFS-303 (fixes some regressions like statusbar fling)
* Fixed BT not working (firmware)
* Updated APN list
* New wallpapers from matt_stang
* Fixed crazy compcache settings
* Fixed syntax error in userinit startup
* Fixed build.prop files
* Patch for LocationManagerService wakelock issue
* More nines
---- v4.1.99
* Now 100% open source (TMO apps are included, not sure of licensing on those yet)
* Tons and tons of bugfixes and enhancements, read the Github logs and old threads for now
* Kernel is 2.6.29.6 with BFS-302 and framework changes to support it.
* HTC Framework and apps are gone, deal with it. See the link above for HTC_IME.
THIS SHOULD HELP YOU OUT! If not,I don't know what can help you.Keep looking if you can't figure this out. But here's the help you asked for. Good luck with the flashing man!
OR - GO to the HTC Website and Look for Android 1.6!: http://developer.htc.com/adp.html#s3

andy_lowe02 said:
Cyan's 1.4 Pimped Out Recovery Image:http://forum.xda-developers.com/showthread.php?p=3915123
To install image: copy it to your sdcard and run:
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a “no space on device” error, try using fastboot and erasing first:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
Changes in 1.4:
* Flash ANY .zip from your SD – by krut0n
* New color scheme and images (background from a random wallpaper site, if it’s yours let me know)
* Fixes from Donut
* Updated nandroid-mobile.sh w/ network support from pensive
* Updated GNU Parted (ext4 support, etc)
TMO OTA DRC83 - US
-- Rooted Base - http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO-OTA-US-DRC83-Rooted_update.zip
----- v1.9.2 Expansion Pack - (10/4/2009)http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO_1.6_ExpPack_v1.9.2.zip
CM-4.1.99+
Install instructions from SimpleHelp:http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Install instructions for an HTC Dream/ADP1/G1:
1- Perform a Backup......nandroid, etc
2- Download:http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image.This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download Cyan's ROM. Posted Below
4- Mount your phone and place BOTH 1.6 Image and my ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
8- Apply sdcard:choose zip *Pick cm-4.1.99-signed.zip* from the list.
9- Reboot!
(v4.1.999 - almost-stable-beta version, updated 10/4):
Download:http://n0rp.chemlab.org/android/experimental/update-cm-4.1.999-signed.zip
Mirror1:http://android.phaseburn.net/mirrors/cyanogen/experimental/update-cm-4.1.999-signed.zip
MD5Sum: 7f8b377c5ded60e057140119ab2a3fbd
Audio Resources (unzip to your SD card):
Download:http://n0rp.chemlab.org/android/audio-resources.zip
MD5Sum:7340ba86ddd4fba918ef97601c675ef9
HTC Touch Input:http://forum.xda-developers.com/showthread.php?t=567294
Code Repository on Github:http://github.com/cyanogen
CHANGELOG
---- v4.1.999
* BFS-303 (fixes some regressions like statusbar fling)
* Fixed BT not working (firmware)
* Updated APN list
* New wallpapers from matt_stang
* Fixed crazy compcache settings
* Fixed syntax error in userinit startup
* Fixed build.prop files
* Patch for LocationManagerService wakelock issue
* More nines
---- v4.1.99
* Now 100% open source (TMO apps are included, not sure of licensing on those yet)
* Tons and tons of bugfixes and enhancements, read the Github logs and old threads for now
* Kernel is 2.6.29.6 with BFS-302 and framework changes to support it.
* HTC Framework and apps are gone, deal with it. See the link above for HTC_IME.
THIS SHOULD HELP YOU OUT! If not,I don't know what can help you.Keep looking if you can't figure this out. But here's the help you asked for. Good luck with the flashing man!
OR - GO to the HTC Website and Look for Android 1.6!: http://developer.htc.com/adp.html#s3
Click to expand...
Click to collapse
If he messed up wit the instructions from the thread, idn if this is gonna help him, but we'll c

[KERNEL][E/GB/ICS/JB] Kernel Installer | thanks to miroslav_mm

Hi... Yesterday I decided to take zImage from boot.img of our version of Android... it is for fun because these kernel are useless (but if you want to try flashing kernels, enjoy ).
These packages will flash on your device the kernel (built in boot.img)... (if you are developer, you know how it works).
But first of all, thanks miroslav_mm for CM7/9/10 kernels and PolishVodka for his builds
SO... if you want to to try mixes of kernel and ROMs, enjoy
-kernel installer taken from Stock ROM 2.1 AOSP:
--https://docs.google.com/file/d/0B48qJUZElguJaFl2ZmhSVGJhU0U/edit?usp=sharing
-kernel installer taken from Gingerbread AOSP 2.0 version by miroslav_mm
--https://docs.google.com/file/d/0B48qJUZElguJaFl2ZmhSVGJhU0U/edit?usp=sharing
-kernel installer taken from Gingerbread CM7 SDSL 4.0 version by miroslav_mm
--https://docs.google.com/file/d/0B48qJUZElguJcmRnY2VaUkpqR1k/edit?usp=sharing
-kernel installer taken from AOKP ICS by PolishVodka
--https://docs.google.com/file/d/0B48qJUZElguJUF80QUhIQ2F5bXc/edit?usp=sharing
-kernel installer taken from CM10 Jelly Bean by PolishVodka
--https://docs.google.com/file/d/0B48qJUZElguJUmpnc0pQQ0dJclU/edit?usp=sharing
Remember:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you. Loud and hard.
*/
Click to expand...
Click to collapse
XD
Have a good day
-Domenico Verde
[EDIT] I forgot a thing... if you flash a kernel and the ROM give you a boot loop on LG logo, don't worry.. you can solve this problem with three ways:
- flash boot.img on your ROM (avaiable in zip update of your rom) with fastboot: put it in platform-tools, open command prompt, enter in fastboot mode on your phone (power button+camera button) then put on prompt this command line:
fastboot.exe flash boot boot.img
Click to expand...
Click to collapse
then your ROM is safe
other way: reflash ZIP update of your ROM if you haven't Fastboot...
other way: take boot.img of your ROM by an old backup with CWN, take boot.ing and flash it with fastboot...
If you haven't fastboot, use this tool [THE FINAL TOOL][EASY TO USE]★★★ AIO Android Toolkit 7.5 ★★★ [= May/04/2013 =] by LeoPosas and use fastboot option... install driver before using tool (driver already in the tool)

i saw a problem... every package has build prop of the romversion where i took the zimage... so the kernels works only for the same version of android, i believe

[TOOL] NEW <<--->> OLD Bootloader ROM Converter v1.0

P990 ROM Converter
from New BootLoader to Old and vice versa​
Actually this tool is Tonyp’s idea. All credits to him.
He asked me if I am interested in making a script and automating the rom porting from one bootloader to the other and he assisted me with all the changes that need to be done.
Due to different EOL (end of line) termination in text files between UNIX-Linux (LF) and windows (CRLF), I had to make bash (linux) scripts necessarily. The good thing is that the tool can be used in both windows and linux systems.​Installation:
Download and extract the attached ROM-Converter-tools.zip package anywhere you like.
Download and extract in the same folder, a newer ROM-Converter-scripts.zip if exists.
For Windows systems only:
Install Cygwin following the instructions below:
Download setup-x86.exe from here http://cygwin.com/install.html
Attention!! Even if you are running x64 windows system install the x86 version. DO NOT install the x64 cygwin version because two binaries (mkbootfs.exe & mkbootimg.exe used to pack boot.img do not work properly).
Run the setup-x86.exe, when the list of packages is shown make sure you add the following:
Expand Archive and select zip & unzip to be installed
Expand Utils and select cpio to be installed
Expand Perl and select ‘perl: Larry Wall’s Practical..’ and perl_vendor to be installed
(If you are already using cygwin run setup again and add the above packages to be installed.)
For Linux systems only:
Download the attached linux-mkboot-binaries.zip (mkbootfs, mkbootimg), extract them in tool folder and remove the windows ones (mkbootfs.exe, mkbootimg.exe).​How to use it:
Put the source ROM.zip(s) in the 'source_zips' folder (otherwise you’ll be prompted to drag n’ drop it in terminal)
Open Cygwin. Type cd (leave a space after cd) and type /cygdrive/c/dir1/dir2/../ROM-Converter-tools
where “c/dir1/dir2/../ROM-Converter-tools” is the full path of the folder you extracted the convert-tool package (e.g C:\dir1\dir2\..\ROM-Converter-tools) and press enter.
In case of long pathname, instead of typing the whole of it, use one of the following tips to easily change to tool's path.
Tip#1: After you type cd , drag n’ drop from windows explorer into cygwin terminal, the folder "ROM-Converter-tools" and it wiil automatically be converted to ‘/cygdrive/c/dir1/dir2/../ROM-Converter-tools’ press enter and that’s it.
Tip#2: After cd /cygdrive/c/ type the 1st one or two letters of the next subdir and autocomplete it's name with TAB.
Type one of these commands in cygwin terminal:
Code:
./convert_rom.sh -stepmode #--> starts in step-mode for debugging purposes
./convert_rom.sh #--> runs unattended (with no pauses).
​What it does:
The scripts use as input the 'files2convert.txt' which contains all possible files needed to be converted.
This is for compatibility purposes to support as many roms as possible and for future changes.
files2convert.txt
Code:
/ramdisk/fstab.star
/ramdisk/fstab.p990
/ramdisk/init.cm.rc
/ramdisk/init.cm-star.rc
/ramdisk/init.star.rc
/system/etc/vold.fstab
/system/bin/setup-recovery
/system/bin/check_sdcard.sh
/META-INF/com/google/android/updater-script
More files can easily be added for conversion if needed.
The converter:
Extracts source ROM zip
Unpacks the boot.img
Reads the above files, replacing partitions' mount points, among some othe things, for the selected bootloader
Replaces the kernel image for the selected bootloader
Builds new boot.img
Creates new converted ROM zip
Under 'kernels' folder there are already included the two latest Kowalski kernel images (zImage) for old & new BL and its modules.
You can add more kernels and you’ll be prompted to choose the desired one when converting a ROM (if more than one is found ).
Read how to do this:
kernels folder contains all kernel images (zImage), kernel modules and any other file the kernel needs.
for each kernel there are:
file(s) named: prefix-KernelName[-ver].zImage
folder(s) named: [prefix-]KernelName[-ver]Kernel
where:
prefix must be oldbl or newbl (depending on which bootloader this kernel is for.
KernelName[-ver] is whatever you like [and optionaly its version].
zImage is the extension of the kernel image.
How to maintain kernels folder
A. Update existing kernels
Download the desired kernel package and open it.
Replace its kernel zIamge in kernels folder
Extract its modules and any other file needed and replace all existing ones
B. Add kernels
Download the kernel package and open it.
Find the zImage inside package and extract it into kernels
Rename it this format: prefix-KernelName[-ver].zImage
Create a folder named: prefix-KernelName[-ver]. It will be used to keep kernel's modules and other files needed. If this kernel is released for both bootloaders and its modules are identicaly on both bootloaders (like the existing kowalski one) then name the folder only KernelName[-ver] (without prefix).
Inside this [prefix-]KernelName[-ver] folder create a subdir tree lib\modules
Extract in lib\modules all kernel's modules from kernel package.
If any other file is needed by kernel then create it's subdir tree (assuming that [prefix-]KernelName is the system folder of the kernel package) and extract it there.
Attention: Current version will hopefully work on CM-based ROMs.
Stock based ROMs need more files to be changed, but they are not included yet, because I don't have the whole info needed.
Hopefully @rugglez or someone else will be willing to help.
Till then avoid converting stock-based roms, (or if you do try, then after converting replace the boot.img in converted rom and "system/lib/modules/*" at least with a working boot.img and modules from another stock-based rom, for this bootloader of course. This could work but I am not the expert to say)​

ChangeLog:
Version 1.0 Aug 23, 2013
- The two convert2xxx_bl.sh scripts are now integrated into one script convert_rom.sh.
- The new convert_rom.sh also accepts an optional switch [-stepmode].
Code:
./convert_rom.sh -stepmode #--> starts in step-mode for debugging purposes
./convert_rom.sh #--> runs unattended (with no pauses).
- A technique added to preserve whitespaces in converted lines. So converted files keep margins and whitespaces of the source ones.
- Script checks whether source rom is a newbl or an oldbl one, displays an error message if rom is not for the expected bootloader and exits.
Version 0.3b Aug 23, 2013
-a typo fixed in converting scripts
Version 0.2b Aug 23, 2013
-liblgeril.so is also replaced with the one for the oldbl or newbl accordingly.
-A forced removal (switch -f) added when removing files and dirs just in case.
-Converted ROM name will be built automatically from the source name suffixed by -oldbl or -newbl accordingly. (If source rom's name contains 'newbl' or 'oldbl' it will be substituted by 'oldbl' or 'newbl' accordingly)
-Converted ROMs are now created under 'converted_roms' folder.
-Converting to oldbl: Files 'check_sdcard.sh' and 'lgdrm.img' are being removed if exist (as they are not used)
-Converting to newbl: Charger dependent images are also copied in ramdisk (not only the charger binary).
-Kernel modules will also be replaced with the ones coming with specific kernel image.
-Kowalski Kernel images & modules, in kernels folder, are replaced with latest ones dated:2013072013. (it was my fault, the previous ones were downloaded from "releases" download folder and were dated 20230303)
-Some changes in display messages.
Version 0.1b Aug 19, 2013
-1st beta version​

I really don't want to have all of the credits.
While it's been my idea to create such a script and I provided the input on what needs to be changed by the script, I couldn't have done it on my own.
I both lack the skills(!) and time.
Steve would say:
Anyways, don't leech. If this helps someone, donations are appreciated:
Donate to spyrosk
Donate to me​

spyrosk said:
To convert a new-bl rom to an old-bl rom: Type ./convert2old_bl.sh
To convert an old-bl rom to a new-bl rom: Type ./ convert2new_bl.sh
​
Click to expand...
Click to collapse
Thanks Android tool guru @spyrosk....and thanks @tonyp
just trying it out. A small comment....people might mistake this....there is no space between the / AND convert2new_bl.sh command line....should be the same with oldbl.sh command....isnt it?
thought of giving a feedback about this.
thanks once again
EDIT: battery charge script cannot be opened error....and cannot be removed error....
Creating new ROM zip ... zip warning: Permission denied
zip warning: Permission denied
something went wrong please zip contents in rom folder manually
done.

SREEPRAJAY said:
Thanks Android tool guru @spyrosk....and thanks @tonyp
just trying it out. A small comment....people might mistake this....there is no space between the / AND convert2new_bl.sh command line....should be the same with oldbl.sh command....isnt it?
thought of giving a feedback about this.
thanks once again
EDIT: battery charge script cannot be opened error....and cannot be removed error....
Creating new ROM zip ... zip warning: Permission denied
zip warning: Permission denied
something went wrong please zip contents in rom folder manually
done.
Click to expand...
Click to collapse
Hi my friend,
First of all sorry again for deleted post(s)..
and thank you.
The "typo" is corrected. Actually it was not a typo but I have noticed that it happens when pasting text from another editor.
Which ROM did you try to convert?
battery charge script cannot be opened error??? On which step did it happen?
I don't try to open any battery charge script
Did you add any file in "files2convert.txt"?

Very interesting tool.
Last july 7th I asked you if this were possibile and didn't have any reply. Now I'm happy that Tonyp convinced you.
Sent from my LG-P990 using xda app-developers app

wals46 said:
Very interesting tool.
Last july 7th I asked you if this were possibile and didn't have any reply. Now I'm happy that Tonyp convinced you.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I was on vacation sorry and when I came back I forgot to reply.
By that time I couldn't tell for sure anyway, before I have the total "picture" of the work that must be done, I mean.

@spyrosk,
my friend
Which ROM did you try to convert? Latest Avatar 3.1 Nightly OLD to NEW BL
battery charge script cannot be opened error??? On which step did it happen?I don't try to open any battery charge script It happened just the step before making the new ROM Zip
Did you add any file in "files2convert.txt"? NO
Nevertheless, I will try to flash the ROM and see what happens
EDIT:
Just now, I tried to do the PAC Man by Metallica for the Old BL and had the same error of battery charge script....
Same in Django Adios Amigo 1.6.5 to OldBL....see the script error below:
STEP 2: EXTRACTING BOOT.IMG ...
Press [enter] when ready
rm: remove write-protected regular file `out/ramdisk/charger'?
rm: cannot remove `out/ramdisk': Directory not empty
mkdir: cannot create directory `out': File exists
STEP 5: PACKING NEW BOOT.IMG ...
Press [enter] when ready
Selected kernel: kernels/oldbl-Kowalski-126.zImage
Using base address 0x10000000
Using command line ''
error: cannot open './ramdisk/charger' for read
rm: remove write-protected regular file `out/ramdisk/charger'?
rm: cannot remove `out/ramdisk': Directory not empty
Hope this helps in checking....

SREEPRAJAY said:
@spyrosk,
my friend
Which ROM did you try to convert? Latest Avatar 3.1 Nightly OLD to NEW BL
battery charge script cannot be opened error??? On which step did it happen?I don't try to open any battery charge script It happened just the step before making the new ROM Zip
Did you add any file in "files2convert.txt"? NO
Nevertheless, I will try to flash the ROM and see what happens
EDIT:
Just now, I tried to do the PAC Man by Metallica for the Old BL and had the same error of battery charge script....
Same in Django Adios Amigo 1.6.5 to OldBL....see the script error below:
STEP 2: EXTRACTING BOOT.IMG ...
Press [enter] when ready
rm: remove write-protected regular file `out/ramdisk/charger'?
rm: cannot remove `out/ramdisk': Directory not empty
mkdir: cannot create directory `out': File exists
STEP 5: PACKING NEW BOOT.IMG ...
Press [enter] when ready
Selected kernel: kernels/oldbl-Kowalski-126.zImage
Using base address 0x10000000
Using command line ''
error: cannot open './ramdisk/charger' for read
rm: remove write-protected regular file `out/ramdisk/charger'?
rm: cannot remove `out/ramdisk': Directory not empty
Hope this helps in checking....
Click to expand...
Click to collapse
I just converted Avatar-3.1 from old to new. No errors at all.
I don't like the write-protected error: rm: remove write-protected regular file `out/ramdisk/charger'
So it tries after that to remove the out directory but of course it's not empty.
Well,
Remove out directory manually and try again from the beginning..
After step 5, Before you continue to next step try to remove the whole out directory manually again.
Try also to give your account full control to the converter's folder.
This problem seems to he a windows security permission issue. Are you an administrator on the system you use?
-------------------------------------------------------------------
Stock based ROMs need more files to be changed, but they are not included yet, because I don't have the whole info needed.
Hope @rugglez or someone else will be willing to help.
Till then avoid converting stock-based roms,( or after converting replace the boot.img in converted rom with a working boot.img from another stock-based rom for the same bootloader of course. This may work)
Try ONLY CM-based roms.
I forgot to write it in OP. I'll do it asap.

spyrosk said:
I just converted Avatar-3.1 from old to new. No errors at all.
I don't like the write-protected error: rm: remove write-protected regular file `out/ramdisk/charger'
So it tries after that to remove the out directory but of course it's not empty.
Well,
Remove out directory manually and try again from the beginning..
After step 5, Before you continue to next step try to remove the whole out directory manually again.
Try also to give your account full control to the converter's folder.
This problem seems to he a windows security permission issue. Are you an administrator on the system you use?
-------------------------------------------------------------------
Stock based ROMs need more files to be changed, but they are not included yet, because I don't have the whole info needed.
Hope @rugglez or someone else will be willing to help.
Till then avoid converting stock-based roms,( or after converting replace the boot.img in converted rom with a working boot.img from another stock-based rom for the same bootloader of course. This may work)
Try ONLY CM-based roms.
I forgot to write it in OP. I'll do it asap.
Click to expand...
Click to collapse
I have a list of files/folders which I was using to port...Thanks to @rugglez ofcourse...
If you have seen the dev section....I was porting a few ROMs from Old to New BL including the stock ROMs.
So, I will send you the list by PM.
I will try the CM based ones with manual clearing...and will check that
EDIT: I am the administrator...so normally only one account and I have that rights too
thanks once again

Okay, I just used the converter on Win8 x64 to create an oldbl version of my CM10.2 ROM.
I have uploaded the resulting zip here: http://tonyp.basketbuild.com/index.php?dir=main/CM-10.2/oldbl-untested-builds/
It is untested - so do a backup!
I will post the steps I took, this might help some people who never worked with tools like this.
Please try it out with different ROMs - and if the resulting zips work a) post that here and b) share the zip in the respective threads for others to use
If you have any erros post the complete cygwin output here.
To get it do a right-click into the cygwin window, then press Enter - it's now copied into the clipboard!
Okay, off we go:
Preparation (one time only):
Downloaded cygwin. and install it
The path C:/cygwin is perfecly fine.
Just press Next until you get to the paket selection, then use the searchbox to quickly get to the tools needed:
(just click once on it, the first checkbox will get checked. The second one is for the sourcecode, you don't need that).
- zip (Archive)
- unzip (Archive)
- cpio (Utils)
- perl: Larry Wall’s Practical (perl) (you might have to open "perl" and look for it manually)
- perl_vendor (perl)
Downlaod the zip attached at the OP, extract it.
I extracted it to C:/temp/ROM-Converter-tools/
done
ROM conversion:
Open the Cygwin Terminal (either in the start menu or execute the Cygwin.bat at C:/cygwin/)
Put the ROM zip into the source_zips folder
Type:
Code:
cd /cygdrive/c/temp/ROM-Converter-tools
Needs to get adapted to your path if you extracted the ROM-Converter-tools somewhere else.
My path is: C:/temp/ROM-Converter-tools/
(Hint: after /cygdrive/c/ autocompletion with TAB will work!)
I didn't try the drag&drop tip of spyrosk.
Type:
Code:
./convert2old_bl.sh
(or convert2new_bl of course if you're going the other direction)
Follow the instructions on the screen,
As it's still in the debug mode you need to press [enter] a couple times.
This will change in the future.
Done, your converted ROM will be in the out_oldbl or out_newbl folder.

do this tool work with CM7

tonyp said:
Okay, I just used the converter on Win8 x64 to create an oldbl version of my CM10.2 ROM.
I have uploaded the resulting zip here: http://tonyp.basketbuild.com/index.php?dir=main/CM-10.2/oldbl-untested-builds/
It is untested - so do a backup!
[/LIST]
Click to expand...
Click to collapse
uhm ... in my case it got stuck at CM booting logo ... is flashing it recovery sensitive?

spyrosk said:
"...I just converted Avatar-3.1 from old to new. No errors at all.
I don't like the write-protected error: rm: remove write-protected regular file `out/ramdisk/charger'
So it tries after that to remove the out directory but of course it's not empty.
Well,
Remove out directory manually and try again from the beginning..
After step 5, Before you continue to next step try to remove the whole out directory manually again..."
Click to expand...
Click to collapse
Hummmmm, I tried experimenting, and it happened to me the same as the partner "SREEPRAJAY"! ...
Here are the errors I had during the experiments (three files *. pdf);

Hrmph.
Was running the latest CM 10.1 nightly. Rooted, old bootloader, CWM Recovery 6.0.3.1.
Made a Nandroid backup. Wiped everything from recovery, factory reset, flashed this :
http://tonyp.basketbuild.com/download.php?file=main/CM-10.2/cm-10.2-20130821-UNOFFICIAL-p990.zip
According to CWM all flashed and well. I rebooted.
Phone's bricked, won't even boot to recovery, gets stuck in the LG logo. Ouch. Halp ?

Ultramanoid said:
Hrmph.
Was running the latest CM 10.1 nightly. Rooted, old bootloader, CWM Recovery 6.0.3.1...flashed this :
http://tonyp.basketbuild.com/download.php?file=main/CM-10.2/cm-10.2-20130821-UNOFFICIAL-p990.zip
Click to expand...
Click to collapse
But...that ROM is for NEW BootLoader!!!...
Use All-In-One Toolkit to reattach the situation (reinstall again CWM Recovery);
http://forum.xda-developers.com/showpost.php?p=34809475&postcount=1

trocopassu said:
But...that ROM is for NEW BootLoader!!!...
Use All-In-One Toolkit to reattach the situation (reinstall again CWM Recovery);
http://forum.xda-developers.com/showpost.php?p=34809475&postcount=1
Click to expand...
Click to collapse
I know ! ( NEVER flash anything as soon as you wake up without checking twice, kids. )
I saw the one for old bootloader for the 20th, moved up a directory, happily flashed the one for the 21th... and for the NEW bootloader.
Don't have access to a laptop to tinker and won't for a few days. Sigh.

millionsun93 said:
do this tool work with CM7
Click to expand...
Click to collapse
No, and it never will.
GB relies on the old bootloader. It would be a lot of work to make it compatible, which isn't worth the trouble at all.
flat__line said:
uhm ... in my case it got stuck at CM booting logo ... is flashing it recovery sensitive?
Click to expand...
Click to collapse
Ah that's a shame. spyrosk needs to have a look at that when he gets some free time.
You did a full wipe didn't you?
If you did it sound like an error in the fstab.
Ultramanoid said:
I know ! ( NEVER flash anything as soon as you wake up without checking twice, kids. )
I saw the one for old bootloader for the 20th, moved up a directory, happily flashed the one for the 21th... and for the NEW bootloader.
Don't have access to a laptop to tinker and won't for a few days. Sigh.
Click to expand...
Click to collapse
Your partitions are borked and you will have to use nvflash.
I'm sorry about that although I don't really know how you came to the idea to try the untested oldbl builds when you got no PC around to recover.
This could have even happened with the correct rom - again, it is completely untested.
Sent from my LG-P990 using Tapatalk 4

tonyp said:
Ah that's a shame. spyrosk needs to have a look at that when he gets some free time.
You did a full wipe didn't you?
If you did it sound like an error in the fstab.
Click to expand...
Click to collapse
I did the full wipe (I checked: I used the ext4 full wipe zip by dr4go for the old bootloader, as I usually do, using CWM 5.0.2.8)

[ROM][UPDATED] Asus ZenFone 4 stock WW 6.5.27 deodexed rom [20141009]

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction/About
This is just stock ww 6.5.27 deodexed rom, packed as ext4 system.img meant to be flash via fastboot, nothing fancy here.
Click to expand...
Click to collapse
Features:
Based on stock ww 6.5.27.
Deodexed.
Zipaligned.
Init.d sysinit.
Zipalign and sqlite init.d script added.
Dalvik optimization in build.prop.
Busybox 1.22.0 applet installed in /system/xbin.
Adblocking hosts file.
Xposed framework fix. Can install/update xposed without bootloop/stuck on booting.
Accessing sdcard fix for thirdparty apps. Can read/write/modify data on sdcard.
Updated asus standalone app from playstore ie camera, calendar, messaging etc.
Debloated by removing app that can be install from playstore eg gmail, youtube, google plus, google music, google book, google magazine, google game, google hangouts, omlet chat etc. If u want them u can just install from playstore.
Probably other things i forgot to list here...
Click to expand...
Click to collapse
What Works:
Everything in stock rom should work.
Click to expand...
Click to collapse
Bugs:
Fc after first boot, just turn off/reboot again and everything should be fine.
Click to expand...
Click to collapse
Installation Instructions:
U need to already have updated to 6.5.27 stock rom either full flash or update ota.
Because zenfone 4 got no custom recovery yet so this is meant to be flash from pc/laptop so u need to have pc/laptop.
Backup your data eg contact, sms, calendar, photos etc.
U need to install Intel android driver.
U need to have adb and fastboot tool, can download from my link below. Just extract the archive, ADB_FASTBOOT.7z somehere in root of drive eg in C or D.
Extract the rom, u will get system.img around 1gb in size. Put it in the same folder as adb and fastboot above.
Boot phone into droidboot mode by pressing volume up+power button together.
Connect phone via usb cable.
Open the adb and fastboot tool folder and double click on OPEN.CMD. Windows terminal will open.
Type in the terminal to erase cache
Code:
fastboot erase cache
and press enter.
Type in the terminal to erase data
Code:
fastboot erase data
and press enter.
Type in the terminal to erase system
Code:
fastboot erase system
and press enter.
Now to flash system, type in the terminal
Code:
fastboot flash system system.img
and press enter. Flashing system would take around 10minutes.
After success flash system, if u want root need to flash supersu. Download and put ASUS_ZENFONE_ROOT.zip in the adb and fastboot folder and type in terminal
Code:
fastboot flash update ASUS_ZENFONE_ROOT.zip
and press enter. Phone will reboot automatically and will flash the root zip, then it will reboot again into system. First boot would take longer to generate dalvik etc.
Click to expand...
Click to collapse
Download:
Click to expand...
Click to collapse
Thanks To/Credits:
God
Linus Torvalds and whole linux kernel team and contributors.
Google
Asus.
shakalaca
and many, many other people whose their tool/app/guide i've used to make this...
Click to expand...
Click to collapse

Thank you for this rom but i have hard bricked my phone flashing this rom would get to normal :crying:

what did u do anyway?
if u follow the instruction it should boot, and even its not booting then can always reflash to stock rom. this rom will only modify system partition.
boot, recovery, fastboot and all other partition wont be touched and can always recover back to stock rom.

great job sir... I will try

syaeful said:
great job sir... I will try
Click to expand...
Click to collapse
Edit :
Succes Deodexed.. Thank you very much sir

Is anyone know to swap the storage of this phone ???
Sent from my ASUS_T00I using XDA Premium 4 mobile app

anyone wanna root the newly released kk update can root using the root zip in first post

Hoping for a kitkat custom ROM soon! :victory:

updated to ww 6.5.27.

mdfzhi said:
updated to ww 6.5.27.
Click to expand...
Click to collapse
Can I use the root package in the 1st post with this update?

ong14 said:
Can I use the root package in the 1st post with this update?
Click to expand...
Click to collapse
yes.

mdfzhi said:
yes.
Click to expand...
Click to collapse
Thank you.
I'll get my zf4 tomorrow.
Can't wait to try your mod.

This was great..been for a while finding exploit for rooting this phone on kitkat..your deodexed one was great..nice job...hope this phone community will grow big...
Cheers.
Bro..where's link..I'm sutfing on xda app..
Nvm..opnened in browser..
Just downloaded root things..tomorrow will try this deodex..
Greet from Malaysia

actually i'm not really into roms, more into kernels. thats why the rom is just deodex and few changes only, no new added features. hated smali editing.
been waiting far too long for asus to unlock zenfone 4 bootloader so that i could compile kernel myself.

mdfzhi said:
actually i'm not really into roms, more into kernels. thats why the rom is just deodex and few changes only, no new added features. hated smali editing.
been waiting far too long for asus to unlock zenfone 4 bootloader so that i could compile kernel myself.
Click to expand...
Click to collapse
Thank you for your contributing in zf4.
I have one question;
How can I revert back to stock firmware?
Can I flash a full stock f/w directly via droid boot menu [sd download]?

Not sure about sd download option in droidboot, never use it before but what i always did to get to full stock is by downloading full rom zip from asus server, extract it to get another zip, copy it into internal memory via usb cable and when removing usb cable will get notification to update.

mdfzhi said:
Not sure about sd download option in droidboot, never use it before but what i always did to get to full stock is by downloading full rom zip from asus server, extract it to get another zip, copy it into internal memory via usb cable and when removing usb cable will get notification to update.
Click to expand...
Click to collapse
Thank you for quick reply.
I'll try your mod tomorrow. (My zf4 have 2 batteries of 1200mAh, and still charging one of them.)

Owh...yeah..nany news on asus for unlocking bootloader.
?

Thanks a lot .. U saved me from a soft brick ...

No news yet about the bootloader, no reply from Asus

[HowTo] Root,TWRP, patched aboot LG L-FINO Dual [D295tested]

As lack of thread of our device developements,hope i can help some ppl out there with same device.
WARNING..its only teseted on DualSim variants A.K.A D295 firmware V10c, and am not responsible to any damages & now your warranty is void.
Needed Tools:
1. LG latest driver (google it)
2. PurpleDrake find on xda
3. Patched aboot (bootloader)here http://www.mediafire.com/download/9q9rd75zla94lr5/abootD295Patched.zip
4. Terminal emulator (playstore)
5. TWRP here
https://mega.co.nz/#!VkVFRYpb!JdhwyP_1uOOyKBxxXgFBLWPSzCgJFdN3P7OHmbtVbxU
Or https://mega.nz/#!BkdWQRQa!JdhwyP_1uOOyKBxxXgFBLWPSzCgJFdN3P7OHmbtVbxU
# BRAIN&SHARP EYES
Before you start backup your important data.
Install LG driver on pc, make sure that whole driver installed properly. ROOT your device; enabling your usb debug,connect to your pc, extract PurpleDrake zip files you can run that batch.exe,follow its instruction, congrats you're rooted now.
Installing TWRP
Put the patched aboot.bin & TWRP img, those files was ziped, extract them and put that aboot.bin&recovery.img on your external_SD.
Go to terminal emulator and type this command correctly
TWRP INSTALL: dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17 bs=2048
Congrats you've TWRP installed. Now to enabling you boot into recovery you've to patched the aboot.bin follow this step
first backup stock aboot with
dd if=/dev/block/mmcblk0p6 of=/storage/external_SD/abootstock.bin
and flash patched aboot* dd if=/storage/external_SD/aboot.bin of=/dev/block/mmcblk0p6*
Now you're able to boot into recovery.
Note: this recovery only accessible via terminal commands &Adb as the buttons combination only work for formating system.
CREDITS&Thanks
4pda member whose make aboot pathced
original link*http://4pda.ru/forum/index.php?showtopic=436618&view=findpost&p=36339432 @GHsR who made the TWRP
Gith TWRP Device Tree for LG L FINO (D295) -*https://github.com/ghsr/twrp_device_lge_l70pds
The PurpleDrake Creators
Myself

[TWRP]STOCK ROM pre-rooted Deodexed
This rom based on stock V10c, debloated some lg apps removed, fixed sdcard access 3rd party apps, deodexed (/app&/priv-app).
Lg keyboard replaced by Xperiakeyboard,
Edited framework-res and resizing its Navbar sizes, changed DPI to 200dpi. As it deodexed more space you got on internal memory.
DOWNLOAD
Initial build
https://mega.co.nz/#!0sc3mAgQ!986jLGVqZm70VYZGb-ojYVzkV_13fFT_cGitaqnZy-c
Ver.1.0
https://mega.co.nz/#!Fhd3TIDT!cBtefFZtE5cVhAT5AzODDwj4M5tghMOHwS7iOlzILeg
ver.1.1 [soon] updated to V10D
Changelog:
1.0 Reverted to Stock DPI
Debloated more apps (500mb)
Deodexed, zipaligned
Adding Snapdragon Audio(use it with playmusic app)
3rd apps write access to external_SD
More..
Don't forget hit thanks
Bugs: ART break (switch to ART caused bootloop)

[STOK FIRMWARE V10C] KDZ LG-D295 with LG Flash tool
Instruction
Unplug usb , power off, hold the vol+ while it off and connect the usb cable to put your phone in download mode.
Extract and run the program... Let the box type set as its default,
Phone mode: DIAG
Reset time: just let its default numbers.
and choose the firmware D29510C_00.KDZ
Hit normal flash without losing your data, and cse to format whole things.
DOWNLOAD
https://docs.google.com/file/d/0B1Vsltuww3UFZy11aEJmNnFJeTg/edit?usp=docslist_api

Will TWRP work on D290?

Not sure,but to keep you save..download flashify to back up your stock recovery, or use this command
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/storage/external_SD/recovery.img bs=2048
Move it inside folder, keep it
And continue to flash the recovery.img
Just search that aboot.bin patched too

So seems there's none used this device huh, anyone just put some post and share your thought here

Thanks for your feedback man! Today some guy released working TWRP for D290n :3

Good news...let ask mod to makes our own forum

It would be awesome

Custom Frameworks-res
For those want ART working, don't use deodexed.zip above, and some who want custom navbar size(changed to 27.dip) resized statusbar.
Use this one custom framework-res
https://mega.co.nz/#!Rs8ylawT!lW587n08JXiSDlYI0Qni3J489lFVIAb0g_nrXyALQeE
Howto;
Extractthe zip files (DO NOT FLASH).. Boot into recovery, mount system, in advanced use file manager before you dellete the original framework-res.apk (copy the original, put it on sdcard).
Replace with the extracted framework-res.apk and chmod 644..
Reboot

See the navbar&statusbar edited

[Bounties] First CM/AOSP Developements
Asam so much interested to have aosp run on this devices, i offered every devs can help and join the developements.
Detail of rewards:
A. Compiled from sources
1. 1st booted [RIL must work] cm/aosp will got $20 bucks and this amount will only transfered via paypal.
2. updated [mote fix and stable use] $15
3. And donations will keep.in going as the dev continuing and updating its builds.
B. PORTING
1. Usable state. RiL, phonecall $15
Updated fix&stable $10
Will will keep continuing
And also there's so much L Fino user out there and join this donations.
Contact me to confirm that youre start the project @hangouts [email protected]
Some proof and im really serious
http://forum.xda-developers.com/showthread.php?t=2952388
For test,ask devices details etc.

[pure stock] TWRP flash
I just repacked from its default KDZ...nothing changed, when you flash this one you may need to re-flash superSU for root access.
DOWNLOAD
https://mega.co.nz/#!o0UgBSTL!OIx_YS87twsqZjjEFu2E2XFIa1J22qHqQUWT2l66iAs

Carliq....thanks , anyway...spread the lg users let the mod see, and we should have our own thread

Hey bro, I'll try this on a D295F from Brazil, V10a ...
You think it will work?
:good:

To make it work..the key was aboot.bin , try search on the link above 4pda your patched aboot.bin when you can't found one, you can try d295 aboot.bin , do back up..

SH1M4BD3 said:
Carliq....thanks , anyway...spread the lg users let the mod see, and we should have our own thread
Click to expand...
Click to collapse
I have traduced it to Spanish in HTCMania. i hope some people Will see it and the Will start cooking thanks

Thats good idea...hope some devs can join&help us

:good::good::good:
Working very well without any problems, thank you :good::good:
Can I share this tuto in my page on G+ ??

Spread the world....translate to your local language, but please make it linked here, so when this thread crowd there's posiblity we own our forum