Droid x2/cm9 beta; I was running scripts for supercharger and had issues. I have lost root access. tired to run the patched BSR but it wont load into recovery. Do I have to SBF? Any help would be appreciated.
Have you checked what your root settings are in developer options? Did supercharger report any errors with the binary? You might want to run the supercharger starter kit.
See if updating the su binary in superuser/supersu app does anthing.
LeadoffMan131 said:
See if updating the su binary in superuser/supersu app does anthing.
Click to expand...
Click to collapse
Thanks guys. But I Bit the bullet and sbf'd. Reflashed, and I'm actually so glad i did. 9 beta is working like a champ now. I really have no issues with lag now with a fresh flash and restored apps from tibu everything is roses. Battery stamina seems to have improved as well. Although i am wondering how some guys out there are getting a whole day out of a battery charge. Ive had to recharge at least twice a day since i got this phone almost a year ago and this is the 4th ROM I've run on it. I was supercharging wen i screwed everything up and with the reflash the pjone is working so well now that i think I'll bag the supercharging til i get bored again! And let me take this opportunity to say thanks to all involved on putting the CM9 ROM out there. Love this ROM! Thanks techno-gods!
Did you put the su binary that was suggested in the forum? I used both the su binary and the busy box version suggested in the forum. I had to do 2 battery pulls but my phone works right now. Never lost access to my recovery though.
Sent from my MB870 using Xparent Cyan Tapatalk 2
Gblake13 said:
Did you put the su binary that was suggested in the forum? I used both the su binary and the busy box version suggested in the forum. I had to do 2 battery pulls but my phone works right now. Never lost access to my recovery though.
Sent from my MB870 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I ran the v6 setup script first, which had the su and busybox, i already had later verdions of both running on my phone. Maybe thats what caused the lockup?
Its been reported that the V6 script can cause issues with BSR. Not sure why. I have never had issues but read others have. If it happens again just unsupercharge if you need to get into the recovery. Did you lose root to all your rooted apps or were you just having problems with BSR? If you lost root all together, then something else went wrong.
Related
After flashing new moto update (the one from this forum, not the one that came over the air) using RSD Lite, it worked. Then I ran through the dock root method to root it, that seemed to work. And then I restarted the phone and get the red moto logo and it will not get past it. Should I reflash this update or do I need to flash something else like stock pudding? I will attempt to flash 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US again and hope that fixes whatever got broke. Any other advice?
Did you try a battery pull and reboot?
Sent from my MB855 using xda premium
Oh yes. The photon battery pull is well documented. It fixes many problems but it's not fixing this one so a reflash of the update is happening now but I have a bad feeling that isn't it.
Okay. It did work. Acted like it wasn't going to but then started to work. Should I redo the dock root and assume I typoed (I'm pretty sure I did not) or should I do photon torpedo? I did dock root before the OTA several weeks ago and it worked fine then.
No you don't have to buy a new photon. Mine did the same thing but I flashed like 4 times before it took. If you can get it into rsd lite to flash something your not bricked. Take the battery out for 5 minutes, put it back in and try to flash it again. It should take and boot up. Also close rsd lite then reopen it.
Sent from my MB855 using xda premium
Try the one click root method. Glad you got out straightened out.
Sent from my MB855 using xda premium
Okay. The phone didn't temp brick last time because of the root method I chose, it was busybox related. I forgot that LCD Density Changer relied on Busybox to set the default system density. The option had already been set to save it as a system default. So whatever was done to install Busybox has to do it again. If someone isn't sure, they can always uninstall any root requiring programs that also use Busybox when going from root to unrooted to rooted.
mikel719 said:
Try the one click root method. Glad you got out straightened out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I agree, try the one click root method as I was having errors and this worked for me.
Edit* glad it all worked out
First off I spent hours searching and trying everything I could under the sun. I have ota update and did the one click root which has worked perfectly. the problem i have is trying to boot into recovery so i can flash speedy v2 roadrunner. thing is have tried d2 dx and i cant boot into recovery it just boots normally. i have usb debug off and even tried booting cwm recovery through rom manager with no success and tried droidx/ x init/ droid 2 versions of clockwork to no avail. what am i doing wrong?
http://forum.xda-developers.com/showthread.php?t=1169677
Download the apk, click install, then plug in your phone, and hit recovery.
Sent from my DROID X2 using Tapatalk
Make sure you're plugging your phone into a wall charger NOT USB to a PC.
Ok sorry for the absence but homework is a @#$%&. Ok so I have system recovery installed. I turned off ish debug and plugged it into a regular charger. I then proceeded to recovery where i hit install zip from sd then installed navens init hack which I guess went ok dunno how to check. I rebooted twice then tried to install speedy v2 and I used root explorer to check for "zipalign" anything in /data but nothing. So obviously im being an idiot and although I tried the rehack also I can't get it to show the log. What gives here?
Oh and thank you tremendously for the time and help.
ilovesoad said:
http://forum.xda-developers.com/showthread.php?t=1169677
Download the apk, click install, then plug in your phone, and hit recovery.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Thanks so much I was finally able to get into recovery.
Anyone with the faintist idea? bump.
Did u try installing busy box 1.18.4 I think its the one overmind reccomended although im not 100%
Do u have ANY busybox installed? U would get it or can check if u have it with jrummy busybox installer from market.
Or just try re flashing the rehack after the initial init.d hack and it is recommend to reboot twice.
Might be a better question to ask overmind or navendrob in their threads regarding the hacks.
ashclepdia said:
Did u try installing busy box 1.18.4 I think its the one overmind reccomended although im not 100%
Do u have ANY busybox installed? U would get it or can check if u have it with jrummy busybox installer from market.
Or just try re flashing the rehack after the initial init.d hack and it is recommend to reboot twice.
Might be a better question to ask overmind or navendrob in their threads regarding the hacks.
Click to expand...
Click to collapse
yea i haz busybox and rebooted twice on both installs.
I installed cm7 for my first rom ever. It was running great next to some force closes which have gone away after rewiping cache,dalvik. Now my 3g hangs a lot/drops completely. I've reset, done battery pulls,*228 several times. It was great before and I *think * it started with restoring apps from titanium.
My question is what can I do? Reflash? Etc. I'm tech literate but a noob with roms etc. Any ideas are much appreciated and a quick description of how would be great. Fwiw I tried the mashup to no avail. All I know is when first flashed it was great. Seems to be affecting battery though it's just from the phone grinding to connect to 3g. Thanks in advanced.
thechaoz said:
I installed cm7 for my first rom ever. It was running great next to some force closes which have gone away after rewiping cache,dalvik. Now my 3g hangs a lot/drops completely. I've reset, done battery pulls,*228 several times. It was great before and I *think * it started with restoring apps from titanium.
My question is what can I do? Reflash? Etc. I'm tech literate but a noob with roms etc. Any ideas are much appreciated and a quick description of how would be great. Fwiw I tried the mashup to no avail. All I know is when first flashed it was great. Seems to be affecting battery though it's just from the phone grinding to connect to 3g. Thanks in advanced.
Click to expand...
Click to collapse
Try the CDMA mods. Theyre simple and do help to certain degree.
Sent from my MB870 using Tapatalk 2
@ TheChaoz
Did u do a RSD to 2.3.4.
Super Root
Install Recovery
Wipe The big 3
Apply zip: CM7 RC1, CM7 GAPPS, AND CM7 RERECOVERY AND REBOOT
DO NOT UPGRADE SUPERUSER OR UPDATE BIANARY ( SU GETS SUPER SKETCHY) RECOMMEND A SWAP TO "SUPERSU" FROM THE MARKET
IF YOU HAVE ALREADY UPDATE BIANARY AND SUPERUSER RECOMMEND STARTING OVER WITH RSD.
EVEN WITH UNINSTALL OF SUPER USER BIANARY STILL STICKS AFTER UPDATES :/....
AFTER MANY ATTEMPTS, THIS IS WHAT SEEMS TO DO THE TRICK
Sent from my MB870 using Tapatalk 2
I've been having 3G issues for the past few months, I had on and off really bad data speeds where I live and they think its a network issue since my 1st and 2nd replacement dx2's still have the issue. And today I found out they are getting ready to roll out 4g in the area. Makes me wonder if they might be screwing with the towers. Location: Scarborough, Maine
Sent from my DROID X2 using XDA
6Flip9 said:
@ TheChaoz
Did u do a RSD to 2.3.4. ***I was already 2.3.4 if that's what your saying
Super Root
Install Recovery
Wipe The big 3 ***So dalvik,cache, and?
Apply zip: CM7 RC1, CM7 GAPPS, AND CM7 RERECOVERY AND REBOOT
DO NOT UPGRADE SUPERUSER OR UPDATE BIANARY ( SU GETS SUPER SKETCHY) RECOMMEND A SWAP TO "SUPERSU" FROM THE MARKET
IF YOU HAVE ALREADY UPDATE BIANARY AND SUPERUSER RECOMMEND STARTING OVER WITH RSD.
EVEN WITH UNINSTALL OF SUPER USER BIANARY STILL STICKS AFTER UPDATES :/....
AFTER MANY ATTEMPTS, THIS IS WHAT SEEMS TO DO THE TRICK
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Ok I followed the instructions to a T on the thread. There was a part about updating su then installing this or that. I'm on phone so I can't check. I have cm7 recovery installed from the thread. Can I get a step by step for dummies? Thanks in advanced guys.
thechaoz said:
Ok I followed the instructions to a T on the thread. There was a part about updating su then installing this or that. I'm on phone so I can't check. I have cm7 recovery installed from the thread. Can I get a step by step for dummies? Thanks in advanced guys.
Click to expand...
Click to collapse
Use this guide to SBF BACK http://forum.xda-developers.com/showthread.php?p=18720189
Then follow the other guides by his signature (bottom of post)
Good luck
DROID DOES, Apple did...like I forgot when
Ok so essentially I'm going back to factory then re root and install rom again?
@chaoz
Yes simply start from scratch (VIRGIN 2.3.4) no scripts... no zips... nothing changed
ROOT IT
Using the normal dx2 recovery
1.Install recovery.apk
2.Boot into recovery
3.Wipe data/cache/dalvic
4. Install 3 zips from SD, cm7 Rc1/ gapps/ rerecovery cm7
5 Reboot
As soon as your all booted
Download "supersu" from market install
Grant superuser acess to "supersu"
To make install permanent create backup of supersu and place in system/app and delete superuser and fix permissions
Sent from my MB870 using Tapatalk 2
K thanks ....that last part was worded strangely and saw nothing in the original thread ....how do I move su aground then delete it then fix permissions? Thanks in advanced
Good Afternoon all,
I am S-OFF HBoot 1.40, I have not had an issues until recently. I tried installing SetCpu and superuser denied permission, even tho I have it set to allow. I then tried updating superuser binary and when it gets to Gaining root access.. "fail!"
I am not sure what the issue could be as, i am able to flash ROMs, Kernals, etc.
Would it be wise of me to S-On it and then S-Off Again ?
The issue with superuser permissions does occur randomly with certain applications, so i am not exactly aware of what is going on. I am hoping someone can give me a hand.
Thank you in advance,
Miamiboi
I have had this issue before and it turns out that I flashed the wrong type of superuser for my phone. It was meant for donut and not Ics. It could be that you flashed the wrong superuser zip. Here's the file http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip. Let me know if that helps you. I flashed this in recovery and it worked like a charm.
Jsparta26 said:
I have had this issue before and it turns out that I flashed the wrong type of superuser for my phone. It was meant for donut and not Ics. It could be that you flashed the wrong superuser zip. Here's the file http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip. Let me know if that helps you. I flashed this in recovery and it worked like a charm.
Click to expand...
Click to collapse
THANKS!!!
That was the issue!!
Now this is occurring ... When checking the su after update it fails. I'm not sure if this is an issue or not.
Sent from my PG86100 using xda premium
Look for SuperSU in the playstore, much better than what you're using, IMHO.
PS: make sure to uninstall the old superuser app.
Sent from my PG86100 using Tapatalk 2
Jim M said:
Look for SuperSU in the playstore, much better than what you're using, IMHO.
PS: make sure to uninstall the old superuser app.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
But only AFTER you install SuperSU first (Superuser has to give SuperSU root access to install first). I like SuperSU better as well.
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Unless you have s-off or have flashed a new kernel, the system partition is right protected, even when you think it isn't. I think that is what is causing your problem.
Why don't you flash a room that already had root/busybix installed?
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk 2
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
When first unlocking and rooting my phone, I thought the same thing about busy box. But what you need to do is flash a new kernel first and foremost which will remove write protection.
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2[/QUOTE]
c2a5nn1o4n said:
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
[/QUOTE]
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access[/QUOTE]
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
c2a5nn1o4n said:
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Click to expand...
Click to collapse
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?[/QUOTE]
No, again, you need to flash a kernel first so that you have write permissions
c2a5nn1o4n said:
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
Click to expand...
Click to collapse
Reading your OP and the rest of your comments in this thread, you're all over the place. Things you are doing will not fix your original problem and trying to achieve s-off just because it looks popular and running into difficulties trying to achieve it only adds to problems and confusion. I suggest you step back, slow down and get familiar with terms before you break another phone. While a small portion of the info is EVO 4G specific, you should check these out for general knowledge:
http://androidforums.com/evo-4g-all-things-root/278898-android-partitions-kernels-explained.html
http://androidforums.com/evo-4g-all...ore-information-about-android-partitions.html
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
docnok63 said:
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
Click to expand...
Click to collapse
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
You're right. I had assumed he had unlocked and flashed an unsecure boot image before attempting to flash su and busybox. Perhaps I did assume too much. I'll refer him to here in that case.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
Ok so I have to have busybox? I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
c2a5nn1o4n said:
Ok so I have to have busybox I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
Click to expand...
Click to collapse
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
UrGuardian999 said:
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
Click to expand...
Click to collapse
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
c2a5nn1o4n said:
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
Click to expand...
Click to collapse
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
c2a5nn1o4n said:
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
Click to expand...
Click to collapse
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Also on my other DNA I installed cynogen but not the bootimage and when I would try to reboot I would get messed up lines would that have caused that? If it would my brain has dropped to a new low
If using Cubed 3.1.3 you'll have to reflash the modules though, correct?
UrGuardian999 said:
If using Cubed 3.1.3 you'll have to reflash the modules though
Click to expand...
Click to collapse
Nope still on stock kernal
I'm currently flashing viper as well right now, had to stop and go to work right in the middle of it. My apologies hahah