Related
I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.
dynamite1985 said:
I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.
Click to expand...
Click to collapse
Is that meant to work for the milestone? I dont see milestone listed on supported devices.
Is this the kitchen you are referring to?
ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.
dynamite1985 said:
ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.
Click to expand...
Click to collapse
Sorry buddy. I ain't a developer. Try sending a PM to Luca or Kabaldan or Feeyo ( on cronosproject ) and see if they can help.
The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.
kabaldan said:
The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.
Click to expand...
Click to collapse
so I'm a little confused...
it seems to me that I should be compiling the kernal with the 2nd-init attack, which confuses me because of the BL issue. or is the stock boot.img used with a customized system.img?
i've tried the latter part, and gotten the noted error.
After I heared that Faryaab stopp Devs for now (I hope he will come back) I tried to make his Build ([ROM][05 APR 11][F1 CyanogenMod 7 V1][EXT2]) to CMW.
I tried it by trial and error.
I used a normal CWM ROM, and replaced the system folder with that of the EXT2 one. There are almost same files in there exept the bin folder. First I used these files from the EXT2 build (CM7 V1) and after that these files of the CWM build (CM6.1 V1).
I booted these ROMs but the Animation never stops, so I decided to remove the animation files (I hoped to see the current code for debbuging) but there was only a black screen, but it continued to the "Desktop" of android but only the statusbar is visible and I can pop it up. But that was it.
Maybe Someone could help me solving this problem (because it's the fastes build here).
Here is the file without boot animation, so you can see the problem
Download
check this, got it from neopeek, saying it has sme work to do to make it work, =)
http://hotfile.com/dl/121453498/1d6eb9f/CM7Final-Developer.zip.html
Hello my fellow Android crack flashers! So Volk and I have wrote(him) and tested(me) his g2x nullifier for our phones. Well it works flawlessly! Which his thread is here. So with our learning adventures he has helped me port it to the O2x. So here is the run down. This was originally created as the g2xscrubber was insufficient enough for our flashberry addiction, and on top of that if wouldn't wipe our /cache either. And yes this is the same thing from the p990 dev thread but I just wanted to post in the official su660 thread since its avail for me to do so...
So the domino effect has begun. This is a simple script that will wipe your internal partitions cleaner then a whistle and get it dam near like new status, perfectly ready for a ROM. Like as if you just purchased it and didnt have any data on it nor a ROM and needed to be flashed. And yes it came all tricked out like that with CWM and all.. haha
So here it is...
The O2x Nullifier
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does something. It also formats the partitions afterward, including /cache too! Enjoy!
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it. I've ran this Nullifier like 20 times in the last two days of first testing and on average its about 1204 seconds or about 19.8 minutes, on average. The Single pass zip is only half of the time of course. Or you can just watch the progress bar. After 20 times of nullifing and log pulling in 2 days, im pretty dang sure the bar is accurate. So enjoy!
2. ONCE THE NULLIFICATION PROCESS HAS BEEN COMPLETED DO NOT, I REPEAT, DO NOT TURN OFF OR LET YOUR PHONE DIE BEFORE FLASHING A ROM OR RESTORING... or you will brick your phone.
3. I will provide help, support, etc. for this, but as always flash at your own risk and I am not responsible if you turn your phone into your next non-aerodynamic frisby.
Enjoy!
Also I have now decided to copy the log to sdcard at completion (thanks to DARKSIDE for the idea). But from now on the log created in /tmp while in cwm is now copied to sdcard as O2x-Nullified-recovery.log. So it will still be deleted from RAM but never lost any more!!!!! muhahahahahahah... love it!
Thanks go to Волк aka Volk for letting me test and learn from his G2x Nullifier script. And also to owain94 for helping me make sure that this thing will run ok on the O2x, since I dont actually have the O2x..
Also if is doesn't work, please we need logs. You need to use a file explorer or put the external sdcard into your pc and grab and upload or pm me the log from your sdcard the file will be named 'O2x-Nullified-recovery.log'
Hi!
I have su660, i would like to know the difference bettween nullifier single n dual? Or which one works with su660?
Im new to this.
Thanks a lot!
Sent from my LG-SU660 using XDA
magbobote69 said:
Hi!
I have su660, i would like to know the difference bettween nullifier single n dual? Or which one works with su660?
Im new to this.
Thanks a lot!
Sent from my LG-SU660 using XDA
Click to expand...
Click to collapse
haha nice avatar pic! but the difference is based on ocd levels. lol Basically we originally did the Nullifier to have two passes in the nullification process just to make sure that all data has been zero'd out before formatting. However with the time it takes to complete such a process it seemed a bit much and end users didnt like it much. So we made the single and dual passes. Basically the single pass only does one nullification pass before formatting and moving to the next partition.
getting an error on CWM saying "build.prop s660..."something and its not doing its thing...sorry was not able to get the exact message...will try later if have time
chupi_24 said:
getting an error on CWM saying "build.prop s660..."something and its not doing its thing...sorry was not able to get the exact message...will try later if have time
Click to expand...
Click to collapse
sorry didnt see this till now.. it was my moms bday yesterday so I wasnt paying attention... however please get the log from /cache/recovery/last_log... Im not going to guess at what the error could be. I gotta have actual info to give you a better resolution.
My Galaxy Tab 7 P1000 was originally running clockwork 3.X... and I just tried to install clockwork 5... and after installation, the device keeps staying at the boot screen. And when I go to recovery mode, the 'HOME' button doesn't work.... :crying::crying:
How can I fixed this brick back to a normal tab?
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
priyana said:
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hey Dude,
Thanks for your reply. I will try it out tomorrow and hope it works on my stupid tab.
By the way, 1 more question. Before reading your reply, I tried to install CWM-based recovery 5.0.2.8 again and tried to install CM9.x on the tab, but not matter which version I used, (P1000, 1000L, 1000N), all of them gave me 'assert failed getprop( ro.product.device ) galaxytab...'. It sounds that the ROM installation file couldn't recognize my P1000 tab.....do you have any idea on how come my device couldn't be recognized.
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Thx X 1000000000000000000000000
ableeker said:
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Click to expand...
Click to collapse
I was wondering how I could edit the framework-res.apk (it can be found in the /system/framework directory) file and not brick my phone, I've tried putting a modified version
in a signed zip file that was supposed to be for that very purpose, a stock update.zip for getting rc29 to 1.5(and yes, I did flash my phone back to rc29) and I recently tried to just take a file manager in root mode and copy-paste-overwrite, but I just soft-bricked my phone halfway into the process, probably because it was still mounted
P.S. I did mount the /system directory as rw
my phone:htc dream,no 2g-3g contract(wifi only),rooted (universal androot),stock 1.6 drc83(but I can get it to rc29,1.5 and crc43; at least I think thats the name of the second update),stock recovery,superuser elite+superuser- latest, su binary- latest, busybox- latest binary, and about 5000 scratches.
--edit-- can also get cyanogen recovery,and root through cm 4.1.99, and cm4.2.15.1.
So is your goal to root your g1? Have you followed any guides to root? Can you give just a bit more detail of end goal and a bit confused about what os you are currently running. Also its nice to get all info from bootloader screen
Sent from my HTC Vision using xda premium
reply
demkantor said:
So is your goal to root your g1? Have you followed any guides to root? Can you give just a bit more detail of end goal and a bit confused about what os you are currently running. Also its nice to get all info from bootloader screen
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I've actually already got cyanogenmod 4.2.15 on it so rooting isn't really an issue right now.
What I really want to do is theme my phone, because I really like the ICS buttons and black statusbar - but I want to wait until I'm more experienced
before I try to port cm7 to the g1 (as far as I know, cm7 is the first cyanogenmod to support themes).
P.S. since this is being sent from my g1 - I can't currently post my bootloader info; but I will as soon as I can.
Also. I want to know how I can sign the framework-res.apk after changing it to my satisfaction.
Sorry, reading my last post (although 2months old) I must have been trying to reply to someone else
You don't need to sign the framework-res
Just decompile with apktool, make changes, recompile (make sure to add the metainf and manifest from original back in) then you can create a flashable.zip to flash it and chmod, or add it to a ROM and sign the ROM or use adb when in recovery to push it and change permissions
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Sorry, reading my last post (although 2months old) I must have been trying to reply to someone else
You don't need to sign the framework-res
Just decompile with apktool, make changes, recompile (make sure to add the metainf and manifest from original back in) then you can create a flashable.zip to flash it and chmod, or add it to a ROM and sign the ROM or use adb when in recovery to push it and change permissions
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
How would I sign the rom if I put it in one?
Apktool gives me errors when I try to recompile.
Ninjamorph from the market makes the changes, but they don't take hold.
P.S. perfect timing with the reply, as I posted my reply only about 45 min. ago!
If there are errors recompiling write those down and I'll take a look, as for as signing the ROM there are many ways, I use signapk for windows and one that amonra made for Linux, just Google search sign ROM android and you'll find many ways
Sent from my Nexus 4 using Tapatalk 2
Is there any posibility that I could just send you the rom I want to mod & a zipped folder containing a modified framework-res, and have you recompile/sign it? I just don't want to brick my phone. Thanks in advance!
If its a ROM for the g1 I already have it, how about just sending me your modded apk along with a link to the ROM and I'll make you a flashable.zip to install
And FYI, this isn't something that could brick your phone, recovery wouldn't be effected so worst scenario is you would end up in a bootloop
Sent from my Nexus 4 using Tapatalk 2
The rom is cyanogenmod 4.2.15.1 and I can't quite remember the link, but I'll post a zip with the frmwrk-rs and my email. Thanks in advance for the help!!
Here is a zip folder with the extracted/modified framework-res, if you don't have the rom I mentioned then ask for it in a comment.View attachment framework-res.zip
Sure, I'll take a look when I get home
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Sure, I'll take a look when I get home
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Once you've signed/recompiled it, send the rom to me as a google drive/google docs file at [email protected] (or, if you know another better method, tell me) and I'll test it.
ok so finally got to a pc,
here you go
havent tested it at all, it recompiled but there was an issues with
framework-res\build\apk\res\drawable-land\Thumbs.db'
and
framework-res\build\apk\res\drawable\Thumbs.db
they were skipped but the rom should flash and whatever mods you made should be present other that this, dont have time to peek around and see what you did
demkantor said:
ok so finally got to a pc,
here you go
havent tested it at all, it recompiled but there was an issues with
framework-res\build\apk\res\drawable-land\Thumbs.db'
and
framework-res\build\apk\res\drawable\Thumbs.db
they were skipped but the rom should flash and whatever mods you made should be present other that this, dont have time to peek around and see what you did
Click to expand...
Click to collapse
Thank you so much for your time!
downloading......................
.......................complete!
flashing......
DREAMWAVE_devteam said:
Thank you so much for your time!
downloading......................
.......................complete!
flashing......
Click to expand...
Click to collapse
--edit-- (the best I can recall it saying)
finding update
opening update
verifying update
failed no verification (352 files)
update failed
installation aborted
Does the ROM flash for you with you current setup before the edited framework-res? What I mean, if you were to flash the update-cm4.... (Whatever the name) right now it flashes correct? With your current SPL, radio, and recovery. The only thing I did was recompile your framework-res, swap it with the one from the ROM you mentioned, rezipped and signed the ROM
I can't think of any edits you could have made to framework-res that wouldn't allow you to at least flash the ROM, may get stuck in a boot loop or never boot, but the ROM should flash
Sent from my Nexus 4 using Tapatalk 2
I looked inside the rom you sent me, and I didn't recognize any of it.
this is a link to the rom I got the framework-res from:
http://code.google.com/p/cyanogen-u...pdate-cm-4.2.15.1-signed.zip&can=1&q=4.2.15.1
from what I saw, the one you sent me looks more like a flash image than an update.zip,
if you look inside the one that I was talking about, it looks more like an ota, and I can flash it in cyanogen+jf 1.4 recovery which I got
from the flashrec app (not on google play anymore, from internet only).
I don't know if an unmodified version of the rom you sent me would flash, but the one you sent me seems to have problems in general.
No errors that would point specifically to the framework-res are appearing.
Here are the files that I modified: View attachment 2212696, decompile your own framework and paste/overwrite the contents over the contents of the res\drawable directory in the framework-res.apk.
I'm pretty sure that's the same ROM I installed you apk into, I'll be home shortly and take a look again, could have made a mistake
Sent from my Nexus 4 using Tapatalk 2
This rom that you gave me is about 10mb larger than the one I use, and takes 30 seconds to load in recovery and freezes everything momentarily.
@DREAMWAVE_devteam
yeah same rom, even checked SHA1 to make sure (with the ROM before i added your framework-res)
which is 1604kb compared with 5589kb of the original. so whatever was changed is what wont allow it to work
can you just quick go over how you decompiled and what changes you made, i know you linked something and ill look at it but i dont have a ton of time to dig right now so a brief overview would be nice