Hello,
I saw on the htc site that an update for the Sprint HTC touch was available so i downloaded it and tried to load it on my phone.
It took a few tries to get it to connect and when it finally did it said there was an invalid command.
I thought it was because i upgraded my phone earlier to the titan rom and radio to get gps and rev a so i put it back to the factory settings.
Everything was normal.
I then tried the official htc software update again and it worked until it got to 10% and it said invalid command again and exited.
It is now stuck on the boot load screen and remains that way after numerous soft/hard resets.
To "unbrick" your phone, follow the steps in this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
In a nutshell:
You'll have to revert back to your carrier's ROM (by carrier, I mean a genuine, signed ROM) by extracting the ROM's exe file and renaming the .nbh file inside the archive to VOGUIMG.nbh.
Then, remove your Micro SD card and use a card reader** to put that file into the root - ensure that the card is formatted as FAT32 and that the card is not an SDHC (meaning any card that is 4GB+().
**card reader or any other device that has a microSD slot that operates as a USB mass storage device - I did the same procedure with an MP3 player... **
Insert the card and reboot the phone, it should go into the bootloader and update automatically.
Good luck
If you can get to the boot screen, chances are it is not bricked
Just download the original ROM and flash to that. Make sure to NOT use a virtual machine! You can only run the .EXE file in Windows XP natively, not in software such as Parallels or VM Ware.
TGHI said:
To "unbrick" your phone, follow the steps in this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
In a nutshell:
You'll have to revert back to your carrier's ROM (by carrier, I mean a genuine, signed ROM) by extracting the ROM's exe file and renaming the .nbh file inside the archive to VOGUIMG.nbh.
Then, remove your Micro SD card and use a card reader** to put that file into the root - ensure that the card is formatted as FAT32 and that the card is not an SDHC (meaning any card that is 4GB+().
**card reader or any other device that has a microSD slot that operates as a USB mass storage device - I did the same procedure with an MP3 player... **
Insert the card and reboot the phone, it should go into the bootloader and update automatically.
Good luck
Click to expand...
Click to collapse
I tried this maybe 5 times and i keep getting a communication error!
bpack428 said:
I tried this maybe 5 times and i keep getting a communication error!
Click to expand...
Click to collapse
If you are getting a communication error while trying to flash from the sd card, you've got some very serious problems. More than likely, if you are flashing from sd and get an error, it is probably not a communications error.
What letters are on the three-color boot-loader screen?
Best regards,
-boggsie
boggsie said:
If you are getting a communication error while trying to flash from the sd card, you've got some very serious problems. More than likely, if you are flashing from sd and get an error, it is probably not a communications error.
What letters are on the three-color boot-loader screen?
Best regards,
-boggsie
Click to expand...
Click to collapse
VOGU100 MFG
SPL-2.01.1000
CPLD-3
in the top right corner it says RUUNBH
bottom it says serial
I think im going to play dumb and get a new phone from sprint.
bpack428 said:
I think im going to play dumb and get a new phone from sprint.
Click to expand...
Click to collapse
This is a pretty simple fix. You need to stick your MicroSD card into your PC via card reader. Format the card to fat32. Re-Formating is important because even if your card is already fat 32 sometimes it still won't work until your re-format it. Then copy "any" compatible Vogue RUU file over to your card. Rename the file "VOGUIMG" without the quotes and stick it back into your phone in the root directory.. Hold down the power and camera button and reset the phone with the stylus. Once inside the bootloader follow the instructions on your screen. Reset when you are done and you should be good. THIS IS ASSUMING YOUR PHONE IS ALREADY UNLOCKED. If you go back to Sprint and they see why your phone isn't booting they may not honor your warranty.
GOOD LUCK....
ptfdmedic said:
This is a pretty simple fix. You need to stick your MicroSD card into your PC via card reader. Format the card to fat32. The copy "any" compatible Vogue RUU file over to yourt card. Rename the file "VOGUIMG" without the quotes and stick it back into your phone. Hold down the power and camera button and rested the phone with the stylus. Once inside the bootloader follow the instructions on your screen. Reset when you are done and you should be good. THIS IS ASSUMING YOUR PHONE IS ALREADY UNLOCKED. If you go back to Sprint and they see why your phone isn't booting they may not honor your warranty.
GOOD LUCK....
Click to expand...
Click to collapse
I have done this. It says loading... on my phone and then i try to load RUU_Vogue_SPRINT_WWE_1.12.651.1_2.13.00_SPC_NV133_Ship on my phone from my pc and i get a communication error
bpack428 said:
I have done this. It says loading... on my phone and then i try to load RUU_Vogue_SPRINT_WWE_1.12.651.1_2.13.00_SPC_NV133_Ship on my phone from my pc and i get a communication error
Click to expand...
Click to collapse
Let me clarify. Use any "Compatible" "Custom" Rom. I don't believe the Sprint Release off the HTC site will work with what you are doing. You need a Custom Rom.
I would suggest you visit: http://forum.ppcgeeks.com/forumdisplay.php?f=59
and just pick one and follow the instructions I gave eariler. I don't believe you can do this type of upgrade with the Sprint ROM you need to try with a custom ROM....
MAKE SURE YOUR PHONE IS UNLOCKED....
ptfdmedic said:
Let me clarify. Use any "Compatible" "Custom" Rom. I don't believe the Sprint Release off the HTC site will work with what you are doing. You need a Custom Rom.
I would suggest you visit: http://forum.ppcgeeks.com/forumdisplay.php?f=59
and just pick one and follow the instructions I gave eariler. I don't believe you can do this type of upgrade with the Sprint ROM you need to try with a custom ROM....
MAKE SURE YOUR PHONE IS UNLOCKED....
Click to expand...
Click to collapse
How do i know if my phone is unlocked?
All that i want to do it update it to the official htc rom
bpack428 said:
How do i know if my phone is unlocked?
All that i want to do it update it to the official htc rom
Click to expand...
Click to collapse
Have you ever loaded a custom ROM?... You said you loaded a Titan ROM? I believe you had to have your phone unlocked for that and that was just for the Radio and it was not a full OS flash. So if you did that then hopefully your phone is unlocked.
If your phone is unlocked you will see the following on you bootloader:
VOGU100 MFG
SPL-2.31.Coke
CPLD-3
What do you have listed.
Let me know and maybe I can help.
He posted the information earlier in the thread:
VOGU100 MFG
SPL-2.01.1000
CPLD-3
Click to expand...
Click to collapse
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie
boggsie said:
He posted the information earlier in the thread:
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie
Click to expand...
Click to collapse
I have no idea if i can or cannot do that.
boggsie said:
He posted the information earlier in the thread:
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie
Click to expand...
Click to collapse
Hye Boggsie,
Didn't COKE release a version of his unlocker that was flashable via SD card. I know that I flashed extracted the .nbh from the .exe and renamed it and flashed. It worked but I only did this because I running Vista 64 and couldn't get it to work from Vista. I will look and see if I can remember how I did it. The op said he flashed a titan rom to get the radio or something. I would guess that might play a part in this.
I agree that the Sprint.exe would be his only option but I will see if I can locate what I did. That may also work........
Thanks for the reply...
Here is the link to the 2.31 unlocker: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker_MFG_2.31.exe
Here is the link to the thread over on PPCGEEKS:
http://forum.ppcgeeks.com/showthread.php?t=20370
What I did was to extract the .nbh and rename it to VOGUIMG. I flashed that from my SD card and unlocked my phone. I don't believe this is a supported method. I don't know how good of an idea it is. But it seems that you have tried everything else already. I would READ the thread VERY CAREFULLY before deciding to try this. I Must be VERY CLEAR. DO THIS AT YOUR OWN RISK. AGAIN READ THE INSTRUCTIONS IN THE THREAD FIRST. I only did this because when I was newer I made a mistake and found myself in a similar position as you. I knew my phone was dead and figured I had nothing left to lose. I take no responsibility for this as I am sharing information that I have from my own experience. I don't think that this is really suppossed to work but it did for me. It has been a while since I fixed mine, and I have flashed to many times to remember. So I am reasonably sure this is what I did.
Good Luck......
Update:
Read this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
This should help you fix this.
UPDATE 2:
Rename the .nbh to VOGUIMG not VOGUIMG.nbh the .nbh is the file extension and not part of the renaming process. If you include .nbh in the name it will not work.....
OK. GOOD LUCK
ptfdmedic said:
Hye Boggsie,
Didn't COKE release a version of his unlocker that was flashable via SD card. I know that I flashed extracted the .nbh from the .exe and renamed it and flashed. It worked but I only did this because I running Vista 64 and couldn't get it to work from Vista. I will look and see if I can remember how I did it. The op said he flashed a titan rom to get the radio or something. I would guess that might play a part in this.
I agree that the Sprint.exe would be his only option but I will see if I can locate what I did. That may also work........
Thanks for the reply...
Click to expand...
Click to collapse
He did, but only for the Titan or Kaiser ... probably the Titan.
AFAIK, he doesn't have a replacement Vogue, yet.
Best regards,
-boggsie
boggsie said:
He did, but only for the Titan or Kaiser ... probably the Titan.
AFAIK, he doesn't have a replacement Vogue, yet.
Best regards,
-boggsie
Click to expand...
Click to collapse
Hey I took the plunge.
I relocked and and then unlocked right from my sd card. It does work. Only recommended if there is no other way. But it does work. It is just like flashing a custom rom from your sd card but it only takes a few seconds.....
ptfdmedic said:
Hey I took the plunge.
I relocked and and then unlocked right from my sd card. It does work. Only recommended if there is no other way. But it does work. It is just like flashing a custom rom from your sd card but it only takes a few seconds.....
Click to expand...
Click to collapse
Wow ... a bit of a gutsy move; yours are bigger than mine, my friend.
Although, I wonder why / how it works? I mean, flashing a bootloader from SD is facilitated through the existing bootloader. So the existing bootloader is being overwrittern by the new bootloader, but the existing bootloader is performing the write / update process, so how can it possibly be overwritten?
This is why the bootloader process from the pc needs activesync; so that a temporary bootloader can be run in memory and then used to write the new bootloader over top of the existing one.
Oh well, who cares why I can't understand it ... it works. Good find!
Best regards,
-boggsie
boggsie said:
Wow ... a bit of a gutsy move; yours are bigger than mine, my friend.
Although, I wonder why / how it works? I mean, flashing a bootloader from SD is facilitated through the existing bootloader. So the existing bootloader is being overwrittern by the new bootloader, but the existing bootloader is performing the write / update process, so how can it possibly be overwritten?
This is why the bootloader process from the pc needs activesync; so that a temporary bootloader can be run in memory and then used to write the new bootloader over top of the existing one.
Oh well, who cares why I can't understand it ... it works. Good find!
Best regards,
-boggsie
Click to expand...
Click to collapse
Boggsie,
Check out this thread. It explains it all.
http://forum.ppcgeeks.com/showthread.php?t=24906
I agree it shouldn't work. But it does. Coke says it should be a last resort. But is actually works....
Related
Can anyone show how to flash through SD card my Blue Angel please...from wm03 to wm06? I was searching on wiki but there says nothignn about SD CARD... Can anyone simply show me how to do that? Which ROM to install and that stuff... MANY THANKS
never heard before flashing BA from SD,
Sorry...
i dont have cabel for connecting with PC :-(... and here i Serbia i cant buy a new one so i will never install WM06 :-(... Any HELP
At this point, your only options are:
find a cable if you want to flash the phone
send it to someone who has a cable so they can flash it for you and send it back
Hard reset
In case you have a preproduction HERMES and you can not update the ROM (due to the fact that your bootloader is <1.04) here the very easy solution:
***info removed, wrong device or mis-informed***
This also works for normal (non preproduction) devices but keep in mind that if the CID does not match the flashing might not work.
gully321 said:
In case you have a preproduction HERMES and you can not update the ROM (due to the fact that your bootloader is <1.04) here the very easy solution:
***info removed, wrong device or mis-informed***
This also works for normal (non preproduction) devices but keep in mind that if the CID does not match the flashing might not work.
Click to expand...
Click to collapse
man, you really misposted this......this is for hermes,, should'nt work at all on blueangel
hfzarx said:
man, you really misposted this......this is for hermes,, should'nt work at all on blueangel
Click to expand...
Click to collapse
This thread was back in 2008...was there any real need to reply to a 2 year old thread...probably not?
Hi.
i was updating my htc touch pro 2 (sprint),Ever thing was going fine and it stuck at 0%
i saw error on my desktop computer (FLASH WRITE ERROR)
so i do a soft reset
all i got now is 3 color screen
NEED HELP TO AGAIN MAKE IT WORK
Sorry for my bad english
THANKS ,
WAITING FOR REPLY
What are you trying to flash?
Are you doing it via SD or via PC? I would assume via PC since you got an error on your PC...
Can you try flashing via SD?
Did you unlock your phone? Did you try to load the stock rom?
You can probably just put the stock rom on the sd card, and load from there.
REPLY
i was updating not flashing
i thing my phone is already unlock i am using it in Pakistan
i try from PC to update
what is SD method and where to find stock rom ?
THANKS FOR THE QUICK RESPONCE
sufian9647 said:
i was updating not flashing
i thing my phone is already unlock i am using it in Pakistan
i try from PC to update
what is SD method and where to find stock rom ?
THANKS FOR THE QUICK RESPONCE
Click to expand...
Click to collapse
Oh, I see... in Pakistan means your phone is unlocked...
You were updating, not flashing....
How silly of me....:silly:
Sigh....
http://forum.xda-developers.com/showthread.php?t=550691
Do i need to do hard-spl
where to find ROM and what mean by root of SD CARD
My phone is already at 3 color screen as u know so do i have to enter boot loader by manual ?
THANKS FOR QUICK RESPONSE :good:
sufian9647 said:
Do i need to do hard-spl
where to find ROM and what mean by root of SD CARD
My phone is already at 3 color screen as u know so do i have to enter boot loader by manual ?
THANKS FOR QUICK RESPONSE :good:
Click to expand...
Click to collapse
What ROM were you flashing before? Just use that one.
wizardknight, look at the screenshot... he's already HSPL'd.
Root of SD card == no folders. 0 folders. Just put the file on the SD card. Not within a FOLDER.
RUU_Rhodium_S2_HTC_Europe_2.07.401.1_Radio_Rhodium_4.49.25.91_Signed_Ship
is the name of file which i use to update ,but its a computer file,how can i use it by putting in SD CARD ?
its a application file,i cant ever extract it
arrrghhh said:
wizardknight, look at the screenshot... he's already HSPL'd.
Click to expand...
Click to collapse
Never said he wasn't.I said the physical location of the phone had no relevance to the locked or unlocked state of the phone.
That would like saying cars can only go fast if they are in France. Completely illogical.
.
---------- Post added at 07:18 PM ---------- Previous post was at 07:18 PM ----------
sufian9647 said:
RUU_Rhodium_S2_HTC_Europe_2.07.401.1_Radio_Rhodium_4.49.25.91_Signed_Ship
is the name of file which i use to update ,but its a computer file,how can i use it by putting in SD CARD ?
its a application file,i cant ever extract it
Click to expand...
Click to collapse
Try 7zip. It will open almost any container file.
i rename the file ruu_signed.nbh to rhodimg.nbh
and put it in SD card root
and start the boot loader
i push the power button to install the update
but got ERROR
SEE THE ATTACHED PIC TO SEE ERROR
sufian9647 said:
i rename the file ruu_signed.nbh to rhodimg.nbh
and put it in SD card root
and start the boot loader
i push the power button to install the update
but got ERROR
SEE THE ATTACHED PIC TO SEE ERROR
Click to expand...
Click to collapse
Hm, it's trying to flash the bootloader... What ROM is this you are trying to flash? It might be a stock ROM which is not appropriate for your device...
wizardknight said:
Never said he wasn't.I said the physical location of the phone had no relevance to the locked or unlocked state of the phone.
That would like saying cars can only go fast if they are in France. Completely illogical.
Click to expand...
Click to collapse
I don't think logic has anything to do with this.... I don't think it ever did my friend, lol.
my mobile is of sprint,i think at start of this thread i put image of my mobile
RUU_Rhodium_S2_HTC_Europe_2.07.401.1_Radio_Rhodium _4.49.25.91_Signed_Ship
this is the file which i downloaded from htc website
i extract it with zip 7
direct me to the link of rom which can work on my device
If this is a Sprint RHOD. Then it should be a Rhod400.
Your screenshot does not show RHOD400.
If it is a sprint RHOD400, then this thread has CDMA wm roms in it.
http://forum.xda-developers.com/showthread.php?t=686903
on my touch pro 2 there in no logo of sprint
but when i power on it display the sprint logo
my question is that is my phone have sprint rom ?
and in pakistan ppcgeek website in block,so i cant access it
u have see the condition of my mobile before and after updating through SD card method also
in my attachment images
did u notice during updating from SD card method it give BOOT LOADER - ERROR
plz help me ,my phone is in this condition almost 1 month
You don't know what kind of phone you have for sure, you don't know what rom was on it for sure, you don't know what rom should be on it, you can't download roms, and you are about 5000 miles away. What do you want us to do?
Go find a repair shop. We can't help you.
i am using touch pro 2
it have sprint ROM Wm 6.5
i have recently downloaded ROM but it give BOOT LOADER ERROR
should i try other ROM also
what can be the cause of BOOT LOADER ERROR,is it due to wrong ROM VERSION ?
I HAVE CONSULTED 2 repair shop they keep my mobile for a week and then return it,
because in Pakistan we have shortage of electricity,so repair shop cant give time to my mobile.
sufian9647 said:
i am using touch pro 2
it have sprint ROM Wm 6.5
i have recently downloaded ROM but it give BOOT LOADER ERROR
should i try other ROM also
what can be the cause of BOOT LOADER ERROR,is it due to wrong ROM VERSION ?
I HAVE CONSULTED 2 repair shop they keep my mobile for a week and then return it,
because in Pakistan we have shortage of electricity,so repair shop cant give time to my mobile.
Click to expand...
Click to collapse
You still have not told us what phone you have. There are at least 5 types of touch pro 2s + some knock off ones.
Sprint rom WM 6.5 does not tell us what rom you are running,
If you downloaded a rom amd it gave you boot loader error, then it must not work on your phone.
I suggest that you find another repair shop that will be able to fix your phone in less than a week, or just buy a new phone.
Good luck. You are going to need it.
i will try next 24 hour to make it run
i will try ROM from the link
http://forum.xda-developers.com/showthread.php?t=686903
but if still failed i will find better repair shop
when i try to download a ROM it give me error
(The file link that you requested is not valid.)
WHAT SHOULD I DO
waiting for your response
THANKS
sufian9647 said:
when i try to download a ROM it give me error
(The file link that you requested is not valid.)
WHAT SHOULD I DO
waiting for your response
THANKS
Click to expand...
Click to collapse
Download another ROM/find another link?
This device is getting quite old now, so it will become infinitely more difficult to find the appropriate files, with valid links.
Good luck.
hi everyone, add me to the list of idiots that shouldn't be doing things like this...
i bought an xtc2clip and should have stopped there, without using it. i had trouble writing files to the chip through their software (latest 1.18). but while poking around, i got s-off. so far so good. when i tried to copy the files over to unlock the bootloader, it kept giving me an error, so i gave up on the xtc2clip (yes, i changed the ribbon cable many times...).
so just after getting s-off, i was able to install TWRP through fastboot. keep in mind, my phone was still s-off, but bootloader locked. i booted TWRP several times just to check things out... all seemed OK.
i then installed SuperSU, using TWRP. i downloaded the 2.46 zip, placed it on my SD card and installed from within TWRP.
i rebooted, and the phone hung on the red verizon screen... i left it like that for at least ten minutes. i was able to reboot through adb, but it never progressed beyond the red verizon screen.
i did some reading, and found other users in a similar state flashed a new ROM to get around that. i then flashed adnybones' Stock Deodexed *Official* -- 3.10.605.7 i found here on XDA.
now - my phone had updated to the latest firmware - so per andybones' instructions, i flashed the 3.10.605.7 linked from his howto.
the flash went OK. i installed the ROM, that seemed to go OK. i rebooted and observed different boot animation - that was a good sign. then the phone hung for over 10 minutes again, never loading the OS.
now, i can reboot to fastboot or download, but cannot boot the OS. the phone goes immediately to fastboot, and will not boot to recovery. it will boot to download, but not recovery...
so i can't get into TWRP and i can't get into the OS.
help?!?!??!?
I have actually used the clip to s-off a VZW M9. It wasn't able to unlock the bootloader at the time, but I was able to flash TWRP and install SU on the stock OS. I then used the shell command to unlock the bootloader.
You stated that your bootloader was never unlocked, and you flashed a custom rom. If that is the case then you need to unlock the bootloader and reflash your custom rom. You will probably need to flash the same VZW stock rom you had prior to flashing a custom rom.
Here is the link to unlocking the bootloader if you are s-off:
http://forum.xda-developers.com/showthread.php?t=3092036
[how to] lock/unlock your bootloader without htcdev(s-off required)
Doesn't the clip now support unlocking VZW M9? Update the xtc software and try again maybe?
If not you will need to flash a stock rom, install SU, and follow the instructions from the link above for unlocking. Once you are unlocked you can start flashing roms.
This is all based on the assumption that your bootloader is locked.
If I misunderstood or you are actually unlocked and forgot to mention it, please disregard everything above.
Sent from my HTC One_M8 using XDA Free mobile app
c5satellite2 said:
I have actually used the clip to s-off a VZW M9. It wasn't able to unlock the bootloader at the time, but I was able to flash TWRP and install SU on the stock OS. I then used the shell command to unlock the bootloader.
You stated that your bootloader was never unlocked, and you flashed a custom rom. If that is the case then you need to unlock the bootloader and reflash your custom rom. You will probably need to flash the same VZW stock rom you had prior to flashing a custom rom.
Click to expand...
Click to collapse
the xtc2clip has two methods to unlock the bootloader. neither will work for me... the "bootloader unlock" tab throws an error when i try to copy the files over the the sd card (i've tried multiple cables and repeated many, many times - something isn't right with this hardware). the newer method, in the "special unlock" tab appears to work, but my phone did nothing after booting with the card installed. and yes, i've seen the other discussions, videos and pics of how to install the sd card. i was able to verify the phone sees the card in the OS, and i'm using the sdcard cradle that came with the phone.
the bootloader status consistently read *** LOCKED *** - so there is no doubt about it.
c5satellite2 said:
Here is the link to unlocking the bootloader if you are s-off:
http://forum.xda-developers.com/showthread.php?t=3092036
[how to] lock/unlock your bootloader without htcdev(s-off required)
Click to expand...
Click to collapse
yes - the problem is that i need root in order to follow those... the problem started after flashing SuperSU. i cannot follow that guide unless i have SU working and an adb shell open to the phone. installing SuperSU is what landed my in fastboot-only land.
c5satellite2 said:
Doesn't the clip now support unlocking VZW M9? Update the xtc software and try again maybe?
If not you will need to flash a stock rom, install SU, and follow the instructions from the link above for unlocking. Once you are unlocked you can start flashing roms.
Click to expand...
Click to collapse
xtc2clip says it does, and i'm certain people can use it to do so... but i've only gotten errors when it tries to write to the sd card. i have manually copied files to the sdcard in the xtc2clip - that's how i got s-off and supercid. i've had nothing but problems trying to use the xtc2clip, and now with s-off, i'm hoping there is a simpler way to do this through adb / fastboot shell. is there?
c5satellite2 said:
This is all based on the assumption that your bootloader is locked.
If I misunderstood or you are actually unlocked and forgot to mention it, please disregard everything above.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
yeah - that's all correct. bootloader is locked, s-off, will boot only to fastboot.
where is the original ROM that came with this phone?? i'll try reflashing that...
pwhitt said:
the xtc2clip has two methods to unlock the bootloader. neither will work for me... the "bootloader unlock" tab throws an error when i try to copy the files over the the sd card (i've tried multiple cables and repeated many, many times - something isn't right with this hardware). the newer method, in the "special unlock" tab appears to work, but my phone did nothing after booting with the card installed. and yes, i've seen the other discussions, videos and pics of how to install the sd card. i was able to verify the phone sees the card in the OS, and i'm using the sdcard cradle that came with the phone.
the bootloader status consistently read *** LOCKED *** - so there is no doubt about it.
yes - the problem is that i need root in order to follow those... the problem started after flashing SuperSU. i cannot follow that guide unless i have SU working and an adb shell open to the phone. installing SuperSU is what landed my in fastboot-only land.
xtc2clip says it does, and i'm certain people can use it to do so... but i've only gotten errors when it tries to write to the sd card. i have manually copied files to the sdcard in the xtc2clip - that's how i got s-off and supercid. i've had nothing but problems trying to use the xtc2clip, and now with s-off, i'm hoping there is a simpler way to do this through adb / fastboot shell. is there?
yeah - that's all correct. bootloader is locked, s-off, will boot only to fastboot.
where is the original ROM that came with this phone?? i'll try reflashing that...
Click to expand...
Click to collapse
Follow this
:http://forum.xda-developers.com/verizon-one-m9/general/ruu-vzw-3-10-605-7-0pjaimg-signed-t3277629
Mr Troop said:
Follow this
:http://forum.xda-developers.com/verizon-one-m9/general/ruu-vzw-3-10-605-7-0pjaimg-signed-t3277629
Click to expand...
Click to collapse
well... i did everything to the letter, and the phone doesn't install the image. in download mode, the phone displays a message at the bottom that the sd card isn't mounted. i tried to check the sd card from within download mode, and it displayed something about smart sd card not found, or something similar.
the sd card is formatted exFat, so maybe i need to format it fat32? it's a 128gb card, i can try again with an 8gb fat32, but i thought exFat was supported...
for the record, i did everything to the letter - even copied the file name from the site to avoid typoing the name... it's a zero, not an O, that sort of thing.
i'll post more information when i have time.
any other help??
pwhitt said:
well... i did everything to the letter, and the phone doesn't install the image. in download mode, the phone displays a message at the bottom that the sd card isn't mounted. i tried to check the sd card from within download mode, and it displayed something about smart sd card not found, or something similar.
the sd card is formatted exFat, so maybe i need to format it fat32? it's a 128gb card, i can try again with an 8gb fat32, but i thought exFat was supported...
for the record, i did everything to the letter - even copied the file name from the site to avoid typoing the name... it's a zero, not an O, that sort of thing.
i'll post more information when i have time.
any other help??
Click to expand...
Click to collapse
Yes format to Fat 32 and it is a zero,also make sure its the only file on the sd card and no bigger than 32gb card
OH! well then, i'll give it another go when i get back to it.
Thanks a lot!
Mr Troop said:
Yes format to Fat 32 and it is a zero,also make sure its the only file on the sd card and no bigger than 32gb card
Click to expand...
Click to collapse
Mr Troop, you're a life saver - thank you very much.
Now if I may be a pest, how do i unlock the bootloader? I keep finding this howto:
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
which is what c5satellite2 pointed me too as well, but this won't work for me since i don't have working SU.
it seems like i need root to unlock the bootloader, but i need to unlock the bootloader (apparently) to get SU...
i have read about 50 different threads spanning the last year+, and I'm not having a lot of luck...
your help is greatly appreciated!
pwhitt said:
Mr Troop, you're a life saver - thank you very much.
Now if I may be a pest, how do i unlock the bootloader? I keep finding this howto:
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
which is what c5satellite2 pointed me too as well, but this won't work for me since i don't have working SU.
it seems like i need root to unlock the bootloader, but i need to unlock the bootloader (apparently) to get SU...
i have read about 50 different threads spanning the last year+, and I'm not having a lot of luck...
your help is greatly appreciated!
Click to expand...
Click to collapse
Well done :good:
Yes i have used this or theirs htcdev
dont forget to change title to solved
https://www.htcdev.com/
Mr Troop said:
Well done :good:
Yes i have used this or theirs htcdev
dont forget to change title to solved
https://www.htcdev.com/
Click to expand...
Click to collapse
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
Just looked and i dont think you can unlock the bootloader by htcdev
will keep looking
Mr Troop said:
Just looked and i dont think you can unlock the bootloader by htcdev
will keep looking
Click to expand...
Click to collapse
right! that's the whole problem. verizon has locked the bootloader, and HTC isn't unlocking verizon phones...
this is killing me. i pay hundreds of dollars for a product, and it's loaded with their bloatware and i can't run an adblocker???
it's insulting.
pwhitt said:
right! that's the whole problem. verizon has locked the bootloader, and HTC isn't unlocking verizon phones...
this is killing me. i pay hundreds of dollars for a product, and it's loaded with their bloatware and i can't run an adblocker???
it's insulting.
Click to expand...
Click to collapse
HTC does not allow devices with a Verizon CID to be unlocked.
Your S-Off, You would need a way to switch to superCID (or any other nonVerizon CID) in order to oem unlock.
but not 100% sure so i would leave it and do some research check back tomorrow :good:
I was able to write the super cid, but I can't get the device string ........ Adb barfs, because oem unlocking can't be enabled.
Edit: n/m, saw you tried this already.
I know there's a way to do this, but you'll have better luck asking in the Verizon M9 forums. Many, many people have unlocked their bootloaders, HTC and Verizon notwithstanding.
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
From what I can recall, I did exactly that. Installed twrp, and had it install su. Then I unlocked boot loader. It doesn't make sense, but it worked.
Sent from my HTC One_M8 using XDA Free mobile app
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
Twrp 2.9.0.1 and supersu 2.65. Only that combo seems to work. That is how mine and many others are set up.
Htcdev to unlock bootloader but you need oem unlocking ticked in the rom.
If adb doesn't work its because you dont have usb debugging enabled in the rom. You only have fastboot access for now. But thats ok because thats all you need to flash twrp 2.9.0.1 and supersu 2.65.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Twrp 2.9.0.1 and supersu 2.65. Only that combo seems to work. That is how mine and many others are set up.
Click to expand...
Click to collapse
I have been using 3.0.0.0 and 2.65 since upgrading to MM and have had zero problems.
Hello all,
I have an HTC ONE M8 that is currently running a Kit Kat Venom rom. I want to update to something newer but my USB port doesn't work for data transfers etc, only can charge with it. I have only seen steps to update involving using PC, am I out of luck?
I also do not have my stock rom back anymore (laptop died and lost all information) , and the phone was originally bought in Kuwait so I am not sure how I go about getting the stock ROM back...
M8
jpeezy1977 said:
Hello all,
I have an HTC ONE M8 that is currently running a Kit Kat Venom rom. I want to update to something newer but my USB port doesn't work for data transfers etc, only can charge with it. I have only seen steps to update involving using PC, am I out of luck?
I also do not have my stock rom back anymore (laptop died and lost all information) , and the phone was originally bought in Kuwait so I am not sure how I go about getting the stock ROM back...
Click to expand...
Click to collapse
If you are already running venom then you are rooted so it should be fairly easy to do it from your phone. You need to know which firmware you will need, I'm guessing you probably have a European model.
I have a Verizon phone so the firmware is different but the process should be the same. I found my firmware and downloaded it directly to my phone, placed it in the root of the SD card (not in a folder), renamed it, rebooted to the bootloader, it recognized the renamed firmware and installed it. For my phone there were stock marshmallow sense ROM's that were prerooted and it was the same process, you download it to your phone, place it in the root of the SD card (not in a folder), rename it, reboot to bootloader and it should recognize it and install it.
Once you have successfully flashed it, then delete it or your phone will Try to install it every time you boot to the bootloader.
Is your USB Port physically damaged? If not then it could be dirty, have you tried blowing it out with compressed air?
And after you update your firmware you will probably need to update your recovery image (TWRP, etc).
I had read that many international models with GSM radios may be able to use the developer edition from the HTC website. There may be more info in the venom forum, at their website or at the HTC site. However, I would recommend you research it before giving it a try.
You need to find out what firmware you need and find the correct forum.
Good luck.
morr22066 said:
If you are already running venom then you are rooted so it should be fairly easy to do it from your phone. You need to know which firmware you will need, I'm guessing you probably have a European model.
I have a Verizon phone so the firmware is different but the process should be the same. I found my firmware and downloaded it directly to my phone, placed it in the root of the SD card (not in a folder), renamed it, rebooted to the bootloader, it recognized the renamed firmware and installed it. For my phone there were stock marshmallow sense ROM's that were prerooted and it was the same process, you download it to your phone, place it in the root of the SD card (not in a folder), rename it, reboot to bootloader and it should recognize it and install it.
Once you have successfully flashed it, then delete it or your phone will Try to install it every time you boot to the bootloader.
Is your USB Port physically damaged? If not then it could be dirty, have you tried blowing it out with compressed air?
And after you update your firmware you will probably need to update your recovery image (TWRP, etc).
I had read that many international models with GSM radios may be able to use the developer edition from the HTC website. There may be more info in the venom forum, at their website or at the HTC site. However, I would recommend you research it before giving it a try.
You need to find out what firmware you need and find the correct forum.
Good luck.
Click to expand...
Click to collapse
Thanks! I will do some research to see which firmware I need. When you say you renamed it after putting it on your SD card, what did you rename it to?
I tried cleaning out my USB port, with canned air , but no luck. If I plug in an OTG cable in it will detect that it is an OTG cable, but it wont read anything from there. I believe I will have to replace the charging port, fortunately for the M8 it is separate from the main board. Also, another indication I believe it is a faulty USB charge port is that it seems to take forever to charge..
jpeezy1977 said:
Thanks! I will do some research to see which firmware I need. When you say you renamed it after putting it on your SD card, what did you rename it to?
I tried cleaning out my USB port, with canned air , but no luck. If I plug in an OTG cable in it will detect that it is an OTG cable, but it wont read anything from there. I believe I will have to replace the charging port, fortunately for the M8 it is separate from the main board. Also, another indication I believe it is a faulty USB charge port is that it seems to take forever to charge..
Click to expand...
Click to collapse
For my Verizon phone the image had to be named OP6BIMG.ZIP. It may be the standard name but once you find the correct firmware thread it will most likely tell you what to name it. And remember, the system will most likely add the "zip" part to the end of the name so double check it after you rename it to see that it is not named ".zip.zip" before you go into the bootloader.
morr22066 said:
For my Verizon phone the image had to be named OP6BIMG.ZIP. It may be the standard name but once you find the correct firmware thread it will most likely tell you what to name it. And remember, the system will most likely add the "zip" part to the end of the name so double check it after you rename it to see that it is not named ".zip.zip" before you go into the bootloader.
Click to expand...
Click to collapse
Ok, thanks! I appreciate your help.
M8
jpeezy1977 said:
Ok, thanks! I appreciate your help.
Click to expand...
Click to collapse
No problem. Good luck.
Ok so in the last thread I started I learned how flashing ROMS works, with the matching firmware, CID's, and other stuff, but now I have another issue... The ROM that I was able to flash was the TeamVenom Viper One ROM for Android L (Lolipop)....The ROM version I used was Viper 3.5.0, but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x).... I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev) and I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link... I don't think I can update Viper because it says "Flashing the new Android M firmware is a must, else your phone won’t boot!!" (trust me it doesn't boot, I've tried)... But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)... What would I need to do from here, how would I A)fix HTC installer, or B) does anybody have a WORKING flashable stock android zip to update from Lollipop to Marshmallow...
Thanks in advanced!
Forum N00b,
qwsderter
qwsderter said:
but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x)
Click to expand...
Click to collapse
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
qwsderter said:
I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev)
Click to expand...
Click to collapse
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
qwsderter said:
I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link
Click to expand...
Click to collapse
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
qwsderter said:
But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)
Click to expand...
Click to collapse
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Flippy498 said:
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Click to expand...
Click to collapse
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash.... Any other ideas, you are the master at this Flippy, there must be another way...
qwsderter said:
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash....
Click to expand...
Click to collapse
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Flippy498 said:
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Click to expand...
Click to collapse
Ah gotcha... So I used the decryption tool to make a SD flashable zip, and what do you know, TWRP crashes when I swipe to flash... How come I can flash other ROMs but I can't flash stock roms without it crashing (Device turns off)
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok thank you "again" I have officially read your ENTIRE guide 3 times now, Not trying to offend you or make shame of your work, but the problem is I "THINK" that I am following your work.... I download the RUU for my phone (in this case SKU: 502 - CID: CWS__001 VERSION 2.11.502 (I have also tried 3.38.502.41 to no avail)) and everything is going as planned, I have verified that BOTH the CID and MID are matching that of my phone.... But when I plug SD card into Phone in download mode I get no such asked if I want to flash the file (as your guide says to do).... Ok so if I try to flash through TWRP it crashes, and if I try to Fastboot Flash the file I get what is seen in the picture attachment, and then nothing happens, except the bootloader page says "Under flash" and adds another line saying Under flash everytime I press the power button... My phone is S-OFF, is there another possible way to do this.... I swear to go I have read your ReadMe thread and I'm not just being arrogant, but my phone WILL not flash to ANY STOCK ROM downloaded anywhere from the Internet... @Flippy498 I promise there has to be something I missed in your ReadMe (I HAVE NO IDEA HOW I COULD) or i'm getting damaged ROMs... I'm sorry that you have to put up with me and help me thus far, and let me say the XDA community deserves people like you, and less people like me who think they know what they are doing until something breaks...
EDIT: It seems the phone is missing a located at /dev/fastboot_download_j in the CMD screenshot. Should that be said issue how would I go about fixing that...
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Flippy498 said:
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Click to expand...
Click to collapse
Once again Thank you for helping me out, the htc_flashboot command was what I needed, I was able to flash the stock rom through the command.... May I just say, you sir know what you are doing, and I wish you continue to help other people on this forms just like you've helped me.... I Installed the 2.x rom, but the OTA update didn't work for some reason... so I'm gonna flash the 4.x and then install ViperOne again...
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place...
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death...
Thanks again,
qwsderter
qwsderter said:
I Installed the 2.x rom, but the OTA update didn't work for some reason
Click to expand...
Click to collapse
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
qwsderter said:
so I'm gonna flash the 4.x and then install ViperOne again
Click to expand...
Click to collapse
Don't forget that you need to flash one of Sneakyghost's firmware packs if you want to be able to flash 4.x RUUs. (Keyword: encryption keys)
qwsderter said:
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place
Click to expand...
Click to collapse
That's actually the difference between my ReadMe thread and most of the RUU collections on other websites. The files only get linked if they're known to be working whereas other sites link every RUU they can find. There are a lot more RUUs for the M9 out there than the ones I listed. However, these RUUs either aren't able to get flashed successfully or their roms aren't able to receive any OTAs - e.g. there's a second RUU for firmware 1.32.401.15 than the one that is linked in my thread and if you flash that other RUU you're stuck on its firmware version until you flash a different RUU.
qwsderter said:
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death
Click to expand...
Click to collapse
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Flippy498 said:
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
Click to expand...
Click to collapse
Funny, I thought the same thing, until I realized it was ATT who I am paying every month to rip my girlfriend and I off. Well oh well, I know you are in Germany (From your profile) but if you ever come to the United States, I will say from my personal experience (my opinion, not facts) ATT has seemed to have the broadest coverage, but also is the (2nd) most constrictive (Verizon seems very constraining), to me ATT feels premium but they are also (in my opinion) the most likely to royally screw up... Oh well, no OTA time to flash!!!
Flippy498 said:
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Click to expand...
Click to collapse
Trust me, when I tried the SD card in the phone I thought, "That is a little odd", then both of my ASUS MemoPads didn't detect it either EVEN THOUGH THEY WERE RUNNING, I just assumed that they didn't work because MemoPads are the most budget friendly tablets ever and something broke, so I go to my Nexus 7 and realize it doesn't have an SD card slot so I couldn't test, so I popped the card in our Camera... Low and behold it doesnt detect.... Now the true question, why did my desktop detect it, eh whatever not worth my time.... The gods were looking down on me, they broke my $10 microSD and not my more than 10$ phone.....
Once again thank you for the help Flippy, you have no idea how much it hurt using my iPhone 5 for 2 days, I felt so inferior