Related
Hey all, I guess if your here its because you want to build your own kernel from the HTC GB Kernel source for the HTC Droid Incredible. So that's what we're gonna do.
First things first. I have to send out a huge thanks to a few guys that helped me out along the way.
jdkoreclipse - Your the best man. Thanks for getting me compiling.
wdfowty - Always good on the code.
ohheyitslou - Standing by while a blabbered on with stupid questions.
conap - The original god of kernels.
Koush - Thanks for the anykernel updater.
Note: The method I descripe below is what worked for me to get this thing to build and boot. Additional packages may be required. Ie; JDK, Android SDK, Python, git and the 32bit libs (if your on a x64 machine). I do assume that you have them and have your computer set up for development. I also assume that you are fully aware that any damage caused to your devices from YOU following this guide is held at your own responsibility.
Click to expand...
Click to collapse
First things first, lets make sure you are on a linux distro. At the time of this writing, I was using Ubuntu 11.10 x64. Note: 64x is highly suggested. My computer is a dual core amd machine with 4GB of ram. I have a 250GB HHD.
Next lets download some things that we will need for your kernel.
The kernel source of course:
DROID Incredible by HTC (Verizon) – GB MR - 2.6.35 kernel source code
This is the correct size and MD5:
88.8 MB (93,175,808 bytes) 67c01623ff73415a99e5f8cd1d8ef11a
You will also want the CM Toolchain. This is what compiles your kernel.
Open a terminal window and type:
Code:
git clone git://github.com/CyanogenMod/android_prebuilt.git prebuilt
And finally, the anykernel_updater.zip for packaging and flashing your kernel: anykernel_updater.zip
Have these things downloaded? Great! Lets continue.
Next we need to create a new build directory to build your kernel in. For this tut, we will make this in your Home dir.
Open a terminal window and type:
Code:
cd ~
mkdir android
cd android
mkdir kernel
Easy huh?
Next grab your HTC Droid Incredible kernel source archive and just open it with archive manager. We don't need to do any untarring here.
You'll want to drag that 395.2MB folder inside called 'incrediblec-2.6.35-gb-mr' to that kernel directory you created.
Next, grab the CM toolchain archive and open it the same way. Yup just drag that folder thats inside there out and put right in your 'android' folder.
So lets review real quick before we continue:
Inside your Home directory you now have a folder called: android
Inside that android folder you have two folders. One called: kernel and the other called: android_prebuilt or prebuilt.
Inside the kernel folder you have your kernel source folder: incrediblec-2.6.35-gb-mr
Is this correct? Good.
Now, lets open a new terminal window and move to your kernel source folder:
Code:
cd '/home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr'
Now we will compile the source. Note: This is a basic kernel source compiling guide. Our focus is to simply compile the source. Nothing more.
In the terminal window type:
Code:
make incrediblec_defconfig
make -j4 ARCH=arm CROSS_COMPILE=/home/yourusername/android_prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Note I used j4. This is because I am using a dual core box to develop on. I think now days most boxes are usually dual core or quad core?
Your kernel should now be compiling. This process could run average between 5min-1hr. My laptop (which is beast) did it in about 2 minutes. But then again I'm running a full install of 'buntu x64 with everything updated and ready to rock.
Anyways after the compiler finishes building it will tell you where to locate your kernel and wifi driver. Yes the wifi driver is included!
The kernel should be at: /home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr/arch/arm/boot/ for those that don't know it is called 'zimage'. Just drag that out to your Desktop.
Now go grab your wifi driver. Its located at: /home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr/drivers/net/wireless/bcm4329_204/ It will be called bcm4329.ko. Again drag that out to your desktop.
Now you can close everything thats open. Grab that anykernel_flasher.zip you downloaded earlier and open it up with archive manager. Don't extract it, just open it.
Navigate to system/lib/module/ and drag your bcm4329.ko right into it.
Next back up all the way to the root of the anykernel_flasher.zip and then open the kernel folder. Yup just drag and drop your zimage right in there. Close the archive manager window.
CONGRATS!!! You just compiled your first kernel from source!
Now you can rename the zip to whatever is easiest for you to remember. Common practice says the date and time should be in the name. Like mine from today is called: 2.6.35.13-stang-kernel-1830-110111.zip.
Now go test your kernel. Just put it on your sd card and flash it through recovery. The anykernel_updater.zip will handle the wiping for you so you shouldn't have to worry about wiping boot, dalvik-cache or cache. You can still wipe those things if you would like.
Once the flash is complete, just hit reboot device and wait for your phone to boot up. It took mine about 5 minutes to fully boot up.
Well, I hope yall enjoyed this guide. I wanted to keep it simple. I am not a kernel god or anything but let me tell ya, I went through a lot to try to learn how to do this. So if you run into any trouble, I'll try to help you out if I can.
Have fun guys!
now what..........
Nice. Good job.
Sent from my ADR6300 using Tapatalk
Way to help us out with a good easy to follow guide stang thanks
sent from my sexy Slcd Droid Incredible. not dinc or D-inc that just sounds stupid.
tiny4579 said:
Nice. Good job.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Thanks Tiny. Now we need to get some more customs going
evilstewie23 said:
Way to help us out with a good easy to follow guide stang thanks
sent from my sexy Slcd Droid Incredible. not dinc or D-inc that just sounds stupid.
Click to expand...
Click to collapse
Thanks stew, You know how much this means to me.
Beast Mode! Very nice guide sir, I'm sure some of the more serious members will get hella use out of this. I have been (sort of) following your progress on twitter, so glad to see that you finally got it figured out. Nice work.
00McD00 said:
Beast Mode! Very nice guide sir, I'm sure some of the more serious members will get hella use out of this. I have been (sort of) following your progress on twitter, so glad to see that you finally got it figured out. Nice work.
Click to expand...
Click to collapse
Thanks Mc. I'm just happy to have learned this much atleast. I'm even more happy to share what I've learned. That's the important part.
wildstang83 said:
Thanks Mc. I'm just happy to have learned this much atleast. I'm even more happy to share what I've learned. That's the important part.
Click to expand...
Click to collapse
Definitely, I have always felt the same way. Sharing is caring lol
That's the stuff, Wildstang. Glad you're back.
Sent from my Prime_XL Incredible via Tapatalk
very nice. Im going to give a this a go and see what i can some up with. does this require a sense rom or a aosp rom?
dirtsky said:
very nice. Im going to give a this a go and see what i can some up with. does this require a sense rom or a aosp rom?
Click to expand...
Click to collapse
This compiles a sense kernel.
tcberg2010 said:
This compiles a sense kernel.
Click to expand...
Click to collapse
Well Sh*t. Oh well ill still give it a go I guess.
tcberg2010 said:
This compiles a sense kernel.
Click to expand...
Click to collapse
these instructions will work fine for aosp. You just have to download that kernel source instead. The compile process is the same.
Sent from my ADR6300 using Tapatalk
Ill have to get the kernel source and see what I can do.
Sent from my Incredibly awesome Droid Incredible.
Thanks for adding this howto, wildstang -
I really appreciate it. I just for the first time in a year+ went from my old rooted inc to this home-brewed self-compiled (I added cifs & tun built into the kernel) and installed it. I'd just tried the insensitive ROM as well and this helped things quite a lot due to cifs & tun. I also set the clock to a not-very-aggressive 1075000 which works fine on my inc.
Much appreciated and good guide.
edit: I forgot to mention that in general and here as well, you can 'brand' your kernel so you're sure you've really installed it and it is running on your phone by checking the firmware revs in about-phone. To do that, just edit Makefile and I think it is called Extra (under Version) which is as it is set to .13, so I set that in my case to .13-cifs-tun-cust, and it shows on my phone. It is useful in case you forget to zip the file up or something.
Hashi
Hello!
This is a thread where potential developers can get kernel and platform source code for Samsung Galaxy S I9070 Advance, and other info. I will try to update this until we will have first custom rom ready. I encourage everybody with some experience with android development, to share their knowledge with other users here. Please if any of you will make any progress in rooting, making recovery or developing custom rom, to write here in this thread or even start a new one if some major break trough will be made.
Ok so here are the links to sources (I don't know the diference between those to, but I guess it is region related):
GTI9070_GB_OpenSoruce
GTI9070_LA_GB_OpenSoruce
All sources, can be found HERE.
In the attachment you can also find some other info I've pulled from my phone, which used to be rooted, cause I had some test version. I hope all this stuff will help us get root access, custom recovery and last but not least a whole bunch of custom roms.
NOW LETS HACKING AND DEVELOPING BEGIN!!!
One more thing, PLEASE take a minute to VOTE for this phone to get its own forum section here on XDA. Just make a post in THIS THREAD. The device is not in the poll yet, so you must write a post in thread. THANK YOU!
We've made a step into a right direction with a lot of help from forum I've made a working root method!
I've hard bricked my phone, so I am off the developemnt from this phone, only if by some chance I get a replacement. Sorry guys, in spirit of developing I've killed my phone .
I wish I was better at kernel development... I would love some development for this phone!
Sent from my GT-I9070 via Tapatalk 2
I've somehow managed to configure linux and pulled andorid sources from the repo, now I have to figured out how to compile a kernel. I have much to learn but if nobody else will give it a try, maybe I will succeed.
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
kilsmap said:
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
Click to expand...
Click to collapse
Dear friend. I come from China, now I already have a good i9070, I can help you with your test, you can send to my mailbox [email protected]
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
kilsmap said:
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
Click to expand...
Click to collapse
Same thing here. I have no idea how to get those, been asking around the forum an searching, but for now all the directions indicates that you need to have root access to get iniramfs. That really sucks...
hahaha...from this point of view, all Samsung phones after Galaxy S Advance will be quite hard to root... I'm waiting for the Galaxy SIII to launch, and for someone to root it... Maybe then we will be able to use the same way to root our phone... If only we can see what's inside our kernel.bin.md5... I'm sure the files we needed are in there...
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
an0nym0us_ said:
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
Click to expand...
Click to collapse
Yeah.. We have the stock rom, but can't figure out which one should we extract the boot.img from.. There was system.img.md5, cache.img.md5, hidden.img.md5, modem.bin.md5, and kernel.bin.md5... So which one? My suspicion lies to the kernel.bin, but I have no idea how to extract it..
Sent from my GT-I9070 using XDA
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Good luck!
Hope you get to a solution soon
I can't work on it as I currently don't have a phone to test on, sent it in for repairs.
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Have u tried flashing it directly to the phone? You don't have to make it into a boot.img to flash it.. Because I'm afraid that the zImage will be useless if not paired with working initramfs.. Compiling the kernel is quite straightforward, the thing is to get the initramfs to turn the kernel insecure.. There are also scripts to extract initramfs from zImage, but I haven't had time to test it..
Sent from my GT-I9070 using XDA
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
qzem said:
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
Click to expand...
Click to collapse
Yep, you got everything right there, I think.. Initramfs, ramdisk are the same thing.. They should include the cpio.gz, init.rc, default.prop etc... Have you extracted these files from the source kernel? Cos I don't think we can copy directly from phone, cos we need to preserve the permissions set on the files... Can you do that with kitchen?
Sent from my GT-I9070 using XDA
I am following the topic and hoping it works out the development of kernels and roms to the device.
Come on it has to be a way to compile an insecure kernel without having the access to rooted phone. Cause all the options I found till now, required some files, that can only bee pull from rooted phone. But the whole point of an insecure kernel is the possibility to root the phone. Anybody can help us? Maybe I should start another thread, damn it!
Haha... Yeah, somehow I feel that Samsung is screwing with us, what with the new firmware format (never had kernel.bin before) and secured kernel, this is becoming impossible.. If we just have some devs good-hearted enough to port CWM recovery for us.. But without initramfs, I don't know if it's possible..
Sent from my GT-I9070 using XDA
The initramfs is inside kernel.bin.md5 (as for the Galaxy S firmware).
kernel.bin.md5 is a normal zImage Linux kernel (+md5).
the initramfs is included in the kernel image (see http://forum.xda-developers.com/wiki/Extract_initramfs_from_zImage)
the initramfs is in our case a uncompressed cpio archive, therefore the script in the wiki does not work, but https://github.com/mistadman/Extract-Kernel-Initramfs/blob/master/unpack-initramfs can extract it without problem.
So, there should be no difficulty to root the i9070...
The easiest way would be to change the initramfs and repack everything.
Dear XIAOMI MI 2 Users,
I know that we are very small community that have this phone , and from some reason , xda won't listen to my request to open to this extreme phone forum schema like the others for itself, so i need to post it here.
i know that everyone will want this
CWM For Xiaomi mi 2
I saw this post on Miui Australia, i can confirm it's working
http://www.miuiaustralia.com/?p=1030
to easy flash it , (because for me miui recovery wasn't let to flash it) recommend the following steps:
1. download the recovery from that post
2. connect your mi 2 with usb to the computer
3. extract the zip archive to some folder, so you will have the recovery.img file in that folder to flash using fastboot later
4. open cmd and use fastboot to erase the mi2 recovery (need to be erased!) using that command
Code:
fastboot erase recovery
5. use fastboot to flash it like that:
Code:
fastboot flash recovery recovery.img
you will see flash ok
6. reboot your phone to recovery (Hold power button + vol up) - you will get into cwm
7. now navigate using the vol keys to reboot system now, it will ask you if you want to disable recovery flashing, hit yes - coz we don't won't to let the miui rom to overwrite it with it's recovery again.
8. njoy
Credit goes to M1CHA - the man who compiled it to us, he is the man
BTW I will be more than happy if you guys will push xda to open forum for this phone too , it will be easy for us
yours, deliad
Thank you for the tutorial. I will try it out. I also truly wish there will be an official xiaomi forum available here.
One question: If I flash the cwm and then flash the OS (i.e, MIUI V5) afterwards, will it erase my cwm?
There is a lot of details here: http://miuiandroid.com/community/threads/2013-03-24-clockworkmod-recovery-6-0-3-0.19686/
With MIUIAustralia shutting down, don't know how up to date that page is compared to this one.
There will never be a forum here for this device or any put out by this company. Their stealing of code from the CM team and closing the missed source up is not what we want here. Not to mention their lack of ability to follow the GPL laws makes sure they will never be welcomed here.
Wayne Tech S-III
Do you have any proof to your allegations that they're stealing codes?
Sent from my GT-N7000 using xda premium
Leechoonhwee said:
Do you have any proof to your allegations that they're stealing codes?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Anyone that knows the history know it to be true. They even admitted it. But it all comes down to them not being gpl compliment
Wayne Tech S-III
zelendel said:
Anyone that knows the history know it to be true. They even admitted it. But it all comes down to them not being gpl compliment
Wayne Tech S-III
Click to expand...
Click to collapse
I know the Xiaomi history and company is following their own "code path" since MIUI v4 (which MI2 was based from start).
So again, please show proof for your "theory". Words, links, pieces of code whould be good.
And let me remind you that you also have Oppo Find 5 forum:
http://forum.xda-developers.com/forumdisplay.php?f=2155
Take a look at their system UI, which is taken from Xiaomi MIUI phones. So maybe you also could block Oppo Find for stealing UI style and code from Xiaomi?
Accidd said:
I know the Xiaomi history and company is following their own "code path" since MIUI v4 (which MI2 was based from start).
So again, please show proof for your "theory". Words, links, pieces of code whould be good.
And let me remind you that you also have Oppo Find 5 forum:
http://forum.xda-developers.com/forumdisplay.php?f=2155
Take a look at their system UI, which is taken from Xiaomi MIUI phones. So maybe you also could block Oppo Find for stealing UI style and code from Xiaomi?
Click to expand...
Click to collapse
Even the wiki states it is based on CM sources. But even beside that fact. They are not GPL compliant and until they are they will not have a place here.
zelendel said:
Even the wiki states it is based on CM sources. But even beside that fact. They are not GPL compliant and until they are they will not have a place here.
Click to expand...
Click to collapse
Wiki? Lol. Yea... Lets believe on everything wiki says...;p
MIUI v5/v4 is not based on CM sources. You have old info.
But I agree about GPL (some aspects...). But also OPPO didnt want to public their kernel sources, which they did recently... And what about Oppo non public aapt sources?
Accidd said:
Wiki? Lol. Yea... Lets believe on everything wiki says...;p
MIUI v5/v4 is not based on CM sources. You have old info.
But I agree about GPL (some aspects...). But also OPPO didnt want to public their kernel sources, which they did recently... And what about Oppo non public aapt sources?
Click to expand...
Click to collapse
Oppo is working hard with the developers. As can be seen every where. The wiki was just the one I cam across first.
MIUI has no respect here and until they start giving back to the community instead of just taking from other developers then they never will. And until they follow the GPL no device forums will ever be here. I am dont arguing about this.
zelendel said:
MIUI has no respect here and until they start giving back to the community instead of just taking from other developers then they never will. And until they follow the GPL no device forums will ever be here.
Click to expand...
Click to collapse
But what about this???
https://github.com/mitwo-dev
https://github.com/mirom
Dikks said:
But what about this???
https://github.com/mitwo-dev
https://github.com/mirom
Click to expand...
Click to collapse
There is no kernel source code there. it is only the patchs for makeing ports.
This recovery works very well and is tactil!
MIUI_Recovery_2.05_aries_beta, http://www63.zippyshare.com/d/40885846/6809583/MIUI_Recovery_2.05_aries_beta.zip
Installation, change MIUI_Recovery_2.05_aries_beta.zip by update.zip
Then install update.zip via recovery
zelendel said:
There is no kernel source code there. it is only the patchs for makeing ports.
Click to expand...
Click to collapse
And what about this? https://github.com/mitwo-dev/mi2_kernel
May be now we will get a Xiaomi forum here??????????? :fingers-crossed:
Dikks said:
And what about this? https://github.com/mitwo-dev/mi2_kernel
May be now we will get a Xiaomi forum here??????????? :fingers-crossed:
Click to expand...
Click to collapse
We will see what happens. They have alot to make up for, This is a step in the right direction for sure. There also has to be enough development to need a set forum for it. Only time will tell if they will make up for past sins.
Here is the kernel source for:
General Mobile Discovery Elite
Gionee Elife E7
These two devices using the same kernel source. You should use the defconfig from your own device to compile and use it with shared source.
Source link: http://www.burakgon.com/kernel-sources-for-general-mobile-discovery-elite-and-gionee-elife-e7-is-here/
Have fun while modifying!
XDA:DevDB Information
Gionee Elife E7 - General Mobile Discovery Elite Kernel Sources, a Kernel for the GiONEE Elife E7
Contributors
burakgon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2014-04-01
Created 2014-04-01
Last Updated 2014-04-05
Thanks a lot burakgon. I knew you were the real deal! Can you please post your ROM as well which is used in discovery mobile? And your flash tools which you promised to release as well?
[OFF TOPIC]
@burakgon Sir i Need General Mobile Discovery Kernel Source... You Made ATOM ROM Having ATOM Kernel For General Mobile Discovery Which Means You Have its Kernel Sources... i Tried Kernel Sources Released By FLY For its Fly-IQ4410 But Those Sources Are Not Complete Lots Of Drivers Are Missing And There is No Hope From Other Rebranded Devices... its An Humble Request Sir
Sorry To Disturb You Here...
Thank You very very much
let my exams complete
i will port cm
if you can provide device tree it will be awesome
yasirmujtaba said:
if you can provide device tree it will be awesome
Click to expand...
Click to collapse
I will try
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
icoolguy1995 said:
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2706689
burakgon said:
I will try
Click to expand...
Click to collapse
hey burakgon did you got correct sources from gionee
i heard you were talking to gionee support for problems with kernel sources
pls reply
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
GTARaja said:
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
Click to expand...
Click to collapse
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Ravikirancg said:
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Click to expand...
Click to collapse
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
GTARaja said:
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Click to expand...
Click to collapse
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
dhirajranger said:
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
Click to expand...
Click to collapse
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Ravikirancg said:
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Click to expand...
Click to collapse
Missing dt.img??
Sent from my ST25i using Tapatalk
AnoopKumar said:
Missing dt.img??
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
They use some dtb.img.......
Have a look at dtb.img method
Sent from my Discovery Elite using XDA Premium 4 mobile app
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
Ravikirancg said:
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
Click to expand...
Click to collapse
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
AnoopKumar said:
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
yes I did that.. and as you mentioned, I get a white screen.. actually, my kernel itself didnt compile.. but I had some dts files and built a dt.img out of it.. if you built a stock kernel, mind sharinng your dt.img?
MOTOROLA UTILITY BY THEREALDUFF1
View https://www.youtube.com/watch?v=6DdZhVae_p0 to see how I created this program !
Please like and subscribe to my youtube channel to encourage me to create more tools for the members of xda ! I really really appreciate it
This is a GUI based program, which I have started programming in python.
Unlike other tools, this one is specifically made for the Motorola G3.
This entire tool is foolproof, so if you think you may brick your device when flashing TWRP, or stock rom by typing the wrong command, this is the place to be!
All of the tools are included in the program, including the TWRP.img file, and ADB and Fastboot tools. The Motorola drivers are inside the zip, so you don't have to go searching for them !
I have updated Motorola Utility, to be able to work with marshmallow perfectly. V6.2 is uploaded now and is avalible at http://forum.xda-developers.com/devdb/project/dl/?id=17073
Lollipop Version Available In Downloads Section !
Features
-- Marshmallow Compatible
-- Moto G 2015 Specific
-- Roots Your Device
-- Flash TWRP
-- Flash Custom Roms ( Coming Soon !)
-- Flash Stock Rom
-- Safely Upgrade Your Device To Marshmallow (Coming From Lollipop Or Marshmallow Custom Rom)
-- Push Modded Zips To The Device(Coming soon to Motorola Utility Marshmallow !)
-- Lock The Bootloader
-- Troubleshoot Your Device For Problems (Currently In My Beta Version Of The Tool)
Information
This program is currently stable, and only finished and beta features are in the program.
If you would like to contribute to this project, feel free to drop me a message, or email me at [email protected]
In one of the comments, I have posted a screenshot of the program, if anyone would like to see it running
Prerequisites
-- Python 3.4
DOWNLOAD
V6.3: http://forum.xda-developers.com/devdb/project/dl/?id=17180
XDA:DevDB Information
[UTILITY][6.0][5.0]Motorola Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Stable
Stable Release Date: 2016-02-22
Created 2015-12-15
Last Updated 2016-03-12
This seems to be amazing. Congratulations!
Where is download link?
Yousvel said:
This seems to be amazing. Congratulations!
Where is download link?
Click to expand...
Click to collapse
Thanks so much !
Sorry, i uploaded the file , but it is not currently showing.
Il put the link in the description
therealduff1 said:
Thanks so much !
Sorry, i uploaded the file , but it is not currently showing.
Il put the link in the description
Click to expand...
Click to collapse
No problem. As you know, xda doesn't accept place holder.
Yousvel said:
No problem. As you know, xda doesn't accept place holder.
Click to expand...
Click to collapse
Does the link show now on your side?
If it does , please to reply with your opinions on the program, as i would greatly appreciate your opinion. Open toolkit.py first, as that is the main program
Please take into account that this is a very early version of the program , and does not include all of the features in the description. This is a start point !
I am also 15 yrs old, so I have alot of time on my hands to work on this
therealduff1 said:
Does the link show now on your side?
If it does , please to reply with your opinions on the program, as i would greatly appreciate your opinion. Open toolkit.py first, as that is the main program
Please take into account that this is a very early version of the program , and does not include all of the features in the description. This is a start point !
I am also 15 yrs old, so I have alot of time on my hands to work on this
Click to expand...
Click to collapse
The download link is up. Good job bro!
Very nice job dude... This was the application I eas waiting for... But does it unlocks bootloader?
Will you be able to root by booting to TWRP vice flashing boot to the G3?
Congrats with an end product. ?
I understand the handiness of such tools, but I've never been a fan of these GUI tools. Ultimately, the tool ends up coddling the new user and allows the lazy, support leech-type users to remain lazy and not learn what they're really doing.
Look at the support threads for Wug's Nexus toolkit as a great example.
Sent from my MotoG3 using Tapatalk
mkmandar123 said:
Very nice job dude... This was the application I eas waiting for... But does it unlocks bootloader?
Click to expand...
Click to collapse
Not yet, but it will be able to in the very near future
Please click thanks to show you like the program
therealduff1 said:
Not yet, but it will be able to in the very near future
Please click thanks to show you like the program
Click to expand...
Click to collapse
Waiting eagerly for it.....
nikon120 said:
Congrats with an end product.
I understand the handiness of such tools, but I've never been a fan of these GUI tools. Ultimately, the tool ends up coddling the new user and allows the lazy, support leech-type users to remain lazy and not learn what they're really doing.
Look at the support threads for Wug's Nexus toolkit as a great example.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I understand where you are coming from completely about lazy tech people , but this tool is intended for people who don't really know what they are doing , or don't want to risk bricking their phone in the flash progress.
therealduff1 said:
I understand where you are coming from completely about lazy tech people , but this tool is intended for people who don't really know what they are doing , or don't want to risk bricking their phone in the flash progress.
Click to expand...
Click to collapse
A don't a disagree a think it is a good tool and people who are using it might not know what a computer is me personally try to do stuff my own but we all need help from time to time.
nikon120 said:
Congrats with an end product. ?
I understand the handiness of such tools, but I've never been a fan of these GUI tools. Ultimately, the tool ends up coddling the new user and allows the lazy, support leech-type users to remain lazy and not learn what they're really doing.
Look at the support threads for Wug's Nexus toolkit as a great example.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I mostly agree, I appreciate that someone makes a tool like this, especially a 15 year old, but a certain niche of people are going to require being spoon fed even if the answer is in front of their face. I've said all along that a large majority of the people that have to get the latest Android and root it are doing it because everyone else is.
Screenshot
I have attached a screenshot of my program
therealduff1 said:
MOTOROLA UTILITY BY THEREALDUFF1
This is a GUI based program, which I have started programming in python.
Unlike other tools, this one is specifically made for the Motorola G3.
This entire tool is foolproof, so if you think you may brick your device when flashing TWRP, or stock rom by typing the wrong command, this is the place to be!
All of the tools are included in the program, including the TWRP.img file, and ADB and Fastboot tools.
Features
-- Moto G 2015 Specific
-- Roots Your Device
-- Flash TWRP
-- Flash Custom Roms
-- Flash Stock Rom
-- Push Modded Zips To The Device
-- Lock The Bootloader
-- Troubleshoot Your Device For Problems
Information
This program is not entirely finished, and some of the features above are not currently functional.
If you would like to contribute to this project, feel free to drop me a message, or email me at [email protected]
In one of the comments, I have posted a screenshot of the program, if anyone would like to see it running
Prerequisites
-- Python 3.4
XDA:DevDB Information
Motorola Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Testing
Created 2015-12-15
Last Updated 2015-12-16
Click to expand...
Click to collapse
If anyone thinks of a feature that could be added, please do 'feature request' it, and Il be happy to do my best to add it for you
What would people think about mobile custom rom installers , which would wipe dalvik and cache , factory reset etc. ,and then install the rom for you ?
Maybe even make a backup on the job
therealduff1 said:
What would people think about mobile custom rom installers , which would wipe dalvik and cache , factory reset etc. ,and then install the rom for you ?
Maybe even make a backup on the job
Click to expand...
Click to collapse
Good idea! That would help some noobs not to brick their phone.
By the way , you might want to put the adb and fastboot tools from version 1 of my program into version 2 , if version 2 is what you want to use . sorry about the problem , I just forgot to adb and fastboot in the zip
A think it's great what you are doing m8t am going to wait till u have a working sample then a will test it for u
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
therealduff1 said:
What would people think about mobile custom rom installers , which would wipe dalvik and cache , factory reset etc. ,and then install the rom for you ?
Maybe even make a backup on the job
Click to expand...
Click to collapse
Excellent idea!!