[Q] My awesomely unrootable Nexus 4 (4.3) - Nexus 4 Q&A, Help & Troubleshooting

Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.

saison said:
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
Click to expand...
Click to collapse
I'm not ENTIRELY sure, but from what I've heard 4.3 causes a lot of problems with root and only one superuser app even works. I'm not sure which one, but it's possible you're using a superuser apk that doesn't work on 4.3.

Try going to Developer Mode > Root Access and change it to Apps and ADB.

IDK about the rest but SuperSU works fine on stock 4.3

thanks, will try this stuff out

moffa~ said:
Try going to Developer Mode > Root Access and change it to Apps and ADB.
Click to expand...
Click to collapse
Does not appear to be a Root Access option.

3rdstring said:
IDK about the rest but SuperSU works fine on stock 4.3
Click to expand...
Click to collapse
OK, I've got that copied into the 'sdcard', but should I remove the old superuser app before installing this one? Not sure how to do it, as it won't delete from the apps menu, it will only give me the option to disable.

saison said:
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
Click to expand...
Click to collapse
If you're on a JWR (Stock) ROM, flash this: http://d-h.st/sDt
If you're on a JSS (AOSP) one, flash this: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Good luck!

Tanmaynarang said:
If you're on a JWR (Stock) ROM, flash this: http://d-h.st/sDt
If you're on a JSS (AOSP) one, flash this: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Good luck!
Click to expand...
Click to collapse
Managed to get it with SuperSU 1.51 as mentioned above. Although I had to do it twice, lol. After flashing and rebooting, I started Titanium, and SU asked if i should grant permission. While thinking about this, the window timed out, and Titanium would not work, nor did the sytem appear rooted, until I reflashed SuperSU and started again. This time, I granted permission for Titanium, and all's well. For now. I guess.:silly:

Yeah for some reason Superuser and 4.3 don't mix very well. SuperSU works fine though, I had to flash it too to get PA 3.92 to work properly. I was really worried that I'd lost all my data since Titanium wasn't working and my CWM backup had failed but ultimately it all worked out.

Related

CWM Error

Whenever I try to make a backup with CMW, it gives me an error that says "An error occurred while attempting to run privileged commands"
How do I fix it?
You have S-Off?
estallings15 said:
You have S-Off?
Click to expand...
Click to collapse
Yep fully rooted and everything. It worked before but not sure why it's not working now.
HTC~TwikiE said:
Yep fully rooted and everything. It worked before but not sure why it's not working now.
Click to expand...
Click to collapse
Try reflashing your recovery. Sounds like it's borked.
estallings15 said:
Try reflashing your recovery. Sounds like it's borked.
Click to expand...
Click to collapse
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
HTC~TwikiE said:
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1242901
estallings15 said:
http://forum.xda-developers.com/showthread.php?t=1242901
Click to expand...
Click to collapse
Just tried that, back to square one. Same error
HTC~TwikiE said:
Just tried that, back to square one. Same error
Click to expand...
Click to collapse
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
estallings15 said:
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
Click to expand...
Click to collapse
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- EDIT: Why of course you have S-off and anyone who asked after you said so would be a silly fellow.
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
tuxkamen said:
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- Do you have S-off?
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
Click to expand...
Click to collapse
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
I had the same error show up recently. I just went around it and did a backup while in boot recovery.
... now... what to do if that starts to fail... Hmm
Sent from my myTouch 4g using xda app
estallings15 said:
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Click to expand...
Click to collapse
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
Click to expand...
Click to collapse
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
tuxkamen said:
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
Click to expand...
Click to collapse
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
estallings15 said:
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
Click to expand...
Click to collapse
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
tuxkamen said:
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
Click to expand...
Click to collapse
Who does anything in ROM Manager? Damn it, OP, reboot into recovery and do it right.
Heh. I didn't want to put it *exactly* that way...
Sent from my HTC myTouch 4g using xda app-developers app

[Q] How to get rid of "System UIDs Inconsistent"?

I was on 4.2.1, rooted, and with TWRP as recovery.
I wanted to get the OTA to 4.2.2 so I did full Titanium backup and then used the WugFresh toolkit to flash stock 4.2.1.
After flashing, I was offered the OTA which I allowed to install.
When finished, I got root back with Rootkeeper and restored all Apps and Data (not System data) with Titanium.
Everything was working, but on every reboot I got the message :
"System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
I also found that My Phone Explorer would no longer connect via USB so I decided to go back to 4.2.1.
I again flashed it with the toolkit and did another restore with Titanium. Again, everything seems to be working, but I still get this message on every boot.
I thought using Titanium Backup was a standard way of restoring apps and data.
How do I get rid of this message without wiping and reinstalling all my Apps individually, which means losing all my game scores, etc?
I also see that in Bootloader there is a line
"Signing - not defined yet".
I do not know if that was there before flashing back to stock.
same problem
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
windwhisper said:
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
Click to expand...
Click to collapse
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
windwhisper said:
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
Click to expand...
Click to collapse
You can boot any recovery you want without hard-flashing it to the device (so long as the boot loader is unlocked).
With the device in bootloader/fastboot mode,
Code:
fastboot boot name-of-recovery-image-file.img
So download TWRP and give it a roll.
Hello,
I got the same "System UIDs Inconsistent" problem. I like to solve my problems myself but I've got no way out this time, so I'm asking for your kind help.
I'm on the SGS III, i9300, I rooted it then went to Omega ROM, and then to Paranoid Android. Everything went well until I got a battery problem (when charging the phone, it was not sufficient to bear with it functionning, so it powered out while charging). After that, the phone restarted and the UID problem appeared. Maybe it's just a coincidence.
So far, I : fixed permissions, did at least 10 factory resets with TWRP, changed ROM (went to CM and came back to PA as nothing changed).
I read the 6 first post about this in xda forum, and other forums too, but nothing came out as an evidence.
Last thing I did was upgrade my PA ROM : the phone couldn't even go beyond the booting process, failed to initiate the phone "first settings" app.
So I came back to the previous version of PA, and was able to use my phone again, but apps like Gmail, Color Note, won't work.
I want to get rid of that, and I wish someone told me, step by step, the things I could do to eradicate the problem. I will do what's necessary to achieve that, I only need someone who knows what to do, and how to do it. I saw some tricks that maybe could do the job but I don't have the knowledge to choose one.
That's my first message here so I hope I didn't break the rules of the forum ^^ If you want any informations about my device to help me, just ask
Thanks a lot, and I hope my english is not too bad ! Have a good day.
Thanks
I got this message too without having any other problem with this TWRP version or Hairy Bean 2.2
The message appeared after flashing the new 4.2.1 (?) modded bootloader for Hairy Bean and the ROM itself.
I'm not sure whether the ROM or bootloader are causing it but mine got fixed by fixing the permissions via TWRP.
Thanks for the tip! :good:
In my case only re-partitioning helped.
for me uninstalling quadrant did the trick
That did it
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
Quick and easy. Worked for me. Thanks
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
This worked for me, too. Thank you.
My situation was a little bit different:
- Flashed Paranoid Android 3.99
- everything was fine (for a few reboots) until I made a nandroid back up with CWM 6.0.3.6 ( which was surprisingly slow, almost 1,5h)
- rebooted
- UID consistency problem
- tried to boot temporary into TWRP - NOT POSSIBLE!
- flashed TWRP 2.6.0.0 permanently
- TWRP: advanced - fix permissions: SUCCESSFUL!
Maybe I'll keep TWRP, but I'm used to CWM for years now.
CWM has removed "fix permissions" since 6.0.3.5 (http://review.cyanogenmod.org/#/c/45945/ )
Fix Permissions
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
edbertin said:
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
Click to expand...
Click to collapse
Me too! TWRP on SlimRom 4.3
Thanks
I am also having this issue after I flashed SlimBean Beta 4 Weekly-409 on my i9300 (wipe data/cache/dalvik and clean install with gapps) and tried restoring a couple of apps like Any do and Temple Run 2 with Titanium Backup.
Is the TWRP being referred here mean the TWRP manager? I installed it from play store but I don't find 'fix permissions' option anywhere in it.
I remember of seeing it in SuperSU but I am unable to install that as well as it says the binary needs to updated.
Could someone please help me here?
Thanks!
--IH
Confirmed. Get into the TWRP n do a fix cache wipe/dalvik wipe/fix permission
Thank you for clarifying this fix
polarfrz said:
Quick and easy. Worked for me. Thanks
Click to expand...
Click to collapse
I just updated my S4 to 10.1 Hyperdrive and experienced this very same issue. Rebooting into safestrap and fixing permissions cleared up this very annoying issue on my phone.
I flashed gummy V4.4 yesterday works great. I went into rom toolbox and changed LCD density to 361 and rebooted, got the UID inconsistent message.
found this thread, fix permissions in TWRP, all fixed. bing bang boom.
thanks all, I also fixed with TWRP latest version, and try to roll back to CWM
I installed a new ROM and I got the System UIDs inconsistent error, then my S Planner FC. I went to find the txt file and it stated that the problem is related to Calendar Storage. I deleted the apk and placed a new one back in. Problem persists, I scratched my head for so long and then I found this thread.
THANK YOU, fixing permission for the Calendar Storage did the trick! Thank God I found this thread!

Fixed by getting pre-rooted ROM -> [Q] G900FXXU1BNL9 root problem

Hi guys,
I've been trying to get Lollipop running properly on my G900F, but there's a problem with my root access - when I start an app that needs root, it takes too long for the system to answer the reques which again makes the app time out. Obviously, this makes it hard to restore my backup from Titanium, but after I manage to run it after lots of swearing, more than a reasonable number of reboots and a little bit of swearing it will still be too slow to give root when running automatic backups. I've tried autoroot, I tried applying the update zip and I've even managed to lock myself out by causing system ui to hang on boot. I'm on my third wipe now and I figured this won't get better by itself and it's not because of a bad ROM update...
So...could someone please help me with how to fix this?
Cheers!
Titanium still not work with lollipop..
For your su problem, you can go into su app and click on the # (right near the apps) and give them su access
kromic1204 said:
Titanium still not work with lollipop..
For your su problem, you can go into su app and click on the # (right near the apps) and give them su access
Click to expand...
Click to collapse
Thanks for replying I actually went with a pre-rooted ROM which seems to work fine. Giving access manually probably wouldn't have worked as it didn't work after I got titanium into the list and even set the timeout to five minutes :S
tiwas said:
Hi guys,
I've been trying to get Lollipop running properly on my G900F, but there's a problem with my root access - when I start an app that needs root, it takes too long for the system to answer the reques which again makes the app time out. Obviously, this makes it hard to restore my backup from Titanium, but after I manage to run it after lots of swearing, more than a reasonable number of reboots and a little bit of swearing it will still be too slow to give root when running automatic backups. I've tried autoroot, I tried applying the update zip and I've even managed to lock myself out by causing system ui to hang on boot. I'm on my third wipe now and I figured this won't get better by itself and it's not because of a bad ROM update...
So...could someone please help me with how to fix this?
Cheers!
Click to expand...
Click to collapse
Latest version of titanium backup works properly with lollipop. What superuser app do you have? I recommend latest SuperSu zip.
I used the latest SuperSU update file and flashed it through both CWM and TWRP. Must have been something with the image - the one I got now works perfectly both with supersu bundled and if I use the update file.

[Q] How do I regain root from accidental update?

My phone kept nagging me to update and I kept exiting out. Apparently somehow I hit install and it updated. I'm on 4.4.4 according to the phone, I don't remember what I was on before I might have been on 4.4.2. I used these files to downgrade from Lollipop previously:
G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar and G900V_NCG_Stock_Kernel.tar
How do I regain root?
Downgrade your Device & root it via previous method,Which you use before.
Bakuryu42 said:
My phone kept nagging me to update and I kept exiting out. Apparently somehow I hit install and it updated. I'm on 4.4.4 according to the phone, I don't remember what I was on before I might have been on 4.4.2. I used these files to downgrade from Lollipop previously:
G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar and G900V_NCG_Stock_Kernel.tar
How do I regain root?
Click to expand...
Click to collapse
Odin the NGC file down in the notes #4 then root with towelroot. Download SuperSU from play store. Update binaries and reboot phone. If you want safestrap as a recovery you must first download busybox from the play store and install it. Then safestrap will install properly.
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Next time install titanium backup pro and freeze SDM to stop the updates.
[email protected] # said:
Downgrade your Device & root it via previous method,Which you use before.
Click to expand...
Click to collapse
Sounds easy enough.
Tulsadiver said:
Odin the NGC file down in the notes #4 then root with towelroot. Download SuperSU from play store. Update binaries and reboot phone. If you want safestrap as a recovery you must first download busybox from the play store and install it. Then safestrap will install properly.
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Next time install titanium backup pro and freeze SDM to stop the updates.
Click to expand...
Click to collapse
The note #4 states
4. If you do not already have root access you must first flash the G900VVRU1ANCG_Full_Odin.tar (flash in Odin's PDA slot(AP in Odin v3.09+)), root with Towelroot (this version does not require internet access), then proceed with the above process.
Click to expand...
Click to collapse
When I clicked the G900VVRU1ANCG_Full_Odin.tar it says it is for Galaxy S4? Is that right? Also how does this way differ from the way I originally did it which was seen here
Bakuryu42 said:
Sounds easy enough.
The note #4 states
When I clicked the G900VVRU1ANCG_Full_Odin.tar it says it is for Galaxy S4? Is that right? Also how does this way differ from the way I originally did it which was seen here
Click to expand...
Click to collapse
Yes, this is actually for the S5.
The difference is all the FCs you have to wade through. Also, the one I suggested is a clean and complete reinstall. It will wipe your SD card and you start fresh. Both will work provided you are not on lollipop. If you are on lollipop you should use the method I suggested.
Tulsadiver said:
Yes, this is actually for the S5.
The difference is all the FCs you have to wade through. Also, the one I suggested is a clean and complete reinstall. It will wipe your SD card and you start fresh. Both will work provided you are not on lollipop. If you are on lollipop you should use the method I suggested.
Click to expand...
Click to collapse
Sorry FC's? I am unfamiliar with the abbreviation. Also was confused when you said SDM, what does that stand for so I know what to freeze when I do it? Much appreciated.
Edit: Also is there a particular reason you recommended a full wipe of everything? I only ask because I hate doing wipes and I never did find a good way to back stuff up really.
Bakuryu42 said:
Sorry FC's? I am unfamiliar with the abbreviation. Also was confused when you said SDM, what does that stand for so I know what to freeze when I do it? Much appreciated.
Edit: Also is there a particular reason you recommended a full wipe of everything? I only ask because I hate doing wipes and I never did find a good way to back stuff up really.
Click to expand...
Click to collapse
FC = force close (aka crash)
SDM - Samsung Data Migration (freeze update software)
Not to answer for tulsadiver... but in my opinion wiping ensures you get rid of any stray "orphan" files that may be even a little borked. Has happened to me before so wiping is often a good way to go.
skeeterpro said:
FC = force close (aka crash)
SDM - Samsung Data Migration (freeze update software)
Not to answer for tulsadiver... but in my opinion wiping ensures you get rid of any stray "orphan" files that may be even a little borked. Has happened to me before so wiping is often a good way to go.
Click to expand...
Click to collapse
Alright one last thing, whats the best way to back stuff up so I can hit the ground running if I decide to do a wipe?
Bakuryu42 said:
Alright one last thing, whats the best way to back stuff up so I can hit the ground running if I decide to do a wipe?
Click to expand...
Click to collapse
You could use titanium backup.
Ok so I went ahead and tried to repeat the steps I did the last time I rooted and so far its not going to well. I've done up to #6 in the instructions here, but when I try to install Busy Box it says I am not rooted properly. Towel root said I was rooted sucessfully though? What should I do?
Bakuryu42 said:
Ok so I went ahead and tried to repeat the steps I did the last time I rooted and so far its not going to well. I've done up to #6 in the instructions here, but when I try to install Busy Box it says I am not rooted properly. Towel root said I was rooted sucessfully though? What should I do?
Click to expand...
Click to collapse
Did you install and setup supersu?
mrjiggywiggy said:
Did you install and setup supersu?
Click to expand...
Click to collapse
The instructions say not to till I install safe strap. Then again because I was previously rooted its actually already installed on there... is that a problem?
Btw a root checker app is also claiming I am not rooted.
Bakuryu42 said:
The instructions say not to till I install safe strap. Then again because I was previously rooted its actually already installed on there... is that a problem?
Btw a root checker app is also claiming I am not rooted.
Click to expand...
Click to collapse
You need to install supersu otherwise root won't work.
mrjiggywiggy said:
You need to install supersu otherwise root won't work.
Click to expand...
Click to collapse
Well I followed those instructions last time and didn't have an issue? Also it seems I can't simply uninstall the superSU I have installed already. I installed it through safestrap like the instructions told me.
Bakuryu42 said:
Well I followed those instructions last time and didn't have an issue? Also it seems I can't simply uninstall the superSU I have installed already. I installed it through safestrap like the instructions told me.
Click to expand...
Click to collapse
Open supersu and install what it tells you, then it should work.
superSu wont open it just gives me a black screen
Bakuryu42 said:
superSu wont open it just gives me a black screen
Click to expand...
Click to collapse
See if it will go ahead and install again from the play store.
Tulsadiver said:
See if it will go ahead and install again from the play store.
Click to expand...
Click to collapse
The playstore shows its installed already and uninstall only uninstalled an update. Tried running it after that and still didn't work, reinstalled it again and still nothing. I also have safestrap installed, which is also not working.
You better start over again. Go Odin the NGC retail tar again. You are too jacked up. After towelroot, install SuperSU from play store. Update binaries and reboot. Then download busybox from play store. Install it. Then install safestrap.
Tulsadiver said:
You better start over again. Go Odin the NGC retail tar again. You are too jacked up. After towelroot, install SuperSU from play store. Update binaries and reboot. Then download busybox from play store. Install it. Then install safestrap.
Click to expand...
Click to collapse
Is there a particular reason it has to format the sd card?

signing OTA update 5.1.1

Hi all,
it's been a while since i started following you and 'till now i haven't had any issue at all.. over the last few days i started experimenting with my N4.
As of now i keep in unlocked, rooted with stock kernel and.. no custom recovery. Bad thing is i've done some crap steps, other than not having a recovery:
1 after unlocking/rooting, i uninstalled some pre-build apps (korean/pying/imeikeyboard/exchange..)
2 everything seemed fine
3 today i tried sideloading 5.1.1 and, of course, it gave me error "couldn't find 'koreanblabla'"
4 i deleted those apps from the ota
5 it passes the apps check but failed upon signature verification - no surprise, i was expecting this.
Now, how do i have that - modified - ota signature ok?
Wipe is not an option, i'd rather buy a new phone lol
Installing those app neither, i'd wanna stick with "my way" : F
I've found these.
jhshi.me/2013/12/02/how-to-create-and-sign-ota-package
source.android.com/devices/tech/ota/sign_builds.html
BTW, along with overclock.net - and reddit lol -, that's one of the best communty driven portal.
Thanks.
urielejh said:
Hi all,
it's been a while since i started following you and 'till now i haven't had any issue at all.. over the last few days i started experimenting with my N4.
As of now i keep in unlocked, rooted with stock kernel and.. no custom recovery. Bad thing is i've done some crap steps, other than not having a recovery:
1 after unlocking/rooting, i uninstalled some pre-build apps (korean/pying/imeikeyboard/exchange..)
2 everything seemed fine
3 today i tried sideloading 5.1.1 and, of course, it gave me error "couldn't find 'koreanblabla'"
4 i deleted those apps from the ota
5 it passes the apps check but failed upon signature verification - no surprise, i was expecting this.
Now, how do i have that - modified - ota signature ok?
Wipe is not an option, i'd rather buy a new phone lol
Installing those app neither, i'd wanna stick with "my way" : F
I've found these.
jhshi.me/2013/12/02/how-to-create-and-sign-ota-package
source.android.com/devices/tech/ota/sign_builds.html
BTW, along with overclock.net - and reddit lol -, that's one of the best communty driven portal.
Thanks.
Click to expand...
Click to collapse
Due to the way 5.0+ does signature checks, if you are even just rooted with stock recovery and no other changes, you have to unroot and revert to stock to install the OTA. It now checks the whole partition and will error if even a byte is out of place. You can either do that, or just flash the images directly, which I find to be the easiest.
Why you don't use factory image and edit flash-all.bat. Remove -w switch and flash. You will lose root and recovery but all apps and data remains.
viktorlj said:
Why you don't use factory image and edit flash-all.bat. Remove -w switch and flash. You will lose root and recovery but all apps and data remains.
Click to expand...
Click to collapse
whatwaitwhat?!
what will that do? is that similar to windows' refresh?
Yes, it will install complete system without wipe. But you must edit flashall.bat and remove -w switch.
what if i reinstall those uninstalled apps? will the integrity check be ok?
If you decide to use factory image there is no integrity check.
mmm
urielejh said:
what if i reinstall those uninstalled apps? will the integrity check be ok?
Click to expand...
Click to collapse
No, because you had to be rooted to remove them in the first place. You have to be unrooted to use the OTA, it has nothing to do with those apps. If you replace, you will just get an error at a different part of the OTA sideload process.
Use the images, as another poster said, you can remove -w from flashall to prevent the wipe (I prefer to always wipe to ensure a clean install however. I don't have anything which I don't backup or can't reinstall quickly)
ok, guys, think i'm done.
using Nexus Root Toolkit i've flashed 5.1.1 update without wiping.
Thanks. pity that i didn't make it the hard way lol

Categories

Resources