Related
Hi Guys,
I've posted in a couple of threads but didn't let loose for fear of hijacking it, so putting my question here for the good fellows to respond to if possible.
Basically put I have a ROM installed (Kang-o-rama SP1) and have a 1GB A2SD partition courtesy of DarkTremor.
What I want to know is what process should I go through to flash a new ROM but retain that Ext partition? I'm not sure if this is even possible? Should the wipe wipe absolutely everything and then after flashing the ROM I should rebuild the EXT partition and then use Titanium Backup (or something similar) to restore my apps to that A2SD partition?
Can somebody please just tell me what the best process is (even if that means wipe everything, and recreate from scratch each time you flash.
I was under the impression you see that I could wipe everything but retain the actual partition (albeit wiped) to restore apps to after a new Flash?
Thanks in advance
Probably your best bet is to use Titanium. When you restore, look for the setting in the app that mentions something to the effect of attempting to integrate your backup into a different ROM (Sorry don't have app in front of me).
You can also use ADB to pull your sd-ext to your computer. Push it back when you have the new ROM set up with ext
adb pull /sd-ext c:\whateveryouwanttocallit
I use Amon Ra's Recovery but I think Clockwork Mod has an option to backup just your sd-ext.
I want to do a full wipe of all data when going from ROM to ROM installing to EMMC.
So far each time I install, some files are left over in one or other area.
I have yet to find a complete answer/quide on how to go about completely cleaning everything before installing a new ROM?
(Ideally the equivalent of formating and partitioning before installing Windows...)
At the moment I am cautious to try the WIPES and FACTORY RESET options in CWM as I have not found a solid answer as to what they do here.
(Is CWM the way to go here?)
Thanks for any help
There is utility like that for GTAB but didn't see one for NC
http://forum.xda-developers.com/showthread.php?t=974422
And in this post all the way down in OP:
http://forum.xda-developers.com/showthread.php?t=985705
Let me see if I understand this correctly, you're saying you manually format each partition under CWR and are sketched about using the factory reset function? Ive both wiped and flashed between various emmc based roms as well as EXT4 based roms to the (EXT2?) based roms without a problem. Each time I use the correct CWR and manually format /system, /data, and /cache. If i'm understanding your question correctly then I hope this helps. It may not be the fix you're looking for but it works.
stevencpoynter said:
Let me see if I understand this correctly, you're saying you manually format each partition under CWR and are sketched about using the factory reset function? Ive both wiped and flashed between various emmc based roms as well as EXT4 based roms to the (EXT2?) based roms without a problem. Each time I use the correct CWR and manually format /system, /data, and /cache. If i'm understanding your question correctly then I hope this helps. It may not be the fix you're looking for but it works.
Click to expand...
Click to collapse
yeah - thanks, i think that is pretty much what i am after.
What is the difference between factory reset/wipe and formating the system/data partitions?
Is there anything on the boot partition that might get left over?
hi,
i'm usin ra passion 2.2.1 and wan't to use a2sd from ics 4.0.3 evervolv. how can i create a part ext4?
Google:
"a2sd partition sd card".
Enjoy.
Try 4EXT recovery www.4ext.net
I think its the easiest way to create partition.
Or else you can do it in pc via partition managers(i use minitool partition wizard)
You can google it and also can search in youtube for video tutorials.
Sent from my Nexus One using Tapatalk
thanks for your help, i've done it in recovery.
one question is left:
what happen if i format the partioned sd-card under windows and do a full wipe in preparation for installing a new rom. i've read sd-ext even survive a full wipe? what does that mean? stays the partition untouched when i format the sd-card with windows? and what about the apps in the partition? are they still there even after a full wipe and can i use them after flashing a new rom out of the box?
Glad u succeeded in partitioning
Now if you format the fat32 partition in windows using those partition tools doesnt affect ur ext. Ext stays untouched but all the data on fat32 will be wiped(so backup first to pc)
If u want to merge there is an option called merge for that.
There is an free windows software called sdformatter, that formats the entire sdcard(fat32+ext)
Hope i helped a bit :thumbup:
Sent from my Nexus One using Tapatalk
ok. i wan't to format it with the windows internal function via right click. is it the same and the ext4 stays untouched?
Full wipe in recovery wipes SD-EXT too.
heinz gruber said:
ok. i wan't to format it with the windows internal function via right click. is it the same and the ext4 stays untouched?
Click to expand...
Click to collapse
i do beleive that it should be untouched, cos normally windows cannot see the ext partition and hence only fat32 will be formatted
Sent from my Nexus One using Tapatalk
ok. when ext4 stay untouched and i flash a new rom the apps are still in the launcher after flashing?
Jack_R1 said:
Full wipe in recovery wipes SD-EXT too.
Click to expand...
Click to collapse
when i flash a new rom i use the format.zip form the xda user temasek which wipes system, boot, data and cache. so is sd-ext untouched when i use this file?
You insist on not listening and/or not understanding.
When you select "wipe data/factory reset" in custom recovery, EXT partition IS WIPED COMPLETELY. It doesn't stay.
I believe the same happens when using temasek's script, never bothered using it, so I can't say with 100% certainty.
If you don't wipe your phone and install a new ROM - be prepared for crashes of anything to everything, unless you install a ROM which is 100% compatible with what you have already - the next generation of the same ROM, usually.
If you're using A2SD and don't wipe EXT partition - you'll have crashes as soon as you boot, since system apps' data will be there (and wrong).
To keep your apps and their data, use one of the backup apps available in the Market, like Titanium Backup.
as Jack_R1 explained its always better to wipe everything(system,cache,dalvik n sdext) to be on safer side to avoid crashes n FCs.
Sent from my Nexus One using Tapatalk
Temasek's Extreme Wipe does Data/System/Boot partitions but don't remember seeing ext in the list
However, as alluded too, I would format all outside phone with sdformatter or I think gparted, although never used that one
I thought I read a long time ago Windows formatter not recommended and do a full wipe not partial with whatever you use
Back up sdcard first
also, I believe you can use the Alignment Cool zip to get ext 4 from 3 on Amon and not lose anything--still backup
you do know MeDroid uses Ia2sd and different from a2sd on implementation
You don't need to wipe the regular FAT partition on SD card between flashes, because there's nothing there that loads automatically. And "wipe data/factory reset" option in recovery also wipes /sdcard/.android_secure.
hey guys, thanks for your answers i will keep them in mind.
edit:
one more question:
if i uses temaseks script and the sd-ext is untouched and i flash a newer version of my rom, are the apps then still there after flashing and booting the updated system? or is there another step i've to do?
No, the apps aren't there anymore - or to be correct, the apps are there, their data is gone (because the app data doesn't reside on EXT partition, unless you use specific mounting methods).
When you flash an updated version of your ROM, just don't wipe anything at all unless the instructions specifically mention having to wipe before installing that version. That means - don't execute temasek's script at all.
Now with the release of many JB leaks for our Galaxy Note, more and more people are starting to flash custom ROMs into their devices. However, many don't do a proper clean-up / wipe of their devices before doing so, complaining about supposed "bugs" that in fact are not real bugs, but just incompatibilities with previous app data and config left from the previous ROM or improperly restored from backups (TB etc.).
So, after facing that myself with the first ROMs I flashed, reading a lot of tips from the senior members, and experimenting different approaches, I came up with a method that I always follow before flashing a new ROM, which gives me less or no issues at all.
Pros: you minimize the chance of having issues when flashing a new ROM.
Cons: you have to manually reinstall your apps (can be somewhat automated from Google Play) and reconfigure everything.
Pre-reqs: I'm assuming you have CWM installed and know how to use it, and are not a complete noob. If you don't, search the forums and read the guides. Read this guide fully and make sure you understand everything before proceeding.
IMPORTANT: ONLY wipe your device if you have a SAFE (BRICK-FREE) KERNEL. Check your kernel and search the forums. Don't proceed if you are not sure! I'm not responsible for any bricks, unexpected issues that can happen to you or personal data loss because you forgot to backup that! If you want to stay safe, don't want to experiment with your cell phone, it's critical you have it working everytime, stay with the official Samsung ROMs updates you get OTA and don't proceed with this how-to.
How-to:
1) Boot into recovery and perform a full backup (a.k.a. nandroid) to your internal or external SD card.
2) Reboot, and create backups of personal data needed from your apps in your internal or external SD card. For instance, I backup data from apps which are not cloud-based; they usually have a "backup" menu for that.
3) Plug your device into your computer, and copy everything you need from your internal and external SD cards (including the backups done in 1) and 2)). Don't forget your pictures and MP3 files.
4) Delete any apps and data from your external SD card. Leave it as clean as possible (it's OK to leave personal data such as MP3s, pictures etc.).
5) Copy the ROM you are about to flash to your EXTERNAL SD Card (don't copy to internal, because we are going to wipe it).
6) Boot into CWM Recovery and do the following wipes:
6.1) Wipe data / factory reset
6.2) Wipe cache partition
6.3) Advanced -> Wipe dalvik cache
6.4) Mounts and Storage -> Format /system
6.5) Mounts and Storage -> Format /preload
6.6) Mounts and Storage -> Format internal SD card (make sure you know if your internal SD card if /emmc or /sdcard; see below!)
7) Install Zip -> Flash ROM from your external SD card.
8) Wipe cache partition again.
9) Advanced -> Wipe dalvik cache again.
10) Reboot
11) Don't restore anything from Titanium Backup. Reinstall and reconfigure everything from Google Play. I never tried but I think that if you just restore user apps, it should work. Just never restore system apps and data. The backups you created in step 2) and copied to your computer in step 3) can be safely restored from within the apps themselves.
Now you may ask why we format the internal SD card. Many apps store their configuration and app data there, so this way we ensure no old data and config are there which may be incompatible with the new ROM. In fact it might not be that important, since it's only related to user apps, but I prefer to clean everything before flashing a new ROM.
How to find if your internal SD card is mounted on /emmc or /sdcard in CWM Recovery:
1) Boot into CWM Recovery.
2) Install Zip -> Choose zip from internal sdcard. In the top you can see where yours is mounted (/emmc or /sdcard).
3) This is the partition you should format in step 6.6. Pay attention to not format the external SD card, because the ROM zip file is there!
If you still have issues after flashing a new ROM, try to reflash it without any wipes (i.e. just do step 7 again).
Hope it can help people with their flashing!
Good job
Is it any better to just install user apps from google play and then restore just the data from TB?
Sent from my GT-N7000 using xda app-developers app
allansy said:
Is it any better to just install user apps from google play and then restore just the data from TB?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
No..the main purpose of the thread is to remove the incompatible app data and system data
Useful.
Sent from my GT-N7000 using xda premium
dbolivar said:
How-to:
6.1) Wipe data / factory reset
6.2) Wipe cache partition
6.3) Advanced -> Wipe dalvik cache
6.4) Mounts and Storage -> Format /system
6.5) Mounts and Storage -> Format /preload
6.6) Mounts and Storage -> Format internal SD card (make sure you know if your internal SD card if /emmc or /sdcard; see below!)
7) Install Zip -> Flash ROM from your external SD card.
8) Wipe cache partition again.
9) Advanced -> Wipe dalvik cache again.
10) Reboot
Click to expand...
Click to collapse
6.2 ---> unnecessary, because factory reset wipes user data and cache
6.6 ---> how on earth does formatting internal SD card help flashing any Rom?
8) ---> unnecessary, because your cache is already wiped
9) ---> see above
6.2) True, thanks for pointing out.
6.6) Some apps, including ones that usually give strange issues between ROM flashes like SNote, leave data there which may cause incompatibilities with a different version. This incompatibility is just a guess; as I said in the original post, it may not be that necessary to format the internal SD card, but I prefer to make sure there is no old data at all floating around, and this recommendation can also be useful when people are going to sell their devices (many think that just a factory reset is enough).
8) and 9) Is it possible that a new ROM can come with stuff in cache and dalvik cache, say, from the developer testing/cooking environment? If it is, can be useful to clean it again after flashing. Otherwise, I agree, it can be skipped.
Yeah total clean scenario is best. In my opinion. So also SD, but never efs
Sent from my GT-N7000 using Tapatalk 2
I too do things that are not necessary, I have a ritual when doing a deep clean lol
It involves things like the above method, but i do it twice.. No harm in that is there !
azzledazzle said:
I too do things that are not necessary, I have a ritual when doing a deep clean lol
It involves things like the above method, but i do it twice.. No harm in that is there !
Click to expand...
Click to collapse
Wel, better safe then sorry. Totally clean just feels right
Sent from my GT-N7000 using Tapatalk 2
Thank you very much. I will do this like you say.
I have CWM v6.0.1.2 and I don't have format/ preload. What can I do?
You can try to proceed without formatting it, or you can first flash a kernel with a more recent CWM. Always a safe kernel, of course. After flashing it, you can just select "reboot recovery" from your current CWM to boot into the new CWM. I'm not sure if the absence of /preload is due to an old CWM, or it's because you don't have a /preload partition. Anyway, trying a newer CWM won't harm.
i follow this guide , considering that i'm a noob it mean that is written really really clear. Thanks for all your job . i have a clean cooked rooted cell now.
error preload
Hello, I got error when formatting preload
it is said "make_extf4fs failed on/dev/block/mmcblk0p9
and when i'm trying to format/scard it pop up some type format
"deafult
"exfat
"fat
bla bla bla
so i choose default, am i right to choose it?
what should i do?
What device, what recovery, what rom?
dbolivar said:
flashing!
Click to expand...
Click to collapse
Hey bro,
i forgot to do step 9
9) Advanced -> Wipe dalvik cache again.
Phone is working fine, but just curious. will it have any effect ? or will it cause any problem later ?
Question: I want to wipe everything from my HD+ and start completely fresh. What is safe to wipe and how do I do it in TWPR or CWM? A "factory reset" isn't good enough. It leaves old data around. But I've read too many stories about bricking a device by formatting /data using CWM.
Background: I've been running CM 10.2.1 for a few weeks now. Given what Jon Lee posted about Google and security, I thought I'd try a clean install of CM 10.2.1 without installing gapps, just to see what that's like. (And what services don't run.)
So I did the usual "factory reset" from TWRP and reinstalled CM 10.2.1. To my surprise, when I booted, the latest version of Google Play was still showing on the launcher!
I had used Link2SD to integrate the latest version of Google Play with the OEM system app. So apparently, that this was not wiped. And of course, internal media data is not wiped (not by TWRP, anyway) in a factory reset. But I thought /system was.
The TWRP FAQ has a page about wiping. It says
Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data.
Click to expand...
Click to collapse
But they don't tell you which to select.
TWRP makes it confusing by offering to 1) wipe data, 2) internal storage, 3) SDcard or 4) SDcard data in Advanced Wipe. Which is it for wiping your media stuff?
From what I've read, "internal storage" should be the same as "SDcard." So why both? And how is "SDcard data" distinct from those two?
To make matters worse, in the Nook I thought there was an additional element of confusion because the Nook doesn't call the internal SDcard memory what everyone else calls it.
So let's say I am selling my HD+. Would I select all of the above and still be able to install a ROM clean?
Or would I brick?
I know that on a desk top computer if you want to start bare metal, you format the hard drive, wiping everything, and install onto that. But judging from what Succulent wrote in his blog about recovering from an EMMC crash, you can't start totally clean with Android. Apparently, Android needs some preexisting files on the "drive" in order to install. (Like the devconf folder, which contains your MAC and your serial number.)
[Am I understanding him correctly? He was talking about recovering from a tablet wrecked by the EMMC brick bug. Perhaps no /data partition at all, as he offers a script to rebuild/expand that partition?]
I have read stories of people bricking their tablets by formatting /data from CWM. I don't understand why that should brick it. Why couldn't you boot into recovery? How can the /data partition affect the /recovery partition?
So - has anybody done a complete wipe on their Nook HD+? Please explain, for those of us who are obsessive compulsive, exactly how you do it.
To wipe your device with CWM go to mounts and storage and format /system, /cache and 'data and datamedia'. A normal factory reset only wipes /cache and the portion of /data that does not hold your media files. It does not wipe /system. Usually the ROM install does that, but the install script has a feature that saves gapps if you are installing the same version of the ROM (eg, CM11 over CM11). So to get rid of everything, including media files and gapps, do what I said in the first sentence. Of course after formatting /system you must put a ROM back on it for it to boot.
And it is not /data formatting that is the brick problem, it is formatting the /bootdata partition. They are different things. Don't format that.
And succulent was talking about /rom partition which is different yet that needs to be left alone. That is where the devconf folder is. It contains things you need to keep.
If you want to understand the partition structure of the HD/HD+ go to my HD/HD+ Tips thread linked in my signature and read item 16.
And please read my PM to you about removing those assert removal instructions from my dummies thread.
Sent from my BN NookHD+ using XDA Premium HD app
Best Answer
leapinlar said:
To wipe your device with CWM go to mounts and storage and format /system, /cache and 'data and datamedia'. A normal factory reset only wipes /cache and the portion of /data that does not hold your media files. It does not wipe /system. Usually the ROM install does that, but the install script has a feature that saves gapps if you are installing the same version of the ROM (eg, CM11 over CM11). So to get rid of everything, including media files and gapps, do what I said in the first sentence. Of course after formatting /system you must put a ROM back on it for it to boot.
Click to expand...
Click to collapse
Thanks for the thorough answer. And explanations. I always find it easier to remember something when I understand the reason for it. So I didn't know before that the install scripts keep gapps.(But that's what I was deducing.)
I know to stay away from /rom and /boot. Hopefully, TWRP would not let one format those in their numerous choices for Advanced Wipe.
From what you've written before in one of your other threads, I know that you're not a fan of TWRP. So I still don't know what the similar commands are in TWRP for a total clean. But for now I can delete /system in TWRP and do the reinstall without gapps. When I'm ready for a total wipe, I'll revert to CWM.
Can we trade /factory for /swap?
leapinlar said:
If you want to understand the partition structure of the HD/HD+ go to my HD/HD+ Tips thread linked in my signature and read item 16.
Click to expand...
Click to collapse
Read it. (And made an image of my factory partition. And then moved it to my extSDcard for safer keeping.)
So, the Nook HD+ partition structure is a bit different from the stock Android partition stuff I had found on the web.
So, for those of us running a custom ROM, I presume the factory image doesn't do us much good anymore. Will the HD+ automagically restore after 8 failed boots?
If not (or even if it will), is there a way to take that 448MB in the /factory image partition and use them for, say, a /swap partition instead? I think an xda developer is doing something like this for the Galaxy Tab 2, where he's using some memory that Samsung uses for animations and uses them for ZRam instead. Since I've backed up the factory image, and since I already have your factory 2.0.2 ROM, I really don't need the image any more. Seems like wasted space.
PMikeP said:
Read it. (And made an image of my factory partition. And then moved it to my extSDcard for safer keeping.)
So, the Nook HD+ partition structure is a bit different from the stock Android partition stuff I had found on the web.
So, for those of us running a custom ROM, I presume the factory image doesn't do us much good anymore. Will the HD+ automagically restore after 8 failed boots?
If not (or even if it will), is there a way to take that 448MB in the /factory image partition and use them for, say, a /swap partition instead? I think an xda developer is doing something like this for the Galaxy Tab 2, where he's using some memory that Samsung uses for animations and uses them for ZRam instead. Since I've backed up the factory image, and since I already have your factory 2.0.2 ROM, I really don't need the image any more. Seems like wasted space.
Click to expand...
Click to collapse
You can play with the partitions all you want. Just don't ask me to help you fix it. You don't seem to heed my warnings anyway.
But other users be warned that factory partition has vital backup information there (it has more than just the factory zip there) and if you lose it, your device is as good as a paperweight. That is why I recommended all users back that partition up. Not for the factory zip, but for the backup files there. The device has other safety backup routines other than just restoring the stock ROM. An example is, I told you and succulent told you that devconf has vital files all ROMs need in /rom. Well, /factory has a backup of /rom there and if the device discovers /rom is messed up, it tries to repair itself. No /factory and no repair. Paperweight!
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You can play with the partitions all you want. Just don't ask me to help you fix it. You don't seem to heed my warnings anyway.
But other users be warned that factory partition has vital backup information there (it has more than just the factory zip there) and if you lose it, your device is as good as a paperweight. That is why I recommended all users back that partition up. Not for the factory zip, but for the backup files there. The device has other safety backup routines other than just restoring the stock ROM. An example is, I told you and succulent told you that devconf has vital files all ROMs need in /rom. Well, /factory has a backup of /rom there and if the device discovers /rom is messed up, it tries to repair itself. No /factory and no repair. Paperweight!
Click to expand...
Click to collapse
Thanks for the quick response.
I am sorry that I seem to have gotten on your bad side. I did what you asked and moved my previous comment out of your thread. And I warned everyone that you don't think it's a good procedure.
And I did heed your warning. I made a backup of the factory partition and even moved the copy to my ext SD card for safer keeping. Especially since we were talking about wiping the sdcard. (Unless you're trying to say that storing the /factory img on the ext SD card is a bad idea because I won't be able to get it back to the internal SDcard if/when I need it.)
As for the devconf files, they're in the /rom partition. I don't understand how using the /factory partition for a /swap is going to ruin the /rom partition.
From what you're saying, the HD+ still has a "safety routine" built in, even when running custom recovery and a custom ROM? Does that mean that its safety routine is hard coded somewhere? Or part of the /rom code itself? How does the HD+ know to look in /factory when its running a non-factory OS? Does CM tell it to do that?
You're the expert. I'm just guessing here. If the /factory partition were used as a /swap, and if the system turned into a paperweight because it needed the /factory image later someday, then couldn't one go into recovery and copy the /factory partition back over, per your instructions? As a minimum, couldn't one use succulent's emmc recovery procedure to get back to factory status?
I'd be willing to trade that off for more performance.
How does one know when the HD+ goes into this safety routine? Does it tell you? Or is it transparent to the user? It would be interesting to know how often that happens. Does the safety routine then repair the /rom partition once booted if it detects a problem in /rom?
PMikeP said:
Thanks for the quick response.
I am sorry that I seem to have gotten on your bad side. I did what you asked and moved my previous comment out of your thread. And I warned everyone that you don't think it's a good procedure.
And I did heed your warning. I made a backup of the factory partition and even moved the copy to my ext SD card for safer keeping. Especially since we were talking about wiping the sdcard. (Unless you're trying to say that storing the /factory img on the ext SD card is a bad idea because I won't be able to get it back to the internal SDcard if/when I need it.)
As for the devconf files, they're in the /rom partition. I don't understand how using the /factory partition for a /swap is going to ruin the /rom partition.
From what you're saying, the HD+ still has a "safety routine" built in, even when running custom recovery and a custom ROM? Does that mean that its safety routine is hard coded somewhere? Or part of the /rom code itself? How does the HD+ know to look in /factory when its running a non-factory OS? Does CM tell it to do that?
You're the expert. I'm just guessing here. If the /factory partition were used as a /swap, and if the system turned into a paperweight because it needed the /factory image later someday, then couldn't one go into recovery and copy the /factory partition back over, per your instructions? As a minimum, couldn't one use succulent's emmc recovery procedure to get back to factory status?
I'd be willing to trade that off for more performance.
How does one know when the HD+ goes into this safety routine? Does it tell you? Or is it transparent to the user? It would be interesting to know how often that happens. Does the safety routine then repair the /rom partition once booted if it detects a problem in /rom?
Click to expand...
Click to collapse
If you want to know more how the automatic repairs work, go to my Nook Color Tips thread linked in my signature and read item A12. The partition numbers are different but the repair process works exactly the same way on the HD/HD+, including the need for stock recovery to be installed. There are two ways to get your device automatically repaired if you have CM and CWM/TWRP recovery installed on internal memory. One is to flash stock recovery back per my item 5 in my HD/HD+ CWM thread, and the second is to flash the plain stock zip from item 6 there. That puts stock recovery back. Then it can repair /rom if need be.
And there is no real drawback of removing the factory.zip file from /factory partition since it is basically the same as a plain stock zip I have published. But the other files there are vital and should not be touched.
You got on my bad side by publishing that assert removal procedure on the help forum after I asked you to remove it from my thread. I don't want to make it easy for any user to do that as I consider it dangerous for noobs to do. See my response to your posting of that procedure.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You got on my bad side by publishing that assert removal procedure on the help forum after I asked you to remove it from my thread. I don't want to make it easy for any user to do that as I consider it dangerous for noobs to do.
Click to expand...
Click to collapse
Thanks for letting me know. Later last night, I saw a post of yours on the Nook Color (I think it was) where you thought that anyone who would remove the updater-script safety check was an "idiot."
Okay, so I'm an idiot. But I am free to be an idiot and start my own thread in the Help forum, right? Just as you are free to respond there as you did. That's what makes the forum go 'round.
PMikeP said:
Thanks for letting me know. Later last night, I saw a post of yours on the Nook Color (I think it was) where you thought that anyone who would remove the updater-script safety check was an "idiot."
Okay, so I'm an idiot. But it's my right to be an idiot and my right to start my own thread in the Help forum, right? Just as it's your right to respond there as you did. That's what makes the forum go 'round.
Click to expand...
Click to collapse
As I recall, I did not say the person that removed the assert was an idiot, it was the person who recommended it that I said was an idiot. The user was a noob and knew no better. He was trying to flash a Nook Tablet ROM to his Nook Color and the assert kept failing (doing what it was designed to do). The idiot was the one that told him just to remove the assert. He did that and bricked his Nook Color.
Sent from my BN NookHD+ using XDA Premium HD app