Related
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'
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
By "still rooted" do you mean you still have the superuser.apk or can you actually still boot into CWM? Because an OTA will not delete those apps but it WILL break root.
oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
The update doesn't wipe the phone at all, it only patches certain files in the /system partition, so it doesn't actually delete the su binary in /system/bin or the superuser.apk in /data/apps.
The update script does, however, do a recursive chmod of the permission on /system/bin, and that broke root on my phone. Even though the files were still there, and some apps thought that I was still rooted, many root things (like Titanium and Root Explorer's ability to mount /system as R/W) wouldn't work.
I've seen some reports that root stuck, but I'd advise flashing the su update again...it's quick and easy to do with CWM, and it will fix the permissions to make sure none of your apps have any issues.
Are you sure the update actually occurred? Your android version and build number have changed?
so, now i have
Android version - 2.3.2
Kernel - 2.6.35.7-g7f1638a
Build number - GRH78C
if start titanium backup - can see that superuser permission granted
Market access working perfectly - i hav an acces for paid apps
Can grab screen with ShootMe
dont remember how did i root - seems i just run some script on ubuntu notebook
Thanks for everybody for replies
yes, going into CWR can easily update the permissions recursively
not sure but probably i am on superboot loader (not SWR)
being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.
RogerPodacter said:
being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.
Click to expand...
Click to collapse
He's saying that he thought the OTA would unroot him, not that being rooted would keep him from OTAing.
Funny how the update seems to impact the root of people differently. It definitely broke mine, even though it didn't erase the files.
Oh oops my bad I mis read!
The update didn't break my root
sagech said:
The update didn't break my root
Click to expand...
Click to collapse
it seems new uppdate does not unroot phones with superboot rooting
No Update
Hello,
I tried to update my phone but I am now looking since 10 minutes at the little Android and nothing happens.
There was a short message where the Clockworkrecovery said something like it could not verfy the update file.
Should I just put out the battery and try to reboot?
Edit:
The Clockwork recovery came up again and I selected to reboot the phone. Now it's still running on 2.3.1.
What have I done wrong?
Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S
Bronk93 said:
Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S
Click to expand...
Click to collapse
Yes, exactly!
So is the solution maybe to wait till the 2.3.2 version is available at the ROM Manager?
I'm rooted and have most of the bloat/useless apps frozen but not removed. I tried to let it auto update, but it just stayed on the "!" screen and did nothing. What all needs to be in place in order for it to work? Someone in the update thread in General said he had a list of what the updater checks/asserts before allowing the update to go through. Can someone post that here?
you have to unroot first before trying to install the update.
ebackbone said:
you have to unroot first before trying to install the update.
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted. Apparently alot of people are having that same exact issue when trying to update. Wonder if its the rooting method that makes the difference.
cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted. Apparently alot of people are having that same exact issue when trying to update. Wonder if its the rooting method that makes the difference.
Click to expand...
Click to collapse
if you actually read the forums, you'll notice that a lot of the 8.6.5.7 rooted users couldn't properly update theirs to the latest 8.6.5.9 before unrooting first. what works for you does not necessarily means it is the absolute truth for all.
Do need to have stock recovery installed to update...and if you have changed other files it still may not update if rooted
Here is a list of the patches. All of these files have to be stock or else the update will fail. There are other ways to install the updates. One of the devs will probably put together a zip file that will install it.
I tried modifying the OTA and flashing through the stock recovery, but it does crypto key checks and I'm not familiar with the key format. It will flash through some version of CWM (don't forget to mount /system first), but the blob won't flash because the staging partition isn't mounted, but this can be done manually in several ways.
Code:
system/app/AWS.odex
system/app/ApplicationsProvider.apk
system/app/ApplicationsProvider.odex
system/app/AsusReader.apk
system/app/AsusReader.odex
system/app/AsusSetupWizard.odex
system/app/Bluetooth.apk
system/app/Bluetooth.odex
system/app/BooksTablet.odex
system/app/Browser.apk
system/app/Browser.odex
system/app/CMClient.apk
system/app/CMClient.odex
system/app/Calculator.apk
system/app/Calculator.odex
system/app/Calendar.apk
system/app/Calendar.odex
system/app/CalendarProvider.apk
system/app/CalendarProvider.odex
system/app/Camera.odex
system/app/CertInstaller.apk
system/app/CertInstaller.odex
system/app/ChromeBookmarksSyncAdapter.odex
system/app/Contacts.apk
system/app/Contacts.odex
system/app/ContactsProvider.apk
system/app/ContactsProvider.odex
system/app/DLNA.apk
system/app/DLNA.odex
system/app/DMClient.apk
system/app/DMClient.odex
system/app/DefaultContainerService.apk
system/app/DefaultContainerService.odex
system/app/DeskClock.odex
system/app/Dictionary.odex
system/app/DownloadProvider.apk
system/app/DownloadProvider.odex
system/app/DownloadProviderUi.apk
system/app/DownloadProviderUi.odex
system/app/DrmProvider.apk
system/app/DrmProvider.odex
system/app/Email.odex
system/app/EmailWidget.apk
system/app/EmailWidget.odex
system/app/Exchange.odex
system/app/FacebookPoster.odex
system/app/FileManager.apk
system/app/FileManager.odex
system/app/Finsky.odex
system/app/GalleryNew3DGoogle.odex
system/app/Gmail.odex
system/app/GoogleBackupTransport.odex
system/app/GoogleCalendarSyncAdapter.odex
system/app/GoogleContactsSyncAdapter.odex
system/app/GoogleFeedback.odex
system/app/GoogleLoginService.odex
system/app/GooglePartnerSetup.odex
system/app/GoogleQuickSearchBox.odex
system/app/GoogleServicesFramework.odex
system/app/HTMLViewer.apk
system/app/HTMLViewer.odex
system/app/HoloSpiralWallpaper.apk
system/app/HoloSpiralWallpaper.odex
system/app/Keyboard.odex
system/app/Kindle-OEM.odex
system/app/LatinImeGoogle.odex
system/app/Launcher2.apk
system/app/Launcher2.odex
system/app/Layar.odex
system/app/LiveWallpapersPicker.apk
system/app/LiveWallpapersPicker.odex
system/app/MEar.odex
system/app/Maps.odex
system/app/MarketUpdater.odex
system/app/MediaProvider.apk
system/app/MediaProvider.odex
system/app/MediaUploader.odex
system/app/ModemUpdateService.odex
system/app/Music2.odex
system/app/MyCloud.odex
system/app/MyGazine.odex
system/app/MyWater.odex
system/app/NVIDIATegraZone.odex
system/app/NetworkLocation.odex
system/app/OneTimeInitializer.odex
system/app/PCSyncLauncher.odex
system/app/PRAndroid.odex
system/app/PackageInstaller.apk
system/app/PackageInstaller.odex
system/app/Phone.apk
system/app/Phone.odex
system/app/PicoTts.odex
system/app/PixWe.odex
system/app/PolarisOffice.apk
system/app/PolarisOffice.odex
system/app/Screenshot.apk
system/app/Screenshot.odex
system/app/Settings.apk
system/app/Settings.odex
system/app/SettingsProvider.apk
system/app/SettingsProvider.odex
system/app/SetupWizard.odex
system/app/SoundRecorder.apk
system/app/SoundRecorder.odex
system/app/StrAsus.odex
system/app/Street.odex
system/app/SystemUI.apk
system/app/SystemUI.odex
system/app/Talk.odex
system/app/TelephonyProvider.apk
system/app/TelephonyProvider.odex
system/app/TtsService.apk
system/app/TtsService.odex
system/app/UpdateLauncher.apk
system/app/UpdateLauncher.odex
system/app/UserDictionaryProvider.apk
system/app/UserDictionaryProvider.odex
system/app/Vending.odex
system/app/Vibe2.odex
system/app/VideoEditorGoogle.odex
system/app/Videos.odex
system/app/VoiceSearch.odex
system/app/Weather.odex
system/app/XT9IME.apk
system/app/XT9IME.odex
system/app/YouTubeTablet.odex
system/app/ZinioReader.odex
system/app/ZinioSettingsProvider.odex
system/bin/brcm_ram_plus
system/bin/debuggerd
system/bin/fu
system/bin/vold
system/bin/wpa_supplicant
system/buildrop
system/framework/am.jar
system/framework/am.odex
system/framework/androidolicy.jar
system/framework/androidolicy.odex
system/framework/android.test.runner.jar
system/framework/android.test.runner.odex
system/framework/apache-xml.jar
system/framework/apache-xml.odex
system/framework/bmgr.jar
system/framework/bmgr.odex
system/framework/bouncycastle.jar
system/framework/bouncycastle.odex
system/framework/com.android.future.usb.accessory.jar
system/framework/com.android.future.usb.accessory.odex
system/framework/com.android.locationrovider.jar
system/framework/com.android.locationrovider.odex
system/framework/core-junit.jar
system/framework/core-junit.odex
system/framework/core.jar
system/framework/core.odex
system/framework/ext.jar
system/framework/ext.odex
system/framework/framework-res.apk
system/framework/framework.jar
system/framework/framework.odex
system/framework/ime.jar
system/framework/ime.odex
system/framework/input.jar
system/framework/input.odex
system/framework/javax.obex.jar
system/framework/javax.obex.odex
system/framework/monkey.jar
system/framework/monkey.odex
system/framework/pm.jar
system/framework/pm.odex
system/framework/services.jar
system/framework/services.odex
system/framework/sqlite-jdbc.jar
system/framework/sqlite-jdbc.odex
system/framework/svc.jar
system/framework/svc.odex
system/lib/drm/libdrmwvmplugin.so
system/lib/hw/gralloc.tegra.so
system/lib/libandroid_servers.so
system/lib/libbcc.so
system/lib/libereader.so
system/lib/libinput.so
system/lib/libjSebring.so
system/lib/libnvomx.so
system/lib/libsensors.mpl.so
system/lib/libsrsprocessing.so
system/lib/libstagefright.so
system/lib/libwebcore.so
system/lib/libwvdrm.so
system/lib/libwvm.so
system/lib/modules/bcm4329.ko
system/lib/modules/scsi_wait_scan.ko
Was rooted, but no CWM recovery, update found when manually checking, and installed fine.
Machine is relatively new, came with 3.1 already on.
Jyveafk said:
Was rooted, but no CWM recovery, update found when manually checking, and installed fine.
Machine is relatively new, came with 3.1 already on.
Click to expand...
Click to collapse
I think not having CWM is the difference, not rooted vs unrooted.
So Rooted + CWD = No OTA Updates
Rooted + No CWM = OTA Updates are OK ?
magicdave26 said:
So Rooted + CWD = No OTA Updates
Rooted + No CWM = OTA Updates are OK ?
Click to expand...
Click to collapse
To be on the safe side, I think it should be
Rooted + No CWM + No system file mod = OTA OK.
jviola said:
I think not having CWM is the difference, not rooted vs unrooted.
Click to expand...
Click to collapse
magicdave26 said:
So Rooted + CWD = No OTA Updates
Rooted + No CWM = OTA Updates are OK ?
Click to expand...
Click to collapse
I think it will flash through CWM if you move it to the SD card and then mount system before you flash it. It will patch the system, but it won't flash the blob file. To flash the blob file, you have to mount the staging partition (/dev/block/mmcblk0p4) and maybe the btmac partition (/dev/block/mmcblk0p5). Or you could just manually copy the blob to the staging partition and reboot.
Just wanted to give everyone a heads up about the recent firmware update (build 10.6.1.15.3) for the TF300T. I had root before the update and all was well in the world and then I saw the update notification. I checked voodoo to make sure I had root backed up and I did. I performed the update and now no root and voodoo is not restoring it. I fired up adb and found su binary and busybox are missing from bin and xbin It appears asus decided to overwrite my system directory in this update and wipe out all those files that I so carefully placed to gain root access.
I think I am now officially stuck unrooted. :crying:
Unfortunately unlocking the bootloader is not an option for me for work related reasons. If anyone has any other information about this update or how I can restore root, please help!
Otherwise you would be wise to stay away from this update if you are currently locked and want to keep root.
This might help you:
[JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
And a little searching might find it even quicker than asking!
Someone just confirmed it is still working with the latest upgrade.
Would have been surprised, if Asus had broken it that quickly.
Sent from my TF300T using Tapatalk HD
ccb1208 said:
Just wanted to give everyone a heads up about the recent firmware update (build 10.6.1.15.3) for the TF300T. I had root before the update and all was well in the world and then I saw the update notification. I checked voodoo to make sure I had root backed up and I did. I performed the update and now no root and voodoo is not restoring it. I fired up adb and found su binary and busybox are missing from bin and xbin It appears asus decided to overwrite my system directory in this update and wipe out all those files that I so carefully placed to gain root access.
I think I am now officially stuck unrooted. :crying:
Unfortunately unlocking the bootloader is not an option for me for work related reasons. If anyone has any other information about this update or how I can restore root, please help!
Otherwise you would be wise to stay away from this update if you are currently locked and want to keep root.
Click to expand...
Click to collapse
I got root back from voo doo. In your message you say you had checked root backed up. You didnt say you took the next step and hit temp unroot so that system appears unrooted whilr updating.
Just wondering.
Woody
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
woodsonmh said:
I got root back from voo doo. In your message you say you had checked root backed up. You didnt say you took the next step and hit temp unroot so that system appears unrooted whilr updating.
Just wondering.
Woody
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I actually did that. I temp unrooted before I updated which in hindsight might have been part of my issue. Anyways, I am going to be using motochopper to reroot but my tmp directory thinks it is a file now :silly:
I am currently downloading the asus firmware file so I can manually update (even though i am already on 4.2.1) and that is suppose to re-write my system directory so my tmp directory will be restored and I can push all the needed files. I will report back with how it goes.
[UPDATE] I was able to apply asus firmware manually (which factory reset my device in the process) then ran motochopper successfully. I backed up root with voodoo and this time updated firmware OTA without temp unrooting. After the update was applied, I restored root with voodoo and all is well now! Thank you everyone for your help
Root for build 10.6.1.15.3
ccb1208 said:
Just wanted to give everyone a heads up about the recent firmware update (build 10.6.1.15.3) for the TF300T. I had root before the update and all was well in the world and then I saw the update notification. I checked voodoo to make sure I had root backed up and I did. I performed the update and now no root and voodoo is not restoring it. I fired up adb and found su binary and busybox are missing from bin and xbin It appears asus decided to overwrite my system directory in this update and wipe out all those files that I so carefully placed to gain root access.
I think I am now officially stuck unrooted. :crying:
Unfortunately unlocking the bootloader is not an option for me for work related reasons. If anyone has any other information about this update or how I can restore root, please help!
Otherwise you would be wise to stay away from this update if you are currently locked and want to keep root.
Click to expand...
Click to collapse
**********
I lost root as well after update to build 10.6.1.15.3,however, all I needed to do is reinstall TWRP and install UPDATE-SuperSU-v1.25.zip and I'm again rooted. You can do a search for UPDATE-SuperSU-v1.25.zip file here on XDA...it will come up. Hope this helps.
Regards,
Julian
julianikos said:
**********
I lost root as well after update to build 10.6.1.15.3,however, all I needed to do is reinstall TWRP and install UPDATE-SuperSU-v1.25.zip and I'm again rooted. You can do a search for UPDATE-SuperSU-v1.25.zip file here on XDA...it will come up. Hope this helps.
Regards,
Julian
Click to expand...
Click to collapse
I was able to reaquire root by using motochopper but thanks for the advise. Sounds like your device is unlocked which like I said was not an option for me.
BTW, if you are unlocked, why are you running stock asus firmware??? You can find AOKP builds over at rootzwiki. http://rootzwiki.com/topic/27152-aokp-build-38-unofficial/
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?