My friend swears up and down that a .ziped system wipe is different then just going into CWR and wiping the data, cache, and divik manually. I tried to reason with him and let him no that wiping the data is your system, but he wont listen. LOL he's like it wipes the partition and the system. I told him the zip file that he's using just contains all the files data, cache, divik to do the all at once. Still the guy is so stubborn.
Thanks for sharing.
Bro: cool story
/sarcasm
/no flame
/not rly srs
oh my bad i forgot no one shares on the internet and blogs. Wait is this a forum with trolls complaining about anything and everything, ya I think I'm iin the right place. Listen my friend and I had a valid argument that maybe some people can clear up. You guys dont have to pick at everyone and everything to make it seem like your better then someone else. RELAX!
So you come in with some pseudo-technical babble (WTF is a ".zipped system wipe?"; "the data is your system," - no, data and system partitions are different). You're obviously looking for some sort of validation that "you're right, your friend's stupid."
abvthegod said:
oh my bad i forgot no one shares on the internet and blogs. Wait is this a forum with trolls complaining about anything and everything, ya I think I'm iin the right place. Listen my friend and I had a valid argument that maybe some people can clear up. You guys dont have to pick at everyone and everything to make it seem like your better then someone else. RELAX!
Click to expand...
Click to collapse
You can't argue with an idiot.
Sent from my Verizon 4GLTE HTC THUNDERBOLT
mike.s said:
So you come in with some pseudo-technical babble (WTF is a ".zipped system wipe?"; "the data is your system," - no, data and system partitions are different). You're obviously looking for some sort of validation that "you're right, your friend's stupid."
Click to expand...
Click to collapse
Thats what I'm saying that his zip wipe file is the same thing, as doing it manually. I also told him that the manaul data wipe will wipe a parition if you do have a partition. yes my friend is very stupid, I guess you know the type, I guess you do follow the forums a lot.
HAHAHA this post made me laugh to myself. Thank you sir.
But seriously, you would've got the same response if you went into a McDonalds and tried to tell the same story to a random group of people. "Cool Story Bro"
I don't know who really uses wipedatacachesystem.zip...If he does it one way, and works for him, good for him. I hope you're proud, and with your super knowledge decided to tell him there's more than one way to skin a cat. Congrats! I bet he owes you something (2 big thumbs up) for showing him a way to wipe his phone, the same way almost everyone else does.
Pure entertainment gold. ;-)
abvthegod said:
My friend swears up and down that a .ziped system wipe is different then just going into CWR and wiping the data, cache, and divik manually. I tried to reason with him and let him no that wiping the data is your system, but he wont listen. LOL he's like it wipes the partition and the system. I told him the zip file that he's using just contains all the files data, cache, divik to do the all at once. Still the guy is so stubborn.
Click to expand...
Click to collapse
So he's wrong because he doesn't do it your way?
Sent from my Transformer TF101 using XDA Premium App
I don't want to...but I have to:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
joshnichols189 said:
So he's wrong because he doesn't do it your way?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I mean you quoted me, But you still didnt read it. I never said he was wrong nor is it wrong to use some kinda of zip file to wipe everything all at once. What he was saying though about the zip file having some magic powers to be more of a wipe then just doing it manually. Thats it I thought it was kinda funny that he was calling it a "whole system wipe" and just wiping the data wouldnt do the samething.
i assume the zip file you're referring to is like the caulkin's wipe all zip (or something like that). it does the same thing that cwr would do, send adb commands to format partitions. nothing really different as they both do the same. either way, "format SYSTEM:" isn't being done.
Related
I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
Repartition 2048 and 0.
Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.
Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Congrats, man. I think you're the first to truly brick his gtab.
tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.
Thanks KJ, I will try those when I get home this evening.
I noticed people complain about errors on a brand new flash of a ROM, errors that I never had, or any other use never had. On occasion, flashing data will leave settings/apps intact and actually not do anything at all..so to follow a complete fail proof guide on ensuring a brand new flash...do the following.
1. Wipe data TWICE (2x) one after the other.
2. Flash the ROM. (ONCE)
3. Wipe cache partition. (2x)
4. Wipe dalvik cache. (2x)
5. Fix Permissions. (2x)
REBOOT.
Leave your phone idle IMMEDIATELY after booting for 10 minutes so the phone's background services and first-time use settings can process themselves. Doing this will provide you the most stable flash, and any force closes / crashes more than likely will be the ROM's fault if you followed all steps to the "T.".
This may not be well known to everyone. Whatever. If you don't find it useful, don't comment. If you do, comment. If you need help or have any questions, post them and I will be sure to answer you as quick as possible.
I've always wondered, what's the point of doing wipe twice?
djh said:
I've always wondered, what's the point of doing wipe twice?
Click to expand...
Click to collapse
On occasions (and this is ALSO true with the SGH-t989)
The ROM won't be completely wiped. It will incorporate the old data with your new ROM and cause force closes, or black screens, slower, lower battery life, etc.
By doing this twice, you ensure yourself the platform is ENTIRELY clean and ready for a new version of the ROM.
For example, I once flashed GOV2, over GenericGinger and STILL HAD a green theme. That's how I knew something was wrong. From there on then, I ALWAYS ALWAYS ALWAYS like a religion, wiped twice. There's no reason NOT to do it. It takes very little time, and is added insurance to a fully functional and stable ROM.
Edit : If no one likes the method, by all means do things your own way ; whatever works for you works ; however I do things judging on the fact from experience of using/doing them.
TheLastSidekick said:
On occasions (and this is ALSO true with the SGH-t989)
The ROM won't be completely wiped. It will incorporate the old data with your new ROM and cause force closes, or black screens, slower, lower battery life, etc.
By doing this twice, you ensure yourself the platform is ENTIRELY clean and ready for a new version of the ROM.
For example, I once flashed GOV2, over GenericGinger and STILL HAD a green theme. That's how I knew something was wrong. From there on then, I ALWAYS ALWAYS ALWAYS like a religion, wiped twice. There's no reason NOT to do it. It takes very little time, and is added insurance to a fully functional and stable ROM.
Edit : If no one likes the method, by all means do things your own way ; whatever works for you works ; however I do things judging on the fact from experience of using/doing them.
Click to expand...
Click to collapse
All that fixing permissions will do is make a apk readable and writable, I believe it isn't necessary after 2 wipes.
insanedrunk said:
All that fixing permissions will do is make a apk readable and writable, I believe it isn't necessary after 2 wipes.
Click to expand...
Click to collapse
I may have been dramatic with the fix permissions bit, but it is what I've been doing since I started picking up the GenericGinger project and it hadn't failed me once. I do however recommend doing everything else (mostly the data format) TWICE.
djh said:
I've always wondered, what's the point of doing wipe twice?
Click to expand...
Click to collapse
It's really silly.
It is a problem with some developers cwm updater-scripts. Rather then formating partitions, they just rm -rf the data on the partition. Then they unmount the filesystem without syncing first.
If you don't sync before unmounting, the deletions might not happen.
So, the effect that some users see by wiping twice is that when the filesystem mounts again, the deletions that happened before get "fsync()"ed by the filesystem driver and it appears that formating twice does the right thing.
So developers are causing the problem without understanding the problem.
bhundven said:
It's really silly.
If you don't sync before unmounting, the deletions might not happen.
Click to expand...
Click to collapse
That sure make sense. Thanks for explaining
So you mean the entire time every time I had this problem, it was due to that damn script? This thing happens on like every ROM Lol...
I can take a crack at adding fsync...but should I add it after RM -rf or change it altogether? What do you recommend?
Sent from my SGH-T989 using xda app-developers app
Probably a little too simple, but is this right bhundven?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bhundven said:
It is a problem with some developers cwm updater-scripts. Rather then formating partitions, they just rm -rf the data on the partition. Then they unmount the filesystem without syncing first.
Click to expand...
Click to collapse
This thread saved my bacon -- I was contemplating messing about with Odin/Heimdall to try and format partitions manually after 'adb restore' command filled up my internal storage on a Samsung Galaxy S4 Mini with ~3GB of unreachable mess. The CWM factory reset option didn't clear it, but executing 'factory reset' and also 'format /data and /data/media (/sdcard)' from the Mounts and Storage Menu twice did the trick. Not entirely certain if it was a missing sync issue or just a matter of specifically selecting 'format /data and /data/media (/sdcard)', but this thread led me to a much safer solution than bootloader tools!
Is this method guarantee a security delete, which means that impossible to recover data by any recovery software?
Hi there, yes I am a noob here but I searched this and couldnt find anything.
I flashed two HTC one S phones and am having the same issue with both. Everything works great except the mobile data.
Mobile data is turned on in settings, but says disconnected. Wifi works great, the phone makes calls, just no mobile data.
I searched networks and it sees my network "Fido" and even registers with Fido, but it still says disconnected next to the Mobile Data option in settings.
I will try calling our provider I suppose but I am stuck at this point..
I have also wiped cache, and dalvik cache and did a full wipe at install.
Recovery - CWM 5.8.3.1
ROM - ViperOneS_v1.2.0
Please help!
Sorry guys. I got it.
I had to search the carrier specific APN settings and manually enter them.
I didnt read anything about that anywhere and like I said... Im still a noob.
thanks
you dont have by any chance a nandroid backup with the original settings of your fido phone.
or at least the original build.prop
Trashking said:
Sorry guys. I got it.
I had to search the carrier specific APN settings and manually enter them.
I didnt read anything about that anywhere and like I said... Im still a noob.
thanks
Click to expand...
Click to collapse
you did good "noob"
apn's are first place to check if no data
ultimul said:
you dont have by any chance a nandroid backup with the original settings of your fido phone.
or at least the original build.prop
Click to expand...
Click to collapse
I did a backup from the "backup and restore" option within CWM recovery, just after I had unlocked and rooted. I had not yet installed the the Viper ROM, which leads me to believe it probably still had the correct settings at that time, but not sure.
wow, can you please put that backup somewhere online?
or at least take out the build.prop file from /system folder
pleaseee
PS: CWM recovery just sucks on this model; better use TWRP
If you post the backup Trashking, make sure you note it was made with CWM and needs restored with CWM. As, most of us use TWRP recovery--
so, don't want to make it available for others?
ultimul said:
wow, can you please put that backup somewhere online?
or at least take out the build.prop file from /system folder
pleaseee
PS: CWM recovery just sucks on this model; better use TWRP
Click to expand...
Click to collapse
Hey,
Sorry I hadn't logged in for a couple days. Ill help out if I can.
okay,
this is the folder that I have that contains the backup files. I'll need specific instruction on what exactly you need uploaded, and where I can upload it to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
Im also abit worried this backup may contain personal information, as Im not sure I did a full wipe until I installed the rom. This backup was done after I had unlocked and loaded CWM. I'd like to be sure none of my crap is getting posted.
Also,
Can you please explain why CWM is crap for this model? It seems to work fine on mine but perhaps im missing something.
Upon further review, it seems the reasons most people prefer TWRP over CWM for interface reasons.
Im not sure im worried about that.
I have to disagree with a few posts here, you can do everything the same way with both recoveries. You don't need to flash the boot image in fastboot with cwm I've done it myself and I didn't see any difference in speed between the two backing up or restoring.
It's preference on which you choose to use, I'm not saying that either is bad they both have a great support background and are dedicated to quality as they should be, it's the most important software on your device in consideration to root users and without it working properly your taking a very large risk.
Personally believe recovery should be layed out in a manner that is easy to use and functional for all types of users, adding gimmicks to something that should be taken seriously I feel is unnecessary and both teams do a great job of keeping it clean and treat the work as if they are paid to make them.
Both are great at their work, both are worth having. - Orical
Click to expand...
Click to collapse
Hi Guys! I know this is a question that many of you wondered, if in specs sensation is mentioned with four Gigabytes why we just got one?
I used Z test and search for memory on it, and look a this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wanna anybody explain me this. Seriously. What are those 2.25 Gigabytes doing there? Nothing, are not sytstem storage, are not cache partition, then, what that? I'd appreciate know it and another question, is there any tool or method to get this space into data partition?
ATTACHED THUMBNAILS
migui0401 said:
Hi Guys! I know this is a question that many of you wondered, if in specs sensation is mentioned with four Gigabytes why we just got one?
I used Z test and search for memory on it, and look a this
I wanna anybody explain me this. Seriously. What are those 2.25 Gigabytes doing there? Nothing, are not sytstem storage, are not cache partition, then, what that? I'd appreciate know it and another question, is there any tool or method to get this space into data partition?
ATTACHED THUMBNAILS
Click to expand...
Click to collapse
2.25GB is devided by data,system,cache some other minor partitions..That app just sums them up in a stupid way.
Just forget about it, you got what you got and there is no way for you to change it!
ivicask said:
2.25GB is devided by data,system,cache some other minor partitions..That app just sums them up in a stupid way.
Just forget about it, you got what you got and there is no way for you to change it!
Click to expand...
Click to collapse
Is not just this app, i've seen it by other ways and that is not just data, sytem and cache partition. There are some others partition that app doesnt show apart of those 128 and 256 megabytes, if that MBs where doing something i would care about but are lost doing nothing.
migui0401 said:
Is not just this app, i've seen it by other ways and that is not just data, sytem and cache partition. There are some others partition that app doesnt show apart of those 128 and 256 megabytes, if that MBs where doing something i would care about but are lost doing nothing.
Click to expand...
Click to collapse
if i remember well there is a fastboot command which shows you all partitions and their sizes
some partitions are completely empty
rzr86 said:
if i remember well there is a fastboot command which shows you all partitions and their sizes
some partitions are completely empty
Click to expand...
Click to collapse
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
migui0401 said:
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
Click to expand...
Click to collapse
AFAIK we can't repartition emmc as we want
i think it is impossible
migui0401 said:
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
Click to expand...
Click to collapse
There is NO space lost, those are "fake" partitions, just kernel mount points, try running same command when phone is not booted from recovery and it will show you real stats, also regardless of all of this we CANT re-partition Sensations nand even if we wanted...So discussion is pointless.
Hello all,
I just tried to make my Nexus 5 read NFC while on the locked screen using this thread.
http://forum.xda-developers.com/nexus-4/development/mod-modified-nfcnci-apk-to-poll-screen-t2391170/page3
Apart from it not working (rooted, read/write, permissions set, etc....) I now get the following error mesage when I try to onter the setting on my Nexus.
"unfortunately, settings has stopped"
Placed back the original 'NfcNci.apk' and 'NfcNci.odex' files with no result.
I did a lot of searching, but cannot find a solution.
I hope anyone can help my out here.
Thanks in advance !!!!!
Don't suppose you made a nandroid before installing the apk. You could just restore it if you did. OtherWise you might have to flash the system.img from the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
Forgot to mension that :silly:
I backed up the original 'NfcNci.apk' and 'NfcNci.odex' before I started. Already placed the back, with no results.
keroner said:
Forgot to mension that :silly:
I backed up the original 'NfcNci.apk' and 'NfcNci.odex' before I started. Already placed the back, with no results.
Click to expand...
Click to collapse
Try clearing data for it if there is any, then try clearing cache?
Lethargy said:
Try clearing data for it if there is any, then try clearing cache?
Click to expand...
Click to collapse
Can you explain how to do this. If it's in the settings menu, it's a problem since I can't get in the settings........
keroner said:
Can you explain how to do this. If it's in the settings menu, it's a problem since I can't get in the settings........
Click to expand...
Click to collapse
And wipe cache + Dalvik in recovery
/data/data
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If that doesn't work you can just make a nandroid backup, flash factory images, use Titanium Backup to backup the fresh Settings.apk/NfcNci.apk/data then restore your nandroid and restore the TiBu backup of those two
Lethargy said:
And wipe cache + Dalvik in recovery
/data/data
If that doesn't work you can just make a nandroid backup, flash factory images, use Titanium Backup to backup the fresh Settings.apk/NfcNci.apk/data then restore your nandroid and restore the TiBu backup of those two
Click to expand...
Click to collapse
Deleted the content in com.android.nfc. No luck.
Dalvik is new to me.
What I discovered is that the 'NfcNci.apk' looks different after replacing it.
It first looked like a bluetooth logo (the backup on sd still does). But after copying it to 'system/app' it looks like an android robot coming out of a blue box with APK written on it.
When I trie to run the 'NfcNci.apk' it gives me a parse error.
keroner said:
Deleted the content in com.android.nfc. No luck.
Dalvik is new to me.
What I discovered is that the 'NfcNci.apk' looks different after replacing it.
It first looked like a bluetooth logo (the backup on sd still does). But after copying it to 'system/app' it looks like an android robot coming out of a blue box with APK written on it.
When I trie to run the 'NfcNci.apk' it gives me a parse error.
Click to expand...
Click to collapse
Delete both the .apk and .odex, along with data folder then reboot to recovery, clear cache and Dalvik, boot into android and put the backed up files back into /system/app with correct permissions and reboot again. If it doesn't work then try the other method I suggested previously, if that doesn't work I don't know what to tell you lol. Also try clearing data of Settings itself
Thanks for all your help thusfar Lethargy!!!
If you can only tell me how to "clear cache and Dalvik" I will give it a go.
I'm a bit new to android so please forgive me for any simple questions......
keroner said:
Thanks for all your help thusfar Lethargy!!!
If you can only tell me how to "clear cache and Dalvik" I will give it a go.
I'm a bit new to android so please forgive me for any simple questions......
Click to expand...
Click to collapse
Depends on what recovery you're using, TWRP or CWM. In CWM it should be in advanced, in TWRP tick the boxes for it in wipe. Search it up if you're not sure.
On the other hand, "Unfortunately, Lethargy is falling asleep"
Different timezones i guess
I ended up flashing and restoring the apps one by one. So far so good.......
keroner said:
Different timezones i guess
I ended up flashing and restoring the apps one by one. So far so good.......
Click to expand...
Click to collapse
Always make a nandroid backup when doing system modifications lol
Lethargy said:
Always make a nandroid backup when doing system modifications lol
Click to expand...
Click to collapse
That my friend is something I learned the hard way
keroner said:
That my friend is something I learned the hard way
Click to expand...
Click to collapse
Hard way is the best way to learn sometimes