had the same problem booted back into recovery wiped cache and dalvik and reinstalled the .zip. currently at "Android is upgrading..."
- Status
I had the same issue. I rebooted to recovery again, wiped cache/Dalvik, reflashed the ROM and GApps, and it booted... but is now stuck at a "Starting apps." screen before the welcome screen or lock screen would normally display.
I dont know if this is the issue but in CM9 the updater-script said this:
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
This jellybean ROM has:
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
The boot.blob/boot.img is no issue, but you can see it's being written to a different block device, someone could try changing it to "/dev/block/mmcblk0p4" in this ROM and see what happens (I'm at work and can't at the moment)
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
This jellybean ROM has:
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
The boot.blob/boot.img is no issue, but you can see it's being written to a different block device, someone could try changing it to "/dev/block/mmcblk0p4" in this ROM and see what happens (I'm at work and can't at the moment)
Logcat has a ton of these
E/SchedPolicy( 109): add_tid_to_cgroup failed; policy=1
which I'm assuming is ok but I did see some of the following errors
E/NetdConnector( 606): Communications error: java.io.IOException: No such file or directory
E/NetdConnector( 606): Error in NativeDaemonConnector: java.io.IOException: No such file or directory
E/BandwidthController( 5781): runIptablesCmd(): failed /system/bin/ip6tables -A bw_INPUT -i lo --jump RETURN res=768
E/Netd ( 5781): Unable to create netlink socket: Protocol not supported
E/Netd ( 5781): Unable to open quota2 logging socket
D/MDnsDS ( 5781): MDnsSdListener::Hander starting up
E/Netd ( 5781): Unable to start MDnsSdListener (Invalid argument)
E/SocketListener( 5781): Obtaining file descriptor socket 'mdns' failed: Invalid argument
I'm going to try and swap out a kernel I know that works (with ics) and see if it makes any difference.
E/SchedPolicy( 109): add_tid_to_cgroup failed; policy=1
which I'm assuming is ok but I did see some of the following errors
E/NetdConnector( 606): Communications error: java.io.IOException: No such file or directory
E/NetdConnector( 606): Error in NativeDaemonConnector: java.io.IOException: No such file or directory
E/BandwidthController( 5781): runIptablesCmd(): failed /system/bin/ip6tables -A bw_INPUT -i lo --jump RETURN res=768
E/Netd ( 5781): Unable to create netlink socket: Protocol not supported
E/Netd ( 5781): Unable to open quota2 logging socket
D/MDnsDS ( 5781): MDnsSdListener::Hander starting up
E/Netd ( 5781): Unable to start MDnsSdListener (Invalid argument)
E/SocketListener( 5781): Obtaining file descriptor socket 'mdns' failed: Invalid argument
I'm going to try and swap out a kernel I know that works (with ics) and see if it makes any difference.
Seems like AOSP update-script has some issues / you have to manually flash the boot.img through fastboot - adding a step in the OP
Edit: here, added a How to install
I'll try to fix update script in next build
Edit: here, added a How to install
I'll try to fix update script in next build
Still not booting for me. I'll grab a logcat when I'm back at my computer.
Do you think swapping out your boot.blob from your cm9 build and changing the update script would do anything. I'm going to try that next.
Sent from my Galaxy Nexus using Tapatalk 2
Do you think swapping out your boot.blob from your cm9 build and changing the update script would do anything. I'm going to try that next.
Sent from my Galaxy Nexus using Tapatalk 2
Flash boot command in OP is slightly wrong?
"fastboot -i 0x0B05 flash boot boot.img"
"fastboot -i 0x0B05 reboot"
---------- Post added at 10:57 PM ---------- Previous post was at 10:45 PM ----------
Did the above and still gets stuck on the above
Last edited:
K I'll be home in a couple hours but I would try this for you dev-ish type people:
I've packed the boot.img into a blob, you can download it here:
http://bacoosta.com/builds/boot.blob
TRY THIS:
Put that boot.blob into the .zip root directory
then inside the updater-script file in META-INF replace:
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
with:
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
If that doesn't work I dunno what would
I've packed the boot.img into a blob, you can download it here:
http://bacoosta.com/builds/boot.blob
TRY THIS:
Put that boot.blob into the .zip root directory
then inside the updater-script file in META-INF replace:
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
with:
package_extract_file("boot.blob", "/dev/block/mmcblk0p4");
If that doesn't work I dunno what would
Last edited:
Having problems working with the zip file, usually I have no problem modifying archives with 7zip but this one won't let me add anything to the archive, deleting seems to be working fine.
To the the linux cave Robin...
Last edited:
Doesn't seem to work either. I dropped the blob in the root of the zip file, and modified the updater-script as mentioned, did a full wipe and flash, but still stuck on the android screen.
Here is a logcat of an attempted boot from a fresh wipe, using the fastboot method to send the boot.img, if it helps.
View attachment boot.txt
Mine didn't go so well:
set_perm: some changes failed
E:Erro in /sdcard/xplodwild-tf300t-JB-20120711_MOD.zip
(Status 7)
Installation aborted.
Tested the archive I modified in linux with 7zip and it failed crc check on a file that I never touched where as xplod's file passed fine so I messed up the archive when I modified it.
Guess I'll leave it alone for now since yours got stuck on boot screen cdspaco, wait and see how termleech makes out.
Last edited:
Please use fastboot to manually flash boot.img
The issue is fixed by a commit on CM.
Anyway, I'll guess I'll migrate my device tree on CM tree, should eliminate the few flashing bugs in here.
I tried manually flashing the boot.img in fastboot a number of times and still get can't get it to boot.
Sorry, my post wasn't very clear. Using fastboot to flash the boot.img file doesn't work for me either. That attempt is what the logcat was from (full wipe, flashed ROM and GApps, reboot to flashboot and manually flash the boot.img, reboot). Anyway, if you are migrating to the CM tree, perhaps these boot issues will be fixed by that.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
26DISCLAIMER
This is an experimental build. It means things doesn't work, and it will take time to fix.
NO ETA
NO REQUESTS
This is temporary until CM10 tree is in a state where I can build it fine for this device. Consider this as a "preview"
Introducing Android 4.1.1 Jelly Bean for Asus TF300T
This is an early ROM built from Android Jelly Bean AOSP code.
What works:
- Wi-Fi
- Bluetooth
- Storage
- Audio playback
- Sensors
What doesn't work:
- Camera
- Audio volume (is stuck at either 0 or 50%)
- Audio recording likely
- HW Video playback (but software playback works)
- Screenshot
Downloads
Please, users with a little bit of experience only. Flash the update zip through CWM.
Build 1: http://dl-bacon.bbqdroid.org/dinner/xplodwild-tf300t-JB-20120711.zip
Google Apps: http://www.mediafire.com/?llva21h5j1ruab0
How to install
- Download the build
- Copy to sdcard
- WIPE DATA
- On your computer, extract the build zip (or just boot.img inside it)
- Reboot to recovery, flash zip
- Reboot to fastboot, type "fastboot -i 0x0B05 flash boot boot.img"
- Reboot to Jelly Bean!
Support
I know what works and what doesn't work, so don't tell me "This doesn't work!! :'(" or "When will you fix that?" - it'll come when it's ready.
If you're a developer, sources are on http://github.com/xplodwild/android_device_asus_tf300t, branch jb-aosp. Feel free to help!
If you want to speed things up, you can hit the "Donate to me" button up ahead
Thanks, and have fun!22
Please use fastboot to manually flash boot.img
The issue is fixed by a commit on CM.
Anyway, I'll guess I'll migrate my device tree on CM tree, should eliminate the few flashing bugs in here.
