Related
Good Evening everyone. As the title says i need help.
I have had my phone rooted fine in the past but went ahead and did the .893 update wich is where something went screwy. It booted fine after doing the .893 update however after doing a reboot it would not boot. just stayed at the M dual core. I think something went wrong on the update because all my apps were still there when it did boot.
So i tried doing a return to stock using the RSD lite program..that fails right away no matter what i do.
So i went and tried to do the One click fastboot system restore program.
Now when i did that the INFOpreflash validation failure showed up however everything else went through fine. the phone reboots and everything works just not great the signal strenght is very low.
The version that got installed says 5.5.1_84_dbn-55. So i try Pete's root method and it go thru to step 2 but then fails at rebooting for the second time saying it could not get root via local.prop.
If anyone could please help me get back to normal stock it would be much appreciated
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
P.S. You are stock now.
Sent from my DROID BIONIC using xda premium
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
dubsx said:
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Or XDA?
Sent from my DROID BIONIC using xda premium
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
that too, haha...
Sent from my DROID BIONIC using XDA App
Sidewind75 said:
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
Click to expand...
Click to collapse
Well, you didn't list that in the OP.
At this point, I don't know. Here is all I got: enter stock recovery and wipe everything. Reboot. Cross your fingers.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
quentin0 said:
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
Click to expand...
Click to collapse
Sometimes the truth hurts. He messed up. Don't shoot the messenger.
Moderator Message
Breathe in, breathe out!!!!
I'll breathe when this .893 goes through and I keep root
There is also some very seriously contradictory info in the OP. While castigating him for being a noob did anyone notice that he claims to have flashed the update and then reverted to stock?
This is impossible from our current understanding of how the bootloader works.
More information about the exact steps followed and the exact results at each step would be very helpful to try and figure out what really happened.
OK?
Less heat and more light...
I just got a little frustrated, as every time I open XDA today I see the same/similar post.
Cell - I didn't see in the OP where he said he flashed back. I read where he tried, but I didn't see any mention of 896.
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated.
Oh and i have also tried to unroot it..it also fails at adb not being able to gain root access
Sidewind75 said:
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated
Click to expand...
Click to collapse
This isn't going to help your current issue, but how long did you let it sit (after installing 893) before you decided it wouldn't boot? I ask because the guy who was ballsy enough to do it here said the first boot takes about 7 minutes.
EDIT: Nevermind - mine booted in 2 minutes.
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Sidewind75 said:
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Click to expand...
Click to collapse
Try to do the fastboot again and root it through there. Or, if you did that already (root in fastboot restore) try rooting afterwards.
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
tghockey07 said:
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
Click to expand...
Click to collapse
yes I did and i checked it twice after making sure root explore was closed reopened and checked the file the chmods where there...but now they are not. and seeing as how i cant root i cannot get them back on it
Receiving my Bionic in a day or two.. Should I root the Bionic before I update or update then root? The reason I ask is many times the carriers patch the root methods that are used and after the update they no longer work.
I also noticed the bootloader is still locked down and is this going to be figured out?? Coming from all HTC devices I have noticed the Recovery that is used is a little different then on my Thunderbolt.
The Recovery that is used is in the Android Market and is called the Bionic Bootloader?
I will be doing lot's of reading but my main concern was the new update that has just been pushed out, should I download it before I root??
Thanks,
Vinny
Go Patriots
I am also interested in this exact same question about what to do first. I just bought my wife a bionic and she came from a rooted Fascinate. She keeps asking me why she can't do certain things on her bionic and I have to keep telling her I'll fix it soon lol. Problem is I'm not sure if I should wait for the official update.
I'm definitely going to root because it will be her wifi at home while I'm at work.
Sent from my SHIFTAO5P
Our update process veers of the course of the official update path. We have a method of retaining root known as Forever Root by P3Droid (I believe?). In addition, our bootloader is still locked, but we are petitioning. Hoping for an Atrix type unlock. As for recovery, since we don't have unlocked bootloader, we can't write recovery. The one you see in the market is a paid donation. There is also a free one. This allows you to flash ROM's.
We also have Safestrap for CM7 and ICS, but they are still very early works.
Sent from my DROID BIONIC
I see there is a new official update rolling out and my phone will be delivered tomorrow. Should I root it right away and then download the update through recovery? Coming from a long line of HTC devices I can say that Motorola is all new to me. If I accept the new update I may not be able to root it thru the current methods. Carriers are great at plugging holes. If anyone can point me in the right direction I would appreciate it. Every article I read about the Droid Bionic there are so many different methods I am not familiar with.
Thanks,
Vinny
I was going to buy the razr but I like the idea of a battery I can get at. Both phones have just about the same specs and accessories. The Locked down bootloader really sucks.
I've been researching this question all day at work, shhh lol, and I'm pretty confident I know what to do now.
Those of us who are not rooted and have not accepted the new update will need to root first using the forever root method developed by the droidtheory crew. Then after we are rooted we can update to the newest ota and still maintain root. We will also be able to flash whatever rom we would like.
This is what I am going to do to my wife's bionic so hopefully I don't screw up! Someone correct me if I am wrong.
Sent from my SHIFTAO5P
Well I got it rooted fine, but I can't get the update to show up. I've rebooted 3 times so far and nothing. I'm currently making a nandroid backup of the complete stock rom. I'm hoping the update just hasn't rolled out yet to the South Dakota area.
Sent from my SHIFTAO5P
I was finally able to get the update. I rebooted into cwm and cleared data/factory reset. Rebooted and the update showed up. The update went smoothly and I was able to keep root. Flashed droidtheory's kinectix rom and everything is perfect now.
Word of caution: Do not format system in cwm and then try to use the reboot recovery option. It will soft brick your phone! Luckily it was very easy to fix, but it still scared the bejesus outta me!
Sent from my SHIFTAO5P
I would follow the steps you stated. follow this link and it works just fine. Be completely stock and should have no issues. Make sure to download the Blur to your SD card.
http://forum.xda-developers.com/showthread.php?t=1327537
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium
i did not see any instructions about this so i figured i would ask instead of turning my phone into a paperweight and yes i looked at the noob section and it states everything from 896 and 893 so i didn't find a solution to my question
bfitzpatrickd2d said:
i did not see any instructions about this so i figured i would ask instead of turning my phone into a paperweight and yes i looked at the noob section and it states everything from 896 and 893 so i didn't find a solution to my question
Click to expand...
Click to collapse
You need to use the pathsaver. This will put you back on 886, then root and install 43v3r root, then update to 893, and then potentially 901 from there. Read up on how to use the pathsaver.
Instructions and more here: http://forum.xda-developers.com/showthread.php?t=1433783
Can you explain to me how this pathsaver does how it works a bit lost at this point
Sent from my DROID BIONIC using XDA App
Pathsaver was for folks that updated to leaked builds that were never officially supported and put us off the OTA (over the air) update path.
Its basically a batch to push the old builds to your phone allowing you to root/permaroot and give you the files needed to run the 893 and 901 updates from stock recovery on your phone once you're back at 886, effectively putting you back on the "OTA update path", thus aptly named "pathsaver".
hth
ok that makes a bit more sense so its like updating a "official" signed ota backwards more or less that makes sense i am really new to locked bootloaders everything seems so damn complicated cause when i had my charge and my epic all i had to do is plug in usb get a .pit file flash odin and bam i was rooted with cwm recovery installed it was magic... so this is super complicated and really can't afford to brick my phone..
Hopefully someone knows this answer...
i've tried both BPS, forever root and 1-click. i've found no answer to this and if it's out there could someone please point me in the right direction?? I apologize beforehand therefore if said answer is out there. I used BPS went right to .893, right to .901. lost root. I tried the other ways (to save time I did if you need specifics i'll give them) to no avail. This is the message I get:
unable to chmod read-only file system. Screen shot attached. thanks
Gossett said:
i've tried both BPS, forever root and 1-click. i've found no answer to this and if it's out there could someone please point me in the right direction?? I apologize beforehand therefore if said answer is out there. I used BPS went right to .893, right to .901. lost root. I tried the other ways (to save time I did if you need specifics i'll give them) to no avail. This is the message I get:
unable to chmod read-only file system. Screen shot attached. thanks
Click to expand...
Click to collapse
I think you need to use the pathsaver, and then once you get to 893 apply root, and 43v3r root, then go to 901.
Bought my bionic a while back and rooted it and used safestrap to use a JB rom.
Now that JB is out for the bionic ive been trying everything i can think of to update it. I've tried unrooting, uninstalling safestrap via the app itself and multiple factory resets. I try to update and it will get to about 25% after rebooting then of course the lil droid will die and i get a software update failed message.
Is there something i missed?
Gabraham said:
Bought my bionic a while back and rooted it and used safestrap to use a JB rom.
Now that JB is out for the bionic ive been trying everything i can think of to update it. I've tried unrooting, uninstalling safestrap via the app itself and multiple factory resets. I try to update and it will get to about 25% after rebooting then of course the lil droid will die and i get a software update failed message.
Is there something i missed?
Click to expand...
Click to collapse
Follow this thread: "http://forum.xda-developers.com/showthread.php?t=2242075"
"mc_akiong" has the solution in the third post. Go and thank him for it.
pmrmx774 said:
Follow this thread: "http://forum.xda-developers.com/showthread.php?t=2242075"
"mc_akiong" has the solution in the third post. Go and thank him for it.
Click to expand...
Click to collapse
i cant seem to locate the file he is referring to. What general area of the phones files should it be in?
Gabraham said:
i cant seem to locate the file he is referring to. What general area of the phones files should it be in?
Click to expand...
Click to collapse
You need the FXZ file from Verizon. You unzip it and open the file suggested. edit out the two entries in notepad and save. Then, run RSD to apply to your phone. this hould be a US based phone.
You can get the file cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip at "http://forum.xda-developers.com/showthread.php?t=2240725"
Been having trouble getting rsd lite to recognize my phone . could these issues be related ?
Sent from my ME172V using xda app-developers app
downloaded the cdma, properly booted my phone into fastboot with RSD lite, flashed the modified cdma zip ( sans step operation lines) worked like a charm, if not a bit overly complex. thanks much