Related
Hi there, I'm having a bit of a crisis, I'll try and describe as accurately as possible:
- I decided I wanted to install a new rom, with Android 2.3 and HTC Sense 3.5
- The rom required going back to to the stock hboot, which as far as I know and can tell (I'm far from even averagely knowledgeable) turned S-ON (the hboot I've got now is 0.93.0001)
- It also required a 1024mb Ext4 partition on my SD card, which I created
- The rom got stuck in a loop at boot, so I entered recovery to try and restore my previous rom (which I had backed up both on the SD card and a copy on my hard drive)
- While there I discovered that recovery was finding an error with the Ext4 partition, and wasn't able to mount it
- I went back and reformatted my SD card to get rid of the Ext4 partition, thinking that if I was restoring to the rom I was using previously I should put the SD card back the way it was
- I transferred the hard drive backup of my previous rom onto the SD card
- When trying to restore the backup I get an error saying:
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(Invalid argument)
E:Can't mount /sdcard
Click to expand...
Click to collapse
- Googling and looking around here led me to download the Android SDK files and attempt to go through fastboot to "USB unbrick". I've tried
fastboot oem enableqxdm 0
Click to expand...
Click to collapse
Which works, and
fastboot oem eraseconfig
Click to expand...
Click to collapse
Which doesn't, presumably because the phone is S-ON
- so I go to adb to try and turn S-OFF by following the steps here: wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting, because I figure it's likely to be the same way for a Desire as it is for a Desire Z. When I try the first command ("adb push busybox /data/local/tmp/) I get back "error: device not found". This is despite fastboot commands working, and the SD card showing up on the PC if I mount it through recovery.
That's everything I think so far. I've tried a few solutions here and on various sites, but everything fails.
If anybody has any suggestions they are extremely gratefully received, whether they work or not! I'll try anything, really.
I think that if I can get the SD card to actually mount I'll be good to go; I'll be able to restore my previous rom and all should be well. But I expect I need to find a way to turn S-OFF for anything to work? Is that right? And is there any way to do that another way using adb (or getting the adb method I was trying to work) or without an sd card/an actual loading and running operating system?
Again, anything at all appreciated. I think I've included all the information I have?
Thanks!
phonicparty said:
- so I go to adb to try and turn S-OFF by following the steps here: wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting, because I figure it's likely to be the same way for a Desire as it is for a Desire Z. When I try the first command ("adb push busybox /data/local/tmp/) I get back "error: device not found". This is despite fastboot commands working, and the SD card showing up on the PC if I mount it through recovery.
That's everything I think so far. I've tried a few solutions here and on various sites, but everything fails.
Click to expand...
Click to collapse
What made you think that what works on DesireZ would work on Desire?? There's a separate section on that wiki for HTC Desire. Just sayin.
If you want root, check http://revolutionary.io
But don't go ahead and do anything yet. Your story is lacking some info. So what was your old rom, what was the new one you tried. How did you manage to change the hboot? If you weren't using stock hboot before, then you should already know the correct tools to s-off your phone. Oh and one more thing so do you have a Desire or a DesireZ??
Please post more information from hboot (start phone with pressed volume down + power button).
In my opinion the best way for you is to flash 2.3.3 RUU for a fresh rom and then use revolutionary to get S-OFF and root.
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
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?
I bought a new never used Tab 3 for the intended purpose of using it as a universal remote. I wanted to strip it down and started right away with installing custom recovery, or at least I tried. No matter what I did I was not able to get Odin to properly load TWRP. It went through all the steps but I was not able to get into recovery other than stock.
Fast forward to the next day, I finally get it to work and somewhere in this process I somehow deleted or unmounted (I really am not sure) my efs folder/partition. If I try to reset deleting all cache and wiping everything including pulling the battery for a few minutes and flashing the stock ROM again I get hung up at the "SAMSUNG' logo. I have tried several ROMs and even tried using Odin to flash a new pit file with I found HERE. When I load both the pit file and my ROM into Odin it eventually says 'FAIL'. I can flash ROMs all day with no issue.
I can only assume that the error I am getting in recovery that says E:failed to mount /efs (Invalid argument) is my issue.
Adb is not really an option for me since I have little to none, more like none at all knowledge of using it. I assume since I have flashed several tries that USB Debugging is not enabled anyway and isn't enabling it key to using ADB anyway?
I have been at this for 2 full days searching everywhere and trying everything I see. I am at a loss and hate to think this new Tab is already junk.
Any help would be greatly appreciated!
The EMCC or something like that requires replacement
andynroid said:
The EMCC or something like that requires replacement
Click to expand...
Click to collapse
So I should junk it then? I only paid $80 for this Tab.
One trial you may try to flash a Cyanogenmod based ROM see if it can write out the partitions else if no luck time to replace that item as mentioned
I have tried flashing CM and still the same issues.
I have since found out what my issue is (or at least 99% sure), I somehow wiped out my efs partition completely. So running a new pit file with Odin does nothing because the partition is gone.
This is fixable and easy for someone who knows shell, but I don't. So now I am trying to figure it out. It's a matter of pushing the 6 following files to the phone using the adb push [file] /sbin/ command using adb which I have done, now I need to figure out the rest.
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
T
you can't do that in the way you think, it requires disassembling the recovery image, making modifications and repacking then reflashing the image.
If you are using an older recovery, namely twrp, install a newer recovery , check @nels83 's thread for a "modern" twrp build.
You can also try one of my philz builds.
Being as you have been abusing Odin, you may actually have damaged your tab.
BUT if you are connecting to wifi without a problem then it's unlikely that you have damaged your efs partition. It's more likely an error with the recovery build you are using, probably in the fstab.
m
Hi there,
I'm kind of stuck right now, my HTC One M9 from Sprint, some day I turned it on, and just shows the HTC logo and reboots, I am able to use TWRP (2.8.7.0) but I can't install any zip from Stock Rom or Venom, I even tried to upgrade TWRP with different versions but nothing it always saying the E:Unable to mount '/data' or /system, /cache, etc, I can use the installer from Venom Rom and it seems to be ok, but at the end always the same with the unable to mount legend.
I can't use Download/fastboot mode, shows failure.
I am able to use adb commands from my PC but not for fastboot, just sticks with "< waiting for device >".
I tried to format those folders (data, system, etc) to FAT or eXFAT it shows succesful, but after I reboot remains in EXT4.
I don't really know how to work with this anymore, I believe that the problem is those folders?
if yes, is there a way to fix it?
if not, what can I do then?
Thank you in advance for any suggestions
=========
HTC One M9
TWRP 2.8.7.0
Unlocked
S-ON
Sprint
Those errors are usually caused by a borked twrp. If flashing this one https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk doesnt work then you'll have to flash back to stock and start over.
Beamed in by telepathy.
shivadow said:
Those errors are usually caused by a borked twrp. If flashing this one https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk doesnt work then you'll have to flash back to stock and start over.
Beamed in by telepathy.
Click to expand...
Click to collapse
I tried but shows the same (unable to mount e /data etc) could you tell me how to "flash back to stock and star over"?
Thanks @shivadow