Original thread
For over a month, I ran SinLessROM flawlessly on my Verizon HTC One (M8). Last week, I woke up with a slow and laggy phone which abruptly shut down after a few seconds of bizarre behavior. Since that time, I have not been able to boot the device past the initial ROM splash screen. I am running TWRP 2.7.1.0 and I am still able to boot into the recovery partition. However, once I am in TWRP, I cannot mount '/data' and the internal storage displays a capacity of 0 MB. Furthermore, no matter what I try, I am unable to modify anything in the phone's memory contents. Write operations such as a reformat are reported to be successful, but upon inspection of the phone's memory, nothing is actually changed. I suspect this to be a NAND failure. Below is a list of everything I've tried so far:
Rebooted countless times
Allowed phone to idle in recovery for prolonged periods of time
TWRP - Erased cache+dalvik; flashed ROM via USB-OTG
TWRP - Erased cache+dalvik; flashed ROM via ADB sideload
TWRP - Erased cache, dalvik system, and data; flashed ROM via USB-OTG
Erased cache via fastboot; re-flashed ROM via USB-OTG in TWRP
Fastboot - Erased cache and re-flashed TWRP
Fastboot - Erased cache and flashed philz touch (did not change recovery partition; still boots to TWRP)
Fastboot - Attempted to boot to RUU (resulted in boot loop)
Hboot - Flashed stock RUU per instructions found in this thread (option 2)
TWRP - File system repair
TWRP - Fix permissions
TWRP - Format data
TWRP - Factory reset
TWRP - Locked + unlocked bootloader per instructions found in this thread (with reboot in between)
Fastboot - Changed from Verizon CID to SuperCID (command executed successfully, but CID was unchanged)
When I attempted to change the bootloader flag in memory via the dd command, everything executed without error. However, I decided to use the dd command again to read from that same address and the value was unchanged. Since that point, I've been pretty much convinced that this has to be a memory hardware issue. I would love to be proven wrong and if anyone has any advice or input, I would be greatly appreciative to hear it. Thanks in advance.
Ok are you currently s-on or s-off?
also what are the stats on your boot screen? OS? Hboot version so on.
Hmm. Writing up a list of what you tried is very helpful, kudos to that. I had the whole "unable to mount /data, /internal storage the other day in twrp, and tried a plethora of " solutions". The only one for me that worked was twrp > wipe > format data.
I see you have not tried the RUU why not give that a go? Vzw doesn't have a full RUU available but the one we have in vzw android dev is more than enough for most people
If that fails why don't you try formatting the phone in windows device manager? (Someone from these forums reported that this fixed their unable to mount data options although I can't guarantee the results.)
agentbardall said:
Ok are you currently s-on or s-off?
also what are the stats on your boot screen? OS? Hboot version so on.
Click to expand...
Click to collapse
I'm S-off.
Here' what Hboot says:
Code:
*** UNLOCKED ***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 1 2014,00:26:53.197
wtoj34 said:
Hmm. Writing up a list of what you tried is very helpful, kudos to that. I had the whole "unable to mount /data, /internal storage the other day in twrp, and tried a plethora of " solutions". The only one for me that worked was twrp > wipe > format data.
I see you have not tried the RUU why not give that a go? Vzw doesn't have a full RUU available but the one we have in vzw android dev is more than enough for most people
If that fails why don't you try formatting the phone in windows device manager? (Someone from these forums reported that this fixed their unable to mount data options although I can't guarantee the results.)
Click to expand...
Click to collapse
I actually did try the RUU several times. It's listed in the first post. It didn't change anything on my system. I did try to format the phone through windows, but unfortunately it doesn't show up in my disk management.
ok as ur Verizon my knowledge is very limited as I am GSM but i had problems with RUU until i tried this method
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
i know it says GSM but im sure i read in the comments people have done it with Verizon too as long as you have the right firmware
Internal memory mount/write issues seem to be a recurring problem on TWRP (but not for everyone). You can also try CWM, as I've seen some folks solve this issue by flashing CWM recovery.
agentbardall said:
ok as ur Verizon my knowledge is very limited as I am GSM but i had problems with RUU until i tried this method
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
i know it says GSM but im sure i read in the comments people have done it with Verizon too as long as you have the right firmware
Click to expand...
Click to collapse
I will try this and report back soon.
redpoint73 said:
Internal memory mount/write issues seem to be a recurring problem on TWRP (but not for everyone). You can also try CWM, as I've seen some folks solve this issue by flashing CWM recovery.
Click to expand...
Click to collapse
I already tried flashing an alternate recovery (philz touch which is based on CWM). It flashed successfully via fastboot, but it had no effect on my recovery partition. I'm still stuck with TWRP.
i thought ud have better luck this way as it only involves the External SD not the internal your having issues with
agentbardall said:
i thought ud have better luck this way as it only involves the External SD not the internal your having issues with
Click to expand...
Click to collapse
Thanks. Appreciate the help. I just flashed the firmware twice. Then in TWRP I ran 'format data' and wiped the cache, dalvik, system, and data partitions (the wipe failed). Finally, I re-flashed the ROM via USB-OTG and rebooted. Unfortunately, I'm still having the exact same issues.
Does anyone know how I can confirm this to be a NAND failure?
I'm leaning toward shipping this back to HTC. Is there anyone out there who can help me confirm this is a NAND failure?
Related
Hi Folks,
i am a noob and have just started picking up the tricks of the trade.i have an unbranded htc desire. Was using the HiAPk rom till now. Then thought of flashing the INsertcoin 1.1.2. Created EXT4 for the same and recopied all data to my sdcard. Now when i try to flash any rom it just gets caught at the boot screen. Hi dont have a recovery image. But i do have a nandroid backup. Restoring the backup is not helping as well. The phone is s-off,rooted with clockword recovery 2.5.0.7. i do have access to recovery but, whatever i do, the phone gets stuck at the boot screen. Please assist. I guess this occured when i accidentally selected/deselected hboot/fastboot option? can that be a potential cause?
Try and go into recovery then wiping Data/Cache, then go to advanced -> wipe dalvik cache and reboot. If it doesnt work, reflash the rom and do the above steps again and reboot. See if it works
EddieN said:
Try and go into recovery then wiping Data/Cache, then go to advanced -> wipe dalvik cache and reboot. If it doesnt work, reflash the rom and do the above steps again and reboot. See if it works
Click to expand...
Click to collapse
Tried doing the above steps but still caught at the boot screen whenever i reboot. Though the rom got installed but, on rebooting the same boot screen staring at me
What version recovery do you have? Try updating it, although remember that having a nandroid backup from an older recovery wont restore if you are on a newer recovery. So maybe it isn't a good idea to update your recovery if you only have a nandroid from an older recovery.
BEFORE READING ON: What partitions are you using? It could be that the new ROM you want to flash doesn't fit in the current partitions you have flashed. Stock? CM7r2? Oxygen?
----------------------------------------------------------------------------
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/showthread.php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
If it doesn't work, I think it will be that you are trying to install a ROM which supports a different partition table than what you have flashed, which is causing the bootloops because of the lack of space on the partitions needed.
Good luck
EddieN said:
What version recovery do you have? Try updating it, although remember that having a nandroid backup from an older recovery wont restore if you are on a newer recovery. So maybe it isn't a good idea to update your recovery if you only have a nandroid from an older recovery.
BEFORE READING ON: What partitions are you using? It could be that the new ROM you want to flash doesn't fit in the current partitions you have flashed. Stock? CM7r2? Oxygen?
----------------------------------------------------------------------------
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/showthread.php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
If it doesn't work, I think it will be that you are trying to install a ROM which supports a different partition table than what you have flashed, which is causing the bootloops because of the lack of space on the partitions needed.
Good luck
Click to expand...
Click to collapse
Hi, was using a HiApk ROM till now which needs no partitions at all. Also i agree that it might be the case that the new rom which i want to flash is not supporting the partitions(no reasons why HiAPK shouldnt run coz had been running it without partitions for the past 2months). Before going ahead ,do u think i should i re-format my sdcard to FAT32 and delete the partitions..Just in case this doesnt work out i go ahead with the fastboot commaHer. Whatever you suggest is what i am going to do. Thanks.
Getshivang89 said:
Hi, was using a HiApk ROM till now which needs no partitions at all. Also i agree that it might be the case that the new rom which i want to flash is not supporting the partitions(no reasons why HiAPK shouldnt run coz had been running it without partitions for the past 2months). Before going ahead ,do u think i should i re-format my sdcard to FAT32 and delete the partitions..Just in case this doesnt work out i go ahead with the fastboot commaHer. Whatever you suggest is what i am going to do. Thanks.
Click to expand...
Click to collapse
Also the new ROM that i was trying to flash requires a 1gb ext2/3/4. So i did a 1 gb Ext4 partition. This one is the stable insertcoin 1.1.2
Getshivang89 said:
Hi, was using a HiApk ROM till now which needs no partitions at all. Also i agree that it might be the case that the new rom which i want to flash is not supporting the partitions(no reasons why HiAPK shouldnt run coz had been running it without partitions for the past 2months). Before going ahead ,do u think i should i re-format my sdcard to FAT32 and delete the partitions..Just in case this doesnt work out i go ahead with the fastboot commaHer. Whatever you suggest is what i am going to do. Thanks.
Click to expand...
Click to collapse
EDIT: Forgot to mention that in order to use Fastboot Commander you'll need the ADB drivers. Just install HTC Sync to get the drivers for it!
Since you say in the beginning that you are S-Off and have Recovery 2.5.0.7, the only things I can think of that you haven't done are this:
1. Insertcoin 1.1.2 (http://forum.xda-developers.com/showthread.php?t=1016940&highlight=insertcoin) says you need to be S-off (which you are), and have the latest recovery (5.0.1.0). So my first piece of advice would be to update your recovery to 5.0.1.0 from what you have now (2.5.0.7) but remember what I said about nandroid backups and recovery earlier on!!
2. Make sure you have a 1GB Ext2, Ext 3 or Ext4 partition on your SD-card. The way to partition your SD-card is here: http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3
Insertcoin says it should work on the stock HBOOT which I'm assuming you have since you said you've never flashed another partition table on your phone.
So basically, update your recovery (best done with Fastboot Commander imo) and make sure the md5 sums match up. Once you've updated your recovery, make sure your SD card is ready, then wipe everything in recovery and reflash the rom, and wipe everything in recovery again before rebooting.
Again, remember that since you made your nandroid backup in CWM 2.5.0.7, it wont be able to restore in CWM 5.0.1.0 so basically once you update your recovery your nandroid from 2.5.0.7 will be useless.
EddieN said:
EDIT: Forgot to mention that in order to use Fastboot Commander you'll need the ADB drivers. Just install HTC Sync to get the drivers for it!
Since you say in the beginning that you are S-Off and have Recovery 2.5.0.7, the only things I can think of that you haven't done are this:
1. Insertcoin 1.1.2 (http://forum.xda-developers.com/showthread.php?t=1016940&highlight=insertcoin) says you need to be S-off (which you are), and have the latest recovery (5.0.1.0). So my first piece of advice would be to update your recovery to 5.0.1.0 from what you have now (2.5.0.7) but remember what I said about nandroid backups and recovery earlier on!!
2. Make sure you have a 1GB Ext2, Ext 3 or Ext4 partition on your SD-card. The way to partition your SD-card is here: http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3
Insertcoin says it should work on the stock HBOOT which I'm assuming you have since you said you've never flashed another partition table on your phone.
So basically, update your recovery (best done with Fastboot Commander imo) and make sure the md5 sums match up. Once you've updated your recovery, make sure your SD card is ready, then wipe everything in recovery and reflash the rom, and wipe everything in recovery again before rebooting.
Again, remember that since you made your nandroid backup in CWM 2.5.0.7, it wont be able to restore in CWM 5.0.1.0 so basically once you update your recovery your nandroid from 2.5.0.7 will be useless.
Click to expand...
Click to collapse
Logs as asked:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.1002.
Radio version: 5.11.05.27.
Main software version: 2.29.405.5.
cid: htc__001.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
-----------------------------------.
STARTING ERASE OF PARTITION(S).
Erasing partition "boot" - PLEASE WAIT.
boot erased SUCCESSFULLY.
Erasing partition "system" - PLEASE WAIT.
system erased SUCCESSFULLY.
Erasing partition "cache" - PLEASE WAIT.
cache erased SUCCESSFULLY.
FINISHED ERASING PARTITION(S).
Getshivang89 said:
Logs as asked:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.1002.
Radio version: 5.11.05.27.
Main software version: 2.29.405.5.
cid: htc__001.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
-----------------------------------.
STARTING ERASE OF PARTITION(S).
Erasing partition "boot" - PLEASE WAIT.
boot erased SUCCESSFULLY.
Erasing partition "system" - PLEASE WAIT.
system erased SUCCESSFULLY.
Erasing partition "cache" - PLEASE WAIT.
cache erased SUCCESSFULLY.
FINISHED ERASING PARTITION(S).
Click to expand...
Click to collapse
Hey Eddie N,
Just one thing. Now just to get back to the ROM i was running till now, should i just flash HiAPK now after doing all those steps as u suggested? Once i get through with this i can go ahead to flash insertcoin. But , first priority now is to just run the phone out of the boot screen in HiAPK(as it requires no partitioning/no recovery issues).. Thanks for the invaluable help. I am gonna keep u posted
I'd do this now:
Nandroid back to your HiAPK, then get RomManager and in Rom Manager update your CWM from 2.5.0.7 to 5.0.1.0 (the EASIEST way). Do a nandroid backup right away through rom manager after installing the new recovery so you can always go back if something goes wrong!! Reboot to recovery and reflash insertcoin.
After doing that you should have what's needed to run insertcoin (S-Off, latest recovery, Stock hboot, 1gb ext2/3/4). Before you didn't have latest recovery and you changed SD-card but i assume you fixed your SD-card now
If nandroiding back doesn't work, reflash it from scratch. If THAT doesn't work I'm not quite sure how to help you further I'm new myself but managed to fix my bootloop last night with the method i gave you
EddieN said:
I'd do this now:
Nandroid back to your HiAPK, then get RomManager and in Rom Manager update your CWM from 2.5.0.7 to 5.0.1.0 (the EASIEST way). Do a nandroid backup right away through rom manager after installing the new recovery so you can always go back if something goes wrong!! Reboot to recovery and reflash insertcoin.
After doing that you should have what's needed to run insertcoin (S-Off, latest recovery, Stock hboot 130mb system, 1gb ext2/3/4). Before you didn't have latest recovery and you changed SD-card but i assume you fixed your SD-card now
Click to expand...
Click to collapse
You are the man!!!yes i changed my sd card now. MAybe my sd card has gone bad. No wonder i couldnt flash any rom..Now back to HiAPK. I am gonna setup my sdcard again using gparted. Dont rely think the partitioning tool i was using till now was wrking(perhaps damaged my sd card) Thanx a lot mate
Just checked.. The phone was loading up even without the sd card(the one suspected of having gone kaput). But, now when restart the phone with that sd card it gets stuck at the boot screen. Any reason why this can be happening?
Seriously.. there should be sticky saying that stuck at htc screen, or bootloop is not a brick.
Hi guy`s looking for some help with and HTC Desire that is stuck on the TMobile UK load screen.
I have tried a few methods to try and get it back to life but without success.
I originally used the Gingerbeard release from HTC to upgrade the phone but after finding it left me with almost no memory to download apps etc I decided to revert back to stock rom RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4.05.00.11_release_122755
After completing this , my phone now turns on and sticks on a screen with a small pink circle.
Before loading the stock rom I gained s-off and created a Naand back up using Unrevocked as I was having issues with the RUU above.
From what I have been reading I have a PVT4 device and the clockworkmod is unsutaible.
I have now downgraded the bootlaoder to AlphaRev Unlock and loaded Recovery-RA-desire-v2.0.0 but when I click onto recovery my phone still just go`s to the pink circle screen again.
When booted into HBOOT the screen shows..
AlphaRev Unlock
Bravo PVT4 SHIP S-OFF
HBOOT 6.93.9999
MICROP 051d
TOUCH PANEL-SYNT0101
RADIO 4.05.00.11
aUG 10 2010 17.52.18
HBOOT
Parsing....[SD.ZIP]
[1] BOOTLOADER
Do you want to start update?
YES
NO.
Could some kind sole please advise me where I am going wrong. If needed I can list what is on my SD card etc etc.
Thanks very much if you can help me. I am a bit stuck with this one and having to revert back to my HTC Hero is a bit of a pain in the hole.
my guide, advanced boot problems S-OFF. I didn't think it'd be that hard to find..
bortak said:
my guide, advanced boot problems S-OFF. I didn't think it'd be that hard to find..
Click to expand...
Click to collapse
it was very easy to find m8 and helped me downgrade the bootloader. My device is PVT4 which in the guide it says to stick to "Flashing Custom Recovery". Unfortunately I am having problems getting Android Flasher to run on my pc. I will try on my netbook later.
At present I can boot into fastboot but when I chose recovery to try and flash Amon Ra`s recovery image I just return to to pink circle logo.
I must admit I am getting a bit mixed up as to what stage I am currently at as I have tried a few different methods from your troubleshoot guide.
Thanks for your help, I will continue to read up on the subject over the next few days and hopefully be able to get my handset back to life.
Ned_Stevens said:
it was very easy to find m8 and helped me downgrade the bootloader. My device is PVT4 which in the guide it says to stick to "Flashing Custom Recovery". Unfortunately I am having problems getting Android Flasher to run on my pc. I will try on my netbook later.
At present I can boot into fastboot but when I chose recovery to try and flash Amon Ra`s recovery image I just return to to pink circle logo.
I must admit I am getting a bit mixed up as to what stage I am currently at as I have tried a few different methods from your troubleshoot guide.
Thanks for your help, I will continue to read up on the subject over the next few days and hopefully be able to get my handset back to life.
Click to expand...
Click to collapse
if android flasher doesn't work try fastboot commander.. you need android SDK set up though, its not that hard, just look at resources its there
bortak said:
if android flasher doesn't work try fastboot commander.. you need android SDK set up though, its not that hard, just look at resources its there
Click to expand...
Click to collapse
Hi Bortak, took things back step or two and I have now managed to gain access to recovery using Fastboot Commander.
I have flashed update-cm-7.10-Desire-signed.zip everything seemed ok then when I rebooted the phone I went straight back to the pink circle screen. I accessed the recovery twice through fast commander without any problems now it`s not letting me get into recovery again lol Oh Well back to the drawing board.
Thanks again for your help
bortak said:
if android flasher doesn't work try fastboot commander.. you need android SDK set up though, its not that hard, just look at resources its there
Click to expand...
Click to collapse
Hi mate sorry for bothering you but I have managed to get back into recovery, could you give me a couple of pointers as to what to do next. I am able to get access through fastboot commander and recovery image RA-Desire-v2.0.0 but as I say any time I try to load the rom I mentioned above it go`s through the update process then dumps me back to the pink circle screen.
I am obviously missing something that I cannot quite put my finger on. I am normally quite good with things like this as I used to be able to flash images etc on to Linux D-Box`s but this really has me stumped.
I am going to try a few different roms but something is telling me that I need to go back to a stock rom, would this be correct?
Thanks again and sorry for being a total pain.
Ned_Stevens said:
Hi mate sorry for bothering you but I have managed to get back into recovery, could you give me a couple of pointers as to what to do next. I am able to get access through fastboot commander and recovery image RA-Desire-v2.0.0 but as I say any time I try to load the rom I mentioned above it go`s through the update process then dumps me back to the pink circle screen.
I am obviously missing something that I cannot quite put my finger on. I am normally quite good with things like this as I used to be able to flash images etc on to Linux D-Box`s but this really has me stumped.
I am going to try a few different roms but something is telling me that I need to go back to a stock rom, would this be correct?
Thanks again and sorry for being a total pain.
Click to expand...
Click to collapse
Did you do a full wipe before you flashed?
Full wipe:
/mounts & storage
> format boot
> format cache
> format system
> format data
> format sd-ext
Also, since you're S-OFF, make sure you have the correct SPL/hboot... Cyanogen Will run on everything BUT Oxygen hboot.
bortak said:
Did you do a full wipe before you flashed?
Full wipe:
/mounts & storage
> format boot
> format cache
> format system
> format data
> format sd-ext
Also, since you're S-OFF, make sure you have the correct SPL/hboot... Cyanogen Will run on everything BUT Oxygen hboot.
Click to expand...
Click to collapse
Hi mate, at present my handset is sitting in the Android System Recovery , My options are..
Reboot System Now
USB-MS toggle
Back Up/Restore
Flash zip from sdcard
Wipe
Partition sdcard
Mounts
Other
Power Off
I dont have the option for mounts & storage. If I go into mounts I have this list...
Mount /storage
Unmount Cache
Mount /data
Mount /sd-ext
Mount /sdcard
If I use the Wipe option I get an option to....
Wipe All Userdata
Wipe only /data
Wipe only /sd-ext
Wipe only /sdcard/ .android secure
Wipe only /cache
Wipe only Dalvik-cache
Wipe only battery stats
Wipe only rotate settings.
I have no option to format anything just the Wipe all userdata which is the closest thing to what I am looking to do. Would this be correct ?
Thanks again m8 I really appreciate your help.
Ned_Stevens said:
Hi mate, at present my handset is sitting in the Android System Recovery , My options are..
Reboot System Now
USB-MS toggle
Back Up/Restore
Flash zip from sdcard
Wipe
Partition sdcard
Mounts
Other
Power Off
I dont have the option for mounts & storage. If I go into mounts I have this list...
Mount /storage
Unmount Cache
Mount /data
Mount /sd-ext
Mount /sdcard
If I use the Wipe option I get an option to....
Wipe All Userdata
Wipe only /data
Wipe only /sd-ext
Wipe only /sdcard/ .android secure
Wipe only /cache
Wipe only Dalvik-cache
Wipe only battery stats
Wipe only rotate settings.
I have no option to format anything just the Wipe all userdata which is the closest thing to what I am looking to do. Would this be correct ?
Thanks again m8 I really appreciate your help.
Click to expand...
Click to collapse
oh right you dont have clockworkmod..
okay here's an idea. Download this then flash it in recovery like you would any ROM..
or this with fastboot
then follow the instructions I wrote before.
bortak said:
oh right you dont have clockworkmod..
okay here's an idea. Download this then flash it in recovery like you would any ROM..
or this with fastboot
then follow the instructions I wrote before.
Click to expand...
Click to collapse
Success I done the wipe all user data , used LeeDroid 2.5 final and everything has worked well.
Thanks again m8, I couldnt have done any off this without you Tutorial or help. Your a top man.
no prob. That's why I prefer using Clock in contrary to Amon RA - the formatting options, sometimes you just can't do without them (without using fastboot)
So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
nodnarb said:
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
Click to expand...
Click to collapse
Try this, reformat your sdcard fat32 with a pc. Then place only this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on the sd in no folders (Do not rename). Boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. I think your issue with the ruu before was that you were trying to flash an older version than you already have installed. If that dosent work try fastboot flashing cwm again, and see if it can mount the sd then.
Thread moved. Please post all questions here in the correct section of the forum.
Thanks
AvRS
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
shivaagarwal1 said:
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
You'll probably get better help in the Incredible S section. This is for just the plain olé Incredible.
Completed the following successfully on my Wildfire S 510c:
Unlocked
Installed CWM v5.0.2.6
Rooted
I wanted to find a way to either move the whole system to the SD card or to increase the Internal memory using the SD card.
I found a guide here explaining how to increase the internal memory using SD card, but after following the instructions to the T my phone hangs up on the white screen with HTC logo every time.
To make matters worse, the partitioned portion of the SD card cannot be seen in windows explorer when I try to access the SD via CWM, only the portion that was left over. I fear that since this problem occurred right after I installed cm-7-20120717-UNOFFICIAL-marvel recovery over the previous CWM I had and the Data2SDInstallerNXE2 I'm speculating 1 of 2 things have occurred: Either the Unofficial CWM is corrupted (All functions work properly inside recovery) or an error occurred where the system files were not properly copied into the newly created partition and so it tries to boot system from empty space.
I'm at a total loss where to go from here. I don't know of any free programs that can see all the partitions of the SD card where Windows cannot, let alone unpartition it, and even then how to set it back up to where it boots up where it needs to. I've tried to reinstall the previous CWM I had via zip installer but it give an "Installation Aborted".
Someone plz halp! lol
Ok, I found that under SD partition in CWM if you select different partition size it will remove the old partition, this still doesn't fix the hangup though.
Now it doesn't hang up, but keeps going back to bootloader screen. I think I should stop before it get worse and wait for a response. XD
Tried flashy method in an attempt to set phone back to locked and unrooted status. Only thing it did was set phone in relocked status. I'm taking a break for awhile, spent too many hours on this ><
LyleVertigo said:
Completed the following successfully on my Wildfire S 510c:
Unlocked
Installed CWM v5.0.2.6
Rooted
I wanted to find a way to either move the whole system to the SD card or to increase the Internal memory using the SD card.
I found a guide here explaining how to increase the internal memory using SD card, but after following the instructions to the T my phone hangs up on the white screen with HTC logo every time.
To make matters worse, the partitioned portion of the SD card cannot be seen in windows explorer when I try to access the SD via CWM, only the portion that was left over. I fear that since this problem occurred right after I installed cm-7-20120717-UNOFFICIAL-marvel recovery over the previous CWM I had and the Data2SDInstallerNXE2 I'm speculating 1 of 2 things have occurred: Either the Unofficial CWM is corrupted (All functions work properly inside recovery) or an error occurred where the system files were not properly copied into the newly created partition and so it tries to boot system from empty space.
I'm at a total loss where to go from here. I don't know of any free programs that can see all the partitions of the SD card where Windows cannot, let alone unpartition it, and even then how to set it back up to where it boots up where it needs to. I've tried to reinstall the previous CWM I had via zip installer but it give an "Installation Aborted".
Someone plz halp! lol
Ok, I found that under SD partition in CWM if you select different partition size it will remove the old partition, this still doesn't fix the hangup though.
Now it doesn't hang up, but keeps going back to bootloader screen. I think I should stop before it get worse and wait for a response. XD
Tried flashy method in an attempt to set phone back to locked and unrooted status. Only thing it did was set phone in relocked status. I'm taking a break for awhile, spent too many hours on this ><
Click to expand...
Click to collapse
Instead of the Data2sd provided in the tutorial, try using INT2EXTV2+(You can easily find it using the search function).....Do remember to flash it after the flashed rom has booted once
Also, you can not see the second partition of the SDCard on Windows...........Windows doesn't support it(EXT partitions)
csoulr666 said:
Instead of the Data2sd provided in the tutorial, try using INT2EXTV2+(You can easily find it using the search function).....Do remember to flash it after the flashed rom has booted once
Also, you can not see the second partition of the SDCard on Windows...........Windows doesn't support it(EXT partitions)
Click to expand...
Click to collapse
Ok, so as the current state of the phone, do I just wipe everything and then run CWM, reboot it then when it comes up again install Int2extv2+ from zip, that's it? Does the relock prevent me from taking the steps neccessary from getting back into the phone? and if so what would I need to do to unlock it again when I only have access to fastboot/bootloader/CWM?
LyleVertigo said:
Ok, so as the current state of the phone, do I just wipe everything and then run CWM, reboot it then when it comes up again install Int2extv2+ from zip, that's it? Does the relock prevent me from taking the steps neccessary from getting back into the phone? and if so what would I need to do to unlock it again when I only have access to fastboot/bootloader/CWM?
Click to expand...
Click to collapse
Unlock the Bootloader, get into CWM, wipe, flash the rom of your choosing, let it boot once, then go back to CWM and flash INT2EXTV2+
csoulr666 said:
Unlock the Bootloader, get into CWM, wipe, flash the rom of your choosing, let it boot once, then go back to CWM and flash INT2EXTV2+
Click to expand...
Click to collapse
Ok, so here is what I've done:
Re-unlocked √
Wipe date/Factory Reset √
Wipe Cache Partition √
Flashed cm-10.1-20130703-4.3-F-NIGHTLY-marvel √
Reboot System Now (Hangs on HTC white screen) - pulled battery out to turn off
Went back into bootloader -> CWM and installed INT2EXTV2+ via zip installer (selected no for SWAP2INT) √
Reboot - Hangs on HTC white screen. X
Here is a question, would S-ON affect this in any way? I've done the partial S-off procedure (which was recommended to me) but the bootloader still says S-On. If it needs to be completely off and shown as S-off would you show me a proper procedure link for me get that taken care of (but only if absolutely necessary)?
I really appreciate your help so far.
LyleVertigo said:
Ok, so here is what I've done:
Re-unlocked √
Wipe date/Factory Reset √
Wipe Cache Partition √
Flashed cm-10.1-20130703-4.3-F-NIGHTLY-marvel √
Reboot System Now (Hangs on HTC white screen) - pulled battery out to turn off
Went back into bootloader -> CWM and installed INT2EXTV2+ via zip installer (selected no for SWAP2INT) √
Reboot - Hangs on HTC white screen. X
Here is a question, would S-ON affect this in any way? I've done the partial S-off procedure (which was recommended to me) but the bootloader still says S-On. If it needs to be completely off and shown as S-off would you show me a proper procedure link for me get that taken care of (but only if absolutely necessary)?
I really appreciate your help so far.
Click to expand...
Click to collapse
Is there a chance you have a 2012 model of the WFS??? If so, see if the rom is compatible with the 2012 WFS.......some roms, like the OWL project(CM10.1) is compatible
csoulr666 said:
Is there a chance you have a 2012 model of the WFS??? If so, see if the rom is compatible with the 2012 WFS.......some roms, like the OWL project(CM10.1) is compatible
Click to expand...
Click to collapse
No go, Owl project roms are for GSM only. Mine does not have SIM card.
LyleVertigo said:
No go, Owl project roms are for GSM only. Mine does not have SIM card.
Click to expand...
Click to collapse
Why didn't you tell that before!! Look for roms with "marvelc" in them........ That's why it doesn't go past the HTC screen
csoulr666 said:
Why didn't you tell that before!! Look for roms with "marvelc" in them........ That's why it doesn't go past the HTC screen
Click to expand...
Click to collapse
The only one I was able to find that specifically called for CDMA that had a working dl link so far is cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip .
I tried to flash it but got this:
Installing update...
assert failed: getprop("ro.produ
ct.device") == "marvelc" || getp
rop("ro.build.product") == "marv
elc"
E:Error in /sdcard/cm-9.1.0-CRYP
TOMILK-ALPHA9-marvelc.zip
(Status 7)
Installation Aborted.
I did all the clearing and formatting required prior.
LyleVertigo said:
The only one I was able to find that specifically called for CDMA that had a working dl link so far is cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip .
I tried to flash it but got this:
Installing update...
assert failed: getprop("ro.produ
ct.device") == "marvelc" || getp
rop("ro.build.product") == "marv
elc"
E:Error in /sdcard/cm-9.1.0-CRYP
TOMILK-ALPHA9-marvelc.zip
(Status 7)
Installation Aborted.
I did all the clearing and formatting required prior.
Click to expand...
Click to collapse
Look for the ones with CDMA written in the thread, here are some CDMA roms I found
http://forum.xda-developers.com/showthread.php?t=2245617
http://forum.xda-developers.com/showthread.php?t=1861623
http://forum.xda-developers.com/showthread.php?t=2274173
Click to expand...
Click to collapse
csoulr666 said:
Look for the ones with CDMA written in the thread, here are some CDMA roms I found
Click to expand...
Click to collapse
I tried all those roms and same error, which leads me to believe that the rom isn't the problem.
However, all of that is irrelevant now, as I gave it to someone who said they knew how to fix it and they bricked it completely, so I just told him to keep it. lol
LyleVertigo said:
I tried all those roms and same error, which leads me to believe that the rom isn't the problem.
However, all of that is irrelevant now, as I gave it to someone who said they knew how to fix it and they bricked it completely, so I just told him to keep it. lol
Click to expand...
Click to collapse
U have marvelc no marvel mobile
Try with fastboot flash custom rom (boot.img,system.img, and recovery.img)
But dont forgot before factory reset.
U will have custom rom mobile, and worked mobile
If u can change rom, u must find marvelc roms, and first try cm7 rom
I too start with this rom (cm7)