Database Info

Basic questions regarding Android ROMS.

sorry if these have been asked many times before, i've searched but cannot find much about it.
new to Android, coming from a WM for the past 8 years background its all foreign to me.
1) what is "adb" and how does it differ from "RC"'s? I presume RC's are just different build numbers for Android.
2) whats the difference between Haykuro, JF's builds? are any of them cupcake? how can i think about them in terms of Windows Mobile roms?
3) if I install one of the above, will the over the air updates still work? if there is an update to the OS (ie cupcake if the rom isnt) can this be applied at all or will i need to "lose everything" and wipe/flash to the new one?
again sorry for the n00byness.

1) what is "adb" and how does it differ from "RC"'s? I presume RC's are just different build numbers for Android.
adb is a way of telnet'ing from your pc to the phone, this gives you root access.
2) whats the difference between Haykuro, JF's builds? are any of them cupcake? how can i think about them in terms of Windows Mobile roms?
Haykuro and JF's builds are based on the android development branch, they are basicly updates that are based on googles on going improvements to the phones OS. Hayjuro's is based on a port from the upcomming saphire phone. Treat them as different "flavours" like schnaps etc
3) if I install one of the above, will the over the air updates still work? if there is an update to the OS (ie cupcake if the rom isnt) can this be applied at all or will i need to "lose everything" and wipe/flash to the new one?
Current custom roms change the signing keys so OTA updates are not updated onto the phone. You would have to manualy change the rom yourself.
Hope this helps
Imp

thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
also if having to reflash with new version, presumably that would wipe everything? is there a way of backing stuff up or are backups not as bigger deals as they are for a WM based OS.

The ADB build you refer to is essentially a rooted version of the ROM that came with the non-T-mobile branded developers phone.
Regards,
Dave

Impossible said:
adb is a way of telnet'ing from your pc to the phone, this gives you root access.
Click to expand...
Click to collapse
Err no. adb (Android Debug Bridge) is a tool for debugging Android devices both physical and virtual (in an emulator instance). One of its features is to give you interactive shell access, but this has nothing to do with telnet.
Haykuro and JF's builds are based on the android development branch
Click to expand...
Click to collapse
Also wrong. JF's builds are based on officially and unofficially released current branches, not development branches. Also, they are not ground-up rebuilds of the source code in as much as they are just modifications to existing releases to add root and other goodies.
Haykuro's builds appear to be coming from some private source close to HTC. These are not based completely on the open source development branches either.

thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
Rc33 is the current US G1 tmobile rom, Rc9 is the current UK G1 tmobile rom and the ADB1.1 is the developers rom thats carrier free. Think of these are the different between a WM "clean" rom and a carrier rom (such as att)
also if having to reflash with new version, presumably that would wipe everything? is there a way of backing stuff up or are backups not as bigger deals as they are for a WM based OS.
As for destructive flashing... the G1 can do non wipe upgrade but IMO I prefere a clean (wipe before) install. As default the G1 roms store images/music/bookmarks and other customisations to the sd card and if your syncing your contacts with gmail, they will be restored after your rom update, so even with a wipe>install you dont loose much (you loose things like text's, mms's and installed apps)

thefunkygibbon said:
thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
Click to expand...
Click to collapse
What you're referring to is the ADP not ADB.
ADP = Android Dev Phone
ADB = Android Debug Bridge

very helpful guys, thanks. as for over the air updates is that just for OS based stuff or do apps too? (do apps even update themselves?
if you have installed apps to the SD card then wiping the device is even less of a problem i assume

If you install JF's RC33, (or RC9 if you are in Europe), you will have a phone pretty much exactly like the official ROM, except you will have root and multitouch.
If you install ADP 1.1, you will have a dev phone with multitouch and root, but you won't see protected apps.
If you install Haykuro's H build, you will have HTC's "cupcake" phone with lots of added goodies and root.
If you install Haykuro's or the Dudes G build, you will have the Google "cupcake" phone and root.
The "cupcake" builds are very usable and stable, but there are still a few bugs being worked out on them.
With any of the builds, you will also need to use the radio version for that build. (RC 33 and RC 9 are using the radio you probably already have).
The radio can be flashed either before or after, and it won't touch anything on your phone, but it will reboot twice, so don't panic if you do that and see your phone hanging for a few minutes on a different screen after the first reboot.
With all of these versions, you can also put your apps on your SD card with a little more work.
If flashing a different rom, first sync your contacts, then use something like power manager or astro to back up your apps to your SD card, that makes it easier to get everything back. You will definitely want to do a wipe to avoid problems.
It is possible to go back to official roms after updating, but you will lose root, and I don't think you will want to go back. Often times you will get the modified updates here before they are even released officially!

Wow thanks, thats pretty much cleared up my questions!
.
With any of the builds, you will also need to use the radio version for that build. (RC 33 and RC 9 are using the radio you probably already have).
Do the files provided in the threads usually contain the radio's too are they seperate downloads/installs?
With all of these versions, you can also put your apps on your SD card with a little more work.
If flashing a different rom, first sync your contacts, then use something like power manager or astro to back up your apps to your SD card, that makes it easier to get everything back. You will definitely want to do a wipe to avoid problems.
Its something i'm used to with WM phones, but its always a complete ball ache resetting everything up and installing everything.
Is it at all possible to have some kind of OTA updates hosted system set up elsewhere (such as you or me) which could deploy the updates for these "hacked" roms, much in the same way as tmobile etc do?

Do the files provided in the threads usually contain the radio's too are they seperate downloads/installs?
It will say in the threads if you need to install the radio seperately. On most of the newer builds you will need to install it.
Is it at all possible to have some kind of OTA updates hosted system set up elsewhere (such as you or me) which could deploy the updates for these "hacked" roms, much in the same way as tmobile etc do?
The only roms which notify you of updates are the JF ones. There is an app on here that you can install which will let you know if there are updates. So far, it is all do it yourself as far as updating goes.
I don't know if it is possible without a lot of work to have the updates pushed automatically to your phone. At the moment, there are so many roms, some of which are updated more than once per day at times.
I have no idea what pushing them automatically to you phone involves, maybe someone else here does.

[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.

Android without Google applications

About the time when further existence of Cyanogenmod was endangered because of Google's legal claims, there happened to be a post from the author of Cyanogenmod:
Since I don't work with any of these closed source applications directly, what I intend to do is simply ship the next version of CyanogenMod as a "bare bones" ROM. You'll be able to make calls, MMS, take photos, etc. In order to get our beloved Google sync and applications back, you'll need to make a backup first. I'm working on an application that will do this for you.
Click to expand...
Click to collapse
The current state is that (supposedly) Cyanogenmod build does not contain any Google apps, BUT in fact to install Cyanogen you should first flash a development image from HTC (DRC83 or so) that contains them, and atop of this Cyanogenmod.
My question is, will the current Cyanogenmod build work without the HTC "base" files, in the way it is described in the message quoted above?
I own a Magic 32A. Could I just flash the latest Cyanogenmod update.zip (and another update.zip with appropriate kernel)?
I DO NOT want any proprietary apps on my phone.
(It will suffice if I have a web browser and a basic contact list application, without syncing.)
If anyone knowledgeable in the affairs of "update.zip" format reads this, I would also like to know if the Cyanogenmod's update.zip does only write some files to existing filesystems, or does it first erase/create new filesystems in some areas of flash memory? And what does the update.zip from HTC do (this one is certainly supposed to erase the root filesystem of the device!)? Would applying just the Cyanogenmod's update.zip leave the HTC files in place if they are already there, and how can I clean the root filesystem?

Not sure if that's how it works. Why don't you just remove the apps after?

If you really want Android without Google Apps, you can also compile from the source Android. That will give you basic functionality (phone, contacts, email) without Google Apps on it. You just need to checkout donut branch, instead of eclair's, since eclair is still on development.
Check: source.android.com and follow the documentation to checkout and compile for dream and sapphire

xaueious said:
Why don't you just remove the apps after?
Click to expand...
Click to collapse
The Google's libraries seem to be hiding in every corner, so that's not really clean.
@dferreira
Right, but it is probably some hassle (and I would duplicate some work of the people who publish their images here), also the download would take a long time with my internet connection. Why do it, if it's already done? A stock Android build from AOSP must be hanging somewhere around... but I haven't seen it yet. All the donut images I've seen on this forum had some silly modifications and were prepared to work with Google packages.
(Or is the source prepared nicely enough to work right if it compiles successfully and is put on the device? How do you put the build in an update.zip to allow flashing to a consumer device with a custom recovery image, but without engineering SPL?)

Donut branch should compile and work without a hitch. Even eclair works out-of-the-box, without camera working and 3D acceleration.
The compiled result will be recovery.img, boot.img, system.img, userdata.img... I've flashed them using fastboot Unless you know how to make a update.zip out of these, you should be all set. The update.zip only works if signed with the right certificates for non-engineering SPL devices.

The update.zip only works if signed with the right certificates for non-engineering SPL devices.
Click to expand...
Click to collapse
I wonder how do some folks from this forum do it then?
I doubt they have relations with google employees!
Do you know which kernel trees are compatible with the 3.22.20.17 radio firmware that is found in stock Magic devices?
AOSP has a kernel project and HTC has put some kernel sources at developer.htc.com, but there's only something called "HTC Magic Kernel Source Code" - no mention for which model.
Well, actually, i might do with some of the kernels that lie around the forum, but do they have any special requirements for initrd and modules, that would require modifying the flash images you get from building the Donut branch?
Seems to me that kernel is in the boot.img. You flashed it and everything works. You have not touched the radio firmware. Correct or not?

kguciek said:
I wonder how do some folks from this forum do it then?
I doubt they have relations with google employees!
Do you know which kernel trees are compatible with the 3.22.20.17 radio firmware that is found in stock Magic devices?
AOSP has a kernel project and HTC has put some kernel sources at developer.htc.com, but there's only something called "HTC Magic Kernel Source Code" - no mention for which model.
Well, actually, i might do with some of the kernels that lie around the forum, but do they have any special requirements for initrd and modules, that would require modifying the flash images you get from building the Donut branch?
Seems to me that kernel is in the boot.img. You flashed it and everything works. You have not touched the radio firmware. Correct or not?
Click to expand...
Click to collapse
Yes, the kernel is in boot.img, and it is the AOSP kernel that comes with the source code There is no radio firmware on AOSP.

update.zip is made by issuing make otapackage.

Hi buddy i thought about something like that few weeks ago and i think MarsDroid has already made some version of Android(Very lite MarsDroid SPL 7) fully without Google apps, so try it..

OK, I've built an image from donut source, coupled it with a kernel from a CyanogenMod port, and it works flawlessly on my phone!
I've uploaded the images to RapidShare, should anyone need them Links are at my website (guciek.net/en/stuff/android_builds).

kguciek said:
My question is, will the current Cyanogenmod build work without the HTC "base" files, in the way it is described in the message quoted above?
I own a Magic 32A. Could I just flash the latest Cyanogenmod update.zip (and another update.zip with appropriate kernel)?
I DO NOT want any proprietary apps on my phone.
(It will suffice if I have a web browser and a basic contact list application, without syncing.)
Click to expand...
Click to collapse
Yes, it works fine if you don't flash the 'defanged' update image first.

unfnknblvbl said:
Yes, it works fine if you don't flash the 'defanged' update image first.
Click to expand...
Click to collapse
But it wouldn't erase the whole system partition, so there could still be some files left.
Now that I realised I can flash images from recovery even without engineering SPL, it seems a safer and cleaner way.
Also, I like to have a second ext2 partition on SD card that is only accessible from a computer, and I wasn't able to do this with CyanogenMod, which instantly filled it with apps2sd data, swap files etc...

kguciek said:
But it wouldn't erase the whole system partition, so there could still be some files left.
Click to expand...
Click to collapse
No, that's why you wipe from recovery before installing.

unfnknblvbl said:
No, that's why you wipe from recovery before installing.
Click to expand...
Click to collapse
Actually wiping only erases the data partition, not the system one.

fastboot erase system -w

carz12 said:
fastboot erase system -w
Click to expand...
Click to collapse
Right, but it isn't possible for users with unmodified SPLs.
Actually, you can just flash a image of an empty yaffs filesystem to system partition (it's just a few blocks at most).

[REL-DEV] - Android 2.2 AOSP - With Demo Video

HTML:
Credit for koush for Droid2 Bootstrap
Credit for edgardcastro for sharing lots of information about 2nd-boot on Milestone1
Credit for Skrilax_CZ for 2nd-init and sh hijack
Credit for r2beta0 for how to 2nd-init on M2
Hello guys,
after weeks of work and trouble with the m2 i finally got a booting 2.2 AOSP image for the m2.
This is still work in progress, many things are not working, i am just releasing this one
to show that it's possible to build custom roms (even without the possibility of a custom kernel, for now).
Because i had some trouble to put the compiled android on the system partition without ending
with a not booting phone, i pulled the compiled system on the preinstall partition.
Installation is a little bit tricky but if you guys do as i describe below anything should work
without problems.
What's not working:
- Many things (Baseband, WLAN...)
What's working:
- Touchscreen (So you can at least play a little bit with the UI)
- Vibration
- Keyboard
- Light sensors
- 3D Gallery
- BT
The phone is faster without Motoblur.
Development is still in progress, but you can give this one already a try.
Based on MILA2_U6_3.12.0_SIGNED_US1MILESTONE2RETBRB125LA016.0R_GSXMILETRETBRLA_P026_A009_M012_HWp2a_Service1FF.sbf
What you need:
Rooted Milestone 2
Droid 2 Bootstrapper
PC with ADB installed
How to install:
1) Extract the files contained in the zip to the root of your sdcard
2) Reboot into recovery mode with usb cable connected
3) Restore the system partition with the image contained in the zip (nandroid restore over recovery)
4) Now open the adb shell and type:
-# cd /preinstall
-# rm -r app
-# rm -r md5
-# rm -r mml
-# unyaffs /sdcard/preinstall.img
5) Perform a full wipe
6) Reboot system
Whe the phone is turned off and you try turn on the phone, you will end in recovery.
Simply choose "Reboot system" to reboot into android.
If you have problem with battery, simply wipe battery stats.
Download
Demo Video

This is first relay rom, thanks

any screen ?

Without motoblur the phone is faster? Great!!! Looking forward to any ongoing development!

This deserves some attention!!!

This sounds good will give it a try if the wifi and baseband get fixed.
Sent from my A953 using XDA App

This made my vacation
Is there any possibility for you to run quadrant, just out of curiousity. even though there is still a lot of stuff not working.
Keep up the good work!

I boot it and it a work very fast
BT IS WORK

Looking forward to this.. Congrats on your feats so far..

Unfortunately i dont get it to boot.. bootloop so today im not going to test it .. maybe tommorow when i have time, yet i dont know why it causes a bootloop since i did it like you've said.. maybe because i forgot the preinstall, pushed it after restore and then did the rest (well its actually the same ... shouldnt cause a bootloop)

Got any screens for us?

Sounds very promising. Can't wait to see any further developments to this!

inheme said:
Got any screens for us?
Click to expand...
Click to collapse
Google "android 2.2"
It's just stock froyo. You'd better be off asking him for photos, but you could always try it yourself though. If you screw up, just follow my tutorial!
Sent from my MotoA953 using XDA App

So the system is basically located in /preinstall and you're using a minimal android build in /system?
Or do you mean you told te update.zip to install files into /preinstall and manually copied them over? Then what are the contens of the preinstall image?
I'll investigate when I have more time.
Sent from my MotoA953 using XDA App

Congratulations ! You are great, Thank you for giving more zest for life to m2

can u update the zip to u.115.com?
you know, we can not visit many american websites in CN,such as your "download" web.

Unfortunately i dont get it to boot.. bootloop so today im not going to test it .. maybe tommorow when i have time, yet i dont know why it causes a bootloop since i did it like you've said.. maybe because i forgot the preinstall, pushed it after restore and then did the rest (well its actually the same ... shouldnt cause a bootloop)
Click to expand...
Click to collapse
Did you do the full wipe? Wich rom do you have on your phone as base?
So the system is basically located in /preinstall and you're using a minimal android build in /system?
Or do you mean you told te update.zip to install files into /preinstall and manually copied them over? Then what are the contens of the preinstall image?
I'll investigate when I have more time.
Click to expand...
Click to collapse
Yes the compiled system is located on /preinstall.
The /system partition is still there for the 2nd-init and the recovery bootstrap.
This is just an experimental build, once i have something that can be released i will move try to move things on the /system partition, but i have tried this for weeks without success.
The system informations says that it is android 2.2, but for real it is 2.2.1. The 2.2 value is read from the build.prop file on the system partition, so don't think that is the stock rom with some customization, but a 100% Froyo AOSP.

Congrats. At least u gave us something real unlike fission Angdroid
Sent from my MotoA953 using XDA App

m0rph3us said:
Did you do the full wipe? Wich rom do you have on your phone as base?
Yes the compiled system is located on /preinstall.
The /system partition is still there for the 2nd-init and the recovery bootstrap.
This is just an experimental build, once i have something that can be released i will move try to move things on the /system partition, but i have tried this for weeks without success.
The system informations says that it is android 2.2, but for real it is 2.2.1. The 2.2 value is read from the build.prop file on the system partition, so don't think that is the stock rom with some customization, but a 100% Froyo AOSP.
Click to expand...
Click to collapse
Great, we (Owain94 and I) appreciate you sharing this information with us. We will build our alpha and beta builds using this method untill we find a way to install to /system. Thanks for your ideas!

Mikevhl said:
Great, we (Owain94 and I) appreciate you sharing this information with us. We will build our alpha and beta builds using this method untill we find a way to install to /system. Thanks for your ideas!
Click to expand...
Click to collapse
No prob. I am currently recompiling, it seems the wifi modules etc have problems if they are launched from /preinstall, i also found a way to get the system boot from /system, but i will be sure later when the build is finished. I will give you more information later.

[REQ][DEV][ROOT] Experienced Android Dev Needed for Rooting Samsung Galaxy Player 4.2

Dear Android Hackers!
Please consider helping if you have some spare time and good will.
The device is Samsung Galaxy Player 4.2 (mine is North America version from the US)
Product code: YP-GI1
Android: Gingerbread 2.3.6
Kernel: 2.6.35.7
There is no special section in XDA for this device, so we (the owners of such devices and others who are trying to help) were discussing the matters of rooting here: http://forum.xda-developers.com/showthread.php?t=1715461&page=999
We have tried all the publicly available exploit-based rooting methods, none works, the device release date is April 2012, and there is no Android Gingerbread Local Privilege Escalation exploit released after that date if I am not wrong, and all the old ones are patched as it comes out...
Disclaimer: I'm not a developer, and everything I know I've learned in the last month, so please not laugh if I'm telling something stupid
So, as I understand the options are:
1.
Solution: Find a new exploit, get root, install SuperSU, profit
Problem: There is no publicly available exploit that I'm aware of
2.
Solution: Create an update.zip package with SuperSU and BusyBox, install it in the Recovery Mode
Problem: We need a genuine Samsung signing key to bypass the signature checking
3.
Solution: Get the stock rom, inject SuperSU and BusyBox, flash using Heimdall or Odin
Problem: There is no stock rom available, where do you people get them ha?
4.
Solution: Port CWM to our device, install it, then install and update.zip with SuperSU and BusyBox
Problem: I don't know how to create a CWM rom for my device
So, can anybody help with anything please? THANK YOU!

Up.. Anybody?

There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.

dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
Thanks for your interest.
No, there were no updates, it is the stock firmware.
The source code of the kernel is available at Samsung's site. And I have dumped the contents of the /system partition (except for several config files, see below):
Code:
$ /data/local/tar -czf /sdcard/external_sd/system.tar.gz /system
tar: removing leading '/' from member names
tar: can't open '/system/etc/bluetooth/audio.conf': Permission denied
tar: can't open '/system/etc/bluetooth/auto_pairing.conf': Permission denied
tar: can't open '/system/etc/bluetooth/input.conf': Permission denied
tar: can't open '/system/etc/bluetooth/main.conf': Permission denied
tar: can't open '/system/etc/dbus.conf': Permission denied
tar: error exit delayed from previous errors
So here is the /system:
http://depositfiles.com/files/e0odb9gvt
password: XDA-DEV
P.S.
Also PM'ed you this post

dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
any way you could help?

You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.

I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53

flapflip22 said:
I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53
Click to expand...
Click to collapse
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.

Have you checked for rom on sammobile.com. If anyone can provide original firmware are those guys. You can also request it on their forum.
Sent from my HTC One S using xda app-developers app

Entropy512 said:
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.
Click to expand...
Click to collapse
can u explain this a bit more? what are touch keys exactly? sorry ima noob but we are still cant find anything. if you could post your ideas on the thread http://forum.xda-developers.com/showthread.php?t=1715461 that would be helpful thanks!

Entropy512 said:
You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.
Click to expand...
Click to collapse
I tought of the 2nd option but I miss actually the init.rc, init.hugo.rc and init and recovery files. Someone that tried to help me said that he can't do it. Maybe alice you can make a dump of this for me so I can build an insecure kernel. (hopefully)

good nice.....

Sorry, I was offline the last 3 days.
Entropy512, thank you very much for detailed description of the available options.
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/show....php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Click to expand...
Click to collapse
I don't understand this part. Wouldn't I just rewrite the stock image when flashing the dumped one? And what is the point of flashing the dumped image without modifications? (or you just didn't write about the needed modifications, e.g. injecting the su binary there?). And should I deodex the /system/app/ and /system/framework directories before creating the new image or no modifications are needed? And if it's preferable to deodex, how do I do that in Linux? Thank you!!
Added:
Meanwhile, I've created a system.img with injected su and superuser.apk, not deodexed, here - http://forum.xda-developers.com/showpost.php?p=31345895&postcount=418

1. Search google and xda...
2. Sign zip with signapk or some other signing tool...
3. Try sams firmware or extract your rom... search for how to in guide in my signature(create custom rom)
4. Search if someone have already ported it on your device or use build.clockworkmod.com
Sent from my GT-S7500 using xda premium