Related
Greetings! I need a rom! My DS can't get out of bootloop, so I can't get the CID. That means I'm not able to make a gold card. All I know is that my device was made for Singapore. Does that mean I need to get a Singapore custom rom to bring my DS back to life? Where can I get it? Any help will be greatly appreciated!
My phone info, if that'll help:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011, 14:58:38
Hey, check out this thread: http://forum.xda-developers.com/showthread.php?t=1002506
I guess those are all we have so far. Just out of curiosity, how did your boot loop happened? There were several reports on this after battery being removed while phone wasn't responding and in all cases it was broken eMMC.
Thank you for your reply. I've tried some of these roms and it said "wrong CID" or smth like that..
I rebooted the phone while it was connected to pc. At the first time it almost booted but hanged when I was typing the sim password. The result of my next attempts to boot it was the htc logo on a white screen. I've tried the factory reset but it didn't work.
Is there a way to find out if it's 100% an eMMC problem?
Hey, I think if your factory reset went ok, there should be no problem with eMMC (but there might still be hardware issue).
Have you tried this ROM? http://www.filefactory.com/file/ca3...0805U_38.03.02.15_M_release_179398_signed.exe
There are very few developers or advanced users in Desire S forums, unfortunately, I'm not one of them, so there's only limited amount of advices I can offer. If I were you, I'd try to contact HTC directly and ask them for help. Is your phone under a warranty?
Tried it, still "wrong cid". HTC-Russia won't help cuz my phone's illegal here.. but thx anywayz
Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.
sorry, as an addendum, I've also successfully created a gold card, if that helps.
Blindshot888 said:
Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.
Click to expand...
Click to collapse
A very rare problem, and since you've done a lot on your phone that were'nt successful, hope for the best that you haven't fried your eMMC. (Check forum for reference)
I would strongly suggest to remove the battery out for atleast 30secs to 1min. Then place it back in.
don't turn on the phone and charge it until full.
Once full, disconnect from power.
Go to bootloader, post your hboot version.
If hboot is still the same, go to fastboot and RUU with the one that your phone came with when you bought it.
It's great that you have a GoldCard, if the step above don't work, try RUU to the latest one.
Now regarding the freezes, I haven't received any freezes from my phone when it was still on stock. It might be a software problem and RUU might fix it. But if its a hardware, you might need to send for repair or maybe replacement.
Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.
Blindshot888 said:
Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.
Click to expand...
Click to collapse
The phone really didn't came with an RUU file. What I meant is that try to remember the Software Version of the phone when it came when you bought it. That means that software version is the RUU that was installed with it. Also the region.
My phone was installed with the one prior to RUU_Saga_hTC_Asia_WWE_1.48.707.1......
Try to get the RUU of your phone.
Post your HBOOT means post here or atleast tell me what is the version of your bootloader.
Example:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011, 14:58:38
the latest as of now is RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.
Thanks again Skanob,
I'll try what you said to do and post the results.
from my initial post, I stated my HBOOT version as 0.98.0002. From what you've told me, should I expect my HBOOT version to change?
Also, I've checked the Europe RUU I attempted to use initially, i can confirm that it was the same version number as my phone. However, it got stuck on the status of "Rebooting to Bootloader" for hours.
Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.
Blindshot888 said:
Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.
Click to expand...
Click to collapse
I was expecting that your HBOOT would've been changed to the new one, it was an honest error on my end. I thought you've RUUed on the latest one. Sorry about that.
Seeing that you already have a GoldCard, I strongly suggest to RUU to the latest Europe version first.
If it still doesn't work, prepare for a long instruction, read on:
If you cannot use any RUU, the only thing you can do is update your HBOOT to the latest official S-ON.
Seeing that you are still currently S-ON. you wont be able to flash anything on your phone properly.
I myself don't have a proper guide on how you can update it as stock as possible, but maybe you can try what I've done before.
Skanob said:
amidabuddha said:
Ok taking my words back And how do you did this? You flashed the Stock 2.10.401.4 ROM over you bricked phone and it worked? (overwritted the revolutionary hboot or which version was it before?).
Click to expand...
Click to collapse
To make the long story short:
I stupidly get the firmware.zip file inside the ota file. That file had the latest hboot, recovery, and others. I renamed it to the correct pgxxximg.zip (cant remember the correct filename, currently drinking ) to flash it from bootloader.
Everything went well. Everything inside the file updated the corresponding file/partition/image to my phone. Hence letting me be stuck to the "locked" hboot 2.xx.xx s-on. ROM wouldn't boot as I said.
Being on the "locked" state wouldn't allow me to flash anything on the phone as far as i can remember. While writing, it will say has its unsuccessful.
But "unlocking" the hboot let me flash the recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
The OTA file that I've mentioned here is the recently released OTA file for Sense 3.0. Use search on where to get the download link.
Once you have the OTA file, just extract it and gather the firmware.zip file. copy it to your phones SD Card and rename it to PG88IMG.zip (.zip should be the extension of the file, not included in the name of the file).
Boot your phone into bootloader and agree to the phone if it asks you to update. AFAIK it should automatically do its thing.
Also, I remembered that it should be stuck in the middle of its update, just past the HBOOT and RADIO procedure. Once you are on that stuck state, maybe wait for about 10-15mins and see if it doesn't move. That is when I've removed the battery and waited for 30secs to 1min then re-plug it in. So you should pay close attention to what it is doing. Then check your HBOOT and see if it is updated.
If it is successful on updating your HBOOT, you would now need to UNLOCK your bootloader. The HTC unlock method supports the new HBOOT, seeing that you are still on the OLD one, thats one reason it wasn't successful.
What we're trying to do here is to get your phone to a state where you should be able to flash a custom recovery (check partitions if they are corrupted, most especially cache), full wipe partitions, flash a custom rom (pre-rooted stock recommended), then RUU back if you still want stock roms.
Goodluck!
P.S.
These instructions that I've given you are the methods that I would've used and thought of if I was in your situation. I am no expert in ADB nor on how to fix the phone properly. I assume that you already know the world-wide disclaimer: "not held responsible, know what you are doing" blah blah blah...
Also, full charge your phone first prior to doing it.
---------- Post added at 02:51 AM ---------- Previous post was at 02:32 AM ----------
And it's Skanob...
oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.
Blindshot888 said:
oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.
Click to expand...
Click to collapse
it should be PG88IMG.zip (.zip is the file extension). But have you double checked if the HBOOT was updated?
I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.
Blindshot888 said:
I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.
Click to expand...
Click to collapse
you might want to try to re-create your GoldCard. You might have a bad one.
Does the phone detects the file? There should be a check of .zip files once you boot on bootloader. The screen will take you there within 3-5 seconds after boot and will stay on checking the files for 1-2 seconds.
Blindshot888 said:
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
Click to expand...
Click to collapse
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course
amidabuddha said:
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course
Click to expand...
Click to collapse
or that ^^^^
Hello, I'm in a major bind. I had TWRP installed on my Rogers Hox, running a cm10 nightly rom. I didn't like the fact that I had no video camera so I decided to switch to CleanRom 5... (Bad idea in hindsight)
My phone kept getting stuck loading up CleanRom so I decided to try and go back to CM10 or stock... Long story short, now I have a "Soft" Bricked phone. I now have no rom installed on my phone at all, and the bootloader is re-locked ( I'm a dummy, I know.)
The phone will not let me flash a HTC dev supplied unlock_code.bin file despite clearing the cache through fastboot, it just gets stuck on sending the code and I cannot access TWRP or Stock recovery.
My bootloader screen reads
*****Tampered******
*****Relocked******
Evita PVT SHIP S-ON RL
HBoot-1.11.0000
Radio-0.18as.32.09.28L
OpenDSP-v28.1.0.32.0504
eMMC-boot
I've been at this for hours and tried every possible thing I can think of and yes I searched on here until I was ready to pull my hair out. Could someone please point me in the right direction ? Thank you very much in advance!
Download and flash the HTC STOCK RUU from this thread ...http://forum.xda-developers.com/showthread.php?t=1671237
It was discussed in another recent thread. One suggested solution: http://forum.xda-developers.com/showpost.php?p=33830816&postcount=12
Never mind. I just re-read your OP, and saw you can't get into recovery.
If you send the token and it gets stuck at "sending", leave cmd open, open up a 2nd cmd window and send the token from that one as well. The first window will finsh sending the token and you can unlock:beer:
Sent from my HTC One XL using Tapatalk 2
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
iceterminal said:
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
Click to expand...
Click to collapse
I gotchu my friend ;D http://www.htc.com/us/support/htc-one-mini-att/news/ That is the ruu for the htc one mini
abzboi said:
I gotchu my friend ;D That is the ruu for the htc one mini
Click to expand...
Click to collapse
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
iceterminal said:
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
Click to expand...
Click to collapse
Ah I read that it will work too if it is fastboot which is why you were suggesting it. I'm wrestling with fastboot drivers and windows 8.1 so it is recognized so I dualbooted into ubuntu which can communicate via fastboot so I'm hoping WINE will run and flash the RUU .exe
So I ended up rebuilding an older laptop to Windows 7 and ran the RUU executable and it looked promising at first with the updater recognizing the device and displaying what software version and stuff.... but then when it rebooted into hboot with it's process, the update failed.. not sure if it matters but it was "updating" from the same version as the current version. I was hoping this would be a fresh install. So now I'm looking into maybe doing a fastboot oem unlock and flashing a rom myself. Not sure if this will help me get the phone back from the dead, but going to do some more reading and exploring. If anyone has some shots-in-the-dark they would like to offer, I'm up for trying them.
I hope you would be able to fix it.
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
iceterminal said:
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
Click to expand...
Click to collapse
Have sent you a PM re your issue.....
Re flashing recovery without fastboot (locked bootloader), it can be done, but only, as far as I know, via the phone os using CWM manager or Flashify (which is a cool app!)
wanted to close the loop on this thread that nelvinchi and I literally tried everything we could think of to bring the phone back to life with no avail. Much respect out to nelvinchi for taking his time to help me out! We've determined that the device has a faulty memory chip and cannot be recovered...
Mine just did the same thing and I can't get through to anything I need help also if you have found a solution
Help my
provided you solve a problem with one htv mini.my I have the same problem, please help me
I just got S-Off with Sun Shine, but can't seem to get SuperuserSU working (I was going to install TWRP from TWRP Manager after getting SuperuserSU.) Anyone know what I need to do? I looked for a thread that explained the process, but have not found anything. Many thanks!
Flash twrp from fastboot. Flash SuperSU from twrp.
Sent from my XT1254 using Tapatalk
I am trying to flash TWRP with Minimal ADB and Fastboot from here..... http://androidmtk.com/download-minimal-adb-and-fastboot-tool
I keep getting this for messages when I type the command flash twrp.img "cannot load 'twrp.img'
I know that the device is connected since it goes into fastboot when I type "adb reboot bootloader".
Any ideas?
Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!
therreid said:
Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!
Click to expand...
Click to collapse
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk
I posted this in the general questions thread, but I wanted to post here as well...
beaups said:
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:
M-FayeHTC said:
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:
Click to expand...
Click to collapse
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)
I'm still having trouble...
dottat said:
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)
Click to expand...
Click to collapse
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!
M-FayeHTC said:
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!
Click to expand...
Click to collapse
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.
First part COMPLETE!
dottat said:
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.
Click to expand...
Click to collapse
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!
M-FayeHTC said:
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!
Click to expand...
Click to collapse
Well if you used the s-off one that's fine too. You will be rooted already. Just need to flash the latest twrp image and you will be fine.