This has been observed in at least one post, buried deep within another thread, but I thought it is important enough to have its own thread.
The latest JH7 OTA update seems to remove the file containing the unlock code for the Captivate. I unlocked my phone a couple of weeks ago, and after receiving the upgrade I verified that the phone is still unlocked. However, the SGS Unlock app no longer finds the code. Presumably, other PC/Mac-basede unlock techniques will be affected, as they look for the unlock code in the same file.
Anybody else can confirm this? In a word (two, really), what now? I was about to buy another Captivate for my wife, but the only reason she was willing to get it instead of the iPhone 4 was the possibility to unlock it (we travel to Europe twice a year).
If I manually peek at the bml3 or nv_data files, I still see my unlock code after JH7. I haven't used any apps to unlock, but it sounds like they just need an update if they are failing.
Well, if you bought the phone today, it wouldn't have the JH7 update, I would presume. So, you can run the unlocker to get the code. It sounds like, though I cannot confirm because the update failed on my phone, that it just deletes a file with a number in it. If that's the case, it shouldn't be able to undo any existing unlocks, and there's no time limit once you have the code.
Then you better buy one now and extract the unlock code before you upgrade. It typically takes AT&T a few months to sell phones with new firmware.
Even though new firm ware makes current unlock method useless, it won't chang your unlock code.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok, so maybe the SGS unlock app fails but could be fixed in the future, or perhaps one of the other methods still works...
Sent from my SAMSUNG-SGH-I897 using XDA App
One question: are you rooted? I tried copying the nv_... file to the sd card using adb, but got a "permission denied" error.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
aloant said:
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
Click to expand...
Click to collapse
OK, so this is very good news.
To clarify (here's the noob asking...): rooting does *not* affect your ability to get the update, right? If all rooting does is install su & friends (and uninstall removes them), there should be no adverse consequences at all, especially if you unroot prior to getting the update. I'm just worried about the reports of updates failing (everything went smoothly for me, but I'm 100% stock and not rooted). Thanks!
MarcianoS said:
To clarify (here's the noob asking...): rooting does *not* affect your ability to get the update, right? If all rooting does is install su & friends (and uninstall removes them), there should be no adverse consequences at all, especially if you unroot prior to getting the update. I'm just worried about the reports of updates failing (everything went smoothly for me, but I'm 100% stock and not rooted). Thanks!
Click to expand...
Click to collapse
I am rooted and the install went fine for me. I had not done any of the lag fixes, overclocking, or flashing custom ROMs though.
Same. Rooted before the update. It even stayed rooted after the update.
If the grep above doesn't work btw, look here for how to manually copy the files to your computer, and view the code using a hex editor: http://forum.xda-developers.com/showthread.php?t=761045 . Just remember you need to use "su" first now. Or just wait... One of the devs will probably update their app soon enough.
Ok, thanks! This helps a lot.
Sent from my SAMSUNG-SGH-I897 using XDA App
WTF!!
I reflash back to stock rom JF6 from JH7.
it seems like flashing back to stock rom JF6 wont restore the unlock code!
aloant said:
If I manually peek at the bml3 or nv_data files, I still see my unlock code after JH7. I haven't used any apps to unlock, but it sounds like they just need an update if they are failing.
Click to expand...
Click to collapse
how do you manually peek at bml3 or nv_data file?
netnerd said:
how do you manually peek at bml3 or nv_data file?
Click to expand...
Click to collapse
Posted it in the previous page. The files are still there for me in JH7, it's just that nv_data requires root access now.
aloant said:
Posted it in the previous page. The files are still there for me in JH7, it's just that nv_data requires root access now.
Click to expand...
Click to collapse
thanks! manually peeked, unlock code still there!
aloant said:
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
Click to expand...
Click to collapse
Ok...total noob here...how and where do I actually do this(on the phone or in some program on the pc)? I too lost ability to retrieve code after JH7..... on a good note...I did get my 3 button recovery that was missing....
Hy, Can you explain to my how you did the Update? I have mine unlocked and I keep getting a mesage "can´t conect to at&t servers".
I had mine rooted but I unrooted it to intall the update
I had mine lag fixed but I unfiexed it to intall the update
I removed all at&t blowatware.
Please Help.
robertoaste said:
Hy, Can you explain to my how you did the Update? I have mine unlocked and I keep getting a mesage "can´t conect to at&t servers".
I had mine rooted but I unrooted it to intall the update
I had mine lag fixed but I unfiexed it to intall the update
I removed all at&t blowatware.
Please Help.
Click to expand...
Click to collapse
It could just that the servers are currently overloaded... take a look at the thread on successful updates; although there are still only a few reports, phones that did not have a lagfix at the time of the update did OK, and rooting does not seem to matter. In any case, it's not like your update failed: you haven't even downloaded it yet.
netnerd said:
WTF!!
I reflash back to stock rom JF6 from JH7.
it seems like flashing back to stock rom JF6 wont restore the unlock code!
Click to expand...
Click to collapse
That makes sense, because the JH7 update changed the *permissions* of the nv_data file. So, even if you reflash the stock ROM, the permissions on that file stay the same.
BTW, I suppose this means that one way to fix this would be to create a very simple update.zip that changes the permissions on that particular file. Although, if you go down that route, you might as well root your phone, I guess!
aloant said:
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
Click to expand...
Click to collapse
Thank you, thank you, thank you aloant. My Captivate is now 'reunlocked'
Related
.... or maybe download link from google?
Hello all,
Wondering if someone could try this since I already upgraded won't work but when i got the update on my phone I was able to go to the cache folder and extract from fumo file the following zip that is on mediafire.
Called OTApkg.zip like the mt3g update file.
Should be the current update.
Anyone on the original firmware should be able to flash this from recovery and be up and running with new firmware
Let us know if it worked.
Just rename update.zip and put to root of memory card
boot with vol down and power.
down and select recover
vol up and power to get options
select update from update.zip and should run.
Download:
http://www.mediafire.com/?jm90w7hr922bpd4
You didn't get a chance to test this at all? Can anyone test this and tell me if it works. Before even thinking about rooting I always like to have a set of file to recover with. G1, original mytouch, and slide i all have had way to undo before I rooted.
Didn't work for me. When I tried it I got an error that said
Code:
-- Invalid operation --
On a side note, when I reboot into recovery I get this
Code:
E:Can't open /cache/recovery/command
Anyone else? Is this correct?
Reviewing the code does look like the right file but may not be able to be flashed manually.
First line in update script is mount ( "MTD" , "system" , "/system" )
Looks like boots is a special "fota" mode that will allow modification and this update run like that won't initialize it.
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
travisjames said:
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
Click to expand...
Click to collapse
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Beast84 said:
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Click to expand...
Click to collapse
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
travisjames said:
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
Click to expand...
Click to collapse
Great that means theres no problem with my phone. I feel so much better now
Beast84 said:
Great that means theres no problem with my phone. I feel so much better now
Click to expand...
Click to collapse
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
travisjames said:
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
Click to expand...
Click to collapse
Very true. In the Vibrant section, those guys were able to make update.zip's that were flashable through the stock recovery. Maybe someone can do that for us with this update. I have no dev experience at all but I am willing to test whatever comes up.
It was weird because when I looked at it
It was in the cache directory but not directly
in the cache directory was a file fumo which on browsing just looked like a file on the phone using sufbs.
But when I copied it to the device using the app that is when fumo turned into a folder and opened and saw that file.
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
bobsbbq said:
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
Click to expand...
Click to collapse
No, there isn't a way for T-Mo to push the OTA to you.
Did the rep say anything about the other update?
If you bought the phone full price instead of on contract be sure to check online and change the phone Tmobile has for you to a Mytouch 4g I think that could have something to do with it. I had mine listed as a Mytouch 3G still and I went and changed it and hope it'll make a difference.
Pretty sure that just changing the phone on my tmo wont change. Only thing that i can think of minus something being changed since i got it off the device vs a direct download if someone can get the link or call tmo to check on thier plans if past thier time frame they may be able to do something
Just hopefully someone could get the google link for it instead.
Sent from my HTC Vision using XDA App
I called T-Mobile today about the OTA and they said that it did matter that my plan wasn't set a mytouch package. They told me the OTA should have gone out after my first phone call. Sounds like a bunch of bull**** to me, just figured I'd fill in anyone who was interested. They told me I should have it within 48 hours. *crosses fingers*
*edit* my friend works at T-mobile, she just received the phone herself and after your phone is set as a Mytouch4G, use *#*#checkin#*#* should help start the process, now were both waiting...
I've been waiting since Sunday. Hopefully has nothing to do with having debugging enabled.
Been leaving the phone connected most of the time running
Code:
adb logcat | findstr clients.google
to try and snag the link for the update.
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
johnowa636 said:
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
Click to expand...
Click to collapse
I've been messing with this. It seems you can put in a filter (I put clients.google) but it doesn't matter if you set it to save to your card periodically it saves the entire logs... but you can open those on a pc later and search them or if you're a linux type you can cat file | grep "clients.google"
I thought I might as well start this thread. The only root method I currently know of is http://www.androidpolice.com/2011/04/30/instructions-how-to-root-the-verizon-samsung-droid-charge/
I have read that z4root works as well, can anyone confirm this? I will be receiving my DROID Charge tomorrow and will try z4root.
jism31 said:
I thought I might as well start this thread. The only root method I currently know of is http://www.androidpolice.com/2011/04/30/instructions-how-to-root-the-verizon-samsung-droid-charge/
I have read that z4root works as well, can anyone confirm this? I will be receiving my DROID Charge tomorrow and will try z4root.
Click to expand...
Click to collapse
use adb...z4root is lame
I am not too familiar with adb, how would i go about using it?
jism31 said:
I am not too familiar with adb, how would i go about using it?
Click to expand...
Click to collapse
install the android sdk
jism31 said:
I am not too familiar with adb, how would i go about using it?
Click to expand...
Click to collapse
Try this
http://lmgtfy.com/?q=how+do+i+use+adb
nitsuj17 said:
use adb...z4root is lame
Click to expand...
Click to collapse
Root however you want to, keep us updated on how it works out.
The method in the first post works well. In step 5 after adb shell you will need to input chmod 755 /data/local/GingerBreak or you will get a permission denied error when trying to run gingerbreak.
Just got my Charge from work finally, will root today and keep you guys posted. I will try z4root first to see if it can be done easily.
jism31 said:
Just got my Charge from work finally, will root today and keep you guys posted. I will try z4root first to see if it can be done easily.
Click to expand...
Click to collapse
So what happened ?
Sent from my SCH-I500 using Tapatalk
jism31 said:
Just got my Charge from work finally, will root today and keep you guys posted. I will try z4root first to see if it can be done easily.
Click to expand...
Click to collapse
What does that mean "just got from work"? Were you able to purchase one? I backed down on getting one from Best Buy at the last minute on the Sunday after the missed launch (they were willing to sell it to me), but when I tried to get one the other day, no sale!
Sorry for the delay, z4root does not work nor does superoneclick method. You need to use adb and add in step 5 that was previously posted. Worked for me. Also to clarify i work for verizon and I was able to get one early, I will not be paying for it until I get back from vacation so we do not get flagged in our commission system.
The adb method using Gingerbreak is broken by the OTA update that just came out as some of us more overeager updaters have learned. Here's hoping for a revised method soon!
I figured that ota did more then something usless. I will not be taking it, my phone has been running great rooted for almost 2 weeks.
Anyone know what I have to do to get rid of the ota notification? I'm rooted but the constant asking me to update now or later is annoying.
Well i did the OTA update because I did what I needed with the root. I will try to get a way to re root and get back to you guys.
when will the ota updated charge get a root?
I was screwed from the start. the guy at verizon updated my phone afer he activated in the back.
I ended up taking the ota after I had frozen all the bloat. I'm guessing the OTA fixed some serious battery issues because this morning at work I went from 100% to 60% in one hour with light usage. I don't know if this was a software issue or because my office is fringe 4g... my phone constantly goes back and forth from 3 to 4.
The rest of the day though after I let the ota install, battery life was much much better.
Found this over Droidpolice forum
At step 5 after adb shell you will need to input chmod 755 /data/local/GingerBreak before doing /data/local/GingerBreak this enables the permissions
Has anyone tries this?
Poloasis said:
Found this over Droidpolice forum
At step 5 after adb shell you will need to input chmod 755 /data/local/GingerBreak before doing /data/local/GingerBreak this enables the permissions
Has anyone tries this?
Click to expand...
Click to collapse
Tried and failed with ED02. This was mentioned a few replies up.
Any chance we can get the OP edited?
If you are rooted then go to the build.prop and change all instances of E1 to E2 that should get rid of the notifications as you are tricking the updater into thinking its updated. If you already on E2 you are SOL until a new root method is posted. I got my charge yesterday and Verizon dude updated the phone before I had a chance to tell him not to. I figure I will wait. All I want is root for titanium backup. Ive been happy with this phone.
hey everyone. i just grabbed a bnib one s off of craigslist that has been locked to a different carrier then i use. when i paid a website for the unlock code from the imei they said they couldnt do it and refunded my money. when i asked why they said the code hadnt been posted by the manufacturer and that i should wait a few weeks. when i googled this i found something that said manufacturers dont usually produce unlock codes until phones have been on the market for 3 weeks.
seeing as how the one s has been out for months, could this mean the actual phone needs to have been released for over 3 weeks?
big thanks to ferraripassion at www.htccode.com, he was able to get my unlock code when 3 other websites failed. the code was also emailed to me almost immediately. hes much faster, and has much better service then the other websites i tried. if anyone ever needs unlock codes, or is having trouble finding theirs either pm him, or visit his website. his site also has an imei checker so you can verify he has your code before you bother paying and dealing with refunds like the other sites.
mikeinaus said:
hey everyone. i just grabbed a bnib one s off of craigslist that has been locked to a different carrier then i use. when i paid a website for the unlock code from the imei they said they couldnt do it and refunded my money. when i asked why they said the code hadnt been posted by the manufacturer and that i should wait a few weeks. when i googled this i found something that said manufacturers dont usually produce unlock codes until phones have been on the market for 3 weeks.
seeing as how the one s has been out for months, could this mean the actual phone needs to have been released for over 3 weeks?
Click to expand...
Click to collapse
Have you taken a look at the thread SIM Unlock for FREE
yes ive read that. my problem with that is:
i recently bought a bnib one s that was unlocked, it worked fine for a few weeks then got stuck in a bootloop without being modified or rooted. i could not enter the recovery and factory reset didnt work. i unlocked the bootloader and attempted to install an aftermarket recovery and it also wouldnt load. installing a ruu also wouldnt fix the problem. when i tried to get it warrantied htc wouldnt cover it because i unlocked the bootloader.
now that ive bought my 2nd one s, im going to use it for a month or 2 before i bother unlocking the bootloader. hopefully a 1 or 2 month grace period will be enough to weed out any potential defects.
i tried another unlocking site htcsimunlock.com, they also couldnt find the code, however they have access to htcs company database and said they have a 99 percent change of unlocking it for an extra 15 bucks. im gonna give them a try.
mikeinaus said:
yes ive read that. my problem with that is:
i recently bought a bnib one s that was unlocked, it worked fine for a few weeks then got stuck in a bootloop without being modified or rooted. i could not enter the recovery and factory reset didnt work. i unlocked the bootloader and attempted to install an aftermarket recovery and it also wouldnt load. installing a ruu also wouldnt fix the problem. when i tried to get it warrantied htc wouldnt cover it because i unlocked the bootloader.
now that ive bought my 2nd one s, im going to use it for a month or 2 before i bother unlocking the bootloader. hopefully a 1 or 2 month grace period will be enough to weed out any potential defects.
i tried another unlocking site htcsimunlock.com, they also couldnt find the code, however they have access to htcs company database and said they have a 99 percent change of unlocking it for an extra 15 bucks. im gonna give them a try.
Click to expand...
Click to collapse
Oh yeah, you can root the phone without unlocking the bootloader using this tool.
https://dl.dropbox.com/s/koi38l3uve546rs/Root_with_Restore_by_Bin4ry_v17.zip?dl=1
Turn on USB debugging on your phone and run the script on your computer.
Press 1 for normal
Then on your phone press "restore my phone"
Then wait for it to finish.
After that use the unlocking guide.
That will keep your warranty intact since HTC will have no trace of your phone on their servers.
thats awesome! when was that released? i was hoping thered be a way to get around unlocking the bootloader.
is it possible to load custom roms or change cid with that or do you still need to unlock the bootloader for that?
deep search couldnt find my unlock code either, looks like ill try your method.
mikeinaus said:
thats awesome! when was that released? i was hoping thered be a way to get around unlocking the bootloader.
is it possible to load custom roms or change cid with that or do you still need to unlock the bootloader for that?
deep search couldnt find my unlock code either, looks like ill try your method.
Click to expand...
Click to collapse
It came out sometime in September it just no one really knows about it around here (One S forums). I think you can change CID without unlocking the bootloader but I'm not sure. I know how to unlock the bootloader without using HTC dev also but I need to test a little more.
for some reason the rooting program isnt working. ive tried running it from cmd with admin rights, click 1, click restore my data on phone, it restarts for a few min script says its complete then it restarts and i dont have root. ive tried it 3 times now i dont know if im doing something wrong or what?
phone is in debug mode with allow 3rd party apps.
i also just noticed there is an error report ready on the phone. any ideas?
dc211 said:
It came out sometime in September it just no one really knows about it around here (One S forums). I think you can change CID without unlocking the bootloader but I'm not sure.
Click to expand...
Click to collapse
Does this work for you? I keep getting the "mount: permission denied" after the reboot
dc211 said:
I know how to unlock the bootloader without using HTC dev also but I need to test a little more.
Click to expand...
Click to collapse
That would be epic! Let us know once it's done!
l3ft3r1s said:
Does this work for you? I keep getting the "mount: permission denied" after the reboot
That would be epic! Let us know once it's done!
Click to expand...
Click to collapse
Strange I tried it today myself. I actually ran a RUU then the first thing I did was try it and it worked just fine. It added the app Super SU to my phone. That's root. Then right after I did it i checkd in adb shell and it dropped down to root no problem. My bootloader was still locked too.
mikeinaus said:
for some reason the rooting program isnt working. ive tried running it from cmd with admin rights, click 1, click restore my data on phone, it restarts for a few min script says its complete then it restarts and i dont have root. ive tried it 3 times now i dont know if im doing something wrong or what?
phone is in debug mode with allow 3rd party apps.
i also just noticed there is an error report ready on the phone. any ideas?
Click to expand...
Click to collapse
Check your app drawer for Super SU? I don't think it's hboot specific at all but what are you guys on?
---------- Post added at 08:53 PM ---------- Previous post was at 08:27 PM ----------
dc211 said:
Strange I tried it today myself. I actually ran a RUU then the first thing I did was try it and it worked just fine. It added the app Super SU to my phone. That's root. Then right after I did it i checkd in adb shell and it dropped down to root no problem. My bootloader was still locked too.
Check your app drawer for Super SU? I don't think it's hboot specific at all but what are you guys on?
Click to expand...
Click to collapse
From what I understand the way you get root is the script exploits a timed event in the adb backup/restore process. So maybe try it a couple times.
dc211 said:
Strange I tried it today myself. I actually ran a RUU then the first thing I did was try it and it worked just fine. It added the app Super SU to my phone. That's root. Then right after I did it i checkd in adb shell and it dropped down to root no problem. My bootloader was still locked too.
Check your app drawer for Super SU? I don't think it's hboot specific at all but what are you guys on?
---------- Post added at 08:53 PM ---------- Previous post was at 08:27 PM ----------
From what I understand the way you get root is the script exploits a timed event in the adb backup/restore process. So maybe try it a couple times.
Click to expand...
Click to collapse
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\Users\Jeff's Computer\Downloads\root_with_restore_by_b
in4ry_v10
C:\Users\Jeff's Computer\Downloads\root_with_restore_by_bin4ry_v10 >runme
================================================== ====================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.09.2012) v10 =
================================================== ====================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
Normal Mode enabled!
Pushing busybox....
2927 KB/s (1085140 bytes in 0.362s)
Pushing su binary ....
2807 KB/s (91980 bytes in 0.032s)
Pushing Superuser app
2905 KB/s (996704 bytes in 0.335s)
Making busybox runable ...
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device!
Waiting for device to show up again....
Going to copy files to it's place
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Click to expand...
Click to collapse
running android 4.0.3
software number 1.84.631.9
hboot is 1.13
su does not get installed and rootchecker says that there is no root. ive tried it like 5 times now...
did the end of the script look similar to mine? i watched a video on how to run it and it looked a little different, however it was a different version of the script so that may have been it. i also get an htc error saying the phone just recovered from an abnormal reset.
mikeinaus said:
running android 4.0.3
software number 1.84.631.9
hboot is 1.13
su does not get installed and rootchecker says that there is no root. ive tried it like 5 times now...
did the end of the script look similar to mine? i watched a video on how to run it and it looked a little different, however it was a different version of the script so that may have been it. i also get an htc error saying the phone just recovered from an abnormal reset.
Click to expand...
Click to collapse
I saw everything you did before with your last One S I know you're competent at all this; so I'm sorry to ask but did you look for the super SU app everytime? You're on T-mobile US right?
I already spent a few hours on phone stuff today. You might have to wait until tomorrow.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
mikeinaus said:
running android 4.0.3
software number 1.84.631.9
hboot is 1.13
su does not get installed and rootchecker says that there is no root. ive tried it like 5 times now...
did the end of the script look similar to mine? i watched a video on how to run it and it looked a little different, however it was a different version of the script so that may have been it. i also get an htc error saying the phone just recovered from an abnormal reset.
Click to expand...
Click to collapse
My script looked exactly like that. The phone rebooted twice and it was done. If your used to seeing the "Super User" app and your looking for that it won't be there this uses the "Super SU" app. They do the same thing.
dc211 said:
Strange I tried it today myself. I actually ran a RUU then the first thing I did was try it and it worked just fine. It added the app Super SU to my phone. That's root. Then right after I did it i checkd in adb shell and it dropped down to root no problem. My bootloader was still locked too.
Click to expand...
Click to collapse
Actually, there other one s users too on the original thread with the same problem ("mount: permission denied").
You re only the second to report it works :/
And Bin4ry said that if you get this message, the exploit won't work.
Here is my log:
Do you have those 2 files missing or did you get the same error?
Also which ruu did you flash?
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
2535 KB/s (1085140 bytes in 0.417s)
Pushing su binary ....
3065 KB/s (91980 bytes in 0.029s)
Pushing Superuser app
2723 KB/s (996704 bytes in 0.357s)
Making busybox runable ...
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Click to expand...
Click to collapse
i wouldnt say im exactly competent but i know a bit lol. ive flashed different roms on my tf101 i bought used that was already unlocked, and i am a bit familiar with looking threw scripts and running commands from using linux but ive never actually rooted a phone. but yeah this seems like a fairly basic process, i doubt there is much i could be doing wrong here.
super su is not installed, and has not installed in any of the attempts that i have noticed.
my phone is locked on fido in canada. maybe this has something to do with it?
do you remember if your phone popped up with the htc error report when it was all done? maybe there is some kind of programming from fido interfering with the script and causing the phone to reboot?
also when the phone reboots the first time and it tries to copy everything. mine doesnt completely load the home screen. my background loads but there are no apps on the screen and the launcher bar at the bottom is missing. i can however pull down the top menu and load into settings.
on a side note, have you seen this? http://forum.xda-developers.com/showthread.php?t=1913729 any idea if it would work with the one s?
i appreciate your help. theres probably not much you can help with but its nice to get some input from someone who knows more about this stuff. i posted on the forum page listing my problem so hopefully the developer of the script can figure something out.
hey l3ft3r1s were those errors posted in the script window or is there a log file that is exported somewhere? mine doesnt report any errors in the script window.
mikeinaus said:
hey l3ft3r1s were those errors posted in the script window or is there a log file that is exported somewhere? mine doesnt report any errors in the script window.
Click to expand...
Click to collapse
Script window.
As i see you get the "Backup-Restore.apk' does not exist" also, but this shouldn't be the problem, if you get the "Restore" prompt on the phone.
l3ft3r1s said:
Actually, there other one s users too on the original thread with the same problem ("mount: permission denied").
You re only the second to report it works :/
And Bin4ry said that if you get this message, the exploit won't work.
Here is my log:
Do you have those 2 files missing or did you get the same error?
Also which ruu did you flash?
Click to expand...
Click to collapse
Interesting I used the RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
That won't be an option for anyone that hasn't downgraded their hboot though. I thought I was pretty sure that I had all this wrapped up and just needed to write instructions.
Do you guys have the HTC drivers installed? I'm sure I'll be able to figure it all out it just might take another day or two.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
mikeinaus said:
i wouldnt say im exactly competent but i know a bit lol. ive flashed different roms on my tf101 i bought used that was already unlocked, and i am a bit familiar with looking threw scripts and running commands from using linux but ive never actually rooted a phone. but yeah this seems like a fairly basic process, i doubt there is much i could be doing wrong here.
super su is not installed, and has not installed in any of the attempts that i have noticed.
my phone is locked on fido in canada. maybe this has something to do with it?
do you remember if your phone popped up with the htc error report when it was all done? maybe there is some kind of programming from fido interfering with the script and causing the phone to reboot?
also when the phone reboots the first time and it tries to copy everything. mine doesnt completely load the home screen. my background loads but there are no apps on the screen and the launcher bar at the bottom is missing. i can however pull down the top menu and load into settings.
on a side note, have you seen this? http://forum.xda-developers.com/showthread.php?t=1913729 any idea if it would work with the one s?
i appreciate your help. theres probably not much you can help with but its nice to get some input from someone who knows more about this stuff. i posted on the forum page listing my problem so hopefully the developer of the script can figure something out.
hey l3ft3r1s were those errors posted in the script window or is there a log file that is exported somewhere? mine doesnt report any errors in the script window.
Click to expand...
Click to collapse
Your carrier wouldn't matter. But it sounds like it created a problem with your stock ROM did I read that right? Also, it's my experience that the error report only shows up if you have the "security warning" flag in hboot and you are using a stock rom.
We can't depend on the Sprint HTC phone stuff that much. They have a SD card slot and we don't if you'd like to look else where then you want to look at the ATT HTC One X stuff. They use a modified version of the root exploit for their phone. I'm guessing that it worked for me becuase I had a lower hboot. I didn't think that would be an issue but it just might. I was going to test it tomorrow since if something goes wrong I know how to fix it. So you might want to hold off. But if you'd like I'll post the link.
If you guys move forward then you might get stuck having to unlock via HTC dev to restore. Which kinda defeats the point of trying all this. You might want to hold off another day or two.
yeah i have the drivers installed.
i dont really have an option at the moment, im not gonna unlock the bootloader just yet so ill go without . if you can figure it out thatd be wicked. i have a link to my ruu if you want to try it...
dc211 said:
Do you guys have the HTC drivers installed? I'm sure I'll be able to figure it all out it just might take another day or two.
Click to expand...
Click to collapse
I think so. How do I confirm this? Either way I don't think this should be the problem, since I get a return to adb devices.
By the way, do all RUUs need downgraded hboot?
l3ft3r1s said:
I think so. How do I confirm this? Either way I don't think this should be the problem, since I get a return to adb devices.
By the way, do all RUUs need downgraded hboot?
Click to expand...
Click to collapse
Easiest way is to just hit the button in the all in one toolkit. Not all RUU's need to downgrade the hboot. You can use an RUU that has a higher hboot (as long as your CID is compatable). So you can always use a RUU to upgrade but not to downgrade.
---------- Post added at 10:07 PM ---------- Previous post was at 10:04 PM ----------
dc211 said:
Easiest way is to just hit the button in the all in one toolkit. Not all RUU's need to downgrade the hboot. You can use an RUU that has a higher hboot (as long as your CID is compatable). So you can always use a RUU to upgrade but not to downgrade.
Click to expand...
Click to collapse
Hold tight I'll figure it all out tomorrow.
dc211 said:
Easiest way is to just hit the button in the all in one toolkit.
Click to expand...
Click to collapse
yeap, htc drivers, still nothing
dc211 said:
Not all RUU's need to downgrade the hboot. You can use an RUU that has a higher hboot (as long as your CID is compatable). So you can always use a RUU to upgrade but not to downgrade.
Click to expand...
Click to collapse
Thanks for the info
dc211 said:
Hold tight I'll figure it all out tomorrow.
Click to expand...
Click to collapse
good luck... Again, I'm not optimistic, because of these 2 different problems.
mikeinaus said:
mine doesnt report any errors in the script window.
Click to expand...
Click to collapse
try v17 of the script, just to compare the outputs
l3ft3r1s said:
good luck... Again, I'm not optimistic, because of these 2 different problems.
Click to expand...
Click to collapse
Yeah I read that too. Have faith.
I am currently running 4.1.2 JB w/stock ROM. But, I was thinking about updating. Everyone calls the bootloader "Knox", this worries me. I like having a rooted device.
Thanks,
Sent from my SCH-I535 using xda app-developers app
jdulmer said:
I am currently running 4.1.2 JB w/stock ROM. But, I was thinking about updating. Everyone calls the bootloader "Knox", this worries me. I like having a rooted device.
Thanks,
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You can root after update but the boot loader will be locked so unless your OK with buggy safestrap I would just flash old and slows 4.3 rom until safestrap is straightened out.
---------- Post added at 07:46 PM ---------- Previous post was at 07:35 PM ----------
well I guess I should say if you like stock (and don't mind the permanent locked bootloader) and all you want is root go for the update just make sure you only use saferoot to root your phone.
Same thing here, but...
I am brand new to this forum(as in this is my first post new) and I would like to ask for help with the same problem as the OP in this thread. I am on stock I535VRBMF1 but rooted and I would like to keep it that way. The only problems are:
I know nothing about how to refuse the OTA from Verizon or if this is even possible
I know very little of the "lingo" used on forums regarding Android phones (Flash this and ROM that and bootstrap this mean very little to me)
I don't know how long the phone will let me keep delaying the OTA update which it claims has already been downloaded and will be installed on the next boot cycle or when I let it. I have delayed it 2 times already.
And of course, I don't even know if this is the right place to ask for help. I am so used to being told to "go read the forum" and "use google; figure it out" that I am honestly not sure if I will get the same here. I am fairly quick to learn but this OTA just hit my phone today and I don't know if I even have time to learn.
I am open to suggestions and have already seriously considered trying to install a CyanogenMod on my S3, but I was "working up to it" and now I don't think I have any time left.
Can anyone advise me on how best to proceed to keep my bootloader from getting locked up permanently? I kinda like my phone the way it is, not that Verizon gives a rat's fart about that.
Any suggestions would be appreciated, if anyone has the time to coach a new guy, I would be forever grateful!
SSR
StainlessSteelRat said:
I am brand new to this forum(as in this is my first post new) and I would like to ask for help with the same problem as the OP in this thread. I am on stock I535VRBMF1 but rooted and I would like to keep it that way. The only problems are:
I know nothing about how to refuse the OTA from Verizon or if this is even possible
I know very little of the "lingo" used on forums regarding Android phones (Flash this and ROM that and bootstrap this mean very little to me)
I don't know how long the phone will let me keep delaying the OTA update which it claims has already been downloaded and will be installed on the next boot cycle or when I let it. I have delayed it 2 times already.
And of course, I don't even know if this is the right place to ask for help. I am so used to being told to "go read the forum" and "use google; figure it out" that I am honestly not sure if I will get the same here. I am fairly quick to learn but this OTA just hit my phone today and I don't know if I even have time to learn.
I am open to suggestions and have already seriously considered trying to install a CyanogenMod on my S3, but I was "working up to it" and now I don't think I have any time left.
Can anyone advise me on how best to proceed to keep my bootloader from getting locked up permanently? I kinda like my phone the way it is, not that Verizon gives a rat's fart about that.
Any suggestions would be appreciated, if anyone has the time to coach a new guy, I would be forever grateful!
SSR
Click to expand...
Click to collapse
Use ES file explorer (download from playstore) and delete the file that already downloaded in this location /cache/fota
Next use Titanium backup to freeze the following files: otacerts.api, fwupdate.apk or fwupgrade.apk and sdm1.0.apk located here /system/app
Your phone will not update anymore. As long as you don't upgrade to 4.3, you're safe to keep your bootloader unlock or relock as you wish. If you update to 4.3 your bootloader is will locked permanently and no more custom rom/kernel or custom recovery for you. So don't update!!
buhohitr said:
Use ES file explorer (download from playstore) and delete the file that already downloaded in this location /cache/fota
Next use Titanium backup to freeze the following files: otacerts.api, fwupdate.apk or fwupgrade.apk and sdm1.0.apk located here /system/app
Your phone will not update anymore. As long as you don't upgrade to 4.3, you're safe to keep your bootloader unlock or relock as you wish. If you update to 4.3 your bootloader is will locked permanently and no more custom rom/kernel or custom recovery for you. So don't update!!
Click to expand...
Click to collapse
OK, I was able to locate and delete the file in /cache/fota easily enough, but evidently there is some trick to using Titanium Backup that I am unaware of. I cannot seem to find any way of locating the files you listed at all. I tried refreshing the apps list(which apparently worked), but saw none of the .a[i nor .apk files listed in your reply. I see no way of navigating to the /system/app folder you mentioned. Maybe I need to pay for the donate version of TB to get that capability?
Thank you, by the way, much obliged.
Edit* OK, found "defrost" and found SDM1.0 and discovered that to use that feature I need to buy the donate version. Will do that and BRB. Still was unable to locate the other files, the fwupgrade/update etc. Only SDM. Edit2* OK, I got SDM frozen as instructed, still no luck finding those other apps from within TB.
StainlessSteelRat said:
OK, I was able to locate and delete the file in /cache/fota easily enough, but evidently there is some trick to using Titanium Backup that I am unaware of. I cannot seem to find any way of locating the files you listed at all. I tried refreshing the apps list(which apparently worked), but saw none of the .a[i nor .apk files listed in your reply. I see no way of navigating to the /system/app folder you mentioned. Maybe I need to pay for the donate version of TB to get that capability?
Thank you, by the way, much obliged.
Edit* OK, found "defrost" and found SDM1.0 and discovered that to use that feature I need to buy the donate version. Will do that and BRB. Still was unable to locate the other files, the fwupgrade/update etc. Only SDM.
Click to expand...
Click to collapse
How about use ES file explorer and navigate to /system/app and look for FWupgrade.apk (2 files same name). If you don't find them it's OK. Freeze SDM1.0 should prevent the software from downloading.
buhohitr said:
How about use ES file explorer and navigate to /system/app and look for FWupgrade.apk (2 files same name). If you don't find them it's OK. Freeze SDM1.0 should prevent the software from downloading.
Click to expand...
Click to collapse
I found 2: one called "FWupgrade.apk" and the other was "FWupgrade.odex", both located using ESFE. Not to be completely dense, but what do I do with them now that I have located them? Is there a "freeze" function or similar in ESFE?
Also, no otacerts.api(nor .apk) anywhere.
---------- Post added at 12:40 AM ---------- Previous post was at 12:34 AM ----------
SDM1.0.apk successfully frozen with TB.
StainlessSteelRat said:
I found 2: one called "FWupgrade.apk" and the other was "FWupgrade.odex", both located using ESFE. Not to be completely dense, but what do I do with them now that I have located them? Is there a "freeze" function or similar in ESFE?
Also, no otacerts.api(nor .apk) anywhere.
Click to expand...
Click to collapse
Rename both to FWupgrade.apk.bak (add dot bak at the end).
Sorry, It should be otacerts.zip located in /etc/security - rename to otacerts.zip.bak
buhohitr said:
Rename both to FWupgrade.apk.bak (add dot bak at the end).
Sorry, It should be otacerts.zip located in /etc/security - rename to otacerts.zip.bak
Click to expand...
Click to collapse
Done and done. A few false starts on my end because I didn't know I had to set my file system |,| as "writable" in the options on ESFE, but once I got that option selected, the rest was easy.
Two last things and I will leave you in peace: first, do you have a thread here on XDA that is like a "ROMs and MODs for Dummies" that I could actually learn things without needing my hand held as you have so patiently done just now? Second, is the "Thanks" button over there the correct protocol for giving credit where credit is due?
Thanks very much for taking the time to help me save my phone from the CML1 and bootloader death. I owe you one, really.:good::good::good:
StainlessSteelRat said:
Done and done. A few false starts on my end because I didn't know I had to set my file system |,| as "writable" in the options on ESFE, but once I got that option selected, the rest was easy.
Two last things and I will leave you in peace: first, do you have a thread here on XDA that is like a "ROMs and MODs for Dummies" that I could actually learn things without needing my hand held as you have so patiently done just now? Second, is the "Thanks" button over there the correct protocol for giving credit where credit is due?
Thanks very much for taking the time to help me save my phone from the CML1 and bootloader death. I owe you one, really.:good::good::good:
Click to expand...
Click to collapse
You're welcom, anytime. No I don't have one for Dummies for this model, but I found that the only way it will stick to your brain where you learn by doing it, if you just read it won't stick. There're many threads in this forum (sticky) which you can read, but again I found that when you run into issue and actually got the answer and solved with your own hands then that's how you learn and don't be afraid to ask...Many of us here to help...with pleasure!!
Yes, the thanks button indicated that I did help you or at least trying to help you and you're appreciated. Happy on both side!
buhohitr said:
You're welcom, anytime. No I don't have one for Dummies for this model, but I found that the only way it will stick to your brain where you learn by doing it, if you just read it won't stick. There're many threads in this forum (sticky) which you can read, but again I found that when you run into issue and actually got the answer and solved with your own hands then that's how you learn and don't be afraid to ask...Many of us here to help...with pleasure!!
Yes, the thanks button indicated that I did help you or at least trying to help you and you're appreciated. Happy on both side!
Click to expand...
Click to collapse
You're my hero, man, I really like that I'll be able to try out Cyanogen, but later when I am ready. All down to you.
SSR
Ok, that's what I figured. I think I am going to give Cyanogenmod a shot.
One more quick question. I used CASUAL to unlock bootloader/root. So I can use CLOCKWORKMOD to flash Cyanogenmod?
Sorry for all the silly Newb questions. This is the first time I've had to deal with a bootloader.
Thanks Again,
Sent from my SCH-I535 using xda app-developers app
jdulmer said:
Ok, that's what I figured. I think I am going to give Cyanogenmod a shot.
One more quick question. I used CASUAL to unlock bootloader/root. So I can use CLOCKWORKMOD to flash Cyanogenmod?
Sorry for all the silly Newb questions. This is the first time I've had to deal with a bootloader.
Thanks Again,
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yes u can .u can use any type of custom recovery to flash roms
if u wanna flash a kitkat rom make sure u have the latest version of the recovery.
did u double check to make sure u have root and unlock bootloader .
Yes, it's unlocked, rooted and backed up. Thanks again for the help.
I'll flash Cyanogenmod, when I get home tonight.
Sent from my SCH-I535 using xda app-developers app
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse
TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?
dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.
nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM
back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...
nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?