Hello guys, hope someone can help me, i have a HTC one S i bought of street, phone was working fine now all of the sudden when i connect to PC i get qhsusb_dload mode, and wont turn on or anything, no LED, so i figure it was bricked, but now when i connect to charger and Hold Power + volume down it boot into stock ROM fine and i can use while i charger, now if i unplug and connect to PC it turns off and get same on Device Mgr.
Battery seems fine and its fully charged, now as long as i dont shut screen off, it works fine.
Also i managed to boot in Boot-loader (Power + Volume down) and on the top it says
" Tampered"
"Locked"
"Security Warning"
Keep in mind i don not have warranty so im thinking my only solution would be jtag but since its not completely dead i'm wondering if it could be something else since it does turn on, mostly whenever it wants. I have not touch anything on the phone related to root or anything
Any help would be appreciate it i cant afford to buy another phone for now.
(Already tried Factory Reset)
(Tried Linux unlimited.io solution)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what is your hboot version you will find it in the bootloader
ill check again and ill try to post a pic its just a pain in the ass to boot into it imagine the ROM, is there a way i can boot it from the rom to the bootloader without having to press power _ volume down
attache a pic of bootloader below
i managed to unlocked the bootloader and root the phone, now seems to be working i have connected to usb and working fine so far
now im tryign to superCID and S-off , so i tried the 11111 trick but didnt work, still show TMOB10 so i cant s-off at all ???
cubanito08 said:
now im tryign to superCID and S-off , so i tried the 11111 trick but didnt work, still show TMOB10 so i cant s-off at all ???
Click to expand...
Click to collapse
Try with 11111111 (8x1 not 5x1 like you said).
no i mean i used 8x1 i just put that, but i found down i need to downgrade to be able to supercid, but my problem is i think my wifi is making my phone reboot or turn off but im not sure yet but it does sometimes turn off by itself unless is a bad battery
Related
I am new to the whole flashing thing. I read a number of guides last night and was finally ready to do it. I downloaded Odin 1.82, had my drivers installed from this thread (Or so I thought) and tried to flash. In Odin, it hangs at "Setupconnection". I couldn't figure out what the problem was and then I noticed when I plug in my Droid Charge, this is what I get...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Odin detects my phone, and I'm able to access the SD card on it from my PC, but like I said it doesn't flash...and I assume that's because of not every driver having been installed. How can I resolve this issue? I'm using the drivers that this site and a number of other sources say to use. I've tried uninstalling and reinstalling them, different cables and different PCs, as well as different versions of Odin.
What confuses me is what I'm reading says to boot into Download Mode with the battery out. How am I supposed to do this when it's not plugged in and no battery? Also, is my phone supposed to stay on when plugged in and the battery is out? Because mine keeps turning off when the battery comes out.
OrbitzXT said:
What confuses me is what I'm reading says to boot into Download Mode with the battery out. How am I supposed to do this when it's not plugged in and no battery? Also, is my phone supposed to stay on when plugged in and the battery is out? Because mine keeps turning off when the battery comes out.
Click to expand...
Click to collapse
Pull the battery, hold VolDown and plug in USB. When the phone is recognized, put the battery back in.
shrike1978 said:
Pull the battery, hold VolDown and plug in USB. When the phone is recognized, put the battery back in.
Click to expand...
Click to collapse
I feel like an idiot. It's working now, thanks a ton. I think I was in recovery mode. I flashed CWM and am now planning to flash Tweak using Odin. What exactly is CWM and how do I use it if I need to? My understanding was that it's a recovery tool. Also for Tweak, I notice one download has a kernel and one doesn't. As a noob, what do these things mean and which should I go with?
After you Odin the rom and cwm, you want to boot into cwm and flash a custom Kernal before you allow the phone to reboot, otherwise the stock Kernal will overwrite CwM with the original recovery... Unless you odin the package that has the Kernal in which case CwM would stick.
FYI - CWM should stick on either of the tweakstock Odin files
dwitherell said:
FYI - CWM should stick on either of the tweakstock Odin files
Click to expand...
Click to collapse
Sorry about that. I didn't mean to give bad info. You have me curious now... Is there something in the process that stops the Kernal from overwriting the recovery?
Adamsaudio said:
Sorry about that. I didn't mean to give bad info. You have me curious now... Is there something in the process that stops the Kernal from overwriting the recovery?
Click to expand...
Click to collapse
No worries - there's an install-recovery.sh script in /system/media/ that - when removed - leaves CWM alone.
I have a Verizon HTC One M8 that can still power on, but will only go to the black screen with an HTC logo in the center and a triangle with an exclamation mark in each of the four corners. This happened while returning my phone to stock. My computer disconnected from the phone half-way through pushing an RUU flash. The cable wasn't unplugged, the computer just made the disconnect sound and the flash stopped. The phone is not recognized as an adb device, but it is recognized as a fastboot device. This gives me some hope that the phone can be recovered, but any attempt to flash an RUU gives me the error: cannot load "file-name". Any suggestions?
Just to help out anybody trying to figure this out:
The phone will not enter recovery
The phone enters something akin to the recovery page if I disconnect it from the PC, but the only option is RUU and pressing the power button will not do anything (picture attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.
MotoTurbo said:
Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.
Click to expand...
Click to collapse
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!
curb42 said:
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!
Click to expand...
Click to collapse
And if you run into any issues hit me up... i can help you out remotely.
dottat said:
And if you run into any issues hit me up... i can help you out remotely.
Click to expand...
Click to collapse
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.
curb42 said:
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.
Click to expand...
Click to collapse
Awesome man, glad you got it working. Also you can try a factory reset after ruu if you've flashed a bunch of Roms and have iffy data
anyone who can help me?
my xperia c2305 got encryption unsuccessful. A little history from my phone, maybe a year ago I root my xperia c2305 to expand my internal storage I follow the instruction from information lord site, at first it did good but after maybe a few months my XC got bricked (only loading at booting and stuck there). So I decided to flash it to make it back using this firmware C2305_16.0.B.2.16 and after that I never root my XC again. Since then maybe after a month, or a few months my XC always got bricked (the notification first appear apps has stopped then when I restart my phone it will stuck at booting proccess). So, I've been flashing my XC maybe a couple times now not because I want to, but the problem is now my XC got Encryption Unsuccessful and I don't know how to repair it. Try to reset the phone but nothing happen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and if I tried power + volume down it gets like this
So what I have tried is :
1. I try to flash it using wmshua (usually i can flash using it), the proccess first got 5%, then 10%, after that jump to 100% and then failed. (* I have tried using another rom or pc companion but the problem always like that error in the middle of the proccess)
2. Cannot reset phone
3. Trying to boot to recovery mode using power and volume down but error.
Someone please help me how can I make it back like original.
*Sorry for my bad english
I have some problem any help please,???
Any help please i have some problem
Press the camera button after booting to recovery to really enter the recovery
Try resetting from there
Might work
tataboga said:
anyone who can help me?
my xperia c2305 got encryption unsuccessful. A little history from my phone, maybe a year ago I root my xperia c2305 to expand my internal storage I follow the instruction from information lord site, at first it did good but after maybe a few months my XC got bricked (only loading at booting and stuck there). So I decided to flash it to make it back using this firmware C2305_16.0.B.2.16 and after that I never root my XC again. Since then maybe after a month, or a few months my XC always got bricked (the notification first appear apps has stopped then when I restart my phone it will stuck at booting proccess). So, I've been flashing my XC maybe a couple times now not because I want to, but the problem is now my XC got Encryption Unsuccessful and I don't know how to repair it. Try to reset the phone but nothing happen
and if I tried power + volume down it gets like this
So what I have tried is :
1. I try to flash it using wmshua (usually i can flash using it), the proccess first got 5%, then 10%, after that jump to 100% and then failed. (* I have tried using another rom or pc companion but the problem always like that error in the middle of the proccess)
2. Cannot reset phone
3. Trying to boot to recovery mode using power and volume down but error.
Someone please help me how can I make it back like original.
*Sorry for my bad english
Click to expand...
Click to collapse
Ok try here https://forum.xda-developers.com/sony-xperia-c/help/xperia-c2305-red-light-blink-sign-death-t3574885
This works on any kind of software issue fallow all the steps dont forgot to hit thanks
Found my old tablet recently while moving and figured I'd charge it up and see what happens. Clearly the younger me had plans to do something with it, but now I am at a loss as to what to do? It boots on the ASUS screen, then restarts and boots into Team Win Recovery Project v2.5.0.0 - what do I do from here to get it to boot into android? Do I have to install android? If needed I can make pictures of the process and what the screen shows.
Thanks for any and all help!
xprob said:
Found my old tablet recently while moving and figured I'd charge it up and see what happens. Clearly the younger me had plans to do something with it, but now I am at a loss as to what to do? It boots on the ASUS screen, then restarts and boots into Team Win Recovery Project v2.5.0.0 - what do I do from here to get it to boot into android? Do I have to install android? If needed I can make pictures of the process and what the screen shows.
Thanks for any and all help!
Click to expand...
Click to collapse
Ok, 1st is the TF700t unlocked? It will say it's unlocked when you boot it up and then you need to know what bootloader version you're on. - NP
The top left corner on the black ASUS screen says Unlocked but that is it. How can I find out what bootloader version is running on the tablet?
Thanks!
You have to boot into the FastBoot screen, hold the volume button down and press the power button, hold the volume down button while it boots and you should see this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2nd line from the top. - NP
My apologies for the delayed response, work got more hectic than usual
It appears to be version 1.00 e, is this a good thing?
It's the number after "US_epad-" looks like 10.6.1.14 let us know what the number reads - NP
It reads "US_epad-10.6.1.14.8-20130514" A03. Your eyes are better than mine, no clue how you read that from the picture.
Thanks again for helping!
I would update the bootloader to 10.6.1.14.10 - NP
On the verge of sounding dumb, how would I go about updating the bootloader version? I have never done any of this before.
Thanks again.
xprob said:
On the verge of sounding dumb, how would I go about updating the bootloader version? I have never done any of this before.
Thanks again.
Click to expand...
Click to collapse
Check this thread out, it has links to the updated bootloader and newer TWRP, you can flash this off the microSD card using the existing TWRP. - NP
https://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Hi,
A few days ago I tried to update my SM-P900 tablet after 3 or more years without updating. I tried to flash this ROM (https://forum.xda-developers.com/ga...7-1-xsm-p900-unofficial-cyanogenmod-t3524788/), but it didn't boot. I flashed the recommended bootloader and recovery with Odin, but I'was not able to boot. Somehow, neither booted Lineage 13 (https://forum.xda-developers.com/ga...t/rom-cyanogenmod-13-0-android-6-0-1-t3366834) nor Resurrection (https://forum.xda-developers.com/ga...lopment/rom-resurrection-remix-5-8-2-t3563635). The only ROM I managed to get working is CM 12 (https://forum.xda-developers.com/ga...t/rom-cyanogenmod-12-lollipop-5-0-1-t2971945/). I thought that the problem was the bootloader, and someone suggested that I flash a more recent (at least lollypop) bootloader. According to Phone INFO, my bootloader version was P900XXUANI1. I tried again and again to flash the BL_P900XXU0BPA1.tar.md5 file, but, despite Odin showing the PASS! message, Phone INFO kept showing the same bootloader version. After that someone recommended that I flash the most recent stock image, so that I get a recent bootloader, that is what I tried to do.
I downloaded the file Samsung_SM-P900_(P900XXS0BPL2_P900OXE0BOI1_Russia_v5.0.2)_by_ (FirmwareOS.com) from a sammobile kind of site. What I look for is that ...BPL2 version that seems to work for other people. But after flashing it, the tablet doesn't boot and I can't access download mode. The only thing that i get to boot is the stock recovery, but it doesn't have the flash img option nor the reboot in Download mode that TWRP had. The only options I got are "Update from external storage" and "Update from ADB". Either of them don't let me flash a full factory image nor, apparently, another bootloader or custom recovery. When I try to flash it I get "E: footer is wrong \n E: signature verification failed" and if I do it via ADB, the error shows right away after a 0% transfer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Other symptoms I found are:
- I can't manage to power off the tablet using just the buttons: it always reboots unless I select the Power off option in the recovery. Also if the tablet is connected by USB to the charger or the computer it always try to boot.
- When the tablet is connected via USB and I try to power it off, the tablet reboots and shows a battery symbol, but is gray and kinda strange.
I'm pretty desperate now. This is my wife's tablet and I tried to update it so that it was more secure. I'm screwed.
Any ideas? Is this fixable?
Thanks in advance.
Regards.
Did you try to download the stock rom which consists of several parts with the samfirm software?
For that you have to check the binary box in SamFirm and to insert device type and region.
Flashing that might work better.
I forgot to update the thread. I managed to fixed the tablet. It turns out the tablet hadn't enought battery to enter download mode and I was messing up with the Vol Up and Vol Down buttons. Really embarrasing. Hahaha. After fully charging the device and pressing down the proper buttons, I managed to enter in Download mode and flash a new image.