Related
Hi,
I am trying to restore a couple of nandroid backups, but a Device Administrator app gone "quirky" seems to materialize no matter what I do. I did a CWM Wipe, restored the nandroid backup before the app went bad. However that did not work, the app was still misbehaving. So I wiped again, restored a nandroid backup from before I had installed the app. Still the app shows up again. It has in effect locked me out of the device.
Can anyone tell what can I do to get rid of the app?
Are these Device Admin app supposed to persist like this? Or am I doing something wrong?
Do I need to choose a different wipe mode (I chose the normal one, which wipes /data/, /cache etc). I did not try to wipe /cache separately, as the first wipe does that by itself. Neither did I wipe the dalvik cache, as I thought they are not relevant here. I don't see any relevant files in the sdcard either, though how the app reappears in the nandroid restore before it was installed is a mystery.
Should I mount more partitions before wiping, like the data/cache etc.
Since the wipes don't seem to make it go away, I am not even sure flashing a different ROM would get rid of this app either, however I can try that (since I was planning to anyway, before this mishap). If that doesn't work either, I might just have the most unusual case of bricking ever.
The XDA forum does not seem to be much info about device-admin apps and my search-fu is not good enough today to find anything directly relevant about the other stuff.
PS. btw the app actually modifies the lockscreen. So I don't actually see the files it has with the pre-app restore, however the lockscreen still comes up, perhaps because of some remanant of the app or because of a setting it left in there somewhere.
efs?
Just to add more info, I see some files in /efs, which look relevant to the lockscren/ They have file names like this "/efs/cryptoprop_lockscreen".
Would these files store the data this app stored. I fortunately have an EFS backup, should I consider restoring these files.
If someone doesn't know the answer, can they suggest which devs would be good to ask about this.
AnDruid said:
Hi,
I am trying to restore a couple of nandroid backups, but a Device Administrator app gone "quirky" seems to materialize no matter what I do. I did a CWM Wipe, restored the nandroid backup before the app went bad. However that did not work, the app was still misbehaving. So I wiped again, restored a nandroid backup from before I had installed the app. Still the app shows up again. It has in effect locked me out of the device.
Can anyone tell what can I do to get rid of the app?
Are these Device Admin app supposed to persist like this? Or am I doing something wrong?
Do I need to choose a different wipe mode (I chose the normal one, which wipes /data/, /cache etc). I did not try to wipe /cache separately, as the first wipe does that by itself. Neither did I wipe the dalvik cache, as I thought they are not relevant here. I don't see any relevant files in the sdcard either, though how the app reappears in the nandroid restore before it was installed is a mystery.
Should I mount more partitions before wiping, like the data/cache etc.
Since the wipes don't seem to make it go away, I am not even sure flashing a different ROM would get rid of this app either, however I can try that (since I was planning to anyway, before this mishap). If that doesn't work either, I might just have the most unusual case of bricking ever.
The XDA forum does not seem to be much info about device-admin apps and my search-fu is not good enough today to find anything directly relevant about the other stuff.
PS. btw the app actually modifies the lockscreen. So I don't actually see the files it has with the pre-app restore, however the lockscreen still comes up, perhaps because of some remanant of the app or because of a setting it left in there somewhere.
Click to expand...
Click to collapse
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
pulser_g2 said:
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
Click to expand...
Click to collapse
Thanks for the help pulser_g2. I am still concerned about the files i saw in /efs related to the lockscreen (see my second post). Would the stock ROM overwrite settings/configuration inside /efs (I guess since the IMEI etc are all in there, that might not be the case)?
Got through finally.
pulser_g2 said:
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
Click to expand...
Click to collapse
OK this worked.
However after I Odin flashed the stock rom and rebooted, I got this
1. First got a different kind of lockscreen.
2. I entered the wrong password five times (after trying the Device Admin alternate password, my Google password, a new 2-step auth password from google) .
3. it said something about wiping sd card. I couldn't catch it (I should probably have videoed this using my point and shoot camera, but this did not strike me then as it was 2am).
4. I was hoping that the stock ROM will boot, cause it stayed on the Samsung logo for too long. (I had already ordered my USB Jig on ebay anyway, but it could have taken time because of my being far off from the seller.). Finally I got the Android Welcome screen and I let out my breath.
In any case, things seem to ok right now. I feel a slight slowness in the rooted stock ROM from my earlier rooted stock ROM, but I am gonna flash a custom ROM later anyway. Thanks a lot for your help pulser.
Hello, I always find the people on this corner of xda very helpful. As usual, I think I know what I'm doing, but I'd like to check that I am proceeding in the right direction.
I've been using Mik's Cyanogen ROMs on my Optimus One. That's going well. But I need to SIM unlock my phone and I need to go back to a stock ROM to input the codes (please let me know if this is incorrect).
Before installing Mik's ROM, I performed a Nand backup. I have boot, cache, data, recovery and system img files. I think I can flash these through recovery and I should be back to stock.
Do I lose my apps and settings by doing this? Do I need to clear any caches?
What about returning to Cyanogen after I unlock my phone... Do I have to root my phone again or will I still be able to flash using recovery?
Using Clockwork, I just backed up my current ROM. I assume I will be able to restore from this later.
Is there anything else I should be aware of?
Thanks for answering my questions / clearing up my confusion.
Hello, I always find the people on this corner of xda very helpful. As usual, I think I know what I'm doing, but I'd like to check that I am proceeding in the right direction.
I've been using Mik's Cyanogen ROMs on my Optimus One. That's going well. But I need to SIM unlock my phone and I need to go back to a stock ROM to input the codes (please let me know if this is incorrect).
this is correct
Before installing Mik's ROM, I performed a Nand backup. I have boot, cache, data, recovery and system img files. I think I can flash these through recovery and I should be back to stock.
Do I lose my apps and settings by doing this? Do I need to clear any caches?
to revert back to stock, you must wipe data/factory reset, cache, and dalvik cache. you will lose your settings. as for your apps, you can back them up with titanium backup and restore them after you have restored your backup.
What about returning to Cyanogen after I unlock my phone... Do I have to root my phone again or will I still be able to flash using recovery?
when you restore your backup of the stock rom, you will still have root. i dont think unlocking your phone will cause you to lose root. your root access and custom recovery will still be intact
Using Clockwork, I just backed up my current ROM. I assume I will be able to restore from this later.
yes this is true
Is there anything else I should be aware of?
just to be on the safe side, please list the steps you are going to follow
Thanks for answering my questions / clearing up my confusion.
Thanks for the quick answer...
I on my sd card, I have a /clockwork directory with two subdirs. One is my original backup that I made before first installing Cyanogen. The other is the one I just made. Both contain boot, cache, data, recovery and system img files. The difference is that with my new backup the image files have an extra yaffs2 suffix: cache.img (stock) but cache.yaffs2.img (Cyanogen). Any problem here?
1. boot into recovery
2. restore stock from my sdcard using nandroid and wipe caches as you indicated
3. reboot, enter unlock code
4. reboot into recovery
5. restore current ROM from my sdcard using nandroid and again wipe the same caches
6. reinstall / restore apps (I'm not using Titanium, instead I backed up the list of installed apps)
Will I need to find and reinstall the GoogleApps (Market, etc) or will they come with the backup of my current ROM?
Pretty simple really. This make sense?
Thanks for the quick answer...
I on my sd card, I have a /clockwork directory with two subdirs. One is my original backup that I made before first installing Cyanogen. The other is the one I just made. Both contain boot, cache, data, recovery and system img files. The difference is that with my new backup the image files have an extra yaffs2 suffix: cache.img (stock) but cache.yaffs2.img (Cyanogen). Any problem here?
there might be a problem. what clockworkmod version did you use to make the backup of the stock rom? if i remember correctly, using cwm 3.x.x.x backs up a certain way (and also does not have the yaffs2 suffix) and using cwm 5.x.x.x backs up a different way (with the yaffs2 suffix) so backups may not be "inter"compatible (more info on that here). however, you can just flash back cwm 3.x.x.x right now (you can do it using rom manager), restore your stock rom backup, do the following steps, flash back cwm 5.x.x.x, then restore your backup
1. boot into recovery
2. restore stock from my sdcard using nandroid and wipe caches as you indicated (i recommend wipe first then restore)
3. reboot, enter unlock code
4. reboot into recovery
5. restore current ROM from my sdcard using nandroid and again wipe the same caches
(same here again, wipe first then restore)
6. reinstall / restore apps (I'm not using Titanium, instead I backed up the list of installed apps)
Will I need to find and reinstall the GoogleApps (Market, etc) or will they come with the backup of my current ROM?
i think you will have to flash gapps again
Pretty simple really. This make sense?
looks good (how sure am i? id say 80-90%. it definitely makes sense, but i have never done this before)
Good good. It's getting late so I'll tackle this tomorrow. Thanks for the detailed help... I'm glad I asked before going at it.
sweetnsour said:
looks good (how sure am i? id say 80-90%. it definitely makes sense, but i have never done this before)
Click to expand...
Click to collapse
I followed your instructions (I downgraded Clockwork before starting) and the 10-20% chance of you being wrong came true... but in a good way
Restoring from the backup brings everything back: apps, settings, contacts, SMSs etc. So it was actually even easier than you suggested since I didn't have to use my backups at all.
Thanks again for the tips!
bosth said:
I followed your instructions (I downgraded Clockwork before starting) and the 10-20% chance of you being wrong came true... but in a good way
Restoring from the backup brings everything back: apps, settings, contacts, SMSs etc. So it was actually even easier than you suggested since I didn't have to use my backups at all.
Thanks again for the tips!
Click to expand...
Click to collapse
glad it worked out for you i am assuming your phone is now unlocked right?
sweetnsour said:
glad it worked out for you i am assuming your phone is now unlocked right?
Click to expand...
Click to collapse
Yes... when I was back in stock I could access the unlock menu by entering 2945*#500# on my keypad. The SIM unlock code that I have worked fine. I haven't actually tested with another SIM card but the phone claimed to have been unlocked, so I should be good to go.
Is there a way to do a complete backup before rooting the device?
Thanks.
If I find something I will let you know
Sent from the only smartphone designed by Chuck Norris
If i am understanding it correctly...Rooting doesnt affect anything in the system or the phone..just lets you access the root of the system..so technically nothing will change at all...you will have everything same as it was before rooting...
If u are trying to flash a custom rom, for which you need to have custom recovery....Then you can take nandroid backup...of the whole system (with app and data)..
Unfortunately, there is no way to make a complete backup of the phone without customizing the device slightly using 'unofficial methods'.
In order to make a complete backup, you need to replace the recovery menu (this is the menu you get if you hold down the Power&Vol+&Vol- buttons with the phone completely off).
It is also supposedly possible to get a full backup with the phone booted but you have to have root so that apps can access directories that are normally system protected (this however is not recommended).
So unfortunately, you have to do one or the other in order to get a complete backup and the preferred method is to install the CWM recovery menu (now at beta 4 for the Note if I am correct), then do a complete backup, then flash the modified kernel that has root already enabled. Feel free to correct me as I have not yet gotten around to doing this yet.
littlewierdo said:
Unfortunately, there is no way to make a complete backup of the phone without customizing the device slightly using 'unofficial methods'.
In order to make a complete backup, you need to replace the recovery menu (this is the menu you get if you hold down the Power&Vol+&Vol- buttons with the phone completely off).
It is also supposedly possible to get a full backup with the phone booted but you have to have root so that apps can access directories that are normally system protected (this however is not recommended).
So unfortunately, you have to do one or the other in order to get a complete backup and the preferred method is to install the CWM recovery menu (now at beta 4 for the Note if I am correct), then do a complete backup, then flash the modified kernel that has root already enabled. Feel free to correct me as I have not yet gotten around to doing this yet.
Click to expand...
Click to collapse
viny2cool said:
If i am understanding it correctly...Rooting doesnt affect anything in the system or the phone..just lets you access the root of the system..so technically nothing will change at all...you will have everything same as it was before rooting...
If u are trying to flash a custom rom, for which you need to have custom recovery....Then you can take nandroid backup...of the whole system (with app and data)..
Click to expand...
Click to collapse
Ok, Thanks guys. I guess I'll root first then make a full nandroid backup.
Hi
Trying to root my table tand get it to work, I have not succeeded something operational yet. I have made a root & CWD sd card, and in the process had backed up my tablet. I copied thgis backup to my PC as I had to try different things with the sd card.
So now I d like to restore (to start afresh) but... I google it around, and dont find any procedure!?
I am sure it is known... and am dummy... but can't invent neither.
I need use those files, because I still can't read .apks and try the apk based nook restore.
How should I go?
Your help appreciated
Thanks, Agnes
Restore method did not work....²
I have found my 3 neurons and realized I could just re do a CWD sd card, do a backup, and then take the card to my PC and add the other backup aside there (they are orgnaized by folders and date)
Then back to the tablet, go CWD / restore... but I only get a MD5 error and it does not want. Same with advanced restore.
I finally found this very simple method from Adam to restore to 1.4.0
http://forum.xda-developers.com/showthread.php?t=1402190
It semt it worked, but then when it starts again... I get the same broken rooted / whatever I have now .
Is your device 16GB or 8GB model? depending on that i can tell you what to do.
16GB model has more development and some modified stock ROMs , i even made 1 of them check here:
http://forum.xda-developers.com/showthread.php?t=1494367
~ Veronica
lavero.burgos said:
Is your device 16GB or 8GB model? depending on that i can tell you what to do.
16GB model has more development and some modified stock ROMs , i even made 1 of them check here:
http://forum.xda-developers.com/showthread.php?t=1494367
~ Veronica
Click to expand...
Click to collapse
Veronica,
You wouldn't happen to have an un-modified stock ROM would you?
LonelyTV said:
Veronica,
You wouldn't happen to have an un-modified stock ROM would you?
Click to expand...
Click to collapse
You want a sotck stock unrooted one? yet you need to reply me if your device is 8GB or 16GB model.
Depending on that i can upload it for you , but later 'cause right now i've got to go.
~ Veronica
lavero.burgos said:
You want a sotck stock unrooted one? yet you need to reply me if your device is 8GB or 16GB model.
Depending on that i can upload it for you , but later 'cause right now i've got to go.
~ Veronica
Click to expand...
Click to collapse
Yeah, an unrooted unmodified stick would be great. I've got a 16gb model.
Thanks.
16Gb device now messed uo....
Hi Veronica, thanks for the reply. I am deseprately in need of expert advice here, instead of guessing and trying...
I have a 16 GB Nook Tablet, that was bought with 1.4.0.
I now seriously again need to make a restore, as I did some bad mismanipulation and my tablet is now out of order:-(
One of my best chance I guess would be use one of the backups I have (I have several copied on my HD), but after I formatted and wrote on my SD card several times (is this the reason?), now when I try restore, I have this MD5 error.
I hope I would not run into other problems, as it seems my prop.build may have changed in the process....!
May I ask you to have a look what I did, and then confirm it would be wise try the restore you provided in the thread?
The history what I did:
- I initially had a 1.4.0 with some tweaks to sideload apps, and could no more sideload with 1.4.2 of course (and that is all I need: be able get Kindle, Le Monde, and few other apps!). I understood I had to root and was ready to try get CM7 on my internal drive, and tried a few things (Rooting with Indirect's method, ...), and could not get it to work, until I got very close:
- I restored 1.4.0 using this thread restore 1.4.0 from Adam Outler. It worked fine and apparently erased some of the problems I had that were previously preventing me to move with rooting etc.
- Then I used Albert Wertz's Backup of a rooted 1.4.0. It worked. It seems it had already OTA bloked (displaying version 9.9.9 or so)
- Then I was to install CM7 using this tutorial from ebook-reader, based on this Celtic XDA thread ("team B") (choosing the internal method) , and used the CWM flasher apk. That is where somewhere I did a mistake: after backing up and erasing all data, I somehow stupidly rebooted and got in trouble, and restored the old B&N I don't know how.
- Willing to go back to stage 1, I tried using the 1.4.0 basic restore from Adam Outler, but that did not work anymore, like if my build.prop had been changed in the process (where?)
It said "assert.failed: getprop ("ro.product.device" = blaze" or something alike.
- Then I got a long powercut (am in Africa) and some sleep
- The worse is, the NOOK does not boot and work anymore at all, it is stuck on "read forever" screen
- The curse is, I cant use other restores I have, it says MD5 mismatch
- I also can't use simple root procedures (with CWM and installing zips), as my basic system seems corrupted.
I guess a proper restore may work if I manage to do it, but I wonder what happened with my prop.build and why it was mentionned up there (was it changed in some of the process) - and whether it will create more trouble.
Your advice will be very precious!
Thanks, Agnes
agnes00777 said:
Hi Veronica, thanks for the reply. I am deseprately in need of expert advice here, instead of guessing and trying...
I have a 16 GB Nook Tablet, that was bought with 1.4.0.
I now seriously again need to make a restore, as I did some bad mismanipulation and my tablet is now out of order:-(
One of my best chance I guess would be use one of the backups I have (I have several copied on my HD), but after I formatted and wrote on my SD card several times (is this the reason?), now when I try restore, I have this MD5 error.
I hope I would not run into other problems, as it seems my prop.build may have changed in the process....!
May I ask you to have a look what I did, and then confirm it would be wise try the restore you provided in the thread?
The history what I did:
- I initially had a 1.4.0 with some tweaks to sideload apps, and could no more sideload with 1.4.2 of course (and that is all I need: be able get Kindle, Le Monde, and few other apps!). I understood I had to root and was ready to try get CM7 on my internal drive, and tried a few things (Rooting with Indirect's method, ...), and could not get it to work, until I got very close:
- I restored 1.4.0 using this thread restore 1.4.0 from Adam Outler. It worked fine and apparently erased some of the problems I had that were previously preventing me to move with rooting etc.
- Then I used Albert Wertz's Backup of a rooted 1.4.0. It worked. It seems it had already OTA bloked (displaying version 9.9.9 or so)
- Then I was to install CM7 using this tutorial from ebook-reader, based on this Celtic XDA thread ("team B"), and used the CWM flasher apk. That is where somewhere I did a mistake: after backing up and erasing all data, I somehow stupidly rebooted and got in trouble, and restored the old B&N I don't know how.
- Wwlling to go back to stage 1, I tried using the 1.4.0 basic restore from Adam Outler, but that did not work anymore, liek if my build.prop had been changed in the process (?)
It said "assert.failed: getprop ("ro.product.device" = blaze" or something alike.
- The worse is, the NOOK does not boot and work anymore at all, it is stuck on "read forever" screen
- The curse is, I cant use other restores I have, it says MD5 mismatch
- I also can't use simple root procedures (with CWM and installing zips), as my basic system seems corrupted.
I guess a proper restore may work if I manage to do it, but I wonder what happened with my prop.build and why it was mentionned up there (was it changed in some of the process) - and whether it will create more trouble.
Your advice will be very precious!
Thanks, Agnes
Click to expand...
Click to collapse
Thanks for post the whole history of what you've done 'cause pfff that saves a lot of time.
Now in this part "after backing up and erasing all data, I somehow stupidly rebooted and got in trouble"
1. Did you get to flash CM7 succesfully
2. When you mention you backed up means you backed up CM7?
3. when you mention erasing all data you mean only wipe data (factory reset) or did you wiped maybe formatted anything else?
4. What method did you use to format your sdcard
Edit: i have a MIUI backup that i made for a guy that could not install it with the other way (install .zip) of the same ROM. So at list try it for now to see what happens, if it works then go ahead and flash back the ROM you want, and always make sure to check the md5 of what you download.
http://minus.com/mwIltnw1I/4f - NT_MIUI_Tweaks_backup.zip | md5: 3518f9a3289ca6e97b569777873b899b
* Uncompress the .zip and put the folder (do not change the name of the folder) in your sdcard and flash in CWM >> backup and restore >> restore
~ Veronica
LonelyTV said:
Yeah, an unrooted unmodified stick would be great. I've got a 16gb model.
Thanks.
Click to expand...
Click to collapse
*This is a flashable .zip:
http://minus.com/mwIltnw1I/5f - NT_stock_1.4.0_B&N_ 16GB.zip | md5: f8ae4f8e88e0ced9f252e9440df3910c
~ Veronica
lavero.burgos said:
Now in this part "after backing up and erasing all data, I somehow stupidly rebooted and got in trouble"
~ Veronica
Click to expand...
Click to collapse
Thanks Veronica. Here is as much as I remember:
1. Did you get to flash CM7 succesfully?
No. While following the procedure, I did some mistake after backing up and before even trying to installing CM7. I did not realize I was in CWM within my existing rooted 1.4.0 (using the .apk), so somewhere I wiped and rebooted... to realize I was rebooting into nothing! Or actually into the original 1.4.0 B&N. And then I did some attempts to go back step by step (like restoring that 1.4.0 from Adam then the rooted 1.4.0 from Albert) and somehow went into more troubles.
2. When you mention you backed up means you backed up CM7?
No, since I did not go so far as to install CM7.
I have a backup of my initial (tweaked) 1.4.2 system, then one of Albert rooted 1.4.0 (not mine), then another one of a Nook normal OS that worked (not sure, I think 1.4.2) at some point later.
These backups were OK, I used at some point, I don't understand why then I got this MD5 errors.
3. when you mention erasing all data you mean only wipe data (factory reset) or did you wiped maybe formatted anything else?
I used the command within CWM, both to wipe data and cache
4. What method did you use to format your sdcard
I usually use Acronis Disk Manager, a quite powerful programme to change partitions on disks and also handle formatting. When I really want to make sure, I first use HP USB formatting tool, and then sometimes check on Acronis to get the partitions I want. I am not sure in what order I did that time, but was not using partitionning in fact.
I will redo it all again as I wonder if it is not a mistake on the disk that lets it misread the MD5, as I think my backups were fine.
I don't undestand:
- why my MD5 are wrong, and is it something I can fix by properly reformatting mys disks
- what is this story with "assert.failed: getprop ("ro.product.device" = blaze" and where I may have changed the build.prop. Is it somehting that will bother me further or should push me into one direction rather than another.
I will try your MUI backup. (What means MUI?). (It may take ma a day or 2 to download this through Lesotho poor internet :-(
Thanks and wil tell you what happens!
agnes00777 said:
Thanks Veronica. Here is as much as I remember:
1. Did you get to flash CM7 succesfully?
No. While following the procedure, I did some mistake after backing up and before even trying to installing CM7. I did not realize I was in CWM within my existing rooted 1.4.0 (using the .apk), so somewhere I wiped and rebooted... to realize I was rebooting into nothing! Or actually into the original 1.4.0 B&N. And then I did some attempts to go back step by step (like restoring that 1.4.0 from Adam then the rooted 1.4.0 from Albert) and somehow went into more troubles.
2. When you mention you backed up means you backed up CM7?
No, since I did not go so far as to install CM7.
I have a backup of my initial (tweaked) 1.4.2 system, then one of Albert rooted 1.4.0 (not mine), then another one of a Nook normal OS that worked (not sure, I think 1.4.2) at some point later.
These backups were OK, I used at some point, I don't understand why then I got this MD5 errors.
3. when you mention erasing all data you mean only wipe data (factory reset) or did you wiped maybe formatted anything else?
I used the command within CWM, both to wipe data and cache
4. What method did you use to format your sdcard
I usually use Acronis Disk Manager, a quite powerful programme to change partitions on disks and also handle formatting. When I really want to make sure, I first use HP USB formatting tool, and then sometimes check on Acronis to get the partitions I want. I am not sure in what order I did that time, but was not using partitionning in fact.
I will redo it all again as I wonder if it is not a mistake on the disk that lets it misread the MD5, as I think my backups were fine.
I don't undestand:
- why my MD5 are wrong, and is it something I can fix by properly reformatting mys disks
- what is this story with "assert.failed: getprop ("ro.product.device" = blaze" and where I may have changed the build.prop. Is it somehting that will bother me further or should push me into one direction rather than another.
I will try your MUI backup. (What means MUI?). (It may take ma a day or 2 to download this through Lesotho poor internet :-(
Thanks and wil tell you what happens!
Click to expand...
Click to collapse
Try formatting your sdcard again, i recommend SDFormatter. Sometimes sdcard can be the cause of many weird errors and issues.
Then copy back one of your backups within clockworkmod >> backup folder
If no go with that then try the following.
* First you need adb working
Here is a tutorial i made about it: http://forum.xda-developers.com/showpost.php?p=22049356&postcount=1
* Plug your NT to your PC using USB cable
* Download the file attached which is 1.4.0 stock build.prop, uncompress it, put it in the same folder adb is located and push it using adb while in CWM
> cd path-of-adb-tools
> adb devices
(verify that you get a code with numbers and letters)
> adb remount
(if this command does not work for you then please mount /system manually from mount&storage > Mount /system in CWM)
> adb push build.prop /system
* Unplug cable
* Try Adams acclaim_update.zip again ( preferably with nothing else in your sdcard only that .zip
* Report back
~ Veronica
OK I now was finally able to download the files.
- I guess I'll try first what you suggested with the MIUI backup after a proper reformat.
(I am just not sure which CWD file to use, as many dont leave any space on the card to put backups....)
- Then the ADB method if the 1st one does not work.
Though, part of the ADB tutorial is this "ADB root hijack" where they say you must already be rooted - that is not my case....
I'll try do tomorrow... and report! So glad to have your help here.
Successfully restored MIUI backup... what next?
YES!
@Veronica, I have been able to restore your MIUI backup!
I am not sure what it is... it looks like for a phone.... but it seems Market is working YEAH! 1st time on this Nook!!!!
Veronica you are a queen !!!
May I ask you what should be my next step now?
As a reminder, I basically want to get here Kindle (because I bought this Nook for Xmas for my Mozambican husband without realizing B&N does not have any Portuguese books, while Amazon does) and a few more apps I like. So this would do! But I d like make sure:
- my system is more or less stable
- I don't get messed up with more OTA updates
So I wonder:
- is this system recommendable? This is rooted, right? Should I prefer Launcher or Zeam Launcher here?
- should I rather use another system? Go into CM7?
Since I dont have even any Nook here behind, I am afraid of more troubles following the normal procedure, should I?
- Do I need at all to set the normal version of Nook behind (like I could use with the Nook button app) - in fact, I don't really care...
HELP PLEASE!!!! Nook 8Gb!
Can somebody help me? I bricked my nook tablet 8Gb!!
This is the whole story:
1) Rooted my NT
2) Used this apk to install CWM
http://forum.xda-developers.com/showthread.php?t=1458630
3) Tried to flash CyanogenMod 7 ROM but while it was flashing the tablet blacked out and rebooted
4) Now the tablet is stuck at the READ FOREVER screen
5) I can boot in CWM holding power+N button, but it can't flash anything, it freezes anytime I try to flash something.
6) I followed these 2 guides to unbrick my NT but they didn't work
http://forum.xda-developers.com/showthread.php?t=1470910
http://forum.xda-developers.com/showthread.php?t=1562130
Can anyone help me restore my NT at least to stock???
Please I'm desperate!!!!
@JohnDorian, Seems you got very similar problem to mine...!
It seems we got the same problem trying to do the same thing... So the same solution may work? (the only difference beeing I have not tried the unbrick mehods you did)
What I just did with Veronica's guidance, and worked for me:
- I created a 50MB sd card to boot into CWD, using this
- booted into CWM with it
- copied onto another SD card the MIUI backup Veronica provided earlier in this thread:
http://minus.com/mwIltnw1I/4f - NT_MIUI_Tweaks_backup.zip | md5: 3518f9a3289ca6e97b569777873b899b
- inserted it and did restore. It just worked and provided something that seems acceptable!
And at least, next steps may be possible...
I hope it works with you too!
Thank you for your answer!
Will this work also with my 8Gb NT?
agnes00777 said:
YES!
@Veronica, I have been able to restore your MIUI backup!
I am not sure what it is... it looks like for a phone.... but it seems Market is working YEAH! 1st time on this Nook!!!!
Veronica you are a queen !!!
May I ask you what should be my next step now?
As a reminder, I basically want to get here Kindle (because I bought this Nook for Xmas for my Mozambican husband without realizing B&N does not have any Portuguese books, while Amazon does) and a few more apps I like. So this would do! But I d like make sure:
- my system is more or less stable
- I don't get messed up with more OTA updates
So I wonder:
- is this system recommendable? This is rooted, right? Should I prefer Launcher or Zeam Launcher here?
- should I rather use another system? Go into CM7?
Since I dont have even any Nook here behind, I am afraid of more troubles following the normal procedure, should I?
- Do I need at all to set the normal version of Nook behind (like I could use with the Nook button app) - in fact, I don't really care...
Click to expand...
Click to collapse
Hello im glad to see you're back, about launchers, addons & apps it all depends of your likes.
What i gave you is MIUI ROM (operative system) without major modification (as-is) and yes it has zeam launcher but all can be modified.
I'm personally not a fan of gingerbread CM7 because i really like the eye candy of MIUI and even stock (which the buttons and menus are very similar to MIUI) so i use MIUI.
About stock i didn't mind using it even though i don't use B&N application and buy books from them buy i enjoyed the eye candy (interface/GUI), now that @cobrato released MIUI i immediately switched to that as im a huge fan of MIUI.
I have always used GO launcher as my main launcher but now im starting to use ADB in MIUI because it manages better the grid feature.
All systems you're going to find already come rooted which is standard and is the feature #1 of custom and stock ROMs, without root there is no fun. If you're in this community is because eather you have a rooted device or you came to learn how to root it and other stuffs.
If you like B&N stock ROM but don't use their apps and services you can bypass the registration and forget about the OTA updates, you can also apply on top of that the OTA block with titanium backup if you want to make sure. That is the methods i used and never ever had a problem. I also recommend you that when you flash a stock ROM do the whole procedure of OTA block and don't guess is already blocked, nothing better than do it yourself manually.
If you decide you want to make use of B&N services then you can eather go back to stock for a complete B&N experience or just install their app from the market if you're on CM7, CM9 or MIUI that is, nothing fancy but it does the job.
I have mentioned days ago that i was going to make a thread for MIUI users with how-tos and info about set it up but i've got very busy with many bricked devices around lol, but i eventually will do.
~ Veronica
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
JohnDorian said:
Thank you for your answer!
Will this work also with my 8Gb NT?
Click to expand...
Click to collapse
no, it is only for 16GB tablet, let me read your problem
~ Veronica
---------- Post added at 03:06 PM ---------- Previous post was at 02:58 PM ----------
JohnDorian said:
Can somebody help me? I bricked my nook tablet 8Gb!!
This is the whole story:
1) Rooted my NT
2) Used this apk to install CWM
http://forum.xda-developers.com/showthread.php?t=1458630
3) Tried to flash CyanogenMod 7 ROM but while it was flashing the tablet blacked out and rebooted
4) Now the tablet is stuck at the READ FOREVER screen
5) I can boot in CWM holding power+N button, but it can't flash anything, it freezes anytime I try to flash something.
6) I followed these 2 guides to unbrick my NT but they didn't work
http://forum.xda-developers.com/showthread.php?t=1470910
http://forum.xda-developers.com/showthread.php?t=1562130
Can anyone help me restore my NT at least to stock???
Please I'm desperate!!!!
Click to expand...
Click to collapse
I don't have a 8GB nook tablet to upload a backup of stock ROM and actually is very important to have nobody has been nice to upload it and post it in development section. Anyway let me give you the link of the official update to see if that helps, i was checking yesterday and they provide one for both i think there is not a separate section for the 8GB model so i assume that update is for both models containing 1.4.2
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/
under -Get Version 1.4.2 Today
~ Veronica
How can I flash this update?
JohnDorian said:
How can I flash this update?
Click to expand...
Click to collapse
right you dont know how, ok let me download the file and see if i make a kind of acclaim_update.zip for you to try.
can't flash any rom as a flashable.zip and backup folder? have you tried both?
~ Veronica
No, I can't flash anything from CWM...
ok so basically i want to find a way to get to 4.3 either rooted or unrooted, my problem is that i have pretty bad ocd and one of my major major problems with that disorder is my tech devices, i will most likely have an anxsiety attack or 2 if i have to set up my phone from scratch and i will spend hours making it look exactly the same. anyway, i want to know:
1:how to update rooted gs3 Gt-i9305t 4g/lte model without loosing data (if possible )
2: update to 4.3 and un root without loosing data (im sure thats impossible )
i would really appreciate the help as i cannot find anyone looking for the same help as me (kinda strange how no one cares about there data at all, but meh)
also on a side note, i have the problem with my s3 where any sd card i put into the machine will eventually kill itself and never work again as far as i know, it has killed 3 32gb sd cards now and its starting to piss me off to the point where i am no longer using an sd card at all. why does the phone do this and is there any way to fix it? either software wise or hard wear wise? thanks !!! :fingers-crossed:
4.3 source code has only just been released. 4.3 roms are not fully functional and have bugs. There are no official releases so they are all "rooted".
You really do need to wipe when making version updates. Theres no way around this.
Stick with what you've got.
that just sucks.
rootSU said:
4.3 source code has only just been released. 4.3 roms are not fully functional and have bugs. There are no official releases so they are all "rooted".
You really do need to wipe when making version updates. Theres no way around this.
Stick with what you've got.
Click to expand...
Click to collapse
that honestly sucks so much, thanks for the info though.
hey another quick question, is there a way to so a full backup, like im talking FULL, like down to the point of where ur apps are placed and all there data, like apple devices have through itunes?? (restore from backup option) cus if so then i dont mind wiping at all, i just hate apple so i will never go back to one of there piece of **** devices again (i like features with my shiny brick) but yeah anything like that? or can kies do that?
i'm using temasek 4.3 preview 3 atm, you should check it out since developer is extremely helpful
and he updates regularly (which is important)
There are a number of ways to keep your data. Including ones that will let you change the ROM and still have your data. Titanium Backup - not sure if it is only Pro version but the one I have lets me create a backup on the extSDcard so I can flash it in a new ROM and restore all my apps and data straight off. SMS Backup and restore and Call Backup and restore both save out your data to the extSDcard so you can bring them back. I used to use My Backup Root as well but it ceased to work on the last update so I nuked it.
Add in a nandroid backup on something like Philz Recovery (where you can do an Advanced Restore from External SDCard and bring back just parts of your current ROM) and you can always get back to your look & feel in any new ROM.
The one thing I ahve NOT found a solution for is replacing my widgets back on the screens they are on - I run 7 screens and it pisses me off a full recovery in something like Titanium doesn't restore my widgets. The only way it happens is a full nandroid restore but that nukes the new ROM I have just installed so that's not an option.
I run Purelook HD as my 1st ROM, GoogyMax kernel and SlimBean as my 2nd ROM. I can nuke either or both and be back to my set up (including widgets) in about 45 minutes.
Journyman16 said:
There are a number of ways to keep your data. Including ones that will let you change the ROM and still have your data. Titanium Backup - not sure if it is only Pro version but the one I have lets me create a backup on the extSDcard so I can flash it in a new ROM and restore all my apps and data straight off. SMS Backup and restore and Call Backup and restore both save out your data to the extSDcard so you can bring them back. I used to use My Backup Root as well but it ceased to work on the last update so I nuked it.
Add in a nandroid backup on something like Philz Recovery (where you can do an Advanced Restore from External SDCard and bring back just parts of your current ROM and you can always get back to your look & feel in any new ROM.
Click to expand...
Click to collapse
Lets dissect this a little.
A Nandroid backup will take a snapshot of your phone. If you flash something wrong, it can be used to restore your data / settings and rom exactly how it was. This will not help restore your data and settings on a new ROM where you had to perform a wipe. (You have to perform a wipe to prevent data and settings incompatibilities with the new ROM that will cause problems.)
Titanium backup is great. However, if you had to perform a wipe, you cannot simply restore everything using Titanium. This is because you will be restoring the incompatabilities (System data) and restoring the problems (negating the point of the wipe in the first place). You can restore user apps and data with titanium but there will be an element of manually setting all your rom settings.
OP - Please read the "Read before rooting" thread in my signature for more info.
**** that
screw it, ill just stay on 4.2.1 i mostly want it cus they (****ING FINALLY ) partially fixed the setting wallpaper problems so you can get at least most of the photo in the screen now, i have it on my nexus 7 but now cant get it on my phone : / screw ocd, it has plagued me since i was little
adex9 said:
screw it, ill just stay on 4.2.1 i mostly want it cus they (****ING FINALLY ) partially fixed the setting wallpaper problems so you can get at least most of the photo in the screen now, i have it on my nexus 7 but now cant get it on my phone : / screw ocd, it has plagued me since i was little
Click to expand...
Click to collapse
We all spend hours making it look exactly the same. It's annoying but essential.
rootSU said:
Lets dissect this a little.
A Nandroid backup will take a snapshot of your phone. If you flash something wrong, it can be used to restore your data / settings and rom exactly how it was. This will not help restore your data and settings on a new ROM where you had to perform a wipe. (You have to perform a wipe to prevent data and settings incompatibilities with the new ROM that will cause problems.)
Titanium backup is great. However, if you had to perform a wipe, you cannot simply restore everything using Titanium. This is because you will be restoring the incompatabilities (System data) and restoring the problems (negating the point of the wipe in the first place). You can restore user apps and data with titanium but there will be an element of manually setting all your rom settings.
Click to expand...
Click to collapse
The Advanced Restore in Philz lets you restore Data. The choices are, Restore Boot, System (+or- reload) Data, Cache and sd ext. The Data restored my latest personal stuff from the BU I tried just before a new ROM experiment. So not all Restores are the same. You don't have to bring it ALL back from a nandroid.
Journyman16 said:
The Advanced Restore in Philz lets you restore Data. The choices are, Restore Boot, System (+or- reload) Data, Cache and sd ext. The Data restored my latest personal stuff from the BU I tried just before a new ROM experiment. So not all Restores are the same. You don't have to bring it ALL back from a nandroid.
Click to expand...
Click to collapse
@Journyman16
You seem to be missing my point.
If you can restore just data via recovery (which you can) then you didn't need to wipe in the first place.
ROM goes in /system. We all know that. Our apps go in /data/app. We all know that. Our data for our apps goes in /data/data but what some may NOT know is that /data/data contains all your system data too. When you set a ring tone or wallpaper, its in /data/data.
If you go from 1 ROM to another, you may not have to wipe. Or you may HAVE to wipe. It depends if there is incompatible system data in /data/data or not.
When you do wipe, you wipe /data/* (includes /data/data). If you nandroid restore /data and your phone works perfectly, you didn't need to wipe. So my point remains.
If you HAD to wipe, you cannot simply restore data via recovery and have a fully working phone.
rootSU said:
@Journyman16
You seem to be missing my point.
If you can restore just data via recovery (which you can) then you didn't need to wipe in the first place.
ROM goes in /system. We all know that. Our apps go in /data/app. We all know that. Our data for our apps goes in /data/data but what some may NOT know is that /data/data contains all your system data too. When you set a ring tone or wallpaper, its in /data/data.
If you go from 1 ROM to another, you may not have to wipe. Or you may HAVE to wipe. It depends if there is incompatible system data in /data/data or not.
When you do wipe, you wipe /data/* (includes /data/data). If you nandroid restore /data and your phone works perfectly, you didn't need to wipe. So my point remains.
If you HAD to wipe, you cannot simply restore data via recovery and have a fully working phone.
Click to expand...
Click to collapse
Thanks for the explanation - that helps me understand better what goes on. Would that explain perhaps why, after some Restores, I had to run Fix Permissions to stop the FC's?
Journyman16 said:
Thanks for the explanation - that helps me understand better what goes on. Would that explain perhaps why, after some Restores, I had to run Fix Permissions to stop the FC's?
Click to expand...
Click to collapse
Yep, it could do.
Any updates (I am facing the same problem)?
BTW, OTA updates seem to be able to keep most if not all settings. How they manage to do this?
moshepupkin said:
Any updates (I am facing the same problem)?
BTW, OTA updates seem to be able to keep most if not all settings. How they manage to do this?
Click to expand...
Click to collapse
Same here. I've been looking for the exact method to do this, but haven't had any luck so far.
I ended up using Kies to update to 4.3 - it does not check root status.
moshepupkin said:
I ended up using Kies to update to 4.3 - it does not check root status.
Click to expand...
Click to collapse
Hmm, it says that my current firmware is the latest version, rather than 4.3. Is there anything special you're supposed to do?
AriaOfSorrow said:
Hmm, it says that my current firmware is the latest version, rather than 4.3. Is there anything special you're supposed to do?
Click to expand...
Click to collapse
Who says there is a 4.3 for your phone ???
JJEgan said:
Who says there is a 4.3 for your phone ???
Click to expand...
Click to collapse
Well, let's see... there's everyone I know that also has this phone. People online that say they have this phone. Web sites saying that this phone has officially received 4.3. The phone itself saying there is an update for the firmware. So, basically everyone/thing except the Kies program.
Who says their is an update for your phone repeat your phone not some other guys phone and as you failed to give any firmware details impossible to check .
Kies/ Samsung says not for your phone yet.
Contact your vendor .
See multiple identical posts .
Flash stock rom through Odin from sammobile .com
JJEgan said:
Who says their is an update for your phone repeat your phone not some other guys phone and as you failed to give any firmware details impossible to check .
Kies/ Samsung says not for your phone yet.
Contact your vendor .
See multiple identical posts .
Flash stock rom through Odin from sammobile .com
Click to expand...
Click to collapse
I already told you who said there is an update for my phone. Unless my phone is disguised as some one of a kind phone, I'm supposed to be able to update to 4.3.