Related
Hi there, as many of you may know dzo or simple god makes a flashable version of android for our KAISERs.
But vefore here are some rules:
THIS THREAD IS MADE TO KEEP THE FLASHING ANDROID ON KAISER DEV THREAD CLEAN FROM USERQUESTIONS!!!
DON'T ASK USER QUESTIONS IN THE DEV THREAD!!!
This Thread is for experienced Kaiser users who aren't in development but wan't to see android running native from NAND.
THIS IS AT THE CURRENT STATE VERY VERY VERY BETA, THERE MAY BE A HIGH RISC TO BRICK YOUR DEVICE. THIS WILL COMPLETLY WIPE WINDOWS MOBILE. JUST USE IT IF YOU CAN ANSWER YOURSELF THE FOLLOWING QUESTIONS: (without search function)
-What is an .nbh file
-how to flash a kaiser
-What is HardSPL /Security unlock
-How to recover a bad rom flash?
-What to do if your device won't start anymore?
-Do you have basic android skills?
Ok Guys, little cleanup and updates:
INDEX:
-Post one:
Different flashing methods
Things to take care off
-Post two:
How to creat your own nbh files
How to make custom splash screens
-Post three:
Working Systems/rootfs
Bugs
Usefull Links
Thanks
HOW TO START ANDROID FROM NAND
Method one:
1-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
2-Download http://www.mediafire.com/?zldjhfnkzk2
3-Copy the androidinstall.tar from the androidinstall.zip file to the root of your sdcard
4-delete/rename any old android files on your sdcard
5-Unzip the androidinstall.zip and replace the ruu_signed.nbh in it with the one you downloaded in the first link. (must be named ruu_signed.nbh)
-6Run the custom ruu.exe - thats all after reboot you'll have a flashed Cupcake android.
Method two:
1-delete/rename any old android files on your sdcard
2-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
3-Create three empty files on your sdcard wihout any extension:
-datafstonand
-systemfstonand
-rootfstonand
4-Copy your prefered rootfs.img, system(img,ext2,sqsh) and an empty data.img to sdcard root
5-Copy the nbh file you downloaded to the root of your sdcard and rename to kaisimg.nbh
6-Reboot your device using restart button and cam button, then when it tells you, press power key to flash the new nbh.
-Reboot by pulling the battery - Thats it ( First start may take a while and may reboot randomly, just give it some time)
Different Tricks and hints (collected in the forums):
-Change Panel Type:
Run: "echo 1 > /sys/module/board_htckaiser/parameters/panel_type" through adb or init
-Experimental GPS:
For working, gps you need to replace libgps.so with the one from the vogue gps thread.
Experimental openGL Drivers ( Eclair Only)
-Download this one and flash your prefered nbh: http://rapidshare.com/files/345432577/kasiandroid_nbh_with_opengl.zip
-Install the included script sheduler, and replace the afterboot.txt with the one included in the zip file
This will install an app that will run the afterboot.txt after every boot and fix file permissions.
-Or you can open the afterboot.txt and run it in terminal after every boot.
To see if it works install the included gallery3d.apk, iff you see thumbnails, it worked
Not tested by me, yet through no time.. (Thanks to quitlahok and rzk333 for this manual)
THIS IS JUST FOR THOOSE WHO ARE MORE IN DEVELOPMENT AND LINUX
HOW TO CREATE YOUR OWN NBH FILES:
1- Set up your prefered Linux Setup, i use Debian.
2-Build kaiser kernel with wiki manual
3-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/tinboot
4-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv
5-cd bootenv
6-cp buildInitrd buildInitrd-mini
7-nano (or whatever your favorite editor is) buildInitrd-mini
8-change all instances (2 of them) of initrd to initrd-mini
9-sh buildInitrd-mini
10-cd tinboot
11-nano tinboot.S
12-the paths to fix are at the bottom of the file, it's pretty self-explanatory. higher up in the file you'll see the kernel cmdline under an .ifdef kaiser line
13-after that you'll need to download and extract any windows kitchen, and install wine however your linux distro requires and make a note of the path you extract nbhmerge.exe to as you'll need it in your tinboot.S file, along with the path to your kernel zImage and initrd-mini.gz
after that if you've got everything else in place, go ahead and run the compilekaiser script in the tinboot dir and you should have an nbh
if the nbh won't flash (i had this issue) copy the output.nb file, boot into windows, and use nbhutil.exe to convert it to an nbh and flash that one. for some reason yang doesn't work right for me personally
HOW TO CREATE CUSTOM SPLASH SCREENS: (this is a manual by POV)
1. Install HardSPL.
2. Create a BMP file in paint, size must be 240x320, save it as BMP 24bit.
3. Download SplashTool
4. Load your BMP on nb_image_converter (included in SplashTool's zip) and save it as splash.nb
5. Open SplashTool.exe and convert splash.nb to new format.
6. Pack the resulting splash.nb into a NBH file using htc rom tool.
7. Flash your cusotm NBH using CustomRUU.
This will not harm your installed android
WORKING SYSTEMS / ROOTFS'S: ( Collected in the forums)
- http://forum.xda-developers.com/showthread.php?t=587116 ION Donut, reuploaded by 160bpm
- http://forum.xda-developers.com/showthread.php?t=619980 MYNs warm Donut
- http://forum.xda-developers.com/showthread.php?t=619718 Jamezelles Sense Tattoo
- http://forum.xda-developers.com/showthread.php?t=591104 Plemens Donut AOSP
- http://forum.xda-developers.com/showthread.php?t=603028 Jamezelles Sense Hero
- http://forum.xda-developers.com/showthread.php?t=619285 Shidells Android 2.1
rootfs 2010-01-06 works best for me get it here: http://sourceforge.net/projects/androidhtc/files/
Bugs:
NOT WORKING: WiFi, GPS, Voice Call, Bluetooth
(GPS experimental with the files from first post)
Usefull Links:
Android on Sourceforge:
http://sourceforge.net/projects/androidhtc/files/
Android on htc Website:
http://www.androidonhtc.com
dzo's page:
http://it029000.massey.ac.nz/vogue/
Android SDK:
http://developer.android.com/sdk/
Tinboot dev thread:
http://forum.xda-developers.com/showthread.php?t=614275
Thanks:
dzo, plemen, jamezelle, zenulator, enatefox, mssmision, vilord, rzk333, diagdave
SORRY IF I'LL FORGET ANYONE
Here's a couple boot screens I made.
Thanks i'll add this to the first post
Thanks JeckyllHavok, good idea I keep posting over here am not into kernel things anyway
Ok after a few attempts I finally got Android flashed, and running, using my backup kaiser, which has no network connection, so the lack of wifi is a bit of a problem, but seems to be working fine so far, and fast
Just wondering if it would be possible to flash other versions, like eclair or even flan, since polyrhythmic's eclair version seems to be nice and stable, or is this going to fast to soon?
Just tested this with sshidels nexus rom, but itjust ends in bootscreen loops. Maybe other roms work
Looks like in need to learn to read. I found these instructions in the Vouge forum:
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
Click to expand...
Click to collapse
Buried for stupidity. Works great so far.
Flashing now.
1st edit: We have Android .
2nd edit:26 min it just turned itself off ... creepy ... soft reset ....I'll post back results.
3rd:39 min later Actual Phone screen came up No SIM ..Opps rebooted waiting agian.
What is working/not working with this flash.
From what I've read everything except.
Blutooth
wifi
GPS
Still waiting back at ANDROID screen
I have successfully flashed THIS BUILD using the following method:
dzo said:
...create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Click to expand...
Click to collapse
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
loserskater said:
I have successfully flashed THIS BUILD using the following method:
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
Click to expand...
Click to collapse
Hi
Can you please send me the files on the sdcard. I am having an issue with every build.
Thanks
Did wifi work with any builds?
I think no, not now
Tilt
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Jaguarius said:
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Click to expand...
Click to collapse
Are the keys on the slide keyboard working correctly
OK now got two nand flashed kasiers, (both kais130), first using the 'original' flash method, ( dzo nbh, androidinstall.tar), and the other method from the vogue threads, with polyrhythmics Eclair build, which is much slower, ( uses SD card rather than Nand?).
Both seem to be working as well as can be expected at this early stage of Nand flashing.
What I would like to know is how to 'upgrade' our zImage, since some builds have a different zImage version than the one we are currently flashing with, ( I am assuming our zImage is in the NBH flash), since this may help enable wifi/gps which we are presently lacking.
see the following article.. can someone post a copy of their build.prop b4 firmware upgrade or confirm that it is rooting the phone that blocks you seeing protected apps.
http://androidforums.com/samsung-ga...ected-app-market-fix-tutorial-build-prop.html
suddenly sling mobile and other protected apps i paid for no longer appear in the market place..
thanks
ok everyone here is a fix for the problem.. i downloaded the original dump of xxjf3 that was posted and modifed the build.prop of my jf7 and here is the file..
here is a link with instructions (note you will have to checkin after installing and reboot)
i didnt use adb i prefer root explorer
in some terminal emulator sufs i copied the original in case i need and also ftpd off the system
ie
su
cd /system
cp build.prop build.prop.orig
then go in root explorer and copy the new one over the one in /system
then reboot
then checkin (the new build.prop: *#*#2432546#*#*)
then reboot again
(make sure you unzip the file first)
i can now see slingplayer again in search in marketplace..
probably would not use same modified build.propr with diff. f/w than jf7 but same approach works
note: if you are going to do this yourself make sure you strip the dos cr off before uploading i use a program called stripcr attached here.. (assuming you are editing on a pc)
here is the original post where i got the idea from
http://forum.xda-developers.com/showthread.php?t=687371
THIS IS FOR TESTING ONLY. DO NOT ATTEMPT TO INSTALL THIS IF YOU DON'T KNOW HOW TO GET INTO BOOTLOADER MODE AND FLASH A ROM FROM THE SD CARD.
Announcements
We are currently replacing Tinboot with LK for boot. This will give us fastboot and many other enhancements and fixes to make our device more like a native Android device. This has already fixed some issues with GSM phones, sleep modes, and a few other things. The current issue being worked on is the power button not working (possible GPIO issue).
Introduction
This thread tracks the most recent NAND development. A huge thanks to [ACL] and WoZZeR999 for dedicating time to NAND development for us, and again, thanks to Jonpry, PHH, stinebd, and the rest of #htc-linux for their contributions. It's truly amazing what these guys have done for us, so be sure to show them your appreciation :wink:
The original NAND boot testing thread can be found here:
http://forum.ppcgeeks.com/tp2-andro...und-test-7-single-nbh-serialno-tilt2-fix.html
File Repository
Autobuild files can be found here: Index of /files/
The LK directory will contain the latest LK Bootloader and boot image code.
The rhodium_nand directory contains the latest kernels
The XDAndroid directory contains the latest OS files and updates (including the root update)
Note: We often disable autobuild when extremely experimental code is submitted, so this may not always be up to date but should be more stable than content we post in the threads.
Latest Files
LK Bootloader: http://htcdevs.wirelesstcp.net/files/LK/RHODIMG_NORECOVERY.NBH
Recovery Image: http://htcdevs.wirelesstcp.net/files/LK/recovery.img
05-22 Kernel: http://htcdevs.wirelesstcp.net/files/rhodium_nand/20110522_175721-kernel-update.zip
FRX06 OS Files: http://htcdevs.wirelesstcp.net/files/xdandroid/FRX6/update.zip
Optional - FRX06 Root: http://htcdevs.wirelesstcp.net/files/xdandroid/opt_updates/Root-Update.zip
Installation Procedure
Obtain Install Files
You need 4 files to get NAND up and running:
LK Bootloader NBH
Recovery.img
Kernel
OS Files
Install Directions
1) Set up your computer to use fastboot: http://forum.xda-developers.com/showthread.php?t=532719
2) Flash your phone with the LK Bootloader NBH
3) Copy recovery.img to your fastboot/adb folder
4) Open bash/command prompt and run fastboot flash recovery recovery.img
5) If successful, type fastboot reboot, and hold the Power Button as your phone boots
6) Your phone should boot into recovery, and there you can apply the various update.zip files in this order:
- FRX06 Update.zip
- Kernel-Update.zip
- Root-Update.zip
To navigate in recovery, use volume up/down (or up/down on keyboard) to change selection, then use End Call key (or Enter on keyboard) to make a selection.
Here's a video from ACL
http://www.youtube.com/watch?v=4r4o2CCKwvU
Work in Progress
Panel init/power down
No data on first boot
Youtube app has issues
GSM can boot with no rild arguments (no data)
Not Working at all
Camera
No bluetooth
No 3.5mm headphone jack
Frequently Asked Questions
What is NAND booting?
NAND booting uses code on the NAND to boot directly into Android without having Windows Mobile on the device. Currently, zImage and initrd.gz are stored on the internal NAND while the modules, rootfs, ext2, and data are stored on the SD card.
How do I setup NAND boot?
First, you need to download the Update Utility (CustomRUU) and the latest package. Extract the NBH to the same folder as the Update Utility and flash like you would a custom ROM. Put the included modules on the SD card (modules must be from the same package as the NBH) along with the modified rootfs.img (see first post) and system.ext2 from http://xdandroid.com/wiki/Main_Page (you can use system.ext2 from BLAZN, but XDAndroid will be better for testing)
Why don't my changes to Startup.txt work/How do I change boot options?
Because we are booting without Haret, Startup.txt is not used. Any changes to Startup.txt will have no effect. If there is a boot option you need enabled, you can either compile a new tinboot with those changes or let me know and I can compile one for you.
Where are the Android files stored and how do I update them?
Modules, rootfs.img, and system.ext2 must be stored under /andboot on the SD card. Every update will require flashing a new NBH (contains zImage) and replace the old modules file with the new one. Sometimes deleting the data.img file is necessary between builds if you experience major problems.
Wifi or other devices aren't working after an update...
The modules and zImage are a pair and must always be updated together. If you only flash the NBH but don't replace the modules file on the SD card, you will get a mismatch on the modules preventing the drivers from loading.
My battery drained and now my phone is stuck in a boot cycle! AHHHHHH!
Don't worry about it. You have two quick and easy options. First, unplug the USB cable, then remove the battery, then put the battery back in, and plug the USB cable back in. Now let it charge for 5 minutes, then turn it on, and you should be good to go. If it still does not work, unplug the USB cable, then remove the battery, then put the battery back in, attempt to enter bootloader mode and plug the USB cable back in as soon as the bootloader screen comes up. Now you can charge it for 5 minutes and restart back into Android (where you should continue charging).
Project Status
What is currently being worked on?
Battery life (up to about 9 hours now)
Backlight control (Dimming works and backlight can be turned off, but re-initializing is causing issues)
What is working?
Phone
Data
Sound
GPS
Keyboard
Wifi
Hardware 3d
What is NOT working?
Camera
Bluetooth
3.5mm headphone jack
Heh, only a matter of time before this thread made it over onto XDA. Thanks Nate
testing
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working
ksper6986 said:
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working
Click to expand...
Click to collapse
Thanks for the heads up. The copy/paste from PPCG killed some of the links. They should be working now
And this does work great. You can find the thread over at PPCGeeks here: http://forum.ppcgeeks.com/tp2-andro...esting-12-11-panel-power-off-now-working.html
First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?
yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot
Bieka said:
First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?
Click to expand...
Click to collapse
Task29 is just recommended to make sure everything is nice and clean. It makes troubleshooting much easier because it ensures nothing weird is being read from the internal nand.
You can easily flash back to WinMo by starting the phone in bootloader mode and flashing. Unfortunately, you will not be able to do the ActiveSync connection through USB and flash that way.
kabu said:
yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot
Click to expand...
Click to collapse
You should have three files in /sdcard/andboot: rootfs.img, system.ext2, and modules (don't rename the modules). Now flash the NBH and it should generate the data.img, and you should be good to go. It should be loaded in under 10 minutes, so if it isn't, I would check the contents of the memory card. Also note the card must be FAT32 formatted and have not be partitioned.
The panel power on/down is apparently fixed for some panels but not others. ACL and bzo have been working together on this and found that there are several different panels being used in our phones, and ACL is working on a patch to fix up the panels that aren't functioning perfectly.
mcnutty said:
RootFS
A custom rootfs.img is required to automatically configure the keyboard. You can override the automatic keyboard by creating a .kb file in your andboot folder. Accepted inputs are: rhod500.kb, rhod400.kb, rhod210.kb, and tilt2.kb
Click to expand...
Click to collapse
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .
Bieka said:
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .
Click to expand...
Click to collapse
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go
Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.
Thordim said:
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go
Click to expand...
Click to collapse
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))
Bieka said:
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))
Click to expand...
Click to collapse
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.
wifi
i want to start off by saying this is an amazing project.
But my problem is that wifi is not working for me. When i try to start wifi, it immediately says "error." I have done many flashes and used task29. i was just wondering if anyone else had this issue.
mcnutty said:
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.
Click to expand...
Click to collapse
I will do that for you in the next days. Before Christmas it's a turbulent time for me. As soon as i can get the Time for it i will flash to nand and follow your instructions. If i need help, can i PM you?
Cheers
I'm using Neopeek's rom instead..how can i set it up? since this rom doesnt use the system.ext2 file
getting calibration without visible points to touch aka the boxes. also, boot ani glitches out on screen with a "solid" animation, and video glitchs on the bottom half of the screen. sits here indefinately.... still waiting..... haha
update: loads to lockscreen, so far can't get screen to stay on??? strange
update2: got it working, but keeps turning screen off immediately... any ideas>?
hmm, i have been trying this and i feel like i have everything right
tilt2.kb, rootfs.img, modules, and system.ext in an andboot folder in my storage card and then, a nbh with the same name as the module in a folder with customRUU.exe. I flash and then it gets to the linux boot screen, after a couple lines go by, the screen fades out and dies and restarts. My battery says 88 percent when i flash back to windows, anybody know what could be going wrong?
HTC Sense
will it only recognize only an ext2 or will it recognize squashfs.
blitzer320 said:
Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.
Click to expand...
Click to collapse
I'm on the rhod210 (T-Mobile), and I've been having this exact issue. Any ideas?
btw, this is my first post here, but I've been reading and following this project for quite a long time. You guys are great! Thanks for all the work you do!
On my rooted Defy - how do I install a zip-file??
Like this one;
http://forum.xda-developers.com/showpost.php?p=12426274&postcount=24
install the 2ndinit apk 1.4.2 newer ones wont work with some files
then reboot 2 times.
third reboot: press volume down, when the led is blue.
now choose recovery by pressin vol up or down and power to accept.
then choose costum recovery, and apply zip from sd. choose your file and confirm.
done
hope this answers your question
Thanks, seems simple enough
uh, where do I find 2ndinit.apk
You can find it here.
I know how to install .zip but I have a question. CWM3.1 does not flash some .zip like a baseband or a theme. It says "aborted". I think that the problem is that the file is not signed or something. In CWM2.5.1.8 works but the problem is that CM7 or MIUI changes it to CWM3. So, what should I do?
Thanks!
Works fine, even the mentioned zip-file!
The "issue" is that the latest CWM3.x no longer support "amend scripting" (stored in update-script) and won't apply zip's created with such scripts. Therefore all .zip which where written using the old method should be converted to edify scripting (which use different statements - more details here-).
is there an way to downgrade the 2ndinit? an how-to would be very nice
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
nepotu said:
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
Click to expand...
Click to collapse
and how do i do that? with rootexplorer? what for do i need the file permission? to change it or to set it after changing the files?
Yup. You can replace it using an app like root explorer. And the file permission should be set up after you copy the file (if you have the wrong file permission it won't work).
EDIT: I haven't tried yet to downgrade it this way but that's what I've read on the forum, therefore I cannot guarantee you it will work.
sry for me being a noob. i found the file named recovery in the folder you mentioned. but have got only the file 2ndinit.apk..... where do i get the recovery file from 2ndinit.apk ?
thank you for your time!
You can unpack it using a tool like Apk Manager 4.9 or simply by using 7zip to extract the files from the apk which is in fact some sort of archive. However as I've mentioned in the previous post I didn't tried to downgrade using this method. All I can say is that I've read here on xda about this method, therefore I cannot guarantee you this will work. I think is better to wait someone with more experience to answer.
As an unexperienced user i think i'll wait for a better solution.
As i read, this problem appears quite often, how come that nobody tried to make a solution for this problem?
im trying to make my own rom trying to try new this out and i was going around taken lil apps tht other roms hads like hulu, mastermind mirror, ect and i dont think i zip it correctly cause when i check the inside of the zip folder the other file is still not zip and i am sure that is a problem right ??? ps im using cwm 3.0 is tht a problem ?
i use this meth...
ok, here it goes.
first, figure out where you want to push your file. i'd reccomend pushing manually in recovery to make sure the file itself works. then, using a tool like 7zip (pc) or betterzip (mac) create a file structure that matches the one on the phone. for example, if you wanted a boot animation to be put in system/customize/resource, make a folder system, customize in that, resource in that, and the bootanimation.zip inside that. now you have the main part. next, make a folder in the root of the zip called META-INF (caps counts) inside that, com, inside that, google, and inside that, android. thats /META-INF/com/google/android/. inside android, you need to place in an update-script. i'd reccomend taking one from another zip and just editing it becasue i still have not figured out a way to make that type of file (unix exec) from scratch. open it up in a .txt editor like notepad++ (pc) or coda (mac) and write your script. here is the baisic script for copying the directory system on the zip to system on the phone (like flashing a boot animation).
copy_dir PACKAGE:system SYSTEM:
CAPS COUNT AND MAKE SURE YOU HAVE AN ENTER AT THE END. IF YOU DO NOT HAVE AN ENTER AT THE END (TO MAKE IT TWO LINES INSTEAD OF ONE, LIKE ISSUEING A COMMAND) THEN IT WILL NOT WORK AT ALL ( E:SYNTAX ERROR IN UPDATE-SCRIPT IS THE ERROR YOU WILL GET)
so put this file into the folder android, and zip it. make sure it is in store only, compatibility mode, if you have such options. then, use an auto signer (or just say zip is not signed and make sure to put sig verification off) to sign the zip. flash, and watch your work magically appear.
the update-script i showed is written in amend. i have no idea how to write in edify bcuz it is much more complicated with the binary and stuff. so dont flash with cwm 3.0+.
i only have 1 thing to say first switch to amon ra amon ra is 1000 times better than clockwordmod
how do i switch?? lol also what if i unroot my phone would tht be a problem?
Jcki4 said:
how do i switch?? lol also what if i unroot my phone would tht be a problem?
Click to expand...
Click to collapse
go here and download the PC36IMG.zip and follow the directions
http://forum.xda-developers.com/showthread.php?t=705026.
as for setting up a rom unzip one to see how it's set up, i have changed a few things in some and zipped it back up and signed it but never built one, sorry couldnt be more help