Related
Here is my another question hope xda dont mind
I am using rooted official stock version of 2.3 on my phone (as for now coz miui not working for me) now i want to over clock it to 1.4 ghz like of tj_style custom rom Rc2
Now the real question is ... is it really possible... coz setcpu app only provides max of 1024 mhz...
kshitij_bhatt said:
Here is my another question hope xda dont mind
I am using rooted official stock version of 2.3 on my phone (as for now coz miui not working for me) now i want to over clock it to 1.4 ghz like of tj_style custom rom Rc2
Now the real question is ... is it really possible... coz setcpu app only provides max of 1024 mhz...
Click to expand...
Click to collapse
It is possible.
For this extract ramdisk from your boot.img and create a new boot.img using DoomKernel's kernel.
Follow these steps:
You will need to extract your boot.img by putting your phone in download mode and copy boot.img file from fih/image folder.
Follow this guide: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
to unpack your boot.img. Then copy your boot-ramdisk.gz file in separate folder (lets say work/).
Download DoomKernel (available in download section)
Extract boot.img from zip file. Follow same above guide to extract DoomKernel-####-kernel and DoomKernel-####-ramdisk.gz. Copy DoomKernel-####-kernel in same work folder.
Now again follow above guide to pack the boot.img.
Beware, while packing using mkbootimg command you will need to change the arguments.
For our device a sample command for creating boot.img is as follows:
Code:
./mkbootimg --kernel DoomKernel-####-kernel --ramdisk boot-ramdisk.gz --cmdline "console=ttyMSM1 androidboot.hardware=qcom" --base 0x00200000 --pagesize 4096 --output boot.img
Please make necessary changes to file names in above command.
Now open DoomKernel.zip (update zip) which you have downloaded. And add this newly created boot.img in the archive by replacing older boot.img.
Now you are ready to flash this update zip using CWM recovery.
(If you are stuck at boot screen or if it shows charging battery icon while booting instead of android splash image then you have not followed these steps correctly. Please re-do everything. If still stuck then post here. )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Napstar said:
It is possible.
For this extract ramdisk from your boot.img and create a new boot.img using DoomKernel's kernel.
Follow these steps:
You will need to extract your boot.img by putting your phone in download mode and copy boot.img file from fih/image folder.
Follow this guide: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
to unpack your boot.img. Then copy your boot-ramdisk.gz file in separate folder (lets say work/).
Download DoomKernel (available in download section)
Extract boot.img from zip file. Follow same above guide to extract DoomKernel-####-kernel and DoomKernel-####-ramdisk.gz. Copy DoomKernel-####-kernel in same work folder.
Now again follow above guide to pack the boot.img.
Beware, while packing using mkbootimg command you will need to change the arguments.
For our device a sample command for creating boot.img is as follows:
Code:
./mkbootimg --kernel DoomKernel-####-kernel --ramdisk boot-ramdisk.gz --cmdline "console=ttyMSM1 androidboot.hardware=qcom" --base 0x00200000 --pagesize 4096 --output boot.img
Please make necessary changes to file names in above command.
Click to expand...
Click to collapse
cant he just flash the kernel from cwm recovery??
mysteriousboy87 said:
cant he just flash the kernel from cwm recovery??
Click to expand...
Click to collapse
this is TJ's kernel flashable via recovery, enjoy
mysteriousboy87 said:
cant he just flash the kernel from cwm recovery??
Click to expand...
Click to collapse
As far as I know, just flashing a boot.img developed for some other ROM is not a stable way to do it.
Each ROM has there specific init.rc commands, specific services, specific binary files etc. which sets up the device while booting for that ROM. And these all files are there in ramdisk.gz file. Though, just flashing DoomKernel.zip (which is build using Andro-ID ramdisk file) has worked for our stock GB roms but this may not be the case for all ROMs.
[Essentially Andro-ID was build using official GB rom itself, so it might have worked.]
The steps mentioned above are most generic, unless your kernel has been extensively modified (Like it was the case for our Cyanogenmod/MIUI port kernels )
P.S. Sorry, I had forgotten about flashing part of newly created boot.img. Edited my original post.
OP, Just flash the DoomKernel from CWM on stock, nothing bad will happen, using since long time and you can OC upto 1.7ghz without any problems (though not recommended so high) but you can easily OC upto 1.4ghz.
What Napstar has told you is technically right and good if you want to learn on your own but you always don't need technically right solutions to work in life For me DoomKernel works on Stock WellCom without any problems and I use it at 1.4ghz constantly without any overheat problems
Napstar said:
It is possible.
For this extract ramdisk from your boot.img and create a new boot.img using DoomKernel's kernel.
Follow these steps:
You will need to extract your boot.img by putting your phone in download mode and copy boot.img file from fih/image folder.
Follow this guide: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
to unpack your boot.img. Then copy your boot-ramdisk.gz file in separate folder (lets say work/).
Download DoomKernel (available in download section)
Extract boot.img from zip file. Follow same above guide to extract DoomKernel-####-kernel and DoomKernel-####-ramdisk.gz. Copy DoomKernel-####-kernel in same work folder.
Now again follow above guide to pack the boot.img.
Beware, while packing using mkbootimg command you will need to change the arguments.
For our device a sample command for creating boot.img is as follows:
Code:
./mkbootimg --kernel DoomKernel-####-kernel --ramdisk boot-ramdisk.gz --cmdline "console=ttyMSM1 androidboot.hardware=qcom" --base 0x00200000 --pagesize 4096 --output boot.img
Please make necessary changes to file names in above command.
Now open DoomKernel.zip (update zip) which you have downloaded. And add this newly created boot.img in the archive by replacing older boot.img.
Now you are ready to flash this update zip using CWM recovery.
(If you are stuck at boot screen or if it shows charging battery icon while booting instead of android splash image then you have not followed these steps correctly. Please re-do everything. If still stuck then post here. )
Click to expand...
Click to collapse
workign out lets try this
too much technical gonna first try doom's kernal or tjstyle
---------- Post added at 02:58 PM ---------- Previous post was at 02:39 PM ----------
paarkhi said:
OP, Just flash the DoomKernel from CWM on stock, nothing bad will happen, using since long time and you can OC upto 1.7ghz without any problems (though not recommended so high) but you can easily OC upto 1.4ghz.
What Napstar has told you is technically right and good if you want to learn on your own but you always don't need technically right solutions to work in life For me DoomKernel works on Stock WellCom without any problems and I use it at 1.4ghz constantly without any overheat problems
Click to expand...
Click to collapse
Forget it i m back on tj_style rc2 ... with minor adjustments for myself and now aal is well
Napstar said:
It is possible...
Click to expand...
Click to collapse
Will this work with MIUI rom?
paarkhi said:
OP, Just flash the DoomKernel from CWM on stock, nothing bad will happen, using since long time and you can OC upto 1.7ghz without any problems (though not recommended so high) but you can easily OC upto 1.4ghz.
What Napstar has told you is technically right and good if you want to learn on your own but you always don't need technically right solutions to work in life For me DoomKernel works on Stock WellCom without any problems and I use it at 1.4ghz constantly without any overheat problems
Click to expand...
Click to collapse
Thanx i updated doom's kernel and as for now its working fine for me bt ya i too m not taking the risk of 1.9 ghz overclock
Is it possible to use DoomKernel on other phone, like U8800 Pro? It's also on MSM8255
DTSpawn said:
Is it possible to use DoomKernel on other phone, like U8800 Pro? It's also on MSM8255
Click to expand...
Click to collapse
i think no... we cant port as all the phones are of diff class and specifications... so it might jst not possible
kshitij_bhatt said:
i think no... we cant port as all the phones are of diff class and specifications... so it might jst not possible
Click to expand...
Click to collapse
No its not possible to flash it as is. We would need to port it by using that device's kernel source, which is different for different devices.
avi_wizard said:
No its not possible to flash it as is. We would need to port it by using that device's kernel source, which is different for different devices.
Click to expand...
Click to collapse
Do you know what we can do with miui for overclocking .? i wanna work out on that.. coz overclocked miui might work well then anyother usual android
i think 1.4 is good enough... but ram is very low 349mb. but only 194 available anyway to inc that.
bandukia said:
i think 1.4 is good enough... but ram is very low 349mb. but only 194 available anyway to inc that.
Click to expand...
Click to collapse
havn't found any way yet bt on miui custom rom it was showing 512 mb of ram bt dont knw how much it was user available
..
kshitij_bhatt said:
havn't found any way yet bt on miui custom rom it was showing 512 mb of ram bt dont knw how much it was user available
Click to expand...
Click to collapse
didnt you see the running apps section of settings?
bandukia said:
didnt you see the running apps section of settings?
Click to expand...
Click to collapse
naa it was freazing too much so i jst stocked back to my backup
I have been using MIUI Rom continuously since the final release. I am not facing any problems like hanging or lag.
But yes, it does have lesser user available RAM than RC2. But on a day to day use I could not find much difference. Inspite of this I am getting better battery backup than RC2.
I think I am going to stick with this ROM until a CyanogenMod ROM is released by Tj_Style
avi_wizard said:
I have been using MIUI Rom continuously since the final release. I am not facing any problems like hanging or lag.
But yes, it does have lesser user available RAM than RC2. But on a day to day use I could not find much difference. Inspite of this I am getting better battery backup than RC2.
I think I am going to stick with this ROM until a CyanogenMod ROM is released by Tj_Style
Click to expand...
Click to collapse
then i think u havnt tested the camera and other issues... even after uninstalling gtalk there are certain loose points in miui ...
bt i frequently facng problem of reboot even in final version of miui.. by tj style
sent from my Spice MI-410 XDA Premium
I have installed Cyanogenmod 7.1 and modified my bootanimation. I would like to also modify my bootloader screen, the first screen that appears just after the phone boots. Please help on t this topic! Thanx in advance!
Well that's not as easy as changing the bootanimation.... Cause i think you need to build your own kernel.
Thanx! Could you please make or modify a kernel for the cyanogenmod 7.1 that I'm using. I'm pretty new to this android development, all I know is how to root, change bootanimation, and other basic things. Thanx in advance!
Ya kernel...read it can be changed in the param.lfs without having to build a kernel. Not sure how true this is in the case of mini.
What do I have to read and edit? And where can I find this param.lfs? Thanx in advance dude!
I replies on your other thread in Galaxy Mini General. Try modifying TASS.rle in root folder. I don't know if you need to unpack-then-repack your boot.img though.
Edit :
Since this "TASS.rle" doesn't exist in CM7 update zip file, then it means you do have to unpack your boot.img, open the ramdisk folder then edit the extracted TASS.rle" using image editor or something. I never modified TASS.rle so I don't know exactly how to do it.
If you're using Windows, you can use dsixda kitchen+custom cygwin package+Java Dev Kit to do the unpack+repack. It's somewhere in xda.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Thanx a lot dude! But are you sure it'll work? I'll try it out, but is there any simpler method than this. Some way that I can modify it using my phone itself? By the way are you using cyanogenmod 7.2 RC 3 by squadzone? How is it? Please give the link too... thanx in advance!
Like I said, I never modified TASS.rle so I have no clue if it will work or not. I did unpacked and repacked boot.img several times using dsixda kitchen and they worked.
I don't know if easier method exist, so I only suggest what I know from browsing.
It looks like in order to do what you want, several steps are needed :
1. Unpacking your boot.img into zImage file (kernel) and ramdisk folder.
Anything inside ramdisk.folder will be flashed into your system partition each time you boot your device. Examples are init.rc, default.prop and TASS.rle. You can do whatever you want with these files, say modifiying their contents, but the changes only persist as long as you do not boot your phone, which will restore them back to initial state as I explained above.
2. Converting TASS.rle found inside ramdisk folder into editable format such as PNG
3. Modifying the converted PNG in point 2 (using Photoshop or other app)
4. Re-converting the modified PNG from point 3 back into RLE format
5. Re-packing (compiling) zImage file and ramdisk folder (having modified TASS.rle from point 4) back into boot.img
6. Flashing boot.img from point 5 into your phone.
To make it short, you need to learn how to :
1. Unpack and repack boot.img, which you can do using dsixda kitchen from here : http://forum.xda-developers.com/showthread.php?t=633246
2. Converting RLE to PNG and vice versa. More info here : http://forum.xda-developers.com/showthread.php?p=20128066
3. Flashing boot.img into phone. You can compress your boot.img into TAR (type this in cygwin shell window "tar -cf boot.img.tar boot.img" and flash it using ODIN with one package option or you can create a flashable zip file.
CM 7.2 RC3 works great for me, better than RC2; but that's my personal judgement and there's a chance you will not agree with me after you try it.
Head over to CM 7.2-RC3 by squazone for download link.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.
roofrider said:
@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.
Click to expand...
Click to collapse
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
distan7 said:
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Thanks.
I have Ubuntu on a vm
And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
distan7 said:
And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Ya...but I didn't try cpio to extract ramdisk..simply clicking it mounted the ramdisk and it's contents were visible...I wonder if I make any change and unmount it will be saved or not?! Then no need to gzip and cpio
Thanx guys! roofrider and distan7 for all your help and support! If I had a bank account, I would have donated by now, but since I don't all I can do is click the thanks button! Thanx a lot dudes!
You're welcome mate
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
I've attached the tass.rle converted to tass.png thanks to ketut.
but this is only one of the 2 images that appear while booting.
I have to dump the stl6 to find the other i think...but dumping stl5 bricks the phone (stepph) so a little nervous...but i might give it a try.
edit: no harm done.
but stl6 had nothing....anyone got any ideas?
the .jpg or whatever is hidden somewhere, at least that is how it is for galaxy s variants.
Before everyone starts flaming me and trying to kill me for being such a noob, i would like to say that i'm a teen and a noob.
ANYWAYS, i got bored and decided to have a go at porting Firefox OS to the Optimus 2X. After figuring out how to make a flashable zip out of .img's, I tested a bit. Unfortunately ADB doesnt work and I don't know how to do live kernel debugging.
What works: Kernel
What doesn't work: everything else
Source code: http://github.com/JordanRulz
Download:
First Semi-working attempt: http://d-h.st/juX (not a flashable zip)
2nd attempt: link on http://jordanrulz.tk/ (flashable)
3rd attempt (current): http://d-h.st/0We(flashable)
Turn signature verification off before flashing
BUILD INSTRUCTIONS (still doesn't work, but for anyone who thinks they might have the answer, go right ahead)
1.
Code:
git clone http://github.com/JordanRulz/B2G.git
2.extract a cm9 rom to B2G/my_device_backup
3.cd to the B2G directory and
Code:
ANDROIDFS_DIR=my_device_backup ./config.sh p990
and wait for the code to download. This has a good chance of failing because repo and git are stupid.
4.
Code:
./build.sh
5.edit core/sysroot/init.rc so that it imports init.p990.rc
6.go to line 98 of build/core/Makefile and change the build fingerprint to something acceptable by the build system
7.go online and find a wpa_ctrl.h and put it in hardware/libhardware_legacy/wifi/libwpa_client/wpa_ctrl.h
8.copy libcamera.so and libwpa_client.so from a cm9-based rom to out/target/product/p990/obj/lib/
9.it should turn out boot,img, system.img, a system folder, userdata.img, a userdata folder, etc. with adaptations, you should be able to craft a flashable zip out of the folders.
Please hit donate if you feel my work is worth donating to.
Good effort bro!
Way to go buddy.... Expecting this Rom for our beloved Optimus 2x. (me too a noob cant help much)..
Thanks and wish u best of luck..
ahahaha, great work! bring to the old O2X a new system!
Interesting tread, I'll look at the files. Let's hope this will be a cooperative tread to make this
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
nicholaschw said:
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
Click to expand...
Click to collapse
doesn't work. "invalid image file"
i think probably you can pm any recognised dev's for help....if you post a thread here i dont think anybody will try to help....you can pm the dev's like tonyp, harsh, carburano or anyone and you can ask for help in packaging and later on continue with your development....just an idea....:good:
good stuff man., were not the flaming community of yester year
This is getting really frustrating, after restarting multiple times and over 10 failed attempts. I have forked all the repos to my github so that all that want to help are able to do so. http://github.com/JordanRulz
Hello everyone. It's for new bl or old bl? Thanks
Sent from my LG-P990 using xda app-developers app
I say it´s for the old BL, if i don´t read the updater-script inside completly wrong.
It's for old bl
Sent from my LG-P990 using xda app-developers app
build instructions (for a non-working build, but still useful for f*cking around) were added.
JordanRulz said:
build instructions (for a non-working build, but still useful for f*cking around) were added.
Click to expand...
Click to collapse
:good::good:
Don't know if you're going at it the right way but good luck, and you should contact another dev just to make sure at least that you're on the right path.
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
JordanRulz said:
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
Click to expand...
Click to collapse
I hope if you develop successful, it will have 1 for SU660 :victory:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob report on f.b.i
alexcyb said:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob
Click to expand...
Click to collapse
Its not a "virus java drive", its a hidden bitcoin miner. If u use a secure browser like Firefox, it will prompt you before running it.
Sent from my LG Optimus 2x using xda app-developers app
Someone has already Deodexar the Stock Rom Zenfone Laser?
Would very much welcome a Tutorial,
help at all ..
Mandrakerj said:
Someone has already Deodexar the Stock Rom Zenfone Laser?
Would very much welcome a Tutorial,
help at all ..
Click to expand...
Click to collapse
use superr kitchen, linux based.
http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
for windows based
http://forum.xda-developers.com/showthread.php?t=2639400
every thread has very good tutorial, hope it will help you. :good:
Well I can not do with these two applications because not Linux but Windows use. And then it would be nice a file ready update-binary and compatible updater-script to instalart then Deodex the device.
not do with these two applications because not Linux but Windows use. And then it would be nice a file ready update-binary and compatible updater-script to instalart then Deodex the device.
Someone has already Deodexar the Stock ROM and install the device?
Can anyone help ??
I will deodex the stock ROM later when I get back. I currently have kitchen running on my Mac.
Rizzed said:
I will deodex the stock ROM later when I get back. I currently have kitchen running on my Mac.
Click to expand...
Click to collapse
I also needed to Zenfone selfie ZD551KL
Alright. I will try to get it done by today..
*Link deleted*
FOR ZD551KL VARIANTS ONLY. Any attempt to flash this ROM on other ZenFone 2 series' variants would result in getting stuck at the manufacturer's logo. In that case, you would need to flash the stock ROM back to get it back to a working condition.
I do not have the ZD551KL variant of the ZenFone 2 Selfie with me now, thus, I can't test it out. Please do report back the results after flashing, and inform me immediately if "errors" or "signals" appear upon installation. Thanks!
EDIT: If this works out fine, I will be doing the same for the other variants of the ZenFone 2 series and then place them all into another thread!
this is for the ze551kl?
install from root with twrp?
rooted?
thanks
beenkenobee said:
this is for the ze551kl?
install from root with twrp?
rooted?
thanks
Click to expand...
Click to collapse
Nope, only for ZD551KL devices. I just found out that there's essentially no point in removing the verification checks, as even if it installs on the other variants, it would fail to boot as the kernel files are different. That is, unless you are willing to flash the boot.img yourself, which requires downloading the original ROM, extracting, and using the fastboot commands "fastboot flash boot boot.img".
Following up on your other questions, no. No root is required to install this ROM, only a custom recovery, such as TWRP or CWM. The ROM is also NOT pre-rooted (well, I need to learn HOW first.)
I could compile a deodex-ed ROM for you later. Though I would suggest you to wait out a while for the people with the ZD551KL variants to test it out first and see if the Android Kitchen's modifications really worked.
As for now, I will leave the download file as it is (no verification checks). I will update it tomorrow, together with the compiling for the deodex-ed ROM for ZE551KL variants (as well as others, if time permits).
Rizzo, what application you are using to Deodexar the Rom? Here I only use Windows 7 x64
Rizzed said:
https://drive.google.com/file/d/0B6QXDUz9wzc9dWIyTUJ1a05TMzA/view?usp=sharing
FOR ZD551KL VARIANTS ONLY. Any attempt to flash this ROM on other ZenFone 2 series' variants would result in getting stuck at the manufacturer's logo. In that case, you would need to flash the stock ROM back to get it back to a working condition.
I do not have the ZD551KL variant of the ZenFone 2 Selfie with me now, thus, I can't test it out. Please do report back the results after flashing, and inform me immediately if "errors" or "signals" appear upon installation. Thanks!
EDIT: If this works out fine, I will be doing the same for the other variants of the ZenFone 2 series and then place them all into another thread!
Click to expand...
Click to collapse
Rizzo, I still do not understand anything.
This Stock ROM that you made available for download, it would be for selfie ZD551KL? What would be the version of this Stock Rom? She has not estarai Deodexada, correct? What do I do here with her in my ZD551KL? Install from sdcard or would the TWRP? I would like to learn how to Unzip the System Image Stock Rom ZD551KL. I do not know how to do this. How can I help you?
Sorry for the confusion guys.... I will be testing it out on my ZE550KL first and see if the tool works properly. If it does, I will help to de-odex the ZD551KL variants (and possibly others too) and post it on an entirely new thread.
Rizzed said:
Sorry for the confusion guys.... I will be testing it out on my ZE550KL first and see if the tool works properly. If it does, I will help to de-odex the ZD551KL variants (and possibly others too) and post it on an entirely new thread.
Click to expand...
Click to collapse
Hi there friend thank you for your help. I will wait for the results with your Laser ZE550KL. I'm hoping that everything goes well. So I will wait for the procedure for Variant selfie ZD551KL because this is what I need right now.
Alright! Everything appears to be working... I have not tried flashing yet, but, it should be able to boot up fine.
I've deodexar the Stock rom selfie ZD551KL. I just can not install because of the error in updater-script.
Mandrakerj said:
I've deodexar the Stock rom selfie ZD551KL. I just can not install because of the error in updater-script.
Click to expand...
Click to collapse
In that case, could you upload the updater-script so that I could have a look at it?
So my friend..
In fact I do not even have the original file to the selfie ZD551KL.
What I was tested in a template JoelDroidLollipopBatchDeodexer the page.
This man did not work ...
I found no script created for Deodexar Rom in selfie ZD551KL.
Here for you ..http://www.mediafire.com/download/84m7v0qubav1m32/InstallerTemplate.zip
Rizzed said:
In that case, could you upload the updater-script so that I could have a look at it?
Click to expand...
Click to collapse
So my friend Rizzed..
In fact I do not even have the original file to the selfie ZD551KL.
What I was tested in a template JoelDroidLollipopBatchDeodexer the page.
This man did not work ...
I found no script created for Deodexar Rom in selfie ZD551KL.
Here for you ..http://www.mediafire.com/download/84...erTemplate.zip
Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official. Officially supported device get automatic builds which are made available at dl.twrp.me/<device_codename> at each major release. Thank you.
Download : My Website
XDA:DevDB Information
TWRP for HOT 2, Tool/Utility for the Infinix HOT 2
Contributors
MSF Jarvis, Nonta72
Version Information
Status: Testing
Created 2016-04-13
Last Updated 2016-04-13
MSF Jarvis said:
Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official.
Click to expand...
Click to collapse
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.
Nonta72 said:
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.
Click to expand...
Click to collapse
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.
MSF Jarvis said:
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.
Click to expand...
Click to collapse
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.
Nonta72 said:
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.
Click to expand...
Click to collapse
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.
MSF Jarvis said:
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.
Click to expand...
Click to collapse
Sure
Let's make it work! :highfive:
Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.
Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
In 15 minutes, there will be twrp-3.0.2-2 available there. If you're interested to see what I did to it, check the commits
This one has logcat enabled as well, so you may wanna help me that way. I don't do WhatsApp, so you may want to hop on to #team-redux on http://webchat.freenode.net rather.
Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:
MSF Jarvis said:
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:
Click to expand...
Click to collapse
Nonta72 said:
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.
Click to expand...
Click to collapse
Another test build is up : 3.0.2-2
MSF Jarvis said:
Another test build is up : 3.0.2-2
Click to expand...
Click to collapse
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...
Nonta72 said:
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...
Click to expand...
Click to collapse
Maybe I should, but where's the similarity?
MSF Jarvis said:
Maybe I should, but where's the similarity?
Click to expand...
Click to collapse
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.
Nonta72 said:
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.
Click to expand...
Click to collapse
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor
Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)
RendyAK said:
Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)
Click to expand...
Click to collapse
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??
MSF Jarvis said:
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor
Click to expand...
Click to collapse
Because MT6580 is a recent version of the MT6582. Forget the "2" that became "0" at the end. The MT6580 is even faster than the MT6582 and can match some MT6592 (with 1GB RAM). I saw a 33,000+ antutu on a MT6580 (with 2GB RAM) and overclocked (yes! overclocked, idk how but they said so).
MSF Jarvis said:
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??
Click to expand...
Click to collapse
Sir, you're talking about the messed up ramdisk. In fact, there are many builds, the one you have seen have many bugs probably because of the messed up rcs.
The only recovery that works good for me is the one made by Ovatek. I made few commits to my github including the fstab file changes you suggested...
Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia
Nonta72 said:
Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia
Click to expand...
Click to collapse
Actually speaking, the OEM for the MT6582 device went with naming the device 'sprout', which I vehemently oppose, to avoid confusion. The stock boot.img's ramdisk also contains files according to the 'sprout' nomenclature. I took the sprout4 device tree, updated all *.rc's from the stock marshamallow boot.img and added in a bunch of TWRP flags.
One important thing you most probably already know, Infinix Hot 2 uses a standard MTK boot.img header, while the LAVA Pixelv1 uses an AOSP format, so it can be unpacked using standard tools, while yours requires Carliv's kitchen.