Related
I've done a lot of googling and searching, but nothing has worked yet.
I've tried freezing fwupgrade and smart device manager 3.3 with Titanium Backup. Also tried wiping cache / dalvik cache, but I still get the OTA update notification after every reboot.
I don't really care to update to LG8 yet, so I am hoping there is something simple that I'm missing.
Edit your build.prop in system changing the parts that end in lg2 to lg8 or just replace w/ this http://db.tt/nO5QAu2a and reboot
billard412 said:
Edit your build.prop in system changing the parts that end in lg2 to lg8 or just replace w/ this http://db.tt/nO5QAu2a and reboot
Click to expand...
Click to collapse
Thanked. Worked.
Out of curiosity I installed link2sd and my device status immediately changed to modified. I uninstalled link2sd but still it is modified. Usually whenever I installed any root application status used to change to modified and when I uninstall it used to change back to normal. But with link2sd it is still modified. Can somebody tell me how to completely remove link2sd so that I get the status back to normal? somehow I am not getting courage to use triangle away
It's not related to triangle away.
Flashing a stock rom helps
Sent From Samsung's Galaxy Note II Using Internet
raj_k_r said:
Out of curiosity I installed link2sd and my device status immediately changed to modified. I uninstalled link2sd but still it is modified. Usually whenever I installed any root application status used to change to modified and when I uninstall it used to change back to normal. But with link2sd it is still modified. Can somebody tell me how to completely remove link2sd so that I get the status back to normal? somehow I am not getting courage to use triangle away
Click to expand...
Click to collapse
Or you could try a Factory Data Reset. That may clear it. It worked for me after rooting with CF Autoroot.
Thank You, I will try tonight and update you
One more question, Kies has detected a new firmware but it says if device is rooted, update might fail. Is it so? Can I update without removing root?
and these are the files added/modified by link2sd
debuggerd from system/bin and
install-recovery.sh and install-recovery.sh.ori from system/etc
I am not sure what to do with these. Can anybody suggest. I want to keep flashing through ODIN as the last option and factory resetting wont remove these files. I believe samsung does not use install-recovery.sh. Can I just delete these files in that case?
norm2002 said:
Or you could try a Factory Data Reset. That may clear it. It worked for me after rooting with CF Autoroot.
Click to expand...
Click to collapse
Still it says modified after Factory resetting
Deleting them will get you a modified status.
Rename them to default.
They restore the default recovery if it had been changed on boot.
You need to remove root.
And have both stock recovery and kernel.
I have 0 counter and official binary and status in download mode.
But settings show device status modified.
Go to supersu and select full unroot.
It will reboot and you will get default status.
Also disable any app that uses root.
Like disabling and restoring and mods.
Last resort is to do factory res reset and then flash stock rom.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Deleting them will get you a modified status.
Rename them to default.
They restore the default recovery if it had been changed on boot.
You need to remove root.
And have both stock recovery and kernel.
I have 0 counter and official binary and status in download mode.
But settings show device status modified.
Go to supersu and select full unroot.
It will reboot and you will get default status.
Also disable any app that uses root.
Like disabling and restoring and mods.
Last resort is to do factory res reset and then flash stock rom.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you but can you check and let me know whether you also have these files? If you have, can you share them here? I dont mind experimenting but I would like to flash stock ROM only when Samsung releases 4.2. Till then I can keep on experimenting with.
raj_k_r said:
Thank you but can you check and let me know whether you also have these files? If you have, can you share them here? I dont mind experimenting but I would like to flash stock ROM only when Samsung releases 4.2. Till then I can keep on experimenting with.
Click to expand...
Click to collapse
I've got the same problem now. Didn't know about JB ROM's not supporting app2sd, and followed a forum's advise to use Link2SD instead. Ended up with Link2SD not working (standard mount of Link2SD very likely already used by the OS itself), and tried to get rid of the scripts it installs in the system.
But no got. Since there is no documentation and no real uninstaller, you end up with messed up scripts in your system folders.
The system modified status won't go away anymore.
I could correct the scripts Link2SD modifies myself (I'm used to do such things in Linux), but I'd need to know, what exactly has changed...
Is there anyone who could help?
My phone prompted me today that an update to 4.2.2 was available.
Its a takju Nexus running with an unlocked bootloader and rooted but otherwise stock rom.
I've tried to get it to do the update, however it reboots to a screen saying "applying system update" then after a few seconds flicks to a screen with an android with an exclamation mark, and the word Error below.
Is this because i'm rooted? or is there something else going on?
Thanks
Kevin
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.
chelseaeuro said:
I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.
Click to expand...
Click to collapse
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.
reysonance said:
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.
Click to expand...
Click to collapse
I did that and my update is gone lol. Guess I'll have to wait for a few hours.
I had to force stop the frameworks and then try updating, which worked. Thanks!
reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Thanks
Just to confirm, if i flash the system.img over my current system, will that delete all my installed apps/data? Which system.img should i be flashing? the one from 4.2.1?
Is there a list somewhere of the version numbers for the various parts (recovery, radio, kernel and bootloader) so i can check they are correct?
Also, is there a way i can flash the OTA update with some error logging or debug output turned on, so i can see what its actually failing at?
Cheers
Yes, the one from 4.2.1, check under Maps > Settings > About, it should gives you the version you're currently running, download it from the factory images page if you haven't already, and no, it should not wipe any apps+data, but back it up anyway if you're worried, better safe than sorry, I'm generally paranoid about data so I always backup, but no it shouldn't wipe anything. You'll lose root and that's it.
And for the bootloader and all that, it all should come all packaged on the factory image, so if you flash 4.2.1 via toolkit, or manually and haven't installed any radio or kernel you should be safe. IIRC, the bootloader version is PRIMELC03, the radio is XXLH1.
reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Very thanks for this explanation. It help me a lot and I finally could update via OTA.
Running converted GPE 4.4.4, stock rooted (recently followed steps to un-root), S-off (sunshine), Unlocked stock bootloader with CID: GOOGL001.
I received the OTA for 5.0.1 last week and received an error. Is there a way for me to install the OTA without wiping my phone?
I've spent the last week looking over the forums and haven't found an answer. Any help will be appreciated as I really want to avoid wiping to get the update if possible. Thanks!
Are you on stock recovery? I realize if you did the full conversion, it would have installed stock recovery. But just wanted to make sure you didn't flash a custom recovery after that.
Also, on the topic of wiping the phone, I would recommend backing up any important data in any case, if you don't already. There is never a guarantee against data loss even with an OTA; or just losing data from day to day usage for that matter.
Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Jamister989 said:
Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
a recovery.log would be useful here to see where the ota fails.
pure guessing : I think if you've messed with the system partition (SDfix) it is likely what is causing your problem (infamous "unexpected content" error in recovery while installing ota).
I'll post one this evening. Where is a quick explaniation of how to the report?
Jamister989 said:
I'll post one this evening. Where is a quick explaniation of how to the report?
Click to expand...
Click to collapse
what do you mean by 'how to the report?' ?
Jamister989 said:
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
If any system files have been altered by root, the OTA will fail. You either need to return the files to the exact "stock" condition, or re-install the stock ROM.
Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.
The SD fix app should have made a back up copy of the original look in /etc/permissions and it's platform.xml the original will have original pre sdfix in the file name..
I had a failed attempt of OTA and it stated that my "platform.xml " was the reason.
Like @graffixnyc said only you you will have to rename the platform.xml to platform.bak and the platform.presdfix to platform.xml as it's the unmodified xml you need.
Jamister989 said:
Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.
Click to expand...
Click to collapse
you can :
- reboot in recovery, try to apply ota, view the recovery.log in recovery menu, adb pull it and eventually post it....
- or assuming your issue is because of the modification of platform.xml as @graffixnyc and @jball stated, switch it with its backup (same dir) and then retry the ota.
Update (May 20): Update to latest version 2.74-2
All versions after SuperSU 2.72 has force encrypt support built in. However it will still disable force encryption by default, you have to set flags manually.
I only modified the default value of the force encrypt flag in the flashing script, so no need to worry that this might break things
If your OCD forces you to use the official version, please look here for instructions to set the flag manually by yourself.
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
I slightly modified the SuperSU flashing script, so now it won't change the encryption flag.
This zip will remain useful until we find a way to decrypt our data partition with working signal.
Hi,
this works without problems, big tanks. Device is rooted now.
regards
starbase64
Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?
MNoisy said:
Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?
Click to expand...
Click to collapse
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3
datafoo said:
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3
Click to expand...
Click to collapse
Yes yes yes please! THANK YOU!
Where can I find them?
Nice buddy, will update the method used in my build, makes life a lot easier.
I had considered making similar modifications but you appear to have beaten me too it
topjohnwu said:
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
Here I come up with a more elegant solution. I slightly modified the SuperSU flashing script, so now it won't change the encryption flag, and also won't remove dm-verify.
NOTE: If your boot image is already modified, it will not reset the flag back to forceencrypt. You have to restore to the stock boot image, then flash this zip. The way I accomplished this is reverting a few modification from the previous ramdisk, so the ramdisk itself has to be stock.
Devs can include this zip into their rom, so users can wipe their whole data with your rom installed.
This zip will be useful until we find a way to decrypt our data partition with working signal.
Click to expand...
Click to collapse
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity
SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.
Chainfire said:
SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.
Click to expand...
Click to collapse
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.
jcase said:
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity
Click to expand...
Click to collapse
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.
topjohnwu said:
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.
Click to expand...
Click to collapse
I'd have to look at the zip and test to see why. It could be that your particular firmware isn't actually enforcing dm-verity (I believe google mandates this on 6.0+), that HTC disables enforcing when s-off or the zip isn't properly enforcing verity.
Best advice is not to enforce verity on system if you are rooted.
What should (and did for my phone) happen if you have dm-verity enabled on system and a modified system is the phone shouldn't successfully boot.
Captain_Throwback said:
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.
Click to expand...
Click to collapse
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.
Chainfire said:
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.
Click to expand...
Click to collapse
Will that cause complications for users who wipe cache often?
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
Will have a bash tonight mate
topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
still no go on boot
LeeDroid said:
still no go on boot
Click to expand...
Click to collapse
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.
Is it OK to use SYSTEMLESS with your current build?
Thanks
ah, perhaps encountered a blarf
you wanna stick with blarp ... he's much nicer
topjohnwu said:
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.
Click to expand...
Click to collapse
Ahh, I knew why.
I cannot separate the forceencrypt flag patch and verify flag by modifying the script.
Had to wait for Chainfire to release new version, or we have to manually modify the boot image.