Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
3vilrabbit said:
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
Click to expand...
Click to collapse
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
CCallahan said:
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
Click to expand...
Click to collapse
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
3vilrabbit said:
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
Click to expand...
Click to collapse
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
CCallahan said:
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
Click to expand...
Click to collapse
I'm gonna bring it back to the shop and hopefully, if I put up a poker face if they ask me about rooting my device :angel:, they accept it and treat it with warranty
For some reason, I really don't know what I have being trying...my tablet miraculously is working again!
Thread can be closed...
I had been using my tablet normally and set it aside for a while. When I went back to it, it was stuck at the boot splash screen that is black with the white Google text on it. I tried rebooting several times and it would return to this state.
I booted into fastboot mode and went to recovery mode. The following errors were displayed at the bottom of the screen:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
E:failed to mount /cache (Invalid argument)
I tried doing "wipe data/factory reset". It says:
-- Wiping data...
Formatting /data...
... and then goes into many more errors regarding failures mount/open /cache
Thinking maybe the cache partition was bad, I went back to fastboot mode and issued the following command from my pc:
fastboot format cache
... but the command never returns (after an hour, it had not returned, so I cancelled)
The same happens if I try
fastboot format userdata
... it never returns.
I can't unlock the bootloader to attempt to flash a new image. I can issue command
fastboot oem unlock
and get the correct screen, but selecting unlock just locks up the tablet. I left it this way for a couple hours, no change.
So to summarize: I can access fastboot, I can access recovery, but I can't seem to affect any change that will recover the system.
I've exhausted everything I know to try. Any thoughts?
It's ironic because I hack on these all the time at work, but this was my personal unit that was stock and unrooted.
Yours is not a common situation, but there have been a few reported just this last week. Unless someone knows of a solution, like why the bootloader hangs at unlocking or if it can be reflashed (not possible AFAIK without unlocking), your only option seems to be warranty service. Sorry.
Pandae said:
Yours is not a common situation, but there have been a few reported just this last week. Unless someone knows of a solution, like why the bootloader hangs at unlocking or if it can be reflashed (not possible AFAIK without unlocking), your only option seems to be warranty service. Sorry.
Click to expand...
Click to collapse
Not what I wanted to hear, but thanks. I wonder if a recent update has stressed the file system or ECCM.
Someone posted a way to test the ECCM chip via command line, but I can't find it. Do you recall?
I've only heard of Android apps that test the eMMC's integrity, nothing that can be run from a PC.
I had a similar problem and when I used to enter 'fastboot devices" I used to get '?????? fastboot'. and the bootloader used to freeze but recovery mode (TWRP) was fine.
I then realized that I wasn't using the USB cable that came with the Nexus 7. When I switched cables. It recognized the device using 'fastboot devices'. Then I just ran the .bat file in the factory image files. I hope this helps.
I have the exact same issue that just started as of Tuesday, January 7th. I feel like I've exhausted all options and continue to get the mount cache error. I secretly suspect the storage went bad on that very cold day in NYC. My old Nexus 7 was off at the time and still works but the new one might have been on in my backpack walking around.
BootlegZani said:
I have the exact same issue that just started as of Tuesday, January 7th. I feel like I've exhausted all options and continue to get the mount cache error. I secretly suspect the storage went bad on that very cold day in NYC. My old Nexus 7 was off at the time and still works but the new one might have been on in my backpack walking around.
Click to expand...
Click to collapse
I'm on the same boat as you, guys. what a coincidence, even on the same date, January 7th. I was browsing on chrome and it froze a second, rebooted and got stuck at the Google Logo. Official KitKat, not rooted.
Nothing works, wiping data via Recovery gives a tonne of "mount /x" errors and flashing through fastboot is impossible because it gets stuck trying to unlock the bootloader.
I, too, think it's a hardware issue, probably with the storage. The only difference is that I am in the very warm Venezuela, so I think the NYC cold wasn't the problem!
The sad thing is my uncle bought it for me in Italy a month back because prices here are ridiculous, so now it's going to be a bit of a problem to return it to Amazon.it :crying::crying:
If any of you find a solution please post it!
Sorry for any misspellings.
Febo00 said:
I'm on the same boat as you, guys. what a coincidence, even on the same date, January 7th. I was browsing on chrome and it froze a second, rebooted and got stuck at the Google Logo. Official KitKat, not rooted.
Nothing works, wiping data via Recovery gives a tonne of "mount /x" errors and flashing through fastboot is impossible because it gets stuck trying to unlock the bootloader.
I, too, think it's a hardware issue, probably with the storage. The only difference is that I am in the very warm Venezuela, so I think the NYC cold wasn't the problem!
The sad thing is my uncle bought it for me in Italy a month back because prices here are ridiculous, so now it's going to be a bit of a problem to return it to Amazon.it :crying::crying:
If any of you find a solution please post it!
Sorry for any misspellings.
Click to expand...
Click to collapse
I honestly don't think there is a solution. I just contacted ASUS support via their website and started a RMA warranty repair.
Can you take a picture with another phone or something of the errors?
Also, can you try to mount the partitions manually in recovery
or go into recovery with adb shell and try to mount the partitions manually.
Also, what recovery do you have?
vaughnsphotoart said:
I had been using my tablet normally and set it aside for a while. When I went back to it, it was stuck at the boot splash screen that is black with the white Google text on it. I tried rebooting several times and it would return to this state.
I booted into fastboot mode and went to recovery mode. The following errors were displayed at the bottom of the screen:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
I tried doing "wipe data/factory reset". It says:
-- Wiping data...
Formatting /data...
... and then goes into many more errors regarding failures mount/open /cache
Thinking maybe the cache partition was bad, I went back to fastboot mode and issued the following command from my pc:
fastboot format cache
... but the command never returns (after an hour, it had not returned, so I cancelled)
The same happens if I try
fastboot format userdata
... it never returns.
I can't unlock the bootloader to attempt to flash a new image. I can issue command
fastboot oem unlock
and get the correct screen, but selecting unlock just locks up the tablet. I left it this way for a couple hours, no change.
So to summarize: I can access fastboot, I can access recovery, but I can't seem to affect any change that will recover the system.
I've exhausted everything I know to try. Any thoughts?
It's ironic because I hack on these all the time at work, but this was my personal unit that was stock and unrooted.
Click to expand...
Click to collapse
mine also
Mine developed this same problem on January 5th while watching a video. I just sent it off for warranty yesterday (Thursday). Was anyone using ART. I know I was
latenighter49 said:
Mine developed this same problem on January 5th while watching a video. I just sent it off for warranty yesterday (Thursday). Was anyone using ART. I know I was
Click to expand...
Click to collapse
I was using Dalvik.
I had a similar issue as you guys therefore I decided to use the factory images to solve the issue. Be warned: using it will erase everything on your device. Photos, music etc.
If you do not mind, proceed on to download the factory images but please download the correct ones and put them into your fastboot folder which will contain these files:
api
image-razor-jss15q(unzipped file)
systrace
adb
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-flo-flo-03.14.img
fastboot
flash-all
flash-all.sh
image razor-jss15q (this is the zip file)
notice
source.properties
Once everything is all in there, open command window by left shirt and right click on your mouse and select command window and put your devices into fastboot and type into the command window: flash-all .bat
And it'll restore your device back to stock
---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------
Here's the link to the factory images for the Nexus 7 2013: https://developers.google.com/android/nexus/images#razor
Bobbi lim said:
I had a similar issue as you guys therefore I decided to use the factory images to solve the issue. Be warned: using it will erase everything on your device. Photos, music etc.
If you do not mind, proceed on to download the factory images but please download the correct ones and put them into your fastboot folder which will contain these files:
api
image-razor-jss15q(unzipped file)
systrace
adb
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-flo-flo-03.14.img
fastboot
flash-all
flash-all.sh
image razor-jss15q (this is the zip file)
notice
source.properties
Once everything is all in there, open command window by left shirt and right click on your mouse and select command window and put your devices into fastboot and type into the command window: flash-all .bat
And it'll restore your device back to stock
Click to expand...
Click to collapse
Hi, thanks for replying.
Correct me if I'm wrong, but you need to unlock the bootloader before flashing an image right? I tried it and it gets stuck trying to unlock it.
Code:
>fastboot oem unlock
<bootloader> Unlocking bootloader...
<bootloader> erasing userdata...
It got stuck trying to erase the data. Whic would be similar to the errors on recovery where it couldn't access the storage.
Febo00 said:
Hi, thanks for replying.
Correct me if I'm wrong, but you need to unlock the bootloader before flashing an image right? I tried it and it gets stuck trying to unlock it.
Code:
>fastboot oem unlock
<bootloader> Unlocking bootloader...
<bootloader> erasing userdata...
It got stuck trying to erase the data. Whic would be similar to the errors on recovery where it couldn't access the storage.
Click to expand...
Click to collapse
You are correct, flashing anything requires unlocking the bootloader. You aren't the only one who's getting stuck at unlocking, which could be a corrupted bootloader or a bad eMMC. I've never heard of solutions except to call for warranty repair.
Hy,
Today, i've the same issue. Nothing to do, i tried a lot of things like you.
Can't wipe cache or data, always failed to mount /cache.
My nexus was on stock rom locked, no root.
I'll go to the store, hope they can repair or change it quickly.
Lexso
Same here in middle east.
I also saw similar post several days ago.
http://forum.xda-developers.com/showthread.php?t=2644981
Anyway, I have exact the same symptom as you guys; locked bootloader and couldn't pass that stage.
I sent it to dubai for a RMA. Hope they will fix it and send it back to me ASAP.
Exactly the same thing just happened to me right now. The tablet restarted itself and do not pass the Google Logo. I did not unlock or whatever else my tablet.
In fact a week go i got a system update and since, my tablet is freezing or restarting without reasons. But that time it is for good. Is the ASUS warranty international ? Cause I bought my tablet in France (I am french) but I am living in Czech Republic.
donatien said:
Exactly the same thing just happened to me right now. The tablet restarted itself and do not pass the Google Logo. I did not unlock or whatever else my tablet.
In fact a week go i got a system update and since, my tablet is freezing or restarting without reasons. But that time it is for good. Is the ASUS warranty international ? Cause I bought my tablet in France (I am french) but I am living in Czech Republic.
Click to expand...
Click to collapse
Yes, it is global warranty. There must be a ASUS local service partner in Czech Republic.
Contact http://vip.asus.com/VIP2/Services/QuestionForm/TechQuery
and the customer service will let you know where you should contact.
I bought my N7 at Italy, but I'm fixing it in middle east.
You try unlocking its bootloader manually and don't use and program to do so
---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------
If you return the device back for warranty , you'll come back with a reconditioned device.
So I'm hoping that you try unlocking its bootloader manually yourself.
Boot the nexus into fastboot and type into fastboot (cmd) : fastboot oem unlock
Than it'll unlock the device than use the factory images with the links I provided earlier to flash them
Are you adverse to completely wiping it?
If you aren't then maybe hard reset it, fastboot oem unlock, and then flash it with Kit-Kat?
With all the buzz about Android 5.0 lately I hastily decided to flash across the latest and greatest. So of course it turned out I needed S-Off for something (because it never gets to be easy) so after running various hacks in an attempt to get S-Off I noticed that I couldn't boot into Android. So I opened up the recovery and tried to sideload across a stock HTC KitKat ROM. When I turned on the sideloading function I got the following error: "failed to open driver control: No such file or directory". And this wasn't the first or last error that I would get. for example, if I tried to access my /sdcard partition I would receive the error message: "E: Can't mount /sdcard". To me this seems like either my partitions have been deleted or corrupted.
Other directories I also cannot mount are:
/data
/firmware/radio
/firmware/adsp
/firmware/wcnss
/sd-ext
Note: I am running PhilZ touch as my recovery.
Hi,
I think you should try to upgrade your bootloader with a Lollipop compatible one (4.16.1540.8 for example).
Maybe during the upgrade the partitions will be recreated.
john_matrix said:
Hi,
I think you should try to upgrade your bootloader with a Lollipop compatible one (4.16.1540.8 for example).
Maybe during the upgrade the partitions will be recreated.
Click to expand...
Click to collapse
Wouldn't this require me to have S-Off? Which is the problem in the first place, when I tried to get S-Off I bricked my phone.
But did you have S-OFF now?
So I received an update for the phone and figured it should be ok given that it's a security update, first one in ages for HTC One m8 and my phone got stuck in boot screen. As I understand it this is what happens as a result of Lollipop and a rooted device, binary and all that rubbish. This I knew AFTER doing the update. Honestly didn't think it would be a problem with an official update but ok...
So this is how it went thus far.
Tried installing back older firmware - nothing.
Tried to RUU but can't, doesn't detect my phone.
Can't even install HTC MTP driver on windows, error code 10...
Device has been fully wiped.
Tried to put the ruu in .zip form on SD card 0p6bimg etc, SDCard it claimed was damaged and needed to be formatted. SDCard is wiped completely.
Stuck in boot screen, no way to flash custom recovery, custom rom etc as my device cannot be detected.
I've been trying to do the usual for close to 10 hours now that I've been busy with this phone and I'm about 1 minute away from thrashing this P.O.S to pieces against a wall. Before that happens I figured I might as well come on here and ask for anymore suggestions.
Thank you.
Additional details about phone: S-OFF, Originally used to be HTC_203 EU device, converted it to Developer Edition. MID/CID are still correct, never changed that after the initial conversion.
Don't know if it's of any relevance or not but in recovery screen(stock recovery of course) it shows following message at the bottom:
E : missing bitmap oem_unlock_bg
(Code -1)
E : missing bitmap oem_unlock_bg_yes
(Code -1)
E : missing bitmap oem_unlock_bg_no
(Code -1)
Hey old mate !
That's normal in stock recovery but what is written after those line is important for the error reading.
Have you tried to use a card reader to read your microSD ? Or you use that mount with TWRP ?
Which RUU.zip ? Is it the ROM.zip that you got from TEMP folder on PC ?
ckpv5 said:
Hey old mate !
That's normal in stock recovery but what is written after those line is important for the error reading.
Have you tried to use a card reader to read your microSD ? Or you use that mount with TWRP ?
Which RUU.zip ? Is it the ROM.zip that you got from TEMP folder on PC ?
Click to expand...
Click to collapse
It was ROM.zip from temp folder yes. I sorted the issue out though, for one or other reason it read the rom.zip after a huge struggle. I tried it at least 7 times and for some reason it took on the 8th, not that anything changed at all. It was the same .zip renamed to 0p6bimg.zip, don't know what changed to have it work after so many tries. The only real thing that "changed" was my frustration in it and I ended up hitting the phone against the desk Yes...it picked up physical damage on the side too, right by the volume buttons it "bent" out a bit :crying:
So the phone is working again but not very happy lol I lost all my data I had on my phone, lost all the data I had on my sdcard... Physical damage of course.
First OTA in ages and this is the nonsense a person has to deal with. Honestly I didn't expect it to give this problem as I haven't been to the forums in ages I didn't read up on this issue. Thought it would be fine lol. Quite disappointed but what can you do.
Hi, maybe your SD card has reached the end of its life? How old is it? Phone said it was damaged and then took a really long time to read.
Could be time for the 128gb upgrade...
As the title says. I tried to go back to stock and got stuck. I was new, and still am to this whole thing to a degree. I had a friend who helped me unlock, root, and slap on a custom rom. I learned about it in the process, but here is my problem. I tried to go back to stock, and locked my bootloader before I slapped on the stock rom. And I wiped the phone, cache, and dalvik etc.. well the OS is gone too. I would like to be able to use my SD card to load the stock rom but it wont read the Ext sd card. Brand new, 3rd diff card. I tried to use adb, but it wont see the device in the command prompt. I have the sdk dev installed and universal adb drivers as well as htc sync. I've rebooted multiple times to make sure drivers are useful. The apk installer can see my phone, adb commands do NOT. So for the moment my m9 is a paper weight, I've tried to read and follow the searches I've run across on here but I seem to be stuck. Phone boots, and stops at the white boot screen. I am S-ON and relocked.
This is the info it shows me
Radio-1.11
OS 1.32.651.30
When I reboot it goes into a white screen. gives options to reboot into bootloader, reboot to recovery etc... If I reboot to recovery it shows it is missing items
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
handle_cota_install: install cwpkg to /data/cwtemp/cwpg.zip
handle_cota_install: install cwprop to /data/data/cwtemp/cwprop
E: fail to open file: /sys/devices/platform/android_usb/hostmode
Write host_mode error
handle_cota_install: No CW files. Skip installation
I can't access my drive on the phone to store files, the only thing I can use is my sd card since adb wont see devices. And my phone wont read from the SD card ( Tried 3 diff ones ). And if I goto apply from sd card I get
E: Find no match PARTITION: for package path /sdcard/ptt.zip
E: Unknown volume for path []
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package....
E: Failed to map file
-----------
But if I goto download mode, the pc will see the phone though APK Installer through taskbar notification. But not adb.:silly:
Sorry if I caused some of you do go "Seriously dude??!!" This is a headache, this I do know. I just want to either get this phone working again through stock ) Right now it's just a bunch of load up to bootloader screen and stop. No OS. And once again, wont read rom from sd card, wont even see sd. Says it can't access it.
And if I goto recovery mode it tells me that same junk about No CW files. skip installation. Am I as screwed as it sounds?
aimjewels said:
As the title says. I tried to go back to stock and got stuck. I was new, and still am to this whole thing to a degree. I had a friend who helped me unlock, root, and slap on a custom rom. I learned about it in the process, but here is my problem. I tried to go back to stock, and locked my bootloader before I slapped on the stock rom. And I wiped the phone, cache, and dalvik etc.. well the OS is gone too. I would like to be able to use my SD card to load the stock rom but it wont read the Ext sd card. Brand new, 3rd diff card. I tried to use adb, but it wont see the device in the command prompt. I have the sdk dev installed and universal adb drivers as well as htc sync. I've rebooted multiple times to make sure drivers are useful. The apk installer can see my phone, adb commands do NOT. So for the moment my m9 is a paper weight, I've tried to read and follow the searches I've run across on here but I seem to be stuck. Phone boots, and stops at the white boot screen. I am S-ON and relocked.
This is the info it shows me
Radio-1.11
OS 1.32.651.30
When I reboot it goes into a white screen. gives options to reboot into bootloader, reboot to recovery etc... If I reboot to recovery it shows it is missing items
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
handle_cota_install: install cwpkg to /data/cwtemp/cwpg.zip
handle_cota_install: install cwprop to /data/data/cwtemp/cwprop
E: fail to open file: /sys/devices/platform/android_usb/hostmode
Write host_mode error
handle_cota_install: No CW files. Skip installation
I can't access my drive on the phone to store files, the only thing I can use is my sd card since adb wont see devices. And my phone wont read from the SD card ( Tried 3 diff ones ). And if I goto apply from sd card I get
E: Find no match PARTITION: for package path /sdcard/ptt.zip
E: Unknown volume for path []
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package....
E: Failed to map file
-----------
But if I goto download mode, the pc will see the phone though APK Installer through taskbar notification. But not adb.:silly:
Sorry if I caused some of you do go "Seriously dude??!!" This is a headache, this I do know. I just want to either get this phone working again through stock ) Right now it's just a bunch of load up to bootloader screen and stop. No OS. And once again, wont read rom from sd card, wont even see sd. Says it can't access it.
And if I goto recovery mode it tells me that same junk about No CW files. skip installation. Am I as screwed as it sounds?
Click to expand...
Click to collapse
Use the full 1.32.651.30 RUU here
(originally from this thread)
I highly recommend you use the 1.32.651.30 one and NOT the newer 2.xx ones, because in the 2.x.xxx.x ones, (Android 5.1), a new setting has been implemented "Settings -> Developer Options -> OEM unlocking", if that is not checked, and it's not by default (and this can only be done during the booted ROM), you will not be able to unlock your bootloader again!! (so be careful!!)
EDIT: oh, and as far as I know, the M9 (unlike it's predecessors) doesnt need a relocked bootloader for RUU, even with S-ON
nkk71 said:
Use the full 1.32.651.30 RUU here
(originally from this thread)
I highly recommend you use the 1.32.651.30 one and NOT the newer 2.xx ones, because in the 2.x.xxx.x ones, (Android 5.1), a new setting has been implemented "Settings -> Developer Options -> OEM unlocking", if that is not checked, and it's not by default (and this can only be done during the booted ROM), you will not be able to unlock your bootloader again!! (so be careful!!)
EDIT: oh, and as far as I know, the M9 (unlike it's predecessors) doesnt need a relocked bootloader for RUU, even with S-ON
Click to expand...
Click to collapse
Well now the problem is that everything goes fine up until it comes time to update the rom. I get an error code of 155 an unknown error. It tells me to use the correct ROM Utility and try again. But This is the correct one I'm using. I am a bit confused now. I have tried even reinstalling some drivers and such all over again just to make sure. And rebooted. It gives an error on the same part every time. It doesn't even get to Step 2/4
But on the plus side it does still respond to the reboot to bootloader command. The screen the phone gets stuck on otherwise...is the install screen. The arrows are not spinning and the progress bar has no progress. That is usually when I get a fastboot.exe error