Download or cook the PRE-ROOTED firmware for ATV580 (Mygica/Geniatech) Rockchip RK3188 ARM Cortex A9 x 4 CPU.
DOWNLOAD ROM - [ROOTED & CLEAN]
Mygica ATV580 Tazpown Firmware (Build 20131213.20140309):
- Download: ATV580.Tazpown.Firmware.Build-20131213.20140309.zip -
Build Information:
Android 4.2.2 Quad Core Enjoy TV Box
Build Number: 20131213.20140309
Release Date: 2014-03-09
Based Mygica Official Build 20131213.102000
Click to expand...
Click to collapse
Change log:
1.) Based on Mygica Official Build 20131213 Android 4.2.2 (Quad Core Enjoy TV Box)
2.) Removed most Chinese and unnecessary or obsolete applications.
3.) Added su (SuperSU v1.93 06.02.2014) and busybox (Busybox defconfig build for 1.21.1 armv71) Android Rooting Utilities.
4.) Switched External SDCard (up to 32GB) with Internal Flash (only 2GB) Memory. Tested: moving apps to SDCard OK!. You should have an micro SD card inserted on your device.
5.) Fixed Black Screen when playing video with Youtube App.
Click to expand...
Click to collapse
Installation Tips:
For a complete information about how install this rom image, scroll down to the bottom of the post.
COOK YOUR OWN CUSTOM FIRMWARE FOR MYGICA ATV580 - DIY!
You can watch the full tutorial process on this video (this video is a little help, the complete steps its only here in this post).
https://www.dropbox.com/s/88330vv1q3p1pzu/Mygica580-custom-firmware.mov
Original Non-Rooted Mygica Latest ATV580 Stock Firmware (official):
http://www.mygicausa.com/boards/search?searchterms=atv580
Based Mygica Official Build 20131012 Android 4.2.2: https://www.dropbox.com/s/kopamtzdr7gv63d/update20131012.img
Based Mygica Official Build 20131213 Android 4.2.2: https://www.dropbox.com/s/36rkjlf98k47uyc/update20131213.img
1. [ON WINDOWS] Extract Rocket Firmware with imgRePackerRK 1.04
imgRePackerRK RockChip's firmware images (*.img) unpacker/packer. Version 1.04 Windows & Linux
http://forum.xda-developers.com/showthread.php?t=2257331&page=2.
How to unpack a firmware IMG (Windows):
1. Obtain firmware IMG [update.img] and imgRePackerRk [above]
2. Extract imgRePackerRk
3. Open command prompt in directory containing imgRePackerRk.exe [hold shift, right click > "open command window here"]
4. Type "imgRePackerRk.exe {IMG_name}.img" [e.g. "imgRePackerRk.exe update.img"]
5. A new directory called "{IMG_name}.img.dump" [e.g. "update.img.dump"] will be created, containing individual IMGs (system.img)
2. [ON UBUNTU] Mount system.img on Ubuntu and mofify!
Code:
sudo mount -t ext4 system.img system-folder -o loop
2.1. [ON UBUNTU] Rooted Android Firmware.
We use SuperSU. You can get SU and BUSYBOX commands from another Android Distribution compatible with RK3188 devices.
In this case we obtained root commands bin/su bin/busybox and xbin/su Rocket 3188 firmware root tools:
RK3066/RK3188 Development Kitchen/Tool by Rockchipfirmware.com/TNT/FMA
You can also get su and busy box commands from:
Minix Neo X7 Custom Firmware
Code:
[email protected]:~/atv/rk3XXX_mod_tool/ref/bin# cp su ~/atv/system-folder/bin/
[email protected]:~/atv/rk3XXX_mod_tool/ref/bin# cp busybox ~/atv/system-folder/bin/
[email protected]:~/atv/rk3XXX_mod_tool/ref/xbin# cp su ~/atv/system-folder/xbin
Code:
#!/bin/bash
#add needed files
sudo cp -fap ~/atv/rk3XXX_mod_tool/ref/bin/su system-folder/bin/su
sudo cp -fap ~/atv/rk3XXX_mod_tool/ref/xbin/su system-folder/xbin/su
sudo cp -fap ~/atv/rk3XXX_mod_tool/ref/bin/busybox system-folder/bin/busybox
#set permissions
sudo chown root:root bin/su
sudo chmod 6755 bin/su
sudo chown root:root bin/busybox
sudo chmod 6755 bin/busybox
sudo chown root:root xbin/su
sudo chmod 6755 xbin/su
This is everything you need for rooting the system. Later you can download SuperSu from Android Play Store Official.
2.2.- [ON UBUNTU] Removed most Chinese and unnecessary or obsolete applications.]
Code:
system-folder/app/
Code:
rm -rf com.waxrain.airplayer-1.apk
rm -rf eHomeMediaCenter_box.apk
rm -rf Facebook_299369.apk
rm -rf flashplayer
rm -rf Music.apk
rm -rf QuickSearchBox.apk
rm -rf RkApkinstaller.apk
rm -rf RkExplorer.apk
rm -rf RKGameControlSettingV1.0.1.apk
rm -rf RkVideoPlayer.apk
rm -rf WifiDisplay.apk
rm -rf youtube_5.0.21.apk
If you really need some of these apps, I packet them into a zip file so you can install them easily as you need:
Download: Official Mygica Firmware Deleted Apps
2.3. [ON UBUNTU] Modify vold.fstab to mount external_sd to REAL sdcard, so you can get more space for your Apps.
VERY CAREFUL WITH THIS!! Just locate duplicate, comments old lines (for security) and modify:
Code:
/etc# vi /etc/vold.fstab
Code:
#dev_mount flash /mnt/sdcard auto /dev/block/mtd/by-name/user
#dev_mount sdcard /mnt/external_sd auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount flash /mnt/sdcard auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount sdcard /mnt/external_sd auto /devices/virtual/mtd/mtd9/mtdblock9
To make the externalised writable, you must edit "platform.xml", from "/etc/permissions" adding in "android.permission.WRITE_EXTERNAL_STORAGE" this: <group gid="media_rw" /> Like this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
2.4. [ON UBUNTU] FIX Youtube black screen (only audio) on build update.img (UPDATE 20131213)
Edit build.prop file, in order to fix Youtube black screen when playing videos:
Code:
sys.browser.use.overlay = 1
2.5. [ON UBUNTU] Umount Custom System folder (system.img) and copy again to Windows.
Umount system image (system.img) and copy back to windows machine, to repack with imgRePackerPk utility:
Code:
umount system-folder/
3. [ON WINDOWS] Build again the new custom firmware
How to repack a firmware IMG (Windows) [Assuming you have followed above to unpack]
1. Open command window in directory containing imgRePackerRk.exe and *.dump directory
2. Type "imgRePackerRk.exe {dump_name}.dump" [e.g. "imgRePackerRk.exe update.img.dump"]
3. New firmware IMG will be created [name will be name of .dump directory without .dump extension]
4. INSTALL ROM ON DEVICE (update.img)
Put the cooked update.img on USB or SDCard, and insert it on Mygica ATV580, then you can apply the update automatically. Your device will reboot and the firmware update will start. The Mygica Bootloader will search for a file called update.img automatically on external_sd micro sdcard. So you should have an micro sdcard inserted on the device.
IMPORTANT: If the Mygica Bootloader show an error like update.img not found when it try to start update process. Probably is because of switched external_sd with internal flash sdcard, probably the updater bootloader won't find the update.img firmware when reboot. This has a simple solution, just manually copy update.img to both, external_sd and sdcard directory. You should need an good tool like Solid Explorer (available en Android Play Store).
IMPORTANT: If the previous method doesn't help you to install the update.img. You can use an editor to switch back to the original mount external_sd and flash sdcard points in /etc/vold.fstab. You should revert the changes on this file. You should need an good tool like Solid Explorer (available en Android Play Store).
IMPORTANT: Before Install this Rooted Original Firmware, remember it is better to RESET DEVICE, so you can make a brand new install cleaning all data files from the previous firmware.
IN CASE OF EMERGENCY (ALTERNATIVES TO SAVE A BRICKED ATV580)!
In case of you brick your ATV580, there is a way to recover it from the dead... Using Android Recovery System. I don't have the full firmware ready for this, but I made some research about how create FLASEABLE ZIP IMAGES for Android Recovery System. So the trick is create a Flashable Zip with our native update.img firmware inside.
To start Android Recovery System, boot ATV580 use a simple clip putting it on a small hole button located an the bottom of the device and connect power supply at the same time during about 5 seconds. Then you can get into this mode, you can use your remote to navigate the menu. In this mode you can load Flasheable Zip loading this files from Computer to SDCARD reader and then to your device.
- Tools and Samples to Build a Flasheable Zip for Android Recovery System (Save your ATV580) rksigner_tazpown-20140324.zip -
This packet include a sample of flasheable zip for Mygica ATV580 that restore build.prop file from a damaged one, which causes the system boot loop and bricked.Just copy the signed Flasheable Zip and use System Recovery System to load it. This flasheable zip fix the system. If you know the problem or you have enough experience to put a right copy of update.img on Flasheable Zip, you can save any bricked or boot loop device, with this tools. You have more docs and information inside of this package.
Screenshots during the flashing process for the sample flashing included in the tools:
- Android Recovery System
- Android Recovery System Flashing my own Flasheable ZIP
Thanks! Dont Forget To PRESS THANKS Button :good:
If you like my work, please consider to invite me a cup of coffee here!
Hi! You really cool! Thanks a lot!
One question - do you fix it for supporting native 1080p resolution?
jalcot said:
Hi,
finally you can download or cook the PRE-ROOTED firmware for ATV580 (Mygica/Geniatech) Rockchip RK3188 ARM Cortex A9 x 4 CPU.
Thanks!
Click to expand...
Click to collapse
Many thanks for all the work!
I need rooted IMG file.. Somebody help me.. I don't have a PC to cook rom..thanks a lottt
Sent from my rk31sdk using Tapatalk
timothypham said:
I need rooted IMG file.. Somebody help me.. I don't have a PC to cook rom..thanks a lottt
Sent from my rk31sdk using Tapatalk
Click to expand...
Click to collapse
Be parient. I fixed the problem when swap sdcard and flash make it writable. but now I have another problem. When I move apps to SDcard these apps dissapear. I am working arround the solution.
I will get the ROM perfect very very soon.
jalcot said:
Be parient. I fixed the problem when swap sdcard and flash make it writable. but now I have another problem. When I move apps to SDcard these apps dissapear. I am working arround the solution.
I will get the ROM perfect very very soon.
Click to expand...
Click to collapse
Thanks for hard working jalcot. I'm waiting your room with root. I buy ATV580 3 months ago, and can't root it...wait your room.. Thanks again.
Sent from my rk31sdk using Tapatalk
jalcot said:
Be parient. I fixed the problem when swap sdcard and flash make it writable. but now I have another problem. When I move apps to SDcard these apps dissapear. I am working arround the solution.
I will get the ROM perfect very very soon.
Click to expand...
Click to collapse
Thanks for keeping working on it!
Jalcot...where are you... I still waiting you...
Sent from my rk31sdk using Tapatalk
timothypham said:
Jalcot...where are you... I still waiting you...
Sent from my rk31sdk using Tapatalk
Click to expand...
Click to collapse
Yes, thank you for your patient... I've worked hard to cook a perfect clean ROM...
pokatusher said:
Hi! You really cool! Thanks a lot!
One question - do you fix it for supporting native 1080p resolution?
Click to expand...
Click to collapse
Yes! With the new XBMC Gotham Beta I was watching MKV 1080p Movies on my home streaming.
Jalcot...love you so much..you save my Atv... i hate Android no root... i will download rom tonight... thanks your hard work...thank Jalcot again....
Sent from my HTC Sensation using Tapatalk
Great rom Jalcot...thanks so muchhhhhh
Sent from my rk31sdk using Tapatalk
---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------
I can't use Phone Remote Control Service .. Are you remove it, Jalcot
Sent from my rk31sdk using Tapatalk
timothypham said:
Great rom Jalcot...thanks so muchhhhhh
Sent from my rk31sdk using Tapatalk
---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------
I can't use Phone Remote Control Service .. Are you remove it, Jalcot
Sent from my rk31sdk using Tapatalk
Click to expand...
Click to collapse
I think so... It is RKGameControlSettingV1.0.1.apk or maybe eHomeMediaCenter_box.apk?
Don't worry, I packed all deleted official apps from the Original Firmware so you can install them easily as you need... You can download them.
Thank so much.. Jalcot..
Sent from my rk31sdk using Tapatalk
I need CWM to install some MOD... Where got it, Jaclcot
Sent from my rk31sdk using Tapatalk
jalcot said:
Yes! With the new XBMC Gotham Beta I was watching MKV 1080p Movies on my home streaming.
Click to expand...
Click to collapse
Launch Antutu and see in System Information real resolution of output, please.Or install small ultility like this and send screenshot
Help me..
Jalcot... can you help me.. plz reup stock firmware for me..
I install PurePerfomes and big bug.. No wifi, no Ethernet detected.. I rollback to your rom but it still bug.. no wifi, no Ethernet... i can't do anything... i hope instal stock firmware will save me...
I can't reinstall your ROM.. I restore factory but it nothing fix.. WiFi and Ethernet is gone... With with me hixhix
Sent from my HTC Sensation using Tapatalk
Everything I have... Not file browser... My ATV is die...
Sent from my HTC Sensation using Tapatalk
Love the clean rooted Rom, many thanks!
Also great job on the internal/external card swap
Gotham latest nightly is still choppy with 1080p content I have but Beyond xbmc 3.3 works great
Thanks Jalcot!
Related
This is how I made ROM, I'll try to write the steps as simple as I can. For advanced users only!
Update 22/08/11:
Revised packaging steps.
Update 13/08/11:
Removed unwanted method for ROM cooking.
Update 04/08/11:
Modified extract and repack ROM guide and added extracting system.rfs guide.
Things you need:
Base firmware
Archiver software (7zip recommended)
Any Linux environment to build ROM or Cygwin
APK Manager to optimize and decompile *.apk files
MagicISO (Optional) if you want to extract system.rfs
And the last thing is... You need enough experience in android world
So, here is the steps to cook a ROM:
Flash your phone with your desired base firmware
Make required modifications
Pull system.rfs from your phone by running this command on adb shell or Terminal Emulator:
Code:
dd if=/dev/stl12 of=/sdcard/system.rfs
Extract any *.tar.md5 files from your base firmware to your working folder with 7zip
Replace the current system.rfs with your modified one
EDIT: Pack your ROM by running this code via terminal or just pack it with 7zip/WinRAR as *.tar
Code:
tar -H ustar -c * >> ROMNAME.tar
change ROMNAME to your desired, well, ROM name.
Here is (yet) useful guide to modify your ROM.
Extract system files on system.rfs to make modding easier:
Extract PDA file (*.tar.md5) files with 7zip
Open system.rfs with MagicISO
To extract it, just drag and drop
NOTE: Never edit your ROM with MagicISO because the file permissions will be ignored, use MagicISO only for extracting files from system.rfs
Deodex, and Zipalign (optimize) your ROM apk files:
Ready to use deodex + root for KPN: http://forum.xda-developers.com/showthread.php?t=1196230
Ready to use deodex + root for KPH and other firmware: http://forum.xda-developers.com/showthread.php?t=1118048
Open APK Manager
To zipalign your apk files, in apk manager folder /place-apk-here-to-batch-optimize put your:
framework-res.apk, twframework-res.apk and all system apk
but not these:
AxT9IME, Calculator, Camera, Email, MMS, Phone, Screen Capture, Settings, Swype, Thinkdroid, Voice search
Choose Choose option 15
Then choose both (zp)
Let it run and done.
Now put back the apk files where they belong in the ROM.
How to put these apk files to my ROM? Copy these files to appropriate locations, such as /system/app to your ROM's /system/app, and etc.
Another handy modification guide:
Unpack and repack boot.img - http://forum.xda-developers.com/showthread.php?t=1173427
Convert firmware filesystem to ext4 - http://forum.xda-developers.com/showthread.php?t=1202049
Overscroll glow for any firmware - http://forum.xda-developers.com/showthread.php?t=1215933"
Give thanks to all dev who made that possible!
If you have more guides to put here, please PM me.
Am I pertamax?
hehe..just kidding.
Nice Info....great share.
I would want the Fla.sh Rom :'(
Thats a gr8 share...Thank you...)
saiftheboss7 said:
I would want the Fla.sh Rom :'(
Click to expand...
Click to collapse
sorry... once again, I'm sorry, I can't continue my ROM
Helpful thread man!
Thanks!
Great job taking your time to make this! Unfortunately, i dont even know the basics but now I know where to check when I do
fla.sh said:
sorry... once again, I'm sorry, I can't continue my ROM
Click to expand...
Click to collapse
Hey!
THX man, nice thread. Very useful!
Just PM to MOD, that they close you previous thread, a bout fla.sh.ROM. Or ppl just waiting it and asking.
CHEERS!
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
an0nym0us_ said:
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
Click to expand...
Click to collapse
Just save it.
didnt work when i just save it. my device got bootloop
an0nym0us_ said:
didnt work when i just save it. my device got bootloop
Click to expand...
Click to collapse
What modification you've added to your ROM? Maybe that modification causing the problem...
fla.sh said:
What modification you've added to your ROM? Maybe that modification causing the problem...
Click to expand...
Click to collapse
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
ketut.kumajaya said:
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
Click to expand...
Click to collapse
I use this command to mount rfs:
Code:
mount -o loop system.rfs /some_dir
Can you share us the command?
now thats really informative. thanks
ROM unpacking and repacking gude has been corrected. Tested by me. If you have any problems, just ask here.
Thanks.
I think you should add the date of update in the title, so that everyone can know about the update...
BTW thanks for this amazing guide...
Love it!!!
After making changes to system.rfs, how to save it as .rfs again?
adiles said:
After making changes to system.rfs, how to save it as .rfs again?
Click to expand...
Click to collapse
Please take look at the first page, it's updated, you know?
After I created md5 file and selected it in odin, it says "invalid image type" and "invalid model binary". How to solve that? After that I continued, skipped these errors and flashed, my phone stopped at boot screen with text "Galaxy ACE....". Plz help me
Things you need:
Base firmware (i'm use Gingerbread S5830SERKPH 2.3.4)
Windows (I'm use windows 7 X64 service pack 1)
Linux (Ubuntu recommended)
And the last thing is, You need enough experience in android world
step-step :
Flash your phone with your desired base firmware.
Make required modifications at your phone.
After that, do hard reset to your phone.
Next back up system.rfs .
put system.rfs with boot.img, data.rfs, recovery.img from PDA base firmware in one folder.
After that, repack your custom rom.
what should we do to modify it :
Remove useless widgets
Add more apps
Change theme
How to back up System.rfs :
Download at market "terminal emulator"
next run this code:
Code:
su
dd if=/dev/stl12 of=/sdcard/system.rfs
How to hard reset your phone :
Move by root explorer your modification apps to system/app then change permission like this :
Code:
User:Read, Write
group:Read
Others:Read
Next change the owner to "root" by root explorer
At least boot into recovery mode "HOME+POWER" and choose "wipe data/factory reset" be sure your contact data already backup
How to repack your custom rom :
PDA by running this code via terminal at linux:
Code:
tar -H ustar -c boot.img recovery.img data.rfs system.rfs >> ROMNAME.tar
md5sum -t ROMNAME.tar >> ROMNAME.tar
mv ROMNAME.tar ROMNAME.tar.md5
change ROMNAME to your desired, of course, ROM name.
If you want to build One-Package ROM, just use 1st and 2nd command and don't forget to include all files on all *.tar.md5 (such as modem, csc, apboot) like this :
Code:
tar -H ustar -c *.* >> ROMNAME.tar
md5sum -t ROMNAME.tar >> ROMNAME.tar
How to change your rom name :
At root explorer you see at folder system "build.prop"
Open it in text editor edit "ro.build.display.id=GINGERBREAD.XXKPH" with your rom name
Another Handy Modification Guide:
How to edit system.rfs on your Pc :
importan : if you want to edit system.rfs at windows, DON'T use Magic Iso, why? because i was use it, then my system.rfs corrupt.
you must have linux (ubuntu recommended)
run it from terminal :
Code:
sudo mount -o loop system.rfs /some_dir
make required modification
then Unmount it
How to Unpacking & repacking the image :
Note: below I give you the details for unpacking and repacking manually, but I have attached two perl scripts that do most of this for you
If you are good with a hex editor, you can open up any of these images and strip off the first 2k of data. Then, look for a bunch of zeroes followed by the hex 1F 8B (which is the magic number of a gzip file). Copy everything from the first line of the file, through the zeroes, and stopping at the 1F 8B. That is the kernel. Everything from the 1F 8B through the end is the ramdisk. You could save each of these files separately. In order to see the contents of the ramdisk, you need to un-gzip it and then un-cpio it. You could use a command like this (ideally after creating a new directory and cd'ing into it):
Code:
gunzip -c ../your-ramdisk-file | cpio -i
That will place all of the files from the ramdisk in your working directory. You can now edit them.
In order to re-create the ramdisk, you need to re-cpio them and re-gzip those files, with a command like the following (remember, cpio will include everything in the current working directory, so you probably want to remove any other cruft you might have in there):
Code:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
The final step is to combine the kernel and your new ramdisk into the full image, using the mkbootimg program (which you should download and compile from the git repository):
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel your-kernel-file --ramdisk newramdisk.cpio.gz -o mynewimage.img
Now, there's a lot of hassle in pulling apart files in hex editors and remembering all of these commands, so I wrote unpack and repack perl scripts for you (attached). Hooray.
How to Manually deodex your phone :
What you'll need:
xUltimate v2.2
Unzip xUltimate v2.2, and launch "Main.exe"
If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
Run option 1. After option 1 is done, run option 2.
Now these well take a while. Run option 3.
IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
Now run option 4, and wait.
Exit xUltimate, and put the phone in USB mass storage.
Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
Put the phone in PC mode
Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Your phone should now be deodexed!
You may notice an increase in speed, and you now have the ability to edit certain files with greater effects.
How to change bootanimation :
using a Root explorer goto the /system/media directory.
Copy bootanimation.zip to your SD Card.
Connect your droid to your computer with usb and mount the SD Card
Copy bootanimation.zip to your computer.
extract bootanimation.zip to a folder
Inside you will find 2 folders with all the individual PNG files in them.
With photoshop or paint modify the png files to add your custom graphics, OR make/download your own pictures. (Make sure they are match with your phone device)
Highlight the two folders and the desc file.
Right click the highlighted files.
Select add files to archive.
Select Zip check box
In the compression method drop down box select Store. (this is key if you dont do this it wont play the animation)
save the archive as bootanimation.zip
copy the new bootanimation.zip to your SD Card
Select the bootanimation.zip file from your SD Card and move it... system>media>paste
________________
i'm just 12 years old if i can do it, why you can't
Advantages of this way is :
More efficient
Reduce your internet usage (dont need kitchen, apk manager, etc)
Easy to modification (You can see the direct result)
Reduce your time (only 2 hours i can do this way)
More soon
You steal my IDEAS Univos! No, just kidding, there are incorrect guide on "how to hard reset" lol. Anyway, try to build a ROM before creating this guide, my friend.
Wow Kids!
are doing development now a days
fla.sh said:
You steal my IDEAS Univos! No, just kidding, there are incorrect guide on "how to hard reset" lol. Anyway, try to build a ROM before creating this guide, my friend.
Click to expand...
Click to collapse
im not steal it.
Where is incorrect guide i'm try to fix it?
Sent from my GT-S5830 using XDA App
GadgetCheck said:
Wow Kids!
are doing development now a days
Click to expand...
Click to collapse
Thanks
Sent from my GT-S5830 using XDA App
This guide tested by me, and i have get result from this.
Sent from my GT-S5830 using XDA App
If you have question just ask me!
Sent from my GT-S5830 using XDA App
I think this guide is the same with fla.sh's guide.
devilsking said:
I think this guide is the same with fla.sh's guide.
Click to expand...
Click to collapse
Different, Fla.sh make guide for cooking his rom.
in this thread i tell you how to make your own custom rom.
with Phone device Samsung Galaxy Ace.
Univos said:
Different, Fla.sh make guide for cooking his rom.
in this thread i tell you how to make your own custom rom.
with Phone device Samsung Galaxy Ace.
Click to expand...
Click to collapse
ya ya. I see tks for your guide
devilsking said:
ya ya. I see tks for your guide
Click to expand...
Click to collapse
Please press thanks button, if i helped you
Sent from my GT-S5830 using XDA App
Univos said:
This guide tested by me, and i have get result from this.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
EmoBoiix3 said:
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
Click to expand...
Click to collapse
Just kept reading, ask people, don't feel has a lot of knowledge, kept countinue to learn
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
Click to expand...
Click to collapse
Maybe this holiday i will developt a simple custom rom.
Sent from my GT-S5830 using XDA App
Univos said:
Maybe this holiday i will developt a simple custom rom.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I am thinking about a kid with two or more different XDA ID.
ketut.kumajaya said:
I am thinking about a kid with two or more different XDA ID.
Click to expand...
Click to collapse
No, the real name Fla.sh is "Aver..." my real name is "iz..." we are student of junior high school at surabaya. I'm "Aver..." friend.
Sent from my GT-S5830 using XDA App
Univos said:
No, the real name Fla.sh is "Aver..." my real name is "iz..." we are student of junior high school at surabaya. I'm "Aver..." friend.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I'm swear.
Sent from my GT-S5830 using XDA App
ketut.kumajaya said:
I am thinking about a kid with two or more different XDA ID.
Click to expand...
Click to collapse
ROFLAMO
Jukirdolly said:
ROFLAMO
Click to expand...
Click to collapse
??????
Sent from my GT-S5830 using XDA App
Hi all. If anyone is willing to help please assist me, im currently trying to upload cm 7 Morrison files for our beloved Ruth devices. I still haven't figured out how the 2nd init injector works yet.
For all charm users we can always branch the files and delete the MOTO.ROTATOR line for your devices.
If you have time, patients and sh¡t loads of guts please help or add links for me to checkout.
EVEYTHING IS APPRECIATED! :fistbump:
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Ok if anyone know of any other motorola developers please let me know.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
ruth(MB511) sensors in init.mapphone30_umts.rc
# sensor interface
chown compass compass /dev/lis331dlh --> not found
chmod 660 /dev/lis331dlh
chown compass compass /dev/kxtf9 --> found
chmod 660 /dev/kxtf9
chown compass compass /dev/akm8973 --> not found
chmod 660 /dev/akm8973
chown compass compass /dev/sfh7743 --> found
chmod 660 /dev/sfh7743
chown compass compass /dev/akm8973_dev --> found
chmod 660 /dev/akm8973_dev
chown compass compass /dev/akm8973_aot --> found
chmod 660 /dev/akm8973_aot
chown compass compass /dev/airc --> not found
chmod 660 /dev/airc
so ruth(MB511) sensors should be /dev/kxtf9, /dev/sfh7743,/dev/akm8973_dev, /dev/akm8973_aot
but Morrison sensors in libsensors/nusensors.h
#define AKM_DEVICE_NAME "/dev/akm8973_aot"
#define ACCEL_MODE_NAME "/sys/class/i2c-adapter/i2c-0/0-0018/mode"
#define CM_DEVICE_NAME "/dev/proximity"
#define LS_DEVICE_NAME "/dev"
#define LIS_DEVICE_NAME "/dev/lis331dlh"
I think porting Morrison maybe less suitable for ruth
Thanks phc, and yes I know its a long shot, I still haven't gotten to the lib files, let alone hardware. But morrison IS the closest port for us. All the other devices are to advanced for the device. Do a compare between the two, ram is almost identical, chips are close, gpu aswell. Only thing that isnt is screen size. Thanks for the lost, it will come in handy later.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Hi,
I used jordan-common and MagicDevTeam's MB508([h t t p s : / / github.com/MagicDevTeam) files,
and compiled eclair AOSP to check different files than create ruth device files.
My ROM VERSION:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
My ruth configure files: ruthconfigureforcm7.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqQUlWTWI3SURGU1U/edit)
https://github.com/phchshow/android_device_motorola_ruth
My unstable update file:v0.1.5.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqaXNzRVJDSU95Slk/edit)
V0.5.0.zip
can work:
battd[2013/03/14]
bluetooth
half work:
audio->media codec can't use.
[2013/03/19]solved some media codec running problem, but video recorder codec still has problem (even use low quality).
[2013/03/23]only mp3 and jpg codec is ok, orthers codec has problem, unknow how to solved...
sensors.
fmradio->FMRadioService.apk can't use, but can purchase "Spirit FM Radio Unlocked" to use.[2013/03/15]
camera->[2013/03/18]replace to use MB508's libcamera.so and libcameraservice.so. can take a picture, but media codec has some problem, so can't photograph.
wifi->[2013/03/23]dhcp has problem, but use command to execute is ok.
use mb508's bootmenu/2nd-init/init, solve setprop question, now wifi is OK.
but no softap beacuse can't compile tiap_drv.ko with 2.6.29 kernel.
ril->[2013/03/25]can call, but no sound, seems like audio codec problem.
not work:
battd->log say INIT BATTD SOCKET SERVER: failed. unknow how to solve. update[2013/03/14]:chmod cpcap permission
camera->used mb508's camera library, log say "mapped at 0x4103c000, not at 0xa7900000" can not load library
used ruth camera library, log say CAMERA HAL not support. unknow how to solve.
radio. unknow how to solve.
wifi->when process step 2, /system/bin/wlan_loader -f /system/etc/wifi/fw_wlan1271.bin -i /system/etc/wifi/tiwlan.ini -e /pds/wifi/nvs_map.bin
failed. [2013/03/16]get new question Failed to start supplicant daemon.unknow to solve.
[2013/03/23]gps->Failed to enable location provider
forget test:
fmradio, gps
phchshow said:
Hi,
I used jordan-common and MagicDevTeam's MB508([h t t p s : / / github.com/MagicDevTeam) files,
and compiled eclair AOSP to check different files than create ruth device files.
My ROM VERSION:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
My ruth configure files: ruthconfigureforcm7.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqQUlWTWI3SURGU1U/edit)
My unstable update file:v0.1.5.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqaXNzRVJDSU95Slk/edit)
can work:bluetooth
halt work:
audio->media codes can't use.
sensors.
not work:
battd->log say INIT BATTD SOCKET SERVER: failed. unknow how to solve.
camera->used mb508's camera library, log say "mapped at 0x4103c000, not at 0xa7900000" can not load library
used ruth camera library, log say CAMERA HAL not support. unknow how to solve.
radio. unknow how to solve.
wifi->when process step 2, /system/bin/wlan_loader -f /system/etc/wifi/fw_wlan1271.bin -i /system/etc/wifi/tiwlan.ini -e /pds/wifi/nvs_map.bin
failed. unknow to solve.
forget test:
fmradio, gps
Click to expand...
Click to collapse
How are you flashing the update.zip files, my phone doesnt seem to respond to any of the changes.
hsr0 said:
How are you flashing the update.zip files, my phone doesnt seem to respond to any of the changes.
Click to expand...
Click to collapse
you can use charm Big Bootstrapped Recovery Update to update.
or use bootmenu to update.
update:
if you want use bootmenu,
you can unzip my update zip (v0.1.5.zip).
WARNING: if step fails, may be need reinstall the system. BE CAREFUL.
1. remount system (root)
mount -o remount,rw / /system
2. push bootmenu files
adb push v0.1.5/system/bin/bootmenu /system/bin/
adb push v0.1.5/system/bootmenu /system/bootmenu
3. chmod files permisson (root)
chmod 0755 /system/bin/bootmenu
chmod 0755 /system/bootmenu/binary/*
chmod 0755 /system/bootmenu/script/*
chmod 0755 /system/bootmenu/recovery/sbin/*
4. change mot_boot_mode(original motorola file) (root)
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
5. edit mot_boot_mode (root) update(2013/02/08)
/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode
#!/system/bin/sh
export PATH=/system/bin:$PATH
/system/bin/bootmenu
mot_boot_mode.bin
6. chmod mot_boot_mode permission (root)
chmod 0755 /system/bin/mot_boot_mode
7. reboot and click click click(loop) "vol down" key until show bootmenu screen
Can you post just the bootmenu files?
I have already tried your steps twice but soft bricked the phone.
hsr0 said:
Can you post just the bootmenu files?
I have already tried your steps twice but soft bricked the phone.
Click to expand...
Click to collapse
OK. I re-installed system. And write script name mkbootmenu.sh
unzip bootmenuDIR.zip
adb push bootmenuDIR/bootmenu /sdcard/bootmenu
adb push bootmenuDIR/mkbootmenu.sh /sdcard
in phone side:
$su
#sh /sdcard/mkbootmenu.sh
#reboot
when MOTO LOGO click click click (loop) "VOL - " (VOL DOWN) until show bootmenu screen
NOTICE: only new system or never changed mot_boot_mode can run this script .
thank you very much, it worked!
However I still do not know why it did not run when I executed it although I did a fresh install with RSD lite.
Maybe because I used windows to create mot_boot_mode file, maybe some character issues occured.
but once again thank you!
Will check it in the morning, so far i've modded most of the make files for CM9 and my only worry is the framework.apk but so far so good :thumbup:
Almost forgot! The 2nd init and a modified boot kernel will be the biggest problems.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
https://github.com/plageran/ruth
Good job, man
My Flipout is waiting for a stable CM
ruth device cpu and gpu
As far as I know, flipout and charm have OMAP 3410 CPU inside, this CPU DOESN'T include GPU. Others like OMAP 3430 in Milestone 1 does include Imagination PowerVR SGX535 GPU.
Please check this location on your device with a root explorer app:
/system/lib/egl/
and in there you will find your gpu drivers, also most phones do have gpu's although it only helps the device a little bit.
I know my device has atleast 3 .so files in there and I think thats android drivers. I must just figure out if it should be recompiled for newer versions of android.
xinbada007 said:
As far as I know, flipout and charm have OMAP 3410 CPU inside, this CPU DOESN'T include GPU. Others like OMAP 3430 in Milestone 1 does include Imagination PowerVR SGX535 GPU.
Click to expand...
Click to collapse
Hijack
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
phchshow said:
you can use charm Big Bootstrapped Recovery Update to update.
or use bootmenu to update.
update:
if you want use bootmenu,
you can unzip my update zip (v0.1.5.zip).
WARNING: if step fails, may be need reinstall the system. BE CAREFUL.
1. remount system (root)
mount -o remount,rw / /system
2. push bootmenu files
adb push v0.1.5/system/bin/bootmenu /system/bin/
adb push v0.1.5/system/bootmenu /system/bootmenu
3. chmod files permisson (root)
chmod 0755 /system/bin/bootmenu
chmod 0755 /system/bootmenu/binary/*
chmod 0755 /system/bootmenu/script/*
chmod 0755 /system/bootmenu/recovery/sbin/*
4. change mot_boot_mode(original motorola file) (root)
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
"5. edit mot_boot_mode (root)
vi /system/bin/mot_boot_mode "
#!/system/bin/sh
export PATH=/system/bin:$PATH
/system/bin/bootmenu
mot_boot_mode.bin
6. chmod mot_boot_mode permission (root)
chmod 0755 /system/bin/mot_boot_mode
7. reboot and click click click(loop) "vol down" key until show bootmenu screen
Click to expand...
Click to collapse
plageran said:
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
Click to expand...
Click to collapse
He basically rewrote the boot script, so while booting up, it opens the bootmenu script and only then does it do a regular boot..
The normal 2nd init installer don't invoke the boot script in the same way I guess and hence it doesn't work.
Well now since bootmenu works, its like a torchlight in an otherwise dark tunnel.
Another point I want to make is that the flipout cm7 update given is in a bootloop. probably I need to change the files for basil (charm).
I think bootloop is audio device (libaudio.so) error. Maybe like when I use MB508's libcamera.so the message log show "mapped at .... " can't load library.
So should be use charm's libaudio.so to recompile CM7 sources. But maybe make some error, like media codec can't use.
hsr0 said:
He basically rewrote the boot script, so while booting up, it opens the bootmenu script and only then does it do a regular boot..
The normal 2nd init installer don't invoke the boot script in the same way I guess and hence it doesn't work.
Well now since bootmenu works, its like a torchlight in an otherwise dark tunnel.
Another point I want to make is that the flipout cm7 update given is in a bootloop. probably I need to change the files for basil (charm).
Click to expand...
Click to collapse
---------- Post added at 10:55 PM ---------- Previous post was at 10:34 PM ----------
The 5 step should be
"/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode", I forgot no install busybox no vi.
Defy use logwrapper to hijack, but flipout can't.
I think flipout processed init have not execute logwrapper, let we can't hijack logwrapper.
But mot_boot_mode executed.
So I rename mot_boot_mode to mot_boot_mode.bin and write new script name mot_boot_mode. Make bootmenu can execute.
And modify init.mapphone30_umts.rc
"exec /system/bin/mot_boot_mode" to "exec /system/bin/mot_boot_mode.bin", make 2nd-init can success execute init files.
In My uploaded bootmenuDIR.zip, the 2nd-init directory is modify for eclair to use.
You can modify eclair init files to test 2ndinit.
plageran said:
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
Click to expand...
Click to collapse
What I've learned so far is that most motorola's have the hijacked kernel from the original device, I'm not sure up to what level of Android os this works but if you dig deep enough. Its all almost the same to stock.
I hope you don't mind me using your scripts for my rom, this changed things big time.
Now to get my build machine up and running and to finish my LIB list for CM
edit: has anyone figured out the fingerprint system yet? I haven't found anything about it yet, whether it's generated or copied over.
phchshow said:
I think bootloop is audio device (libaudio.so) error. Maybe like when I use MB508's libcamera.so the message log show "mapped at .... " can't load library.
So should be use charm's libaudio.so to recompile CM7 sources. But maybe make some error, like media codec can't use.
---------- Post added at 10:55 PM ---------- Previous post was at 10:34 PM ----------
The 5 step should be
"/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode", I forgot no install busybox no vi.
Defy use logwrapper to hijack, but flipout can't.
I think flipout processed init have not execute logwrapper, let we can't hijack logwrapper.
But mot_boot_mode executed.
So I rename mot_boot_mode to mot_boot_mode.bin and write new script name mot_boot_mode. Make bootmenu can execute.
And modify init.mapphone30_umts.rc
"exec /system/bin/mot_boot_mode" to "exec /system/bin/mot_boot_mode.bin", make 2nd-init can success execute init files.
In My uploaded bootmenuDIR.zip, the 2nd-init directory is modify for eclair to use.
You can modify eclair init files to test 2ndinit.
Click to expand...
Click to collapse
hey dude, r you guys still working on flip/charm? any progress to share?
xinbada007 said:
hey dude, r you guys still working on flip/charm? any progress to share?
Click to expand...
Click to collapse
keep an eye on our github pages, i can only update monthly due to cost's. Still need to get and build my build machine lol!
Hi,
For everyone Using the Samsung Galaxy Grand I9082 Here is a way to Root your Phone without Increasing the BIN Counter. In the Second Post I am posting the Steps for advanced Users on how to do it yourselves.
In the Third Post I am posting a pre-rooted Firmware for people Who just want to root the Phones Without all the Headache for Creating their Own.
Be Advised that even though this will Not increase the Bin Counter it is still advised to Flash a Stock Firmware when Claiming warranty.
For those who want to know the Procedure
Requirements
1) Linux (Preferably Ubuntu)
2) An Official Firmware tar (Search http://www.sammobile.com/firmwares/)
3) SU Binary and Ext4uils (Attached)
4) Patience
5) Windows (To use ODIN)
6) ODIN (To Flash)
Flash the Firmware through ODIN First so that there are no Firmware Mis-matches later.
Steps:
1)Create a "sam" directory in your Home Directory (home/username) folder where username is your linux username.
2)Extract the downloaded firmware, then move system.img and cache.img to home/username/sam dir
3)Extract su.zip and ext4utils.zip in the same folder where you have system.img and cache.img.
4)Open a terminal window, and enter:
Code:
mkdir /home/username/sam/system
sudo –i (this will ask for password..Enter your Root password)
apt-get install zlib1g-dev
cd /home/username/sam
make
mv system.img system2.img
./simg2img system2.img system.img
mount system.img system
Copy the su binary to the mounted folder
Code:
cp su system/bin/su
Give the Binary the Required Permission
Code:
chown root:root system/bin/su
chmod 06755 system/bin/su
Code:
./mkuserimg.sh -s sam ./new_system.img ext4 ./temp 1511M
Now unmount the system File and delete it
Code:
umount system
rm system.img
Rename new_system.img to system.img
Code:
mv new_system.img system.img
Now Create a flashable tar:
Code:
tar cf rooted.tar system.img
Now you need to tar the cache.img file we copied as well.
Code:
tar cf cache.tar cache.img
All Done. Now you can Flash them through ODIN.
In ODIN only Auto reboot and F. Reset Time should be checked
In PDA select: rooted.tar
In CSC select: cache.tar
After the phone Boots Download the Superuser app through Play Store.
Now you have root and No Increase in Bin Counter.
I am not that good at explaining.Incase of Question please ask them here or PM me
Also Please Consider Donating to Support My Work
For those who Just want to root.
Here i am Posting the Pre-Modded Firmware.The firmware is based on I9082XXAMB3_I9082ODDMB2_INU.zip
If you are on a different firmware then please download the firmware and Flash through ODIN.Link for the Official Firmware is:
http://uppit.com/46oxsxob7re3
Also Download the Pre-rooted firmware as well.It is in 3 parts so you need to Download all three.Also Download 7zip to extract the files.
Links for the files are:-
1) https://www.dropbox.com/s/9jh9yi88yuz49hr/Samsung Rooted.7z.001
2) https://www.dropbox.com/s/g1rk1qfuk440839/Samsung Rooted.7z.002
3)https://www.dropbox.com/s/1ej082e1z4ipqwc/Samsung Rooted.7z.003
right click on Samsung Rooted.7z.001 ->7zip ->Extract.
Wait for it to Extract
Open the extracted folder.there will be 2 files:-
1)rooted_system.tar
2)csc.tar
open ODIN:
In PDA select rooted_system.tar
In CSC select csc.tar
and Flash it.Wait for the Phone to start.once it Starts go to the Play Store and download the superuser app.
All done now you have a rooted phone Without increasing the BIN Counter
I am not good at explaining. Incase of any problems post here or Send me a PM.
Also Please Consider Donating to Support My Work
Another one
Just in case
Last Reserve
Does root package.zip refer to su zip???
How do I get CWM??
Also if I already have bin count (5 in my case)..does it reset it or stay as it is??
Sent from my GT-I9082 using xda premium
Ambarishbakre said:
Does root package.zip refer to su zip???
How do I get CWM??
Also if I already have bin count (5 in my case)..does it reset it or stay as it is??
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
I have the same questions.
BTW, thank you. I wish I had this method earlier, before I bumped up my bin counter.
Sent from my GT-I9082 using Tapatalk 2
manasgirdhar said:
Hi,
For everyone Using the Samsung Galaxy Grand I9082 Here is a way to Root your Phone without Increasing the BIN Counter. In the Second Post I am posting the Steps for advanced Users on how to do it yourselves.
In the Third Post I am posting a pre-rooted Firmware for people Who just want to root the Phones Without all the Headache for Creating their Own.
Be Advised that even though this will Not increase the Bin Counter it is still advised to Flash a Stock Firmware when Claiming warranty.
Click to expand...
Click to collapse
Hi,
I have already rooted my device b4, and my if I flash back with original samsung firmware, will it reset bin back to original ?
And then i can i use your procedure, would it work?
Please explain.
Thanks
Ambarishbakre said:
Does root package.zip refer to su zip???
How do I get CWM??
Also if I already have bin count (5 in my case)..does it reset it or stay as it is??
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Yes root package refers to SU Zip and it is not flashable..it is to be included if creating a pre-rooted firmware.No it wont Flash CWM.And no it wont reset the counter.
This is basically for people who have not yet rooted their Device or for people who dont want to increase their counter.
Hey bro can u provide the link gor multiwindow manager'
Sent from my GT-I9082 using Tapatalk 2
yuvi123456 said:
Hey bro can u provide the link gor multiwindow manager'
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Here You go:
http://forum.xda-developers.com/showthread.php?t=2079807
chotu222 method is the best because it also helps in addons of him as well as CWM
It is not about rooting a device, it is about the ROM that we are going to get as well as many other features.I am sure he is going to figure out a way to reset bin counter.
respect
conanFX said:
chotu222 method is the best because it also helps in addons of him as well as CWM
It is not about rooting a device, it is about the ROM that we are going to get as well as many other features.I am sure he is going to figure out a way to reset bin counter.
Click to expand...
Click to collapse
chottus method might be the best , but respect the developer and it is not an easy task...this method allows you too root without voiding the warranty
if this doesn't benefit you.. don't discourage the developer bro:good:
conanFX said:
chotu222 method is the best because it also helps in addons of him as well as CWM
It is not about rooting a device, it is about the ROM that we are going to get as well as many other features.I am sure he is going to figure out a way to reset bin counter.
Click to expand...
Click to collapse
Actually we can have Features without custom recovery as well.At the Moment there is no Custom ROM so it makes no point in Increasing the Counter.And What if someone has to submit his phone at the service center before we can reset BIN Counter?
There are a lot of things to consider when dealing with a samsung Phone.Anyway..If you dont like it then dont use it.
how to unroot galaxy grand??
shahid9695 said:
how to unroot galaxy grand??
Click to expand...
Click to collapse
download frimware from sammobile.com flash with odin 3.04
Sent from my GT-I9082 using xda premium
What about TriangleAway? http://forum.xda-developers.com/showthread.php?t=1494114
Links are not working........
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
manasgirdhar said:
For those who want to know the Procedure
Requirements
1) Linux (Preferably Ubuntu)
2) An Official Firmware tar (Search http://www.sammobile.com/firmwares/)
3) SU Binary and Ext4uils (Attached)
4) Patience
5) Windows (To use ODIN)
6) ODIN (To Flash)
Flash the Firmware through ODIN First so that there are no Firmware Mis-matches later.
Steps:
1)Create a "sam" directory in your Home Directory (home/username) folder where username is your linux username.
2)Extract the downloaded firmware, then move system.img and cache.img to home/username/sam dir
3)Extract su.zip and ext4utils.zip in the same folder where you have system.img and cache.img.
4)Open a terminal window, and enter:
Code:
mkdir /home/username/sam/system
sudo –i (this will ask for password..Enter your Root password)
apt-get install zlib1g-dev
cd /home/username/sam
make
mv system.img system2.img
./simg2img system2.img system.img
mount system.img system
Copy the su binary to the mounted folder
Code:
cp su system/bin/su
Give the Binary the Required Permission
Code:
chown root:root system/bin/su
chmod 06755 system/bin/su
Code:
./mkuserimg.sh -s sam ./new_system.img ext4 ./temp 1511M
Now unmount the system File and delete it
Code:
umount system
rm system.img
Rename new_system.img to system.img
Code:
mv new_system.img system.img
Now Create a flashable tar:
Code:
tar cf rooted.tar system.img
Now you need to tar the cache.img file we copied as well.
Code:
tar cf cache.tar cache.img
All Done. Now you can Flash them through ODIN.
In ODIN only Auto reboot and F. Reset Time should be checked
In PDA select: rooted.tar
In CSC select: cache.tar
After the phone Boots Download the Superuser app through Play Store.
Now you have root and No Increase in Bin Counter.
I am not that good at explaining.Incase of Question please ask them here or PM me
Also Please Consider Donating to Support My Work
Click to expand...
Click to collapse
I tried this procedure....flashed it and yes it has no bin count. BUT still showing SYSTEM CUSTOM. Perhaps in the next version this will be solved. Thanks for the effort. I would have donated if not for this.
Futhermore:
./mkuserimg.sh -s sam ./new_system.img ext4 ./temp 1511M
Click to expand...
Click to collapse
sam should be replaced by
/home/username/sam/system
Click to expand...
Click to collapse
At first it tried to follow this guide (especially the video linked from there) to flash, but with the update to 5.1.2 much of the bootloader functionality needed for rooting/flashing seems to be locked by amazon so that the root process of the SuperTool (Version from March 12th 2016, the MD5 of the AmazonFire5thGenSuperTool.zip was 8d813f3eacef9e932af5c366769b505e, not the one given on the download page where the file came from) failed.
So following the recommendation from here I tried to use KingRoot for rooting.
Rooting
I downloaded and installed KingRoot 4.8.2 from here. (file name "NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk", md5 11d61bfa1ab79ad3bb55cbaa1ebd6fc7).
Running
Code:
adb install NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk
worked flawlessly.
Now I started KingRoot on my Kindle. KingRoot said that root is (currently) not available on this device, but that it can try rooting.
I connected to WiFi and let KingRoot download its instructions. At probably about 20% into the rooting process, the device rebooted.
Afterwards I had to restart KingRoot and after some further thinking and reaching ~27% it said that the rooting process failed.
But I didn't give up, rebooted the device, restarted the KingRoot rooting process and voilà - this time it ran through without rebooting and I got root.
Installing SuperSu and FlashFire
Now on getting SuperSu to work for using FlashFire, which won't work with KingRoot.
I extracted the Superuser.apk from the official .zip distribution obtained from here ("UPDATE-SuperSU-v2.65-20151226141550.zip"), but you can probably also get it from the playstore if you got that installed. The md5 of the Superuser.apk was b4a76bb94927431f0d5b617836fb3f9c.
After installing SuperSu via adb install it complained that another su app was installed and its binaries needed an updated. Neither the automated removal of KingRoot nor the update of the binaries worked.
So following this guide I downloaded the mrw.zip that was attached to the third post (md5 1c769fe61e1fe5952b81fb80965c4d6b) and then unzipped and pushed the contained "mrw" folder to /sdcard/ on my kindle using
Code:
adb push mrw /sdcard/mrw
As the script reported some failures (which is supposedly normal) and the SuperSu didn't come any further, I checked the mrw/root.sh script.
After replacing ´cat sdcard/mrw/busybox > /system/bin/busybox´ with ´cat /sdcard/mrw/busybox > /system/bin/busybox´ in line 17 (see the missing root slash?) I got the script to work (at least when not being started from the root dir).
The important part from the skript (see below) now ran without errors.
The two
Code:
>/dev/null 2>&1
files, /system/xbin/kugote and /system/xbin/pidof did realy not exist, so that didn't matter.
Thanks beingtejas for the skript (again, see the mrw.zip from the link above for the full, working version of the script):
Code:
cat /sdcard/mrw/busybox > /system/bin/busybox #this was line 17 with the missing slash
chown 0.1000 /system/bin/busybox
chmod 0755 /system/bin/busybox
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
busybox chattr -ia /system/xbin/kugote >/dev/null 2>&1
rm /system/xbin/kugote >/dev/null 2>&1
busybox chattr -ia /system/xbin/su
rm /system/xbin/su
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof >/dev/null 2>&1
rm /system/xbin/pidof >/dev/null 2>&1
cat /sdcard/mrw/su > /system/xbin/su
cat /sdcard/mrw/su > /system/xbin/daemonsu
cat /sdcard/mrw/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d
Now KingRoot was uninstalled, the SuperSu update ran through and I rebooted the device as recommended.
Flashing
Afterwards the FlashFire installation ran fine with the SuperTool as described in the beginning and I could continue the normal installation.
After a very long AOSP boot sequence I now got the Fire Nexus ROM running nicely ob my kindle.
I mainly wrote this as documentation for myself but wanted to share it for other users facing the same problems with the updated bootloader.
If this post actually belongs elsewhere, please tell me to move it, as it is my first one and I couldn't find a better place to put it.
Dude... :fingers-crossed:
I love you. In a non sexual way.
Deleted
I managed to get it done also. Thanks for posting those steps. It took about 20 trys with kingroot, but it finally went all the way, lol. I had the same problems SuperSU also but following your compilation of forum guides, I got the Fire Nexus ROM and I'm loving the absence of Amazon!
Deleted
Hello. Just posting to let people know that this also worked for me as well.
Once you get Kingroot to work, it's all smooth sailing. Not sure if this helped the process but keeping the screen on while Kingroot to do its thing might help. I had several failed attempts and on all of those instances, my display expired and I had to unlock my device. The successful attempt, I just held my device and prevented it from locking... went to 30% and rebooted. Then I had root.
I have Fire Nexus installed.
Very nice!
Posting to say thank you! I did not know any of the roms could be flashed with FlashFire! I attached the most recent version of FlashFire.
feefeeboomboom said:
Posting to say thank you! I did not know any of the roms could be flashed with FlashFire! I attached the most recent version of FlashFire.
Click to expand...
Click to collapse
Flashfire v.30 appears to be a beta version according to Chainfires site
kgirlx said:
Flashfire v.30 appears to be a beta version according to Chainfires site
Click to expand...
Click to collapse
All versions released to date are betas (evidenced by '0.' prefix)
Davey126 said:
All versions released to date are betas (evidenced by '0.' prefix)
Click to expand...
Click to collapse
Ok, boy am I dumb. Thanks
kgirlx said:
Ok, boy am I dumb. Thanks
Click to expand...
Click to collapse
Not 'dumb'...learning
Just used your method, am now running 5.1.2 rooted, may have screwed up with KingRoot, but otherwise good, gonna try removing the KingRoot crap now
I really appreciate your post. It helped me get SuperSU working great! For some reason FlashFire 0.27 was closing on launch so I had to try the 0.30 version that someone posted using adb install -r
Thanks all!
Thank you a million times!! Fire OS was making me insane
Now to block the OTA updates. I haven't seen the definitive word on that as yet (if anyone could guide me, I'd be very appreciative!)
I was able to root and get SuperSU and Flashfire onto 5.1.2, but it died when I tried to flash it with SlimLP. I tried restoring it to stock 5.1.1 (probably a bad idea) and it's fully bricked, won't turn on at all. Are there any ways to recover from a full blank-screen no-turn-on with a 5.1.2 device? Has anyone had success flashing CM12 or SlimLP onto a 5.1.2? If so, what versions of the ROMS and what versions of flashfire did you use? Thanks!
(BTW, I'm testing a few options, so I have a few of these used cheap tablets, so bricking one of them isn't a tragedy, just want to get this to a working state.)
drmattyg said:
I was able to root and get SuperSU and Flashfire onto 5.1.2, but it died when I tried to flash it with SlimLP. I tried restoring it to stock 5.1.1 (probably a bad idea) and it's fully bricked, won't turn on at all. Are there any ways to recover from a full blank-screen no-turn-on with a 5.1.2 device? Has anyone had success flashing CM12 or SlimLP onto a 5.1.2? If so, what versions of the ROMS and what versions of flashfire did you use? Thanks!
(BTW, I'm testing a few options, so I have a few of these used cheap tablets, so bricking one of them isn't a tragedy, just want to get this to a working state.)
Click to expand...
Click to collapse
Any rollback attempt will yield an unrecoverable brick...as you discovered.
Multiple reports of installing CM 12.1 and Fire Nexus on a device that previously hosted FireOS 5.1.2. FlashFire v0.31. Latest ROM builds.
drmattyg said:
I was able to root and get SuperSU and Flashfire onto 5.1.2, but it died when I tried to flash it with SlimLP. I tried restoring it to stock 5.1.1 (probably a bad idea) and it's fully bricked, won't turn on at all. Are there any ways to recover from a full blank-screen no-turn-on with a 5.1.2 device? Has anyone had success flashing CM12 or SlimLP onto a 5.1.2? If so, what versions of the ROMS and what versions of flashfire did you use? Thanks!
(BTW, I'm testing a few options, so I have a few of these used cheap tablets, so bricking one of them isn't a tragedy, just want to get this to a working state.)
Click to expand...
Click to collapse
HOW TO ROOT FIRE 7 THAT HAS FIRMWARE 5.1.2 AND THEN INSTALL NEXUS ROM USING FLASHFIRE.
I have three Fire 7's with 5.1.2 firmware. I rooted them with RootJunky's SuperTool. After they were rooted, I installed FlashFire v.031 and then used that to load the Nexus rom (the latest one from early April). All of those are mentioned in threads here on xda.
Run RootJunky's SuperTool and root the Fire 7.
With the SuperTool, you can also load FlashFire. But it loads v.030. I believe you can get v.031 through a special link here on xda to the Google Play store.
If not, you can find FlashFire v.031 on a european server. Download v.031 apk and install it manually.
The FlashFire program icon will appear with the other installed apps on the Fire 7 apps screen, even on the Amazon Fire OS menu system.
Copy the Nexus rom (a zip file "lp-fire-nexus-rom-ford-20160405.zip" ) to your Fire 7's sd card root folder.
Make sure your Fire 7 is fully charged.
I started FlashFire v.031 and made the following menu selections:
In the FlashFire program do the following:
- Click the Red + and choose 'Wipe'.
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED.
- Click the Red + button and choose 'Flash ZIP/OTA'.
- Navigate to and choose the latest Fire Nexus ROM Zip (I used "lp-fire-nexus-rom-ford-20160405.zip" that I had previously loaded on the root folder of the SD Card.).
- Ensure Auto-mount and Mount /system read/write are UNCHECKED.
- Move (drag) "Wipe" to the Top of the order (just above the ROM flashing).
- Press the big FLASH button.
- Ignore any warnings that appear.
The Fire 7 screen will go black for a few seconds.
-Then it will say, "Loading" and lines of text will go by rapidly for a few seconds.
-A red bar will then appear at the top of the screen titled "FlashFire".
-The rest of the screen is black. Don't touch the tablet. Just let the program run. It takes 5 or 10 minutes. It looks like nothing is happening, but it is.
-Finally the tablet will reboot. The Amazon logo will appear for a little while, then a pulsing color dots animation will appear. This dot animation will run for 5 or 10 minutes more as the tablet boots for the first time. Don't touch the tablet until a Setup screen appears.
You can now set up the tablet, registering it with Google and loading your desired apps.
The Nexus rom gives you a generic Android 5 Lollipop interface. After loading the Nexus rom, I installed the Nova launcher, it gives you a lot of options for menu control.
Nexus is a nice ROM. Much better and faster than the stock Amazon Store ROM.
With the Nexus rom installed, I then added the Link2sd app from the Google Play store to recover 3.5gb of internal storage, linking apps to the sd card.
Link2sd is an app that links and moves most or all of an app to your sd card, but someway links it to the Fire 7 internal storage for the android system to run. Some custom roms allow you to just move and run the apps from the sd card. But with the Nexus rom, the app file is moved to the sd card, but run, maybe virtually from internal storage.
I have 150 apps installed on the Fire 7 with a Nexus rom. Before I loaded Link2sd, the Fire 7 had about 500mb internal storage free. After loading Link2sd and linking apps to my sd card, there is 3.5gb for free internal storage on the Fire 7.
In order for Link2sd to use the sd card you have to partition the sd card into Fat32 and ext4 partitions. The ext4 partition is used by Link2sd for app linking. The Fat32 partition is used in a normal manner for MP3, picture, video, e-book, etc storage.
I am using Linux Mint on my pc, so I used the linux program Gparted to partition a 32gb micro sd card for Link2sd to use. There are also free Windows programs that will allow you to do the same functions on your Windows 7 or 10 pc..
Link2sd uses a linux ext4 partition on the sd card to place and link apps to. The other half of the sd card is partitioned as a Fat32 format, for MP3, video, ebook, pictures storage.
Here is how to partition a 32gb micro sd card using the linux program Gparted. Use some type of micro sd adapter to connect the micro sd card to your linux pc. My Dell laptop has a built in sd slot, so it only needed and sd to micro sd adapter.
First delete the existing partition on the micro sd card. Then create a Fat32,. Primary partition, that takes 1/2 of the space on the micro sd card. Format the Fat32 partition as Fat32.
Next create a linux ext4, Primary partition, using the other 1/2 of the space on the micro sd card. Format the ext4 partition as ext4. The micro sd card is now ready for use by the Link2sd app.
Insert the micro SD card into the Fire 7 with a Nexus rom and Link2sd installed.
Start Link2sd and point it at the ext4 partition on the sd card when it asks and you are set to link apps to the sd card.
You can probably partition 64gb and 128gb sd cards in the same way, although I haven't tried. The Fire 7 is suppose to be able to accept up to a 128gb micro SD card.
Fire 7 boot times with the Nova rom are about 45 seconds to a minute. After installing Link2sd, the first boot after linking about 100 apps took 3 minutes. Later boots took about 90 seconds. So linking apps to the sd card does increase boot time on the tablet. Those times are for a cold start, from pushing the power button to being able to open the lock screen.
ADDENDUM: Well, after a couple of days of use, boot times are back to 60 seconds from a cold boot. Link2sd must have sorted things out. Wow.
Deleted
Thanks for the info, I managed to stumble through most and got root, updated the root.sh as per your instructions above and pushed the MRW folder to SD, installed Superuser, installed FlashFire. However, I am stumped at how to run the root.sh script!
Sorry for the noob question, but I just couldn't find a noob-friendly instructions ...
Do I install a Terminal Emulator on the Fire tablet, and run the script? I tried that (installed "Terminal Emulator") but just couldn't get any prompt to run.
If you don't mind giving me a more detailed instruction of how to run the script ... Mainly how to remove Kingroot ... Most appreciated!
Thanks!
---------- Post added at 09:07 PM ---------- Previous post was at 08:30 PM ----------
vn33 said:
Thanks for the info, I managed to stumble through most and got root, updated the root.sh as per your instructions above and pushed the MRW folder to SD, installed Superuser, installed FlashFire. However, I am stumped at how to run the root.sh script!
Sorry for the noob question, but I just couldn't find a noob-friendly instructions ...
Do I install a Terminal Emulator on the Fire tablet, and run the script? I tried that (installed "Terminal Emulator") but just couldn't get any prompt to run.
If you don't mind giving me a more detailed instruction of how to run the script ... Mainly how to remove Kingroot ... Most appreciated!
Thanks!
Click to expand...
Click to collapse
Duh! I managed to run the script through Terminal Emulator. It updated the, and rename the Kinguser to com.kingroot.kinguser
Now just trying to figure how to delete that file.
Thanks OP for this thread!