My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)
Flameninja00 said:
My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)
Click to expand...
Click to collapse
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you
flying_dutchman said:
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you
Click to expand...
Click to collapse
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X
Flameninja00 said:
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X
Click to expand...
Click to collapse
I'm having the same exact software. I uninstalled and froze a few bloatwear. Used MotoFail2Go to get my root. So what do we do now??? are you tell me we're stranded unless we beef up another 300.00 for a new device?????? Nahhh all these nerds on XDA someone's gotta have an answer....................right?
I'm glad I'm not the only one having issues, but I agree. Someone's gotta have an idea on what to do, or try next.
Sent from my DROID RAZR HD using xda app-developers app
Well I gave up. Luckily I got Verizon to send me another device
Sent from my DROID RAZR HD using xda app-developers app
same thing happened to me..and yes they gave me another device too...
Ncruze said:
Well I gave up. Luckily I got Verizon to send me another device
Click to expand...
Click to collapse
johnxpotter said:
same thing happened to me..and yes they gave me another device too...
Click to expand...
Click to collapse
I'm assuming you both were rooted via MotoFail2Go? What did you do before you sent it in to hide your root? Just unrooted and restore to factory?
Thanks everybody for your help!!!
Sent from my DROID RAZR HD using xda app-developers app
Cool did your new device come pre installed with job? If not did you have any problems upgrading to job on ur replacement device?
Sent from my DROID RAZR HD using xda app-developers app
Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.
djousma said:
Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.
Click to expand...
Click to collapse
The bloatware came back and works fine after a factory reset though.
Are you telling me I'm screwed then?
Sent from my DROID RAZR HD using xda app-developers app
No, you are not screwed. You may have to reload original ICS from FBR process. It is documented on this site. I had to do that not because the OTA failed, but because I lost root.
"UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail."
I have the Dev Edition with an unlocked Bootloader.. is this why my update is failing?
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean.
When I try to load the update my self through recovery, same thing happens, but the error shows....
assert failed:motorola.update_bl_backup()
Any one...Any one...Bueller.
rebretz000 said:
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean
Click to expand...
Click to collapse
Mine fails 1/3 of the way up the bar, but the animation is the same.
Sent from my DROID RAZR HD using xda app-developers app
Hi I am using galaxy S2 i1900g. yesterday i downloaded the jellybean update for my device OTA. when installing it said device will reboot .
After the droid loading symbol it rebooted and now its stuck where the device name "Samsung GALAXY SII" comes and its stuck here for the past 2 and a half hours .
what should i do..... should i reset the device in the middle of installation but that will curru[pt the device right?? Has the installation failed.???? please help
Related
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
mcduck$ said:
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
Click to expand...
Click to collapse
What ROM were you running? It should have disable OTA's thats why I ask.
Brian Gove said:
What ROM were you running? It should have disable OTA's thats why I ask.
Click to expand...
Click to collapse
The title says rooted stock.
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Did you try re-rooting using current methods?
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Zalithian said:
Did you try re-rooting using current methods?
Click to expand...
Click to collapse
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
mcduck$ said:
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
Click to expand...
Click to collapse
Pretty sure it will just work or fail, but I'd wait for confirmation from someone else first - better safe than sorry.
Can you supply your new Baseband Version number?
I just froze sdm 1.0. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from Land Line using pay phone
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
I535VRLG7
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
marcucci217 said:
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was going to play around with flashing different roms eventually, but after upgrading from a decrepit half working ICS flashed Droid X I was just happy to have fully working phone again. Unfortunately I was under the false impression that the jerks at Verizon would have given me the option to accept their so-called upgrade.
Didn't they already remove local search on Verizon? My phone came that way. Of course I didn't stay on stock once we were freed...
rooting with the rootdebugfs tool should still work!
I woke up to a failed update message. Ran the update again to see why it failed and it fails because it reboots into custom recovery. Rooted, unlocked, stock. Just have some apps disabled or frozen.
Can anyone point out where the in the directory the downloaded update zip would go to?
I didn't get an update message but I did check for one it was available for me. So I ticked ok and it downloaded but failed to update as expected because of the custom recovery I have in place.
But I can't find where the zip file download to.
I wanted to try and see if Chainfire's Mobile ODIN Pro would root the updated zip as it claims.
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Yes my laziness allowed verizon to update both of my SGS3 to I535VRLG7. I hope I can reroot when I get a chance later.
I was running stock root on both devices.
Sent from my SCH-I535 using xda premium
Successful OTA Flash using Mobile Odin Pro and Kept Root/Unlocked Status
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Thanks, running a backup now before I try Mobile ODIN Pro. Will update this post:
Edit: Ok, it seems I have a successful flash using Mobile ODIN Pro.
Mobile Odin Pro gave me some Warnings in advance before continuing the Flash.
1) EverRoot may need to remove Google Maps during the flash to free up some space... yadda yadda..
2) The Modem Image on your device does not match the signature check....yadda yadda..
3) 5 out of 499 system files do not match the signature checks in the OTA zip... yadda yadda..
NOTE: I disabled signature checks on both warnings before proceeding.
But you do that AT YOUR OWN RISK!!
From what I gather, Mobile Odin made its own OTA zip from the target file before flashing it
I"ve uploaded some screen shots.
IMPORTANT!
PLEASE RUN A BACK UP before attempting anything risky like this.
ALSO! and VERY IMPORTANT!!
If you are using CWM as your recovery PLEASE PLEASE PLEASE check the size of your backup before proceeding with the update.
It seems CWM is not working properly on my SGSIII because the backup file sizes were only about 22 MB's large.. and thats is SO NOT GOOD!!
I went into GooManager and Flashed TWRP over CWM and ran a backup via TWRP and checked the file size to be in the range of 2.34GB's and thats what it should be (IMO). The only thing that bugs me about both recoveries is the date is 1979-12-31.. and thats definately wrong..
Anyways, my way of checking for root after an OTA is to run Titanium Backup because it always asks for SuperUser Rights before loading.
So all is well with that and checking to see if the Bootloader on my device was still Unlocked with EZ-Unlock said it still was..
Thats all I can think for now..
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Stock rooted & it tried & failed 2x to do the update and there is nothing in /fota/
I still have root
Second attempt it booted into recovery & I just restarted as it had a fail error
The ICS OTA update keeps failing on my A2. I rooted it quite some time ago, and I don't really remember what method I used. As I recall, I initially used super one click, but it became un-rooted some months ago when they the OTA update was released that added emergency updates and a few other tweaks. I then used the first exploit available to root the phone.
I imagine that root access is the most likely culprit, so I did a factory reset; and put in blank microSD card just for good measure, but somehow, it was STILL rooted. I tried unrooting with super one click, and during the process it says
Shell rooted...false
su rooted...True
and continues to say that no matter how many times I try to unroot it. I seem to be stuck. The only other possibility is that it won't update because I'm visiting my wife's family in Canada; but it ALERTED me to the update, and it DOWNLOADS it just fine, so I would imagine that is should install it regardless. Someone help me out?
yes im a noob...please help me not to be
I tried updating and ended up haveing to wipe to the original 2.3.5 install...then update all the way back...unfortunently I think that will kill your root.....
I was having your issue now I am not and am on 4.5.1 but un-rooted till I can find a way to root it again...
hope that helps
theundecided said:
I tried updating and ended up haveing to wipe to the original 2.3.5 install...then update all the way back...unfortunently I think that will kill your root.....
I was having your issue now I am not and am on 4.5.1 but un-rooted till I can find a way to root it again...
hope that helps
Click to expand...
Click to collapse
I was able to un-root it, from what I can tell. I found the exploit I used and there was an un-root option. Root check says it's lokced down, so does super one click, but it still won't update; so I suppose it's probably just more of AT&T's crap. I guess I'll know when I get back to the states next week; I'm just impatient.
Then again, I waited this long for the official OTA, fighting back the urge to just install the leak, so I guess I'm not TOO impatient.
I just want my freaking update!
Having root will not affect being able to OTA update.
What else have you done to your phone?
Sent from my MB865 using xda app-developers app
dk-v1 said:
Having root will not affect being able to OTA update.
What else have you done to your phone?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Nothing. I've even un-rooted it. My next step is to try to locate a stock ROM and flashing instructions, roll it back and see if that helps. Can anyone point me in the direction for that.
Aaaaand now I've screwed myself up even further. Tried to flash back to 2.3.5 and it's failing at step 6/20. Guess I'll have to go dig up the 2.3.6 stock, which will put me all the way back at square 1.
Sounds like you are trying to use the unmodifed 2.3.5 FXZ. Read this. It has everything you will need to recover.
Good luck!
Yup. That was the problem with that step. I'm not sure WHAT was going on when I was on 2.3.6, but that thing did NOT want to take the update. Going down to 2.3.5, then OTA to 2.3.6 FINALLY allowed me to OTA to ICS. Thanks everyone!
Just pulled in a new update on my s3 so let's pray it's the fix for mobile data. Will post up build number when finished. Build is I535VRBMF1 android 4.1.2 and was a pretty small update.
Is there multiwindow?
Sent from my SCH-I535 using xda app-developers app
Oh good.. That sounds like a new update. Hopefully that means InvisibleK will package a new AIO with the new modem/rpm/sbls for us.
Sent from my SCH-I535 using xda app-developers app
Multi Window is still there.
Currently not being productive on my S3.
---------- Post added at 12:23 AM ---------- Previous post was at 12:18 AM ----------
Build number I535VRBMF1
Currently not being productive on my S3.
http://www.droid-life.com/2013/06/1...hopefully-this-addresses-connectivity-issues/
Sent from my SCH-I535 using Tapatalk 2
Can anyone post the update file?
Sent from my SCH-I535 using xda app-developers app
bricked my phone
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Chadashcroft22 said:
...and was a pretty small update.
Click to expand...
Click to collapse
How small ? The previous update that they pulled was just under 130mb as I recall. This one should be very close to the same size unless it's a firmware update only and the "premium suite" will come later.
jdrama12 said:
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Click to expand...
Click to collapse
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
DigitalMD said:
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
Click to expand...
Click to collapse
So after trying about 5 times my phone booted back up and is working. The update did not go through but my phone is working as it was before. I dont know why the recovery wouldnt boot at first unless it was the update blocking it for a few minutes.
Might have made the rookie mistake since I didnt do the temp un-root with voodoo, but I was trying to be innovative and see if it worked with out it like it did with the MD3 OTA.
Thanks for everyones help on here, teaching a noob like me new tricks.
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
rsswga said:
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
Click to expand...
Click to collapse
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Updated: I535VRBMF1
I can actually send text messages again...! Cant wait to test 4G in areas it was disabled with the mb3 update.
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
jdrama12 said:
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Click to expand...
Click to collapse
rsswga said:
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
Click to expand...
Click to collapse
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Any way I can remove twrp so I can take the update?
Sent from my SCH-I535 using xda app-developers app
jdrama12 said:
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Click to expand...
Click to collapse
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
something stSettem
kidqwik said:
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
Click to expand...
Click to collapse
Glad to hear that method worked for you. I just tried it again and I get to right after it shuts off and get past the Samsung screen with RECOVERY in the top left in blue, to the yellow triangle saying "you have unauthorized VZW software...turn off device and take to store..." with SECURE:KERNEL in red in the top left...i think thats what it says.
Guessing flash method is all that will work for me, owell.
Thanks again.
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
rsswga said:
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
Click to expand...
Click to collapse
Thanks, just not sure how it got locked on me unless MD3 did that. I will try that later when I am not at work though.
Okay to make this easier to understand Ill start from the beginning. I rooted my phone on june 20th of this year. Everything went smooth. I did a backup of my stock system although I didnt load any ROMs or unlock my bootloader. I tried updating to 9.18.79 and I get about 1/4 of the way through, maybe a 1/3 and it freezes, follwed by the dead droid icon and a reboot. I tried temporarily unrooting my device to install the update and I had the same issue. Then I unrooted my phone and delted the superuser backup and once again, the update failed. Ive tried to do a stock recovery from the boot menu only to get the dead droid icon. One of the other things I noticed is that my backup assistan icon is missing all of a sudden (maybe it was removed as an app Icon like the navigation, I dont know) but I still have backup assistant plus in my apps when I go to system settings. My question at this point would be how do I get this update to fully install? Do I necesarily need the update? Will it hurt jus having 9.16? Is my phone incapable of being saved? Before I get bullied about creating a thread thats already adressed I havent seen anyone in the same situation that Im in. Any help is greatly appreciated! Thanks.
If you update you won't be able to unlock your bootloader. So it's not really worth it. Nothing major in the update. If you insist flash the stock firmware back on your phone.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
If you update you won't be able to unlock your bootloader. So it's not really worth it. Nothing major in the update. If you insist flash the stock firmware back on your phone.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I read you can't unlock the bootloader on 9.16 anyway with verizon. But alright. How could I flash the stock firmware back on? Will I be able to get updates in the future like 4.2 if we ever get it? And now Im trying to root again, In motochopper I dont get the option to run.bat file. It just says run, when I click on it and hit enter It says daemon is running. On my phone it isnt saying I have root at all though.
Ok so heres my first question?........... Is there any possible way of gaining root access through linux for my android ? ....Like running certain commands to do so......I know u have to change permissions and make changes to the android file system......And was wondering since linux uses root in terminals and so on and so forth would it work to access root in linux and maybe use a file manager to open your android system files in linux to make these changes so u may root. .. Instead of waiting for a DEV to create a method or script that will work ... Isnt there a way we can gain this back without waiting for an actual script to release . I rely on my root for a vast majority of my apps and i am lost without it . I know it may be more complex and diffucult for some people but to gain root access back this way ... But it would be great.
I have a working linux set up on my comp already with working adb /sdk installed ..... If anybody can help me with rooting my phone it would be very much appreciated. Im not new to this at all im very familiar with linux and how to use it. i basically need help with the rooting process and what to do when it comes to that.
I do not have an unlocked bootloader if that makes any difference.
Took 9.30.1 OTA and lost root.
As far as i know there is no script/method to root for the new OTA 9.30.1 update.
Tryed rooting already with Linux but my file system wont allow anything to be written to it.. Its Read Only File System. I think it has to be Read/Write
I really hope there is a root script/method released soon if this way isnt possible
Any help would be much appreciated. Thank you
No. Unless an exploit is found, you are out of luck.
Sent from my Droid RAZR HD under an Eclipse.
iBolski said:
No. Unless an exploit is found, you are out of luck.
Sent from my Droid RAZR HD under an Eclipse.
Click to expand...
Click to collapse
Do you have any idea what the progress lioks like for an exploit coming out soon for this update?
mnkurk1989 said:
Do you have any idea what the progress lioks like for an exploit coming out soon for this update?
Click to expand...
Click to collapse
I doubt there will be another exploit. This phone is a year old now and most devs are focusing on custom ROMs.
mnkurk1989 said:
Do you have any idea what the progress lioks like for an exploit coming out soon for this update?
Click to expand...
Click to collapse
Mostly likely none. Because at this point 95% of people know to protect root before taking an ota. Or just don't take it.
Sent from my PACMAN MATRIX HD MAXX
My phone is the not-unlockable one and locked.
I happend to click yes when this update question came. After realizing what was happening, I set my phone to flight mode, and the update downloading is now paused. Is there anyway to cancel this downloading/update process?
I have installed safestrape and backup my stock ROM before this. The worst is that I restore the backup and the update question will be prompted again, right?
Or is there other way to stop the update downloading in progress?
Another question, if root is lost through the OTA update, can I restore the backup through Safestrape and get root again? Or is everything gone?
xknobi said:
My phone is the not-unlockable one and locked.
I happend to click yes when this update question came. After realizing what was happening, I set my phone to flight mode, and the update downloading is now paused. Is there anyway to cancel this downloading/update process?
I have installed safestrape and backup my stock ROM before this. The worst is that I restore the backup and the update question will be prompted again, right?
Or is there other way to stop the update downloading in progress?
Another question, if root is lost through the OTA update, can I restore the backup through Safestrape and get root again? Or is everything gone?
Click to expand...
Click to collapse
Once root is lost after the ota has been fully applied, the backup will do you no good as there is a new kernel applied.
As for it being paused, I believe you should be okay. Just because you started the download doesn't mean it's been applied. Freeze the updater apk and reboot. I believe that will cancel the download and with the frozen updater, you won't get bothered again.
You could apply the update if you save root with voodoo root keep but if you ever have to reimage your phone, you will lose root permanently. I'd just hold off and wait and see if an exploit is ever found.
Sent from my Nexus 7 using Tapatalk 4
iBolski said:
Once root is lost after the ota has been fully applied, the backup will do you no good as there is a new kernel applied.
As for it being paused, I believe you should be okay. Just because you started the download doesn't mean it's been applied. Freeze the updater apk and reboot. I believe that will cancel the download and with the frozen updater, you won't get bothered again.
You could apply the update if you save root with voodoo root keep but if you ever have to reimage your phone, you will lose root permanently. I'd just hold off and wait and see if an exploit is ever found.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the info. I have just restored the backup stock rom and all is good. Installed Root Keeper anyway.
Anyone working on a root exploit for 9.30.1
So is anyone working on an exploit to root this update?? I just don't want to have to keep SBF'ing my Razr Maxx HD back to older versions and reconfiguring all my stuff. For what ever reason, I could not get OTA's. I was rooted(motochopper) and used superuser and voodoo. Protected my root, temp unrooted, downloaded the update, but then it would fail on install. I even tried flashing back to the stock recovery and it failed. So just to see what the 9.30 did, I installed it through Droid Razr HD Utility 1.34...of course I lost root, can't put a custom recovery on it, but my phone seems to run pretty good for a stock rom. So, I'm just wondering.
deeje00 said:
Mostly likely none. Because at this point 95% of people know to protect root before taking an ota. Or just don't take it.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I had root with the 9.30.1 update. I backed up root with OTA RootKeeper but my phone was acting up so i factory reset it and all went to hell...!!! I protected everything and backed up hoping that would do the trick but unfortunately it didnt save the root like it should have now i sit I regret ever resetting it thats for sure. It was risky on my part playing with the reset option knowing there was no exploit out yet and i payed the price
richardjrdeal said:
So is anyone working on an exploit to root this update?? I just don't want to have to keep SBF'ing my Razr Maxx HD back to older versions and reconfiguring all my stuff. For what ever reason, I could not get OTA's. I was rooted(motochopper) and used superuser and voodoo. Protected my root, temp unrooted, downloaded the update, but then it would fail on install. I even tried flashing back to the stock recovery and it failed. So just to see what the 9.30 did, I installed it through Droid Razr HD Utility 1.34...of course I lost root, can't put a custom recovery on it, but my phone seems to run pretty good for a stock rom. So, I'm just wondering.
Click to expand...
Click to collapse
I have a few guys looking into it for me im hoping to hear back soon with some good news
richardjrdeal said:
So is anyone working on an exploit to root this update?? I just don't want to have to keep SBF'ing my Razr Maxx HD back to older versions and reconfiguring all my stuff. For what ever reason, I could not get OTA's. I was rooted(motochopper) and used superuser and voodoo. Protected my root, temp unrooted, downloaded the update, but then it would fail on install. I even tried flashing back to the stock recovery and it failed. So just to see what the 9.30 did, I installed it through Droid Razr HD Utility 1.34...of course I lost root, can't put a custom recovery on it, but my phone seems to run pretty good for a stock rom. So, I'm just wondering.
Click to expand...
Click to collapse
im assuming your bootloader is unlocked?
if so, search for a flash-able zip of SU. you can root any build, problem solved.
I know our RAZR HD's are old, but there's nothing better out there. At this point, I'm willing to pay cash money for anyone able to find a new root exploit for this dumb 9.30 update. I took all the precautionary steps and have an unlocked phone, yet for some reason as soon as the update applied I lost root. It happened during the last ota and I got lucky that the warranty covered me. Not gonna happen now with a unlocked booty. So once again, please find a root exploit and I'll pay you. I dont want to get rid of my razr. Thanks yall
razrretard said:
I know our RAZR HD's are old, but there's nothing better out there. At this point, I'm willing to pay cash money for anyone able to find a new root exploit for this dumb 9.30 update. I took all the precautionary steps and have an unlocked phone, yet for some reason as soon as the update applied I lost root. It happened during the last ota and I got lucky that the warranty covered me. Not gonna happen now with a unlocked booty. So once again, please find a root exploit and I'll pay you. I dont want to get rid of my razr. Thanks yall
Click to expand...
Click to collapse
there is no need for a new exploit if you have an unlocked bootloader.
search for a flash-able SU zip or search razr forum for the rooting unlocked bootloader thread.
problem solved, cash payments preferred
bweN diorD said:
there is no need for a new exploit if you have an unlocked bootloader.
search for a flash-able SU zip or search razr forum for the rooting unlocked bootloader thread.
problem solved, cash payments preferred
Click to expand...
Click to collapse
I've tried every su time there is in here and other sites. They fail every time. I've tried recovery through twrp and cwm and they both fail. As a matter of fact since I took the update neither one of those will work now either. I'll keep trying new stuff until I succeed or brick this phone. All other devices that are currently available can't hold a flame to the RAZR.
razrretard said:
I've tried every su time there is in here and other sites. They fail every time. I've tried recovery through twrp and cwm and they both fail. As a matter of fact since I took the update neither one of those will work now either. I'll keep trying new stuff until I succeed or brick this phone. All other devices that are currently available can't hold a flame to the RAZR.
Click to expand...
Click to collapse
Then are you sure you have an unlocked boot loader? If not, then you are hosed. We're just going by the fact that you posted " Not gonna happen now with a unlocked booty".
iBolski said:
Then are you sure you have an unlocked boot loader? If not, then you are hosed. We're just going by the fact that you posted " Not gonna happen now with a unlocked booty".
Click to expand...
Click to collapse
I get the "warning, boot loader unlocked" message every time I power up. Used *#*#4636#*#* and checked that device shows root. I took all the precautionary steps before installing the ota, and I was having problems that both 9.20 and 9.30 fixed. Was running eclipse as a ROM before all this went screwy lewy
tried using motochopper (no winning)
All boxers are checked, however when I get the true ending to check my SU, it gives me some bogus message about needing to update SU, however it says I have an HTC device, I'm very confused on this, and don't understand what it is even referring too.
Anyone know what I'm reading about here?
razrretard said:
I get the "warning, boot loader unlocked" message every time I power up. Used *#*#4636#*#* and checked that device shows root. I took all the precautionary steps before installing the ota, and I was having problems that both 9.20 and 9.30 fixed. Was running eclipse as a ROM before all this went screwy lewy
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php?/topic/20473-[How-To]UNIVERSAL-Recovery-and-Root-ANY-{Unlocked-Bootloader-XT926-&-XT907}-Easy! I have used this twice after I've taken an update from vzw... If if your phones not being recognized it could be your drivers or the cable
Sent from my XT926 using Tapatalk