Related
I've been reading .. and in my readings I've read different people saying different things . I heard running task29 a lot can cause bad blocks .. and I flash a lot of ROMs . So I created a task29 zip flash from recovery which formats all nand partitions 3 times in a row to wipe out everything . Is that good for the memory and is that enough to wipe everything clean or should I use task29 every time and not worry about that being the cause of bad blocks ? In short , which is safer ?
Sent from my HTC HD2 using Tapatalk
Well do the math,, task 29 wipes every block once, your zip wipes some three times, which would you suspect as being there times more likely to end in bad blocks?
To be honest what's the point? In 999 out of 1000 flashes its enough to do a 'wipe data factory reset' and then flash.
samsamuel said:
Well do the math,, task 29 wipes every block once, your zip wipes some three times, which would you suspect as being there times more likely to end in bad blocks?
To be honest what's the point? In 999 out of 1000 flashes its enough to do a 'wipe data factory reset' and then flash.
Click to expand...
Click to collapse
Well , in every ROM thread ive read , it says to task29 before flashing . and i thought task29 was a more "harsh" way of wiping the nand . Like a format , does it not just clear the blocks without writing to them ? I personally think either way is still "not good" for the flash memory . But i could be wrong . And i always thought there were "leftovers" from just doing a factory reset ?
In my opinion, task29 is very unnecessary.
Only do it if your device is having issues, otherwise flash roms and bootloaders directly without task29'ing.
By the way, by "task29" they mean empty-rom.nbh .. not empty-rom.zip .
As for the .zip, a full wipe does the same.
Marvlesz said:
In my opinion, task29 is very unnecessary.
Only do it if your device is having issues, otherwise flash roms and bootloaders directly without task29'ing.
By the way, by "task29" they mean empty-rom.nbh .. not empty-rom.zip .
As for the .zip, a full wipe does the same.
Click to expand...
Click to collapse
A full wipe cleans all partitions of the nand ? i thought it just did /userdata . and thank you thats what i thought task29 was . but is flashing an empty .nbh worse then running the format command ?
Let me clarify a few things for you:
Task29: removes everything off your device's internal memory, when you boot your phone after a task29 you will get stuck at bootscreen (first splash), because there is nothing on your device (no bootloader).
Under CWM:
Wipe data/factory reset is different from format that can be found in (mount & storage):
Wipe data/factory reset: does not remove your OS, it will only delete your personal data retaining your ROM intact.
But a format will completely remove your ROM and you will be stuck at the bootscreen if you do so.
Every thing under CWM does not touch your device's bootloader (cLK or MAGLDR), and they only affect the Android ROM within CWM.
Hope this help you
Marvlesz said:
Let me clarify a few things for you:
Task29: removes everything off your device's internal memory, when you boot your phone after a task29 you will get stuck at bootscreen (first splash), because there is nothing on your device (no bootloader).
Under CWM:
Wipe data/factory reset is different from format that can be found in (mount & storage):
Wipe data/factory reset: does not remove your OS, it will only delete your personal data retaining your ROM intact.
But a format will completely remove your ROM and you will be stuck at the bootscreen if you do so.
Every thing under CWM does not touch your device's bootloader (cLK or MAGLDR), and they only affect the Android ROM within CWM.
Hope this help you
Click to expand...
Click to collapse
Yes this i knew thanks though . My question is this , is it safer to wipe the bootloader off using task29 , then starting over , or is it safer to format all partitions of the NAND in CWM before changing to another ROM ?
I don't know which is safer. (or in other words, I don't know which is dangerous )
But if you must do a wipe, I'd recommend "Wipe data/factory reset" . That should do the job. (Most roms format partitions upon installation anyway so I coudn't care less )
Marvlesz said:
Wipe data/factory reset: does not remove your OS, it will only delete your personal data retaining your ROM intact.
Click to expand...
Click to collapse
it also wipes cache partition, the sd-ext partition on your sd card, and clears the .android folder on the fat32 part of the sd card. These last two are the reason many roms wont boot after flashing, even with a task29, since those two areas aren't touched by task29 (or your format zip presumably)
Im with Marvlesz, steer away from task29, , whats the use in removing magldr and cwm only to reflash it?
For me, a clean install would be ,,, cwm - wipe data factory reset - flash the new rom.
Only if the fresh rom doesn't boot after a few times rebooting (and performing a wipe data on the fresh rom, just like how in winmo it was recommended to do a hard reset straight after flashing) would i consider a task29.
Marvlesz said:
I don't know which is safer. (or in other words, I don't know which is dangerous )
But if you must do a wipe, I'd recommend "Wipe data/factory reset" . That should do the job. (Most roms format partitions upon installation anyway so I coudn't care less )
Click to expand...
Click to collapse
Okay thanks ! I wasnt sure if the single format they do upon installation was enough . Ive been getting small app crashes in some ROM's ive tried , so i formated each partition at least once before flashing the ROM and it fixed it . I remember when flashing WinMo ROMs a task29 was a must on my Rhodium . But i was pretty sure wiping the partitions in CWM was indeed good enough . I just kept getting confused when each ROM's thread said YOU MUST TASK29 so i was like well now im just confused lol . I'll mark thread solved
samsamuel said:
it also wipes cache partition, the sd-ext partition on your sd card, and clears the .android folder on the fat32 part of the sd card. These last two are the reason many roms wont boot after flashing, even with a task29, since those two areas aren't touched by task29 (or your format zip presumably)
Im with Marvlesz, steer away from task29, , whats the use in removing magldr and cwm only to reflash it?
For me, a clean install would be ,,, cwm - wipe data factory reset - flash the new rom.
Only if the fresh rom doesn't boot after a few times rebooting (and performing a wipe data on the fresh rom, just like how in winmo it was recommended to do a hard reset straight after flashing) would i consider a task29.
Click to expand...
Click to collapse
Thanks again guys !
For me clean install means first do a factory/data reset. Will clean ext, and previous roms leftover folders. Then i will go to mounts in cwm. Do format every thing i got except sd.
On next boot, magldr, cwm is there. But no boot or rom. Then from magldr, i go to cwm and install the zip. I barely had done task 29 2 times in 3 mnths, just for repartition. ( though its not needed for repartition).
Sent from my HTC HD2 using xda premium
In my quest to clean my Internal SD card i did a Twrp Format Data. I once done loaded a custom rom.
Worked fine until reboot.
The phone hanhs at the Galaxy S4 boot screen. Whatever i put back, backups etc once i reboot the same story.
How can i fix this gents ??
Please help
Xetalx said:
In my quest to clean my Internal SD card i did a Twrp Format Data. I once done loaded a custom rom.
Worked fine until reboot.
The phone hanhs at the Galaxy S4 boot screen. Whatever i put back, backups etc once i reboot the same story.
How can i fix this gents ??
Please help
Click to expand...
Click to collapse
try reflashing the ROM your on
hapticxchaos said:
try reflashing the ROM your on
Click to expand...
Click to collapse
I did try a clean flash of my rom... Same thing it goes well until i reboot. Stalls on Samsug Galaxy S4 screen.
It feels like TWRP Format Data screwed up something... V 2.5.0.2
Xetalx
Try reflashing twrp.
Sent from my SGH-M919 using xda premium
hmm i would probably try restoring sans odin...should fix whatever partition issues your having
I had to restore from KIES...
Wouldnt boot again.
Go in stock recovery and
Format data / factory RESET the thing...
WTH I almost tought i lost it for a sec !!
Never format data. What you should have done is odin back to stock, then factory reset through stock recovery. Kies is hit or miss when it comes to recognizing the phone in that state. You got lucky. There are a few topics on how to fix the problem you had.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I format /data every time I flash a new ROM and I experience fewer bugs because of it.
I just back up all my important files (data folder) to external SD and then restore after I install the new ROM. Works great for me. :good:
CZ Eddie said:
I format /data every time I flash a new ROM and I experience fewer bugs because of it.
I just back up all my important files (data folder) to external SD and then restore after I install the new ROM. Works great for me. :good:
Click to expand...
Click to collapse
What do you use to format data ?
Stock ?
CMW ?
TWRP ?
Thanks
I prefer to format as well . But chances are that with the issues i got i wont do it again...
Xetalx said:
What do you use to format data ?
Stock ?
CMW ?
TWRP ?
Thanks
I prefer to format as well . But chances are that with the issues i got i wont do it again...
Click to expand...
Click to collapse
I'm mostly on TWRP but I do it in CWM also.
At most, your issue (whatever it was) was due to user-error or a random system glitch.
At worst, you have to ODIN back to stock which only takes about ten minutes to do, five minutes to re-root and install TWRP and then you're good to go again.
Don't know if any further research has been done on this subject, but it's the only thread that came back with TWRP+format.
This same thing happened to me last week, I *think* it was my first internal format on my i337, was able to boot then fail.
Odin back to stock fixed issues.
Any thought why this happens? Any suggestions for best clean format approach besides an Odin? Flash CWM/Philz for the format then back to TWRP if desired?
I'm currently stuck in the same situation. Used TWRP to format /data to try and clean up the internal sdcard and now I'm bricked. Flashed 3 diff recoveries and about a billion roms, nothing works. Downloading a fresh odin flashable stock rom as we speak.
edit: so flashing stock rom via ODIN wasnt quite enough. I then had to enter stock recovery and do a factory reset. I noticed any time I tried to format /data the system would crash and reboot. The stock recovery was able to properly format data and now I'm back on a custom recovery/rom again.
Hi everyone, yesterday i was in Omega V4 and i was happy with it, and by the night i had my phone running with all the apps, BUT suddenly the phone auto reboots and starts giving FC's in all apps.
I went to recovery to try and do a full wipe, which means:
Wipe /data, /cache, /system, /preload and dalvik cache...
And try to recover my phone flashing MJ7 latest stock rom:
N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar
Had a bootloop issue before and doing this saved me, and all i had to do was flash CWM back, and a custom rom, and that's it...
Now i have a big problem, and i mean BIG one because i don't know how to solve it.
I flashed the stock rom back and it does boot fine and work for about 2 minutes, then auto reboots and doesn't pass the Samsung logo..
Tried to redownload stock firmware, the original one
N9005XXUDMJ7_N9005OXXDMJ4_XEO
And basically i can't get the phone to work, i can't get it to boot properly and the strange thing is that it doesn't detect my SIM after booting.
BUT i have a EFS backup and did restore it thru odin so that is not the problem here, since i can't get any firmware to get stable on the phone.
Do i have to take it to the Samsung Repair Center?
I do have knox 0x1 :\
zylor said:
Hi everyone, yesterday i was in Omega V4 and i was happy with it, and by the night i had my phone running with all the apps, BUT suddenly the phone auto reboots and starts giving FC's in all apps.
I went to recovery to try and do a full wipe, which means:
Wipe /data, /cache, /system, /preload and dalvik cache...
And try to recover my phone flashing MJ7 latest stock rom:
N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar
Had a bootloop issue before and doing this saved me, and all i had to do was flash CWM back, and a custom rom, and that's it...
Now i have a big problem, and i mean BIG one because i don't know how to solve it.
I flashed the stock rom back and it does boot fine and work for about 2 minutes, then auto reboots and doesn't pass the Samsung logo..
Tried to redownload stock firmware, the original one
N9005XXUDMJ7_N9005OXXDMJ4_XEO
And basically i can't get the phone to work, i can't get it to boot properly and the strange thing is that it doesn't detect my SIM after booting.
BUT i have a EFS backup and did restore it thru odin so that is not the problem here, since i can't get any firmware to get stable on the phone.
Do i have to take it to the Samsung Repair Center?
I do have knox 0x1 :\
Click to expand...
Click to collapse
Problem you have is warranty is void as you have tripped knox
2 ways to try the easy way pull battery out for a minute that can help
Or wipe internal sd card with cwm that will wipe everything so you will have no rom at all nothing so put a rom on external sd or flash stock with odin
jaythenut said:
Problem you have is warranty is void as you have tripped knox
2 ways to try the easy way pull battery out for a minute that can help
Or wipe internal sd card with cwm that will wipe everything so you will have no rom at all nothing so put a rom on external sd or flash stock with odin
Click to expand...
Click to collapse
I can go there and pay for the repair... not a problem but wanted to avoid it lol
Trying this:
Script / Fix Brick Loop After restoring from TWRP Recovery_01.11.13
Edit: using this method solved it... efs partition corrupted!
zylor said:
I can go there and pay for the repair... not a problem but wanted to avoid it lol
Trying this:
Script / Fix Brick Loop After restoring from TWRP Recovery_01.11.13
using this method solved it... efs partition corrupted!
Click to expand...
Click to collapse
If that doesn't work flash this its like super rom lol i had a big problem with my phone and this was the only thing that fixed it http://forum.xda-developers.com/showthread.php?t=2461929
jaythenut said:
If that doesn't work flash this its like super rom lol i had a big problem with my phone and this was the only thing that fixed it http://forum.xda-developers.com/showthread.php?t=2461929
Click to expand...
Click to collapse
it did work, the problem was the efs partition that was corrupted... and already happened to me to twice... no idea why lol
Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Orangley said:
Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Click to expand...
Click to collapse
Try a full factory reset. Be careful as this will wipe your internal storage.
GDReaper said:
Try a full factory reset. Be careful as this will wipe your internal storage.
Click to expand...
Click to collapse
Thank you for your answer but I did it after flash stock rom via odin. Wiped data / factory reset , cache partition , mounted cache , system , data , wiped dalvik cache..
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
GDReaper said:
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
Click to expand...
Click to collapse
Flashing stock rom is same with factory reset i think clears everything.
I don't know. Haven't flashed stock on this device yet.
But don't most guys recommend doing a wipe before going back to stock?
I dont know i'll try that when i have free time. I did research some guys saying lollipop causing these problems. I'll try wipe before flash stock rom again , if issues keep happen i'll use lates 4.4.2 custom rom. Thank you for your answers i'll report back.
Real reset
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have the PIT file downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Thank you so much i'll try this now.
AndroidInitiate said:
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have it downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Click to expand...
Click to collapse
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Orangley said:
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Click to expand...
Click to collapse
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
AndroidInitiate said:
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
Click to expand...
Click to collapse
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Orangley said:
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Click to expand...
Click to collapse
What carrier are you using, model number of the phone, etc.
Have you backed everything up? And can you flash the custom recovery through Odin if it fails?
Try it without wiping efs first just to be safe
Look here for your device you will be able to find standalone flash able versions of twrp that should work through odin.
http://twrp.me/Devices/
Using i9500. And i did what you said and works fine thank you! Mods close thread please.
I recently updating cyanogen12 to cyanogen13. Things were running well but while running backup I ran out of memory.
Realised I want installing lots of old apps I no longer used so thought I would factory reset and start again!!! Found out the hard way that this is not the done thing.
Now my phone starts to boot into recovery and all that happens is the 'Teamwin' page just flashes on and off. Is there any way to get the phone back or have I bricked it?
Thank you for any assistance
Flash TWRP with ODIN again, see if it boots, if not, flash CM13 without wiping from TWRP and see if it boots then
Make sure you clear the caches from TWRP, might be an idea to wipe SYSTEM before flashing CM13 again too
As long as you don't wipe DATA or INTERNAL STORAGE, you're apps etc will remain