Not sure if I'm in the right place, but I cant post under the specific rom thread (post count)
Anyways, I'm running a clean install of Jelly "Beans" Build 5. I updated busybox because it was requested by another program and now my phone wont get past the pink boot logo.
So I have two questions...
How can I fix this?
If it involves restoring/reflashing rom, is there any way to get a number from my recent text messages that didn't yet sync with my online google contacts?
Thanks!
+1
Had this exact problem, I'm on Synergy 118 and tried 6 different times to update busybox each time same problem hangs at bootscreen. Only thing I could do was restore and not update busybox. so far everything works as long as I don't update to the latest busybox, when an app tells me it's out of date I just ignore it. Would love a solution to this!
Just dirty flash your ROM and don't update your busy box this time
Sent from my SGS3 running Eclipse 2.1
that's what I ended up trying, and it resolved the problem.
Thanks!
Related
Tried to run a fix permissions and I got "An error occurred while attempting to run privileged commands!".
I'm running the 8/1 OTA, new hydra kernel, and 2.15.X radio.
Has anyone encountered this before??
For the record, I already updated to superuser 2.3.1 and it's still not working.
Not sure if this should be in the themes and Apps section or General.....I have had the same issue although I don't get any error when I try to run the fix permissions option it goes to a black screen then stalls. This didn't start happening until I upgraded to the newest Superuser Permissions.
Yeah I actually tried switching super user apps, but it didn't make a difference
-Sent from your mom's phone.
I just tweeted a message to Koush about it. Hopefully we'll get a reply.
Keep us updated. I just ran into this issue too. Did a backup last night with no issues, but suddenly today, I'm getting that message.
any word on this
I'm on cm6.0.1 now and no longer having the issue. Never got a reply from koush though.
-Sent from your mom's phone.
I don't mess with Fix Permissions anymore. It really screwed me up the first time I worked on SkyRaider, and a bunch of strange things began to happen. I find my phone tends to run better just leaving everything as-is.
Asterdroid said:
Tried to run a fix permissions and I got "An error occurred while attempting to run privileged commands!".
I'm running the 8/1 OTA, new hydra kernel, and 2.15.X radio.
Has anyone encountered this before??
For the record, I already updated to superuser 2.3.1 and it's still not working.
Click to expand...
Click to collapse
I was experiencing a similar deal and the only solution was; removed, rebooted and reinstalled the app......that resolved all the issues. My current setup: Leaked Hybrid Froyo 2.2 version 3.21.605.1, radio 2.15.00.07.28, Hydra 2.6.32 occuv-v10, S-OFF and what not.......Good Luck !
Another thing, in my case I was not even able to uninstall the app using the MENU/SETTINGS/APPLICATIONS/MANAGE APPLICATIONS procedure so I used 'Root Explorer', search for the app, Mount R/O and "adios"........
been reading about a bug do to "Bash" in the new roms, not sure what the fix is as i don't use RM but i think in the skyraider 3.0 rc3 tread there is a temp fix for this issue
i have been having an issue with rom manager also every time i tell it to install a zip from sd or do a back up or even reboot into recovery i get an error that says the update.zip failed signature veri. also it says the update.zip is in /cache
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
I have an HTC One S, rooted and unlocked. I downloaded CM10, attempted to update to it, yes without wiping(my fail) and sent the phone into a bootloop. In my attempts to fix I lost the ability mount the SDCard.
I did this to fix the SDCard and it worked - http://forum.xda-developers.com/showthread.php?t=1630459&page=12
I have tried to do the RUU update to bring it back to stock but it failed with error 171, USB Connectivity lost so I abandoned that idea. I did play with drivers, HTC Sync, reinstalls and registry cleanups all to no avail. This is the process I wanted to follow but no luck.....http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
When updating with CM10 it installed VERY quick, like 20ish seconds. This seemed very fast so I thought maybe a different ROM would work and I went with Dark Jelly http://forum.xda-developers.com/showthread.php?t=1848100
No matter what I do I am stuck in the bootloop. Looking for any guidance available of things to try. I have searched all over and tried the solutions that make sense but to no avail.
Fixed
So I did this: http://forum.xda-developers.com/showpost.php?p=33857020&postcount=2181
delete that file and it booted right up. Have not looked at the Dark Jelly rom to see fi it has that file too but that may have been the issue with the other ROM as well.
Summary - CM10 contains that file that needs to be deleted before upgrading if you have hboot of low versions...I know, not very descriptive but its all in my posts above.
nvm, you got it.
Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
I started this thread just because of the issue SUPERSU 0.99 brings to HTC One S with Jelly Bean update.
I hope i can help someone because i didnt find any solution to my problem until i flashed superuser and it solved my problem.
shadowch31 said:
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
Click to expand...
Click to collapse
I agree that this adds clutter, but I have been lightly following the threads for the JB ROMs and tried using superuser (though not the rc) without it working (still unable to update system). It's good to have this kind of solution in its own thread but general would probably be a better section.
Sent from my HTC One S Special Edition using xda app-developers app
This doesn't belong in the dev section for multiple reasons
Sent from my HTC VLE_U using xda app-developers app
Im sorry i didnt see that it was Development section. If someone can move it pls do so.
everyone uses SU...... this is very important for everyone using JB... leave it in here...
I feel it belongs here... this is where SU apps are in the development section... SO, this is where it should stay... (that is just my opinion)
I never want to start this thread like an development because im not a developer.
Reason is that i want to share my issue with anyone who is facing the same problem as i did.
Just like i said if someone think this thread doesn´t belong here then admins can move it to right section.
Updated to JB with OTA yesterday night.
Short version:
-Initially rooted with CWM recovery-> flashed MoDaCo stock recovery
-Apply OTA
-Flash CWM recovery
-Used CWM recovery to flash SuperSU 0.99 zip
-Uninstall/reinstall SuperSu from the Market
When starting SuperSU, it asks for update, if agree -> reboot.
BUT
When using root needing apps, like Titanium backup or FX file manager, they ask for root permission through SU and everything runs normally.
So SuperSU seems to work, only the front end app has some bug. I'm staying with that config waiting for an update.
Hi, same problem here on S3 cpu. Is this method works on S3 cpu as well? Thx for replying.
Hi. I think I have a problem with SuperSU (or something else??). I first started SuperSU last thursday (31.1.2013.). It ask me to update binary, I hit OK, and then it took about half hour to restart. System then recovered, and everything seem to be OK, but it's not!
When I connect my HTC One S to PC I only see files created (photos, videos) until 31.01.2013. Also, when I run Settings -> Memory com.android.settings crashes.
What to do?
I'm new to android. Plese help!
bihslk said:
Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Click to expand...
Click to collapse
I'm glad I ran across your thread. It helped me tremendously...
Da Baron
Any idea on how to get SuperSU work instead of SuperUser? I purchased SuperSU in the play store and I think it just looks better...
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2