• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Stuck at boot after system update.

  • Thread starter Thread starter Android Question
  • Start date Start date
A

Android Question

Guest
I have a asus fonepad 7 dual sim version, from factory android 5.0 lolipop i rooted it by installing drivers manually couple weeks ago went fine, yesterday an asus system update started to install restarted an stayed at the asus boot screen for couple of hours an nothing so turned it off restarted it, same thing wont go further than boot logo, i thought ok then i will go into fastboot recovery launcher and clear the cache an rebooted still nothing, factory reset an the same, went into CWM recovery again an no recovery found, im now lost of what to do. i have no backup coz i thought its only rooted so worst case would be it would unroot it if it updated ive read an i would just have to manually re do it. plus ive not messed with custom roms or kernal either. so any help please

Ps. an if it needs reflashing i dont really understand as what about my IMEI number an all the other importent information etc that makes it run as a phone as it was my phone aswell till this happened.
 
Intel drivers for it then UPDATE-SuperSU-v2.46 CWM.zip+fastboot recovery thethering T4 option Lam Nguyen from youtube but it was in writing on xda.forums
 
Last edited:
Welcome to our AndroidForums, chodere.

You're likely experiencing a boot loop because the /system/bin/app_process[32] file(s) that get linked to the daemonsu binary as part of rooting are either stripped of its permissions and/or not compatible with the new OTA files that get installed.

Fixing this would likely require you to replace (with proper ownership and permissions) the app_process (and/or app_process32) files from the stock ROM for your device (i.e., from/for the version that matches the OTA that just got installed).

I experienced the same thing (bootloop) when trying to take a 5.x OTA update on my (2012, 1st gen) Nexus 7. Thankfully, I was able to flash back the stock system image from a set of factory images that are available for the Nexus devices.

Unfortunately, I've no idea what that would entail for your Asus Fonepad 7 device.

I don't see your specific device listed in our http://androidforums.com/categories/android-phones.3/ (phone) or http://androidforums.com/categories/android-tablets.223/ (tablet) areas, but you might have a look and see if there are any threads that might discuss your device or the restoring back to a stock state.

Wish I could be of more help :(.

edit: not sure if this is for your device, but you might have a look here to start: http://forum.xda-developers.com/showthread.php?t=2709256
 
so u mean find out which version it tryed updating but failed and update that file but manually instead of when it tryed updating from the phone an failed leaving it in the state it is now? coz it will have higher permisions to write if i do it through CWM RECOVERY on pc instead
 
To sum-up what I'm saying is that taking an OTA while rooted nowadays can indeed lead to bootloops (due to the reasons mentioned above).

[never take an OTA while you are rooted or be prepared to have a Nandroid backup to restore from or a means to flash your device back to a stock / factory state]

"Fixing" that (and other) file(s) is pretty complicated and getting your /system/bin files back to the proper stock state is the best way to go (of which I'm not familiar at all how to accomplish that for your device).
 
You must log in or register to reply here.
Back
Top Bottom