Develop Bugs

[Q] Completely wiped my One X, cannot mount usb, no backups, need backups

Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(

Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"

Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before

Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA

Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?

Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly

This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:

Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3

Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%

ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....

Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.

ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?

Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)

ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??

Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?

i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man

I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app

Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App

You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.

You could also take this opportunity to install a custom Rom, with which I can also help.

[Q] HTC One V Recovery doesn't work, Phone Stuck

Hi Y'all, sometime lurker, first time poster.
I got an HTC One V (CDMA, Virgin Mobile) today and given the relative ease of rooting my old Droid Inc I thought it would be a breeze to do this phone as well, but I did not do enough research and messed it up. Here is what I did as best as I can recall:
I unlocked the bootloader without a problem using Fastboot.
Then I flashed CWM recovery through hasoon2000's all in one tool, but it didn't work. I believe I did not flash the correct CWM (CDMA). I tried reflashing stock recovery, and then CDMA CWM recovery, but I couldn't get past the white HTC with the red warning message.
Because I couldn't get recovery to work, I thought maybe I should flash the kernel. I was using hasoon2000's all in one tool, but I did not realize that it would try to boot into recovery in the middle of flashing the kernel (yeah, I'm a noob and an idiot).
So now it won't load into the standard ROM anymore, it just gets stuck on the HTC White screen with the Red Warning. I can get it to load the bootloader, and I tried flashing the kernel from the all in one tool through fastboot, but it didn't work.
Is there any way I can save my phone or am I out of luck?
Thanks for any help you can provide.

Get the stock boot.img and put it in your fast boot folder and go to cmd prompt and type
C:\fastboot
Fast boot flash boot boot.IMG
Make sure your in fastboot
Sent from my One V using xda app-developers app

Thanks XxlemonxX. I did that a few times and it didn't seem to stick.
But! While I was fastloading I went ahead and did the Superboot step found here:
http://forum.xda-developers.com/showthread.php?t=1598964
And the phone restarted! Huzzah! Now I just have to see if I can get a recovery actually working...

OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?

jimmymcsnakes said:
OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?
Click to expand...
Click to collapse
That is an old cwm. thats how it operates. Once your booted into the system you can install rom manager from play store and then you can update cwm so you wont have to enable the power button for use. But anyway seems you cant boot into a stable system right now. So If you are willing to follow theses instructions you can get back to factory conditions.
1. get the fastboot package if you dont have it. http://www.mediafire.com/?4dx982z93w8z7wk and put those files in a folder in the C drive.
2. Get the ruu from here its the top one if you are virgin mobile US. http://www.filefactory.com/f/0eafb9c43276c308/ look for RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
3. This is how your going to get the stock recovery and stock kernel. run the ruu but dont do anything with it just yet. After the ruu is opened and is at the welcome screen just click and drag the window down out of the way and open ANY folder and type %temp% in the address bar of that folder and press enter. You will see a bunch of folders with titles like this "{B2B09672-51AB-4EF6-BDDF-50CB9719052B}" This is just an example. While in that temp folder just do a search for rom.zip and when you find it you can copy that file to your desktop and then just click cancel in the ruu welcome screen for now.
4. Open the rom.zip file with 7zip. You must use 7zip. The built in windows zip program wont work. Once its opened with 7zip, extract these two files 'recovery_signed.img' and 'boot_signed.img'. This is your stock recovery and stock kernel. Extract those to the fastboot folder.
5. You must somehow get your device into the bootloader again. I had the same symptoms as you did with the dark screen and dim red text. I just kept playing with the volume down during boot and eventualy got there. DO NOT USE VOLUME UP!!
6. Once your in the bootloader choose fastboot and plug your device in and it should now say fastboot usb at the top of the bootloader screen. Now run theses commands.
7. Commands to run.
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
8. Now while in bootloader fastboot usb still just run the ruu and follow all instructions. Make sure you have atleast 30% battery while performing this. And if all goes well you will be back to square one.

Nexus 7 2013 stuck at Google screen

So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you

See this thread: http://forum.xda-developers.com/showthread.php?t=2381582

krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.

[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.

anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state

hard reset ?
hard reset always works for me. 20 seconds

krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.

sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen

Is your device rooted? If not that is just rediculous on asus's part

slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.

I would return it..I'm sorry to hear that I have had troubles myself with two devices so far

krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.

sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.

sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?

krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.

sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?

sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?

I have no way to enable usb debugging since I cant tun on the device, right?

krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.

Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you

[Q] No CWM just HTC boot screen

So, I tried to get the latest Cyanogenmod on my phone.
Resulted in the the process com.android.phone has stopped issue.
FInally managed to get around that but no my phone is stuck with no CWM, no USB Windows fileshare and a HTC bootscreen.
I have searched, and read a lot of posts and the closes thing to recovery is a post on putting on a Nandroid backup for my Y13 (http://forum.xda-developers.com/showthread.php?t=1975140)
But, since I have no USB fileshare I am unable to get it on the phone and start the process.
Can anybody point me in the right direction?
I need to completely wipe and reinstall everything but has no access other that fastboot USB.
What info should I post and how do I find it if more is needed.

smurf69 said:
So, I tried to get the latest Cyanogenmod on my phone.
Resulted in the the process com.android.phone has stopped issue.
FInally managed to get around that but no my phone is stuck with no CWM, no USB Windows fileshare and a HTC bootscreen.
I have searched, and read a lot of posts and the closes thing to recovery is a post on putting on a Nandroid backup for my Y13 (http://forum.xda-developers.com/showthread.php?t=1975140)
But, since I have no USB fileshare I am unable to get it on the phone and start the process.
Can anybody point me in the right direction?
I need to completely wipe and reinstall everything but has no access other that fastboot USB.
What info should I post and how do I find it if more is needed.
Click to expand...
Click to collapse
Download Philz recovery and flash via fastboot. After this go in recovery and mound the sd card and wait 3-4 min. copy your rom on SD card flash the rom and flash the boot.img!

Thant said:
Download Philz recovery and flash via fastboot. After this go in recovery and mound the sd card and wait 3-4 min. copy your rom on SD card flash the rom and flash the boot.img!
Click to expand...
Click to collapse
Thanks Thant!
So, I have downloaded Philz, I think I have flashed the recovery.img file over to the phone from CMD shell window.
I have rebooted my phone to fastboot menu and selectet recovery.
The result is still the same. Just the htc boot screen.
I`m sure I`m doing something wrong but cant figure out how. Philz How to uses USB / PC file transfer so I`m unable to use it as a step by step.
Would really appreciate a step by step command overview. If possible with an explanation so that I learn why I do the different commands. Then I wont be so f.. ignorant about these things anymore. Hopefully

smurf69 said:
Thanks Thant!
So, I have downloaded Philz, I think I have flashed the recovery.img file over to the phone from CMD shell window.
I have rebooted my phone to fastboot menu and selectet recovery.
The result is still the same. Just the htc boot screen.
I`m sure I`m doing something wrong but cant figure out how. Philz How to uses USB / PC file transfer so I`m unable to use it as a step by step.
Would really appreciate a step by step command overview. If possible with an explanation so that I learn why I do the different commands. Then I wont be so f.. ignorant about these things anymore. Hopefully
Click to expand...
Click to collapse
The command to flash the recovery is fastboot flash recovery recovery.img you must to put recovery.img in your fastboot directory and you can run the command fastboot erase cache after this go in bootloader and choice the recovery this is all

Thant said:
The command to flash the recovery is fastboot flash recovery recovery.img you must to put recovery.img in your fastboot directory and you can run the command fastboot erase cache after this go in bootloader and choice the recovery this is all
Click to expand...
Click to collapse
Again, thanks!!
Forgot my phone at work so I`ll have a go tomorrow!

This issue will remain unsolved.
The phone no longer charges so I am unable to start any process what so ever.
Thank you so much for the help I got

smurf69 said:
This issue will remain unsolved.
The phone no longer charges so I am unable to start any process what so ever.
Thank you so much for the help I got
Click to expand...
Click to collapse
there is also a zip with a .bat file to charge in fastboot ...it should all work...as it was said before fastboot flash recovery recovery.img and fastboot erase cache...if nothng works then do the factory reset through bootloader helps often...if not working...hm try to find latest RUU for your CID which ould work...if already on hboot 1.7x only RUU from 3.14 and up would work

One-X-master said:
there is also a zip with a .bat file to charge in fastboot ...it should all work...as it was said before fastboot flash recovery recovery.img and fastboot erase cache...if nothng works then do the factory reset through bootloader helps often...if not working...hm try to find latest RUU for your CID which ould work...if already on hboot 1.7x only RUU from 3.14 and up would work
Click to expand...
Click to collapse
Thanks, but the phone is completely dead and unable to boot.
There is no power and the phone won`t charge so I guess it`s a gonner.

smurf69 said:
Thanks, but the phone is completely dead and unable to boot.
There is no power and the phone won`t charge so I guess it`s a gonner.
Click to expand...
Click to collapse
Search the forums, there are answers to get your device back to live. Like the charging script.

Trying to fix an M8

So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!

TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.

xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.