Database Info

[Q] Fresh ROM for Evo Shift 4G: Keeps Resetting

I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?

SoopahMan said:
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
Click to expand...
Click to collapse
Sounds like you either had a bad Flash, a bad Download, or both. So redownload the Rom you choose, then Clear and Flash your device according to THESE INSTRUCTIONS .

Thanks for the response. I downloaded the ROM again and ran a check - identical to the file I downloaded previously. So, if the ROM is the culprit, then the latest version of Fresh ROM for Evo Shift does not work (4.1.1).
I followed the instructions linked, wiping the cache and dalvik-cache twice (why?), and wiping system etc prior to installing the ROM.
I'm running into the exact same issues as before - I can't install anything from the Market, and the phone resets if I connect it to a computer over USB. When it resets, it resets multiple times and when it comes back up the 4G no longer works.
If I rerun the above instructions, the 4G works again, but I'm stuck back in this loop - can't use the Market or connect it over USB or it will reset, so forth.
Could Fresh ROM 4.1.1 for Evo Shift be bad? I still suspect the real problem is something is not sufficiently wiped or setup prior to install.
In case it might help, here's an ls -al after installing Fresh Rom 4.1.1 on my phone (an HTC Evo Shift 4G after following the above install instructions).
/
drwxr-xr-x 2 root root 0 Jan 17 07:39 boot
drwxr-xr-x 4 root root 1024 Jan 17 07:41 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 17 07:39 datadata
-rw-r--r-- 1 root root 3462 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3060 Jan 17 07:39 dev
drwxr-xr-x 2 root root 0 Jan 17 07:39 emmc
drwxr-xr-x 2 root root 0 Jan 17 07:39 etc
-rwxr-x--- 1 root root 94372 Jan 1 1970 init
-rwxr-x--- 1 root root 899 Jan 1 1970 init.rc
dr-xr-xr-x 79 root root 0 Jan 1 1970 proc
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 May 15 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 17 07:39 sd-ext
drwxrwxrwx 78 root root 32768 Jan 1 1970 sdcard
drwxr-xr-x 18 root root 0 Jan 17 07:39 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 17 07:45 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4027 Jan 1 1970 ueventd.rc
-rw-r--r-- 1 root root 987 Jan 1 1970 ueventd.speedy.rc
/data
(empty)
/system
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
/system/bin
(empty)
/sys
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera_awb_cal
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_touch
drwxr-xr-x 2 root root 0 Jan 17 07:53 block
drwxr-xr-x 2 root root 0 Jan 17 07:39 board_properties
drwxr-xr-x 9 root root 0 Jan 17 07:53 bus
drwxr-xr-x 2 root root 0 Jan 17 07:53 camera_led_status
drwxr-xr-x 47 root root 0 Jan 17 07:53 class
drwxr-xr-x 4 root root 0 Jan 17 07:53 dev
drwxr-xr-x 10 root root 0 Jan 17 07:39 devices
drwxr-xr-x 2 root root 0 Jan 17 07:53 firmware
drwxr-xr-x 3 root root 0 Jan 17 07:53 fs
drwxr-xr-x 6 root root 0 Jan 17 07:53 kernel
drwxr-xr-x 62 root root 0 Jan 17 07:53 module
drwxr-xr-x 2 root root 0 Jan 17 07:53 power
drwxr-xr-x 2 root root 0 Jan 17 07:53 systemlog
I can post more or other diagnostics if others have something to recommend. Really stuck here.

Is it odd that /sd-ext is at root and not located on the SD card, and a directory not a symlink?

Now that you have 10 posts you should try posting your questions in the thread for flipz's rom.So the dev can help and maybe anyone else that is running this rom. Also have you tried the a2sd remove command adb shell or from terminal emulator? See if that helps.
Sent from my PG06100 using Tapatalk

A bit more to isolate the problem:
If the phone resets (due to attempting an install from the Market or plug in from USB), 4G fails - but if I restart the phone at that point, when it reboots 4G works again. So 4G appears to be fine, it's the resets that are at the core of the issue.
I shutdown, removed the SD card, booted, and attempted to install an app and got the same reset, so it's not the SD card - it's definitely a problem somewhere on internal storage.
What else do I need to clear to clear this up?
Fresh ROM's pages say to look in /data/app and /system/app for a place where an app already exists that would cause a conflict.
Here's /data after booting the ROM and setting up a Gmail account:
lrwxrwxrwx 1 root root 14 Jan 17 07:54 app -> /system/sd/app
lrwxrwxrwx 1 root root 22 Jan 17 07:54 app-private -> /system/sd/app-private
drwx------ 5 system system 1024 Jan 6 1980 backup
drwxrwx--x 2 system system 14336 Jan 17 16:25 dalvik-cache
drwxrwx--x 161 system system 9216 Jan 17 07:57 data
drwxr-x--- 2 root log 1024 Jan 17 07:54 dontpanic
lrwxrwxrwx 1 root root 11 Jan 17 07:54 drm -> /data/local
-rw-r--r-- 1 root root 6134 Jan 6 1980 dta2sd.lg1
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.lg2
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.log
drwxrwxrwx 2 root root 1024 Jan 17 07:54 htcfs
drwxr-xr-x 4 root root 1024 Jan 17 07:42 jit
drwxrwx--x 4 shell shell 1024 Jan 17 07:54 local
drwxrwx--- 2 root root 12288 Jan 17 07:41 lost+found
drwxrwx--t 10 system misc 1024 Jan 17 07:55 misc
drwx------ 2 root root 1024 Jan 6 1980 property
drwx------ 3 system system 1024 Jan 17 07:55 secure
drwxrwxr-x 9 system system 1024 Jan 17 17:48 system
drwxrwx--- 3 system system 1024 Jan 17 17:14 wimax
I'd like to know if app and app-private are as expected (they appear to be the result of the ROM install, since they were completely wiped prior to installing it). The app symlink is a strange one. It points to /system/sd/app, which I can't cd to. /system/sd I can cd to, and this is all it contains:
-rw-r--r-- 1 root root 17 Aug 1 2008 placeholder
A file named placeholder. What?
I'm starting to suspect apps2sd. None of the relevant partitioning steps are in those install instructions, and they appear to be specific to the apps2sd of CyanogenMod. Google's appears to support a DOS partition, while CyanogenMod's appears to only support an ext3 partition, which I do not have.
At the same time, removing the SD card didn't change things, so color me confused.

As suggested by FdxRider you should definately post up in the Rom thread. That way you can get help resolving the issue from others running the same Rom.

It was apps2sd.
To resolve this problem, I had to:
Reboot into ClockwordModRecovery
Connect the phone to a computer over USB
In Clockwork, choose Mount Storage and choose the last option, Mount USB.
Dump anything I wanted to keep off of the SD card (most importantly, the FreshRom zip file).
Then, back in Clockwork, Advanced>Partition SD
Choose a size (they recommend 1024M)
This wipes out everything on the SD card, creates a Linux partition for apps2sd to use, marks the rest as a Windows partition.
Wait till it's done, then, still from ClockworkModRecovery:
Wipe cache, dalvik cache, system, data
Factory reset
Now Mount USB again so you can copy the FreshRom zip back onto the Windows partition (the only part that will come up on a Windows machine).
Eject on the Windows machine to ensure the copy completes, Unmount in Clockwork.
Install the ROM again
Let it boot, restart
Setup my Google Account/Gmail user
And one final thing:
As it turns out ES File Explorer is pre-installed on this ROM. That means installing it from the Market will make the phone go crazy regardless of proper setup. But I am now able to install other apps just fine from the Market (at last).

reset loop NO clockwork until factory reset
I installed Fresh 4.1.1 on my shift 4g
I went to install ROM Manager got it downloaded and it reset the phone at install.
I even tried going to the website and installing it that way. Same results.
I can't get clockwork to work, when i hold the volume down and then press power nothing happens until i release the power button then it goes directly to the Fresh install.
PLEASE HELP!!!!
---------- Post added at 05:30 AM ---------- Previous post was at 05:09 AM ----------
I got the problem solved. I used the RRU and it walked me through a recovery, part of it was yanking the battery. DUH!

[HACK] ViperOneS2.0.0 boot.img to use /etc/firmware rather than partitions - fix wifi

edit try this first if you just want wifi: http://forum.xda-developers.com/showthread.php?t=2151142
I love Sense and Viper ROM. What I don't love is HTC's definition of “unlocked” - so changing my WIFI and Radio firmware is a pain.
I hacked Viper's boot.img to use /etc/firmware rather than the WIFI(x2) + Radio partitions. I can now change my firmware using adb or an install tool => just put/update the files into /etc/firmware. As CM10 ROMs (my 2nd love) use /etc/firmware, you can now use their firmware installers.
This worked for me on my phone - but it is a hack - maybe it will work for others, mabye not. I would not try this if you aren't experienced, as it's totally untested and unverified. If this is a viable solution you'll see refinement and success reports over time.
This might help you get your wifi working with the Viper ROM - if you cannot flash your write protected WIFI partitions
This will make it really easy to change Radios
prerequisites
- Working Viper Install
- Recovery Image working (I used TWRP, but for sure their are others)
- Fastboot working
- adb working
- Ability to diagnose and fix a boot loop
- Guts as this is untried, untested and unverified...
1. Make a backup and copy it off your phone.
I use TWRP and then adb to 'pull' it.
2. Load WIFI firmware and Radio firmware into /etc/firmware - these are most often (*) transparent to Sense ROMS
You need to load the Radio, Wifi (q6) and Wifi (wcnss) firmwares into /etc/firmware. You will have an awsome boot loop later on if you leave something out.
I copied the files with adb, but you can also install zip files:
Radio: The awsome Tecardo's CM10 Radio Collection, use the CM10-Radio-InstallerV1.5.zip - from here.
WIFI (q6 and wcnss): I hacked an installer to use /etc/firmware rather than the partitions see attached file . I shamlessly copied from Zarboz WIFI firmware installer. These are the firmware files that fixed the WIFI authentication problem for me.
Boot into TWRP then install:
Ville.WIFI.Firmware_etcfirmware.RC1.zip
CM10-Radio-InstallerV1.5.zip -> choose the radio you want (
3. Sanity check - Boot Viper and make sure it's still working.
The firmware you just added is most often (*) ignored. You should verify the additional files are in /etc/firmware - adb shell.
Code:
[COLOR="RoyalBlue"][SIZE="2"]bash-4.2$ adb shell
[email protected]/# cd /etc/firmware
[email protected]/etc/firmware#
[email protected]/etc/firmware# ls -al | grep q6
-rw-r--r-- root root 276 2013-02-17 11:15 q6.b00
-rw-r--r-- root root 6580 2013-02-17 11:15 q6.b01
-rw-r--r-- root root 3428272 2013-02-17 11:15 q6.b03
-rw-r--r-- root root 2032526 2013-02-17 11:15 q6.b04
-rw-r--r-- root root 766032 2013-02-17 11:15 q6.b05
-rw-r--r-- root root 13248 2013-02-17 11:15 q6.b06
-rw-r--r-- root root 6856 2013-02-17 11:15 q6.mdt
[email protected]/etc/firmware# ls -al | grep wcnss
-rw-r--r-- root root 212 2013-02-17 11:15 wcnss.b00
-rw-r--r-- root root 6540 2013-02-17 11:15 wcnss.b01
-rw-r--r-- root root 8360 2013-02-17 11:15 wcnss.b02
-rw-r--r-- root root 1787316 2013-02-17 11:15 wcnss.b04
-rw-r--r-- root root 6752 2013-02-17 11:15 wcnss.mdt
[email protected]/etc/firmware#
[email protected]/etc/firmware# ls -al | grep modem
-rw-r--r-- root root 308 2008-08-01 22:00 modem.b00
-rw-r--r-- root root 6600 2008-08-01 22:00 modem.b01
-rw-r--r-- root root 22530448 2008-08-01 22:00 modem.b02
-rw-r--r-- root root 5120129 2008-08-01 22:00 modem.b03
-rw-r--r-- root root 1345816 2008-08-01 22:00 modem.b04
-rw-r--r-- root root 71376 2008-08-01 22:00 modem.b06
-rw-r--r-- root root 717044 2008-08-01 22:00 modem.b07
-rw-r--r-- root root 6908 2008-08-01 22:00 modem.mdt
-rw-r--r-- root root 1044 2008-08-01 22:00 modem_fw.b00
-rw-r--r-- root root 7060 2008-08-01 22:00 modem_fw.b01
-rw-r--r-- root root 2676 2008-08-01 22:00 modem_fw.b02
-rw-r--r-- root root 958928 2008-08-01 22:00 modem_fw.b03
-rw-r--r-- root root 579884 2008-08-01 22:00 modem_fw.b04
-rw-r--r-- root root 239892 2008-08-01 22:00 modem_fw.b05
-rw-r--r-- root root 94208 2008-08-01 22:00 modem_fw.b06
-rw-r--r-- root root 13568 2008-08-01 22:00 modem_fw.b07
-rw-r--r-- root root 11212 2008-08-01 22:00 modem_fw.b08
-rw-r--r-- root root 9596 2008-08-01 22:00 modem_fw.b09
-rw-r--r-- root root 68295 2008-08-01 22:00 modem_fw.b10
-rw-r--r-- root root 118028 2008-08-01 22:00 modem_fw.b13
-rw-r--r-- root root 158676 2008-08-01 22:00 modem_fw.b14
-rw-r--r-- root root 3604 2008-08-01 22:00 modem_fw.b21
-rw-r--r-- root root 28628 2008-08-01 22:00 modem_fw.b22
-rw-r--r-- root root 19424 2008-08-01 22:00 modem_fw.b23
-rw-r--r-- root root 74384 2008-08-01 22:00 modem_fw.b25
-rw-r--r-- root root 50108 2008-08-01 22:00 modem_fw.b26
-rw-r--r-- root root 84588 2008-08-01 22:00 modem_fw.b29
-rw-r--r-- root root 8104 2008-08-01 22:00 modem_fw.mdt
[email protected]/etc/firmware# [/SIZE][/COLOR]
4. Test boot the hacked boot.img
Do a one off download of the hacked boot.img into your phone. It will not over-write the boot.img on the phone, just download it into memory and execute it just this once See attached file
boot into the bootloader for fastboot session:
fastboot boot hackedviperforfirmwarelinks_boot.img
5. Test and post results - either way
Total number of users to try this, that aren't me: 0 be scared
6. Install the hacked boot.img
If your happy and want to keep using the hack. Flash the hacked boot.img.
boot into the bootloader for fastboot session:
fastboot flash boot hackedviperforfirmwarelinks_boot.img
7. To uninstall - remember to do this when you upgrade Viper or restore a ROM
Extract boot.img from ViperOneS_2.0.0.zip - on your linux/windows rig
fastboot flash boot boot.img
(*) note:
The firmware loading mechanisms on Sense ROMs are complicated, RC scripts will search and then link to any salient firmware they might find. Things will depend on what/where and even the case of the filenames!
Caution:
I absolutely 100% guarantee you a boot loop either now or in the future. If you forget to flash the Viper supplied boot.img when you upgrade you'll have a great little recovery excercise! Same goes if you restore a backup. I forgot every time. There probably is some locale specific firmware that I don't know about. If your phone depends on it and it isn't in /etc/firmware then it will boot loop.
Technical Details
I updated the init.target.rc to: see copyright, license banner attached
not mount the firmware partitions: /firmware_radio, /firmware_q6, /firmware_wcnss
softlink above to /etc/firmware
Credit's:
On my screen the entire time was AKToronto's partition list + cat2115
I'd never put a zip file together, so what I've done probably sucks. I shamlessly copied Zarboz's extracted firmware and anything good from his install script, refer.

Nice I will try this later when I switch back to viper rom
Sent from my HTC One S using xda app-developers app

AW: [HACK] ViperOneS2.0.0 boot.img to use /etc/firmware rather than partitions - fix
Nice thanks just what Tecardo and I discussed all the time.
I like your sense of humour in your post. Cheers for making this!
(Although it's quite useless now since we have S-OFF but I'm sure you enjoyed making it!)
sent from viper 2.1

Unicode

How can I utilize unicode myanmar(burmese)on my android
galaxy y

Android is natively UTF-8 (that is Unicode).
There are two conditions to that.
1) You need a font that has the characters that you require for your language.
2) You might want/need some way to type in those characters.
You could replace your fallback font with another font that contains Myanmarese.
If you have a compatible font on your browser, this should be (kind of) legible.
ပြည်ထောင်စု သမ္မတ မြန်မာနိုင်ငံတော်

Thanks for your kindness,but I still have problem.Here we are I installed south east asia font and I change my font style to it.I don't know whether it is utf-8 or ttf.
After that I saw empty space in the place of myanmar font ,this happen on web page,sms page and memo page.So how can I replace fallback font or any other way available?

UTF-8 and TTF are different concepts.
Give me a link to the font that you are using.

Thanks for yr kindness.
But unfortunately I cannot post the link though I tried cause I m new user of xda so what the alternatively way?

You could always PM me the link.

I have already done the pm of the software link

I haven't looked into what the apk itself does but assets/fonts/hsfsea.ttf is the font "Padauk".
Unzip the .apk
Remount your /system on your device as read/write
Code:
adb pull /system/fonts/DroidSansFallback.ttf
adb push hsfsea.ttf /system/fonts/DroidSansFallback.ttf
adb reboot
Here's a screenshot of my post from above on my Nook:

I am not clear yr post,but I have done unzip the apk, I saw hfsea.ttf. So I copied that to system/font/ and set file permission as droidsansfallback.ttf.And reboot my phone.Nothing changed.So please reply me more detail the procedure.

You do have exactly this (capitalization is important)?
Code:
ls -l /system/fonts
-rw-r--r-- root root 1139424 2013-03-01 12:00 DroidSansFallback.ttf
(-rw-rw-rw- is ok too)
Did you test in a browser?

Yes ofcourse,in the browser also nothing change, but the blank.

I'm unclear here.
You are saying that the stock DroidSansFallback.ttf was there,
that you replaced it with the hsfsea.ttf, and that the sizes agree?
Did you already try to install some other font?
Try clearing the cache.
Try explicitly setting the font to DroidSansFallback.

The procedure I have done is that I added hsfsea.ttf to system/font and I set the file permissin as other ttf.I also tried as u said rw rw rw.I clear cache.I reboot my phone.I also go to recovery and cwm recovery but I saw nothing related to font.Currently I have 4 fonts, unicode/south east asia,zawgyi one ttf,zawgyi one 2008 and system default.What elese thing shall I do for unicode?May I thank you in advance.

I don't know what is going on with your system.
You may be specifying a font that says it has the Unicode range for Myanmar, but doesn't.
Are you telling your apps to use a specific font?
Paste a ls -l /system/fonts please.

Me too I don't know what the problem is?I saw other android user also,they can not see myanmar font by using this application(unicode/south east asia )

Renate NST said:
Paste a ls -l /system/fonts please.
Click to expand...
Click to collapse
It may be that your system is rejecting it as a fallback font because it does not support the Basic Latin Unicode range (A-Z, etc).
You might try overwritng DroidSansFallback.ttf with Zawgyi.

How can I overwrite droidsansfallback.ttf by zawgyi? Any way I always thank you for your kindness.

Well, didn't you already overwrite DroidSansFallback.ttf with hsfsea.ttf?
We may be having miscommunication problems here.
I've been asking you to post a listing of ls -l /system/fonts
Could you do that, please?

Yes,that is
/system/font/
Clockopia.ttf
Droidindia.ttf
Droidsans-bold.ttf
Droidsans.ttf
Droidsansarabic.ttf
Droidsansfallback.ttf
Droidsanshebrew.ttf
Droidsansmono.ttf
Droidsansthai.ttf
Droidserif-bold.ttf
Droidserif-bolditalic.ttf
Droidserif-italic.ttf
Droidserif-regular.ttf
hsfsea.ttf(I have already added)
Samsungamericanregular.ttf
Samsunggeorgianregular.ttf

Code:
ls [b]-l[/b] /system/fonts
That's the small L in there, so that we can actually see something.
Code:
ls -l /system/fonts
-rw-r--r-- root root 4824 2012-06-29 04:58 AndroidClock.ttf
-rw-r--r-- root root 4824 2012-06-29 04:58 AndroidClock_Highlight.ttf
-rw-r--r-- root root 4824 2012-06-29 04:58 AndroidClock_Solid.ttf
-rw-r--r-- root root 6880 2012-06-29 04:58 Clockopia.ttf
-rw-r--r-- root root 366760 2012-06-29 04:58 DroidNaskh-Regular.ttf
lrw-r--r-- root root 2012-06-29 05:01 DroidSans-Bold.ttf -> Roboto-Bold.ttf
lrw-r--r-- root root 2012-06-29 05:01 DroidSans.ttf -> Roboto-Regular.ttf
-rw-r--r-- root root 13856 2012-06-29 04:58 DroidSansArmenian.ttf
-rw-r--r-- root root 227928 2012-06-29 04:58 DroidSansEthiopic-Regular.ttf
-rw-r--r-- root root 5300184 2012-06-29 04:58 DroidSansFallback.ttf
-rw-r--r-- root root 21096 2012-06-29 04:58 DroidSansGeorgian.ttf
-rw-r--r-- root root 30280 2012-06-29 04:58 DroidSansHebrew-Bold.ttf
-rw-r--r-- root root 30024 2012-06-29 04:58 DroidSansHebrew-Regular.ttf
-rw-r--r-- root root 119380 2012-06-29 04:58 DroidSansMono.ttf
-rw-r--r-- root root 35584 2012-06-29 04:58 DroidSansThai.ttf
-rw-r--r-- root root 185228 2012-06-29 04:58 DroidSerif-Bold.ttf
-rw-r--r-- root root 190304 2012-06-29 04:58 DroidSerif-BoldItalic.ttf
-rw-r--r-- root root 177560 2012-06-29 04:58 DroidSerif-Italic.ttf
-rw-r--r-- root root 172916 2012-06-29 04:58 DroidSerif-Regular.ttf
-rw-r--r-- root root 139296 2012-06-29 04:58 Lohit-Bengali.ttf
-rw-r--r-- root root 64232 2012-06-29 04:58 Lohit-Devanagari.ttf
-rw-r--r-- root root 66184 2012-06-29 04:58 Lohit-Tamil.ttf
-rw-r--r-- root root 79620 2012-06-29 04:58 Roboto-Bold.ttf
-rw-r--r-- root root 82880 2012-06-29 04:58 Roboto-BoldItalic.ttf
-rw-r--r-- root root 82580 2012-06-29 04:58 Roboto-Italic.ttf
-rw-r--r-- root root 79396 2012-06-29 04:58 Roboto-Regular.ttf
Why is the capitalization of all your files different?
You realize that this is the fourth time that I have asked you to do a simple directory listing.

[MOD] Galaxy Core 2 Boot logo / Boot animation SM-G355HN

Greeting every1
This is gor Galaxy Core 2 phones ( SM-G355HN )
Been messing about the logo on my GC2. As mentioned it's in the param.lfs (for flashing with Odin) or /dev/block/mmcblk0p13.
You can do it with emulator,root explorer , adb or any other way ...
With the adb :
Code:
C:\ADB>cmd /k cd "C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools"
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
[email protected]:/ # cd /mnt/extSdCard
cd /mnt/extSdCard
[email protected]:/mnt/extSdCard # ls
ls
Android
Apk's
DCIM
LOST.DIR
bluetooth
device.nng
iGO
iGO primo 9.6.29.404739 - 30 jun 2014
param
[email protected]:/mnt/extSdCard # tar
tar
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: tar -[cxtZzJjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
Z (De)compress using compress
z (De)compress using gzip
J (De)compress using xz
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
1|[email protected]:/mnt/extSdCard # tar -t -f param
tar -t -f param
adv-env.img
ani_upload_1_kernel_panic.jpg
ani_upload_2_cp_crash.jpg
ani_upload_3_forced_upload.jpg
ani_upload_4_hardware_reset.jpg
ani_upload_4_smpl.jpg
ani_upload_4_unknown_reset.jpg
ani_upload_4_watchdog_reset.jpg
ani_upload_4_wtsr.jpg
ani_upload_4_wtsr_smpl.jpg
ani_upload_5_user_fault.jpg
ani_upload_6_hsic_disconnected.jpg
download.jpg
download_error.jpg
logo.jpg
lpm.jpg
sud_0.jpg
sud_1.jpg
sud_2.jpg
sud_3.jpg
sud_4.jpg
sud_5.jpg
sud_6.jpg
sud_7.jpg
sud_8.jpg
sud_9.jpg
warning.jpg
[email protected]:/mnt/extSdCard #
After changing logo, messing with photos,sizes of the file and other stuff and when i copy new image and replace the original after booting I get default logo.
The tar files in this case doesn't follow the user and file permissions ?
Have check the image and block after changing logo and image, the image/logo is accepted and installed into, but guess there is some checking or something else while booting. The installed image isn't accepted during boot,guess It's missplaced with the original ("from where ?") or am I missing some other possible way the image is/can be stored ina any other image/partition.
Has any1 tried this with our phone ?
The files for flash the param partition and self flashing archive is included as attachement.
The boot logo (logo.jpg) is the file download.jpg.
The animation "Samsung" is in the /system/media inside bootsamsung.qmg
You can check it via bootanimation in /system/bin, use it via adb or u will have to take the battery out to stop the animation or get to the home screen.

good....some developing for this phone.
I read that the HTC desire 700 have the same SOC as the core2...they have cwm and Twrp...if I dont read bad...maybe we can use some files for the core2.
I play a little with my gilrdfriend core2...and Im trying to make custom recovery...but no luck. I cant play to much cuz of I broke the phone...my GF will kill me.

Boot animation, boot sound ...
Ok, here is the deal for my GC2 Samsung SM-G355HN :
If u have a original firmware (mine is G355HNXXU0ANH3) the boot animation and boot sound are not stored in kernel,ramdisk any other zip (bootanimation ...)
Samsung has made their own qmf's for animation. You can check your bootanimation preferably throught adb with 'bootanimation' in /system/bin/.
If u start the program in phone U'll have to take the battery out to get your phone usable, the animation is top moded aplication.
...In adb mode press just cancel '<Ctrl>+C' or exit/quit adb shell.
Ok, the bootanimation source (qmf's) are in system/media
Code:
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ cd system/media
cd system/media
[email protected]:/system/media $ ls -l boot*
ls -l boot*
-rw-r--r-- root root 307252 2014-08-27 14:56 bootanimation.zip
-rw-r--r-- root root 2597636 2008-08-01 14:00 bootsamsung.qmg
-rw-r--r-- root root 1213332 2008-08-01 14:00 bootsamsungloop.qmg
-rw-r--r-- root root 49319 2014-08-27 14:56 bootsound.mp3
[email protected]:/system/media $
bootanimation.zip as told doesn't do nothing, some chinese leftover stuff here.
'Bootsamsung.qmg' is the boot file while booting after the end the 'bootsamsungloop.qmg' file is loading/showing until the anroid system is fully loaded and activated.
Check the shutdown.qmg ...
Ok, it took me a little bit to find that the sound is not the usual visible bootsound.mp3.
The animation is only for graphical animation, the boot sound is located in system/media/audio/ui (user interface).
Code:
[email protected]:/system/media/audio/ui $ ls -l
ls -l
-rw-r--r-- root root 7577 2014-08-27 14:56 Alert_on_call.ogg
-rw-r--r-- root root 5146 2014-08-27 14:56 Auto_focus.ogg
-rw-r--r-- root root 571497 2014-08-27 14:56 Birdsong_by_the_Lake.ogg
-rw-r--r-- root root 8059 2014-08-27 14:56 Call_Connect.ogg
-rw-r--r-- root root 6566 2014-08-27 14:56 Cam_Start.ogg
-rw-r--r-- root root 7567 2014-08-27 14:56 Cam_Stop.ogg
-rw-r--r-- root root 6262 2014-08-27 14:56 Camera_Timer.ogg
-rw-r--r-- root root 26266 2014-08-27 14:56 Camera_Timer_2sec.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Camera_click_short.ogg
-rw-r--r-- root root 3726 2014-08-27 14:56 Camera_empty.ogg
-rw-r--r-- root root 14351 2014-08-27 14:56 Charger_Connection.ogg
-rw-r--r-- root root 6773 2014-08-27 14:56 Dialer_new.ogg
-rw-r--r-- root root 18648 2014-08-27 14:56 Dock.ogg
-rw-r--r-- root root 786319 2014-08-27 14:56 Fairy_Fountain.ogg
-rw-r--r-- root root 637833 2014-08-27 14:56 Gentle_Spring_Rain.ogg
-rw-r--r-- root root 4713 2014-08-27 14:56 Highlight.ogg
-rw-r--r-- root root 4705 2014-08-27 14:56 HoverPointer.ogg
-rw-r--r-- root root 10937 2014-08-27 14:56 Lock.ogg
-rw-r--r-- root root 6907 2014-08-27 14:56 Lock_none_effect.ogg
-rw-r--r-- root root 8559 2014-08-27 14:56 Lock_tension.ogg
-rw-r--r-- root root 14323 2014-08-27 14:56 LowBattery.ogg
-rw-r--r-- root root 470154 2014-08-27 14:56 Media_preview_Over_the_horizon.ogg
-rw-r--r-- root root 6687 2014-08-27 14:56 New_chat.ogg
-rw-r--r-- root root 97411 2008-08-01 14:00 PowerOn.ogg
-rw-r--r-- root root 11242 2014-08-27 14:56 S_Beam_end.ogg
-rw-r--r-- root root 12070 2014-08-27 14:56 S_Beam_error.ogg
-rw-r--r-- root root 13673 2014-08-27 14:56 S_Beam_start.ogg
-rw-r--r-- root root 9922 2014-08-27 14:56 S_HW_Touch.ogg
-rw-r--r-- root root 4766 2014-08-27 14:56 S_SIP_Backspace.ogg
-rw-r--r-- root root 6830 2014-08-27 14:56 Sent_chat.ogg
-rw-r--r-- root root 558556 2014-08-27 14:56 Serenity.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 Shutter.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Shutter_multiple.ogg
-rw-r--r-- root root 7294 2014-08-27 14:56 SideSync_Connected.ogg
-rw-r--r-- root root 838441 2014-08-27 14:56 Sparkling_Mist.ogg
-rw-r--r-- root root 15785 2014-08-27 14:56 TW_Battery_caution.ogg
-rw-r--r-- root root 8350 2014-08-27 14:56 TW_Call_Disconnect.ogg
-rw-r--r-- root root 4789 2014-08-27 14:56 TW_SIP.ogg
-rw-r--r-- root root 7868 2014-08-27 14:56 TW_Silent_mode_off.ogg
-rw-r--r-- root root 9926 2014-08-27 14:56 TW_Touch.ogg
-rw-r--r-- root root 5515 2014-08-27 14:56 TW_Volume_control.ogg
-rw-r--r-- root root 16795 2014-08-27 14:56 Tap_tension.ogg
-rw-r--r-- root root 5176 2014-08-27 14:56 TextSelection.ogg
-rw-r--r-- root root 816576 2014-08-27 14:56 The_Secret_Forest.ogg
-rw-r--r-- root root 18669 2014-08-27 14:56 Undock.ogg
-rw-r--r-- root root 10939 2014-08-27 14:56 Unlock.ogg
-rw-r--r-- root root 7287 2014-08-27 14:56 Unlock_none_effect.ogg
-rw-r--r-- root root 15468 2014-08-27 14:56 Unlock_tension.ogg
-rw-r--r-- root root 12860 2014-08-27 14:56 Voice_processing.ogg
-rw-r--r-- root root 8038 2014-08-27 14:56 Voice_start.ogg
-rw-r--r-- root root 10141 2014-08-27 14:56 Voice_stop.ogg
-rw-r--r-- root root 10235 2014-08-27 14:56 Zero_Clickr_Ready.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 camera_click.ogg
-rw-r--r-- root root 13878 2014-08-27 14:56 lens_flare_lock.ogg
-rw-r--r-- root root 4407 2014-08-27 14:56 lens_flare_unlock_silence.ogg
[email protected]:/system/media/audio/ui $
Here and in the /audio/ dir you can insert other music for alarms,notification,ringtones and ui interfaces like :Auto_focus,Undock,Unlock,Camera sounds ...
We are interested in PowerOn.ogg - our boot song
It's the ogg format. Save your favourite boot - Power On sound as PowerOn.ogg in /system/media/audio/ui.
You can do it manually or throught ADB,Terminal emulator :
Here is for the ADB :
First make your /system/ is rw (readwrite) :
Code:
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ #
Copy your files to SD root (bootsamsung.qmg,bootsamsungloop.qmg,PowerOn.ogg) or anywhere in the phone, local ADB folder on comp...
overwite *.qmg files in /system/media/ and PowerOn.ogg in /system/media/audio/ui/
Code:
[email protected]:/system/media # cd /storage/extSdCard
cd /storage/extSdCard
[email protected]:/storage/extSdCard # cp bootsamsung.qmg /system/media/bootsamsung.qmg
system/media/bootsamsung.qmg
[email protected]:/storage/extSdCard # cp bootsamsungloop.qmg /system/media/bootsamsungloop.qmg
g /system/media/bootsamsungloop.qmg
[email protected]:/storage/extSdCard # cp PowerOn.ogg /system/media/audio/ui/PowerOn.ogg
m/media/audio/ui/PowerOn.ogg
[email protected]:/storage/extSdCard #
remount back to ro (readonly) and run bootanimation throught adb to check graphic Power ON sequence only:
Code:
[email protected]:/storage/extSdCard # mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ # bootanimation
bootanimation
^C
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
You can also change the permission of the files before ro remount :
chmod 644 is the primary for those 3 files ( -rw-r--r-- [email protected] ) but not needed if su (#) enabled
Power Off phone and enjoy ... U can change other stuff PowerOff, shutdown ...
Have also provided mine bootanim, loop and sound as update zip recovery package included.
... for now I'm working on to change the boot logo before boot animation.Help or any other infos are mostly wanted.
And about the *.qmg files, check and search the xda, there are lot about it ...
The animations I used are original files from other Samsung devices, PoverOn wav found and converted from the internet.
The update script :
Code:
ui_print("********************************");
ui_print("* StratOS boot animation,sound *");
ui_print("********************************");
ui_print("");
ui_print("For SM-G355H*");
run_program("/xbin/busybox", "mount", "/system");
run_program("/xbin/busybox", "mount", "-o", "rw,remount", "/system", "/system");
ui_print("Deleting files");
delete("/system/media/audio/ui/PowerOn.ogg");
delete("/system/media/bootsamsung.qmg");
delete("/system/media/bootsamsungloop.qmg");
ui_print("Extracting files");
package_extract_dir("system", "/system");
ui_print("");
ui_print("Finished");
run_program("/xbin/sleep", "5");
unmount("/system");
Sent from my SM-G355HN using XDA Free mobile app

StratOS_HTC said:
Ok, here is the deal for my GC2 Samsung SM-G355HN :
If u have a original firmware (mine is G355HNXXU0ANH3) the boot animation and boot sound are not stored in kernel,ramdisk any other zip (bootanimation ...)
Samsung has made their own qmf's for animation. You can check your bootanimation preferably throught adb with 'bootanimation' in /system/bin/.
If u start the program in phone U'll have to take the battery out to get your phone usable, the animation is top moded aplication.
...In adb mode press just cancel '<Ctrl>+C' or exit/quit adb shell.
Ok, the bootanimation source (qmf's) are in system/media
Code:
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ cd system/media
cd system/media
[email protected]:/system/media $ ls -l boot*
ls -l boot*
-rw-r--r-- root root 307252 2014-08-27 14:56 bootanimation.zip
-rw-r--r-- root root 2597636 2008-08-01 14:00 bootsamsung.qmg
-rw-r--r-- root root 1213332 2008-08-01 14:00 bootsamsungloop.qmg
-rw-r--r-- root root 49319 2014-08-27 14:56 bootsound.mp3
[email protected]:/system/media $
bootanimation.zip as told doesn't do nothing, some chinese leftover stuff here.
'Bootsamsung.qmg' is the boot file while booting after the end the 'bootsamsungloop.qmg' file is loading/showing until the anroid system is fully loaded and activated.
Check the shutdown.qmg ...
Ok, it took me a little bit to find that the sound is not the usual visible bootsound.mp3.
The animation is only for graphical animation, the boot sound is located in system/media/audio/ui (user interface).
Code:
[email protected]:/system/media/audio/ui $ ls -l
ls -l
-rw-r--r-- root root 7577 2014-08-27 14:56 Alert_on_call.ogg
-rw-r--r-- root root 5146 2014-08-27 14:56 Auto_focus.ogg
-rw-r--r-- root root 571497 2014-08-27 14:56 Birdsong_by_the_Lake.ogg
-rw-r--r-- root root 8059 2014-08-27 14:56 Call_Connect.ogg
-rw-r--r-- root root 6566 2014-08-27 14:56 Cam_Start.ogg
-rw-r--r-- root root 7567 2014-08-27 14:56 Cam_Stop.ogg
-rw-r--r-- root root 6262 2014-08-27 14:56 Camera_Timer.ogg
-rw-r--r-- root root 26266 2014-08-27 14:56 Camera_Timer_2sec.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Camera_click_short.ogg
-rw-r--r-- root root 3726 2014-08-27 14:56 Camera_empty.ogg
-rw-r--r-- root root 14351 2014-08-27 14:56 Charger_Connection.ogg
-rw-r--r-- root root 6773 2014-08-27 14:56 Dialer_new.ogg
-rw-r--r-- root root 18648 2014-08-27 14:56 Dock.ogg
-rw-r--r-- root root 786319 2014-08-27 14:56 Fairy_Fountain.ogg
-rw-r--r-- root root 637833 2014-08-27 14:56 Gentle_Spring_Rain.ogg
-rw-r--r-- root root 4713 2014-08-27 14:56 Highlight.ogg
-rw-r--r-- root root 4705 2014-08-27 14:56 HoverPointer.ogg
-rw-r--r-- root root 10937 2014-08-27 14:56 Lock.ogg
-rw-r--r-- root root 6907 2014-08-27 14:56 Lock_none_effect.ogg
-rw-r--r-- root root 8559 2014-08-27 14:56 Lock_tension.ogg
-rw-r--r-- root root 14323 2014-08-27 14:56 LowBattery.ogg
-rw-r--r-- root root 470154 2014-08-27 14:56 Media_preview_Over_the_horizon.ogg
-rw-r--r-- root root 6687 2014-08-27 14:56 New_chat.ogg
-rw-r--r-- root root 97411 2008-08-01 14:00 PowerOn.ogg
-rw-r--r-- root root 11242 2014-08-27 14:56 S_Beam_end.ogg
-rw-r--r-- root root 12070 2014-08-27 14:56 S_Beam_error.ogg
-rw-r--r-- root root 13673 2014-08-27 14:56 S_Beam_start.ogg
-rw-r--r-- root root 9922 2014-08-27 14:56 S_HW_Touch.ogg
-rw-r--r-- root root 4766 2014-08-27 14:56 S_SIP_Backspace.ogg
-rw-r--r-- root root 6830 2014-08-27 14:56 Sent_chat.ogg
-rw-r--r-- root root 558556 2014-08-27 14:56 Serenity.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 Shutter.ogg
-rw-r--r-- root root 6210 2014-08-27 14:56 Shutter_multiple.ogg
-rw-r--r-- root root 7294 2014-08-27 14:56 SideSync_Connected.ogg
-rw-r--r-- root root 838441 2014-08-27 14:56 Sparkling_Mist.ogg
-rw-r--r-- root root 15785 2014-08-27 14:56 TW_Battery_caution.ogg
-rw-r--r-- root root 8350 2014-08-27 14:56 TW_Call_Disconnect.ogg
-rw-r--r-- root root 4789 2014-08-27 14:56 TW_SIP.ogg
-rw-r--r-- root root 7868 2014-08-27 14:56 TW_Silent_mode_off.ogg
-rw-r--r-- root root 9926 2014-08-27 14:56 TW_Touch.ogg
-rw-r--r-- root root 5515 2014-08-27 14:56 TW_Volume_control.ogg
-rw-r--r-- root root 16795 2014-08-27 14:56 Tap_tension.ogg
-rw-r--r-- root root 5176 2014-08-27 14:56 TextSelection.ogg
-rw-r--r-- root root 816576 2014-08-27 14:56 The_Secret_Forest.ogg
-rw-r--r-- root root 18669 2014-08-27 14:56 Undock.ogg
-rw-r--r-- root root 10939 2014-08-27 14:56 Unlock.ogg
-rw-r--r-- root root 7287 2014-08-27 14:56 Unlock_none_effect.ogg
-rw-r--r-- root root 15468 2014-08-27 14:56 Unlock_tension.ogg
-rw-r--r-- root root 12860 2014-08-27 14:56 Voice_processing.ogg
-rw-r--r-- root root 8038 2014-08-27 14:56 Voice_start.ogg
-rw-r--r-- root root 10141 2014-08-27 14:56 Voice_stop.ogg
-rw-r--r-- root root 10235 2014-08-27 14:56 Zero_Clickr_Ready.ogg
-rw-r--r-- root root 9520 2014-08-27 14:56 camera_click.ogg
-rw-r--r-- root root 13878 2014-08-27 14:56 lens_flare_lock.ogg
-rw-r--r-- root root 4407 2014-08-27 14:56 lens_flare_unlock_silence.ogg
[email protected]:/system/media/audio/ui $
Here and in the /audio/ dir you can insert other music for alarms,notification,ringtones and ui interfaces like :Auto_focus,Undock,Unlock,Camera sounds ...
We are interested in PowerOn.ogg - our boot song
It's the ogg format. Save your favourite boot - Power On sound as PowerOn.ogg in /system/media/audio/ui.
You can do it manually or throught ADB,Terminal emulator :
Here is for the ADB :
First make your /system/ is rw (readwrite) :
Code:
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ #
Copy your files to SD root (bootsamsung.qmg,bootsamsungloop.qmg,PowerOn.ogg) or anywhere in the phone, local ADB folder on comp...
overwite *.qmg files in /system/media/ and PowerOn.ogg in /system/media/audio/ui/
Code:
[email protected]:/system/media # cd /storage/extSdCard
cd /storage/extSdCard
[email protected]:/storage/extSdCard # cp bootsamsung.qmg /system/media/bootsamsung.qmg
ystem/media/bootsamsung.qmg
[email protected]:/storage/extSdCard # cp bootsamsungloop.qmg /system/media/bootsamsungloop.qmg
g /system/media/bootsamsungloop.qmg
[email protected]:/storage/extSdCard # cp PowerOn.ogg /system/media/audio/ui/PowerOn.ogg
m/media/audio/ui/PowerOn.ogg
[email protected]:/storage/extSdCard #
remount back to ro (readonly) and run bootanimation throught adb to check graphic Power ON sequence only:
Code:
[email protected]:/storage/extSdCard # mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ # bootanimation
bootanimation
^C
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
You can also change the permission of the files before ro remount :
chmod 644 is the primary for those 3 files ( -rw-r--r-- [email protected] ) but not needed if su (#) enabled
Power Off phone and enjoy ... U can change other stuff PowerOff, shutdown ...
Have also provided mine bootanim, loop and sound as update zip recovery package included.
... for now I'm working on to change the boot logo before boot animation.Help or any other infos are mostly wanted.
And about the *.qmg files, check and search the xda, there are lot about it ...
The animations I used are original files from other Samsung devices, PoverOn wav found and converted from the internet.
The update script :
Code:
ui_print("********************************");
ui_print("* StratOS boot animation,sound *");
ui_print("********************************");
ui_print("");
ui_print("For SM-G355H*");
run_program("/xbin/busybox", "mount", "/system");
run_program("/xbin/busybox", "mount", "-o", "rw,remount", "/system", "/system");
ui_print("Deleting files");
delete("/system/media/audio/ui/PowerOn.ogg");
delete("/system/media/bootsamsung.qmg");
delete("/system/media/bootsamsungloop.qmg");
ui_print("Extracting files");
package_extract_dir("system", "/system");
ui_print("");
ui_print("Finished");
run_program("/xbin/sleep", "5");
unmount("/system");
Sent from my SM-G355HN using XDA Free mobile app
Click to expand...
Click to collapse
Why you use adb? its easy to use a root file manager like ESfilemanager....and just copy and give permissions. Im doing it like that and no problems.......just an idea.
p/s: I send you a PM....I make a zip to deodex the rom...so we can use the TW mods in xda (all the mods are for Deodex roms). I cant test it, but maybe its a good start point to mod the phone.
Thanks for your hardwork! :good:

Cocolopes said:
Why you use adb? its easy to use a root file manager like ESfilemanager....and just copy and give permissions. Im doing it like that and no problems.......just an idea.
p/s: I send you a PM....I make a zip to deodex the rom...so we can use the TW mods in xda (all the mods are for Deodex roms). I cant test it, but maybe its a good start point to mod the phone.
Thanks for your hardwork! :good:
Click to expand...
Click to collapse
Yes it would be great.
Some folders are not visible on different carriers,manufacturers, because they have to be manualy mounted into partition of folder, just like /system/media/, but you can manualy mount it for rw if you know where to link to/mount to.
It's good to post some code to enforce other users to see what's begind ...
Have checked the PM, will try something tomorrow ...

StratOS_HTC said:
Yes it would be great.
Some folders are not visible on different carriers,manufacturers, because they have to be manualy mounted into partition of folder, just like /system/media/, but you can manualy mount it for rw if you know where to link to/mount to.
It's good to post some code to enforce other users to see what's begind ...
Have checked the PM, will try something tomorrow ...
Click to expand...
Click to collapse
well...I just did it...and everything works great. (I have to manualy delete de odex files cuz stock recovery dont use the script to do it in the zip)
now I will try some mods for other samsung phones...

Cocolopes said:
well...I just did it...and everything works great. (I have to manualy delete de odex files cuz stock recovery dont use the script to do it in the zip)
now I will try some mods for other samsung phones...
Click to expand...
Click to collapse
Well after quick view there is I guess an error in update binnary in zip :
Code:
ui_print("------------------------------------------");
ui_print(" Installing Deodexed Apps and Framework ");
ui_print("------------------------------------------");
ui_print(" Deleting odex-files ");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("del_odex.sh", "/data/local/tmp/del_odex.sh");
set_perm(0, 0, 0777, "/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
run_program("/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
You should manually edit it
the *.sh is :
Code:
#!/sbin/sh
rm -rf /system/app/*.odex
rm -rf /system/framework/*.odex
rm -rf /system/priv-app/*.odex
exit 0
Think in sh U have to set the fs /system/ to rw again before deleting
Yes, thing are doing ok. I could upload the SIO version of latest rom, it contains some usefull apps ... if u want to.
So the update will have to clear those *.odex

StratOS_HTC said:
Well after quick view there is I guess an error in update binnary in zip :
Code:
ui_print("------------------------------------------");
ui_print(" Installing Deodexed Apps and Framework ");
ui_print("------------------------------------------");
ui_print(" Deleting odex-files ");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("del_odex.sh", "/data/local/tmp/del_odex.sh");
set_perm(0, 0, 0777, "/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
run_program("/data/local[COLOR="Red"][B]//[/B][/COLOR]tmp/del_odex.sh");
You should manually edit it
the *.sh is :
Code:
#!/sbin/sh
rm -rf /system/app/*.odex
rm -rf /system/framework/*.odex
rm -rf /system/priv-app/*.odex
exit 0
Think in sh U have to set the fs /system/ to rw again before deleting
Yes, thing are doing ok. I could upload the SIO version of latest rom, it contains some usefull apps ... if u want to.
So the update will have to clear those *.odex
Click to expand...
Click to collapse
Great...I just replace some system apps like systemIU, secSetting, SecSettingProvider and other to get some new options...like 7 effects in lock screen.... so options dont work...and I need to fix it...but Its something....

boot logo ?? where
Trying to get something for boot logo,as mentioned before param have the logo,but this thing doesn't work or it has to be changed.It has to be somewhere in low level of boot sequence.
Messing with decompilation of kernel and bootloader,spl to check for the image.

Boot logo
StratOS_HTC said:
Trying to get something for boot logo,as mentioned before param have the logo,but this thing doesn't work or it has to be changed.It has to be somewhere in low level of boot sequence.
Messing with decompilation of kernel and bootloader,spl to check for the image.
Click to expand...
Click to collapse
As mentioned before, have made a sorted tar ball but it won't work. The file is accepted in block ( dev/block/mmcblk0p13 ), but as told before the logo must be extracted from somwhere else before. The question is from where and why ?
On other Samsung devices it is in the param (dev/block/mmcblk0p13). If any1 wants to check it with odin and create your own tar & md5 checksum feel free to visit : http://www.rwilco12.com/forum/showthread.php?tid=92 but I guess it will be the same .
Buying a beer if some1 get this right or find out where the hell is it ...

mmcblk0p13 - Samsung leftover ?
Update : The param.lfs / PARAM/ mmcblk0p13 is leftover.
Original files ( Even download logo ... ) is/are stored somewhere else.
Have deleted / changed mmvblk0p13 to 0 b file, at boot it shows logo, so the logo must be somwhere in low level.
sboot.bin / SPRDCP.img / SPRDDSP.img / nvitem.bin / hidden.img ???
Help appriciated

Samsung osrc comments delivery notification
[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
classification : Mobile Phone
model name : SM-G355HN_EUR
Dear Customer,
Thank you for your interest in our product.
There are some proprietary which we developed by ourselves in kernel.
When you make custom ROM, it will be different from our offical ROM because of not opening our proprietary.
Our offical ROM is optimized for our device, so we don't recommand and guarantee to execute custom ROM.
So, we can't officially give you information how to execute or download your custom ROM.
However you can easily find it through internet because there are lot's of information regarding what you want.
It would be appreciated if you can understand our situation.
Please accept our apology for not being able to handle your request up to your satisfaction.
Thank you. Sincerely yours,
Select URL below to evaluate satisfaction for our reply.
http://opensource.samsung.com/satisfaction/mail_satisfaction.do?mailId=???????
----- Original Message -----
Sender : StratOS_HTC#####
Date : 2015-03-21 19:28:42 (GMT+09:00)
Greetings.
I have created the custom rom based on stock release and modified by my needs, even changed kernel,ramdisk and recovery sucessfully.
I have a problem : Cannot find resource to edit boot logo.
The param partition/ param.lfs files are just leftovers. Just want to know where can I find resources to edit boot logo ( not boot animation ).
I'm asking this because I really don't want to get messed with bootloader and other low level boot sources.
I'm just asking for reveal of the resources to edit / how to recompile the boot logo for Samsung G355HN Galaxy Core 2 model.
Waiting for your reply.
Thx in advance.
Regards
Click to expand...
Click to collapse
Samsung Open Source Release Center
http://opensource.samsung.com

need original bootlogo for core 2
StratOS_HTC said:
Greeting every1
This is gor Galaxy Core 2 phones ( SM-G355HN )
Been messing about the logo on my GC2. As mentioned it's in the param.lfs (for flashing with Odin) or /dev/block/mmcblk0p13.
You can do it with emulator,root explorer , adb or any other way ...
With the adb :
Code:
C:\ADB>cmd /k cd "C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools"
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
cat /dev/block/mmcblk0p13>/mnt/extSdCard/param
[email protected]:/ # cd /mnt/extSdCard
cd /mnt/extSdCard
[email protected]:/mnt/extSdCard # ls
ls
Android
Apk's
DCIM
LOST.DIR
bluetooth
device.nng
iGO
iGO primo 9.6.29.404739 - 30 jun 2014
param
[email protected]:/mnt/extSdCard # tar
tar
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: tar -[cxtZzJjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
Z (De)compress using compress
z (De)compress using gzip
J (De)compress using xz
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
1|[email protected]:/mnt/extSdCard # tar -t -f param
tar -t -f param
adv-env.img
ani_upload_1_kernel_panic.jpg
ani_upload_2_cp_crash.jpg
ani_upload_3_forced_upload.jpg
ani_upload_4_hardware_reset.jpg
ani_upload_4_smpl.jpg
ani_upload_4_unknown_reset.jpg
ani_upload_4_watchdog_reset.jpg
ani_upload_4_wtsr.jpg
ani_upload_4_wtsr_smpl.jpg
ani_upload_5_user_fault.jpg
ani_upload_6_hsic_disconnected.jpg
download.jpg
download_error.jpg
logo.jpg
lpm.jpg
sud_0.jpg
sud_1.jpg
sud_2.jpg
sud_3.jpg
sud_4.jpg
sud_5.jpg
sud_6.jpg
sud_7.jpg
sud_8.jpg
sud_9.jpg
warning.jpg
[email protected]:/mnt/extSdCard #
After changing logo, messing with photos,sizes of the file and other stuff and when i copy new image and replace the original after booting I get default logo.
The tar files in this case doesn't follow the user and file permissions ?
Have check the image and block after changing logo and image, the image/logo is accepted and installed into, but guess there is some checking or something else while booting. The installed image isn't accepted during boot,guess It's missplaced with the original ("from where ?") or am I missing some other possible way the image is/can be stored ina any other image/partition.
Has any1 tried this with our phone ?
The files for flash the param partition and self flashing archive is included as attachement.
The boot logo (logo.jpg) is the file download.jpg.
The animation "Samsung" is in the /system/media inside bootsamsung.qmg
You can check it via bootanimation in /system/bin, use it via adb or u will have to take the battery out to stop the animation or get to the home screen.
Click to expand...
Click to collapse
The process seems.quite complicated n i didnt understand..
Will you plz upload the original stock boot logo and procedure to flast it

StratOS_HTC said:
As mentioned before, have made a sorted tar ball but it won't work. The file is accepted in block ( dev/block/mmcblk0p13 ), but as told before the logo must be extracted from somwhere else before. The question is from where and why ?
On other Samsung devices it is in the param (dev/block/mmcblk0p13). If any1 wants to check it with odin and create your own tar & md5 checksum feel free to visit : http://www.rwilco12.com/forum/showthread.php?tid=92 but I guess it will be the same .
Buying a beer if some1 get this right or find out where the hell is it ...
Click to expand...
Click to collapse
Try for boot animation:
framework-res/assets/sounds/bootanim0.raw and bootanim1.raw
about samsung splash boot img:
http://forum.xda-developers.com/galaxy-s2/themes-apps/logo-img-param-lfs-t1315401

Y300-0100 said:
Try for boot animation:
framework-res/assets/sounds/bootanim0.raw and bootanim1.raw
Click to expand...
Click to collapse
Boot animation/boot sounds for our device has allready been changed along time ago in this post by me :
http://forum.xda-developers.com/showpost.php?p=56610974&postcount=3
Y300-0100 said:
about samsung splash boot img:
http://forum.xda-developers.com/galaxy-s2/themes-apps/logo-img-param-lfs-t1315401
Click to expand...
Click to collapse
The splash / lfs is just another leftower. The splash is located in kernel itself. The beer for boot logo for our devices is still in my fridge
http://forum.xda-developers.com/showpost.php?p=59556505&postcount=11
jasbinkarki said:
The process seems.quite complicated n i didnt understand..
Will you plz upload the original stock boot logo and procedure to flast it
Click to expand...
Click to collapse
The "process" is simple, it's not a process. The boot logo is hidden/integrated in lower level kernel
I cannot get source or resource to handle it. So for now still no knowable option how to do it.
Boot anims,boot sounds are simple to change, see previous post in this thread.
BEER :fingers-crossed:

Hey can anyone here will create a custom boot animation in qmg format..
i want windows xp boot animation in qmg format.. i

[TUT] ROOT HD10 (2017), HD8(2016-2017) - EASY SuperSu

Update - March 23rd, 2019.
There is now an excellent offline rooting method for HD10 (2017), HD8(2016-2018), all current FireOS versions, thanks to the fantastic effort by @diplomatic - link. This new root is obtained within a few seconds, so it is very fast. To install permanent root after mtk-su for HD10 (2017), HD8 (2016-2017), use the scripts by @Rortiz2 in here: v2.1, or v1.0 (see this link for a Linux script). For HD8 (2018), there is a dedicated full bootloader unlocking and permanent root guide - link. For HD10 (2017) there is also a full bootloader unlocking procedure available - link. The historical Kingoroot rooting procedure for HD10 (2017) is below. As a friendly reminder, once you have a root shell (obtained by any means), ensure that you disable OTA updates as to avoid getting an unrootable update (except for HD8 (2018) - do not run the commands below before you unlock the bootloader!!!):
Code:
mount -w -o remount /system
mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
ls -l /system/priv-app/DeviceSoftwareOTA/
The original Kingoroot method for HD10 (2017), all current FireOS versions - EASY SuperSu
Update v0.9, 12/29/18 As empasized by shonkin in this post, the method still works for FireOS 5.6.3.4. Enjoy!!! I would never have expected the hole to last his long ...
Update v0.8, 01/26/18 - as first reported by @najoor in this post, FireOS 5.6.0.1 is rootable! Today I verified this myself after a somewhat unsuccessful FlashFire update.
Update v0.7, 01/14/18 - @freaky2xd made a video with these rooting instructions, please follow it if you prefer a visual guide (here or here)
Update v0.6, 01/09/18 - there were reports that dr.fone app seems to be able to root the device as well. I took dr.fone for a spin, and based on its bloatedness and a few other annoying features, my personal recommendation is that you stick with the devil we know - Kingoroot (link)
Update v0.5, 01/04/18 - add a DOS bat file to remove any possible updates to Amazon packages
Update v0.4, 01/02/18 - title update
Update v0.3, 12/31/17 - light clean up; I got into a bootloop, and had to sideload a stock ROM & re-root - a.k.a. "eat my own dogfood" - Everything works fine.
Update v0.2, 12/30/17 - some redundant commands are removed.
Update v0.1, 12/30/17 - the rooting procedure is essentially taken from @retyre (here and here). Except, the instructions below include a lot of details, and handle mostly everything from the PC/ADB side. Try, and report back. GOOD LUCK!
Here is the guide to the painless root (while out of the box FireOS allows it; right now all FireOS versions up to and including 5.6.0.1 - the current OTA - are rootable). The key enabler is the original post by @ztrund (link), great work blazing the trail (and motivating me to get another Fire tablet ASAP, LOL).
Given that the devices will be shipping with the (older) rootable FireOS for the next few months (but beware of the upcoming updates - see below !!!), there is a good window of opportunity to acquire a rootable Fire HD 10, and root it. As of Dec 27th 2017, there are no reports yet of non-rootable OTAs, but those OTAs will be coming soon, count on it!
The utmost goal here is to preserve the earliest FireOS version that you get, and not let it get updated by Amazon on a whim.
I am starting with a recently bought Fire HD 10 2017 (light refurb from eBay, missed the Black Friday mega sale ). I have FireOS 5.5.0.0 (earlier than 5.6.0.0!), version name 5.3.5.1 (591450020)
Part I (avoiding Amazon updating procedure upon the initial Fire setup) - this can (almost safely) be skipped today (end of Dec, 2017), since there are no reports of unrootable OTAs yet
Low tech way (thanks to @Blaiser47 and @retyre for suggestions!):
Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
Choose any option on that WiFi screen, press cancel, and then skip
Once Alexa shows up, swipe down from the top, turn on Airplane mode just to be sure
High tech way:
Set up a dedicated slow router, limit upload/download speed to ~25 kbps (this is the trickiest part, I have a dedicated Tomato router which I use to control traffic)
Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
Connect Fire to your slow router
Once Fire finds Internet, it'll immediately have "Checking for updates" on the screen, this is where the slow router should kick in, and do the trick of forcing the update to give up
Wait a bit for updates, hopefully, it won't find them, if found something, do factory reset, and repeat (on my 1st try it did find the update, although, could not download it quickly enough, I did a factory reset via Pwr&Vol+ recovery mode, and tried again - the 2nd time it skipped the update due to the slowness of the connection)
Sign in to Amazon account when prompted
Once Alexa shows up, swipe down from the top, turn on Airplane mode - no more risk of updates!!!
Part II (rooting via Kingoroot, disabling OTA, and getting SuperSu replacement, as per @retyre recommendations)
Take your Fire HD as is, do not do anything dramatic such as "factory reset", Amazon ROM sideloading, etc
Swipe down from the top, turn on Airplane mode - to ensure that there are no OTA updates during the procedure
In "Settings/Device Options", tap "Serial Number" 7 times, a menu "Developer Options" will appear
In "Settings/Device Options/Developer Options", turn ADB debugging to ON (under "Debugging")
In "Settings/Security", turn "Apps from Unknown Sources" to ON
Download ADB to your PC (link)
Setup ADB drivers on your PC, connect Fire to your PC, make sure "adb devices" command shows your Fire device, authorize ADB connection on Fire
Download SuperSu 2.79 (this exact version!!!) to your PC from this link, place it into your ADB PC folder. The filename of this apk will be assumed to be SuperSU-v2.79-20161205182033.apk below
Download the attached su64.zip to your PC (see the attachment below), unzip to your ADB PC folder
Open a CMD window in ADB PC folder (this will be called ADB_cmd window in the following steps), type
Code:
adb devices
adb uninstall eu.chainfire.supersu
This is a clean up of possible old SuperSu (just in case), ignore any errors you may get (if SuperSu is absent ...)
Download Kingoroot to your PC (link), install, let it update
Connect Fire to your PC; launch Kingoroot on PC; before pushing the big "ROOT" button in Kingoroot, uncheck a small box in the lower left corner for "Install recommended app" ; push "ROOT" button; wait for Kingoroot to root
Once Kingoroot succeeds, open a 2nd CMD window in ADB PC folder to your Fire (this will be called ADB_root window in the following steps), get a root shell, and disable OTA updates
Code:
adb shell
su
mount -w -o remount /system
mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
ls -l /system/priv-app/DeviceSoftwareOTA/
ignore any errors you may get while doing this; after 'su', you should see root (#) prompt here
Switch to the first ADB_cmd window, type
Code:
adb uninstall com.lionmobi.powerclean
adb uninstall com.kingoapp.link
adb uninstall kingoroot.supersu
adb install SuperSU-v2.79-20161205182033.apk
adb shell "am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity"
Skip this step - it is not needed
Switch to the second ADB_root window (with # prompt), type
Code:
cd /data/local/tmp
mount -w -o remount /system
cp ./su64 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su64 /system/xbin/su
chmod 0755 /system/xbin/su
am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity
On your Fire, SuperSu should pop up. Update SuperSu binary as "Normal", it should report "Installation failed." Proceed to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Uninstall all the junk from Kingoroot on your Fire, thanks to @fstanis for detailed instructions (copied here, executed from PC):
Code:
adb uninstall com.nemo.vidmate
adb shell rm -rf /sdcard/VidMate
adb shell rm -rf /sdcard/.a
adb shell rm -rf /sdcard/.DataStorage
adb shell rm -rf /sdcard/.UTSystemConfig
Some troubleshooting options:
If you believe you have the correct FireOS, but Kingoroot (or SuperSu) still fail, download the attached no_amzn_updates.zip to your PC, unzip to your ADB PC folder, open a CMD window in ADB PC folder, and type
Code:
.\no_amzn_updates.bat
The script will attempt to uninstall any apk updates to the official Amazon packages. Then repeat the rooting procedure from Step 1 skipping as necessary. See this post for more additional info on what the script does.
If you mess up your /system too much and get into a bootloop with "Fire" logo - use this post for links to the official Amazon ROM files; these bin's can be sideloaded via "adb sideload" in recovery
Want to say thanks by clicking the "Thanks" button ?
{
"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"
}

Fire HD 10 ROM links & misc :
Update: Uploaded modified Supersu 2.82 SR5 ready to be flashed in FlashFire. It really represents the Chainfire's swan song, the last of the true SuperSu versions, the end of the era !!!
Fire HD 10 (7th Gen 2017) ROM links from Amazon (use for sideloading your preferred version in case you mess up). If possible, turn off WiFi before sideloading a bin file - you don't want to catch an OTA while it's loading!
FireOS 5.6.3.0 (reports say that it's still rootable, the downgrade behavior is not clear)
update-kindle-suez-40.6.2.6_user_626533320.bin
update-kindle-40.6.2.6_user_626533320.bin
FireOS 5.6.2.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.1.2_user_612495820.bin
FireOS 5.6.1.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.0.5_user_605485120.bin
System image (restore via FlashFire) link. Unzip files to /sdcard/FlashFire/Backups/5.6.1.0, rename the 2 img to bin extensions. Create md5 sum files (in a shell, type "md5 system.bin > system.md5", same for boot.bin) The system image includes SuperSu, Xposed, Busybox; OTA apk is NOT renamed.
FireOS 5.6.0.1
update-kindle-40.5.9.5_user_595550320.bin
System image (restore via FlashFire v0.24) - link. Unzip files to /sdcard/FlashFire/Backups/5.6.0.1. The system image includes SuperSu, Xposed, Busybox; OTA apk is renamed.
FireOS 5.6.0.0
update-kindle-40.5.9.5_user_595457320.bin
FireOS 5.6.0.0
update-kindle-40.5.9.5_user_595457020.bin
FireOS 5.5.0.0
update-kindle-40.5.9.1_user_591450020.bin
In addition, please find attach a SuperSu zip that works with Flash Fire v0.24 (tested with FireOS 5.5.0.0 & 5.6.0.0).
The file was created by taking SuperSu v2.82 zip from this link (file name - SuperSU-v2.82-201705271822.zip).
Then in META-INF\com\google\android\update-binary I replaced one line forcing SuperSu to install armv7 binaries instead of arm64:
Code:
if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=arm64; SYSTEMLIB=/system/lib64; APPPROCESS64=true; fi;
with this one:
Code:
if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=armv7; fi;
Everything else is identical to the official version.
Using the official SuperSu zip will cause a bootloop - it looks like Fire HD 10 is not quite arm64 yet, and needs armv7 version of su binaries to work.

Useful tips & information:
How to install Xposed & Flashfire for easy backups and ROM updates
Follow this post by @retyre (and thank him!!!): link
Note: With stock FlashFire versions, the latest Flashfire version you can use is v0.24 (see the attached v0.24 apk, it needs the date patch which requires Xposed installed). Alternatively, it is possible to replace a library in Flashfire v0.51, and make v0.51 work:
link1
link2
link3
For convenience, I've done this procedure to the free FlashFire v.51 version using free apktool, and attached the file below (the signature will not match with the original FlashFire signed by @Chainfire, so you will need to uninstall other FlashFire packages before installing this one!)
With v0.51, uncheck two options (as per link2):
1) Emulate framebuffer in Settings
2) Mount /system read/write (after you choose the update file).
If you don't do 2), Flashfire v.51 will just sit there and never do anything
How to enable Amazon packages (apk) updates but prevent the ROM updates (keeping root & rootable rom).
1) Edit /system/build.prop and change ro.build.version.number to have "9" as the first value instead of "5", as recommended in this link
2) Reboot
3) Enable OTA by ensuring that /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed back to apk from apk_
4) Reboot
At this point the Fire will download a lot of apk packages, and will update Amazon system components (keeping FireOS version the same).
Partition trivia:
Partition info (gdisk binary) :
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 907.7M 80.0K 907.6M 4096
/dev/logd 512.0K 96.0K 416.0K 4096
/sys/fs/cgroup 907.7M 12.0K 907.7M 4096
/mnt/asec 907.7M 0.0K 907.7M 4096
/mnt/obb 907.7M 0.0K 907.7M 4096
/system 1.5G 1.2G 317.9M 4096
/data 26.5G 1.1G 25.4G 4096
/data/metrics 5.8M 232.0K 5.6M 4096
/cache 410.7M 14.9M 395.8M 4096
/mnt/sqfs 79.8M 79.8M 0.0K 32768
/mnt/cd-rom 1.2M 1.2M 0.0K 2048
/mnt/shell/emulated 26.5G 1.1G 25.4G 4096
/storage/emulated 907.7M 0.0K 907.7M 4096
/storage/emulated/0 26.5G 1.1G 25.4G 4096
/storage/emulated/0/Android/obb 26.5G 1.1G 25.4G 4096
/storage/emulated/legacy 26.5G 1.1G 25.4G 4096
/storage/emulated/legacy/Android/obb 26.5G 1.1G 25.4G 4096
[email protected]:/data/local/tmp # ./gdisk -l /dev/block/mmcblk0
./gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): B1541C10-343E-474B-B5B2-05796C64E992
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326
Partitions will be aligned on 1024-sector boundaries
Total free space is 990 sectors (495.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 1024 7167 3.0 MiB 8300 proinfo
2 7168 16383 4.5 MiB 8300 PMT
3 16384 18431 1024.0 KiB 8300 kb
4 18432 20479 1024.0 KiB 8300 dkb
5 20480 22527 1024.0 KiB 8300 lk
6 22528 32767 5.0 MiB 8300 tee1
7 32768 43007 5.0 MiB 8300 tee2
8 43008 123903 39.5 MiB 8300 metadata
9 123904 124927 512.0 KiB 8300 MISC
10 124928 141311 8.0 MiB 8300 reserved
11 141312 174079 16.0 MiB 8300 boot
12 174080 208895 17.0 MiB 8300 recovery
13 208896 3515391 1.6 GiB 8300 system
14 3515392 4383743 424.0 MiB 8300 cache
15 4383744 61071326 27.0 GiB 8300 userdata
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 81664 loop0
7 1 1254 loop1
7 2 10240 loop2
179 0 30535680 mmcblk0
179 1 3072 mmcblk0p1
179 2 4608 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 40448 mmcblk0p8
179 9 512 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 17408 mmcblk0p12
179 13 1653248 mmcblk0p13
179 14 434176 mmcblk0p14
179 15 28343791 mmcblk0p15
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 33 2 mmcblk0boot0p1
179 34 2 mmcblk0boot0p2
179 35 256 mmcblk0boot0p3
179 36 747 mmcblk0boot0p4
[email protected]:/ # ls -l /dev/block
ls -l /dev/block
brw------- root root 7, 0 2017-12-28 11:05 loop0
brw------- root root 7, 1 2017-12-28 11:05 loop1
brw------- root root 7, 2 2017-12-28 11:05 loop2
brw------- root root 7, 3 2017-12-28 11:05 loop3
brw------- root root 7, 4 2017-12-28 11:05 loop4
brw------- root root 7, 5 2017-12-28 11:05 loop5
brw------- root root 7, 6 2017-12-28 11:05 loop6
brw------- root root 7, 7 2017-12-28 11:05 loop7
brw-rw---- root system 179, 0 2017-12-28 11:05 mmcblk0
brw-rw---- root system 179, 32 2017-12-28 11:05 mmcblk0boot0
brw------- root root 179, 33 2017-12-28 11:05 mmcblk0boot0p1
brw------- root root 179, 34 2017-12-28 11:05 mmcblk0boot0p2
brw------- root root 179, 35 2017-12-28 11:05 mmcblk0boot0p3
brw------- root root 179, 36 2017-12-28 11:05 mmcblk0boot0p4
brw-rw---- root system 179, 64 2017-12-28 11:05 mmcblk0boot1
brw------- root root 179, 1 2017-12-28 11:05 mmcblk0p1
brw------- root root 179, 10 2017-12-28 11:05 mmcblk0p10
brw------- root root 179, 11 2017-12-28 11:05 mmcblk0p11
brw------- root root 179, 12 2017-12-28 11:05 mmcblk0p12
brw------- root root 179, 13 2017-12-28 11:05 mmcblk0p13
brw------- root root 179, 14 2017-12-28 11:05 mmcblk0p14
brw------- root root 179, 15 2017-12-28 11:05 mmcblk0p15
brw------- root root 179, 2 2017-12-28 11:05 mmcblk0p2
brw------- root root 179, 3 2017-12-28 11:05 mmcblk0p3
brw------- root root 179, 4 2017-12-28 11:05 mmcblk0p4
brw------- root root 179, 5 2017-12-28 11:05 mmcblk0p5
brw------- root root 179, 6 2017-12-28 11:05 mmcblk0p6
brw------- root root 179, 7 2017-12-28 11:05 mmcblk0p7
brw------- root root 179, 8 2017-12-28 11:05 mmcblk0p8
brw------- root root 179, 9 2017-12-28 11:05 mmcblk0p9
brw-rw---- root system 179, 96 2017-12-28 11:05 mmcblk0rpmb
drwxr-xr-x root root 2017-12-28 11:05 platform
drwx------ root root 2017-12-28 11:05 vold
brw------- root root 254, 0 2017-12-28 11:05 zram0
[email protected]:/ # ls -l /dev/block/platform/mtk-msdc.0/by-name/
ls -l /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-12-28 11:05 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-12-28 11:05 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-12-28 11:05 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-12-28 11:05 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2017-12-28 11:05 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2017-12-28 11:05 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2017-12-28 11:05 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2017-12-28 11:05 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-12-28 11:05 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-12-28 11:05 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-12-28 11:05 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-12-28 11:05 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-12-28 11:05 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-12-28 11:05 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-12-28 11:05 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-12-28 11:05 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-12-28 11:05 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-12-28 11:05 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-12-28 11:05 userdata -> /dev/block/mmcblk0p15
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 3786.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/mmcblk0: 29 GB, 31268536320 bytes, 61071360 sectors
3786 cylinders, 256 heads, 63 sectors/track
Units: cylinders of 16128 * 512 = 8257536 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors
Size Id Type
/dev/block/mmcblk0p1 0,0,2 1023,255,63 1 4294967295 4294967295 2047G ee EFI GPT

bibikalka said:
Here is the guide to the painless root (while out of the box FireOS allows it - right now all versions up to FireOS 5.6.0.0 are rootable). The key enabler is the original post by @ztrund (link), great work blazing the trail (and motivating me to get another Fire tablet ASAP, LOL).
Given that the devices will be shipping with the (older) rootable FireOS for the next few months (but beware of the upcoming updates - see below !!!), there is a good window of opportunity to acquire a rootable Fire HD 10, and root it. As of Dec 27th 2017, there are no reports yet of non-rootable OTAs, but those OTAs will be coming soon, count on it!
The utmost goal here is to preserve the earliest FireOS version that you get, and not let it get updated by Amazon on a whim.
I am starting with a recently bought Fire HD 10 2017 (light refurb from eBay, missed the Black Friday mega sale ). I have FireOS 5.5.0.0 (earlier than 5.6.0.0!), version name 5.3.5.1 (591450020)
Part I (avoiding Amazon updating procedure upon the initial Fire setup) - this can (almost safely) be skipped today (end of Dec, 2017), since there are no reports of unrootable OTAs yet
Set up a dedicated slow router, limit upload/download speed to ~25 kbps (this is the trickiest part, I have a dedicated Tomato router which I use to control traffic)
Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
Connect Fire to your slow router
Once Fire finds Internet, it'll immediately have "Checking for updates" on the screen, this is where the slow router should kick in, and do the trick of forcing the update to give up
Wait a bit for updates, hopefully, it won't find them, if found something, do factory reset, and repeat (on my 1st try it did find the update, although, could not download it quickly enough, I did a factory reset via Pwr&Vol+ recovery mode, and tried again - the 2nd time it skipped the update due to the slowness of the connection)
Sign in to Amazon account when prompted
Once Alexa shows up, swipe down from the top, turn on Airplane mode - no more risk of updates!!!
Done
Click to expand...
Click to collapse
Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.

Blaiser47 said:
Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.
Click to expand...
Click to collapse
Even simpler: Choose any option on that WiFi screen, press cancel, and then skip.
No offense to the OP, but given the kind of questions that get asked on these root threads, s/he probably lost half the visitors at "dedicated slow router."

Blaiser47 said:
Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.
Click to expand...
Click to collapse
retyre said:
Even simpler: Choose any option on that WiFi screen, press cancel, and then skip.
No offense to the OP, but given the kind of questions that get asked on these root threads, s/he probably lost half the visitors at "dedicated slow router."
Click to expand...
Click to collapse
Great! Awesome tip!!! Even better than messing with the router - I've updated the post! XDA is no strangers to people with routers, especially if it involves blocking Amazon updates.

Curious does this work for the Fire 8? If not why?

ginfest said:
Curious does this work for the Fire 8? If not why?
Click to expand...
Click to collapse
The key difference is that the 2017 Fire HD 10 has an 'arm64-v8a' compiled system (with 64 bits), while all the older Fires are running 'armeabi-v7a' (with 32 bits). So a 64 bit bug must have slipped in. But let's be clear, if history is any guide, an Amazon update plugging this rootable bug is imminent at this point in time. That is why I urge everybody with root to disable OTA for good by renaming /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to *apk_
Unfortunately, all the other Fires seem to be on lock down, for now I have disabled updates on all of mine (including Fire TV 2 sticks) in case an exploit becomes available in the future.

bibikalka said:
Great! Awesome tip!!! Even better than messing with the router - I've updated the post! XDA is no strangers to people with routers, especially if it involves blocking Amazon updates.
Click to expand...
Click to collapse
Thanks very much for your simple approach to rooting the hd 10, starting from unboxing it, and giving step by step guide.
What apps/tweaks/settings did you do after you rooted your HD 10 that you recommend we do, you seem to have a way of writing that is concise and to the point, very much appreciated. Any other suggestions for protecting the HD 10 from Amazon OTA updates or other hazards?
Thanks again.

Are you saying at the beginning that 5.6.0.0 is or is not rootable?

encephalon9986 said:
Are you saying at the beginning that 5.6.0.0 is or is not rootable?
Click to expand...
Click to collapse
It is rootable, I clarified, thanks!

Amazing, much easier than the previous guide!
For those interested, I wrote here how to remove the Kingoroot junk: https://forum.xda-developers.com/hd8-hd10/general/added-kingoroot-t3721482

After rooting can I remove FireOS and install Oreo?

Stansted said:
After rooting can I remove FireOS and install Oreo?
Click to expand...
Click to collapse
No. That requires an unlocked boot loader and a custom oreo rom. Neither are available yet and likely will not be

This guide didn't work for me. While KingoRoot reported achieving root, I couldn't run SuperSU because the SuperSU binary is already occupied (presumably by KingoRoot's version of SuperSU).

Stansted said:
This guide didn't work for me. While KingoRoot reported achieving root, I couldn't run SuperSU because the SuperSU binary is already occupied (presumably by KingoRoot's version of SuperSU).
Click to expand...
Click to collapse
Thanks!
I was not sure if unrooting was necessary, it now looks like you should launch SuperSu from the root shell after running unroot with Kingoroot:
Unroot Fire via Kingoroot on PC
Can you try and report back?

bibikalka said:
Thanks!
I was not sure if unrooting was necessary, it now looks like you should launch SuperSu from the root shell after running unroot with Kingoroot:
Unroot Fire via Kingoroot on PC
Can you try and report back?
Click to expand...
Click to collapse
I already tried that. It didn't work. After unrooting, SuperSU won't do anything because it doesn't detect root.

Stansted said:
I already tried that. It didn't work. After unrooting, SuperSU won't do anything because it doesn't detect root.
Click to expand...
Click to collapse
How about going back to su commands - link

Yeah, so I just double-checked to make sure I hadn't made a mistake. This doesn't work. While SuperSU launches just fine from the root shell, it won't do anything after you've unrooted with KingoRoot. And if you haven't unrooted with KingoRoot, the SuperSU binary is occupied. For the record, I'm using a 7th Gen Fire HD 10 running Fire OS 5.6.0.0. I might try retyre's method later, but I don't currently understand what he's asking me to do.

Stansted said:
Yeah, so I just double-checked to make sure I hadn't made a mistake. This doesn't work. While SuperSU launches just fine from the root shell, it won't do anything after you've unrooted with KingoRoot. And if you haven't unrooted with KingoRoot, the SuperSU binary is occupied. For the record, I'm using a 7th Gen Fire HD 10 running Fire OS 5.6.0.0. I might try retyre's method later, but I don't currently understand what he's asking me to do.
Click to expand...
Click to collapse
Download the 5.6.0.0 update .bin from here, adb sideload that file, and follow these steps to the letter. It will work.