Edited to add data I found in recovery mode:
"HTC/htc_himauhl/htc_himauhl
6.0/MRA58K/buildteam10121728"
And there are a bunch of error messages ending in:
"E: failed to mount /cache (Invalid argument).. try emmc mount)
E: Can't find device node for mount point /cache"
Can anybody point me to a good resource explaining how I can attempt to apply an image from the sd card?
Or how to check if usb debugging is switched on?
Original post:
When I unplugged my HTC M9 this morning it was on a screen saying the phone is encrypted and prompts to enter the screen lock password. I enter what I think is the correct code (I've been using pattern unlock but put in the code i used to use) and it tells me its correct but the data is corrupted and it needs to do a factory reset.
There is no other option apart from accepting the factory reset.
When I accept the factory reset it just says 'rebooting...' and then never does (I waited an hour).
I've tried the obvious holding down volume up and power off.
I can get to the options screen to choose reboot, download mode, recovery etc. I tried reboot (obviously) but it only boots back to the decrypt screen. I also tried recovery mode and I got a picture of a phone with a red warning triangle containing an exclamation mark and nothing else happened. I tried pressing power and volume up and it just rebooted back to the decrypt screen.
It says it is:
***Software status: Official ***
*** LOCKED ***
*** S-ON ***
It's a carrier-free version, bought from Amazon UK. I haven't done anything to it (I used to root and flash custom roms but not for 2-3 years - I have a nearly 2-year old - so my knowledge is mostly forgotten and out of date).
I have no reason to think that usb debugging is on so I'm worried that there is nothing I can do.
Edit: Maybe I can install something from the sd card. I'm going to try that.
Any suggestions greatly appreciated.
srjones said:
Edited to add data I found in recovery mode:
"HTC/htc_himauhl/htc_himauhl
6.0/MRA58K/buildteam10121728"
And there are a bunch of error messages ending in:
"E: failed to mount /cache (Invalid argument).. try emmc mount)
E: Can't find device node for mount point /cache"
Can anybody point me to a good resource explaining how I can attempt to apply an image from the sd card?
Or how to check if usb debugging is switched on?
Original post:
When I unplugged my HTC M8 this morning it was on a screen saying the phone is encrypted and prompts to enter the screen lock password. I enter what I think is the correct code (I've been using pattern unlock but put in the code i used to use) and it tells me its correct but the data is corrupted and it needs to do a factory reset.
There is no other option apart from accepting the factory reset.
When I accept the factory reset it just says 'rebooting...' and then never does (I waited an hour).
I've tried the obvious holding down volume up and power off.
I can get to the options screen to choose reboot, download mode, recovery etc. I tried reboot (obviously) but it only boots back to the decrypt screen. I also tried recovery mode and I got a picture of a phone with a red warning triangle containing an exclamation mark and nothing else happened. I tried pressing power and volume up and it just rebooted back to the decrypt screen.
It says it is:
***Software status: Official ***
*** LOCKED ***
*** S-ON ***
It's a carrier-free version, bought from Amazon UK. I haven't done anything to it (I used to root and flash custom roms but not for 2-3 years - I have a nearly 2-year old - so my knowledge is mostly forgotten and out of date).
I have no reason to think that usb debugging is on so I'm worried that there is nothing I can do.
Edit: Maybe I can install something from the sd card. I'm going to try that.
Any suggestions greatly appreciated.
Click to expand...
Click to collapse
This is the M9 forum, so the advice we have here is for that device. Head over to the M8 forum for help specifically tailored to your phone.
Typo!
computerslayer said:
This is the M9 forum, so the advice we have here is for that device. Head over to the M8 forum for help specifically tailored to your phone.
Click to expand...
Click to collapse
Thanks, sorry, it is an M9. I initially thought it was an M8 and had to google the difference so I must have been thinking of that. Have edited the post now
srjones said:
Thanks, sorry, it is an M9. I initially thought it was an M8 and had to google the difference so I must have been thinking of that. Have edited the post now
Click to expand...
Click to collapse
In that case, check out the readme thread at the top of this forum. It has all you'll need to find the correct RUU and apply it properly.
computerslayer said:
In that case, check out the readme thread at the top of this forum. It has all you'll need to find the correct RUU and apply it properly.
Click to expand...
Click to collapse
Thanks for your reply, but are you sure? As I said in my post, the device is locked, S-ON and usb debugging is not switched on and I cant get into the phone to turn it on. The normal instructions seem to assume that I can turn usb debugging on.
Thanks again for your time
srjones said:
Thanks for your reply, but are you sure? As I said in my post, the device is locked, S-ON and usb debugging is not switched on and I cant get into the phone to turn it on. The normal instructions seem to assume that I can turn usb debugging on.
Thanks again for your time
Click to expand...
Click to collapse
I am sure ...and the readme thread explains this too. Take some time to read through it, especially the post about RUUs.
You mention not getting the phone to turn on....do you mean that it won't power on at all or that it won't boot? If it does turn on, what do you see?
[EDIT] Re-reading your original post, you say that you can get into download mode. If this is still the case, then you should be able to apply the appropriate RUU. Again, the readme thread has all you need to get that going[/EDIT]
Thank you, you've been incredibly patient. I'd got a bit discouraged at the scale of the problem. It makes it much easier to know that a fix should be possible at the end of the process.
srjones said:
Thank you, you've been incredibly patient. I'd got a bit discouraged at the scale of the problem. It makes it much easier to know that a fix should be possible at the end of the process.
Click to expand...
Click to collapse
The first time going through this kind of thing is always a bit intimidating. After going through it a few times it becomes familiar.
Read through the RUU section in the readme thread. As it'll describe, you'll need your OS version to determine your SKU which will lead you to the right RUU and so on. Post here if you've got questions along the way.
computerslayer said:
The first time going through this kind of thing is always a bit intimidating. After going through it a few times it becomes familiar.
Read through the RUU section in the readme thread. As it'll describe, you'll need your OS version to determine your SKU which will lead you to the right RUU and so on. Post here if you've got questions along the way.
Click to expand...
Click to collapse
Hi, I've been reading post #3 in the reader (all seems very straightforward, I feel foolish for not persisting in the first place). I still need to get a card reader to get a ruu onto the card from my pc but im trying to get the right ruu ready now.
In download mode I have a line that says OS-3.35.401.32
I think this means that I look in the SKU 401 section but then there isn't a file for my exact number, the closest ends in .12 rather than .32
Does this mean that I need to look in other places to get one that matches exactly?
Thanks again
srjones said:
Hi, I've been reading post #3 in the reader (all seems very straightforward, I feel foolish for not persisting in the first place). I still need to get a card reader to get a ruu onto the card from my pc but im trying to get the right ruu ready now.
In download mode I have a line that says OS-3.35.401.32
I think this means that I look in the SKU 401 section but then there isn't a file for my exact number, the closest ends in .12 rather than .32
Does this mean that I need to look in other places to get one that matches exactly?
Thanks again
Click to expand...
Click to collapse
Sounds like you've read it well! Don't be too hard on yourself - there is a lot to take in. From your OS version your SKU is indeed 401.
You're good to use the RUU 3.35.401.12 even though your current version ends in .32 (from the readme: "In other words the part marked with y of x.xx.xxx.yy is allowed to differ whereas x needs to be the same for your current firmware version and the RUU").
computerslayer said:
Sounds like you've read it well! Don't be too hard on yourself - there is a lot to take in. From your OS version your SKU is indeed 401.
You're good to use the RUU 3.35.401.12 even though your current version ends in .32 (from the readme: "In other words the part marked with y of x.xx.xxx.yy is allowed to differ whereas x needs to be the same for your current firmware version and the RUU").
Click to expand...
Click to collapse
Aah, thanks. Amazing what I can miss even after I think I've read it "thoroughly".
computerslayer said:
The first time going through this kind of thing is always a bit intimidating. After going through it a few times it becomes familiar.
Read through the RUU section in the readme thread. As it'll describe, you'll need your OS version to determine your SKU which will lead you to the right RUU and so on. Post here if you've got questions along the way.
Click to expand...
Click to collapse
Hi, I'm following the Instructions for the SD card method from post #3 of the readme. I've just done step 5: "You will be asked whether you want to flash the file. Confirm with the volume up button"
The phone is now vibrating regularly every (approx) 3 seconds and flashing a silver HTC logo on the screen. I'm pretty sure this isn't normal. This isn't normal, right?
It's been doing it for several minutes.
Do you have any suggestions? Maybe leave it for a good long while and then try holding down power and volume up?
srjones said:
Hi, I'm following the Instructions for the SD card method from post #3 of the readme. I've just done step 5: "You will be asked whether you want to flash the file. Confirm with the volume up button"
The phone is now vibrating regularly every (approx) 3 seconds and flashing a silver HTC logo on the screen. I'm pretty sure this isn't normal. This isn't normal, right?
It's been doing it for several minutes.
Do you have any suggestions? Maybe leave it for a good long while and then try holding down power and volume up?
Click to expand...
Click to collapse
It doesn't seem normal, I must admit. I think I'd let it go for about 30 minutes to see if it is rebooting as part of the RUU installation. After that, I'd force it to power off and re-try the attempt - though I might re-download the RUU matching my SKU and use that instead. It could be that your download got corrupted.
There is a way to check the MD5 sum of your download to confirm the integrity of your file. I haven't done that in a while, but I recall that there are plenty of tools easily available (Google will help you here).
computerslayer said:
It doesn't seem normal, I must admit. I think I'd let it go for about 30 minutes to see if it is rebooting as part of the RUU installation. After that, I'd force it to power off and re-try the attempt - though I might re-download the RUU matching my SKU and use that instead. It could be that your download got corrupted.
There is a way to check the MD5 sum of your download to confirm the integrity of your file. I haven't done that in a while, but I recall that there are plenty of tools easily available (Google will help you here).
Click to expand...
Click to collapse
Thanks, the MD5 sum is fine (managed to take in that bit of the read me).
I tried to use the ruu again just to be sure but there's no difference.
I think it's not able to apply the ruu at all. It takes no time at all before it does the buzzing/ flashing thing and when i force a restart I still have the exact same error message in recovery mode. Like maybe it started by trying to wipe the cache, couldn't find it, tried to format and mount again, but couldn't find the device node (not totally sure there) and then gave up.
I used to use Linux a long time ago (was never an expert) and if I saw this sort of thing with a pc, I'd be repartitioning the hard drive while googling the price of a new one. I just don't know enough about Android (i know nothing about Android) to work it out though.
I took a photo of the error message using another phone, is it worth trying to post it? I don't know how to do that and will have to spend time finding out which is why I'm asking rather than just posting out.
srjones said:
Thanks, the MD5 sum is fine (managed to take in that bit of the read me).
I tried to use the ruu again just to be sure but there's no difference.
I think it's not able to apply the ruu at all. It takes no time at all before it does the buzzing/ flashing thing and when i force a restart I still have the exact same error message in recovery mode. Like maybe it started by trying to wipe the cache, couldn't find it, tried to format and mount again, but couldn't find the device node (not totally sure there) and then gave up.
I used to use Linux a long time ago (was never an expert) and if I saw this sort of thing with a pc, I'd be repartitioning the hard drive while googling the price of a new one. I just don't know enough about Android (i know nothing about Android) to work it out though.
I took a photo of the error message using another phone, is it worth trying to post it? I don't know how to do that and will have to spend time finding out which is why I'm asking rather than just posting out.
Click to expand...
Click to collapse
It's certainly better than nothing - and I'm interested to hear more about an error message. I haven't applied a RUU in a while, but I don't recall the phone ever booting into recovery.
Try formatting data in TWRP recovery. It will wipe your internal memory though. This fixes the issue on the 10.
computerslayer said:
It's certainly better than nothing - and I'm interested to hear more about an error message. I haven't applied a RUU in a while, but I don't recall the phone ever booting into recovery.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, it doesn't boot into recovery mode straight away, it just dies a bootloop. I then hold down various buttons to get to the boot loader. Hopefully I've added the picture correctly.
Edit: I can't see the photo. I don't know why it's not working. It is here https://imgur.com/gallery/vkP5Z
Did I do something stupid? Is imgur not the right thing to use?
side_flip15 said:
Try formatting data in TWRP recovery. It will wipe your internal memory though. This fixes the issue on the 10.
Click to expand...
Click to collapse
Thanks, I'm not sure what 'Formatting data in TWRP recovery' means. Posts #4 and #5 of the readme mention TWRP. Do i need to download one of the linked backups and use it to restore?
srjones said:
Thanks, I'm not sure what 'Formatting data in TWRP recovery' means. Posts #4 and #5 of the readme mention TWRP. Do i need to download one of the linked backups and use it to restore?
Click to expand...
Click to collapse
Let's back up a step - do you have TWRP installed? Unless you received the phone from someone who installed it themselves, you'd have to have done this yourself (by unlocking the bootloader & flashing TWRP via ADB) - so if you don't know, you probably don't.
If you did receive the phone from someone else and want to check:
boot into download mode (PWR-VOLDWN)
use the volume keys to highlight 'boot into bootloader' and the power key to select that option once it is highlighted
use the volume keys to highlight 'boot into recovery' & the power key to select that option once it's highlighted
If you have TWRP installed, you'll see the blue TWRP logo and name. Otherwise you'll be loaded into the stock Android recovery. You can back out by using the volume keys to navigate and the power button to select the option to get out.
computerslayer said:
Let's back up a step - do you have TWRP installed? Unless you received the phone from someone who installed it themselves, you'd have to have done this yourself (by unlocking the bootloader & flashing TWRP via ADB) - so if you don't know, you probably don't.
If you did receive the phone from someone else and want to check:
boot into download mode (PWR-VOLDWN)
use the volume keys to highlight 'boot into bootloader' and the power key to select that option once it is highlighted
use the volume keys to highlight 'boot into recovery' & the power key to select that option once it's highlighted
If you have TWRP installed, you'll see the blue TWRP logo and name. Otherwise you'll be loaded into the stock Android recovery. You can back out by using the volume keys to navigate and the power button to select the option to get out.
Click to expand...
Click to collapse
Ah, right, no, nothing non-standard installed. So that's not an option. Thanks
Related
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
obones said:
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
Click to expand...
Click to collapse
Not sure if you do or not but do you need to have Htc Sync installed for the drivers?
I do have HTC Sync installed
Are you rooted? You need root to do this. If you are then why not use fake flash or unrevoked to enter recovery.
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
obones said:
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
Click to expand...
Click to collapse
Recovery-windows.bat won't work unless you are rooted. The screen with the red triangle isn't actually recovery mode. The .bat file you would run pushes the recovery to the phone.
If you are not going to root, then you can get an app from the market that puts your phone on silent as you switch it off, and then back to normal when it's booted. This disables the boot sound. It's called silent boot I think.
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
obones said:
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
Click to expand...
Click to collapse
try fake flash? ive never used it so i duno if u need to be rooted
Fake flash needs root. No custom recovery will work without root. Quite simply, if you are not rooted you will not have write access to /system
please help.
i try to install froyo rom.
after flash FroYo_inkreDroid (14.07.2010) rom (throught standart flashrom procedures by update.zip) the device will not boot into os. i try update modem and after this the device win not booting to recovery mode.
i try press both combination (back key + power and volume down + power). the result of both combination is: 7 short vibro signals and black screen.
please help me, how me recovery my device.
thnx and sorry for my english.
your going to have to root it.
Hey guys,
I hope you're all well.
Great forum by the way.
I've searched extensively for solutions to my problem, yet I've been unable to find anything.
I think the problem started yesterday, when I restarted my phone and for some reason it went into safe mode.
I didn't lost any functionality so I didn't care too much until this morning, when I tried to get out of safe mode.
My phone has taken me to the bootloader (white screen with skateboarding Android) and for some reason, the power key (used to select options) and the volume keys (used to scroll) are not functioning.
As a result I cannot click or choose anything and the white bootloader screen persists in limbo.
I desperately need some suggestions, any help is very much appreciated.
Just so you know:
I've taken the battery out and put it back in, which takes me straight back to the bootloader screen, same with sim card.
The phone is running Coredroid (can't remember which version).
Has S-OFF.
Sorry I'm not much of an expert...
Also, on startup, phone says something along the lines of:
SD Checking...
LOADING... [PD98DIAG.zip]
NO IMAGE!
LOADING... [PD98DIAG.nbh]
NO IMAGE OR WRONG IMAGE!
LOADING... [PD98IMG.zip]
NO IMAGE!
LOADING... [PD98IMG.nbh]
NO IMAGE OR WRONG IMAGE!
Kind regards,
- Ric
Something has become corrupted.
Best bet would be to use an ruu 2.36.405.8 and lower, once loaded up, skip through the setup and then root again.
http://driphter.com/index.php?topic=3867.0
after you've done all that, install rom manager, and then restore your last backup.
Just a quick update.
Managed to get into Clockwork Mod Recovery.
Got the SD Card to mount.
Formatted it in windows.
Copied over Coredroid.
Went thru the install process.
Installed without error.
Booted up.
Took it's time, displayed the Coredroid animation but then vibrated and took me straight to Bootloader again.
Any advice or best to do this RUU thing?
Would this:
RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed
Be ok?
Am I in the right ballpark?
Truly got no clue when it comes to this stuff
use the 2.36.405.8 RUU, then you wont have to spend your time updating the radio and such, that version of gingerbread is rootable using gingerbreak (so just follow that path of my method and you're set)
JSLEnterprises said:
Something has become corrupted.
Best bet would be to use an ruu 2.36.405.8 and lower, once loaded up, skip through the setup and then root again.
after you've done all that, install rom manager, and then restore your last backup.
Click to expand...
Click to collapse
Hello mate,
Just a quick question.
How do I get my computer to recognize my phone prior to running this RUU thing?
Considering I can't scroll or select anything in bootloader screen?
Can I run this RUU thing from ClockworkMod?
Kind regards,
- Ric
you run it from your pc. its an advaced installer that pushes the stock rom to the device and overwrites everything... it will put the phone into a different bootloader state than the one you can nav through.
Also, sometimes the phone is booting into bootloader, while other times it is booting into ClockworkMod.
It seems I have no control over which screen it initially boots to.
I DO HAVE options in ClockworkMod because my volume keys allow me to scoll and my power button allows selection, whereas in bootloader, the keys do not function.
Could you PLEASE provide some advice on how to boot into ClockworkMod rather than bootloader?
Kind regards,
- Ric
JSLEnterprises said:
you run it from your pc. its an advaced installer that pushes the stock rom to the device and overwrites everything... it will put the phone into a different bootloader state than the one you can nav through.
Click to expand...
Click to collapse
Yes I do realize I run the RUU from the PC.
I don't think I was very clear.
I was trying to ask you what state the phone needs to be in?
Do I have to mount the SD Card from ClockworkMod?
Or can I run the RUU while in Bootloader?
Does it matter?
Neither have worked.
I get a 170 error (USB Connection error).
The RUU cannot see my phone.
I was wondering if there's a way to fix this?
I have also now tried to install Leedroid and Gingervillian.
Both have installed perfectly but refuse to boot all the way.
Instead taking me back to Bootloader...
Ok, Leedroid somehow booted.
No network or anything though.
Very unstable...
if the phone is running leedroid now and you have the htc sync tools installed (but without sync running, just needs to be installed for the drivers)
leave it as it is connected to your pc, doesnt matter if debugging or anything else is on or off. just leave it alone sitting where it is on your desk or wherever it is...
Start the RUU, and then just follow the path the installer takes you through, then let it do its magic...
Ended up d/l Cyanogen.
Installed it.
Working, detected networks, wifi is connected.
All good I suppose.
That was a bit scary!
Thanks for your help mate.
So, this morning at 5am (yes, stupid time to be playing) I flashed a zip. I have stored on my phone zips for both this and my tablet, and guess what genius did? flashed the wrong friggin one! Very surprised it went through without fault, but hey, **** happens.
So, basically what happened, is my phone became a brick. Black screen, could not boot it up, couldn't et to bootloader or download mode or recovery, tried several things like pulling battery for 30 secs then putting back in, plugging into PC without battery and putting battery in, leaving without battery or SIM for 30 minutes and putting back in, NA friggin DA. Still a brick. Not even the vibration when it first kicks in. Nothing
Starting to think time to call tech support, but as I was trying to plug into PC, I noticed something trying to install, then disappearing real fast. That was my first clue. I opened device manager, plugged phone in, and watched what was happening. A device called OMAP4460 was trying to install for half a second before disappearing, failing, but still, it was something. Even though screen was still blank, and not even bootloader would come up, this was happening. So I googled.
I found this site/thread: http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/. Legija, is a friggin genius Downloaded and unzipped the package, ran the bat, and plugged in the phone. But alas, still no joy
Reread his post - install drivers first...So, putting on my tech hat, how to install drivers if device is not listed, I went into the Actions menu in Task Manager (Win 7), and selected to add legacy hardware. I then chose to install manually, then selected have disk, and browsed to the drivers in the zip package from Legija (all this without device plugged in BTW). I installed the OMAP flash driver successfully, and now showing in task manager with the nice yellow triangle/exclamation mark.
Ran the bat file again, plugged phone in **WITHOUT** battery in phone, and off it went scrolling through it's processes, ninja'n away my f'up. When it completed, put battery back in, held down power, and up she came! Woot! Got back into OS no issues, and I'm one very happy camper.
So I thought i'd share, not thinking anyone else may do the same bloody stupid thing, but maybe a variance, or just have the same symptom (black screen, attempt to install OMAP when plugged into USB), this may just help you! AS for me...deleted all files not for GNEX, i'll continue to stuff around before work, so this is safe
EDIT:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process. Once you see "Press any key to continue..." close the CMD window and proceed to step 9
9. Unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Thanks for sharing this find, I'm sure others will find this to be useful
No problem, true believer in sharing my stupid mistakes so other may not follow, or if they do, know how to fix
Oh, in my write up - one change now edited - run the bat with the phone connected to USB **WITHOUT** battery in, once it's finished insert and boot up
Next time I'll be more safe while flashing roms to my phone.
Great find.
wow, this is possible? i thought cwm will prevent you from flashing wrong zips and even if not, why would it kill the bootloader? i was under the impression gnex is close to unbrickable but this topic you linked opened a whole can of worms for me, whats with all these hundreds of people who hard(!)bricked their nexus ... did i miss something?
This was a custom zip I had created myself to do some things on my tab, it ran from install script an install.sh that then went and installed a recovery img. Pretty sure i've never seen this before from any install zip, it was the behaviour I put in mine that allowed it to go through, and I hadn't put into the script to stop if not correct device - lesson learned
BUT - that said, you can do things like this to your phone running scripts, very easy to actually if it's running from su... So never run scripts unless you trust he person whose created it (or have written it yourself and certain of it), know it's definitely for your device, and, most importantly - never miss this step - have had 3 cups of coffee first :good:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
rekrapg said:
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
Click to expand...
Click to collapse
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If it's not permanent, it's not, and never was, a brick.
Click to expand...
Click to collapse
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
Well it happens my dude.....at least he took the time out to give a guide and explained how he fixed it just in case someone else does something similar
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
efrant said:
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
True....but most people would not know what to do in this situation and call it a day....at least he searched Google and fixed his problem. Wish more people were like him ya know
---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------
rekrapg said:
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Click to expand...
Click to collapse
Exactly I said most people would have called it a day.....ZOMGZ MA FONEZ NO LITE UPZ IT HARDSOFT BRICKED!! .....lol all joking aside man your like me I wouldn't have stopped until I was absolutely sure I needed them JTAG boys
Persistence pays off...remember that
Yup. In most cases, there's a way around a problem, you just have to dig until you find it
Congratulations
Saludos desde Ecuador
Though I don't want to have chance to perform your provided method, it's really good to know, in case....
Congratulation and thanks!
rekrapg said:
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Chad_Petree said:
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Click to expand...
Click to collapse
Choose the one closest to what displays on the device manager. I started with the OMAP Flash Drive one and it worked for me, but you can always choose the 'update driver' option and install another if required. Turn off User Account Control in Control Panel/Users and make sure you're on an admin account, as it may by default block the ability to install unsigned drivers, to be honest not sure on that one as it's always been first port of call for me on Win 7 (and Vista).
I also found this that might help: http://www.techspot.com/community/t...signed-drivers-in-windows-vista-7-x64.127187/
Wish I would have found this a week ago! The exact same thing happened to me, except I had been running a working JB ROM for a day or so.
Went jogging, was listening to music, came home, music stopped, screen wouldn't turn on with power button or USB cable with a charger or a computer, but there was a notification LED flashing. No amount of pressing and holding the power button would bring it back to life, so I pulled the battery. After that it was in the exact state your GNEX was in. Not even the vibrate when trying to power it up. After a few hours of charging and trying all sorts of things to breathe life into it (including a battery swap) I ended up returning it to the brick and mortar VZW store and they replaced it because I was under 2 weeks with the phone.
Thanks for posting!
I ran the OMAPFLASH_tuna on my GNex and now, I seem to be stuck at "Sending Data"(SEE last line in the image attached)
The values of 131072 has been like that for over 20 minutes and have not changed. What data is it sending and to who or where?
to those who've used this too, What should happen after this?
thanks...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would be lying if I said I knew exactly what this wonderful tool is doing mate With mine, it ran through in like 30 seconds to completion. I ran it 3 times to be sure! I have 2 suggestions,
1. Sign up to those forums and ask the expert
2. If your device is already 'bricked', it may be worth just disconnecting, closing the CMD window, reconnect and re-run it.
I'm no expert on this application though, I simply found it, it worked for me, so I shared. So option 1 may be your best shot. It's quite likely the bloke who created the tool will be able to let you know the proper path to go down.
EDIT: I am at work atm, so I can't 're-run' it on my device to show you the screen - but I recall it comes up with a 'press any key to continue' prompt after completion (pressing any key just re-runs it).
Funny because another person on GSMHosting is experiencing the same problem and says that his just stops downloading... Just like mines and at the same stop too... hummm...
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
sjmahmoudi said:
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
Click to expand...
Click to collapse
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply a RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
computerslayer said:
this problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your sku and whether or not there really is a hardware issue or not, it may be possible to apply a ruu, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your os version, which will help us determine your phone's sku.
Click to expand...
Click to collapse
os: 3.35.401.32
shivadow said:
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
Click to expand...
Click to collapse
I rooted this phone when I first bought it. but 4 months ago I unroot it so I could update it's android to marshmallow. after unrooting, i receive the android update and everything was as normal as a fresh unrooted phone.
I was able to go to download mode when first my phone faced this problem. but now the download mode is not available
it says: failed to boot to download mode
press volume up or down to back to menu
this build is for
development purposes only
do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.
computerslayer said:
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply an RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
Click to expand...
Click to collapse
I took my m9 to HTC service center. he said that main chip must be replaced. after replacing the chip, he said that I need a dump.bin file and I do not have it. now after 3 months, my dear m9 is still on the service center . I search all over the net for the dump.bin file but there is nothing at all.
I do not even know what the hell is the dump.bin file. he said that your phone can boot but it will not have antenna without relevant dump file. I'm confused please help me
my phone model ID: 0PJA100
Did you give your phone to an official HTC service center? HTC should have the needed file so the fact that you should provide it to the service center confuses me a bit.
It's impossible to get that file (from a working phone) without a JTAG device and I doubt that many M9 owners have one since they're quite expensive. Sorry for the bad news.
Greetings to all XDAdevelopers community. Please sorry me if that queiston was discussed. I can't find ANY solution of that problem.
I don't even know where to start.
I woke up in the morning, turned on my HTC One M9 and saw: "Your phone is encrypted To decrypt your phone, enter your screen lock password"
Of course I did not do ANYTHING including encryption etc....
By the power of my mind i decided to try to enter the password "0000" (Four zeros). The next phrase was: Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account.
There was an inscription below stated: "Reset phone"
I clicked "Factory reset" Factory data reset - rebooting ..... That is ALL. Rebooting for about 30 minutes and nothing happens.
I was advised (another forum) to reflash my firmware. (Using SD-card)
I clicked VolumeUP+VolumeDown+Power Button - Reboot to download mode (I have attached a picture below)
The phone saw my SD-card (I have attached a picture below) and the firmware which I uploaded and renamed to my SD-card.
I clicked "Press VolUp to start flash"
"HTC download mode" - written red letters - "Start UI updating'' --- After that the phone is rebooting - HTC letters on a black background - vibration - screen is out - HTC letters on a black background - vibration - screen is out - HTC letters on a black background - vibration - screen is out .... And so on and so on and so on infinitely.
The Question: Could anyone give me an explanation about that issue? I can't find any information about it. I don't know what I should do.
Please sorry for grammar mistakes and incorrect grammar sentence construction sometimes. English is not my native.
Kind regards.
P.S. I have deleted pictures due to forum restriction. I don't have 10 messages.
S-off or s-on?
Did you flash the same firmware version as what was already on the phone?
Any error messages?
Is the phone still responding?
shivadow said:
S-off or s-on?
Did you flash the same firmware version as what was already on the phone?
Any error messages?
Is the phone still responding?
Click to expand...
Click to collapse
Thank you for the respond.
Of course I did flash the same firmware version that was already on the phone previously. I did it not long time ago (I had "google app" error). I exclude "wrong version firmware error" from my side.
The phone is responding to what I have attached on the pictures. I tried to go to recovery mode and made "Wipe data factory" the phone said "error SD is not mounted" or something in that way.....
I went to the service center. They told me eMMC is dead.
Is the google account recoverable to another device using the same password?.
If the phone boots to download mode try flashing from another sd card.
Double check the md5 is correct and that the firmware is EXACTLY the same as the one the phone is currently running. It is important. If not then find another source.
If you get fail90 then flash again and again until successful.
If this steps have been done then your phone will be faulty.
Those pictures would have helped..
shivadow said:
Is the google account recoverable to another device using the same password?.
If the phone boots to download mode try flashing from another sd card.
Double check the md5 is correct and that the firmware is EXACTLY the same as the one the phone is currently running. It is important. If not then find another source.
If you get fail90 then flash again and again until successful.
If this steps have been done then your phone will be faulty.
Those pictures would have helped..
Click to expand...
Click to collapse
Shivadow, thank you for helping me! Yes I did it. Phone is dead.
Kind regards
My HTC ONE M9 is giving me the "Your phone is encrypted" message.
It says that i must enter my screen lock password to decrypt my phone.
Firstly i did not have a screen lock on my phone.
Secondly it happened all of a sudden