Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,808,556 Members 42,900 Now Online
XDA Developers Android and Mobile Development Forum

Screwed Up Need Help URGENT

Tip us?
 
ckpv5
Old
(Last edited by ckpv5; 25th August 2014 at 05:34 AM.)
#21  
ckpv5's Avatar
Recognized Contributor
Thanks Meter 8,858
Posts: 6,880
Join Date: Feb 2008
Location: Kuala Lumpur

 
DONATE TO ME
Quote:
Originally Posted by Oditius View Post
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.
Again ????

Do you really read that OP has a VODAP M8 and you suggest to use AT&T RUU .. the same case as before that you suggest the same AT&T RUU for a TELUS M8

Read man ... read OP ... many many times when your fingers get itchy to write something.

Another thing I always wonder why these people with AT&T like to hang around in Int'l GSM forum instead their own AT&T forum here : http://forum.xda-developers.com/att-htc-one-m8

You guys can help those needy in AT&T ... don't create confusion to the newbies on Intl GSM forum ... please
Unless you're a noob yourself then I have nothing else to say
The Following 4 Users Say Thank You to ckpv5 For This Useful Post: [ Click to Expand ]
 
jarrodli2
Old
#22  
jarrodli2's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 13
Join Date: Aug 2014
Location: Sydney
Quote:
Originally Posted by Mr Hofs View Post
No you need to PM the guy with the mkfs file and fix that first.
Gawsh i'm lost, i've done everything right but when it comes to the mount /data the console says

mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
On an external website it says;

How Do I Recognise The Problem?

When trying to mount the DATA partition from inside the custom recovery using the mount /data command you will most likely see this output: mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument

To be 100% sure you can check filesystem structure with the following command: /sbin/e2fsck -n -f /dev/block/mmcblk0p37

When I type /sbin/e2fsck -n -f /dev/block/mmcblk0p37 it comes up with;

~ # /sbin/e2fsck -n -f /dev/block/mmcblk0p37
/sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p37: 11/6400 files (9.1% non-contiguous), 1233/6400 blocks

Does this make any sense?
 
jarrodli2
Old
#23  
jarrodli2's Avatar
Junior Member - OP
Thanks Meter 3
Posts: 13
Join Date: Aug 2014
Location: Sydney
FINALLY Fixed my phone (took me long enough), but to no avail I downloaded the latest snapshot of cm11 which i think ill change to viperone (soz cm11). Many thanks to those who helped me and a BIG thank you to Mr Hofs for being there in times of agony and pain. I'm soon going to post a thread to how to solve fixing your m8 after wiping the system . This Thread Is Now Closed!
The Following 2 Users Say Thank You to jarrodli2 For This Useful Post: [ Click to Expand ]
 
One-M8-Master
Old
#24  
One-M8-Master's Avatar
Senior Member
Thanks Meter 2,407
Posts: 6,889
Join Date: May 2012
Location: Hannover
Normally the system wipe doesn't do anything bad...it could be that twrp doesn't mount it right and the wiping process will be somehow corrupted..
Its simple read before asking and use the search button and always be thankful its FREE!!!

Devices : HTC HD2 (Sold/broken), HTC One X (has my sister now), HTC One M8 (current) (changing roms always after few weeks of use and testing)
 
Mr Hofs
Old
#25  
Mr Hofs's Avatar
Recognized Contributor / Themer
Thanks Meter 8,438
Posts: 13,852
Join Date: Sep 2011

 
DONATE TO ME
Thanks for the kind words ! Very glad you got it solved.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes