Related
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Just curious as to if this is rooted or just fixed to allow use of CWM?
Nevermind just read the full post!!
So just to make sure, I could use the one zip to return to full stock but with the 1.2 update? Also will this work if I have CM7 and CWM on my emmc? So reboot into CW, format \system and \data then flash the update-nc-stock-1.2-signed.zip, then Reboot. At that point, I should be 100% 1.2 stock, sound about right?
I thinking about returning to stock and just run CM7 for my SD if this is an options.
Thanks,
Derek.
DGarmon said:
So just to make sure, I could use the one zip to return to full stock but with the 1.2 update? Also will this work if I have CM7 and CWM on my emmc? So reboot into CW, format \system and \data then flash the update-nc-stock-1.2-signed.zip, then Reboot. At that point, I should be 100% 1.2 stock, sound about right?
I thinking about returning to stock and just run CM7 for my SD if this is an options.
Thanks,
Derek.
Click to expand...
Click to collapse
Assuming you haven't fooked up any paritioning by using the "dual-boot" stuff you can return to 100% stock by doing the folllowing:
Download the update-nc-stock-1.2-signed.zip above
Flash the zip with CWM (either from emmc or sdcard)
Use CWM to factory reset the device (wipe /data and /cache)
Reboot into 100% stock froyo
If you have modified your partitions this will not work.
This won't work off of an sd right?
I'd like to modify this so it just installs to my dual boot partition.
I've done this before with flashing kernels, but there are more partitions here to take care of.
I figure if I'm going to change the updater script to mount the correct block partitions then I should also have it wipe /data and /cache on the secondary partition.
Any ideas on syntax?
sassafras
Thanks
Once we have a rooted version I'll probably check it out for fun.
nemith said:
Assuming you haven't fooked up any paritioning by using the "dual-boot" stuff you can return to 100% stock by doing the folllowing:
Download the update-nc-stock-1.2-signed.zip above
Flash the zip with CWM (either from emmc or sdcard)
Use CWM to factory reset the device (wipe /data and /cache)
Reboot into 100% stock froyo
If you have modified your partitions this will not work.
Click to expand...
Click to collapse
But then I'm stuck with stock froyo - I can't go back to CM7 after I've satisfied my curiosity, right?
Hmmm, have to think about that......then, again, maybe not.
nemith said:
There are two files.
Click to expand...
Click to collapse
Many thanks for these.
Please post MD5's of these so that we can be sure that the download was successful (some may want to store the file for later use).
BTW, free MD5checker can be found at getmd5checker.com
HarleyChick said:
But then I'm stuck with stock froyo - I can't go back to CM7 after I've satisfied my curiosity, right?
Hmmm, have to think about that......then, again, maybe not.
Click to expand...
Click to collapse
Create a backup first.
Thanks for the files nemith. Much appreciated.
Sent from my NookColor using Tapatalk
Hey nemith, would it be okay if I used this as a base for a rooted version? Give you full credit of course, just dont feel like going through the hassle of the updater script and what not.
msgnyc said:
Create a backup first.
Thanks for the files nemith. Much appreciated.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I guess I wasn't clear the first time: if I use this method, am I stuck with B&N's version of Froyo until someone figures out how to root this one, or can I just reflash CM7? And I'm not sure I understand the difference between both of the zips that nemith has produced.
In any case, thanks nemith - I always appreciate the work that the devs do!
HarleyChick said:
I guess I wasn't clear the first time: if I use this method, am I stuck with B&N's version of Froyo until someone figures out how to root this one, or can I just reflash CM7? And I'm not sure I understand the difference between both of the zips that nemith has produced.
In any case, thanks nemith - I always appreciate the work that the devs do!
Click to expand...
Click to collapse
If you dont like this, just boot into a bootable clockwork recovery and flash cm7 or whatever you want. You wont be stuck on this.
One zip removes Clockwork Recovery and puts the stock recovery back. The other leaves Clockwork Recovery intact.
I'd assume, leaving it intact allows you to flash back to any backups or any other Rom if incase you do not like the official build.
I'm at work so I'm unable to test it out.
Or you can always just use a bootsble SD with clockwork on it to reflash whatever ron or backup you have.
Sent from my NookColor using Tapatalk
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
My rooted BN1.1 with auto-nooter 3.0 does NOT have CWM in emmc. Can I use update-nc-stock-1.2-signed.zip to go to 1.2 unrooted?
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
Any way you could make something would allow you to flash 1.2 onto a secondary parttion for those of us who are dual booters?
So Ive got this thing rooted but I for the life of me cannot get the market to work. I have the vending.apk and googleservicesframework.apk under /system/app but market will not show up in my app drawer on the stock or adw launcher. Under manage applications, market or googleservicesframework arent there either. Does the nook have other dependencies? If anyone with some experience could throw some suggestions my way. ADB isnt currently working without the driver. Ive added other apps that are showing up and working perfectly.
Did you modify the build.prop?
Sent from my Nook Color using XDA App
scoutcamper said:
Did you modify the build.prop?
Sent from my Nook Color using XDA App
Click to expand...
Click to collapse
Nope didnt touch it, im usually devving for the evo, so modding that isnt normally needed for gapps. What would need to be modified in the build.prop?
The device code will have changed and prevent market access. Try pulling the device code from a froyo device with market access like Droid X.
Sent from my Nook Color using the XDA App
If one enables full device encryption in Ice Cream Sandwich, am I correct in assuming that that the internal SD of that device is now not going to be available in the CWM recovery mode? And even if it was, the root fs would not be available? If so, this pretty much would make CWM flashing your device near impossible?
Does CWM even work if you use FDE? Or is it planned/
The question I guess is, when do you input your encryption password? Is it some pre-boot step?
I really want to enable device encryption but I can't find enugh details on how it works.
I did read this post on it., but it doesn't really answer my questions. And it is unclear if it encrypts the internal SD, or just the root FS?
http://source.android.com/tech/encryption/android_crypto_implementation.html
No one knows anything about this?
I got a Gnex today from Verizon in the US and I encrypted my phone after I unlocked the bootloader but before rooting. As a result I don't think I will be able to root because it doesn't seem that the modified boot.img that the instructions tell me to use can mount the encrypted system (it sat at the Google logo w/ the unlocked icon for 10 minutes before I pulled the battery and let it boot the stock boot.img) which came up fine.
It seems the only way to decrypt the phone is by doing a factory reset.
That's all I know. That being said, while a custom recovery may work for wiping partitions (such as cache), it would probably be mostly useless until the custom recovery is updated to support the encrypted file systems. I'm a *NIX user and an engineer, but don't have a lot of experience with Android's internals, so take all that with the appropriate sized grain of salt.
Regards,
Chris
Bump.
Anyone experimented with full device encryption / ROM flashing / SD Card? I'm curious about this as well, but not curious enough to experiment.
I dident try it myself, so i dont exactly know, how this works. But i think device encryption shouldent completly block clockworkmod recovery.
I think it could be a problem to make a backup while your device is encrypted. But i think it shouldent be a problem to recover a old system over an encrypted one. Encryption keeps people without the key away from reading data. This dosent mean you cant wright something over it and replace the locked data with some new one. But then you defenitly loose the old data. I dont think you can flash a new ROM or a recovery without a full wipe. You probably gona loose all the data you had on the old system.
But i general i think this is anyway a good think to do when you flash a new ROM.
I think you could give it a try, without briking your phone. But i dident try it, so i cant take any responsibility.
Would any of you happen to know how to get to the diagnostic mode?
ryfly65 said:
Would any of you happen to know how to get to the diagnostic mode?
Click to expand...
Click to collapse
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Sent from my HTC Desire HD using XDA App
Hilmy said:
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Click to expand...
Click to collapse
I need to edit modem information and enable a diag port for QPST, essentially allowing me to flash it to another carrier.
Is there any new information on this? Any help would be very appreciated!
Sent from my Galaxy Nexus using XDA App
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
nevarDeath said:
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
Click to expand...
Click to collapse
So if I factory reset the device from CMW I will not loose my pictures or TB in the internal SD?
What about flashing a new ROM?
Thanks!
I have been playing with ICS + FDE for several days doing different things. First off this is:
Nexus S 4G, running Pete's crespo4g OTA ROM
I flashed with CWM which is still on there and runs fine.
However: /data and /sdcard and /system (?) are encrypted and CANNOT be mounted.
To restore you have to 1) make a full backup over USB to a PC of the whole SDcard (or at least the important folders).
2) wipe and reformat everything. This isn't just a factory reset, this kills the sdcard as well.
3) mount (hopefully) the newly reformatted /sdcard and blow your backup from the PC onto the /sdcard
4) use CWM to restore a previous ROM.
That's pretty much it, give or take. Not for the faint of heart. However, if you are concerned enough to want encryption, you don't want to just say reboot recovery and voila all your files are belong to us, right?
---------- Post added at 03:58 PM ---------- Previous post was at 03:34 PM ----------
Also, the backup to PC part is just your sdcard. It doesn't back up the whole system. There might be a way to do that via adb, I don't know.
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Pete's to CM9 - still encrypted
IT does indeed take a fairly long time to encrypt. If I understand correctly it will build the encrypted partition on a loopback (or something like) before erasing the original (by overwriting?).
I've got more to report. I followed my plan (couple posts back) for unencrypting and reflashing my phone. (Nexus S 4g).
The first bits of this worked fine. I was able to flash CM9 onto my phone (works like a champ btw). While the phone was in recovery I mounted the SD and copied my backup back onto it.
However...
When CM9 booted I STILL got the "unlock your device" screen, still the same password, and it decrypted and booted. That was surprising, but not as much as when I looked for the SD card, it said it was incorrectly formatted! The only thing to do was reformat and copy with the phone on and unlocked.
So lessons learned: 1) a factory reset from _inside_the_ROM_ doesn't remove the encrypted partition at all and
2) As far as I can tell, the SD card _is_ encrypted along with /data
I'd be very interested to hear other's experiences, especially someone who can remove their SD storage.
Undoing FDE
First off - Lacking a device with removable storage to test with all I can tell you is that the sdcard is not accessible by any normal means after FDE is enabled without booting into the encrypted system.
"Removing" FDE required three steps beyond normal:
-Factory reset from within the ROM
-factory reset/wipe at recovery and/or format /data
-once into a running ROM, reformat the sdcard
Once all that is done (in addition to normal setup for ROM) you should be able to operate normally again.
problem with encryption on sgs2 with android 4.0.3
I really want to enable my device encryption too, but I can't !!!
the phone start encrypting after he ask me for a new secure password, rebooting and asking again for my password and surprise!!!.... the password is not match ?!?!
I repetead these steps for 3 times but the same result...the password does not match!!! ?
Please, if someone found a trick to repair this inconvenient, tell us in this post steps to be followed.
Regards!
SGS2, Android Icecream 4.0.3
leech2082 said:
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Click to expand...
Click to collapse
I did exactly what you did, and so far everything seems to be intact Thanks!
I've been having alot of issues, lag, freezes, reboots, and ive been having these issues on a few different roms ive tried. I had Been running the paranoid android one from Jamied81 and it worked great but then i switched around and on any rom including the PA one, and other cm10 roms, im having the same issues, So There must be something wrong with my phone... i guess?
How can i completely wipe clean and start fresh? because ive been wiping data, cache and dalvik cache but thats not helping...
Of course i could go back to best buy and cash in on my warranty.. but i really dont want to do that...
thanks
Well,
It depends on the level you want to take the "cleaning" too...
Data, cache, dalvik cache, and stats are a normal cleaning, and used by most folks to get an average clean.
Some roms even state to do this 3 times or more to be sure.
Two additional steps are needed to get the device "clean". and it involves moving everything off of the device to PC storage, and wiping the following two areas.
( by everything, I mean "anything" you want to keep. pictures etc.)
First, the SD card. As the device uses this memory location for cache of files, and bits of user data, it can be a source of misery when bouncing between roms. so a complete format to FAT32 on the PC will wipe this card clean.
Second, and my personal favorite, is wiping of the internal card space, or the EMMC partition.
This is performed through the recovery, under the advanced options menu, in the format sub-section.
Effectively, wiping the emmc "will" remove all rom data from the device, above the normal data wipe level, and leaves the device empty.
Note: the new rom will re-populate the needed files to run the rom upon the first boot cycle.
IMPORTANT !!!
If moving files back to your device from PC, you must ensure that they are clean too. It is very easy to forget that many files contain rom specific data, and should be avoided as a restore function, especially APK's....
The partitions from the last rom will remain in place, but they will be overwritten by using odin to restore the device. ( if you wish to restore the factory rom architecture )
If odin or kies are not used, the rom partitions remain, but are empty anyway.
"WARNING" !!!!
Although this method is considered safe, you "will lose "any" data or files left behind on the internal space of the device, or on your External SD card by formatting.
And you must place a new rom to your External card prior to placing the card back into the phone, and use CWM or TWRP recovery to flash a new rom in recovery mode. (unless odin or kies are used to return a device to stock condition)
Note: (no pun intended)
This method will "not" touch your recovery, Unless using odin or kies to push a non-rooted rom to the device, and the user must choose carefully when selecting any firmware image to flash.
It is up to the user to restore the factory partitions by flashing a stock odin rom, unless the last rom was a "stock" rom. (Note: kies may be used as well, but Odin is the most common, and works well )...
The standard recovery flash can be used, and is advised if you want to retain root...!!!!
"WARNING" !!!... THE USE OF ODIN OR KIES TO FLASH A STOCK FIRMWARE IMAGE WILL REMOVE YOUR ROOT, AND RECOVERY, FORCING THE DEVICE BACK TO A STOCK STATE....( choose carefully as you select any image to flash using Odin or Kies, as these roms are likely "NOT" rooted roms, and will jam you up)...
I hope this helps you.
Please ask if you have any questions, "before" attempting this procedure... PM included.
And could the Mods please move this thread to QA ? Thank you.....g
gregsarg said:
Well,
It depends on the level you want to take the "cleaning" too...
Data, cache, dalvik cache, and stats are a normal cleaning, and used by most folks to get an average clean.
Some roms even state to do this 3 times or more to be sure.
Two additional steps are needed to get the device "clean". and it involves moving everything off of the device to PC storage, and wiping the following two areas.
( by everything, I mean "anything" you want to keep. pictures etc.)
First, the SD card. As the device uses this memory location for cache of files, and bits of user data, it can be a source of misery when bouncing between roms. so a complete format to FAT32 on the PC will wipe this card clean.
Second, and my personal favorite, is wiping of the internal card space, or the EMMC partition.
This is performed through the recovery, under the advanced options menu, in the format sub-section.
Effectively, wiping the emmc "will" remove all rom data from the device, above the normal data wipe level, and leaves the device empty.
Note: the new rom will re-populate the needed files to run the rom upon the first boot cycle.
IMPORTANT !!!
If moving files back to your device from PC, you must ensure that they are clean too. It is very easy to forget that many files contain rom specific data, and should be avoided as a restore function, especially APK's....
The partitions from the last rom will remain in place, but they will be overwritten by using odin to restore the device. ( if you wish to restore the factory rom architecture )
If odin is not used, the rom partitions remain, but are empty anyway.
"WARNING" !!!!
Although this method is considered safe, you "will lose "any" data or files left behind on the internal space of the device, or on your External SD card by formatting.
And you must place a new rom to your External card prior to placing the card back into the phone, and use CWM or TWRP recovery to flash a new rom in recovery mode.
Note: (no pun intended)
This method will "not" touch your recovery, Unless using odin or kies to push a non-rooted rom to the device, and the user must choose carefully when selecting any firmware image to flash.
It is up to the user to restore the factory partitions by flashing a stock odin rom, unless the last rom was a "stock" rom. (Note: kies may be used as well, but Odin is the most common, and works well )...
The standard recovery flash can be used, and is advised if you want to retain root...!!!!
"WARNING" !!!... THE USE OF ODIN OR KIES TO FLASH A STOCK FIRMWARE IMAGE WILL REMOVE YOUR ROOT, AND RECOVERY, FORCING THE DEVICE BACK TO A STOCK STATE....( choose carefully as you select any image to flash using Odin or Kies, as these roms are likely "NOT" rooted roms, and will jam you up)...
I hope this helps you.
Please ask if you have any questions, "before" attempting this procedure... PM included.
And could the Mods please move this thread to QA ? Thank you.....g
Click to expand...
Click to collapse
Wow.... first of all, thanks for the very detailed reply.
So i format the card separately, format the emmc in recovery, and install a new rom? do i need to deal with the other partitions? or will the new rom just take care of that?
mottyengel said:
Wow.... first of all, thanks for the very detailed reply.
So i format the card separately, format the emmc in recovery, and install a new rom? do i need to deal with the other partitions? or will the new rom just take care of that?
Click to expand...
Click to collapse
The partitions will be empty....and the device will be as clean as you can safely get it, without risking a brick....g
gregsarg said:
The partitions will be empty....and the device will be as clean as you can safely get it, without risking a brick....g
Click to expand...
Click to collapse
Thanks alot for your help!!
mottyengel said:
Thanks alot for your help!!
Click to expand...
Click to collapse
Always welcome...g
Another easy way...go to this site: http://rootzwiki.com/topic/25980-sgh-i717ucle2-official-leak/, follow the instructions, bam. Basically just throw into DL mode and hit start, its one of the one click Odin ICS leaks from designgears and it completely wipes everything on your phone.
I have run into similar sounding problems as yours where my phone won't wipe properly in cwm, and I've used this to completely nuke my internal storage and start over.
Of course, transfer all pictures, music, and important files to your computer first. Then after you use the one click Odin, just begin romming as usual
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
With a nice moist wipe!
Sent from the TermiNOTEr!
While i've seen and like the rootzwiki method, I prefer to manually wipe and install roms.
For me, it adds back in, that level of control I like to have when changing roms etc.
I'm the " do it myself " kinda user ...but I agree, it's a good system.
Thank you for posting it ....g
---------- Post added at 06:09 PM ---------- Previous post was at 06:08 PM ----------
borijess said:
With a nice moist wipe!
Sent from the TermiNOTEr!
Click to expand...
Click to collapse
..springtime fresh ??
Oh yehhhhhhhhhh!!!.....LOL .......g
I factory reset. cache wipes. Darkside wipe zip.
"The clean getaway"
gregsarg said:
Always welcome...g
Click to expand...
Click to collapse
View attachment 1291207
Sent from A Closet @ Arkham Asylum on my GNote using Forum Runner, Black ★.
Yeah, I prefer the manual way in cwm as well, but I've run into an error a couple of times where it won't wipe properly. So I nuke my phone to fix the ability to wipe. There's no way I would do that every time I flash a ROM.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
welchertc said:
Yeah, I prefer the manual way in cwm as well, but I've run into an error a couple of times where it won't wipe properly. So I nuke my phone to fix the ability to wipe. There's no way I would do that every time I flash a ROM.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
True ....and of course, my post was meant in the context of a device having severe problems.
I seldom use that method either, but in a pinch it's good to have available ......and if users see and retain either of the methods we've posted, they can repair virtually any problem going forward.
And hopefully avoid those JTAG moments we all dread ....g
That's for sure. Haha.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Must wipe...
View attachment 1291573
Sent from A Closet @ Arkham Asylum on my GNote using Forum Runner, Black ★.
LOL. !!!
Excellent !!!
welchertc said:
Another easy way...go to this site: http://rootzwiki.com/topic/25980-sgh-i717ucle2-official-leak/, follow the instructions, bam. Basically just throw into DL mode and hit start, its one of the one click Odin ICS leaks from designgears and it completely wipes everything on your phone.
I have run into similar sounding problems as yours where my phone won't wipe properly in cwm, and I've used this to completely nuke my internal storage and start over.
Of course, transfer all pictures, music, and important files to your computer first. Then after you use the one click Odin, just begin romming as usual
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. But, i dont see any instructions... what do i do with the file?
Basically its a one click version of Odin with the files already loaded into it so you don't have to pick anything.
Download it to your comp, unzip the file (I believe?), open the program, put your phone into download mode, connect it to your comp, make sure Odin recognizes it, then click start.
Takes a bit because its a huge process that it's undertaking, but at times its necessary to go nuclear on your phone.
Really should only be used as a last resort to wiping your phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
welchertc said:
Basically its a one click version of Odin with the files already loaded into it so you don't have to pick anything.
Download it to your comp, unzip the file (I believe?), open the program, put your phone into download mode, connect it to your comp, make sure Odin recognizes it, then click start.
Takes a bit because its a huge process that it's undertaking, but at times its necessary to go nuclear on your phone.
Really should only be used as a last resort to wiping your phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Agreed ....g
I mostly wipe front to back.
Hello Everyone,
I have not play with any android devices since android 2.0 and even back then found self rooting tools. I got my Kid Nabi2 tablet. Runs Android 4.0.4 currently. Nice little tablet. Problem is only have 8GB or storage. About 4gb after all system partitions and recoveries. So my question is can I safely back up my recovery partition to external source to free up some space? I assume recovery partition has complete recovery files when I do restore to factory option. I I remember correctly android has few partitions. /boot, /system, /recovery, /sd. is there a way just to have your operating system and whatever apps. Have recovery mode but have files on like sd card. If I decide to root this device dose that changes anything in my recovery partition. If device is rooted can I just go back to completely stock by doing factory reset? I just want to make sure that if I root it and want to go back to complete stock for any reason I can do that.
You can restore from your backup that gets made after you flash the custom recovery.
Here is the original script for using on Windows:
http://forum.xda-developers.com/showthread.php?p=32207344
Though you should use the gapps package from http://forum.xda-developers.com/showthread.php?p=35888524 as it gets rid of the 'android upgrading' messages on every boot.
If you want a more manual method, or are on linux, see http://forum.xda-developers.com/showthread.php?t=2016463
t499user said:
You can restore from your backup that gets made after you flash the custom recovery.
Here is the original script for using on Windows:
http://forum.xda-developers.com/showthread.php?p=32207344
Though you should use the gapps package from http://forum.xda-developers.com/showthread.php?p=35888524 as it gets rid of the 'android upgrading' messages on every boot.
If you want a more manual method, or are on linux, see http://forum.xda-developers.com/showthread.php?t=2016463
Click to expand...
Click to collapse
T499user, thank you for replaying. I do run windows. I did look at the section you direct me to me before. What I don't understand is when you root with his program do I use option 1 or 2. Where dose the back up go and how do I restore it later? when I restore dose that bring it back completely to stock, meaning just like it was when i got it? I'm currently running new nabi software do I have to worry about losing wifi?
Also is there a way of freeing up space on my nabi 2 by keeping a back up somewhere else. I think now there is recovery/back up partition. that works when I do factory reset. is that is how that works?
By installing new custom recovery would other recovery still be there?
Sorry trying to get back after many Apple years..
skull791 said:
T499user, thank you for replaying. I do run windows. I did look at the section you direct me to me before. What I don't understand is when you root with his program do I use option 1 or 2. Where dose the back up go and how do I restore it later? when I restore dose that bring it back completely to stock, meaning just like it was when i got it? I'm currently running new nabi software do I have to worry about losing wifi?
Also is there a way of freeing up space on my nabi 2 by keeping a back up somewhere else. I think now there is recovery/back up partition. that works when I do factory reset. is that is how that works?
By installing new custom recovery would other recovery still be there?
Sorry trying to get back after many Apple years..
Click to expand...
Click to collapse
I prefer to do it manually, but if you are going to use the script, use option 2. Then you can install gapps from TWRP using http://forum.xda-developers.com/showthread.php?t=2065878.
The backup that gets created is of the current system state. It is stored in /sdcard/TWRP/backups/*serialnumber*/backupname
No worries about wifi as long as you did all of the OTA updates.
t499user said:
I prefer to do it manually, but if you are going to use the script, use option 2. Then you can install gapps from TWRP using http://forum.xda-developers.com/showthread.php?t=2065878.
The backup that gets created is of the current system state. It is stored in /sdcard/TWRP/backups/*serialnumber*/backupname
No worries about wifi as long as you did all of the OTA updates.
Click to expand...
Click to collapse
Now do I have to install TWRP or when i root it will do it for me?
It will be done with the script.
t499user said:
It will be done with the script.
Click to expand...
Click to collapse
What dose exactly gets back up?
also do you know why nabi2 only has about 4.45gb of free storage when total is 8gb? 3.55gb seems a lot for system files???
skull791 said:
What dose exactly gets back up?
also do you know why nabi2 only has about 4.45gb of free storage when total is 8gb? 3.55gb seems a lot for system files???
Click to expand...
Click to collapse
The system, boot, and data partitions get backed up. That is the way they set it up for the partitions.
All of your questions have already been answered in the other threads, might want to do a search for 'Nabi' and have a read.
t499user said:
The system, boot, and data partitions get backed up. That is the way they set it up for the partitions.
All of your questions have already been answered in the other threads, might want to do a search for 'Nabi' and have a read.
Click to expand...
Click to collapse
T499user trust me I been reading crazy and still cant find an answer. Want to point me to the right place ?
No problem, I would start with the following:
http://forum.xda-developers.com/showthread.php?t=1905674
http://forum.xda-developers.com/showthread.php?t=2016463
t499user said:
No problem, I would start with the following:
http://forum.xda-developers.com/showthread.php?t=1905674
http://forum.xda-developers.com/showthread.php?t=2016463
Click to expand...
Click to collapse
Thank you. I did read all of them. Do you know where I can find something about android system file. Mostly why I have only 4.45gb out of 8. Is thereba way to move back up patition? To external source to free up some space?
Hey all. Can anyone tell me exactly what "success rebooting by reason oem-00" means? And why is it every time I boot into recovery I get can't mount cache/recovery/command. I believe its my sdcard. Thanks!
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Hey all. Can anyone tell me exactly what "success rebooting by reason oem-00" means? And why is it every time I boot into recovery I get can't mount cache/recovery/command. I believe its my sdcard. Thanks!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I doubt it's your SDcard. Its mount point is at /sdcard, not /cache. Sounds like you either need to wipe your cache or you're trying to do something with s-off when you're still s-on.
This is making the assumption that you're trying to flash an update via recovery. If not, please ignore.
Tourney3p0 said:
I doubt it's your SDcard. Its mount point is at /sdcard, not /cache. Sounds like you either need to wipe your cache or you're trying to do something with s-off when you're still s-on.
This is making the assumption that you're trying to flash an update via recovery. If not, please ignore.
Click to expand...
Click to collapse
I'm completely stock. Just when I make a selection in recovery I get a bunch of errors. I can't factory reset, well I can but it won't fix the problem. I can run an ruu over and over and still get the same errors. I'm just wondering what the success reboot means and why it won't let me choose anything in recovery. Should I flash 4ext?
Sent from my PG86100 using xda app-developers app
Ya me to think its sd card problem i recomennd format card ree root re install clock work mod it will fix it .....
HOPE SO
DONT JUST SAY THANKS CLICK IT..
Sent from my LG-P500 using xda premium t from my LG-P500 using xda premium
harshgpt816 said:
Ya me to think its sd card problem i recomennd format card ree root re install clock work mod it will fix it .....
HOPE SO
DONT JUST SAY THANKS CLICK IT..
Sent from my LG-P500 using xda premium t from my LG-P500 using xda premium
Click to expand...
Click to collapse
I've already formatted, without backing up my picture music ect.., and still won't fix. What could be causing the ruu not to fix my phone?
Sent from my PG86100 using xda app-developers app
It still sounds to me like it's not an SDcard issue since the mountpoint isn't /sdcard, but after looking at some Google results I could be wrong. Do you still get the error if you boot with the SDcard removed?
Tourney3p0 said:
It still sounds to me like it's not an SDcard issue since the mountpoint isn't /sdcard, but after looking at some Google results I could be wrong. Do you still get the error if you boot with the SDcard removed?
Click to expand...
Click to collapse
I'm not sure. But I really don't wanna pull the sd. That requires taking the battery out and if I do that I'm stuck in a boot loop.
Sent from my PG86100 using xda app-developers app
I believe you can unseat the SD card without entirely removing it or the battery. If not, no big deal.
What method are you using to flash the RUU? It seems to me like the installer would automatically wipe the /cache directory, but that's probably not a safe assumption to make. At this point it couldn't hurt to install 4ext and make absolutely sure all partitions other than sdcard are wiped. Also, do you get any mount errors other than /cache/recovery/command?
I would try the following, seeing if there is progress after each step:
1) Unseat the sdcard without removing the battery, if possible. If not then skip this step.
2) Install 4ext and wipe cache (all cache, not just davlik)
3) Remove battery and remove sdcard. I know this sucks and you'll get boot loops, but it doesn't matter because the next step is:
4) Wipe all partitions other than sdcard. Even wipe sdcard if you've got a backup. Then attempt an RUU install.
If none of these work, I'm out of ideas. Maybe someone else can chime in. I know there used to be a lot of reports from other devices about /cache/recovery/command and some other directories not being mountable when the eMMC died. It's possible yours is dying and the cache is getting corrupted by hardware failure. That's a worst case scenario, but we gotta eliminate all other possibilities before we make that call.
Tourney3p0 said:
I believe you can unseat the SD card without entirely removing it or the battery. If not, no big deal.
What method are you using to flash the RUU? It seems to me like the installer would automatically wipe the /cache directory, but that's probably not a safe assumption to make. At this point it couldn't hurt to install 4ext and make absolutely sure all partitions other than sdcard are wiped. Also, do you get any mount errors other than /cache/recovery/command?
I would try the following, seeing if there is progress after each step:
1) Unseat the sdcard without removing the battery, if possible. If not then skip this step.
2) Install 4ext and wipe cache (all cache, not just davlik)
3) Remove battery and remove sdcard. I know this sucks and you'll get boot loops, but it doesn't matter because the next step is:
4) Wipe all partitions other than sdcard. Even wipe sdcard if you've got a backup. Then attempt an RUU install.
If none of these work, I'm out of ideas. Maybe someone else can chime in. I know there used to be a lot of reports from other devices about /cache/recovery/command and some other directories not being mountable when the eMMC died. It's possible yours is dying and the cache is getting corrupted by hardware failure. That's a worst case scenario, but we gotta eliminate all other possibilities before we make that call.
Click to expand...
Click to collapse
Yes when I try to wipe the cache in stock recovery I get a bunch of mourning errors. Recovery.log last.log and a few others. I'll try yo get the SD out. If not I'll install 4ext and try to wipe cache. How would I go about wiping my partitions? I can use 4ext without root correct? Thanks!
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Yes when I try to wipe the cache in stock recovery I get a bunch of mourning errors. Recovery.log last.log and a few others. I'll try yo get the SD out. If not I'll install 4ext and try to wipe cache. How would I go about wiping my partitions? I can use 4ext without root correct? Thanks!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Installing 4ext without root should be no problem. Just make sure the device is unlocked using the HTC Dev Tool (mandatory). Then go through the flashboot process for recovery.img. It couldn't hurt to install SuperSU while you're in there, though that's outside the scope of what we're trying to repair right now. Once you're in 4ext, under the Wipe menu, there should be an option for "Wipe all partitions other than sdcard" (paraphrased). Go with that. Though if the stock recovery didn't do it, I don't have high hopes for 4ext to be able to.
The fact that you're getting multiple mounting errors leads me to believe you have a bad eMMC. If all the steps from the previous post fail, that'll tell you for sure.
Tourney3p0 said:
Installing 4ext without root should be no problem. Just make sure the device is unlocked using the HTC Dev Tool (mandatory). Then go through the flashboot process for recovery.img. It couldn't hurt to install SuperSU while you're in there, though that's outside the scope of what we're trying to repair right now. Once you're in 4ext, under the Wipe menu, there should be an option for "Wipe all partitions other than sdcard" (paraphrased). Go with that. Though if the stock recovery didn't do it, I don't have high hopes for 4ext to be able to.
The fact that you're getting multiple mounting errors leads me to believe you have a bad eMMC. If all the steps from the previous post fail, that'll tell you for sure.
Click to expand...
Click to collapse
Okay. Just gotta wait since I let my dad borrow my laptop. Should be home soon. If it is emmc, where does that put the phone? Beyond repair? If so I'm not to worried since I'm upgrade eligible soon. Just worried that I'm gonna get stuck in a bootloop and have to use the recovery option from fast boot since thats the only thing that cures the bootloop (until next battery pull) and start over again. Pain in the butt!
Sent from my PG86100 using xda app-developers app
I would recommend that you do a Titanium Backup, but since you don't have root that's out of the question. Kind of an unfortunate situation. I've never done this, but it seems like you could probably use Online Nandroid to make a nandroid backup of your working system. Then if you ever get stuck in a boot loop, you could restore the backup to your current (hopefully) working configuration. It doesn't help you right now, but it might help in the future. Just make sure to root it while you're doing all this.
I believe eMMC is on the main logic board. You might want to call Sprint to confirm, but it stands to reason that you could probably swap in another one. I'm noticing a couple on eBay in the 30-40 dollar range. Not sure if there are any phone-specific values on the logic board that make the board unswappable, but hopefully Sprint could tell you for sure.
Maybe you'll get lucky and that's not the problem anyway.
Tourney3p0 said:
I would recommend that you do a Titanium Backup, but since you don't have root that's out of the question. Kind of an unfortunate situation. I've never done this, but it seems like you could probably use Online Nandroid to make a nandroid backup of your working system. Then if you ever get stuck in a boot loop, you could restore the backup to your current (hopefully) working configuration. It doesn't help you right now, but it might help in the future. Just make sure to root it while you're doing all this.
I believe eMMC is on the main logic board. You might want to call Sprint to confirm, but it stands to reason that you could probably swap in another one. I'm noticing a couple on eBay in the 30-40 dollar range. Not sure if there are any phone-specific values on the logic board that make the board unswappable, but hopefully Sprint could tell you for sure.
Maybe you'll get lucky and that's not the problem anyway.
Click to expand...
Click to collapse
Normally i use App Monster Pro. No root. Im going to back up and and flash the recovery right now. Ill let you know what happens. Hopefully this works.
well i removed the battery and sd card and replaced the battery and she booted up fine! no bootloop this time. Maybe its the sd after all? but i think your right cause i get cant mount cache recovery command and thats not on the sd like you said. Im going to boot back down, remove battery reinstall sd and then see if it boots up.
EDIT: reinserted sdcard and it booted up fine AGAIN. Why phone?! haha. Wonder what was causing the bootlooping when the battery was removed?
I checked for those locations in my cache directory and they don't exist for me either. That probably means they're created dynamically during recovery, but I know very little about what happens behind the scenes there. Maybe certain parts of your cache are unwriteable. Just to clarify, the mount errors happened even while the sd card was out and continued to exist even after it was put back in, right? Maybe it's the sd card after all if not. Any errors while wiping all the partitions?
Glad to hear that it's at least sort of working for now. Couldn't hurt to do a nandroid backup anyway just in case it happens again while you're out and about and don't have time to do a full manual reinstall.
Tourney3p0 said:
I checked for those locations in my cache directory and they don't exist for me either. That probably means they're created dynamically during recovery, but I know very little about what happens behind the scenes there. Maybe certain parts of your cache are unwriteable. Just to clarify, the mount errors happened even while the sd card was out and continued to exist even after it was put back in, right? Maybe it's the sd card after all if not. Any errors while wiping all the partitions?
Glad to hear that it's at least sort of working for now. Couldn't hurt to do a nandroid backup anyway just in case it happens again while you're out and about and don't have time to do a full manual reinstall.
Click to expand...
Click to collapse
Haven't flashed the recovery just yet. My primary goal was to get this boot looping to stop. Success! I will flash recovery tonight. And I haven't checked the recovery.
Sent from my PG86100 using xda app-developers app