Don't forget to hit that "thanks"/Donate button or check out my APK(s) installer tool found in my signature :0)
Updated to version 1.51.
Added: Conversion of BMP images to ready-to-flash splash files on all 3 systems.
Modified: Graphical layout is now more in sync in all 3 systems.
Modified: All tooltips are now corrected and fully helpful :0)
Hi everyone.
This is a tool written in JAVA for easier flashing of the following partitions:
Radio, hboot/spl, recovery, system, boot, userdata, kernel and splash.
It can do much more, like:
Conversion of 24bit BMP images to ready-to-flash splash files.
Erase/wipe multiple or single partitions.
Reboot device either to system or fastboot.
Print of device info.
Flash of kernel.
Possible to run custom fastboot commands instead of using cmd/shell.
Flash of signed zip files (E.g. fastboot flash zip myzip.zip)
The above(Flash of signed zip) should not to be confused with flashing of custom rom files!
It's only meant for signed HTC roms with complete system layout.
Flash multiple files in one click by using custom folders and tags.
It's basically a GUI over most fastboot commands.
It works for Windows, Linux and Mac.
No need for Android SDK, the jar-file has all needed files bundled!
It's well tested and have more than +10000 users.
It works for all devices which has fastboot :0)
Any feedback is appreciated.
Requirements:
Min 30 % battery!
Engineering hboot/spl OR S-OFF!
Do not reboot or shutdown, if you ever get an error flashing the radio or the hboot/spl!
Ask here for help if it happens!
Instead of having to maintain multiple OPs, i have decided to redirect the OP to the desire forum. It's only the facade and nothing else. All questions and ect regarding the Desire HD will still be on this thread :0)
The tool is the same and will work on any device which have fastboot mode.
LINK:
http://forum.xda-developers.com/showthread.php?t=1193915
nice tool : )
thank you for your work!
Should add zimage partition flashability as well
What do you mean?
zimage = ?
This is Absolutely Best Tool for HDHD! Needs visibility in this forum...
Awesome tool mate, should make things easier for new people
Glad you like it :0)
Nice work
mumilover said:
What do you mean?
zimage = ?
Click to expand...
Click to collapse
kernel mumi
capychimp said:
kernel mumi
Click to expand...
Click to collapse
Ohh... thx O' great rom master :0)
Hope life is treating you well :0)
For the kernel flashing part... the tool is just a graphical interface build on top of the fastboot binary. So i can only do what fastboot can do.... so no kernel flashing or the like..
I think i have milked every thing i could from the fastboot binary :0)
hehe well nice to see your still here mumi, been awhile
good job
thanks for your nice work
capychimp said:
hehe well nice to see your still here mumi, been awhile
Click to expand...
Click to collapse
Some bastards stole my laptop and magic device... so i have busy lately securing my home and changing all my passwords etc...
But i'm hot again.
Flashed new Radio without any problems, great prog.
Thnx
mumilover said:
Ohh... thx O' great rom master :0)
Hope life is treating you well :0)
For the kernel flashing part... the tool is just a graphical interface build on top of the fastboot binary. So i can only do what fastboot can do.... so no kernel flashing or the like..
I think i have milked every thing i could from the fastboot binary :0)
Click to expand...
Click to collapse
Erm, correct me if i'm wrong, but sometime i/we flash the kernel via fastboot.. "fastboot flash zimage zImage"
So, i think, it can be implemented in your tool.. good job anyway..
so if i want to flash a splash image what do I name that as ??, thanks.
vtec303 said:
so if i want to flash a splash image what do I name that as ??, thanks.
Click to expand...
Click to collapse
Normally it's called splash1.nb0 (that's nbZERO).
SAPPH1RE said:
Erm, correct me if i'm wrong, but sometime i/we flash the kernel via fastboot.. "fastboot flash zimage zImage"
So, i think, it can be implemented in your tool.. good job anyway..
Click to expand...
Click to collapse
I DID NOT KNOW THAT... Just to be sure, can anyone confirm that!
If it's confirmed then i will implement it in 2 min :0).... maybe 2.5!
To flash a kernel, you can use
fastboot flash zimage c:\zimage
Sent from my Desire HD using Tapatalk
Thx for the confirmation ( i used Google to double check anyway :0)
I will add it as soon as possible... i cannot test it though :0|
The bastards stole my magic device :0(
Anybody here willing to test ( it will be a piece of cake to make the functionality, i have the code, just have to modify a very small portion). If there is anybody, just post here or pm me :0)
Related
Hello everyone,I'm new here
I have a HTC Magic and update now to CursorSense 0.4
I have viewed many tittle and I like another rom only for HTC Hero
But I heard that If I update the rom for my Magic,the camera will can not work
Can I make a port by my self？
If it is easy for someone,teach me please,very kind of you
……If it is impossible ,tell me please
If I pull some files from CursorSense rom
Then push them to hero rom,can it work ok？
hubo19890319 said:
If I pull some files from CursorSense rom
Then push them to hero rom,can it work ok？
Click to expand...
Click to collapse
I've tried that before, it doesn't work very well.
Download the system.img and boot.img from:
http://forum.xda-developers.com/showthread.php?t=589722
This is the base that I started with.
Then from there you can root the ROM image through an adb shell, install new apps, etc...
Start here for information:
http://forum.xda-developers.com/showthread.php?t=551711
Good luck and happy developing!
thank you very much
I will try it right now
hubo19890319 said:
thank you very much
I will try it right now
Click to expand...
Click to collapse
Oh, and make sure you don't use Windows.
Install Linux on a spare computer, or use VirtualBox.
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
It also seems that this error is caused by the double vibration at the beginning of boot process and was solved once by paipo (see this post) by commenting out the vibration part and rebuilding. But those kernel is outdated and misses some latest features and fixes.
So I did the same as paipo but with the latest kernel from the git repository (as of 19.07.2010, revision d5d0a56fae6df779443a82e2d90b7ec8097cb332). zImage is attached to this post. I'll try to update the kernel from time to time.
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Disabling the vibration and rebuilding the kernel yourself
So how do you do this?
First of all, follow the steps 1 to 4 of Building kernel For Vogue, Kaiser, and Polaris part from this guide to prepare your building environment.
Now you need to open the arch/arm/mach-msm/board-htcpolaris.c file in your favourite text editor.
Search for vibrate word (it was line 1019). You'll see something like this:
Code:
// vibrate
for (i=0; i<2; i++) {
while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
mdelay(75);
}
Remove this part or replace with the following:
Code:
// vibrate
// for (i=0; i<2; i++) {
// while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
// mdelay(150);
// while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
// mdelay(75);
// }
As you can see, all lines now start with two slashes.
Now follow step 5 from the guide, mentioned above. You'll see a menu.
Go to System Type and select Android Optimization accroding to your needs. Then select Exit, than again Exit, then Yes.
Now follow step 6 from the guide. This will take some time. At the end you should see:
Code:
Kernel: arch/arm/boot/zImage is ready
Copy zImage from arch/arm/boot folder to \Storage Card\andboot folder on your device and use it
I update this option in the kernel.
Now double vibration is disable by default.
You are great !!!
leppa said:
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
...
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Click to expand...
Click to collapse
YOU ARE GREAT !!!
THANKS A LOT A LOT A LOT !!!
THIS EVENING I WILL TRY SURELY !!!!!!!
Only a question: Optimized for Eclair is equal to Optimize to FROYO ?
Can I use your zImage to Froyo RLS 11 ?
Thanks in advance.
Bye
This flag now do nothing, so it's indifferent
GGGGGGGGGGGGGGRRRRRRRRRRRRRRRRRREEEEEEEEEEEEEEEEEAAAAAAAAATTTTTTT !!!!!!
I Have Just tested zImage in attached files.
Froyo seems better reactive, more smooth and rock stable.
Thanks a lot ...
When Video Playback will be solved... I will flash immediately Froyo to give a new life to my Cruise!!!
Thanks thanks thanks!
@foxct2005 : you can flash it month ago!
All these problems are only for haret!
l1q1d said:
I update this option in the kernel.
Now double vibration is disable by default.
Click to expand...
Click to collapse
This change isn't yet in the git repository, is it?
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
The attached kernel images work as they did before - with double vibration on boot and "waiting for notbusy" error. To disable the double vibration (and get rid of the error) add board-htcpolaris.no_boot_vibration=1 to default.txt so this line:
Code:
set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
will look like this:
Code:
set cmdline "board-htcpolaris.panel_type=1 [COLOR="Red"]board-htcpolaris.no_boot_vibration=1[/COLOR] ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
Adding this parameter is mandatory if you suffer from "waiting for notbusy" error.
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
leppa said:
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
Click to expand...
Click to collapse
Good idea!
I have long think why developers not added it to the cmdline.
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
DmK75 said:
Good idea!
I have long think why developers not added it to the cmdline.
Click to expand...
Click to collapse
I think, they have much more other, more serious, things to do
michasch said:
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
Click to expand...
Click to collapse
nikiiv said:
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
Click to expand...
Click to collapse
You're welcome
If this patch gets upstream, we will not need to rebuild the kernel every time a new build comes out. I already posted it in the Polaris Android Linux Kernel Development Project thread.
thanks leppa,
i tried the froyo one, but for me doesn't work. last days i used the last dzo one, it worked for 2 or 3 days, and now doesn't work again. the only zimage that works is the 29-04 one, but my battery doesn't like it so much
loscassapalle said:
thanks leppa,
i tried the froyo one, but for me doesn't work.
Click to expand...
Click to collapse
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
leppa said:
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
Click to expand...
Click to collapse
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
loscassapalle said:
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
Click to expand...
Click to collapse
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
leppa said:
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
Click to expand...
Click to collapse
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
the animation problem is strange. the zimage of 29-4 works, the animation ends in a few seconds, but the battery life is very short. the last dzo zimage worked for a couple of days, then i had the same problem after a softreset...and this one is the same...
EDIT: now it works... lol
loscassapalle said:
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
Click to expand...
Click to collapse
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
loscassapalle said:
EDIT: now it works... lol
Click to expand...
Click to collapse
So, it started working?
leppa said:
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
So, it started working?
Click to expand...
Click to collapse
i don't know how to edit the zimage...but now it works...i didn't change anything...
loscassapalle said:
i don't know how to edit the zimage...
Click to expand...
Click to collapse
You don't need to. I was talking about editing default.txt as I described in post 8.
Hello Fire owners!
I open this thread to keep all things of Fire together, only one thread, everything here.
So here we go:
THIS THREAD IS FOR MOTOROLA XT311/XT316/XT317, XT530/XT531, XT532 AND XT611 (aka SMARTFLIP) ONLY. IF YOU HAVE A SIMILAR THREAD, PLEASE PM ME AND PASS ME YOUR POST. LET'S KEEP XDA ORGANIZED!
CWM FOR FIRE XT XT530/XT532, SPICE XT XT531, FIRE XT311, SPICE KEY XT316 OFFICIALLY LAUNCHED
This thread was focused in the 2nd-Init for XT31X and XT530, 531 and 532. For almost six months, we worked patientlly to get the CWM working on our devices. The wait for CWM is OFFICIALLY OVER. In a couple days ago, our friend aweosomeabhijeet found a way to run CWM on Gingerbread. The tutorial (made by himself) will be posted NOW:
Hey Guys
All your wait is over.
Here I'll tell you how to get CWM for Moto Fire XT.
Disclaimer : I'm not responsible for any damage to your phone. I have tried it and finished successfully.
Try only if you know little bit about android.
This is beta version. However, a dev is working on not using a PC to reboot back into system, and is trying to make the installation simplified.
Lot of thanks to andrewidya
Required things
1. Rooted XT
2. Pc
Download these things on your phone:
1. Terminal emulator
2. Busybox(Open it and install)
3. Root browser
4. Pimp my Rom
5. ES file explorer
You can find all of them in the Play Store.
If you have done with it download the attachment.
Now main work.
It is not easy though but I think everyone can do it.
Steps:
1. Extract the attachment and copy it to your sdcard
2. Mount /system as RW.
3. Open Root Browser and copy bootmenu folder from sdcard/XT530 and paste it in /system.
4. Open Pimp My Rom and Add universal init.d support.
5.Create 97bootmenu manually.(For this using ES file explorer is recommended)
Steps:
a.Open /system/etc/init.d
b. Create a file, name it 97bootmenu.
c. Open the file as text
Type:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
d.save the file
6. Change permissions of 97bootmenu to rwx r-- r--
7. Reboot your phone.
Now your phone will start at bootmenu.
Select Recovery>Custom Recovery
PS: If you want to get back the phone to boot normally. Just connect it to PC, open CMD and type
cd path-to-adb.exe
adb shell
rm -R /system/etc/init.d/97bootmenu
exit
adb reboot
I succeeded here's the video:
http://youtu.be/OyHwMqkBArk
Sorry for poor camera quality.
Thanks to all the members.
Special Thanks to:
Gentrylamp for creating bootmenu.
7amdoun for his great knowledge and modding bootmenu for XT530.
andrewidya for correcting me at every point.
Mazen.kh for everything he did.
Mr.Indigo for giving us hopes.
And all other members whom I forgot to mention here.
Click to expand...
Click to collapse
This above quote is the 1ST post of his thread.
THANKS TO HIM AND TO ALL OF THE DEVELOPERS WHO HELPED TO GET THIS.
ROOTING & UNROOTING
You will follow this tutorial if you have 2.3.5 version of Android:
Downloads:
Here are the apps/files needed for Rooting -
1. SuperOneClick 2.3.3.0
2. SUT LR 1.8.2 (Doesn't seem to be working on 64-bit systems)
3. FXX_PR3_NV.xml and NvDefinition.xml [ATTACHED]
Before Rooting:
Prepare your phone by doing the following:
- Go to Settings > Applications > CHECK "Unknown Sources"
- Go to Settings > Applications > Developer > CHECK "USB Debugging" and "Stay Awake"
- Connect your phone via USB, when prompted DO NOT select USB Mass Storage.
- Extract FXX_PR3_NV.xml and NvDefinition.xml from the attached zip file in to a folder
- Now, install SUT LR, run the app
- Select the FXX_PR3_NV.xml [ensure NvDefinition.xml is also in the same folder as FXX_PR3_NV.xml]
- Your phone will restart.
It does NOT erase anything on the phone, since it only patches the ROM.
Rooting:
After the phone restarts, open SuperOneClick and select root. It will take less than a minute to finish.
Click to expand...
Click to collapse
From: Motorola Fire XT / XT-530 / XT-531 ROOTING! - NEW METHOD - [ DEVS NEEDED ] posted by the user jeet.9890427233
Official Motorola SBF Files
Link: www.grupoandroid.com/topic/43248-motorola-firmwares-superthread/
Just copy and paste.
Custom ROMs
None yet.
Custom Recovery
None Yet.
Custom Kernels
None yet.
Applications that you can removeThere are some apps that you can remove, here is the complete list with all apps:
My ROM is VIVO 2.3.5 and can be different in some ROMs.
7x27_FQC or FQC Program= YES, maybe is F actory Q uality C heck or other thing....
AccountAndSyncSettings.apk= NO
ApplicationsProvider.apk= NO - Will brick apps install/uninstall
APR.apk= ?
BatteryManagerAP.apk= YES
BatteryProtect.apk= ?
Bluetooth.apk= NO
BlueToothTestMode.apk= NO
Browser.apk= YES
Calculator.apk= YES
Calendar.apk= NO
CalendarProvider.apk= NO
Camera.apk= NO
CDA.apk= ?
CDASYSTEM.apk= ?
CertInstaller.apk= NO
Contacts.apk= NO
ContactsProvider.apk= NO
DataConnectionWidget= YES
DateTimeSetup.apk= NO
DbgCfgTool.apk= ?
DefaultContainerService.apk= ?
DeskClock.apk= YES/NO
DMClient.apk= NO
DownloadProvier.apk= NO
DownloadProviderUI.apk= NO
DrmProvider= NO
DxDrmApplication= NO
DxDrmPlugin= NO
ECompassCalibration= NO
Email= NO
Facebook_LT= YES
Fallback= NO
FileManager= YES
FM Radio= ?
Gallery3D= YES, but replace with another gallery app
GenieWidget= ?
- THIS LIST WILL BE UPDATED SOON -
Click to expand...
Click to collapse
If you are a DEV our a guy who can provide a ROM for us, please PM me and i will add you in GTalk. If you have a mod or something useful or want to help me, please PM me and i will add you on GTalk. If we get sucess this thread will be updated!
Thread changelog:
- Initial post
- CG2.smg extractor added to the 2nd Post (THANKS TO: Mazen.kh)
- Chainfire 3D support added ( THANKS TO: Overcrasher)
- Thread stopped a lil bit
- Back with some news
- SUPPORT FOR XT530/531/532 (FIRE XT) Added
- SUPPORT FOR XT317 (FIRE in Brazil) Added
- XT317 kernel tested, but didn't work smoothly as 2.2 kernel
- SUPPORT FOR XT611 (aka SMARTFLIP) added
- SUPPORT FOR XT611 DROPED. See more below.
- CWM FOR FIRE DEVICES LAUNCHED BY aweosomeabhijeet
about CG2.smg
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Mazen.kh said:
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Click to expand...
Click to collapse
IT WORKED!
Thanks!
It helps me a lot!
Now my device Works!
Thanks!
Sent from my Xt316
Is there any custom rom for XT316/XT311?
luume said:
Is there any custom rom for XT316/XT311?
Click to expand...
Click to collapse
Unfortunately not yet.. Neither custom recoveries
Mr.Indigo said:
IT WORKED!
Thanks!
Click to expand...
Click to collapse
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Mazen.kh said:
Unfortunately not yet.. Neither custom recoveries
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Click to expand...
Click to collapse
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Mr.Indigo said:
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Click to expand...
Click to collapse
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Mazen.kh said:
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Click to expand...
Click to collapse
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Mr.Indigo said:
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Click to expand...
Click to collapse
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Mazen.kh said:
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Click to expand...
Click to collapse
Some guys tried to do an 2ndInit to maybe try to get CWM work. But didn't worked. A file from the battery (when you turn off the phone and conntect the charger, the big battery icon) was missing. But works without this file.
AND I FOUND WHERE WE CAN ACTIVATE SRS! Is in cda.prop, it's configured to false.
So what happens if i changed the value to true ?
i don't think cda props apply actually i tried to change the value of lock screen support rotation to true and nothing changed.
And Yup i read something about that battery icon too but i didn't understand fully how does that relate to unlocking bootloader
i think the bootloader must get hacked easily since as i see it's a common bootloader in many fones for ex. xt530 xt531 xt532 xt300 xt311 xt316 xt317 or am i wrong ?
If i can test the ROM in my computer (i don't know how to do it), we see if works. And Bootloader it's not the same for every phone series. XT300 executes 2.1 WITH UNLOCKED BOOTLOADER. And XT316 with 2.3.5 WITH THE LOCKED Bootloader.
The SRS file is in the attachments. Just take a look on the 'st line:
BLOCK... I understand that is blocked.
And the battery icon maybe is on a apk or anywhere. We might look better.
EDIT:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Mr.Indigo said:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Click to expand...
Click to collapse
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Mazen.kh said:
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Click to expand...
Click to collapse
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Mr.Indigo said:
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Click to expand...
Click to collapse
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Mazen.kh said:
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Click to expand...
Click to collapse
Maybe... Here is the error they got:
I got this after the flash attempt.
Phone[0000]: Error flashing subscriber unit. Device API error. 0xE002000B Address 0x94C3800 Command: BIN (0xE032300B)
Click to expand...
Click to collapse
I've got from ModMyMobile (M3). They mod and bang! Bricked the device!
But they recovered.
See another error here
The recover is change the FLEX VERSION to please flash please (something like that)
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
kent_lkc said:
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
Click to expand...
Click to collapse
This is cda.prop right?
it has some tweaks like build.prop, if you tried to change the mobile model that appears to the market from build.prop it won't work, but if you change it from cda.prop it will work also it have some other tweaks that i actually don't know what's it's use
And Don't Forget Thanks Button ^^
XT316 bricked
Hello guys, sorry if this is not the best place to post a problem but, this is the only one active discussion about XT316 that i have found, i have this phone with Brazil Claro stock 2.3.3 Gingerbread Android installed, then i have installed the ChainFire3D hoping to have better experience with some games...
But i got a bricked phone... when powering on, the phone shows only the Motorola logo, then a black screen with no response, and continous reboot
I started the phone in recovery mode and tryed to perform a Factory Recover, but no sucess, same with Wipe Cache Partition option, so, what is left to do now is my question...
Well, after doing some testing with this for the last couple days I have had great results. The actual kernel is untouched, since we don't have source yet, but the initramfs has been tweaked to provide proper multitasking capabilities.
Compatible with 1.85 ONLY!
Features:
Insecure (adb always runs as root)
Better multitasking (still sucks, but better)
Init.d Support (run user scripts on boot)
Download:
deprecated
Instructions
Flash from fastboot
Update: I just tested things out with angry birds space, the game will pause and stay in memory like it should, but it will kick all other apps out and cause them to reload.
designgears said:
Well, after doing some testing with this for the last couple days I have had great results. The actual kernel is untouched, since we don't have source yet, but the initramfs has been tweaked to provide proper multitasking capabilities.
This is a beta test, I tested it will standard apps, I have yet to test it with games. Please report what you find!
Compatible with 1.85 ONLY!
Download:
http://www.gigashare.in/91105
Instructions
Flash from fastboot
Click to expand...
Click to collapse
Thanks DG!
have you made this boot.img insecure in the init.rc?
Zarboz said:
Thanks DG!
have you made this boot.img insecure in the init.rc?
Click to expand...
Click to collapse
heh, no, totally forgot about that, meant to.
edit:
just updated the link with one that is
Thanks DG, testing now
EDIT: From preliminary testing it looks like it can handle around 3 small tasks (like a webpage, google music, and gmail) pretty easily. But when you get to 4 it kicks out the oldest task there.
designgears said:
heh, no, totally forgot about that, meant to.
edit:
just updated the link with one that is
Click to expand...
Click to collapse
can't wait for them to let out kernel source i wanna get to building !
this just made my day
adb root
adbd is already running as root
who cares if multitasking works we have a unsecured image to play with now
thanks again and another #win for sure
What device / ROM did you test on?
EDIT: Worked on mine!
Thanks!
What tool did you use to pack / unpack this?
I tired with DSI Kitchen and it only caused no boot. How did you do this?
init.d support?
scrosler said:
What tool did you use to pack / unpack this?
I tired with DSI Kitchen and it only caused no boot. How did you do this?
init.d support?
Click to expand...
Click to collapse
Not sure what tool you are talking about but I had also tried this:
http://forum.xda-developers.com/showthread.php?t=1659584
And I was ending up with a bootloop every time before the animation.
scrosler said:
What tool did you use to pack / unpack this?
I tired with DSI Kitchen and it only caused no boot. How did you do this?
init.d support?
Click to expand...
Click to collapse
waiting for reply as well so we can play with stuff
this is great, i would love to know what you used to unpack it as well and if it does support init.d
rohan32 said:
Not sure what tool you are talking about but I had also tried this:
http://forum.xda-developers.com/showthread.php?t=1659584
And I was ending up with a bootloop every time before the animation.
Click to expand...
Click to collapse
Pretty much the same tool but different. But that exactly what was happening to me too.
I decompiled this boot.img and it doesnt have init.d support. Maybe OP will add it
I am using the same method as dsixda uses in his kitchen to extract it. The build command is a bit different tho.
mkbootimg --cmdline 'console=ttyHSL0,115200,n8' --kernel <kernel path> --ramdisk <ramdisk path> --base 80400000 --ramdiskaddr 81800000
You have to set the ramdiskaddr, and it has to be set after the base or it will be overwritten.
-------------
and multitasking still sucks.. lol, I think we will need kernel source to fix it properly.
designgears said:
I am using the same method as dsixda uses in his kitchen to extract it. The build command is a bit different tho.
mkbootimg --cmdline 'console=ttyHSL0,115200,n8' --kernel <kernel path> --ramdisk <ramdisk path> --base 80400000 --ramdiskaddr 81800000
You have to set the ramdiskaddr, and it has to be set after the base or it will be overwritten.
-------------
and multitasking still sucks.. lol, I think we will need kernel source to fix it properly.
Click to expand...
Click to collapse
Well you got us unsecured boot.img!!!!!!
Going to try your command to see if I can get init.d working... Unless of course you can beat me to it
Thanks DG for deciding to mod for the One X. You and scrosler do awesome work. Two awesome developers on board.
Sent from my HTC One X using XDA
Got init.d support!!!!!!!!!!!!!!!!!!!!!!
Here it is!
Thanks for the help OP!!!!!!!!!
I attached it to this post if you dont want it here I will remove it.
scrosler said:
Got init.d support!!!!!!!!!!!!!!!!!!!!!!
Here it is!
Thanks for the help OP!!!!!!!!!
I attached it to this post if you dont want it here I will remove it.
Click to expand...
Click to collapse
sweet! did you set it up with logwrapper?!
designgears said:
sweet! did you set it up with logwrapper?!
Click to expand...
Click to collapse
No, I just took your boot.img and added modded init.rc. I have to head to work now so I cant play any more but I wnated to try what you told me about the command line parameters and it worked perfect!
Thanks for helping me figure this out. I had been pulling my hair out (what little left I have).
designgears said:
Instructions
Flash from fastboot
Click to expand...
Click to collapse
fastboot flash <imagename> ?
Thank you
nugzo said:
fastboot flash <imagename> ?
Thank you
Click to expand...
Click to collapse
fastboot flash boot imagename.img
nugzo said:
fastboot flash <imagename> ?
Thank you
Click to expand...
Click to collapse
fastboot flash boot <path/to/img>
Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse
No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:
munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it
Sounds definitely awesome!
Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!
munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL
XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!
munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.
New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback
Solved! Will give you soon cm11 in multiboot!
munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:
Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!
Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47
Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?