Database Info

German users hands up

Hey this thread should be for all german users and problems occuring on german G1s , i would suggest that german users who have problems downgrading or rooting the G1 can posthere,
i would like to know if someone with an German G1 has already downgraded the device!

well everybody is waiting for a messias
some tried to downgrade but did not succeed..
there are 2 possibilities
1 - someone alters the american downgrade with a different CID or whatever keeps it from running on our G1
2 - some european linux pros find an exploit in our firmware

rc33
What if we get the RC33 update[version 1.5]? Can we downgrade to RC29 then?
I'm a Dutch G1 user, same build thus. Also waiting for root access, for tethering & auto rotate mainly.

As i mentioned in other threads we all got the same issues with downgrading/becoming root/chanching hte bootloader/do anything weird with this device..
My spec are:
Model Info:
T-mobile G1
Firmware version :
1.1
Basebandversion:
62.33.20.08U_1.22.12.29
Kernel version:
2.5.25-01843-gfea26b0
[email protected] #6
Build number:
123099
Bootscreen says:
DREA110 PVT 32B
HBOOT-0.95.000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
When booting o the update.zip it seays: Finding - / opening - /verifying update package and then at "installing update" package it prompts:
Code:
E:Failure at line1:
assert file_contains("SYSTEM:build.prop", " ro.build.fingerprint=tmobile/kila/dream/trout:1.0/TC4-RC30/116143:user/ota-rel-keys, release-keys") == "true" || file_contains("SYSTEM:build.prop", "ro.build.fingerprint=tmobile/kila/dream/troInstallation aborted.
any ideas?
Do the others have the same issues?

I thiunk i will wait for other comanies to sell android-able phones and get one of their's.
Spent about 20 Hours now on googleing and searching. That usually should do it 10 ten times trying to solve any problem with linux, but it doesn't.
It occurs to me that android isn'T as free as they say and that it isn't as opensource as everybody is told. That's CRAP!

dirty_ said:
It occurs to me that android isn'T as free as they say and that it isn't as opensource as everybody is told. That's CRAP!
Click to expand...
Click to collapse
Please search "open source" on the dream forums. This stupid bs has been gone over before.

German G1s with the new CID can NOT be downgraded with the available leak NBH files. CID mismatch. They also can NOT be upgraded with RC33 update.zip files, as updaters are region specific (assertion in the update script that checks the device's existing fingerprint against an allowed list).
Long story short: German G1 owners have to wait for now.

dirty_ said:
I thiunk i will wait for other comanies to sell android-able phones and get one of their's.
Spent about 20 Hours now on googleing and searching. That usually should do it 10 ten times trying to solve any problem with linux, but it doesn't.
It occurs to me that android isn'T as free as they say and that it isn't as opensource as everybody is told. That's CRAP!
Click to expand...
Click to collapse
Example of someone who does not read, just *****es. The OS is open, the device is not. Blame your cell provider, not Android. Also go read a few threads and by all means, return your G1 and buy something later after you have done some reading.

You can also debate in german here.
hopefully they will fix this issue ...

hm, i'm also waiting for a solution, i've allready asked JF but didn't get an answer yet

when you can't contribute, you're in a really bad position to get an answer
when you have a good idea in how doing this, I'm sure JFv is willing to help...

Can you made a package which install telnet server?
I didnt understand what exact happened when you install a new application, I think it install as root???

seriously waiting for the DREAIMG.nbh for german t-mobile G1.
seriously waiting for the DREAIMG.nbh for german t-mobile G1.
I updated my german t-mobile G1 from rc29 to rc33.
after i upgrade my g1 to rc33 i keep getting an sms from an operator number every 5 minutes. I have to disable the notifications for the text messages cuz I have 36 sms from the same operator and it's getting more.It's annoying.
and the number is +491770702600 . i don't use an t-mobile sim card. my sim card is from e-plus.
I didn't have any problems until i upgraded the g1.
can't downgrade.have read about "SoftSPL Flash any ROM" for fake changing the CID but it's too complicated :S
anyone has the same problem?

Yes the same exactly , i just update it with the:
https://android.clients.google.com/updates/signed-kila-ota-126986.f6469a1e.zip
to rc33 and get the f.... sms all the time, any ideas anyone out there

emiliosdance:
you have a t-mobile sim?

The signed-kila-ota-126986.f6469a1e.zip is a USA RC33 Update...
I dont know why it run on German G1, and the Downgrade RC29 not...
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PLAT-RC33
ro.build.version.incremental=126986
ro.build.version.sdk=2
ro.build.version.release=1.1
ro.build.date=Fri Jan 16 15:36:09 PST 2009
ro.build.date.utc=1232148969
ro.build.type=user
ro.build.user=android-build
ro.build.host=apa1.mtv.corp.google.com
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=T-Mobile G1
ro.product.brand=tmobile
ro.product.name=kila
ro.product.device=dream
ro.product.board=trout
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
# ro.build.product is obsolete; use ro.product.device
ro.build.product=dream
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=kila-user 1.1 PLAT-RC33 126986 ota-rel-keys,release-keys
ro.build.fingerprint=tmobile/kila/dream/trout:1.1/PLAT-RC33/126986:user/ota-rel-keys,release-keys
# end build properties
#
# system.prop for dream
#
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface = tiwlan0
ro.ril.oem.ecclist = 999,000,08,118,112,120,122,110,119
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientid=tmobile-us
Click to expand...
Click to collapse

Cause of the rom signature, you can not install der RC29 rom. Your G1 is not able to boot this rom.

Fix it
I just did this update , and it worked , hope that i will not get the messages again:
https://android.clients.google.com/updates/signed-PLAT-RC33-from-RC30.f06aa9b3.zip

what is the diffrent from
signed-kila-ota-126986.f6469a1e.zip

The fix did not work.
The update proses is a little more detailed but the f.....messages still coming.
I am trying now to change the boot loader so i can downgrade, since the German g1 give no access to it.
any ideas

[ROM] myTouch 3G: Nothing but Netfilter 1.6 - Donut Update

Download link: MT3GV1.5_NBN1.5.zip
MD5:
1c962a4767659f86776fe6daf3052cf7 MT3GV1.5_NBN1.5.zip
This is the result of the work/messing around I did in this thread.
I started with the T-Mobile OTA stock ROM available here:
signed-opal-ota-150449.95700137.zip
I then:
1. Rebuilt the kernel with the same config as the ROM, except with the addition of the netfilter features required for tethering. (Kernel source is slightly newer than in the ROM as yesterday there were a few security related patches added to the repo.) The wlan.ko driver was rebuilt to match the new kernel as well.
2. Added the Superuser app and the Tethering app.
3. Removed the T-Mobile recovery and radio images. They are redundant at best, bricks waiting to happen at worst.
4. Re-packed and re-signed the ROM. (Only the ROM zip was signed so it would install via our recovery images. The internal apks were left alone.)
The result should be an experience identical to the stock software you had out of the box, but with the possibility of running apps that require root as well as tethering. Speed is the same, features are the same, apps are the same, etc.
There are plenty of great custom ROMs here if you're looking for more, but this will work if you're going for simple with no surprises.
UPDATE: Donut /1.6 update is on page 3.
UPDATE: Donut /1.6 DMD64 update is on page 4.

Is this for 32B or 32A?

This is for 32B.

awesome
hey man great job this is exactly what i want!!! great job!!!

atomtom, thank you for doing that. It's been working great the last 24 hours, no hidden gotchas or surprises from the updated kernel/wifi driver.

Thank you!!!...This is EXACTLY what I was looking for ..expecially for my friends who want root for wifi tether!!

Clean and Stock
Thanks for this ROM. I like clean and simple builts and this fullfill my tethering needs with my Viliv S5. I installed it today on MyTouch 3G.

Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?

Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.

Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.

atomtom said:
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Click to expand...
Click to collapse
Hi there
I am running SPL 2005 (aman_ra mytouch root guide)
32B radio from htc site for google ion 2.22.19.26I
recovery 1.2.0G (aman_ra)
I have been going back and forth trying to find the rom that works best for me so yes i have done the format/wipe. Also since i want to be sure i might even run the following ontop of the format/wipe
fastboot erase system -w
fastboot erase boot
I dont erase recovery since i dont think i need to.
Please let me know.
Also - I would LOVE it if you could provide the same rom but with HTC keyboard/dialer.

flamingblue8z said:
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
Click to expand...
Click to collapse
Yeah, the one that is available stand-alone is older than the one that comes with other ROMs. When I tried installing the newer apk pulled from Cyanogen 4.0.1 it would fail due to the key used to sign the ROM internals.
adb install Superuser.apk:
Code:
159 KB/s (14979 bytes in 0.091s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
adb logcat:
Code:
E/PackageManager( 58): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 58): Package couldn't be installed in /data/app/org.zenthought.android.su.apk
If anyone knows how to sort this out let me know and I'll update it.
That said, su still worked perfectly when I installed Better Terminal Emulator. (Of course, Better Terminal Emulator doesn't work to begin with. Try typing in a number.)

hmm interesting. when I was using just the stock ROM, then used 1click root, went into CM-recovery, followed by your directions, adb mount -a, then adb push the SU in reference, zenthought's, I had no issue. I then pushed the wlan.ko you put up, and flashed boot.img, rebooted, and finally installed the Superuser.apk, and I had NO issues whatsoever. i've got a nandroid backup of that system setup, in case there is anything of interest in there. I would have to boot back into it and remove my txts/mms/contacts, but i'd gladly share it for analysis.
I noticed the myTouch NBH appeared earlier, im going to try downloading that on my WinMo Wing (it connects to the wifi at the college im at but my G1 and myTouch won't.) i'll try flashing the NBH then your ROM, see what happens... oh and yes, I obviously wiped before installing ur ROM.

ROM has Superuser Permissions and Superuser Whitelist? Whats the difference and are they both needed?

Superuser Whitelist is the name of the apk that manages which app gets root access, su is the command line tool that actually performs the actions requested as root.

speedyls91 said:
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Click to expand...
Click to collapse
After last night and today of normal use, and leaving it on overnight, I haven't seen any behavior out of the ordinary.

I spent the last hour or so playing around with the donut update, but there are problems.
I downloaded the COC10 to DRC92 update zip and looked through it. Appears to be a new boot.img, a handful of files, and a bunch of binary patches. I made the following changes:
1. New kernel with the netfilter features enabled, but otherwise same sources and config.
2. Replaced the wlan.ko patch with the full file that goes with the new kernel since the one we're upgrading isn't the original and the patch won't apply.
3. Changed the update script to not try to patch the wlan.ko and skip over the version/key checks.
The update (applied manually via the recovery image) went fine, but there are problems with one of or both of WiFi Tether and Superuser. When attempting to start tethering there is just a general failure error but nothing bad in the log screen. In addition the Superuser app no longer honors the "always yes" setting. There are newer versions of both apps so I'll check those out later tonight/tomorrow.

Wow, doesn't sound good. Maybe leave out Wifi tether? I have been using a better su whitelist app, I think u may want to use it. I am using stock Donut at the moment, runs GREAT, so if I can help this would be great. What I am going to do is load my nandroid backup, clear out some garbage, and if you want I can send u my system.img and u can pick it apart appropriately to take a look at the SU I have along with the whitelist app. Perhaps that will solve the problems.

Wifi Tether is kinda the whole point so leaving it out isn't an option (or rather, having the user install it manually won't help). I think getting the new Superuser app working is a higher priority though. Unfortunately a system image of a stock ROM won't do any good. The problem is that the Superuser app ties in to the system in a way that requires them to be signed with the same key (or a shared key, something I haven't looked in to yet.)
Code:
I/PackageManager( 78): /system/app/Superuser.apk changed; collecting certs
E/PackageManager( 78): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
My guess that the system is signed with T-Mobile's production key but Superuser is signed with a test key that is used on the fully custom builds. So it works fine with stock Android, Cyanogen, etc., but not here since I only changed the kernel, not the keys.
Obviously I can't re-sign Superuser.apk with T-Mobile's key so I have to re-sign the system with the test key. Unfortunately I have no idea 1) which file this is specifically, or 2) how to do it even if I knew.
Any suggestions are of course appreciated.

You mentioned that before. But even on the stock COC10 ROM, I pushed THAT su (from the last JF ROM,1.51) into /system/bin and then installed the apk into /data/app and it worked previously. If you wouldn't mind, plz send the new boot.img and I'll try flashing it through fastboot, as well as cm-recovery so I can use the root access adb to push the su into the stock donut. Which spl has fastboot enabled? I'll PM u my email.

Donut 1.6 Official system images for ADP1 now available!

Hi,
Some people on the forum probably noticed it already before me, but tweets from Cyanogen and JBQ brought it to my attention that the official Android 1.6 system images for the ADP1 are now available for download from HTC:
http://developer.htc.com/adp.html
I haven't installed them yet because my unofficial Cyanogen build is probably better than those in a number of ways ;-) But I did download them.
Also, these are probably required to build a real & working Donut 1.6 build from the AOSP tree.
Cheers everyone, and enjoy!
--Tim

Just wondering couple things:
1. Does it have Google Apps?
2. Do you loose root if you install this?
3. Does it mess-up recovery image?
So did anyone try it yet?

Hi Karolis,
I haven't checked the contents of the images but I expect them to have the Google apps. The 1.5 images from the same site contained them, as far as I know.
Whether or not it messes up the recovery image depends on the method of installation you choose, but you can always put back the recovery image of your choice on your ADP1.
I don't know about losing root access or not. I've heard people claim that it depends on your recovery image used. It will not include the SuperUser application but you can install that manually.
Cheers,
--Tim

HTC is an authorized Google distributer I guess:
# Use of the Google Software by You
1. You agree to use the Google Software only for purposes that are permitted by (a) this License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries).
Click to expand...
Click to collapse
I'm going to flash just the system image and see how it goes...

Didn't wipe, going from CM 4.1.11.1 to 1.6 - boot looped.
Finally got back to recovery (Cyanogen Recovery gone!) and wiped cache + user data, and at least got it to boot. Phew!
Better get Cyanogen's recovery back pronto, so I can restore my nandroid backup.
/Mats

dude.... dont use the OTA, use fastboot and fastboot flash boot and system and reboot -w. The reason it requires a wipe is because of the differences in frameworks, apps, dependencies, ramdisks, etc.
I was waiting for this, this is going to be my default now. I don't like all the stuff Cyanogen does to builds, I preffer the official ADP builds 1000's times more.
---edit----
I flashed it right away and now I'm confused. It's 1.6 alright, but the build is different from previous ADP builds, no dev tools or spare parts or anything else. This is almost exactly what you'd probably get from a stock 1.6 build, weird...

BTW, you don't lose root with this, ADP builds are meant to be rooted, you know?

can someone confirm if you lose cyanogen's recovery image?

···
这个还不错··希望走点出update包····but··我最期待cm 4.2···

Agh someone plz post a 32a version

Gosh, what a mess. After finally getting CM recovery back in, I went for a nandroid restore, but instead made a nandroid backup, overwriting my precious backup of my phone as it was before embarking on this 1.6 adventure. Well, after reinstalling CM 4.1.11.1 (hush - I had a backup on my SD card!) at least I got all my apps back.
Why must I dive into stuff like this when I'm in a rush and really don't have the time for it?
/Mats

I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.

marty22877 said:
can someone confirm if you lose cyanogen's recovery image?
Click to expand...
Click to collapse
You wont loose it if your flash the new system and boot partitions via fastboot. Any of the Apps 2 SD stuff won't work though.

elzee said:
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
Click to expand...
Click to collapse
????
Aaaanyway... I noticed this build doesn't let you su (wrong uid for the su binary), but that can be fixed easily, just pull su and Superuser.apk from another build, boot your phone into recovery, and push su to /system/bin and Superuser.apk to /system/app, then chmod 4755 /system/bin/su and reboot.
---edit--
you might also want to rm /system/xbin/su, but I don't know if it's really necessary or not. Gonna try it.

ok, removing xbin/su did nothing apparently, so it's safe. Keep in mind though that the stock boot.img is doesn't allow you to adb remount, but you can still adb shell, then su, and then remount manually (mount -o rw,remount /system). We just need to change ro.secure in it and we're good to go.

Using fastboot to only flash boot and system worked perfectly fine for me.
Very nice and clean.
Apps2sd can still be had if you want to, just do it the manual way (creating symlinks).
Pushing the xda versions of Launcher and Messaging makes the phone very, very nice - and the only things that I feel I'm missing is the userinit.sh and compcache really....I never really noticed/cared too much about the BFS.
Pretty nice build to be honest....

elzee said:
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
Click to expand...
Click to collapse
Because the G1 and ADP1 are both identical Dream handsets? And people want an official donut, rather than 1.5 with many donut features hacked in?

just wondering, will this work with rooted Dream Phones???

bootloader
i'm getting error message updating from 1.5 adp crc1:
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: HT847GZ00498
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Click to expand...
Click to collapse
i have a adp phone.
tried to roll back to stock 1.5 img or ota, same issue, is someone had this issue?

@ anyone who tried this. Which build number is this? Is it newer than 1.6_r1 (DRC79) or should I keep building the experiemental tree?

eClair 5.2 by Laszlo

..:: Eclair ::...
Powered by Android (2.1)
Made by Laszlo
==========================================
ROM Version: R5.2 edition (9 Mar 2010)
==========================================
# # #
(Google translate. please Laszlo PM a good translation)
# # # Introduction # # #
Android 2.1 Eclair EN! With all his ...!
Changed the name of the phone at the Era G1 / Sapphire (32b)
Speed, thanks to use SWAP partitions on startup
BFS Linux kernel!
10MB RAM patch!
Stability! 2.1 is the latest stable version of A. It is based on the SOURCE CynaogenMod!
Kernel WG-V3
The massive list of APN, including Polish operators ! (Era, Orange, Play, Plus MBank ...)
APP2SD = partition straightforward operation EXT 2/3/4 - Save space on your phone!
EXT partition information in the settings!
Animation page with Google Nexus One!
Graphic changes! Nexus One + Espresso + Others!
New wallpapers, ringtones (more than 250!)!
Active wallpaper!
Updates of Eclair camera!
Added applications: ES File Explorer, Gadu-Gadu_laszlo.edit, QuickBoot. APNdroid, HTC Teeter, SIM Tool Kit, Phone.apk_cytown, WyContacts, QuickOffice, ProcessManagerF Aktywne_optymalizowane_Tapety the Nexus!
After the installation is only a search engine!
Option "Reboot Phone" from the menu, red headphones!
Multi Touch! (By default, the 'Internet' and 'Maps')
Google Maps (Maps) 4.0 to navigate after the U.S. and Google BUZZ!
HTC virtual keypad with XT9 Polish dictionary!
Launcher with the Nexus One!
Probably forgot something, check yourself!
YouTube HighQuality working!
3D probably working, need testing
DOWNLOAD
http://l-rom.googlecode.com/files/clr_le-5.2-signed.zip

great
great to see variety i will flash soon

great to see the variety of devs, but is this any different from the eclairs we already have..?
ill flash it right now.

BadASS!! thats what I was trying to do is find more ROMs!, this is great! another new Eclair ROM!! Im gonna flash it right now!

nicknowsky said:
BadASS!! thats what I was trying to do is find more ROMs!, this is great! another new Eclair ROM!! Im gonna flash it right now!
Click to expand...
Click to collapse
Let us know some feedback and how it compares to other Eclair roms
Also
@dadme
You might wanna add [ROM] to the title ^^

just flashed
setup wizard FC'd
gonna try login google account thru market now.
okay i realized i dont have 3g with this rom, dunno why, lol restoring nandroid backup.
faill

3d
Probably no 3D since it has the ram hack

chim4ira312 said:
great to see the variety of devs, but is this any different from the eclairs we already have..?
ill flash it right now.
Click to expand...
Click to collapse
I agree, its great to see more. I mean with other devices there was tons of DEVs and Chefs. I know it complete different process, but still its great to see more ROMs

what is ment by
Graphic changes! Nexus One + Espresso + Others!
can we have the bubble look of espresso with this?

asb123 said:
what is ment by
Graphic changes! Nexus One + Espresso + Others!
can we have the bubble look of espresso with this?
Click to expand...
Click to collapse
I think it means the transitions/ animations for the windows and stuff...

What about camera/video/gps?

digitallysick said:
What about camera/video/gps?
Click to expand...
Click to collapse
dadme said:
Updates of Eclair camera!
Google Maps (Maps) 4.0 to navigate after the U.S. and Google BUZZ!
YouTube HighQuality working!
Click to expand...
Click to collapse
It should have working camera (updated), gps (google maps 4.0, so gps probably works) and video playback (since youtube hq is working)
Imma flash it tomorrow, so I can't confirm

Won't boot....
I can't get it to load on my G1 without Danger SPL, get error
"E:Can't chown/mod /system/xbin/procmem (No such file or directory)
E:Failure at line 24: set_perm 0 0 06755 SYSTEM:xbin/p"
Not sure how to fix it or I'd give you all some answers.

dont all 2.1 roms require danger spl as they are too large in size for original spl

asb123 said:
dont all 2.1 roms require danger spl as they are too large in size for original spl
Click to expand...
Click to collapse
Maybe he got the system partitin to be lower than 67 mb somehow

hmmm...
I removed almost all of the apps he added as extras along with the media folder. System is well under 67mb. Not sure why the failure.

sianaka said:
I removed almost all of the apps he added as extra along with the media folder and system is well under 67mb. Not sure why the failure.
Click to expand...
Click to collapse
What is the error message when you flash?

See above post.
I typed the error in my above post.
E:Can't chown/mod /system/xbin/procmem
(No such file or directory)
E:Failure at line 24:
set_perm 0 0 06755 SYSTEM:xbin/p
Installation aborted.

sianaka said:
I typed the error in my above post.
E:Can't chown/mod /system/xbin/procmem
(No such file or directory)
E:Failure at line 24:
set_perm 0 0 06755 SYSTEM:xbin/p
Installation aborted.
Click to expand...
Click to collapse
Only time I flashed a rom without an spl and the rom was to big (a hero rom) my rom flashed fine but then it hung at the g1 screen. So I had to just boot into recovery and flash something else.

well...how is the rom doing? i flashed...3 roms to my phone today LOL so i am waiting a bit to flash a new one
anyways, hows the speed/stability etc

[KERNEL] OTA 1.47.651.1 stock boot.img in update.zip

CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded

I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.

Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!

I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???

snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.

Any comments from people that have this applied (and working with full root)?

Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.

That worked Thanx

Kernel's working just fine with Avalaunch's Froyo ROM.

joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.

Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.

lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!

Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.

Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk