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
Related
Model number: GM_DSTL1
Firmware version: 1.5
Baseband version: 20/05/09,st32,x2a.m1
Kernel version: 2.6.28-svn1368
Build number: CUPCAKE.eng.long.20090720.210535.r1368
Trying to figure out how this could be rooted because I can't seem to use traditional methods like downgrading and 1-click rooting.
If I understand correctly this is possible for me due to CVE-2009-2692
In an effort to try and cover my butt I have backed up all that "adb shell" permission would let me.
Zinx's "Recovery partition flasher for Android" has not been helpful.
Getting my device to use FastBoot seems to be my first step.
Constructive comments?
still no luck
Ruled out the telnetd hack, bummer:
I run telnetd in terminal and it gives me no errors but a port scan doesn't return anything besides port 110(pop3), 25(smtp), and 21(ftp) - none of which have proved useful thus far. Must have been patched with cupcake... or something I'm missing.
Also ran cat /proc/cpuinfo for fun
--------------------------------
Processor : XScale-V3 based processor rev 2 (v5l)
BogoMIPS : 103.58
Features : swp half thumb fastmult edsp iwmmxt
CPU implementer : 0x69
CPU architecture: 5TE
CPU variant : 0x0
CPU part : 0x689
CPU revision : 2
Hardware : yuhua X2_V4 on Marvell (Littleton)
Revision : 0004
Serial : 0000000000000000
-----------------------------------------------------
103.58 is weak sauce... but apparently that is the minimum for the Marvell PXA310 RISC Microprocessor
I wonder if anyone else on this board is bumpin the DSTL1? I may be the lone fish out here
Following this guide to get Fastboot aka Engineering Bootloader
I skipped flashing the radio because I figured it had to do with the OTA stuff which doesn't affect my model...
So I downloaded spl-signed.zip and renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL.
update.log from failed update
Starting recovery on Thu Oct 8 01:22:51 2009
framebuffer: fd 4 (240 x 400)
I:text_cols 24 text_rows 22
E:Can't open /cache/recovery/command
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.long.20090710.190105.r1322
ro.build.version.incremental=eng.long.20090710.190105.r1322
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Fri Jul 10 19:15:42 CST 2009
ro.build.date.utc=1247224542
ro.build.type=user
ro.build.user=long
ro.build.host=long-desktop
ro.build.tags=ota-rel-keys,test-keys
ro.product.model=GM_DSTL1
ro.product.brand=generic
ro.product.name=gm_x2
ro.product.device=x2
ro.product.board=x2a_v4
ro.product.manufacturer=yh
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=
ro.build.product=x2
ro.build.description=gm_x2-user 1.5 CUPCAKE eng.long.20090710.190105.r1322 ota-rel-keys,test-keys
rild.libpath=/system/lib/libyh-ril.so
rild.libargs=-d /dev/ttyp1
persist.gsm.dual.mode.phone=1
persist.gsm.sim.active.phone=GSM1
sms.supports.national.lang=1
wifi.interface=eth0
ro.config.sm_notification_snd=notf_gm_02.ogg
ro.config.sm_notification_snd_2=notf_gm_02.ogg
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.ringtone=GM_01.ogg
ro.config.ringtone_2=GM_01.ogg
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=yuhua
ro.revision=4
init.svc.recovery=running
init.svc.adbd=running
init.svc.yuhua-board-init=stopped
ro.kernel.android.qemud=0
ro.radio.use-ppp=no
ro.com.google.locationfeatures=1
RecVer:Fri Jul 10 19:15:42 CST 2009
Recovery tools:
HOME: Sd-card update
CALL: Board test
BACK: Factory reset
POWER: Reboot system
I:Key 102 pressed, alt 0
Search /sdcard/update/*
I:Find file . in /sdcard/update/
I:Find file .. in /sdcard/update/
I:Find file update.log in /sdcard/update/
I:Find file update.zip in /sdcard/update/
Find update.zip, Home to update
I:Update package /sdcard/update/update.zip
Installing /sdcard/update/update.zip
Installation failed.
Another Fastboot attempt
http://android-dls.com/wiki/index.php?title=Engineering_Bootloader
Downloaded update.xxx, renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL... again.
From the log files it seems this stock recovery system SUCKS...
Another FAIL
Revisiting http://forum.xda-developers.com/showthread.php?t=532719 from my earlier post (#3). Tried to do the Radio Update... Downloaded ota-radio-2_22_19_26I.zip and renamed it to update.zip... yada yada yada, you know the rest.
Visit "http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support", and you can find how the update system work(it is not a G1). Also take some time to see the install package and hack it.
1. Unzip the package.
unzip Android_20090826_r1502.zip
2. Copy some missed property app(http://www.sendspace.com/file/dii80c get from adp1.5) to /system/app/ after diff it with the ADP image.
3. zip the new package.
zip Android_20090826_r1502_hack.zip -ry system boot.img
4. update package and wait it bootup.
Very cool!
@wineleven
THANKS!
That was very cool! Finally some progress
So I was not too off from that path, I had already downloaded the update from General Mobile and had been inspecting the zip file they were trying to shove in my face as a quick fix to their buggy ROM. I was asking the support some very hard questions, which is probably why it has taken them more than their 48 hours to reply to me. (its been 5 days now)
General Mobile's update is Android_20090826_r1502.zip
containing the following particularly interesting (to me) files:
/system/build.prop
/system/system-update-post-script
/boot.img
/update-validate-script
Attempt 1
Here I tried to zip up their unmodified package with the suggested -ry arguments and hope that stock recovery takes it and runs with it.
FAIL
I reviewed wineleven's suggestions noticed he omitted the file update-validate-script
This was probably my problem
Attempt 2
Here I omitted update-validate-script
SUCCESS!
Attempt 3
Spirits high I go for the gusto:
I downloaded superuser.zip from this forum and embedded it in the location /system/app
Flash SUCCESS, functionality FAIL
I got too excited and put Superuser.apk and su both in the same directory... silly mistake
Attempt 4
This time I put Superuser.apk in /system/app and su in /system/bin
Flash SUCCESS, functionality FAIL
running su in terminal gave me "permission denied" with the following carriage return:
here1here2here3here4$
obviously I'm missing something here... but have made progress and feel more confident about this.
More attempts to come. Suggestions and advice is welcome!
Question to those knowledgeable
Why are certain files in the /system/bin included as "links" and not actual files? save space in zip?
Can boot.img be modified? Replaced with a better (more useful) one?
Any ideas on obtaining root?
Root idea and shortcommings
After reviewing http://android-dls.com/wiki/index.php?title=Magic_Root_Access
I may have bin (lol) too hasty with slapping su in /system/bin
But logic tells me it shouldn't matter... bin or xbin
And I feel like permissions are my real issue because my current su (residing in /system/bin)
command
ls -l /system/bin/su
returns
-rwxr-xr-x root shell 34612 2008-08-01 08:00 su
command
chmod 6755 /system/bin/su
returns
Unable to chmod su: Read-only file system
^--- in hindsight I see that as a DUH, because I can't remount the /system partition as read/write
More questions
I have always understood chmod to use three digits, why are there four digits now?
Also, what is 's' in terms of permission... is that to see? like hidden files?
Main task accomplished!
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip - NEW BUILD HERE
MD5: F1DE9A270CDDF01ADEE708B6660B7AFA
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
@wineleven THANK YOU for the nudge in the right direction!
Thank you:
Google for the open source Android OS - without the free SDK wouldn't have been possible for me
General Mobile for the nifty device
Remote Exploit for BackTrack3/4 - I did most of my work on this Live CD distro
XDA-Developers Forum for info and resources: superuser files and Cyanogen's ROM for info
congratulation to you.
Some notice:
As this devices is deeply modified based on Android open source and hardware different to G1. So you can not rebuild any system framework APK from open source unless you can get the DSTL1 source code. As i now, one thing we can do is to add some external APK file (API compatible to device, now SDK 1.5) to system. Like the Superuser.apk you do.
crzyruski said:
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip
MD5: C3C13F6DC75BF6F86E5C9E41D7FB4C59
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
Click to expand...
Click to collapse
Hi crzyruski
I'm a new android and DSTL1 user and this information is cool
it's easy to do for a newbie as I?
What do you mean easy? What would you like to do?
I took General Mobile's only update: http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support and gave it ROOT. If this is all you want to do, I have compiled the package already for you in my post above. If you want to do it manually then read the whole thread to see how I did it.
If you want to use my compiled package, it is easy.
Then again, I don't know if anyone else has tried it. It worked for me.
You are only the second individual to inquire about it, I am not sure if the other fellow had any luck - he hasn't replied to me.
Hope this helps.
Keep in touch!
I only have 3 days with Android, but I think that I want to get root access. The only thing I have to do is a second "update" with your package, isn't it?
I'm going to look for a backup system program first...
Can I have problems to update from General Mobile support web in a future? (i.e Android 2.0)
It does not need to be second. That is your choice. You can use it in any order. This is not a patch so order is no relevant.
My package is basically the original General Mobile update + 2 files.
These two files are su and Superuser.apk - nothing special (except that you will obtain root access on demand)
I currently only utilize root access to run Advanced Task Manager.
And in the future I want to overclock because I feel the DSTL1 is greatly underclocked though it should max out at ~600Mhz.
Good luck with a backup program as I have not found any free versions and NAndroid is ideal but not not yet possible as you have to flash the SPL and I am not aware how to do this for DSTL1 though I am sure it is possible.
Please let me know what you end up using to backup, if you do.
I would like to note that I am not all knowing and if something goes wrong I am sorry, but can't take responsibility.
There is no reason you should not be able to update from my package to another like: original 1.5 or new 1.6 or future 2.0 (whenever it comes out).
Hopefully when those come out I will be able to modify them similarly and make them available.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
crzyruski said:
Please let me know what you end up using to backup, if you do.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
Click to expand...
Click to collapse
I'm going to try with My Backup Pro
And about 2.0 this all I know...
http://www.boygeniusreport.com/2009/10/16/android-2-0-screenshot-walkthrough/
Good luck to you.
I think I may begin working on some more DSTL1 hacks.
Please keep me updated with your progress
I only have to do ALL this process with your zip, isn't it?
How to Install the Product Update:
Create a folder at the top-level of your memory card called 'update' , and copy file '*.zip' into your phone's memory card.
Make sure your phone is off, and press the Home key together with the Power & End key to enter the recovery mode, do the operations following the UI indication:
1- Press the Home key to search the zip file from your memory card, and press the Home key again to update the software.
2- Press the Call key to do board test.
3- Press the Back key to restore the factory settings.
4- Press the Power & End key to reboot your phone after update finishes.
Click to expand...
Click to collapse
Looks correct to me. Tell me how it works out.
crzyruski said:
Looks correct to me. Tell me how it works out.
Click to expand...
Click to collapse
I've done it! and all seems to be ok...
Thank you crzyruski.
I'll be waitng for your future DSTL1 hacks.
Can someone with root and is familiar with adb please pull and post the file below:
http://forum.xda-developers.com/showpost.php?p=28883421&postcount=25
Thanks!
errors out for me, no such file.
Mines called 1970 emmcbl0p2. Sprint variant.
Dual Booting Project
Android OS - Ubuntu Phone OS
As the title says, I think we can make posible dual booting Android and Ubuntu.
1st post Experimental Methods, Useful Infromation and Help Needed
2nd post News
3rd post How to install Ubuntu Phone OS
Experimental Methods
1-. This method was originally posted by beidl
The method that beidl suggested us is to make this steps:
"Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff"
"Flash CM back to the device"
"Copy specific files back to /system"
"By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up."
NOTE: Nobody try it, be the first!
*Using these methods you could brick your GNex, the poster of each method and me aren't responsible of any damage on your GNex!*
Useful Information
Here is partition table:
ytwytw said:
[...]
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
[...]
Click to expand...
Click to collapse
&
lrwxrwxrwx root root 2012-07-01 01:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-01 01:03 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-07-01 01:03 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-01 01:03 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-01 01:03 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-07-01 01:03 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-01 01:03 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-01 01:03 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-01 01:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-07-01 01:03 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-01 01:03 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-01 01:03 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-07-01 01:03 xloader -> /dev/block/mmcblk0p1
Click to expand...
Click to collapse
Info about GRUB on ARM v7
Help Needed
I think we can modify partition table making more partitions and modifiying Ubuntu Phone OS kernel to boot in asigned partitions but I need help:
How much partition we have to add? (System, data..)
I think we have to edit bootloader + kernel, How to do it?
It will be posible?
I don't know a lot about partition tables and editing bootloader & kernel but, I think I will be able to help.
PD: If moderator or developers in this section think that it will be better to post this thread in general or in development, don't worry moving it.
News
News
22/02/2013:Thanks to beidl, I think we have the posibility to boot CM 10.1 and Ubuntu Phone OS. Take a look at the 10th post:
beidl said:
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
Click to expand...
Click to collapse
23/02/2013: I'm working on a modified version, now fisrtly I will delet all videos & images that came as a sample. EDIT: I have edited it, to download it, go to the 3rd post!
Files & How to install Ubuntu Phone OS
How to install Ubuntu Phone OS
NOTE: This files doesn't include the option to make a dual boot yet
-I'm not responable of any damage could have your GNex after flashing Ubuntu Phone OS this way-
Steps:
Download files quantal-preinstalled-armel+maguro.zip (4,6 MB) and quantal-preinstalled-phablet-armhf.zip (481 MB), and copy them to your GNex.
NOTE: You can use a modified file without all sample photos, videos and messages modified by me. Donwload it here: edited-quantal-preinstalled-phablet-armhf-v1.zip
Make a Nandroid Backup (to be able to restore Android later)
Make a Factory Reset
Flash them in CWM or TWRP (1-.quantal-preinstalled-armel+maguro.zip and 2-.quantal-preinstalled-phablet-armhf.zip)
Reboot (In a few seconds Ubuntu will boot up)
If you want to restore Android, make a backup of Ubuntu first if you want to install Ubuntu again
*This guide was originally posted by eng.stk*
NOTE: Second file (quantal-preinstalled-phablet-armhf.zip) will take few minutes to flash so don't panic and relax until it's flashed but, if you use the file that it has been modified by me, it will be faster. This method doesn't wipe your internal storage (/sdcard)
This way you could have both system only restoring backups of both OS. It's a good to have both system while dual boot it's being developed.
Don't you need like a bootloader to dual-boot?
jimmyco2008 said:
Don't you need like a bootloader to dual-boot?
Click to expand...
Click to collapse
Read the op again. *i think we need to edit the bootloader.
Sent from my Galaxy Nexus using Tapatalk 2
jimmyco2008 said:
Don't you need like a bootloader to dual-boot?
Click to expand...
Click to collapse
Yes, I need help to edit GNexs' bootloader to be able to boot both OS
Regards,
Urko
Enviado desde mi Galaxy Nexus usando Tapatalk 2
It's a very bad idea to screw around with the bootloader and partition table.
kexec would be the way to go, but it requires kernel patches for both the Android ROM and the Ubuntu ROM.
Also, since Ubuntu Touch is just chrooted inside CM, I guess it would be possible to make some CM specific tricks,
like creating a file on the filesystem, check for it on bootup, if it exists, boot into the chrooted Ubuntu environment.
I still have to take a look at the source though, basically finding out at which stage the ways of Android and Ubuntu seperate.
beidl said:
It's a very bad idea to screw around with the bootloader and partition table.
kexec would be the way to go, but it requires kernel patches for both the Android ROM and the Ubuntu ROM.
Also, since Ubuntu Touch is just chrooted inside CM, I guess it would be possible to make some CM specific tricks,
like creating a file on the filesystem, check for it on bootup, if it exists, boot into the chrooted Ubuntu environment.
I still have to take a look at the source though, basically finding out at which stage the ways of Android and Ubuntu seperate.
Click to expand...
Click to collapse
Do you think we will be able to run Ubuntu and CM? My idea was to modify partition table to add more partition and then, if you wanna run Android OS, flash its kernel to boot it in Android OS or flash Ubuntu Phone OS kernel (edited to boot specific partions) to boot Ubuntu Phone OS. Do you really think that it's a bad idea? I think it is the best option (and it's the only I know). Could you give me more details of that "Specific tricks" to do with CM?
BTW, I NEED MORE HELP!
Not a dev, but thought I'd try and give some helpful advise. I have an HP TouchPad that dual boots webOS and Android. Maybe looking at how that works will help you. Just a thought.
urko95 said:
Do you think we will be able to run Ubuntu and CM? My idea was to modify partition table to add more partition and then, if you wanna run Android OS, flash its kernel to boot it in Android OS or flash Ubuntu Phone OS kernel (edited to boot specific partions) to boot Ubuntu Phone OS. Do you really think that it's a bad idea? I think it is the best option (and it's the only I know). Could you give me more details of that "Specific tricks" to do with CM?
BTW, I NEED MORE HELP!
Click to expand...
Click to collapse
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
beidl said:
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
Click to expand...
Click to collapse
I will give it a try later!
Thanks for your help!
couldn't modifying the bootloader be considered distributing a derivative work under the dmca?
In my opinion to have a dual booting you will need:
- A ramdisk that will prepare the partitions according to the choice of which OS
- A kernel that supports two versions of OS
- Two separate SD with the respective folders drivers etc. ... (This Is not possible on GNEX)
For the rest I do not know ubuntu for phone, it would take some expert.
anarkia1976 said:
In my opinion to have a dual booting you will need:
- A ramdisk that will prepare the partitions according to the choice of which OS
- A kernel that supports two versions of OS
- Two separate SD with the respective folders drivers etc. ... (This Is not possible on GNEX)
For the rest I do not know ubuntu for phone, it would take some expert.
Click to expand...
Click to collapse
Anarkia, What do you think about beidl's method?
NOTE: Thread organized and updated
A edited phablet file, I have deleted all sample photos, videos and messages. To download it, go to the 3rd post!
Excuse me,
can i flash these flies with CWM recovery?
urko95 said:
How to install Ubuntu Phone OS
NOTE: This files doesn't include the option to make a dual boot yet
-I'm not responable of any damage could have your GNex after flashing Ubuntu Phone OS this way-
Steps:
Download files quantal-preinstalled-armel+maguro.zip (4,6 MB) and quantal-preinstalled-phablet-armhf.zip (481 MB), and copy them to your GNex.
NOTE: You can use a modified file without all sample photos, videos and messages modified by me. Donwload it here: edited-quantal-preinstalled-phablet-armhf-v1.zip
Make a Nandroid Backup (to be able to restore Android later)
Make a Factory Reset
Flash them (1-.quantal-preinstalled-armel+maguro.zip and 2-.quantal-preinstalled-phablet-armhf.zip)
Reboot (In a few seconds Ubuntu will boot up)
If you want to restore Android, make a backup of Ubuntu first if you want to install Ubuntu again
*This guide was originally posted by eng.stk*
NOTE: Second file (quantal-preinstalled-phablet-armhf.zip) will take few minutes to flash so don't panic and relax until it's flashed but, if you use the file that it has been modified by me, it will be faster. This method doesn't wipe your internal storage (/sdcard)
This way you could have both system only restoring backups of both OS. It's a good to have both system while dual boot it's being developed.
Click to expand...
Click to collapse
LucaZPF said:
Excuse me,
can i flash these flies with CWM recovery?
Click to expand...
Click to collapse
Yes, you can, with TWRP or CWM, you choose.
Reporting semi-success
So i diffed the system directories of CM 10.1 and Ubuntu Touch and found the new files.
/system/bin/modelid_cfg.sh
/system/bin/ubuntuappmanager
/system/bin/ubuntu_chroot
/system/bin/uchroot
/system/usr/idc/autopilot-finger.idc
/system/quantal-ubuntu_stamp
Click to expand...
Click to collapse
I pushed those files to my working CM 10.1 installation on the GNex.
Since I did not wipe my GNex when I went back from Ubuntu Touch to CM 10.1, the folder structure
of Ubuntu stayed at /data/ubuntu/.
Then, I rebooted into the bootloader and flashed the boot.img of Ubuntu Touch to the GNex.
After rebooting, the device was stuck at the Google boot logo but the kernel did actually boot, so I was able to adb shell into the device.
dmesg returned:
Code:
<6>[ 15.739807] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4783, /home/ubuntu/jenkins/workspace/phablet-image/kernel/samsung/tuna/drivers/gpu/pvr/bridged_pvr_bridge.c]
That means Canonical still uses the kernel from before a week, this kernel doesn't play nicely with the new proprietary GPU driver.
I'll try pushing the old GPU blobs now...
beidl said:
Reporting semi-success
So i diffed the system directories of CM 10.1 and Ubuntu Touch and found the new files.
I pushed those files to my working CM 10.1 installation on the GNex.
Since I did not wipe my GNex when I went back from Ubuntu Touch to CM 10.1, the folder structure
of Ubuntu stayed at /data/ubuntu/.
Then, I rebooted into the bootloader and flashed the boot.img of Ubuntu Touch to the GNex.
After rebooting, the device was stuck at the Google boot logo but the kernel did actually boot, so I was able to adb shell into the device.
dmesg returned:
Code:
<6>[ 15.739807] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4783, /home/ubuntu/jenkins/workspace/phablet-image/kernel/samsung/tuna/drivers/gpu/pvr/bridged_pvr_bridge.c]
That means Canonical still uses the kernel from before a week, this kernel doesn't play nicely with the new proprietary GPU driver.
I'll try pushing the old GPU blobs now...
Click to expand...
Click to collapse
Waiting to your results, great job beidl!
Sv: [DEV] Dual Booting Project [Android - Ubuntu Phone OS] (HELP NEEDED)
First zip to flash is linked wrong it links to the IMG
Ubuntu phone os is nice but laggy buggy power eating just tried it. Maybe we should focus on it running good before dual boot
Did anyone try using it ? Gsm and all that did not work on my gnex. Did you guys have luck?
Sent from my Galaxy Nexus using xda premium
This isn't hard. Towel root, use ES file Explorer to uninstall system app Device Services Platform from rooted device to disable OTA updates. Do everything else from other posts to install Gapps. Enjoy a truly nice phone.
Not sure if I am doing something wrong but I downloaded the towelroot v3 apk from geohots site and when I press the make it rain button it says "This phone isn't currently supported".
I also tried tapping the towelroot v3 button and trying the below with no luck:
1337 0 1 0 4 0
1337 0 1 7380 4 0
1337 0 1 0 4 1
I am experiencing the same. When you click "make it rain" in Towel Root you get a phone is unsupported. Looks like no way as of yet to root Amazon Fire Phone.
Guys,could you try Bin4ry's rooting method? I has worked on all tate and jem models. Also,can someone make a list of the files in /dev/block?
SafinWasi said:
Guys,could you try Bin4ry's rooting method? I has worked on all tate and jem models. Also,can someone make a list of the files in /dev/block?
Click to expand...
Click to collapse
@SafinWasi - I tried the Bin4ry root method but I don't see an option in the Fire OS to enable USB debugging, so adb does not read the device. I will try to get a list of the files in /dev/block/ to you if I'm able to read the file system through one of the explorers. Sounds like towelroot is working for some, and not for others?
EDIT: Here is the list of files in /dev/block/
/platform/msm_sdcc.1
/voId/ (EMPTY FOLDER)
/loop0
/loop1
/loop2
/loop3
/loop4
/loop5
/loop6
/loop7
/mmcblk0
/mmcblk0boot0
/mmcblk0boot1
/mmcblk0p1
/mmcblk0p10
/mmcblk0p11
/mmcblk0p12
/mmcblk0p13
/mmcblk0p14
/mmcblk0p15
/mmcblk0p16
/mmcblk0p17
/mmcblk0p18
/mmcblk0p19
/mmcblk0p2
/mmcblk0p3
/mmcblk0p4
/mmcblk0p5
/mmcblk0p6
/mmcblk0p7
/mmcblk0p8
/mmcblk0p9
/mmcblk0rpmb
/ram0
/ram1
/ram10
/ram11
/ram12
/ram13
/ram14
/ram15
/ram2
/ram3
/ram4
/ram5
/ram6
/ram7
/ram8
/ram9
/zram0
Please let me know if there's anything else I can do to help.
I am M3 said:
@SafinWasi - I tried the Bin4ry root method but I don't see an option in the Fire OS to enable USB debugging, so adb does not read the device. I will try to get a list of the files in /dev/block/ to you if I'm able to read the file system through one of the explorers. Sounds like towelroot is working for some, and not for others?
EDIT: Here is the list of files in /dev/block/
/platform/msm_sdcc.1
/voId/ (EMPTY FOLDER)
/loop0
/loop1
/loop2
/loop3
/loop4
/loop5
/loop6
/loop7
/mmcblk0
/mmcblk0boot0
/mmcblk0boot1
/mmcblk0p1
/mmcblk0p10
/mmcblk0p11
/mmcblk0p12
/mmcblk0p13
/mmcblk0p14
/mmcblk0p15
/mmcblk0p16
/mmcblk0p17
/mmcblk0p18
/mmcblk0p19
/mmcblk0p2
/mmcblk0p3
/mmcblk0p4
/mmcblk0p5
/mmcblk0p6
/mmcblk0p7
/mmcblk0p8
/mmcblk0p9
/mmcblk0rpmb
/ram0
/ram1
/ram10
/ram11
/ram12
/ram13
/ram14
/ram15
/ram2
/ram3
/ram4
/ram5
/ram6
/ram7
/ram8
/ram9
/zram0
Please let me know if there's anything else I can do to help.
Click to expand...
Click to collapse
Oh yeah,it's got a boot0block file(mmcblk0boot0). Can you check which file is ridiculously large? Also,what's in the platform file?
Sent from my device running CyanogenMod 11
SafinWasi said:
Oh yeah,it's got a boot0block file(mmcblk0boot0). Can you check which file is ridiculously large? Also,what's in the platform file?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
@SafinWasi - The files in the dev/block/ all show as empty 0.00b. And I apologize, looks like msm_sdcc.1 is actually a folder which contains the following:
By-name (folder)
aboot
boot
cache
dbi
DDR
fsc
fsg
misc
modem
modemst1
modemst2
persist
recovery
rpm
sbl1
ssd
system
tz
userdata
By-num (folder)
p1 thru p19
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
Again, all files show as 0.00b for me, but I'm using ES File Explorer. Also the files are showing with -rw permissions.
I am M3 said:
@SafinWasi - The files in the dev/block/ all show as empty 0.00b. And I apologize, looks like msm_sdcc.1 is actually a folder which contains the following:
By-name (folder)
aboot
boot
cache
dbi
DDR
fsc
fsg
misc
modem
modemst1
modemst2
persist
recovery
rpm
sbl1
ssd
system
tz
userdata
By-num (folder)
p1 thru p19
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
Again, all files show as 0.00b for me, but I'm using ES File Explorer. Also the files are showing with -rw permissions.
Click to expand...
Click to collapse
Can you pull the boot file and send it to me? Looks like we just found the kernel. Also,the system file should be large
Sent from my device running CyanogenMod 11
towelroot
SafinWasi said:
Oh yeah,it's got a boot0block file(mmcblk0boot0). Can you check which file is ridiculously large? Also,what's in the platform file?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
All versions of towelroot are not created the same it seems. I had rooted my Kindle Fire HDX 8.9 and done everything it seems that everyone here had posted. Installed Super SU, KindleFree Pro, etc. Well, the pesky Kindle Fire updated nonetheless and I had to search for and find a version of towelroot that would work to re root the device again. At the same time, it was a different version of towelroot that rooted my 2 day old phone weeks ago and before I knew it, I was getting nags that when I was connected to wifi again, the phone was going to update OS! I did I boatload of searching on the internet and discovered that the Fire TV uses system app Device Services Platform (DSP) to do OTA updates. I just took a gamble and used ES File Explorer to uninstall that system app. ES File Explorer gave me an error saying uninstall failed (on phone and Kindle HDX 8.9). but on reboot nag was gone and I continue to have access to Gapps, playstore, Chrome, everything. I did use xposed installer to load Gapps. Amazon Instant video still works, it's all the phone it should be and is fast as heck and pretty, lol.
I have no idea why there are so many sources for towelroot and why seemingly same versions really are NOT. I just know that Google is your friend and shotgun approach works and there is a version that will your phone. I am not a geek and did this
Dilbert1959 said:
All versions of towelroot are not created the same it seems. I had rooted my Kindle Fire HDX 8.9 and done everything it seems that everyone here had posted. Installed Super SU, KindleFree Pro, etc. Well, the pesky Kindle Fire updated nonetheless and I had to search for and find a version of towelroot that would work to re root the device again. At the same time, it was a different version of towelroot that rooted my 2 day old phone weeks ago and before I knew it, I was getting nags that when I was connected to wifi again, the phone was going to update OS! I did I boatload of searching on the internet and discovered that the Fire TV uses system app Device Services Platform (DSP) to do OTA updates. I just took a gamble and used ES File Explorer to uninstall that system app. ES File Explorer gave me an error saying uninstall failed (on phone and Kindle HDX 8.9). but on reboot nag was gone and I continue to have access to Gapps, playstore, Chrome, everything. I did use xposed installer to load Gapps. Amazon Instant video still works, it's all the phone it should be and is fast as heck and pretty, lol.
I have no idea why there are so many sources for towelroot and why seemingly same versions really are NOT. I just know that Google is your friend and shotgun approach works and there is a version that will your phone. I am not a geek and did this
Click to expand...
Click to collapse
I agree mate. Towelroot versions are different.
Dilbert1959 said:
All versions of towelroot are not created the same it seems. I had rooted my Kindle Fire HDX 8.9 and done everything it seems that everyone here had posted. Installed Super SU, KindleFree Pro, etc. Well, the pesky Kindle Fire updated nonetheless and I had to search for and find a version of towelroot that would work to re root the device again. At the same time, it was a different version of towelroot that rooted my 2 day old phone weeks ago and before I knew it, I was getting nags that when I was connected to wifi again, the phone was going to update OS! I did I boatload of searching on the internet and discovered that the Fire TV uses system app Device Services Platform (DSP) to do OTA updates. I just took a gamble and used ES File Explorer to uninstall that system app. ES File Explorer gave me an error saying uninstall failed (on phone and Kindle HDX 8.9). but on reboot nag was gone and I continue to have access to Gapps, playstore, Chrome, everything. I did use xposed installer to load Gapps. Amazon Instant video still works, it's all the phone it should be and is fast as heck and pretty, lol.
I have no idea why there are so many sources for towelroot and why seemingly same versions really are NOT. I just know that Google is your friend and shotgun approach works and there is a version that will your phone. I am not a geek and did this
Click to expand...
Click to collapse
Hi @Dilbert1959 - could you please post in this thread, or PM me, the towelroot apk which worked for you?
I am M3 said:
Hi @Dilbert1959 - could you please post in this thread, or PM me, the towelroot apk which worked for you?
Click to expand...
Click to collapse
Same here, interested in the working towelroot apk. Having the same issue with what I can get from the towelroot site.
Grizzlax said:
Same here, interested in the working towelroot apk. Having the same issue with what I can get from the towelroot site.
Click to expand...
Click to collapse
I got a response from Dilbert1959 which linked to a file on Google Drive, but would not let me download as it violated ToS. Haven't gotten a response from him since. Every towelroot apk I've tried has not worked for me, and I've tried around 10 different sources. I've also tried multiple variations of the modstrings in the v3 towelroot with no success, however I believe there is a modstring that will work for this phone - we just haven't found it yet.
So nothing new yet on this front?
I've tried several versions of Towelroot with no success.
I'm really digging the phone, with a few exceptions. I'd love to be able to get Google Services on it.
Hopefully something solid works out soon.
rkalajian said:
So nothing new yet on this front?
I've tried several versions of Towelroot with no success.
I'm really digging the phone, with a few exceptions. I'd love to be able to get Google Services on it.
Hopefully something solid works out soon.
Click to expand...
Click to collapse
If your phone is already updated to 3.5.1, there is currently no root method. You can follow this guide to install the Google apps on your phone. They work (with some annoying force close messages)
http://www.gizmag.com/how-to-install-google-apps-kindle-fire-hd-hdx/30736/
Click to expand...
Click to collapse
I am M3 said:
If your phone is already updated to 3.5.1, there is currently no root method.
Click to expand...
Click to collapse
Damn. I'm already on 3.5.1. Has anyone been able to successfully roll back somehow?
rkalajian said:
Damn. I'm already on 3.5.1. Has anyone been able to successfully roll back somehow?
Click to expand...
Click to collapse
Amazon still has the download link up for the 3.5 OS. The stock recovery has an option for "update via ADB" which will prompt you to sideload an update file. I'm thinking this will allow us to revert to version 3.5 unless Amazon has somehow blocked it. This hasn't been tested yet (and since this is my only phone to use right now, I'm not willing to risk turning it into a paperweight)
I suggest installing a different launcher (CLauncher works good) and installing the GApps if you want a more "regular" Android experience.
I am M3 said:
If your phone is already updated to 3.5.1, there is currently no root method. You can follow this guide to install the Google apps on your phone. They work (with some annoying force close messages)
Click to expand...
Click to collapse
I tried this method of non-root access to install Google Play support. It didn't work for my purposes. I could pull up GMail (after setting up a one-time App password since I use 2-step verification), but there were lots of error messages all the time about Google services stopping. What I really wanted it for was to be able to link my Clash of Clans game into my Google+ account for backups. But, that App won't even pull up with the bastardized Play support they had developed for the Fire HDX.
Anyone else have any luck with Towelroot after the 3.5.1 update? I'd really like to get working Google Services support - it is by far the most disappointing feature of the phone. I actually love the Fire Phone other than that.
Thanks in advance,
MR
Guys,if you have trouble in recovery with Update Via ADB,try using a linux distro. @Dilbert1959 @I am M3 please try this.
I was able to get into recovery and sideload the 3.5 bin and downgrade. It worked sort of. In that it killed the phone services and created a lot of errors but it was on 3.5 and I was able to use towelroot to root it. Unfortunately the fact that it killed the phone made it a non-starter and I had to go back. And it wasn't as simple as just updating again I had to do a full factory restore.
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.