Those of us who flashed rootboot.img to install a rooted/insecure boot image were unable to update via the 2.3.1 OTA (Status 7 Error). A few different solutions have been posted. Here's one which worked for me, courtesy of momohammed20 and Luxferro:
Step 1: Restore the "2010-12-22.21.06.07" Nandroid backup which momohammed20 shared in this thread. That wipes your phone completely and gives you stock 2.3.1 without root.
Step 2: Follow the steps provided by Luxferro in this post. That gets you back root along with ClockworkMod Recovery.
Worked perfectly for me. Again, the solution is already out there in a few other threads, but I thought this deserved its own thread since a lot of folks have been stuck with the Status 7 error when trying to update.
Thanks again to momohammed20 and Luxferro!
Umm if we have 2.3 we can't nandroid a 2.3.1 backup. Ull get an error every time.
Sent from my Nexus S using XDA App
I followed these steps, and they worked nicely with no errors whatsoever. Others have done the same.
U were runninr2.3 rooted and then nandroid the 2.3.1 and u didn't get a MD5 error? Hard to beloved BC I've tried 5 times. Can anyone else try this out n let us know? ?
Sent from my Nexus S using XDA App
EDIT: just got it to work.. I re-downloaded it and it loaded. Seems the nandroid I dl from that thread the first time got renamed n it had a "(" in it, and recovery couldn't read the file...
Thanks alot tho, u were right!!
Sent from my Nexus One using XDA App
So will this allow the future flashing of OTAs without issue?
i also want to know if this will allow for future updates. i dont want to be reflashing my phone for every minor update.
Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Oh btw there's no root, in case u didn't understand what Stock 2.3.1 meant.
Sent from my Nexus S using XDA App
petep86 said:
Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
From what I understand, the problem lies in the boot.img and not ClockworkMod.
TheBiles said:
From what I understand, the problem lies in the boot.img and not ClockworkMod.
Click to expand...
Click to collapse
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App
petep86 said:
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
"Status 7" is the result of a rooted boot.img. It has nothing to do with ClockworkMod Recovery.
TheBiles said:
So will this allow the future flashing of OTAs without issue?
Click to expand...
Click to collapse
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.
Wish this was posted this morning before i gave up
between some people getting it to work and other not working. People posting methods with stock boot.img but come to find out it wont work with rootboot....ect
Then realizing some people are on one root method while other used another...too confusing and i gave up after countless tries and gave and flashed modaco GRH78 r2 and glad i did because its pretty good..
IMO guys if this is going to require to you wipe your data save your self from headaches and just flash modaco GRH78 r2 with supercurio's EXT4 tweak it also rooted has new market and other fun stuff
demo, that's a good point. I'm using the r2 MoDaCo ROM now - it seems very good!
Amin Sabet said:
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.
Click to expand...
Click to collapse
Nope, that is false. I had initially used superboot to root my phone when I first got it (w/ the pre-rooted modified boot.img). And I still got the prompt for the update. It will just give you a MD5 mismatch error when you accept the prompt and try to update.
deleted (accidental double post)
Luxferro, I think you misunderstood what I wrote. I too was rooted and got the prompt for this particular OTA, and some folks who were rooted (without root boot) were able to apply the OTA without an error. What I was trying to say was that the only way to be sure that they can receive and apply all future OTA updates would be to revert to stock (or have a means to revert to stock).
the status 7 error is a result of the patch process not finding a proper checksum for the things its patching if you have deleted system/framework apk's/odex's de-odexd the system/framework themed the system/framework changed the kernel this will cause status 7 error and will give you a hint on where the issue lies i.e. it will say somthing about calculator not match if you deleted it and error code 7
Related
Hi Guys,
I am a newbie to all things root etc.,but wanting to start I have purchased a 2nd hand Nexus One. However it seems to have a different Build number than most of you. Here are the specs: Android version
2.2.1
Baseband version
32.50.00.32U_5.12.00.08
Kernel version
2.6.32.9-Connect-UTB-20101020-27240-gbca5320
Build number
UTB-ROM 1.1
Could some one please guide me to revert my phone to a complete up to date Stock phone?
Any help much appreciated!
Anyone?
I Haven't just posted without spending hours on reposts and wiki, even asked original member who devised UTB-1.1 but no replies yet.I have tried instructions on wiki to revert to FRG33,but I get an error! Have tried other members advice posts, Rusty being one,still get an error. On the Recovery mode I notice I have Clockwork there,is this the problem?
Stuck on UTB-1.1 just want original stock phone to receive OTA updates etc.,
Which hboot version do you have?
Sent from my Nexus One using XDA App
Hi it is 0.35.0017
Ahhhh, well that's why the passimg method won't work.
I don't know of anyway, other than rooting, or unlocking the bootloader. You may already be rooted, though...
Sent from my Nexus One using XDA App
Hi, Thanks for taking the time to reply, so, I don't know either if it is rooted, if I root will I be able to use passimg? don't really want to unlock the bootloader unless there is no other way.
To see if you're rooted, download a flashlight app that requires root, and see if it works...
You cannot use the passimg method, sorry.
Unlocking bootloader is the easiest, but I can respect you not wanting to do that.
Let me know if you're rooted...
Sent from my Nexus One using XDA App
Well, since the FRG33 PASSIMG has HBOOT 0.35.0017 in it, how come you cannot reflash it? I also have that HBOOT (at least I think so, I used the FRG33 PASSIMG then OTA'd to FRG83D) and I can reflash that anytime I want.
I tried yesterday night... I didn't actually reflash but I forgot I had the file there, launched HBOOT and it checked and offered me to flash it. So by using a FRG33 PASSIMG I guess it should work.
You can try it, but like the OP said, you get an error...
Sent from my Nexus One using XDA App
G0belet you were right! danger-rat I did get error x 3 , but whilst searching to see if my n1 is rooted, I saw G0belet's post and went back to my passimg file. I am an idiot! I copied the instructions for FRG33 from wiki exactly. Where I went wrong was renaming the passimg file passimg.zip, it is already a zip file,so my phone sd card read passimg.zip.zip! Argggh! after all those hours and your help I am now on Build FRG33.
Thank you G0belet and danger-rat for spending time to help.Guess you can tell I am new to this. Now all I need to do is update to FRG83 somehow?
Many Thanks again guys...
Update: After I finished typing all this, my nexus updated ota to FRG83D!
so all fixed I think..
Instructions in the wiki to upgrade from FRG33 to FRG83...
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
You're welcome
Just connect your N1 to your Wi-Fi or cellular network. You will get a prompt to update very soon. Check Settings > About this phone > Updates (or something like this) to see if it's loading. If it's not, you can attempt tapping Phone, and typing *#*#2432546#*#* to manually trigger the update verification. That's the easy and official way to update. It will directly load stock FRG83D on your phone.
Thanks it's on FRG83D now after OTA update, Brilliant!
All I would like to do is get my (not unlocked, but un-rooted) back to a stock recovery (I think?) and a stock OS. I want to be able to do updates OTA as they arrive on my phone, and the only reason I rooted in the first place was to get Gingerbread from CM7 and they didn't work. It got stuck in a endless boot loop and once I finally got a nightly working, it wasn't even worth it to me anymore.
I have used this thread: http://forum.xda-developers.com/showthread.php?t=614850
and done hours and days of research to try and solve my problem and get me to where I would like to be. I'd like to think I am not a noob to Android but clearly I am and I can't achieve 100% of my goal.
Where I am currently: Stock image, not sure of recovery, unrooted, bootloader unlocked.
Where I would like to be: Stock everything (I know I cannot relock the bootloader) just like when I bought it, so I can patiently wait for Gingerbread to push OTA whenever Google solves the issues.
Thank you and I apologize.
That guide has pretty much all the information you need. Flashing the stock HTC images and stock recovery will enable you to get OTA updates.
Read my signature, find "Unroot/restore" guide, look for the part for unlocked bootloaders.
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
rynstphn said:
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
Click to expand...
Click to collapse
You didn't explain where you got stuck, what you attempted, what went wrong and couldn't even state your recovery image. The guide you linked to is there for a reason, it works, however onlyif you follow it correctly without jumping in with 2 feet. If in future you require more precise help perhaps you should give precise information.
Perhaps the OP has encountered some of the issues i've posted about HERE?
Don't mean to kind of hi-jack this thread...
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
CTR01 said:
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
Click to expand...
Click to collapse
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Thanks!
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Awesome! Thanks for the reply and details.
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
efrant said:
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
DirkGently1 said:
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
Click to expand...
Click to collapse
Uh, sorry, but NO. What he says in that post is incorrect.
I have been using a custom recovery since I first got my Nexus One, and I have received EVERY OTA update.
EDIT: But hey, don't take my word for it. Try it yourself.
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
danger-rat said:
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
So, in my setup (which is a rooted-but-otherwise-stock ROM and Amon_RA's 1.9.0 recovery), I receive OTA updates, and they auto-install with no problem (as Amon_RA's 1.9 recovery does not verify signatures). Note, however, that every OTA update also does two things: 1) it removes the permissions on the su binary (which obviously disables root access), and 2) it copies two files (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) back onto the system partition, which will flash the stock recovery back to your devices as soon as you reboot. You will need to root first (either manually or by flashing ChainsDD su update before you reboot, or use SOC), then delete the two files, then reflash the custom recovery you want.
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Jack_R1 said:
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Click to expand...
Click to collapse
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
efrant said:
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
Click to expand...
Click to collapse
Yep, that's correct.
Cool
thanks for all the other responses to my question! I will look into this further when i have more time
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
DirkGently1 said:
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
Click to expand...
Click to collapse
If you read post 14, you will see that you CAN install them with a custom recovery...
Rooted and running CM 6.1.0, have backed up 1.21 firmware, what is the easiest way to unroot and return to stock? (remove CWM also). Need to send the phone in for button repair. If I apply OTA update on the 1.21 firmware (updating to 2.2) will it wipe everything clean?
Thanks in advance
DrBarrell said:
Rooted and running CM 6.1.0, have backed up 1.21 firmware, what is the easiest way to unroot and return to stock? (remove CWM also). Need to send the phone in for button repair. If I apply OTA update on the 1.21 firmware (updating to 2.2) will it wipe everything clean?
Thanks in advance
Click to expand...
Click to collapse
uhh im not too sure anymore but i think the best way to do it would be to apply an older stock rooted rom and then plug your phone into a comp with htc sync, and then do the update thing thats it got on there.. thats the way i was told a while back but im not sure if theres an easier/better way to do it. probably should wait till someone else comments before you go do anything but yeah youre meant to do something like that ^ i believe..
From my own experience, the technicians doesn't know if its stock, cm or what. They fix the problem and that's it.
I've sent my device twice with cm on it and there was no problem
Sent from my Legend
Thanks for the replies although I would be happy to send it in with CM and whatnot, as it is not mine I do not even want to take the risk. Can anyone confirm that installing the latest vodafone firmware will restore phone to stock?
basically run a htc update on it (if you haven't S-OFFed then 2.1 is fine)
Search isn't working now so I can't link you, but either way find an offical RUU and it will do everything for you. Remember if you do update it to froyo (official) it is a difference process to root again (but still possible)
Or else.. search the forum.. I made a thread called "easiest way to unroot".. or something like that.. Always use the SEARCH feature before asking questions..
Sent from my Legend using XDA App
Or ask anyway, and feel the loving response from the XDA forums
Ol' whitetigerdk's thread on unrooting is a good one though, check it out buddy!
TheGrammarFreak said:
Or ask anyway, and feel the loving response from the XDA forums
Ol' whitetigerdk's thread on unrooting is a good one though, check it out buddy!
Click to expand...
Click to collapse
Old???? Okay I admit.. did turn 34 on the 17th this month.. but Old¿?? ;-P
Sent from my Legend using XDA App
whitetigerdk said:
Old???? Okay I admit.. did turn 34 on the 17th this month.. but Old¿?? ;-P
Sent from my Legend using XDA App
Click to expand...
Click to collapse
It's time for the younglings my friend
method 1 (preferred)
you can leave the LEGEIMG.zip to the root of your goldcard and go to boot loader and let it load and you confirm the update. i suggest using the same one that you use for the downgrade.
if, you don't have it download Legend rooting tools, extract the zip. locate testimage.zip... copy it to your goldcard and rename it to LEGEIMG.zip. (make sure you dont ended up renaming it to LEGEIMG.zip.zip if you know what i mean lol)
method 2 (goldcard not needed)
For the past few days i've been playing around with official RUU. and heres what i've done so far on testing the official RUUs from HTC (link from stickies)... it'll turn your Legend to stock.... even if your on CM7 or any other roms....
But... if you have an HBOOT of less than 1.00... be warn. RUU with Froyo will update it and there's no known method to downgrade. unless you dont care about it and thinks its about time you update it and you have intention on doing the S-OFF...
After the initial jubilation of finally getting Gingerbread on my stock Nexus one, I have come to the conclusion that its a little half baked and setting aside all the little annoyances, the current battery life bug that seems to be affecting some people (myself included) is just terrible.
So my question is, how to I get back to stock 2.2 (or 2.2.2) now that I have 2.3.3 installed.
I don't want to root, or open the boot loader or do anything to invalidate the warranty. Is there a way ?
Thanks, and sorry if this has already been covered somewhere else (could not find it)
shimsim said:
...I don't want to root, or open the boot loader or do anything to invalidate the warranty. Is there a way ?...
Click to expand...
Click to collapse
No.
10chars
shimsim said:
After the initial jubilation of finally getting Gingerbread on my stock Nexus one, I have come to the conclusion that its a little half baked and setting aside all the little annoyances, the current battery life bug that seems to be affecting some people (myself included) is just terrible.
So my question is, how to I get back to stock 2.2 (or 2.2.2) now that I have 2.3.3 installed.
I don't want to root, or open the boot loader or do anything to invalidate the warranty. Is there a way ?
Thanks, and sorry if this has already been covered somewhere else (could not find it)
Click to expand...
Click to collapse
http://www.google.com/support/forum/p/android/thread?tid=3ee1ccfdaffc5881&hl=en
Worked for lots of people, don't know if it works for 2.3, it worked for 2.2.
So.. ya might just wanna keep an open mind.
Anyway, some of the links on the page are dead, you might need to dig around for what you need.
Google is your friend
http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
I tried this also (just to see for myself, instead of listening to the rumors), and can confirm it works.
The only comment I would make is that the filename is NOT case sensitive (I got it to work as PASSIMG.zip, passimg.zip, and also combinations like PassImG.zip)
Sent from my Nexus One using XDA App
Passimg method is working? Nice find! I imagine this will be of great help to many people.
Thanks for all the suggestions and help, I will give it a go.
In terms of the most recent version that I can go back to, I assume it has to be a manufacturer shipment ROM or full system image.
The latest release on shipped roms is FRG33 http shipped-roms.com/index.php?category=android&model=Passion%20(Nexus%20One
I found on the HTC developers site (http developer.htc.com/) FRG83 but the link seems to be broken http dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
Assuming I can find a copy of FRG83 system image, am I correct in assuming I can also rename this to passimg.zip and downgrade or does it have to be the FRG33 manufacture shipped rom?
ps, sorry i cant post url links hence the http
If it's a shipped image, then yes.
If you look in the zip, and see a bunch of image files, instead of a folder structure, then it will probably work...
Let me know if you find FRG83.
I know someone who would LOVE to find it!
Sent from my Nexus One using XDA App
danger-rat said:
If it's a shipped image, then yes.
If you look in the zip, and see a bunch of image files, instead of a folder structure, then it will probably work...
Let me know if you find FRG83.
I know someone who would LOVE to find it!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks!!!
Hi,
I know this question may sound stupid but I have this doubt and I would like to understand better one thing:
Can someone please explain me why it's not possible to restore 2.2 from 2.3.3 using directly a nandroid restore skipping the PASSIMG.zip part?
I'm new to this and I'm still learning some things, but if the nandroid is a backup of the entire system, why can't I just wipe out everything and restore from that file?
Thank you so much for your help!
If you have nandroid - great.
If you flashed stock image - you don't have it anymore, because stock image overwrites your custom recovery, and without unlocked bootloader or option to root, there is no way to restore it.
Thank you so much for the reply
So, just to be sure: since my bootloader is unlocked this means that if I wipe everything, then I can flash a custom recovery and then restore from a nandroid backup without having to flash first another stock ROM and root again, right?
That is correct.
However, keep in mind that rebooting your phone when you soil have the stock ROM will cause the stock recovery to be restored, so as soon as you install your custom recovery, you need to boot into recovery without rebooting the phone...
Sent from my Nexus One using XDA App
efrant said:
http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
Click to expand...
Click to collapse
The dowload link include in the link above for the ROM is not working. I am getting this error message: "Unable to open shipped/Passion (Nexus One/"
efrant: Can you please update the link?
Thank you!
jay_supreme said:
The dowload link include in the link above for the ROM is not working. I am getting this error message: "Unable to open shipped/Passion (Nexus One/"
efrant: Can you please update the link?
Thank you!
Click to expand...
Click to collapse
Updated...
I think I found a copy of FRG83 here:
androidpit.de/de/android/forum/thread/407726/ROMs-Kernels-Radios-fuer-das-Nexus-One
p.s. sorry, i still cant post url links ..... so add the w w w
I've been following the guide here to flash Jelly Bean onto my Atrix HD, so I could next flash the Batakang ROM as the guide recommends. I got Jelly Bean onto the device, but after I install Safestrap and try to open it, it immediately displays "Unforuntately, Safestrap has stopped working" and closes itself. I think I installed the right version (the one for Razr HD, tried both 3.04 and 3.05. I think it works with the Atrix HD as well). Voodoo OTA shows that all checkboxes under Status are checked, so I don't think it's a root issue.
I did a search for Safestrap and I didn't really see anything related to my problem. I'm kinda at a loss here. Maybe I got a bad flash and need to redo everything?
redphazon said:
I've been following the guide here to flash Jelly Bean onto my Atrix HD, so I could next flash the Batakang ROM as the guide recommends. I got Jelly Bean onto the device, but after I install Safestrap and try to open it, it immediately displays "Unforuntately, Safestrap has stopped working" and closes itself. I think I installed the right version (the one for Razr HD, tried both 3.04 and 3.05. I think it works with the Atrix HD as well). Voodoo OTA shows that all checkboxes under Status are checked, so I don't think it's a root issue.
I did a search for Safestrap and I didn't really see anything related to my problem. I'm kinda at a loss here. Maybe I got a bad flash and need to redo everything?
Click to expand...
Click to collapse
Try downloading safe strap again maybe you had a bad download.
Sent from my MotoAHD
Update superuser and binary
Sent from my MB886 using Tapatalk 2
Youngunn2008 said:
Try downloading safe strap again maybe you had a bad download.
Sent from my MotoAHD
Click to expand...
Click to collapse
SirHoover2010 said:
Update superuser and binary
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Updating Superuser and binary fixed it. I thought I had done that already, so I didn't think to try that. I feel kinda stupid now.
Thanks to both of you for your help.
Don't I did the same thing and got kinda mad for about 10 min till I checked that lol
Sent from my MB886 using Tapatalk 2
lost root
Had same problem and tried to up date Su Binary and lost root. Need Help. I am on ota 4.1.1 it said su has stopped and have not had root since. Any ideas?
fullpozzy said:
Had same problem and tried to up date Su Binary and lost root. Need Help. I am on ota 4.1.1 it said su has stopped and have not had root since. Any ideas?
Click to expand...
Click to collapse
You have voodoo ota root keeper with a backup of su? I'd restore root with that then make sure superuser is updated and move it to system/apps then update binary
Sent from my MotoAHD
Tried using voodoo and no success. Voodoo shows phone as rooted and have a back up of root, but doesn't have root access and no way of accessing back up of root. I can hit temp unroot but nothing happens. Any other suggestions?
I'm having this same issue with my Galaxy S4, build NC5. I rooted using Towelroot v3, then installed Safestrap (JFLTEVZW-3.71). Everything seemed to be working fine, I installed the recovery, rebooted, and now I can't open the app. This is frustrating because I decided I would rather use a different recovery, and want to remove Safestrap. I can get into recovery on boot, but no matter what I do the app won't open. SuperSU/binary seems to be up to date. Any ideas?
ahouse3733 said:
I'm having this same issue with my Galaxy S4, build NC5. I rooted using Towelroot v3, then installed Safestrap (JFLTEVZW-3.71). Everything seemed to be working fine, I installed the recovery, rebooted, and now I can't open the app. This is frustrating because I decided I would rather use a different recovery, and want to remove Safestrap. I can get into recovery on boot, but no matter what I do the app won't open. SuperSU/binary seems to be up to date. Any ideas?
Click to expand...
Click to collapse
I doubt you're having the same issue, because you have a completely different phone than the one contained within this thread. You posted your question in the forum for the Motorola Atrix HD.
Seeing as this is your first post, I will simply refer you to here: http://forum.xda-developers.com/galaxy-s4-verizon
Good luck over there.
quasihellfish said:
I doubt you're having the same issue, because you have a completely different phone than the one contained within this thread. You posted your question in the forum for the Motorola Atrix HD.
Seeing as this is your first post, I will simply refer you to here: http://forum.xda-developers.com/galaxy-s4-verizon
Good luck over there.
Click to expand...
Click to collapse
Sorry, I didn't think this sounded like a device-specific issue, and this was the only thread anywhere that seemed to address it. But anyway thanks for showing me the ropes . I ended up fixing it by changing SELinux from enforcing to permissive (I had done this to install Safestrap, but then it reverted back). Problem solved!
ahouse3733 said:
Sorry, I didn't think this sounded like a device-specific issue, and this was the only thread anywhere that seemed to address it.
Click to expand...
Click to collapse
Right, but you also should have noticed that the last post was back in December 2012. That's because the Atrix HD later had its bootloader unlocked, thus negating the need for anything Safestrap related on this phone. So if you really needed help, it's unlikely that anyone here would be able to help you, because no one is using Safestrap anymore. Which is why I was trying to steer you towards someone that could actually help.
Just another reason to use the correct forum. Otherwise, glad you figured it out.
I know this may be the wrong section.. But do u by any chance still have the safestrap apk because all of the downloads are bad now and I can't find one anywhere on the internet . I really need it.. My computer quit working so I can't unlock the bootloader right now.. I just need an easy recovery because I want to use xposed but I need recovery in case anything goes wrong. Any help will be appreciated