THIS IS A WORK IN PROGRESS, CURRENTLY AT A VERY EARLY STAGE OF DEVELOPMENT
What is Flash Gordon ?
In laymen's words, Flash Gordon is an apk which allows you to flash any flashable zip (except for Roms) without having a recovery installed.
You just point it to the zip you want to flash, (be it a kernel, a mod, a gapps package, a modem, a RIL, a recovery...) and it will interpret the updater-script of this package and install its content just like a recovery would.
How does it work ?
Here is what happens step by step :
You tap the "select a zip" button, select the built-in file explorer to select the zip you want to flash
Flash Gordon will first extract this zip, depending on its size it can take a little time
When you press the "Flash Now" button, Flash Gordon will locate the updater-script and start translating it into shell code, line by line
It will output the resulting translated bash script on your sdcard and execute it, thus installing the zip's content
The app creates a notification, just tap on it to reboot
In order to achieve those last 2 steps, I'm writing a full Edify to Bash parser and translator.
Here is the list of all the Edify commands this parser can currently process and what their respective bash translation is (in green), using examples:
(more will be added over time, this is really just a draft)
By no means am I a bash expert, so if you have suggestions for better bash equivalents of any edify commands please post them
Code:
package_extract_file("path/to/source/file.txt", "/path/to/destination/file.txt");
[COLOR="DarkGreen"]busybox cp -fp /path/to/source/file.txt /path/to/destination/file.txt[/COLOR]
package_extract_dir("/source/folder", "/destination/folder");
[COLOR="DarkGreen"]busybox cp -rfp /source/folder/* /destination/folder[/COLOR]
set_perm(0, 2000, 0755, "/file/or/folder");
[COLOR="DarkGreen"]chown 0:2000 /file/or/folder
chmod 0755 /file/or/folder[/COLOR]
set_perm_recursive(0, 2000, 0644, 0755, "/path/to/set/permissions/recursively");
[COLOR="DarkGreen"]chown -R 0:2000 /path/to/set/permissions/recursively
chmod 0644 /path/to/set/permissions/recursively
chmod -R 0755 /path/to/set/permissions/recursively
[/COLOR]
delete("file/to/delete");
[COLOR="DarkGreen"]busybox rm -f /file/to/delete[/COLOR]
run_program("/script/to/run.sh");
[COLOR="DarkGreen"]sh /script/to/run.sh[/COLOR]
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
[COLOR="DarkGreen"]busybox mount -o rw,remount -t auto /system [I](will soon change to -t mmcblk0p9 or whichever mount point is in the updater-script)[/I][/COLOR]
unmount("/system");
[COLOR="DarkGreen"]busybox mount -o remount,ro /system[/COLOR]
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/adjtimex", "/system/xbin/arp", "/system/xbin/ash",
"/system/xbin/awk", "/system/xbin/base64", "/system/xbin/basename",
"/system/xbin/bbconfig", "/system/xbin/blkid", "/system/xbin/blockdev",
"/system/xbin/brctl", "/system/xbin/bunzip2", "/system/xbin/bzcat",
"/system/xbin/bzip2", "/system/xbin/cal", "/system/xbin/cat",
"/system/xbin/catv", "/system/xbin/chattr", "/system/xbin/chgrp",
"/system/xbin/chmod", "/system/xbin/chown", "/system/xbin/chroot",
"/system/xbin/clear", "/system/xbin/cmp", "/system/xbin/comm",
"/as/many/lines/as/you/want");
[COLOR="DarkGreen"]ln -s busybox /system/xbin/[ /system/xbin/[[
/system/xbin/adjtimex /system/xbin/arp /system/xbin/ash
/system/xbin/awk /system/xbin/base64 /system/xbin/basename
/system/xbin/bbconfig /system/xbin/blkid /system/xbin/blockdev
/system/xbin/brctl /system/xbin/bunzip2 /system/xbin/bzcat
/system/xbin/bzip2 /system/xbin/cal /system/xbin/cat
/system/xbin/catv /system/xbin/chattr /system/xbin/chgrp
/system/xbin/chmod /system/xbin/chown /system/xbin/chroot
/system/xbin/clear /system/xbin/cmp /system/xbin/comm
/as/many/lines/as/you/want
(not sure about this one, please correct me if I'm wrong, I could change to [I]ln -s argument/number/1 argument/number/2[/I] as many times as required if needed)[/COLOR]
write_raw_image("/tmp/boot.img", "mmcblk0p5");
[COLOR="DarkGreen"]dd if=/tmp/boot.img of=/dev/block/mmcblk0p5[/COLOR]
This is just a proof of concept for the moment, I'm aiming at adding all the possible Edify commands, and maybe doing it backwards (Bash2Edify) in the future, too.
Screenshots
This is from the apk I use for debugging, so the UI is pretty barebones atm, it will quickly evolve to something more fancy and featureful
{
"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"
}
Contribute
Flash Gordon is fully Open-Source, and contributions are more than welcome!
You can check-out the full source code on my github at : https://github.com/Androguide/FlashGordon
This app depends on the following Open-Source libraries :
My fork of the CardsUI library by [URL="https://plus.google.com/101314917101345770417/posts"]Nadav Fima[/URL]
aFileChooser by Paul Burke
Frequently Asked Questions
Q: Why can't I flash a Rom with Flash Gordon ?
A: Because when some system files are replaced while the device is running, it causes it to crash and will stop in the middle of the installation, resulting in a bootloop.
Q: Where can I see the bash script translation of the package I selected ?
A: After tapping the Flash Now button, head to /sdcard/RecoveryEmulator/tmp/flash_gordon.sh
The full translation is also output to the logcat while flashing.
Q: I select a flashable zip but it tells me it is not valid or that it's not a zip package, why ?
A: Make sure that there is no whitespace in the name of the zip package you're trying to flash, otherwise it won't be recognized.
If your package has no whitespace but the app still gives this error, try to shorten its name.
Q: Which versions of Android are supported ?
A: From Froyo (2.2) up to the latest JellyBean (4.2.2)
Q: Why is this app useful?
A: Some people might not be able to install a custom recovery on their device, either because there is no custom recovery for this model, or maybe their bootloader is locked. Flash Gordon allows them to flash packages even then.
Or maybe you're simply lazy and you don't want to have to reboot to recovery to flash that new kernel or that new cool flashable mod ? Then Flash Gordon is for you too.
Or maybe just for the heck of it ?^^
Requirements
All you need is a rooted Android device with a proper busybox installed. Required applets include :
mount
sed
unzip
rm
cp
Changelog
25/04/2013 : Initial release
26/04/2013 : Added a few fixes and regex corrections. (Github commit)
26/04/2013 : Hotfix for some flashable zips mistakenly identified as unvalid + Hotfix for kernels where the updater-script uses package_extract_file(); instead of write_raw_image(); (Github commit)
Click to expand...
Click to collapse
To Do List
Using a private version of busybox to remove having busybox installed/installing new applets as a requirement for the user
Implementing an equivalent of nandroid backups (zipping the content of the defined partition(s) and generating an updater-script to allow the user to restore the backup either through recovery or through Flash Gordon
Translating ui_print(); to echo in bash and make the "Flashing" ProgressDialog's message display the content of those ui_print();
Disclaimer
If you're going to test this app, make sure you have a nandroid backup handy as it is very far from stable.
I won't be held responsible for any damage done to anything whatsoever. You use this tool at your own risk.
Download
A preview/pre-alpha/proof-of-concept/work-in-progress/whatever-but-stable apk is attached to this post.
Again, make sure to have a nandroid backup before flashing anything through Flash Gordon for the moment.
If you like this project, please press the "Tip us?" button so that more people can know about it.
Reserved
Reserved too
Last one
You made it possible man.. hats off.. ^_^
Sent from my MT27i using xda premium
Will try this out!
Sent from my LT26i using xda premium
This i will test for sure!
Amazing work once again!
Sent from my Nexus 4
For the gsm galaxy nexus at least, choosing two zips (recovery, kernel) brings back a 'file not valid'. Looking forward to the "final" version.
Edit- if this helps.. twrp 2.5.5.0 and trinity kernel. If there is something for me to do please ask.
Flashed a XXEMB6 I9300 Modem+RIL with no problems.
dirtyreturn said:
For the gsm galaxy nexus at least, choosing two zips (recovery, kernel) brings back a 'file not valid'. Looking forward to the "final" version.
Edit- if this helps.. twrp 2.5.5.0 and trinity kernel. If there is something for me to do please ask.
Click to expand...
Click to collapse
Make sure there is no whitespace in the name of the zip, otherwise the app won't be able to pick it up.
If it still doesn't work, try shortening the name of the zips, for some reason I had the same issue with files which have long names
rickoslyder said:
Flashed a XXEMB6 I9300 Modem+RIL with no problems.
Click to expand...
Click to collapse
Thanks a lot for the feedback
Androguide.fr said:
Make sure there is no whitespace in the name of the zip, otherwise the app won't be able to pick it up.
If it still doesn't work, try shortening the name of the zips, for some reason I had the same issue with files which have long names
I gave shortening the file names a try with no success. And no spaces.
Click to expand...
Click to collapse
dirtyreturn said:
Make sure there is no whitespace in the name of the zip, otherwise the app won't be able to pick it up.
If it still doesn't work, try shortening the name of the zips, for some reason I had the same issue with files which have long names
I gave shortening the file names a try with no success. And no spaces.
Click to expand...
Click to collapse
That's weird, can you please give me a link to the zip you're trying to flash or attach it here ?
Would be very helpful for me to try and track the problem down
Top development here! Thanks
Sent from my GT-I9305 using Tapatalk 2
http://db.tt/SHgN82F1. http://db.tt/9hBvqE7d
Androguide.fr said:
That's weird, can you please give me a link to the zip you're trying to flash or attach it here ?
Would be very helpful for me to try and track the problem down
Click to expand...
Click to collapse
Cool idea. Thanks. :thumbup:
Sent from my EVO using xda premium
dirtyreturn said:
http://db.tt/SHgN82F1. http://db.tt/9hBvqE7d
Click to expand...
Click to collapse
Thanks a lot :good:
I tried them both after removing flashing from the app and they got extracted and translated properly on my device.
Please make sure you have a proper busybox install, if you do, please give me the output of this command in terminal :
Code:
unzip
I made a few fixes and corrections, here is the apk (the one in the OP was updated too)
Thanx a million :thumbup:
Androguide.fr said:
Thanks a lot :good:
I tried them both after removing flashing from the app and they got extracted and translated properly on my device.
Please make sure you have a proper busybox install, if you do, please give me the output of this command in terminal :
Code:
unzip
I made a few fixes and corrections, here is the apk (the one in the OP was updated too)
Click to expand...
Click to collapse
I have busybox v1.20.2-Stericson installed... in /system/xbin. .. in terminal running .unzip. gives the busybox info, 'Usage', followed by extract files from ZIP archives with other options. I am on CM10.1 if that makes a difference. edit- checked the applet manager section and 'unzip' is installed. And had installed updated apk. sorry this post is not much help.
This is GOLD.
Sent from my Galaxy S3. Long live the original Galaxy S
Related
Just finished porting the CWM 3.0.0.5/6 recovery.
Some notable changes are the following:
Auto EXT4 conversion system. If a partition is found to be RFS, but referenced in recovery.fstab as ext4, the system will AUTOMATICALLY convert the filesystem, backing up ALL data on the partition, and restoring it after. This may still have kinks, so if you run into any problems, simply flash your rom over it.
Removal of Amend script. This is a HUGE change for everyone using the update-script method to create flashable .zip files. ALL developers should begin using Edify scripts (updater-script and update-binary). I will post a few examples of common things below.
Color contrast changed from green on black to orange on black.
New mounting system. Partition types are no longer required to be compiled into CWM, and are instead detected from /config/recovery.fstab (Modified path to work with the redirector)
Notice: DO NOT INSTALL UNLESS YOU WANT EXT4!!!
[NEW] FOR EB13:
http://efragtv.com/android/OneClickRootCWM3-EB13.zip
NOTES FOR EB13: Auto conversion/restore seems to work 100% now. I converted and did NOT have to flash a rom over it. =]
[OLD] FOR DK28:
http://efragtv.com/android/OneClickRootCWM3.zip
INSTRUCTIONS:
1. Unzip to your desktop.
2. Go into your phone and Go to settings->Applications->Development and turn on USB Debugging.
3. Now double click run.bat in the folder you unzipped. (If you are on linux ./run.sh from the folder)
4. Wait for everything to happen.
5. Use the THREE BUTTON METHOD to get to CWM3.
6. Wait for the conversion operation to finish.
7. DO NOT REBOOT!!!!
8. IF YOU ARE ON AN ODEXED ROM (DEFAULT OTA) THEN YOU NEED TO REFLASH A ROM AFTER THE CONVERSION!!!!!!! ODEXED ROMS DO NOT GET RESTORED PROPERLY!
9. Flash the Default Stock Dual FS kernel For EB13: http://efragtv.com/android/EB13-DUALFS-KERNEL.zip
10. Enjoy CWM 3.0.0.5/6
See post #2 for Edify examples vs the old Amend style.
RESERVED for updater-script examples.
Syntax:
Code:
Amend Code
Edify Code
Copying a directory from the update package to the phone:
Code:
[COLOR=Red]Amend:[/COLOR] copy_dir PACKAGE:system SYSTEM:
[COLOR=SeaGreen]Edify:[/COLOR] package_extract_dir("system", "/system");
The first parameter is the direct location inside of the package.
The second location is the destination on the phone.
Mounting /data /system and /cache in Edify
Code:
run_program("/sbin/mount", "/dev/block/stl9", "/system");
run_program("/sbin/mount", "/dev/block/stl10", "/data");
run_program("/sbin/mount", "/dev/block/stl11", "/cache");
Printing a UI Message in Edify
Code:
ui_print("Some text here");
Create a symlink in Edify:
Code:
symlink("from","to");
Setting permissions in Edify:
Code:
Single file: set_perm(0, 0, 06755, "/system/xbin/su");
Recursive: set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
Run a program in Edify:
Code:
run_program("filetorun", "option1", "option 2", "option 3");
Delete a location recursively (like Amend's format):
Code:
delete_recursive("/path/to/delete");
Remember that script functions that take options (For example, run_program) must have each item that would require a space between it to be surrounded in double quotes, and followed by a comma. The last parameter must not have a comma afterwards.
Remember that ALL edify commands must end with a semi-colon.
Can't hardly wait! Am looking forward to learning about Edify scripts.
Will my download mode work after this?
:: rolls eyes ::
Sent from my SPH-D700 using XDA App
DevinXtreme said:
Will my download mode work after this?
:: rolls eyes ::
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No. Your phone will be dead forever.
This sounds promising but I'm gonna need help on the home binary scripts
Sent from my SPH-D700 using Tapatalk
Well it looks like we will all be releasing ROM updates later this week.
Sweeeeeeet
Sent from my SPH-D700 using XDA App
Thanks for all your hard work Dameon, def one of the best devs we have for the Epic. Donation will be coming your way soon Looking forward to trying this out!
Looking forward to this as well. So for those of us who currently have 2.5.1.0 / .2 installed, what will happen as far as updating to the newer cwm?
Dameon .. Nice work .. really sweet !! I don't have any money for you but if you need some new sick clothes let me know =) I own a dope clothing company in SO CAL... just drop me a line of what you need. Im running cwm .2 would i want to upgrade to this or just keep .2 ?
What is likely to happen is that this new one will overwrite 2.5.1.0. The other one, 2.5.1.2, is only baked into the rom. As per the OP, this will convert to ext4 and should only be used if you want ext4. However, the OP also said that the recovery.fstab file determines the file system (being a file system table and all). Since 2.5.1.0 was useless to us once converting to ext4, and we are basically running a hack to gain access to a usable recovery, this will simplify things for us.
And thanks Dameon. You've been busy the past few days.
No, I was unaware of that. I have only been using android since October, but I have been using linux on and off for almost 10 years. I've been learning what I can, but haven't found good explanations on how everything is put together in android. I need to spend some time reading the developer's guide and finding more guides. Also, I've been meaning to set up a kitchen so I can dig into the source, but I need to backup and wipe my laptop first. Not to thread jack, but do you know of any good places to start?
One thing that I'm sure will come up that the Edify zips will need to be signed using the android sdk. The good thing is that it's not hard to do.
That is, unless Dameon87 did something to Clockworkmod so that signing isn't necessary.
Sent from my SPH-D700 using Tapatalk
Signing is not necessary =]
Updated, Link added:
http://efragtv.com/android/OneClickRootCWM3.zip
Follow instructions in OP.
Link fixed in OP.
so this recovery will change the file system to ext4? There are no previous steps?
Sent from my SPH-D700 using XDA App
That is correct. Just run it like you would the one click root/CWM redirector installer.
AWESOME
Sent from my SPH-D700 using XDA App
*/Haters gonna hate/*
ROM currently "DISCONTINUED". But, the init.rc tweak remains :fingers-crossed:
Hi to all those who are reading this! Lemme answer a few questions before I get started.
First of all, What kinda name is this???
TBH, I haven't yet thinked of a name for this... So, I just named it Stock ROM MOD
And, the name has been thought of! The name is... CyanicSense! Why this name? More details later
What does this do?
Though this is gonna be as stock as possible, the major feature that I had planned out for this is reversed-mount. As you might know, stock ROMs definitely do have mounts2sd (which might give some trouble in setting up), but, complete reversed-mount (i.e. the /sd-ext partition mounted as the /data partition as the int2ext script does, hasn't been achieved yet (on stock ROM). So, practically, this does that stuff.
How is this even possible?
Believe me. This ain’t no magic. Simple init.rc tweak… Mounting the mtdblk0p2 partition, which is basically the sd-ext partition as we better know it, in the /data folder does the trick. In CyanogenMod, this is done via the famous int2ext script…This is a more or less similar command, done during startup. Just make some changes to init.rc, and Voila!!! Your sd-ext is mounted in the /data partition.
So, why make a new thread for this???
Erm, but that ain’t the end of story here. I am planning on some more features. Current features are minimal, reversed-mount, and updated apps. Yep. Updated apps, not one but all of them. I can assure you that you will have every single update including Google Play Store v4.0.xx in this ROM. Also, applications which were basically “stub’s” have also been updated, so that you wouldn’t have to download any more apps. P.S. I have added a small file explorer, named “Explorer”, by Speed Software, the same people who brought about “Root Explorer”. Planning to replace it with OI File Manager in next build, if people prefer it
So, those were the two features of this ROM. Also, I am planning to work on some other features, which mainly include, init.d script support, and, removing bloatware. Currently, there are around 10 apps which I don’t use, and presume that most other users wouldn’t be using it either. So, I am gonna either make them uninstallable, or remove them completely, so that one can get more /system space More features might come up too. You can request new features, but… be reasonable
Is it safe???
I can’t answer that question, but, I am guessing the answer is yes. Why I think so??? Because I am using this as my daily driver for the past few days. Also, “reverse-mount” via scripts like int2ext, and mounts2sd do the same thing, so, I don’t think its gonna create problems
Will it make my phone laggy?
Not sure. Works fine in my Class 4, 8 GB memory card. Anything Class 4 and above, I assure you it wouldn’t “visibly” lag.
What about gaming?
Well, this is the part where you come in. I don’t use my phone for gaming, so, I can’t be sure whether Temple Run 2 is lagging, or its I who can’t play it properly But, one fact can be sure that Stock ROM isn’t always the best choice for gaming.
Anything else left?
Yeah… This build is… kinda heavy. 160+ MB is definitely too big for the “stock” ROM. It is because of all the updated apps which were included. I will try to make subsequent builds lighter, and more bloatware free
Now that Q&A Section is over, let’s get back to business. The simple init.rc tweak is explained in the next post.
Instructions:
Pretty basic. Wipe everything, except SD-Card, and flash the ROM.
The following video might give you a slight idea
P.S.: Recovery used: TWRP 2.5.0.0 (http://forum.xda-developers.com/showthread.php?t=2123503)
Bugs:
I need help with that If you encounter any bugs, please report immediately in this thread.
Downloads:
Link: http://www.mediafire.com/?8grcxx1rbngr6g2
Here is the link… 162 MB approx. Why so big? You are the typical TLDR case. Read the Q&A section above.
Beta Link: http://forum.xda-developers.com/showpost.php?p=41966646&postcount=19
Any issues, please post in this thread. I will try to fix it, ASAP
init.rc tweak that I used:
First of all, get a stock boot.img, and boot_img tools from here: https://github.com/sakindia123/boot-image-tools
Unpack it to some location safe, and, copy-paste the boot.img into this folder.
Then, run the following commands:
Code:
mkdir -p unpack
Code:
./unpackbootimg -i ./boot.img -o unpack
Code:
mkdir -p boot
Code:
cd boot
Code:
gzip -dc ../unpack/boot.img-ramdisk.gz | cpio -i
Code:
cd ../
Thus, you will have the ramdisk of your boot.img in the "boot" folder. Open up that folder, and open "init.rc" with any of your favourite editor.
Now, search for this line:
Code:
mount yaffs2 [email protected] /data
Replace that line with this:
Code:
mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
Now, I know you are confused... I too was, at first. So, let me make things clearer for you...
This is basically a mount command, which is executed in this order
mount [type of partition] [partition] [mount directory] [options]
So, the partition type is ext3, to be made more compatible with most devices.
/dev/block/mmcblk0p2 is the sd-ext partition.
/data is the folder we are going to mount the partition in.
nosuid and nodev: Allow an ordinary (i.e., non-root) user to mount the filesystem if one of his groups matches the group of the device.
noatime and nodiratime: Access timestamps are not updated when a file is read. So, there is no writing on the partition everytime the disk is read.
barrier=0
This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance penalty. The ext3 filesystem enables write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure.
data=ordered
Specifies the journalling mode for file data. Metadata is always journaled.
commit=15
Sync all data and metadata every 15 seconds.
noauto_da_alloc
does give a slight performance increase, especially when working with databases..
nouser_xattr
Support "user." extended attributes (or not).
errors=continue
Define the behaviour when an error is encountered.
Reserved, for screenshots
Yo, screenshots will occupy this post
Reserved,
in case i forgot anything to say
i admit, i typed this in a hurry...
credits are yet to be given, so... please don't flame here
Nice work bro.
For I understand it, is a stock ROM with memory script by you only, yes?
Sorry my english lvl xDDD....
Good job
Edit: well.. must say brother you did good work..
Rom is purely stock with only this tiny mod..
No bugs till now
This ain't no memory script.
TBH, I haven't even enabled init.d support yet. This is solely related to boot.img's init.rc... Which initiates reverse mount when you start your phone.
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Yes.
@rcane said:
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Stock ROM, version: 1.43.720.2
Brother.. here's a big problem..
The data folder of the Rom is now empty and all the app's apk files and app data installed can't be accessed using the root explorer..
And it is no where.. o can't find them..
Did you make a link to the data folder while mounting the ext partition to data..??
Sent from noob machines
I recommend using another application.
P.s. you will find it in the data folder only. It won't be in the sd-ext folder.
P.s. sorry for the short reply. I ain't at home currently
Sent from my HTC Explorer A310e using xda app-developers app
I used solid explorer..
I got them.. but on es file explorer.. the folder is still empty..
And also there is no sd-ext folder in root... Because you didn't make one..
Sent from noob machines
Did you enable Root Explorer or so...
AFAIK, even in the latest update, root exploration should be first enabled.
Press menu key, and in tools option, there will be the "root explorer" option, or a similar option.
Enable that, and then, you will be able to browse the data partition.
P.S.: if you don't get a superuser request, it will not work.
OK got it...
Thanks brother...
I got my mistake... it works now..:good:
Ohk, tiny flashable zip's coming up!!! HELP NEEDED!
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
me..
vineethraj49 said:
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
Click to expand...
Click to collapse
if u find something i can do , feel free to tell..
Thanks
artistaditya said:
if u find something i can do , feel free to tell..
Click to expand...
Click to collapse
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
I have this..
vineethraj49 said:
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
Click to expand...
Click to collapse
Sorry i dont have access to all the roms but i can give you information on Nextgen and jaggyrom..
--JaggyRom [specific version 3.2.1 lite]
1.) init.d support - yes
2.) apps2sd script used [without gui]
boot.img here- jaggyrom_boot.img
--NextGen [specific version 1.5]
1.) init.d support - yes
2.) mounts2sd script used [without gui]
boot.img here- nextgen_boot.img
Note to Beta testers! Cyanic Sense Beta is out!
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Screenshots
vineethraj49 said:
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Click to expand...
Click to collapse
Seems the OP forgot to add the "obligatory" screenshots
No worries here I am xD
{
"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"
}
Click to expand...
Click to collapse
Seems OP is working great,waiting for future updates!
Hey Guys, Here is a small application i created as i was fed up with the slow rom installs due to the format line of the updater-script
{
"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"
}
Code:
Requires NET Framework 4.5
Put simply this small application will patch the .zip
Replacing the line below
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
With the following line
delete_recursive("/system");
It supports manually browsing to the zip file
It supports dragging the zip file on to the exe
It supports right clicking the zip file and selecting "Patch ROM Zip File"
Note: Make sure to run the exe directly once to enable right click context menu. No installation required.
1.1
Fixed small issue with .zip detection
1.0
Initial Release
Released by Cyanlabs for XDA-Developers.
http://cyanlabs.co.uk
Download Here - http://kitchen.cyanlabs.co.uk/LG_G2/index.php?dir=G2+Tools+By+Cyanlabs/
It knocks off around 5-10minutes of flashing time and only takes about 10 seconds to patch
Use this file to remove the context menu entry RemoveContextMenu.reg (it will be re-added upon launching the application again)
Source:
Code:
Imports System.IO.Compression
Imports System.IO
Imports Microsoft.Win32
Public Class Form1
Dim FileToModify As String = ""
Private Sub NsButton1_Click(sender As Object, e As EventArgs) Handles NsButton1.Click
Using dialog As New OpenFileDialog
dialog.Title = "Select ROM Zip File"
dialog.Filter = "Zip Files (*.zip)|*.zip"
dialog.RestoreDirectory = True
If dialog.ShowDialog() <> DialogResult.OK Then Return
ModifyFiles(dialog.FileName)
End Using
End Sub
Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load
WriteRegistryHandler()
Try
FileToModify = My.Application.CommandLineArgs(0)
If FileToModify.Contains(".zip") Then
ModifyFiles(FileToModify, True)
Else
MsgBox("Invalid file selected!")
End If
Catch ex As Exception
End Try
End Sub
Sub ModifyFiles(update As String, Optional close As Boolean = False)
Try
Using archive As ZipArchive = ZipFile.OpenRead(update)
Dim File As ZipArchiveEntry = archive.GetEntry("META-INF/com/google/android/updater-script")
If System.IO.File.Exists(Application.StartupPath & "\" & File.Name) Then System.IO.File.Delete(Application.StartupPath & "\" & File.Name)
File.ExtractToFile(Application.StartupPath & "\" & File.Name)
archive.Dispose()
End Using
Catch ex As NullReferenceException
MsgBox("no updater-script found")
Application.Exit()
End Try
Try
Dim reader As New StreamReader(Application.StartupPath & "\updater-script")
Dim s = reader.ReadToEnd().Replace("format(""ext4"", ""EMMC"", ""/dev/block/platform/msm_sdcc.1/by-name/system"", ""0"", ""/system"");", "delete_recursive(""/system"");")
reader.Close()
If System.IO.File.Exists(Application.StartupPath & "\updater-script") Then System.IO.File.Delete(Application.StartupPath & "\updater-script")
Dim writer As New StreamWriter(Application.StartupPath & "\updater-script")
writer.Write(s)
writer.Close()
Using archive As ZipArchive = ZipFile.Open(update, ZipArchiveMode.Update)
archive.GetEntry("META-INF/com/google/android/updater-script").Delete()
archive.CreateEntryFromFile(Application.StartupPath & "\updater-script", "META-INF/com/google/android/updater-script")
End Using
If close Then MsgBox("Patched Successfully!", MsgBoxStyle.Information, "Success")
Application.Exit()
Catch ex As Exception
MsgBox(ex.Message)
Application.Exit()
End Try
End Sub
Private Sub Label2_Click(sender As Object, e As EventArgs) Handles Label2.Click, Label1.Click
Process.Start("http://cyanlabs.co.uk")
End Sub
Sub WriteRegistryHandler()
Registry.CurrentUser.CreateSubKey("Software\Classes\CompressedFolder\shell\Patch ROM Zip File\command")
Registry.CurrentUser.OpenSubKey("Software\Classes\CompressedFolder\shell\Patch ROM Zip File\", True).SetValue("Icon", """" & Application.ExecutablePath & """")
Registry.CurrentUser.OpenSubKey("Software\Classes\CompressedFolder\shell\Patch ROM Zip File\command", True).SetValue("", """" & Application.ExecutablePath & """ ""%1""")
End Sub
End Class
Linux version
mattmannlt said:
I threw these together for Linux. Any other Linux users out there here you go.
LG-G2-RomFormatFix.sh
Nautilus script for right click menu.
LG-G2-RomFormatFix.sh
Thanks fma965. Good find.
Click to expand...
Click to collapse
sub'd. interested in this. possible to make it work via mac? and also on android itself?
Looks interesting, will take a look
Sent from my LG-VS980 using Tapatalk
I could make it work on Mac and Android but I don't have the skills for the coding languages used on those platforms
Sent from my LG-D802 using Tapatalk
I hear ya! So slow formating on this device.
This will come in handy for the real flash addicts.
Yep. Added this to my soon to be released EnergyROM for the LG G2. Thanks for the tip
Would be great if this could be done on Android. Download ROM with the phone, patch it, flash it
Thanks!
MaluNoPeleke said:
Would be great if this could be done on Android. Download ROM with the phone, patch it, flash it
Thanks!
Click to expand...
Click to collapse
Read up!
fma965 said:
Hey Guys, Here is a small application i created as i was fed up with the slow rom installs due to the format line of the updater-script
Code:
Put simply this small application will patch the .zip
Requires NET Framework 4.5
Replacing the line below
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
With the following line
delete_recursive("/system");
It supports manually browsing to the zip file
It supports dragging the zip file on to the exe
It supports right clicking the zip file and selecting "Patch ROM Zip File"
Note: Make sure to run the exe directly once to enable right click context menu. No installation required.
Version 1.0 - Released by Cyanlabs for XDA-Developers. http://cyanlabs.co.uk
Download Here - http://kitchen.cyanlabs.co.uk/LG_G2/index.php?dir=G2+Tools+By+Cyanlabs/
It knocks off around 5-10minutes of flashing time and only takes about 10 seconds to patch
Use this file to remove the context menu entry RemoveContextMenu.reg (it will be re-added upon launching the application again)
UPDATE: And yes this is a simple application it has only around 70 lines of code, this is one of my most basic applications and it was designed to be quick and basic, i can code programs that are much more advanced than this... check my github for proof, (http://github.com/cyanlabs)
Click to expand...
Click to collapse
Thank you good sir, I was doing this manually for a long time, now I no longer need to do this with your script!
djkinetic said:
Thank you good sir, I was doing this manually for a long time, now I no longer need to do this with your script!
Click to expand...
Click to collapse
My first and hopefully not last contribution to the LG G2 community, I have made many contributions while i was in the xperia play community as can be seen in my signature
offtopic: dont forget XDA has a thanks button
------------------------
v1.1 Uploaded - Read OP For Info
If any one with android/java programming skills is here then this post may help
http://pastebin.com/KiqLaTLT or http://pastie.org/8499361 (detailed information on what my application does so that some one can recreate it in java using the java class java.util.zip and inputstreams
Linux Versions
I threw these together for Linux. Any other Linux users out there here you go.
LG-G2-RomFormatFix.sh
Nautilus script for right click menu.
LG-G2-RomFormatFix.sh
Thanks fma965. Good find.
mattmannlt said:
I threw these together for Linux. Any other Linux users out there here you go.
LG-G2-RomFormatFix.sh
Nautilus script for right click menu.
LG-G2-RomFormatFix.sh
Thanks fma965. Good find.
Click to expand...
Click to collapse
Nice work, Uh could these run under terminal emulator on Android?
Sent from my LG-D802 using Tapatalk
fma965 said:
Nice work, Uh could these run under terminal emulator on Android?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Is this patcher thing only for linux? cause I can't run it since its on win-32 bit.....
HeXaLox said:
Is this patcher thing only for linux? cause I can't run it since its on win-32 bit.....
Click to expand...
Click to collapse
mine is for Windows
the other one is for Linux
Sent from my LG-D802 using Tapatalk
FMA Saves the day again ^_^ +thnx bud
great idea but I easy question: why dev don't change script in rom? In my rom I use this form first ver
acer73 said:
great idea but I easy question: why dev don't change script in rom? In my rom I use this form first ver
Click to expand...
Click to collapse
well yes of course that is the ideal outcome but I can't control the devs so I make my own method
Sent from my LG-D802 using Tapatalk
I used this in my last round of ROM updates, but there is an issue with it. I had experienced this once and thought it was my recovery. One of my port testers experienced the same problem, so I decided to confirm the issue.
When I go back to my restore of my original stock ROM, do a Factory Reset, and then flash my ROM (with your included code), the ROM install fails. However, if I flash the same ROM (without your included code), the ROM installs fine. If I am also on a custom ROM and then flash and then flash my ROM (with your included code), the ROM installs fine.
Something about the original stock ROM creates this issue. I can't confirm a custom stock ROM, but I thought you may want to include this information in the OP in case anyone else runs into this issue. I'll include my exact steps in case you want to see it in action.
STEPS
ITEMS USED: I had my HeatshiverSX v1.5 (your code included) and a HeatshiverSX v1.5 copy (without your code). I had a backup of my original stock ROM, and used TWRP as my recovery.
Restored the backup.
Booted into OS.
Booted into recovery.
Factory Reset.
Flashed HeatshiverSX v1.5 (with code).
Install failed.
Factory Reset again.
Flashed HeatshiverSX v1.5 copy (without code).
Install worked.
Heatshiver said:
I used this in my last round of ROM updates, but there is an issue with it. I had experienced this once and thought it was my recovery. One of my port testers experienced the same problem, so I decided to confirm the issue.
When I go back to my restore of my original stock ROM, do a Factory Reset, and then flash my ROM (with your included code), the ROM install fails. However, if I flash the same ROM (without your included code), the ROM installs fine. If I am also on a custom ROM and then flash and then flash my ROM (with your included code), the ROM installs fine.
Something about the original stock ROM creates this issue. I can't confirm a custom stock ROM, but I thought you may want to include this information in the OP in case anyone else runs into this issue. I'll include my exact steps in case you want to see it in action.
STEPS
ITEMS USED: I had my HeatshiverSX v1.5 (your code included) and a HeatshiverSX v1.5 copy (without your code). I had a backup of my original stock ROM, and used TWRP as my recovery.
Restored the backup.
Booted into OS.
Booted into recovery.
Factory Reset.
Flashed HeatshiverSX v1.5 (with code).
Install failed.
Factory Reset again.
Flashed HeatshiverSX v1.5 copy (without code).
Install worked.
Click to expand...
Click to collapse
THanks for the information, Wouldn't this be due to something relating to the partition being formatted and not rm -rf'd ?
The purpose of this guide is to show users here in our Forum how to use the DSIXDA kitchen so that they may become familiar with cooking their own Roms and possibly becoming a valuable asset to our community down the road. So I hope to see this become useful for some of you willing to learn and well, to also not be lazy and expecting others to do the work for you - no pun intended lol.
Let's understand what a basic Rom contains:
- First and foremost, a Rom.zip will always have at minimum:
-- A boot.img at the root of the Rom.zip
-- A /system folder
-- A /META-INF folder
{
"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"
}
--- Now, I assume you already have done me the favor of installing the kitchen and so by therefore, saving me the trouble of having to explain the process of installation. It's simple. Moving along now.
--- Go ahead and get the kitchen up and running in your CMD Window. I will be using Ubuntu in reference to this guide but the same should also apply to those who prefer Windows/Cygwin.
As you see in your CMD Window there are some options with basic information as to what those options will do for you.
The first thing we need to do is set up our working folder which will be option number 1, but before we can do that we need a Rom to work with. There are many ways to getting your hands on a Rom. However, for the sake of this tutorial I will use a Nandroid Backup created by TWRP (Custom Recovery).
-- Please note that a TWRP system backup will require additional steps.
-- This is because the kitchen does not support its backup format.
--- Go ahead and make a copy of your boot and system backup and paste them in the original_update folder which can be found in the kitchen directory. From a 'TWRP backup' the boot.img will be originally named boot.emmc.win and the system.img will originally be named system.ext4.win. Go ahead and change them respectively to boot.img and system.img (It is that easy).
--- Now, create a folder and name it whatever you like, BUT the name MUST include WORKING_ at the beginning of its name.
-- An example: WORKING_k2cl_412_deodexed
--- Move the boot.img in to the created folder. Open up the working folder and create another sudirectory folder named system.
--- Go ahead and move the system.img in to the subdirectory folder named system located inside of your working folder.
--- Open up a new CMD Window and change directories to where the system.img is currently located at.
--- Go ahead and enter:
Code:
tar -xvf system.img
-- This will unpack the system backup made by TWRP
-- DSIXDA Kitchen does not currently support this format so YOU must do it.
--- As you can see, the system folder is now complete with all that you will need to start on your Rom. Go ahead, and remove the actual system.img file as it will not be needed now.
--- Go back to the CMD Window which has the kitchen up and running. Select option 1 to set up your working folder for the kitchen. It will give options to show supported formats or to abort. Go ahead and just press enter.
--- It will bring up a list of working materials to use for establishing your working folder for the kitchen. In my case, the working folder I will be using is option number 2, WORKING_k2cl_412_deodexed. Go ahead and select your option now.
--- It will ask you if you want to change the name of the new working folder. The option is yours. Choose yes or no (this part really doesn't matter).
--- Once you press enter it will create the new working folder which can be found at the root of the kitchen directory. It will be copying the contents over to the new working folder.
--- It will detect whether or not your rom has an updater script, symlinks, root, busybox, etc. If any of these are detected it will let you know it found them and it will adjust accordingly to them. Which saves you lots of time.
--- Now it will ask you if you would like to view the Rom's information. This is optional for you. If you want to see it then select yes, if not, then select no.
--- Congratulations! You have a Rom set up to be worked on! At this point you can choose to deodex your Rom, unpack and edit your boot.img, root your device both, /system and boot.img. Add additional tweaks, apply init.d support, etc.
--- Once you have finished playing with your Rom as a first timer, go ahead and back out to the main menu of the kitchen. Select number 99 to build your Rom from the working folder.
--- You will be asked to select a build option. Go ahead and select option number 1.
--- Select yes to zipalign your apk files
--- Next it will build your updater-script for your Rom based on an android device. It will ask you to review the updater-script before proceeding forward. You MUST insure the updater-script is ready for your device or it will not flash!
--- Go to the working folder of that rom and scroll the the subdirectories found in the META-INF folder until you see the updater-file. Open it up with notepad++ for Windows users or Gedit for linux users. You are going to look at the top and add the following (PLEASE INSURE YOU USE THE PROPER SYSTEM PARTITION FOR YOUR DEVICE - THIS EXAMPLE IS BASED ON MY K2_CL DEVICE!:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "/system");
delete_recursive("/system");
package_extract_dir("system", "/system");
--- Now scroll to the bottom of the updater-script. You may see some crazy stuff about raw writing the boot.img. Go ahead and remove that mess and replace it with the following (PLEASE INSURE YOU USE THE PROPER BOOT PARTITION FOR YOUR DEVICE - THIS EXAMPLE IS BASED ON MY K2_CL DEVICE!:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
--- Once done, go ahead and save the updater-script file. Go back to the CMD window running the kitchen and select yes to keep the updater-script for the Rom.
--- It will create the update.zip, it will ask you to sign the Rom (say yes), then it will ask you if you wish to change its name or leave it as is (your choice).
--- Congratulations, now go ahead and flash your Rom to test it out. Be sure to Factory reset your device from within the custom recovery, and insure that the system partition is wiped also. After it is done flashing the rom, wipe the dalvik and cache before rebooting, and remember... Any problems without a logcat is trivial!!!
--- Happy Hunting!!
That's my pet lizard, Saucy. He keeps me company, haha.
Sent from my C525c using Tapatalk
Thanks man. This is exactly what I wanted to get me going. It's late for me but I'll definitely be checking this guide out tomorrow.
Good luck. I used a TWRP backup as an example because it requires extra steps. Any other time, like a system dump for example, the kitchen will detect it and be able to unpack the system.img for you automatically, but because of how TWRP formats the ext4 backups it must be done manually since the kitchen doesn't support it yet. Just some insight so you know that you don't always have to manually unpack the system.img.
Sent from my C525c using Tapatalk
If a normal system img aside from TWRP then all is required is naming them boot.img and system.img then placing both inside of the 'original_' folder then running the kitchen. Select option 1 and it should detect both. It will build the working folder, the subdirectory system folder, meta-inf folder, place the boot.img, and unpack the system.img automatically. For future reference.
Sent from my C525c using Tapatalk
also, for the "newbies" including me,
http://forum.xda-developers.com/showthread.php?t=2597220
[KITCHEN][FORK] Android Kitchen Continuation (WIP) [Linux / Mac / Windows]
here's a link to a more up to date kitchen, I haven't used it but it seems legit.
Haha, just took a look at it. Most of the added features I have already done for my personal use. Guess I can hit this guy up with some ideas. Thanks for that link @russellvone
Sent from my C525c using Tapatalk
Top priority is adding support for TWRP backups, and looking into implementing the ability to re-odex the Rom. It can be done, despite that the founder says otherwise.
Sent from my C525c using Tapatalk
Oh, and don't no one take offense to my title, "Newbies". Meant nothing insulting by it. Just used it regarding that maybe you are new to it. We all got to start somewhere.
Sent from my C525c using Tapatalk
If you ran through and deodexed, did you by chance get an error when it attempts to deodex HTCNotes?
Here's what I'm getting:
Code:
NOW AT FILE 1 OF 1 IN system/app: HtcNotes.odex
Disassembling HtcNotes.odex ...
java -Xmx512m -jar baksmali.jar -a 17 -d ../framework -x HtcNotes.odex
Error while disassembling method Lcom/htc/notes/detail/NotesDetailActivity$13;->handleMessage(Landroid/os/Message;)V. Continuing.
org.jf.dexlib.Code.Analysis.ValidationException: Could not resolve the method in class Lcom/htc/widget/HtcSeekBarPopupWindowListener; at index 75
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInvokeVirtualQuick(MethodAnalyzer.java:3655)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:1110)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:389)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:311)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:310)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:117)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:186)
at org.jf.baksmali.main.main(main.java:308)
opcode: invoke-virtual-quick/range
CodeAddress: 1478
Method: Lcom/htc/notes/detail/NotesDetailActivity$13;->handleMessage(Landroid/os/Message;)V
ERROR: Aborting HtcNotes.odex
Finished system/app
WARNING: Could not deodex the following (you can try to deodex these files again):
HtcNotes.odex
I've already tried again too
@palmtree5
Is your Rom 4.1.2 or 4.2.2?
Sent from my C525c using Tapatalk
Modding.MyMind said:
@palmtree5
Is your Rom 4.1.2 or 4.2.2?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
4.1.2
@palmtree5
Thought so lol.
You are getting that error because you are using API 17 setting for a 4.1.2 Rom. 4.1.2 is built on 16. Change it to 16 and try it again.
Sent from my C525c using Tapatalk
Modding.MyMind said:
@palmtree5
Thought so lol.
You are getting that error because you are using API 17 setting for a 4.1.2 Rom. 4.1.2 is built on 16. Change it to 16 and try it again.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Now why didn't I think of that!
---------- Post added at 01:54 PM ---------- Previous post was at 01:33 PM ----------
palmtree5 said:
Now why didn't I think of that!
Click to expand...
Click to collapse
Ok, the deodexing worked out fine after that
@palmtree5
Just a heads up...
When you go to flash your deodex Rom, it will take forever to boot up for its first intial boot. Afterwards, it will boot up at normal timing. So when you flash it and it goes through the bootanimation then hangs on the HTC logo, be patient. Don't pull the battery lol.
Sent from my C525c using Tapatalk
Should take no more than 5 to 10 minutes at most given my personal experience.
Sent from my C525c using Tapatalk
Modding.MyMind said:
@palmtree5
Just a heads up...
When you go to flash your deodex Rom, it will take forever to boot up for its first intial boot. Afterwards, it will boot up at normal timing. So when you flash it and it goes through the bootanimation then hangs on the HTC logo, be patient. Don't pull the battery lol.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yeah, fairly certain I've used deodexed roms before on other devices, just never deodexed one myself
palmtree5 said:
Yeah, fairly certain I've used deodexed roms before on other devices, just never deodexed one myself
Click to expand...
Click to collapse
Nice
Just making sure bro lol. Didn't want you coming back panicking under the assumption you may had not been aware.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Nice
Just making sure bro lol. Didn't want you coming back panicking under the assumption you may had not been aware.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Right. Better to err on the side of caution
I'm bumping this thread because I am seeing A LOT OF PEOPLE ON HERE having troubles fixing their devices and for whatever the reason may be it seems to be with a LOT of these twrp backups people are grabbing from others because they either lost theirs or never made one from the get go (horrible decision).
So, if you are having troubles restoring with a backup then this guide should help you make up a quick Rom and get your device back.
You aren't looking to do anything fancy with the "kitchen" but to just build a quick odex or deodex Rom to flash and be up and running again.
Please take advantage of this if all else is failing for you.
IT IS NOT THAT HARD TO DO
--- Happy Hunting!!!
Sent from my C525c using Tapatalk
{
"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"
}
EagleRootTool - Xperia M2 Lollipop Root Tool
based on iovyroot & rootkitXperia
Hi all!
I'm very happy to announce you that, thanks to iovyroot, and with a lot of help from zxz0O0, we managed to get a new root binary working on the Sony Xperia M2, meaning we don't actually need to use Kingroot anymore to root LBL devices under Lollipop (18.6.A.0.182, and probably 18.6.A.0.175 too) :victory:
Requirements:
Stock kernel, from Sony's stock firmware 18.6.A.0.182, Linux version 3.4.0-gc82e70f based.
ADB enabled
Settings -> About phone -> Click 7 times on Android Build to unlock Developer options, and USB Debbuging
ADB drivers installed (you can pick them from Sony Mobile's website)
Material Terminal, from Yaroslav Shevchuk, if you want to do the root process right from your device.
You can get it on Google Play or APKmirror
Usage:
Download the tool
Extract the files
Execute the install.bat with a double click if you're on Windows, or simply do "sh install_mobile.sh" on Material Terminal (remember to use cd /path/to/where/you/placed/it to change to the folder were you extracted the files)
Wait until the process ends. Your device will reboot automatically
Download: Version 2016/05/31
Please, consider donating (or at least saying thanks!) to the people involved in the project if this tool was useful to you! zxz0O0, Cubeundcube, AleksJ & myself
Special thanks to:
- @zxz0O0 for iovyroot and his help
- @cubeundcube for his rootkitXperia scripts
- @AleksJ for providing copymodulecrc, ric_mod and testing
Enjoy! That kitty is a bad kitty!
XDA:DevDB Information
EagleRootTool (Root any Xperia M2 in 5.1.1, LBL & UBL), Tool/Utility for the Sony Xperia M2
Contributors
linuxct
Version Information
Status: Beta
Current Beta Version: 2016/05/31
Beta Release Date: 2016-05-31
Created 2016-06-02
Last Updated 2016-12-17
Frequently Asked Questions
- Can I use the install_mobile.sh installer on Linux for PC?
No.
- Can I use any other Terminal app?
No. Have a look at the install_mobile.sh file, and you'll realize why.
- Can I use this with an already rooted device (such as kingroot) to change the SU management app?
Not advisable. Format your system first using a FTF & Flashtools.
- Is RIC working / will I have RW access to System after rooting with this?
RIC is killed by default in every boot thanks to a init.d script, called 00stop_ric, so you'll have RW access to system always.
- Will you port this to other Xperia devices?
Yes, if they decide to collaborate and it's kernel's supported (aka vulnerable to CVE-2015-1805). We'd need the full kernel offsets of that particular device, so that we can look for the ones we actually need.
Reserved
Nice work fella, not tried it myself but beats using kingroot that's for sure. Unfortunately I may never get to try it out my M2 is getting replaced in a few weeks.
can i use for 4.4.4 (LOL) i just ask
NieeLz said:
can i use for 4.4.4 (LOL) i just ask
Click to expand...
Click to collapse
There's already a kk one linuxct made its on here somewhere.
Very useful and helpful, probably not only for M2.
All is fine here.
NieeLz said:
can i use for 4.4.4 (LOL) i just ask
Click to expand...
Click to collapse
Just as Adrian said, there's already a tool for that lmao
RootXperia Toolkit 2015/09/26 (Or how to Root 4.4.4 without downgrading)
I think it'll work on the t2u/c3 aswell.
aidy.lucas said:
I think it'll work on the t2u/c3 aswell.
Click to expand...
Click to collapse
As it is right now, it won't. I need the kernel offsets from those devices (T2u, C3, E4 users, I'm looking at you), which can be easily get in an already rooted device through catting /proc/kallsyms to a file using > /path/to/your/sd/kallsyms.txt, for example. (more info on getting the kallsyms here). Also, it'd be neat to have the /proc/version and the firmware version installed on the device.
Please remember, the kernel timestamp must say it was compiled before December 2015 to ensure the vulnerability is still there.
Once we got that, I can just add the offsets we need to the offsets.c database and recompile the iovyroot binary, and there shouldn't be any reason to touch the other scripts since they should work out of the box
linuxct said:
Just as Adrian said, there's already a tool for that lmao
RootXperia Toolkit 2015/09/26 (Or how to Root 4.4.4 without downgrading)
Click to expand...
Click to collapse
aidy.lucas said:
There's already a kk one linuxct made its on here somewhere.
Click to expand...
Click to collapse
hahahah i mean if i download this i have one tool can root kitkat and lollipop btw thanks for reply
why the script doesn't exist in init.d folder after using this?
DavidMKD said:
why the script doesn't exist in init.d folder after using this?
Click to expand...
Click to collapse
00stop_ric gets created, doesn't it?
Maybe I dropped the ball on something, can I get the full output of the script?
P.S. The init.d is in /system/etc/init.d, maybe you were looking for it somewhere else.
DavidMKD said:
why the script doesn't exist in init.d folder after using this?
Click to expand...
Click to collapse
When the tool finishes its execution, 00stop_ric and 99SuperSUDaemon can be found in the /system/etc/init.d directory.
linuxct said:
00stop_ric gets created, doesn't it?
Maybe I dropped the ball on something, can I get the full output of the script?
P.S. The init.d is in /system/etc/init.d, maybe you were looking for it somewhere else.
Click to expand...
Click to collapse
AleksJ said:
When the tool finishes its execution, 00stop_ric and 99SuperSUDaemon can be found in the /system/etc/init.d directory.
Click to expand...
Click to collapse
Yes, indeed that's the folder. The folder gets created, the wp_mod.ko gets copied but the script stops at execution of stopric.sh script and after trying to remount the system. The script stops at that point and no 00stop_ric.sh script get's created. All files get stuck in data/local/tmp/ folder and nothing is created after that. I will try to run the script from terminal but I'm pretty sure that the program can't write on system at this point i.e. operation is permitted
DavidMKD said:
Yes, indeed that's the folder. The folder gets created, the wp_mod.ko gets copied but the script stops at execution of stopric.sh script and after trying to remount the system. The script stops at that point and no 00stop_ric.sh script get's created. All files get stuck in data/local/tmp/ folder and nothing is created after that. I will try to run the script from terminal but I'm pretty sure that the program can't write on system at this point i.e. operation is permitted
Click to expand...
Click to collapse
This situation is extremely weird, and uncommon, I would say...
If the ric_mod.ko gets copied, by using dd, then it means the case was chosen correctly, so there's no reason for not creating the 00stop_ric, since it's just about echoing some lines to the file, change the owner, the permission, and that's it, as seen in the pic attached.
May I have your current environment (firmware version, etc)? Was the device previously rooted, and un-rooted to test the tool? Any info is appreciated.
linuxct said:
This situation is extremely weird, and uncommon, I would say...
If the ric_mod.ko gets copied, by using dd, then it means the case was chosen correctly, so there's no reason for not creating the 00stop_ric, since it's just about echoing some lines to the file, change the owner, the permission, and that's it, as seen in the pic attached.
May I have your current environment (firmware version, etc)? Was the device previously rooted, and un-rooted to test the tool? Any info is appreciated.
Click to expand...
Click to collapse
Well I've reflashed the phone since it had some display repairs and I've tried this method to disable the ric and get root and all I've got was the root only. The ric wasn't disabled and the script to disable the ric only by alex wasn't working at all since it had conflicts with this tool. The firmware version is 18.6.A.0.182. The old fashioned way by using kingroot then changing it to SuperSU and applying the disable ric script works without a problem. I will try to reconstruct the problem by giving you the outputs from the script as soon as I can
DavidMKD said:
Yes, indeed that's the folder. The folder gets created, the wp_mod.ko gets copied but the script stops at execution of stopric.sh script and after trying to remount the system. The script stops at that point and no 00stop_ric.sh script get's created. All files get stuck in data/local/tmp/ folder and nothing is created after that. I will try to run the script from terminal but I'm pretty sure that the program can't write on system at this point i.e. operation is permitted
Click to expand...
Click to collapse
Very strange results.
Tested again on clean installation (1281-1516-18.6.A.0.182).
EagleRootTool_20160531.zip
MD5: 2e59c4963e0e8824cb774726d3743513
File Size: 3947624 bytes
http://pastebin.com/hgRhqfbk
Guys can I use this with a PC? And Lollipop version? I have a D2403
tquin said:
Guys can I use this with a PC? And Lollipop version? I have a D2403
Click to expand...
Click to collapse
Yes, and yes. Answers for both of your questions were already answered (by the context) in the OP.