Develop Bugs

[BOOT ANIMATION]SGS2 BIOS with Sound

This is based on the great work done by animelover - all credit goes to him.
NOTE: This is flashable via a custom recovery, like CWM
Preview:
http://www.youtube.com/watch?v=6NLi1-O8PJY
EDIT 9/27: Due to some tricky stuff Samsung/Sprint did with the boot animation, I edited this update script to remove the bootsamsung.qmg and bootsamsungloop.qmg files, enabling this to work with all ROMs regardless of if you're on stock kernel or not.
EDIT 10/27: Make sure you wipe Dalvik and Cache before rebooting after applying this.
EDIT 11/14: Some have reported that they have issues using this with their custom ROMs. Make sure you follow the manual steps some have identified below if that is you.
Download E4GT Animation

This is really nice. Anyone try it on our phones yet?

jirafabo said:
This is really nice. Anyone try it on our phones yet?
Click to expand...
Click to collapse
Yeah works and looks great. I also changed my startup sound to the old school mac startup sound and now I love it even more! I'm using Zedomax kernel v3 by the way.

jirafabo said:
This is really nice. Anyone try it on our phones yet?
Click to expand...
Click to collapse
I have modified this to work on any kernel/ROM for the E4GT. Works great.

Hi I flashed this via CWM and it works looks and sounds great. However after the boot animation is done, my screen goes blank for about 10 seconds then finally is done booting. Is this normal? I had previously tried installing by using zedomaxs guide using root explorer where u just copy and paste into system/media directory. Maybe I have some wrong or extra files in there? Sorry for such a long post
Edit: oh and I'm running zedomaxs v3 kernel and starburst rom if that helps. Thanks.
Sent from my SPH-D710 using XDA App

rsalinas1 said:
Hi I flashed this via CWM and it works looks and sounds great. However after the boot animation is done, my screen goes blank for about 10 seconds then finally is done booting. Is this normal? I had previously tried installing by using zedomaxs guide using root explorer where u just copy and paste into system/media directory. Maybe I have some wrong or extra files in there? Sorry for such a long post
Edit: oh and I'm running zedomaxs v3 kernel and starburst rom if that helps. Thanks.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Shouldn't make a difference. I recommend that you use CWM to wipe Dalvik and Cache then boot.

Boot Animation Troubleshooting
To report issues please provide as much information as possible so that someone can assist you. This would consist of:
ROM and Kernel you are using
Did you wipe dalvik and cache before booting?
The barometric pressure and the phase of the moon when you had a problem
Were you under the influence of any mind-altering substance?
Before you report a problem - please try these simple steps:
Wipe dalvik and cache in CWM
Reboot if you have a problem and verify it still exists
Most problems are resolved by the above. If not, then please post your issue.

Well..?? Followed the steps and have the sound but it's still the stock android boot animation. Running bubbys stock rooted kernel with CWM. And AEmods rom.
Samsung Galaxy S II

stangdriverdoug said:
Well..?? Followed the steps and have the sound but it's still the stock android boot animation. Running bubbys stock rooted kernel with CWM. And AEmods rom.
Samsung Galaxy S II
Click to expand...
Click to collapse
can you post the result of this command when your phone is connected (assuming you can do adb to it)
adb shell ls -l /system/media

OK I wiped dalvik and cache then rebooted, still no luck. Tried again and still no luck. After boot animation, phone seems as if it's off for about 10-15 seconds before completely booting up.
Sent from my SPH-D710

jerdog said:
can you post the result of this command when your phone is connected (assuming you can do adb to it)
adb shell ls -l /system/media
Click to expand...
Click to collapse
ok, I ran it but I am not sure how to copy and paste it to here.
Edit: Got it.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd c:\android\platform-tools
c:\Android\platform-tools>and devices
'and' is not recognized as an internal or external command,
operable program or batch file.
c:\Android\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
464119471A47A67E device
c:\Android\platform-tools>ls-i\system/media
The system cannot find the path specified.
c:\Android\platform-tools>adb devices
List of devices attached
464119471A47A67E device
c:\Android\platform-tools>ls -I/system/media
'ls' is not recognized as an internal or external command,
operable program or batch file.
c:\Android\platform-tools>ls -l /system/media
'ls' is not recognized as an internal or external command,
operable program or batch file.
c:\Android\platform-tools>adb shell ls -l /system/media
-rw-r--r-- 1 root root 21060 Aug 1 2008 Disconnected.qmg
drwxr-xr-x 6 root root 4096 Sep 27 07:52 audio
-rw-r--r-- 1 root root 21224 Aug 1 2008 battery_batteryerror.qm
g
-rw-r--r-- 1 root root 22216 Aug 1 2008 battery_charging_10.qmg
-rw-r--r-- 1 root root 19636 Aug 1 2008 battery_charging_100.qm
g
-rw-r--r-- 1 root root 22408 Aug 1 2008 battery_charging_15.qmg
-rw-r--r-- 1 root root 22540 Aug 1 2008 battery_charging_20.qmg
-rw-r--r-- 1 root root 22804 Aug 1 2008 battery_charging_25.qmg
-rw-r--r-- 1 root root 22724 Aug 1 2008 battery_charging_30.qmg
-rw-r--r-- 1 root root 22804 Aug 1 2008 battery_charging_35.qmg
-rw-r--r-- 1 root root 22880 Aug 1 2008 battery_charging_40.qmg
-rw-r--r-- 1 root root 23036 Aug 1 2008 battery_charging_45.qmg
-rw-r--r-- 1 root root 22144 Aug 1 2008 battery_charging_5.qmg
-rw-r--r-- 1 root root 22948 Aug 1 2008 battery_charging_50.qmg
-rw-r--r-- 1 root root 23020 Aug 1 2008 battery_charging_55.qmg
-rw-r--r-- 1 root root 23100 Aug 1 2008 battery_charging_60.qmg
-rw-r--r-- 1 root root 23264 Aug 1 2008 battery_charging_65.qmg
-rw-r--r-- 1 root root 23164 Aug 1 2008 battery_charging_70.qmg
-rw-r--r-- 1 root root 23236 Aug 1 2008 battery_charging_75.qmg
-rw-r--r-- 1 root root 23320 Aug 1 2008 battery_charging_80.qmg
-rw-r--r-- 1 root root 23292 Aug 1 2008 battery_charging_85.qmg
-rw-r--r-- 1 root root 23368 Aug 1 2008 battery_charging_90.qmg
-rw-r--r-- 1 root root 23452 Aug 1 2008 battery_charging_95.qmg
-rw-r--r-- 1 root root 20688 Aug 1 2008 battery_error.qmg
-rw-r--r-- 1 root root 1739057 Aug 1 2008 bootanimation.zip
-rw-r--r-- 1 root root 21676 Aug 1 2008 chargingwarning.qmg
drwxr-xr-x 3 root root 4096 Sep 27 07:52 video
c:\Android\platform-tools>

stangdriverdoug said:
ok, I ran it but I am not sure how to copy and paste it to here.
Edit: Got it.
Click to expand...
Click to collapse
I don't know what to tell you on that. Every test I ran showed this worked. I will keep doing some testing and see what others have to say.

AEmod rom stock kernel no workie, sound works though.

jerdog said:
I don't know what to tell you on that. Every test I ran showed this worked. I will keep doing some testing and see what others have to say.
Click to expand...
Click to collapse
Any idea on why it might not be working for me? Thanks
Sent from my SPH-D710

jerdog, how does one install this without CWM? Can I delete Samsung's files and throw your animation into the appropriate folder or are the other files in the .zip important?

Problem solved. I switched to Zedomax's kernel V4 and sound and animation work.

Deleted post.

Sound and Animation working for me with Zedo v3 installed over AEMod 3.2. I also got the black screen for 10 or 15 sec after the first boot. I used one of the other bios animations and they have the little android guy after the initial animation. Was this removed for some reason because it would be nice to have put back in for when the phone needs to boot for a longer period of time (like after cache wipe or rom change.) Thanks for the mod!

Download link not working or is it just me?

Not working for me either
Sent from my SPH-D710 using XDA App

[Q] will restore work?

SGN2 N7100
Stock firmware N7100DXDLK5
Guys,
Will restoring first full backup work to get back efs.
I was on N7100DXDMF2 when I made my first backup.
Eventually was advised by DR.Ketan to make a efs backup which I did but lost all saved files on pc.
However I had kept the full backup on my usb pendrive minus the efs backup.
After a long time on 4.1.2 I wanted to try out 4.4 kitkat at which time the imei/sn/service state and the mobile
network state were all intact.
Then tried out SupremeBean 4.3 and I think it was still okay since I had made some calls using said rom.
Then I opted to go back to 4.1.2 and all hell broke loose.
Lost mobile net.state/service state.Imei number 0049.....and the sn is different.
Do I need to flash back the original firmware i.e. N7100DXDMF2,Root,download a custom recovery like TWRP and use the old backup file.
Funny thing is, I could not find that firmware anywhere.And the stock recovery is being stubborn of not allowing other recovery to overwrite.
Maybe this has been answered a 100 times over but I think situations differ.Why, cos I still have a corrupted imei number and a serial number which is not far off from the original.
Any aid be much appreciated.

Sandro8771 said:
SGN2 N7100
Stock firmware N7100DXDLK5
Guys,
Will restoring first full backup work to get back efs.
I was on N7100DXDMF2 when I made my first backup.
Eventually was advised by DR.Ketan to make a efs backup which I did but lost all saved files on pc.
However I had kept the full backup on my usb pendrive minus the efs backup.
After a long time on 4.1.2 I wanted to try out 4.4 kitkat at which time the imei/sn/service state and the mobile
network state were all intact.
Then tried out SupremeBean 4.3 and I think it was still okay since I had made some calls using said rom.
Then I opted to go back to 4.1.2 and all hell broke loose.
Lost mobile net.state/service state.Imei number 0049.....and the sn is different.
Do I need to flash back the original firmware i.e. N7100DXDMF2,Root,download a custom recovery like TWRP and use the old backup file.
Funny thing is, I could not find that firmware anywhere.And the stock recovery is being stubborn of not allowing other recovery to overwrite.
Maybe this has been answered a 100 times over but I think situations differ.Why, cos I still have a corrupted imei number and a serial number which is not far off from the original.
Any aid be much appreciated.
Click to expand...
Click to collapse
N7100DXDLK5 - this have old modem and use old efs partition..latest kernel modified the efs partition
FLash MF2..it may help
N7100XXDMF2_N7100OLBDMD2_XME.zip

Managed to find the bloody efs backup in a private folder kept in external sdcard.
Thank God!!
The contents of this folder-MyEFS are as follows:
bluetooth folder - bt_addr 1 item 0kb
drm folder - play ready folder - 5 items
i) 0002.PRV 0 kb
ii) DXDeviceKey 0 kb
iii) DXSecureDB 7.1 kb
iv) DXSecureDB-secondary 8.3 kb
v) NVS 0.1 kb
factory app folder - 12 items
i) baro_delta 0 kb
ii) batt_cable_count 0 kb
iii) earjack_count 0 kb
iv) epen_count 0 kb
v) factorymode 0 kb
vi) fdata 0 kb
vii) hist_nv 0 kb
viii) hw_ver 0 kb
ix) keystr 0 kb
x) prepay 0 kb
xi) serial_no 0 kb
xii) test_nv 0.3 kb
imei folder - 1 item
i) mps_code.data 0 kb
wifi folder - 1 item (empty)
- 00000000.authtocont 0.1 kb
- efs.img - 20 mb
- gyro_cal_data 0 kb
- h2k.dat 1.1 kb
- nv_data.bin 2 mb
- nv_data.bin.md 5 0 kb
- nv.log 2.3 kb
- wv.keys 0.2 kb
- efs.tar 2 mb
With all this, minus the efs.tar used TWRP recovery via dr.ketan's v.2 aroma tool and still no change.
GT-N7100
Android version: 4.1.2
Baseband version: N7100 DXDLK5
Kernel version: 3.0.31 - 679347
se.infra @ SEP -87#1
SMP PREEMPT Thu Feb21
13:37:37 KST 2013
Build Number: JZ054K.N7100 XXDMF2
Sent from my GT-N7100 using xda premium

Sandro8771 said:
Managed to find the bloody efs backup in a private folder kept in external sdcard.
Thank God!!
The contents of this folder-MyEFS are as follows:
bluetooth folder - bt_addr 1 item 0kb
drm folder - play ready folder - 5 items
i) 0002.PRV 0 kb
ii) DXDeviceKey 0 kb
iii) DXSecureDB 7.1 kb
iv) DXSecureDB-secondary 8.3 kb
v) NVS 0.1 kb
factory app folder - 12 items
i) baro_delta 0 kb
ii) batt_cable_count 0 kb
iii) earjack_count 0 kb
iv) epen_count 0 kb
v) factorymode 0 kb
vi) fdata 0 kb
vii) hist_nv 0 kb
viii) hw_ver 0 kb
ix) keystr 0 kb
x) prepay 0 kb
xi) serial_no 0 kb
xii) test_nv 0.3 kb
imei folder - 1 item
i) mps_code.data 0 kb
wifi folder - 1 item (empty)
- 00000000.authtocont 0.1 kb
- efs.img - 20 mb
- gyro_cal_data 0 kb
- h2k.dat 1.1 kb
- nv_data.bin 2 mb
- nv_data.bin.md 5 0 kb
- nv.log 2.3 kb
- wv.keys 0.2 kb
- efs.tar 2 mb
With all this, minus the efs.tar used TWRP recovery via dr.ketan's v.2 aroma tool and still no change.
GT-N7100
Android version: 4.1.2
Baseband version: N7100 DXDLK5
Kernel version: 3.0.31 - 679347
se.infra @ SEP -87#1
SMP PREEMPT Thu Feb21
13:37:37 KST 2013
Build Number: JZ054K.N7100 XXDMF2
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
use MF2 modem

Used modem mf1 that worked.
Now at least ive got a phone that can make calls.
Imei is back to original service state shows in service.
Mobile network state remains as not connected but im able to dial out.
Odd.
And serial number is unchanged.Still showing wrong number.
You are from Malaysia.Which part.Im from Penang.Thank you again.
Ive added you as a friend.
Sent from my GT-N7100 using xda premium

you are wlcome mate. im from N.Sembilan.
some said ariza patch will help to recover the serial number..but im not recommed it.you can read quote below
Ariza patch does not fix IMEI issues. It fixes "00000" Serial number issues, which has similar symptoms. This patch does not work on EFS v2 ROMs. If you use it, you may irreparably break your phone.
Also it would seem, Phones that had this patch ON EFS v1 ROMS will break their IMEI if they upgrade to EFS v2 ROMS.
As yet, there is nothing proved to resolve this issue fully. Search the Ariza thread for posts by zuluman for potential fixes. This Page is hopefully the most useful or one of the patched modems posted
It would probably be best to get the serial number professionally restored either under warranty or by sla mobile repair shop. The Ariza patch was always only fixing something that should have been fixed under warranty anyway.... now we are seeing this issue - cut your losses
Click to expand...
Click to collapse
source

Good afternoon.
My mistake.The serial number had been correct even whilst corrupted. I missed out one alphabet when copying it down.lol.
That had me going around in circles for a couple of days.
So I guess the only problem to solve is that of the mobile network state being disconnected and also could you compare the list above with regards to the backup.
Does your backup have the same folders and values?
And when doing the restore do we put the whole bunch of stuffs or just the efs.img is sufficient.
Sent from my GT-N7100 using xda premium

good for you,now its not a problem anymore.
my backup only has efs.img, 20mb in size
i use this tool.
so i don't know about your backup..since there so many backup method out there.

Yes this is what I wanted to try now.
But then in the guide it says you need the
.bat file together with the efs.img
As you can see I do not have that .bat file of 1kb.
So how can I do it.
Sent from my GT-N7100 using xda premium

Sandro8771 said:
Yes this is what I wanted to try now.
But then in the guide it says you need the
.bat file together with the efs.img
As you can see I do not have that .bat file of 1kb.
So how can I do it.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
download this N7100_EFS_Backup_Restore_WIN.rar
---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------
you said in that thread you make efs backup with twrp..so better restore it with twrp mate

Galaxy Note 2 imei nbr don't tally
hi there,
i have been searching endlessly for a topic which is similar in region and model.
my name is lai. i have a samsung galaxy note 2 GT-N7100 stock standard running the following
Android - 4.1.2
Baseband - N7100DXDMF2
Kernel - 3.0.31-1071214
Build nbr - JZ054K.N7100XXDMF2
about 4 months back (Dec 2014/Jan 2015), my note2 suddenly could not make phone calls
stating "not registered on network", whereas wifi is working.
i've brought it to service centre and was told, main board faulty, antenna module faulty and so forth, which i suspected was BS
i recently notice that the imei number on screen is not the same as the imei number on the back of the phone
could someone help me rectify this matter.
thank you
Sandro8771 said:
Used modem mf1 that worked.
Now at least ive got a phone that can make calls.
Imei is back to original service state shows in service.
Mobile network state remains as not connected but im able to dial out.
Odd.
And serial number is unchanged.Still showing wrong number.
You are from Malaysia.Which part.Im from Penang.Thank you again.
Ive added you as a friend.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse

did you repair mainboard or got a new one?

Galaxy Note 2 imei nbr don't tally
No, never had any repairs done on the Note 2 since i first bought it in 2013.
yaro666 said:
did you repair mainboard or got a new one?
Click to expand...
Click to collapse

Galaxy Note 2 imei nbr don't tally
hi guys,
manage to rectify the problem as follows:
emei number in phone settings > about phone > status showed 004999/01/064000/0
emei number at the back of the phone shows 355696/05/540730/4
Android - 4.1.2
Baseband - N7100DXDMF2
Kernel - 3.0.31-1071214
Build nbr - JZ054K.N7100XXDMF2
Problem was phone unable to make calls out neither can it receive calls in (everytime a call is made a pop up message stating "not registered on network"), however, bluetooth and wifi are not affected.
SOLUTION
Download ODIN3 version 3.07
Download Stock ROM from SamMobile site (you need to register first, then choose your appropriate phone model and region)
Before flashing i did a factory reset via the Hard Reset (hold power, volume up and menu buttons together)
Flash Stock ROM onto your phone, follow the instructions from website
Everything went back to normal, emei number in settings tally with the emei number on the back of the phone. I am able to make and receive calls, wifi and bluetooth all working.
hope this helps, i am a noobie so i hope my explanation will help someone too.
cheers

laidsz67 said:
hi guys,
manage to rectify the problem as follows:
emei number in phone settings > about phone > status showed 004999/01/064000/0
emei number at the back of the phone shows 355696/05/540730/4
Android - 4.1.2
Baseband - N7100DXDMF2
Kernel - 3.0.31-1071214
Build nbr - JZ054K.N7100XXDMF2
Problem was phone unable to make calls out neither can it receive calls in (everytime a call is made a pop up message stating "not registered on network"), however, bluetooth and wifi are not affected.
SOLUTION
Download ODIN3 version 3.07
Download Stock ROM from SamMobile site (you need to register first, then choose your appropriate phone model and region)
Before flashing i did a factory reset via the Hard Reset (hold power, volume up and menu buttons together)
Flash Stock ROM onto your phone, follow the instructions from website
Everything went back to normal, emei number in settings tally with the emei number on the back of the phone. I am able to make and receive calls, wifi and bluetooth all working.
hope this helps, i am a noobie so i hope my explanation will help someone too.
cheers
Click to expand...
Click to collapse
another one...
Every single day someone has problem with IMEI and tried everything.
The solution in most cases is to flash stock rom with odin.

[Q] IMEI Repair Help!

I've researched this extensively and still not finding the solution I need. I recently flashed a ROM to my GNEX (unlocked from Google Play store). I'm not sure at what point it happened, but my /factory/ folder seems to have been emptied. So now I'm getting a generic IMEI that is blocked y my carrier T-Mobile. I'm getting absolutely no service.
Strangely I had no backup other than a backup of all my apps and data from Titanium backup, but I doubt there is anything useful in there. I have since reset my phone several times, removed the battery for 20 minutes, flashed the stock version of android that came with the phone...
my radio folder looks like this:
/data/radio/
nv_data.bin
nv_data.bin.md5
log folder
The log folder contains nv.log which contains the following:
Sat May 24 21:01:16 2014: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
Sat May 24 21:01:16 2014: MD5 is turned on.
Sat May 24 21:01:16 2014: /data/radio/nv_data.bin does not exist.
Sat May 24 21:01:17 2014: default NV restored.
Sat May 24 21:20:43 2014: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
Sat May 24 21:20:43 2014: MD5 is turned on.
Sat May 24 21:25:23 2014: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
Sat May 24 21:25:23 2014: MD5 is turned on.
Sat May 24 21:31:56 2014: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
Sat May 24 21:31:56 2014: MD5 is turned on.
Sat May 24 21:33:07 2014: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
Sat May 24 21:33:07 2014: MD5 is turned on.
Sun May 25 00:51:15 2014: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
Sun May 25 00:51:15 2014: MD5 is turned on.
my /factory/ folder was empty, but I copied the two files from my radio folder in the factory folder to see if that would help. I think that changed the messages in the log file but did not fix the problem. I know I need to repair my IMEI, but I'm not sure how. I would GREATLY appreciate any help. Thanks!

[Q] Is My AFTV Bricked??? Reward

Hi, I came home today and my AFTV is stuck on the white & yellow AFTV logo (Ctrl+i+Prt Screen just send me back to CWM). I haven’t done anything to it recently. I am wondering how to fix it. I have CWM-based Recovery v6.0.5.1.4a on it and tried to reinstall the last ROM I installed, and it did install but still will not boot. Should I run that or the restore from backup option in CWM? I never made an official back up to my knowledge it’s “1970-01-01.00.40.56/”. I just don’t know what I should do bc the boot kernal is obviously corrupted. Should I “image restore” in CWM or is there a 3rd option? I'm hoping there is still a chance to recover the boot image since I can still access CWM and can use a usb hub to upload zip files (no ADB connect). I have SPMC with bootloader running, and am debating reinstalling that zip file, but I do not think it will work. I think what caused my issue was setting my Android Screen Saver to Shutdown instead of sleep, since it happened the next morning. I tried looking on this forum for clues but the only guy to have a similar issue said it fixed itself, which does me no good.
I am offering a $11.11 reward (Paypal donation) to anyone who can guide me in fixing this.

Kul-Aid23 said:
Hi, I came home today and my AFTV is stuck on the white & yellow AFTV logo (Ctrl+i+Prt Screen just send me back to CWM). I haven’t done anything to it recently. I am wondering how to fix it. I have CWM-based Recovery v6.0.5.1.4a on it and tried to reinstall the last ROM I installed, and it did install but still will not boot. Should I run that or the restore from backup option in CWM? I never made an official back up to my knowledge it’s “1970-01-01.00.40.56/”. I just don’t know what I should do bc the boot kernal is obviously corrupted. Should I “image restore” in CWM or is there a 3rd option? I'm hoping there is still a chance to recover the boot image since I can still access CWM and can use a usb hub to upload zip files (no ADB connect). I have SPMC with bootloader running, and am debating reinstalling that zip file, but I do not think it will work. I think what caused my issue was setting my Android Screen Saver to Shutdown instead of sleep, since it happened the next morning. I tried looking on this forum for clues but the only guy to have a similar issue said it fixed itself, which does me no good.
I am offering a $11.11 reward (Paypal donation) to anyone who can guide me in fixing this.
Click to expand...
Click to collapse
http://androidflagship.com/3217-fix-damaged-bricked-android-device
Maybe read through the link above.
I'm not an Android expert. Aftv was my first experience then I bought a phone and then rooted kfhd. But I have heard you should wipe dalvik cache and heard it's essential to even factory reset in recovery before flashing a new Rom. That is NOT stressed in any of the aftv guides I read and it may not be necessary but if for no other reason than to learn I'd like to know why???
But like I said. I'm the equivalent of a kindergartner when it comes to android so ask questions before you try anything. I don't want to cause more issues for you.

Kul-Aid23 said:
Hi, I came home today and my AFTV is stuck on the white & yellow AFTV logo (Ctrl+i+Prt Screen just send me back to CWM). I haven’t done anything to it recently. I am wondering how to fix it. I have CWM-based Recovery v6.0.5.1.4a on it and tried to reinstall the last ROM I installed, and it did install but still will not boot. Should I run that or the restore from backup option in CWM? I never made an official back up to my knowledge it’s “1970-01-01.00.40.56/”. I just don’t know what I should do bc the boot kernal is obviously corrupted. Should I “image restore” in CWM or is there a 3rd option? I'm hoping there is still a chance to recover the boot image since I can still access CWM and can use a usb hub to upload zip files (no ADB connect). I have SPMC with bootloader running, and am debating reinstalling that zip file, but I do not think it will work. I think what caused my issue was setting my Android Screen Saver to Shutdown instead of sleep, since it happened the next morning. I tried looking on this forum for clues but the only guy to have a similar issue said it fixed itself, which does me no good.
I am offering a $11.11 reward (Paypal donation) to anyone who can guide me in fixing this.
Click to expand...
Click to collapse
Start Recovery CMM and select the rom.zip in Sdcard/0. that should bring you back with the boot menu thus saving your root, but you will have to setup everything again. remember disable updates using /su disable commands. i wouldn't mind helping you if you live closeby to Los Angeles.

navigates said:
Start Recovery CMM and select the rom.zip in Sdcard/0. that should bring you back with the boot menu thus saving your root, but you will have to setup everything again. remember disable updates using /su disable commands. i wouldn't mind helping you if you live closeby to Los Angeles.
Click to expand...
Click to collapse
Hey, I appreciate the input but I have already tried that, I mentioned it in my original post. I am not sure exactly as to what happened. It says it installed but same ****. I am assuming my AFTV updated to the new firmware, even though I thought I had updates blocked on my device. I also had the 3 urls blocked via my router. The only thing I can think of is my Asus router limits the characters so it's blocking amzdigitaldownloads.edgesuite.ne instead of .net. Or if it uses a different URL for Canada bc I use a DNS service on my router so I can watch local and playoff hockey games through NHL GCL. I also changed my screen saver in SPMC (which is what my AFTV boots to) to android power off instead of sleep a day before this happened. I was curious about maybe clearing the cache then trying to reinstall the rom again or try a different Rom file. Or maybe even hard mod if it would fix it. I'm in StL btw, Thank You though.

Kul-Aid23 said:
Hey, I appreciate the input but I have already tried that, I mentioned it in my original post. I am not sure exactly as to what happened. It says it installed but same ****. I am assuming my AFTV updated to the new firmware, even though I thought I had updates blocked on my device. I also had the 3 urls blocked via my router. The only thing I can think of is my Asus router limits the characters so it's blocking amzdigitaldownloads.edgesuite.ne instead of .net. Or if it uses a different URL for Canada bc I use a DNS service on my router so I can watch local and playoff hockey games through NHL GCL. I also changed my screen saver in SPMC (which is what my AFTV boots to) to android power off instead of sleep a day before this happened. I was curious about maybe clearing the cache then trying to reinstall the rom again or try a different Rom file. Or maybe even hard mod if it would fix it. I'm in StL btw, Thank You though.
Click to expand...
Click to collapse
I cant block a domain name on my router either. I need to ping the domain name--that yields an IP address then I copy that into the appropriate box to block internet access.
But, if you're blocked on the box itself, I really don't think you got an update, ESPECIALLY if you have custom recovery. It will attempt to install it but it will fail and the box will boot itself to recovery. It happened to me before when I forgot to pm disable after wiping data. I think there's a slim chance of an update sneaking through but I doubt they found a way. Otherwise a lot more people would be reporting your issue right now.
BTW--our problems aren't really similar. I'm not bricked. I've got something going on that I narrowed down to my usb port. I thought it was a corrupted usb drive but every drive I plug in, unmounted, causes the box to boot into a snow/static screen then hang on amazon. Unplug it and it boots fine. Still working on a solution. Good luck!

You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
cd /data/app
ls -lt
Click to expand...
Click to collapse
Find the last apps you installed
And to uninstall them
rm com.apps.name.apkfilename
Click to expand...
Click to collapse

smartymcfly said:
You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
Find the last apps you installed
And to uninstall them
Click to expand...
Click to collapse
Oh snap, this may work. I didn't realize I could ADB into it still ( posted this on reddit and someone said I could too), I've tried before but was over wifi, so I will have to give this a shot. By any chance would you know of an article that has this info in a little bit more detail?

Our issues do seem somewhat similar. You altered the normal sleep options which thinking about it now...that's one of the functions in elmerohueso launcher. As long as I don't leave a flash drive plugged in everything works normally Except Display/Screensaver on home screen. But I've used that repo before and that specific option. It never highjacked the fire display options (could always access and change them) so I don't see how deleting anything in the repo would effect that? My instinct is telling me to reinstall xposed and it might correct itself. My anxiety is yelling I'm gonna end up not being able to boot it up normally if I try. Sorry don't mean to intrude but can you confirm you had xposed installed when this happened?

I had xposed, towel root, super SU, and all the other good stuff installed. I also had used the power off option before too. I'm just going to install kodi 14.1 with the boot loader and hope it overwrites whatever happened after I get home from work. The thing has been running great since mid-December and I hadn't really changed anything at all, except for that power option.

smartymcfly said:
You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
Find the last apps you installed
And to uninstall them
Click to expand...
Click to collapse
Can you be more clear or link to something that explains this better, I've tried what you are saying but I am messing something up. Can you be less vague?

Kul-Aid23 said:
Can you be more clear or link to something that explains this better, I've tried what you are saying but I am messing something up. Can you be less vague?
Click to expand...
Click to collapse
If you need it.
connectify
Run an Ethernet cable to your firetv. Then you will have adb while in recovery if needed. You will need to go into connectify or your router....never mind cwm shows the IP right on the screen.
So after you get your firetv connected via Ethernet cable then you will be able to connect.
http://www.reddit.com/r/fireTV/comments/2ux6vx/i_bricked_and_unbricked_my_firetv_using_an/
You can block the domains by blacklisting it in adaway
---------- Post added at 05:21 PM ---------- Previous post was at 05:13 PM ----------
What do you mean spmc running? That is just a version of gotham/kodi right? Do mean the prerooted ROM by rbox? I would flash the latest version of that.
You might need to go back to aftvnews.com to download and older version of the ROM and then follow the steps on there from the part where CWM recovery is installed. Did you install the boot menu that allows you to choose what you want to boot? If not you should probably also do that.

smartymcfly said:
You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
Find the last apps you installed
And to uninstall them
Click to expand...
Click to collapse
This is what I got:
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb conn
ect 192.168.1.219
already connected to 192.168.1.219:5555
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shel
l
error: protocol fault (no status)
error: protocol fault (no status)
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb conn
ect 192.168.1.219
connected to 192.168.1.219:5555
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shel
l
~ # cd /data/app
cd /data/app
/data/app # ls -lt
ls -lt
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rw-r--r-- 1 system system 10609976 Feb 2 2015 com.splashtop.m360.amz-
1.apk
-rw-r--r-- 1 system system 6691947 Jan 30 2015 net.gtvbox.videoplayer-
1.apk
-rw-r--r-- 1 system system 6793950 Jan 25 2015 com.nuclearheart.robree
dflippinawesome-2.apk
-rw-r--r-- 1 system system 26916397 Jan 16 2015 com.msherwin.traversal-
1.apk
-rw-r--r-- 1 system system 849239 Jan 16 2015 com.koushikdutta.cast.r
eceiver-1.apk
-rw-r--r-- 1 system system 15314637 Jan 10 2015 com.entwicklerx.perrypi
gjumptv-1.apk
-rw-r--r-- 1 system system 16953271 Jan 10 2015 air.com.tangerinepop.ru
nic-1.apk
-rw-r--r-- 1 system system 169316954 Jan 5 2015 com.frogmind.badland-1.
apk
-rw-r--r-- 1 system system 132039052 Jan 5 2015 com.jackboxgames.ydkjpa
rty-1.apk
-rw-r--r-- 1 system system 37907298 Jan 5 2015 com.concretesoftware.pb
achallenge_amazonfree-1.apk
-rw-r--r-- 1 system system 13859655 Jan 5 2015 com.amazon.weather.tv-1
.apk
-rw-r--r-- 1 system system 7165418 Dec 30 2014 com.pbs.video-2.apk
-rw-r--r-- 1 system system 49309428 Dec 27 2014 com.sega.sonic2-1.apk
-rw-r--r-- 1 system system 50121408 Dec 27 2014 com.halfbrick.ageofzomb
ies-1.apk
-rw-r--r-- 1 system system 33200359 Dec 27 2014 com.fallentreegames.ama
zon.quellreflect-1.apk
-rw-r--r-- 1 system system 76108096 Dec 25 2014 com.digitalx.chichiledf
ish-2.apk
-rw-r--r-- 1 system system 29096021 Dec 15 2014 com.hg.farminvasionc-1.
apk
-rw-r--r-- 1 system system 57260455 Dec 15 2014 com.hg.frozenfront-1.ap
k
-rw-r--r-- 1 system system 46766549 Dec 15 2014 com.hg.ninjaherocats-1.
apk
-rw-r--r-- 1 system system 25019798 Dec 15 2014 com.hg.savethepuppiesc-
1.apk
-rw-r--r-- 1 system system 31679186 Dec 15 2014 com.hg.aotlpremium-1.ap
k
-rw-r--r-- 1 system system 22356882 Dec 14 2014 com.nhl.gc1112.free-1.a
pk
-rw-r--r-- 1 system system 27404 Dec 10 2014 rbox.xposed.firetvmods-
1.apk
-rw-r--r-- 1 system system 4595035 Dec 7 2014 com.estrongs.android.po
p-1.apk
-rw-r--r-- 1 system system 595059 Dec 7 2014 com.adrise.profilms-1.a
pk
-rw-r--r-- 1 system system 2758702 Dec 7 2014 com.kebab.Llama-1.apk
-rw-r--r-- 1 system system 32168267 Dec 7 2014 com.android.chrome-1.ap
k
-rw-r--r-- 1 system system 728857 Dec 7 2014 de.robv.android.xposed.
installer-1.apk
-rw-r--r-- 1 system system 8042116 Dec 6 2014 com.netflix.ninja-1.apk
-rw-r--r-- 1 system system 2577850 Dec 5 2014 stericson.busybox-1.apk
-rw-r--r-- 1 system system 113099 Dec 5 2014 com.geohot.towelroot-1.
apk
/data/app # rm com.splashtop.m360.amz-1.apk

That splashtop is not something that would have caused a problem.
Did you flash the ROM but you didn't wipe the data beforehand. Also did you clear the cache & dalvik cache before flashing?
amazon doesn't ship the firetv with splash top or the other apps you installed.
http://www.aftvnews.com/start/
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
You will have to start over because when you wipe system/data/cache/dalvik it will uninstall root unless you flash a prerooted version.
I do not believe you had the latest ROM because you said you used Ctrl print I to get to cwm but now on the latest bootloader it gives you the option to boot into recovery.
What was the last version of the ROM that you installed?
---------- Post added at 05:46 PM ---------- Previous post was at 05:35 PM ----------
This is required to install the latest prerooted rom
http://www.aftvnews.com/how-to-install-a-kernel-boot-menu-on-the-amazon-fire-tv/

smartymcfly said:
That splashtop is not something that would have caused a problem.
Did you flash the ROM but you didn't wipe the data beforehand. Also did you clear the cache & dalvik cache before flashing?
amazon doesn't ship the firetv with splash top or the other apps you installed.
http://www.aftvnews.com/start/
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
You will have to start over because when you wipe system/data/cache/dalvik it will uninstall root unless you flash a prerooted version.
I do not believe you had the latest ROM because you said you used Ctrl print I to get to cwm but now on the latest bootloader it gives you the option to boot into recovery.
What was the last version of the ROM that you installed?
---------- Post added at 05:46 PM ---------- Previous post was at 05:35 PM ----------
This is required to install the latest prerooted rom
http://www.aftvnews.com/how-to-install-a-kernel-boot-menu-on-the-amazon-fire-tv/
Click to expand...
Click to collapse
I had "51.1.4.1_514013920 fixed" rom when this happened. I have not cleared anything, should I? Also my AFTV is acting really weird, when I run adb shell it tells me I dont have SU, and when it connect to the utility, it says I have amazon updates turn on (though I am also in CWM so maybe thats default, idk). Also, I tried doing that crtl+i+prnt scrn again and nothing happens. I think I was mistaken on that bc it does not work. I probably just press ctrl+atl+delete and it just rebooted to the boot menu. My friend is bringing over his AFTV and I'm just going to make a back up and load it on mine, basically try to clone it. If that doesn't work I'm just taking a hammer to it and buying one of these next month:
http://www.cnet.com/products/intel-compute-stick/
I'm not a patient man, hence the reward.

Kul-Aid23 said:
I had "51.1.4.1_514013920 fixed" rom when this happened. I have not cleared anything, should I? Also my AFTV is acting really weird, when I run adb shell it tells me I dont have SU, and when it connect to the utility, it says I have amazon updates turn on (though I am also in CWM so maybe thats default, idk). Also, I tried doing that crtl+i+prnt scrn again and nothing happens. I think I was mistaken on that bc it does not work. I probably just press ctrl+atl+delete and it just rebooted to the boot menu. My friend is bringing over his AFTV and I'm just going to make a back up and load it on mine, basically try to clone it. If that doesn't work I'm just taking a hammer to it and buying one of these next month:
http://www.cnet.com/products/intel-compute-stick/
I'm not a patient man, hence the reward.
Click to expand...
Click to collapse
You already have su when in recovery, or else you need to mount system in cwm.
Well you have access to cwm so should not be bricked right?
You can wipe system/data/cache/dalvik and then flash it otherwise whatever is causing the problem will still be there. Make sure to have the supersuv1.94.zip so you have root when you boot.
Not sure it would be a good idea to try flashing a copy of your friends backup before you try to wipe and flash. You will keep the contents of sdcard, just everything else will be wiped.

STOP all the nonsense you were told to do. Download this and put it on a usb stick. Boot into recovery and wipe cache and dalvik cache. Then VERY CAREFULLY wipe system. DO NOT REBOOT!!!! Flash the prerooted rom I just told you to download. When its done reboot and you will be on 51.1.4.0_514006420+updated. You can STOP NOW with a working FireTV. Or you can proceed to make sure you have most recent recovery, bootloader unlocked, and the the most recent 51.1.4.1_514013920+fixed rom. Make sure you follow the guides carefully.

Kul-Aid23 said:
I had "51.1.4.1_514013920 fixed" rom when this happened. I have not cleared anything, should I? Also my AFTV is acting really weird, when I run adb shell it tells me I dont have SU, and when it connect to the utility, it says I have amazon updates turn on (though I am also in CWM so maybe thats default, idk). Also, I tried doing that crtl+i+prnt scrn again and nothing happens. I think I was mistaken on that bc it does not work. I probably just press ctrl+atl+delete and it just rebooted to the boot menu. My friend is bringing over his AFTV and I'm just going to make a back up and load it on mine, basically try to clone it. If that doesn't work I'm just taking a hammer to it and buying one of these next month:
http://www.cnet.com/products/intel-compute-stick/
I'm not a patient man, hence the reward.
Click to expand...
Click to collapse
So I just cloned my buddies AFTV by making a recovery file and saving it to a usb. I found an article on here talking about cloning. It worked out real well. Everything was still saved with even the same SPMC settings, just changed my IP address and amazon account. Idk why it messed up because the power off option is still there and it works fine. It worked real well.

Question Aquire FFS dump

I am going to buy another phone due to this being a temporary test phone. This is not BOOTLOADER unlocked and straight talk locked. I want to recover a full file system dump or even a full chip dump of this phone unencrypted. Is there any one click root that's safe so I can get a full filesystem dump? A CVE? Forensic tools? Do I need to go to my local police department to get it?

Phone: moto e 2020
Locked by Straight Talk by TracFone
Build Number: QPGS30.82-141-1
Kernel Version: 4.9.206-perf
#1 Thu Dec 2 08:05:31 CST 2020
Baseband: M632_19.00.03.50.04R GINNA_GWLC_CUST
Patch Level: December 1, 2021
OS: Android Queen Cake
Version: 10
Bootloader locke
Encrypted data
I specifically want NO FACTORY RESE
Any exploit to read data from /data would work, even with a PC. I have a PC but the hard drive is slow as fk.