I made a full Nandroid through TWRP and a full App/data backup via ROM Toolbox before flashing the OTA zip. I just found the deal breaker for me with 4.2. LogMeIn does not display the remote desktop properly which is essential for me as I use it daily for work. My only concern with running the Nandroid restore is how many scripts and file structure changes were done in 4.2.
Has anyone done this without flashing a fresh 4.1.2 ROM?
i'm trying to restore a nandroid backup of 4.1.2 with TWRP but i dont think it's showing up..only the nandroid i just did..wtf
That's because 4.2 changes the SD card folder structure. You'll have to manually move the backup folder back to its right path.
Nandroids replace everything, so you should be ok going back.
What's wrong with logmein ? My remote desktop app requires that I change the resolution for it to work. I would also screw with the dev options.
Sent from my Nexus 7 using XDA Premium HD app
Well I'm back and running 4.1.2, I do think it is much smoother. I flashed a rooted stock rom then did a factory reset. The problem with using just the nandroid was the symlinks created by 4.2. The stock rom reset those, the nandroid may of but I still had to move around some directories and fix the 'sdcard' since the revert left all of my data in the 0 folder and I had to manually move it back to the root of data/media/ as well as consolidate the obb an twrp folders which I did from twrp. Once I was back on a confirmed functioning 4.1.2 base I did a nandroid restore and wiped cache and davlik. All seems to be perfect. I kept root and all.
Logmein was a widespread issue and although it's a $30 app they are slow to support and update it and it is the one app I must have working. There were a few other daily apps that were having issues also, some were updated by the time I reverted though haha. Overall Thought 4.2 was not as quick and was buggy for me. I loved they fixed the volume and the keyboard was great but this is a work device first so ill let xda and the devs iron out the kinks before jumping back up. Volume+ and SwiftKey will hold me over for now
Sent from my Nexus 7 using Tapatalk 2
kangy, i did the same. i figured out that stupid file structure (why is it under /sdcard/0 now?) and i copied the nandroid..took about 1 hour to get everything done how i wanted it.
then i did the stupid thing of flashing the gapps package for 4.2 because i wanted the new apps...without realizing its only for deodex roms, and stock 4.1 is odex lol whoops. had to nandroid like 2 times lol
They did it like that for the multi users to each have their own SD card directory.
Sent from my HTC Evo 3D using Tapatalk 2
I keep getting the prompt to install the ota update, anyone know how to clear that out and then block it. I have to ride out 4.1.2 until Logmein is fixed sometime in the next decade
Sent from my Nexus 7 using Tapatalk 2
kangy said:
I keep getting the prompt to install the ota update, anyone know how to clear that out and then block it. I have to ride out 4.1.2 until Logmein is fixed sometime in the next decade
Sent from my Nexus 7 using Tapatalk 2[/QUOT
know what i did? installed that FOTA.apk ota killer.....it came up like twice after, and hten never has again....awesome!
Click to expand...
Click to collapse
Do you have a link to that apk?
Related
Some apps not working after updated to 4.2, so I'm considering back to 4.1.2.
Though I never done this before since the day I get Nexus 7,
I think use Wug's Nexus Root Toolkit should get it done.
But just for sure:
1. Do I need to unlock/root to flash factory 4.1.2 image? (I think it is not but not so sure)
2. Directory structure seems different from 4.1.2, is it OK just using Toolkit to backup/restore settings?
(Sorry for my English if anything looks impolite)
1) unlock bootloader yes; root no, as you're going to overwrite the system anyways.
Also I'd suggest not using a toolkit, just download the factory image off google's page and run the "flash-all.bat"
2) Use Titanium Backup to backup all app data, wipe after flashing 4.1.2 and then restore apps + data with Titanium again
I just downgraded this morning. All your data will be wiped .. ALL YOUR DATA ... meaning, after I got back to 4.1.2 I was having 13GB of free space on the tablet (out of 13 possible) .
So, if you HAVE a nandroid from the 4.1.2 days, save it to your computer (along with all your files).
If you don't have a 4.1.2 nandroid, at least create now a backup repository with whatever tool you prefer and then save the respective files to PC.
Then, flash the factory image for 4.1.2.
Then copy all your files back to the internal memory, install the backup tool and restore your apps.
The reason behind this is that the update from 4.1.2 to 4.2 has some scripts that are porting the original /data and /sdcard mounts to the new structure used in 4.2
When downgrading, you no longer have scripts to do that for you so the newly installed 4.1.2 will not recognize anything so it will bootloop like crazy (I tried first to restore just the /system ... but all the other data was already affected by the update so was no longer usable).
My thoughts:
If you got the ota, and things messed up, try flashing the 4.2 factory image. That seemed to help me. If you're not rooted already, I would recommend becoming familiar with the adb backup command to backup apps before doing anything else. You have to unlock the boot loader to downgrade or flash the factory 4.2 image, and this will wipe the device.
Once you update either way, definitely take the time to root. You can then use adb restore or titanium backup to restore from the adb backup you made before unlocking.
Just be aware that adb backup doesn't seem to backup all apps, and that titanium backup isn't exactly fast parsing through a big adb backup file.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
step by step?
srry, very nooby questions:
how do i flash my nexus?
where do i find the factory image?
what is the backup tool?
ro_explorer said:
I just downgraded this morning. All your data will be wiped .. ALL YOUR DATA ... meaning, after I got back to 4.1.2 I was having 13GB of free space on the tablet (out of 13 possible) .
So, if you HAVE a nandroid from the 4.1.2 days, save it to your computer (along with all your files).
If you don't have a 4.1.2 nandroid, at least create now a backup repository with whatever tool you prefer and then save the respective files to PC.
Then, flash the factory image for 4.1.2.
Then copy all your files back to the internal memory, install the backup tool and restore your apps.
The reason behind this is that the update from 4.1.2 to 4.2 has some scripts that are porting the original /data and /sdcard mounts to the new structure used in 4.2
When downgrading, you no longer have scripts to do that for you so the newly installed 4.1.2 will not recognize anything so it will bootloop like crazy (I tried first to restore just the /system ... but all the other data was already affected by the update so was no longer usable).
Click to expand...
Click to collapse
HellcatDroid said:
1) unlock bootloader yes; root no, as you're going to overwrite the system anyways.
Also I'd suggest not using a toolkit, just download the factory image off google's page and run the "flash-all.bat"
2) Use Titanium Backup to backup all app data, wipe after flashing 4.1.2 and then restore apps + data with Titanium again
Click to expand...
Click to collapse
restoring my apps with Titanium Backup is unsuccessful , when i first tried a full app+data restore it freezes at 0 percent
and when i tried backuping app the missing apps , it worked but after i rebooted it . It went into a bootloop
Youssef Hossam said:
restoring my apps with Titanium Backup is unsuccessful , when i first tried a full app+data restore it freezes at 0 percent and when i tried backuping app the missing apps , it worked but after i rebooted it . It went into a bootloop
Click to expand...
Click to collapse
Assumed you are referring to downgrade from 4.2.1 to 4.1.2 and rooted to run TB, so the basic stock rom is up & running otherwise, correct?
Let's try Plan B instead - go into (Custom) Recovery and wipe dalvik cache first, then reboot. Give it a few minutes to settle and try to do your TB restore WITHOUT data, and see if it works. The /SD and/or /SD/0 directory structures are setup differently on the N7 and trying to retore with your custom settings will just make it more difficult & complicated. If this works, you can then try to selectively restore one or more with data and hopefully without going into endless bootloop again.
Plan C - go to Play Store, then Settings and "All" - you should see all of your Apps and what's installed, etc. - and install from there, it's semi-manual but it works for me 99.8% of the time when it would otherwise freeze within TB, especially true when switching custom Rom & kernels.
I usually manually copy & move back items such as documents, pictures & mp3's, etc. from standalone/usb backup drives or cloud storage back into the device once everything else are up & running properly.
Let us know if this helps & working for you or not.
Thankss !
Letitride said:
Assumed you are referring to downgrade from 4.2.1 to 4.1.2 and rooted to run TB, so the basic stock rom is up & running otherwise, correct?
Let's try Plan B instead - go into (Custom) Recovery and wipe dalvik cache first, then reboot. Give it a few minutes to settle and try to do your TB restore WITHOUT data, and see if it works. The /SD and/or /SD/0 directory structures are setup differently on the N7 and trying to retore with your custom settings will just make it more difficult & complicated. If this works, you can then try to selectively restore one or more with data and hopefully without going into endless bootloop again.
Plan C - go to Play Store, then Settings and "All" - you should see all of your Apps and what's installed, etc. - and install from there, it's semi-manual but it works for me 99.8% of the time when it would otherwise freeze within TB, especially true when switching custom Rom & kernels.
I usually manually copy & move back items such as documents, pictures & mp3's, etc. from standalone/usb backup drives or cloud storage back into the device once everything else are up & running properly.
Let us know if this helps & working for you or not.
Click to expand...
Click to collapse
Thanks for your help , but I think the problem was that there were apps in the backup only compatible with the custom ROM I had and android 4.2.1 xD
I restored the apps one by one , but I think if I deleted the extra custom rom apps , the process would have finished without any problems
Hi fellow people,
i'm a noob just made my xda account like 5 mins ago. I've been trying to search for my problem but I haven't really a found a direct answer. So yesterday I just got my Samsung Galaxy nexus update to 4.2.1. I was really excited until I started having the battery issues, screen lock issues, and overheating problem. I really don't like 4.2.1 and want to downgrade my version back 4.1.2. My carrier is the Mobicility (Canadian). I did not do anything previously with this phone such as rooting it, doing all the funky stuff that will void my warranty. I heard about flashing some google images to get back 4.1.2 but I'm not sure if I need to root or how to like do it through the gnex toolkit that mskip made. As well what if the difference between yakju and maguro? I heard if you flash the wrong image it will brick your phone or something like that. If there is a method without having to root it and lose all my contacts, then I would prefer that a lot.
Thanks,
mleung754
mleung754 said:
Hi fellow people,
i'm a noob just made my xda account like 5 mins ago. I've been trying to search for my problem but I haven't really a found a direct answer. So yesterday I just got my Samsung Galaxy nexus update to 4.2.1. I was really excited until I started having the battery issues, screen lock issues, and overheating problem. I really don't like 4.2.1 and want to downgrade my version back 4.1.2. My carrier is the Mobicility (Canadian). I did not do anything previously with this phone such as rooting it, doing all the funky stuff that will void my warranty. I heard about flashing some google images to get back 4.1.2 but I'm not sure if I need to root or how to like do it through the gnex toolkit that mskip made. As well what if the difference between yakju and maguro? I heard if you flash the wrong image it will brick your phone or something like that. If there is a method without having to root it and lose all my contacts, then I would prefer that a lot.
Thanks,
mleung754
Click to expand...
Click to collapse
You dont have to root but you need to UNLOCK the bootloader which will obviously erase all your data(and VOID your warranty). you can find the factory image here https://developers.google.com/android/nexus/images . just flash the appropriate image and you should be as good to go.
mleung754 said:
Hi fellow people,
i'm a noob just made my xda account like 5 mins ago. I've been trying to search for my problem but I haven't really a found a direct answer. So yesterday I just got my Samsung Galaxy nexus update to 4.2.1. I was really excited until I started having the battery issues, screen lock issues, and overheating problem. I really don't like 4.2.1 and want to downgrade my version back 4.1.2. My carrier is the Mobicility (Canadian). I did not do anything previously with this phone such as rooting it, doing all the funky stuff that will void my warranty. I heard about flashing some google images to get back 4.1.2 but I'm not sure if I need to root or how to like do it through the gnex toolkit that mskip made. As well what if the difference between yakju and maguro? I heard if you flash the wrong image it will brick your phone or something like that. If there is a method without having to root it and lose all my contacts, then I would prefer that a lot.
Thanks,
mleung754
Click to expand...
Click to collapse
mleung754,
You are posting in the wrong forum.
Asus Nexus 7 is not the same thing as a Samsung Galaxy Nexus.
Ignore mmystere68's remarks.
Forgive me if this question has been raised before but I haven't found anything relevant on a search.
Everytime I reset my Nexus 7 it seems to create a new layer of directories. I've had the N7 for a week and I've already got three layers of subdirectories. Files that have been downloaded might be in sdcard/0/download, or sdcard/0/0/download, or sdcard/0/0/0/download. I have to manually reset the directory for Titanium Backup, etc.
What's causing this and, more importantly, what can I do fix/stop it?
Thanks,
Ted.
this happens to me to. idk what causes it
Did you flash a custom room? If so did you upgrade your recovery to the latest version? If not that will be your problem.
Sent from my Nexus 7 using Tapatalk 2
How are you resetting? I have two users, power off occasionally, and have never had more than one level zero.
Sent from my Nexus 7 using xda app-developers app
leelaa said:
Did you flash a custom room? If so did you upgrade your recovery to the latest version? If not that will be your problem.
Click to expand...
Click to collapse
I'm running CM10 with ClockworkMod Recovery 6.0.1.0.
If I install the latest version of CMR it won't automatically clean up the directory structure, will it? What's the easiest/best way to deal with this?
Well this o file was holding 5 GB of space and I want to know why it happened? I had to reflash the stock ROM because of a bad kernal
Sent from my Nexus 7 using xda premium
Sounds like this does not apply to people running the stock rom at all.
Somehow we need a disclaimer on threads like this, so all the folks with unmodified Nexus 7's don't freak out.
Most likely if u are on xda your rooted and running some type of mod or ROM.
And mine is stock just rooted
sent from a galaxy far away
jetbruceli said:
Most likely if u are on xda your rooted and running some type of mod or ROM.
And mine is stock just rooted
sent from a galaxy far away
Click to expand...
Click to collapse
Maybe back in the old days - but XDA has outgrown it's modest beginnings.
I would love to see some real figures, but my guess would be no more than 10 percent of XDA members are running a custom rom.
That is based on just reading posts on the Nexus forums.
Like you - I am stock and rooted. I would need to see a real benefit to put a custom rom on - and stock is pretty good.
rmm200 said:
Maybe back in the old days - but XDA has outgrown it's modest beginnings.
I would love to see some real figures, but my guess would be no more than 10 percent of XDA members are running a custom rom.
That is based on just reading posts on the Nexus forums.
Like you - I am stock and rooted. I would need to see a real benefit to put a custom rom on - and stock is pretty good.
Click to expand...
Click to collapse
Stock on the nexus is awesome with nova launcher but as soon as aokp is running 4.2 I am going to run it. I use it on my s3 and makes it so much better.
Again though this O file came from re flashing the stock ROM which has never happened to me
sent from a galaxy far away
rmm200 said:
How are you resetting? I have two users, power off occasionally, and have never had more than one level zero.
Click to expand...
Click to collapse
I'm talking about a full wipe with factory reset from ClockworkMod Recovery, not just powering down.
rmm200 said:
Sounds like this does not apply to people running the stock rom at all.
Somehow we need a disclaimer on threads like this, so all the folks with unmodified Nexus 7's don't freak out.
Click to expand...
Click to collapse
I suspect you're right. This probably only applies to users have installed a custom recovery and/or custom ROM. I certainly never had the problem before I installed CM10.
As far as "freaking out" goes, why would anyone be concerned if they DIDN'T have multiple "0" directories? There are hundreds of posts on XDA about people having problems with their devices, but if you don't have that problem why would you be concerned?
Apparently the problem has to do with upgrading to Android 4.2. There is a lengthy discussion at http://forum.xda-developers.com/showthread.php?t=1999214.
I had upgraded with the OTA 4.2 then flashed CM10 (which is 4.1.2), went back to 4.2 and then re-flashed CM10. I think the easiest solution may be to back up internal storage /sdcard/, reformat internal storage, full wipe/factory reset, reflash 4.2, and finally restore files selectively. After that the problem should be solved. Maybe.
I had 10gb of stuff that after flashing a 4.2 rom (I think it was cleanrom 2.5)got sent into a 0 folder and then it was as if it set up its own file structure again as if all the folders that come stock it were there (empty) and then a 0 folder with all my previous stuff but all downloads and pictures that are taken on the new rom with this new folder setup get stored in the new folders and not the 0 folder. I'm running the latest twrp so that shouldn't be the problem and when I wipe I always do cache, dalvik, factory reset, and system (full wipe) so yeah. Hope this adds a little insight
Sent from my EVO using Tapatalk 2
Update your recovery to 6.0.1.9, You will face this problem if on older clockwork mod.
sahshah said:
Update your recovery to 6.0.1.9, You will face this problem if on older clockwork mod.
Click to expand...
Click to collapse
Could be then and my only issue was the double data it was using. I just deleted it.
I noticed this file when I was flashing a zip file and the selection for files in cwm was wierd and my downloads were in file O
Sent from my Nexus 7 using xda premium
OK so the O file is because now we have multiple users. When u flash over an existing ROM it makes the admin file 0 and when u add more users it gives them thier own file structure. This would be good for someone who wants to share their n7 but only give them certain rights!!
sent from a galaxy far away
/0/ is a user
if you were to add multiple users there would also be a /1/, /2/ etc
/0/ is the primary user, if you were to wipe and reflash with a custom recovery that didn't wipe all of the /sdcard/ too then it will probably get confused (unless the recovery was new and fixed this 'bug') and then create a /0/0/ etc.
Lennyuk said:
/0/ is a user
if you were to add multiple users there would also be a /1/, /2/ etc
/0/ is the primary user, if you were to wipe and reflash with a custom recovery that didn't wipe all of the /sdcard/ too then it will probably get confused (unless the recovery was new and fixed this 'bug') and then create a /0/0/ etc.
Click to expand...
Click to collapse
Nit: Second user is /10, not /1. Third user is /20 - I think.
I have a nexus 7 running 4.1.2 and Aokp ROM.
Can I update to 4.2 and flash to CM 10.1 without losing any data or settings?
Can someone point me in the right direction to do this step by step.
I have clockworkmod and titanium backup installed but I have not made a backup or transfered data to my PC yet.
Thanks in advance for the help.
I used to come to this site when it first started and I had my T-Mobile XDA running windows.
Sent from my Nexus 7 using xda app-developers app
When I made the exact same transition (4.1 aokp to CM10.1), the upgrade completely killed my filesystem.
I can't post links yet, so just google "twrp and 4.2", the first result explains it all.
I suggest you make a backup with Titainium and/or completely wipe the device before you install 10.1
timpattinson said:
When I made the exact same transition (4.1 aokp to CM10.1), the upgrade completely killed my filesystem.
I can't post links yet, so just google "twrp and 4.2", the first result explains it all.
I suggest you make a backup with Titainium and/or completely wipe the device before you install 10.1
Click to expand...
Click to collapse
I want to go to 4.2 and cm 10.1. If i make a complete back up or nandroid back up and update everything will i be able to restore all my data and apps from my nandroid?
chriskob said:
I want to go to 4.2 and cm 10.1. If i make a complete back up or nandroid back up and update everything will i be able to restore all my data and apps from my nandroid?
Click to expand...
Click to collapse
If you have Titanium Backup Pro you can.
Ok I made a titanium backup of all apps and data. I also created a update.zip file and copied everything to my pc.
Now when I go into recovery to flash 4.2.1 I get a error 7. I read that it's not matching the required md5 or so. I guess I have to find a rooted version of 4.2.1???
Thanks,
Chris
Sent from my iPhone 4 using Tapatalk
Well i have rooted nexus 7 wifi with cwm installed
I wanna update my tablet to android 4.3 and dont wanna loose any data itried updating via ota and cwm via zip
Getting status 7 error kindly help me out solving this issue without loosing data
Sent from my Nexus 7 using Tapatalk HD
pleasant said:
Well i have rooted nexus 7 wifi with cwm installed
I wanna update my tablet to android 4.3 and dont wanna loose any data itried updating via ota and cwm via zip
Getting status 7 error kindly help me out solving this issue without loosing data
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Do backup of your apps with Titanium backup. backup your SDCARD to a PC, wipe, flash fresh 4.3 and then restore data/apps... you can't use OTA because it checks your system for modifications.... it is good to wipe a device once in a while anyway, especially if you tweak it a lot
dalanik said:
Do backup of your apps with Titanium backup. backup your SDCARD to a PC, wipe, flash fresh 4.3 and then restore data/apps... you can't use OTA because it checks your system for modifications.... it is good to wipe a device once in a while anyway, especially if you tweak it a lot
Click to expand...
Click to collapse
Well i havent done any tweaks i had installed dr beats mod since then it has become issue to update via ota
Last time while updating 4.2.2 i was having the same issue but some guy over here helped me updating it to 4.2.2 via zip file and the good part was it didnt gave any status7 error neither it wiped any of my data
I dont wanna connect the device to pc for just update though i have made backup via rom manager do i need to make backup using titanium backup as well ?
Sent from my Nexus 7 using Tapatalk HD
Yes. Dalanik's suggestion is that you backup your apps and data, then wipe, then flash 4.3, then restore apps and data. To do this, you need a backup of your apps and data alone, without the Rom. That's what titanium backup does. If you were to try this with the Nandroid backup you made using Rom manager, you'd just end up back where you started.
pleasant said:
Well i havent done any tweaks i had installed dr beats mod since then it has become issue to update via ota
Last time while updating 4.2.2 i was having the same issue but some guy over here helped me updating it to 4.2.2 via zip file and the good part was it didnt gave any status7 error neither it wiped any of my data
I dont wanna connect the device to pc for just update though i have made backup via rom manager do i need to make backup using titanium backup as well ?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Well, yes, beats mod qualifies as a "tweak" or a changed system
Yes, I know what you;'re saying, with 4.2.2 I think somebody posted modified OTA zip and it didn't check for changes (or not ALL anyway) I updated like that too, because I didn't want to lose my data. But now I just did Titanium and reset the whole thing.
IF you mean nandroid backup, that is good, but that is the image of your whole system. You need backup of each application so you can restore them.
What I did is just waited for most of the apps to re-install from the google play automatically and then restored the rest from Titanium.
Hi.
I have multiple user profiles on my Nexus 10, and as you know the is no good way to backup/restore multiple accounts.
I'm currently running stock 4.2.2, and is wondering what the best way to upgrade to 4.3 is? Should I just use the system update and reroot the device afterwards? Will this keep qll my profile data etc?
How did you do it?
Sent from my Nexus 10 using XDA Premium HD app
No one have any suggestions?
Sent from my Nexus 4 using xda premium
ChosSimbaOne said:
No one have any suggestions?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I was wondering the same thing
Upgrading to 4.3
I also would like to know what to do. I am currently on 4.22 rooted and running twrp as a custom recovery. Should I use the OTA upgrade to 4.3 and then root or flash the pre rooted AOSP 4.3. I don't want to lose my data or settings
rocky3 said:
I also would like to know what to do. I am currently on 4.22 rooted and running twrp as a custom recovery. Should I use the OTA upgrade to 4.3 and then root or flash the pre rooted AOSP 4.3. I don't want to lose my data or settings
Click to expand...
Click to collapse
Okay so what I finally did was this: I don't know if you rooted+unlocked it with the wugfresh tool but I had done that a few months ago.
So I opened the nexus tool rootkit from wugfresh --> it updated to the latest version
After that I made a full back up of my data and my system
Then I pressed Flash Stock +Unroot after that it asked if I wanted to install the 4.3 after unrooting
I selected that and followed the orders etc etc
It all went pretty smoothly and now I have an unlocked + unrooted 4.3 nexus 10
You should first check whether fastboot is configured well and update some stuff in de Android SDK manager (I don't know which stuff and I'm not sure if that updating is something that you must do, I'm guessing it won't be necessary ) But the fastboot thing is really important I guess.
Also maybe you better wait till somebody with more computer knowledge answers your questions, because I don't know what I'm doing
I like to screw around with my devices and it hasn't had a bad consequence yet. Just try to google everything if your not totally sure about it.
Tangonaf said:
Okay so what I finally did was this: I don't know if you rooted+unlocked it with the wugfresh tool but I had done that a few months ago.
So I opened the nexus tool rootkit from wugfresh --> it updated to the latest version
After that I made a full back up of my data and my system
Then I pressed Flash Stock +Unroot after that it asked if I wanted to install the 4.3 after unrooting
I selected that and followed the orders etc etc
It all went pretty smoothly and now I have an unlocked + unrooted 4.3 nexus 10
You should first check whether fastboot is configured well and update some stuff in de Android SDK manager (I don't know which stuff and I'm not sure if that updating is something that you must do, I'm guessing it won't be necessary ) But the fastboot thing is really important I guess.
Also maybe you better wait till somebody with more computer knowledge answers your questions, because I don't know what I'm doing
I like to screw around with my devices and it hasn't had a bad consequence yet. Just try to google everything if your not totally sure about it.
Click to expand...
Click to collapse
Did this method made you loose your data/settings? Think this is what i will try. Nandroid backup device, flash stock recovery run ota upgrade, and install custom recovery and root afterwards. Hope this woill work
Yes I lost all my data nut I also had backed up al my data with backup data+media of the wugfresh tool. Both backing up the data and retrieving it afterwards took a long time but I had patience and now I have almy data back again
Verstuurd vanaf mijn Nexus 10 met Tapatalk 4
I'm not sure restoring the data will be stable, since the directories structure has been slightly changed between 4.2 and 4.3.
I also has multiple accounts. I've tried to backup the users apps with Titanium backup. I thought I would be able to create myself the user profiles, then restore the apps with Titanium. However, this didn't work since Titanium is unable to correctly backup and restore apps for multiple user accounts.
I ended up installing manually the apps for the other user.
Also note that even for your main profile, restoring the apps may require restoring the device uid. Titanium is able to do that if you backup its settings.
So far my atempt left me with a nexus that wont boot, dont know if it is the updated bootloader, but it vibrates a lot at boot, and then goes to bootloader. Think i better just flash the 4.3 stock image and reroot and restore what i can :-/