Database Info

htc one s semibrick?

Hey, guys this is the first time I write, I have a Htc rootato s one from me and then updated with the latest ver. the sense of 4.0.4 and 4.1, it worked fine until the other day I was discharged the battery to reboot I noticed something strange, extreme slowness and inability to uninstall programs or return to the original configuration, it should be in bootloader, and if I ask him to go to recovery restarts back to the original screen (for a moment I can see the recovery, at least I see the little man cone orange lettering, but it's a flash, that with all the recovery I try to install) I tried again to do the unlock procedure these always successful, but I can not for example to re-lock the bootloader, it gives me the quest error:
(bootloader) Lock successfully ...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.940s
When I uninstall the apk seems to do it but when I reboot (and often do so alone) I installed the meeting again.
I also tried to delete files from the SD card, same thing when you restart are still there, I also formatted but when you reassemble as I had not formatted.
Sorry for the length, but I tried to explain as well as possible difetto. Can anyone help me?
Thanks, sorry for my bad english, the result of google translator

guys ... so, no one can help me?

Nvidia shield boot on charge carputer

Hello guys, I have looked for days and days for a solution... Could only find a solution if the tablet was a Nexus 7 or a Samsung device. I looked into the system files for anything remotely similar but unfortunately could not.
So do the great minds that are here able to help me ? So that the tablet will boot on a power input? Booting down is achieved by using an app so all I need is to boot the tablet. The tablet is a 2014 shield, rooted with cwm on 5.1.1
I am not a developer so will need a little hand holding but can usually achieve things, I would of thought somebody would have tryed this before considering the price of the tablet...
Can this be achieved by modifying a system file or does it have to be done on the bootloader ? If so can you please help.
I use the tablet mainly for in car diagnostics, and also media so want it to auto boot on power. All wiring is done just need a final little help. Regards BT

I doubt you will get your tablet to boot on charge, as it would require modifying the bootloader (wich is, AFAIK, not open-source).
But you can try some alternative, for example, don't shut it down, just let it sleep instead of powering it off. With the right settings you can get almost 0% discharge (Wifi off when screen off, turn bluetooth off, disable syncing, airplane mode, ...)
By default, the tablet screen turn on when on charge.

Cheers I will give that a try, I will see if I can get it working as you described above, what would you advise using tasker?
To anybody else;
I have tried running the : fastboot oem off-mode-charge 0 command through Minimal ADB. But unfortunately it comes back saying;
(bootloader) Unknown Command!
OKAY [ 0.029s]
finished. total time: 0.033s
When I test some other commands such as 'fastboot devices' it comes back with the correct serial so I am communicating with the device, and when I do 'fastboot oem unlock' It comes back saying unlocked too. But running 'fastboot oem device-info' again returns an unknown command... So is this a problem with what I am doing or the shield tablet not being compatible?

I've tried everything but my phone just won't turn on

Yesterday I tried to update my phone to android 6.0 but something must have gone wrong during the process because now my phone is stuck in a bootloop, I've tried as hard as i can to fix it but nothing is working. I tried to do a hard factory reset and wiped my phones memory but it won't turn on, I really don't know what to do because I cannot afford to get a new phone.

ineedhelplz said:
Yesterday I tried to update my phone to android 6.0 but something must have gone wrong during the process because now my phone is stuck in a bootloop, I've tried as hard as i can to fix it but nothing is working. I tried to do a hard factory reset and wiped my phones memory but it won't turn on, I really don't know what to do because I cannot afford to get a new phone.
Click to expand...
Click to collapse
If you can get into the bootloader, reflash your firmware to get it back to working condition.

damianx5 said:
If you can get into the bootloader, reflash your firmware to get it back to working condition.
Click to expand...
Click to collapse
Yes I can get into the bootloader but my computer isn't recognizing that my phone is plugged in, it just says charging

ineedhelplz said:
Yes I can get into the bootloader but my computer isn't recognizing that my phone is plugged in, it just says charging
Click to expand...
Click to collapse
Make sure you have all the drivers installed and that you have adb and fastboot files as well.

If you still cant access to transfer files, search for "adb push and pull" commands at google to directly send files to and from your devices.

I am having the same issue!
Here is the difference:
Updated phone to the new OS and my phone went into a boot loop. Booted my phone in Fastboot to try to Factory Reset, it won't reset, it just goes back into Boot Loop... *sobs* I've looked everywhere to find a solution to the following problem, and I'm posting here in order to avoid making unnecessary forums.
My Issue:
As stated above, I updated my phone and it went into boot loop. I am trying to flash it to the previous version, but because I can not factory reset my phone I can not flash my phone. I can not unlock the Bootloader because my USB Debugging is disabled and can not be enabled because my phone is bricked.
I've tried clearing the cache - wipe_data | wipe_cache | fastboot format userdata
I've tried
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
********** fastboot (serial number)
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.546s]
writing 'recovery'...
OKAY [ 2.699s]
finished. total time: 3.245s
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Only to later find it did not work due to my Bootloader being Locked...
Here's what I'd like to know: How do I Factory Reset my phone OR Unlock my Bootloader from my computer? Heck, why not tell me both, I can really use the help as this is my only phone and Motorola REFUSED to fix my phone due to some magical liquid damage... to a water resistant phone... that was never once touched by liquid of any kind... but I digress... [...vents on]
About my Phone:
Model XT1548
Rooted: No
Bootlader: Locked
Flashed: No (I believe)
Cause of Problem: Update to Marshmallow
_________________________________________________________
BTW: I made a new thread for this because I wasn't sure if posting here would get any help. HERE

Could you get it working?

Random Reboots, Then Phone Bricked Itself! Help Recover My Kid's Disneyland Videos!

This is a standard US Google Pixel 128GB that I picked up in January from Swappa. I have not ever modified it in any way. Never been dropped or abused either.
Since early April, the phone would randomly freeze and reboot itself. Sometimes it would be days between reboots, sometimes it would reboot multiple times even before it finishes booting. It's usually random, but I noticed it would always reboot if I am recording a really long video (5-10 minutes). Audio also failed once (no sound could be heard from speaker or earpiece) even after rebooting multiple times. Three days ago, while recording a long video of my kid at Disneyland, it froze. This time, the reboot failed to. The screen flashes some garbled stuff on the screen. Only difference this time is that I know the internal flash memory was almost full before I even started recording the video.
I can't get the phone to boot at all. If I press the vol-down button (doesn't even need the power button), I can get to the bootloader menu. In the bootloader menu, if I choose "Start," Restart bootloader," or "Recovery mode," the screen will flash again forever (I've waited hours). If I choose "Barcodes," then I will see all the proper IME/SKU/Serial numbers and barcodes. Choosing "Power off" works too, if it's not plugged in -- if it's plugged into power, the screen will flash a "static" screen endlessly. I took a video of this happening at Disneyland.
https://youtu.be/VlQ_PpZQ9SY
https://youtu.be/5m8_u0nQ4hE (the flashing screen)
After I got back from vacation, I plugged it into a Windows PC. No ADB access, but I can get fastboot to see it. Trying to reflash the lastest stock image (https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3) fails with this:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.810s]
writing 'bootloader_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.919s
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.055s
< waiting for any device >
Click to expand...
Click to collapse
The screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.430s]
writing 'radio_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.542s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
< waiting for any device >
Click to expand...
Click to collapse
Once again the screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: FA6C70300873
checking product...
OKAY [ 0.052s]
checking version-bootloader...
FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1703151359'.
finished. total time: 0.367s
Press any key to exit...
Click to expand...
Click to collapse
That's it. The bootloader screen does show BL and Baseband versions as "N/A", but can't these be overwritten? And is it normal for the device to say LOCKED? This is everything on my bootloader screen:
BL: N/A
Baseband: N/A
Product/Variant: sailfish-US-PVT
Serial Number: FAxxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Click to expand...
Click to collapse
If it'll help, I can get better photos/videos of the phone. The screen flashes some random distorted Google/Android logos and some "static"-looking pixels.
Any clue about what I should do? I would like to be able to get my photos/videos from the phone. I would also like to be able to recover the phone. Doing both would be awesome. I'm not sure if there is a hardware issue or software issue, but this phone has been horrible since April.

I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.

Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.

Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard

UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
justinxfan said:
I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.
Click to expand...
Click to collapse
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
danielt021 said:
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard
Click to expand...
Click to collapse
adb didn't see the device. Just fastboot.

ken830 said:
UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
adb didn't see the device. Just fastboot.
Click to expand...
Click to collapse
Yep sounds like the boot loader is screwed. Phone is a brick. She thing happened to my Nexus 7. I had to replace the motherboard.

did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.

AlphaOrion said:
did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.
Click to expand...
Click to collapse
Sorry to hear this, but I didn't have any solution except for replacing the entire phone. You should contact Google anyhow.

this is so disappointing...I wonder how many people this has happed to already, I was using the phone and it just randomly shut off and wont turn back on..almost exactly what the OP is experiencing...obviously phone is now out of warranty and apparently motherboard needs to be replaced (which is ridiculous!!)….I've never had a phone brick on me ever, never thought it would actually happen, especially on stock everything.
---------- Post added at 08:02 AM ---------- Previous post was at 07:57 AM ----------
Maybe its me....but it seems like more and more people are having this issue...looks like as the hardware gets older the more prone to partition being corrupted....this is not acceptable for a 2 year old phone

I have had numerous pixel replacements. One of them was a hard brick like yours. Even took it to iFixit and they confirmed it was dead. So it may not be uncommon.

I just don't get if photos and videos were so important if no one ever does a weekly backup? Use Google drive, use Google photos, use your USB cable to PC if you don't trust Google.
Phones break, get over it. You want a fast phone? Expect it to die even faster. 2 years for a phone is normal, if you don't think it is get then budget phones are there, with the long life low hardware aspect

I had TWRP and Magisk flashed. Now I wanted to go back, flashed factory, locked the bootloader and now I can only boot into fastboot. Everything elsa ends in a bootloop with a short flashing Google logo.

Water damage, need to format before fixing

Hi, I had nearly finished setting up my brand new Pixel 3a when I made a classic mistake - & dropped it into a toilet. I pulled it out almost instantly, but the damage had been done. I tried to turn it off, but it wouldn't even let me do that as the screen was completely non responsive & whatever I did kept on rebooting it. It was set to ask for a pin on boot, but I can't type it in as the touch screen doesn't work. The whole screen is completely black, so I can't see anything either. I used Google's Locate my Phone & set it to wipe it for me, but the alarms that I set on the phone keep on going off at the times that I set, so it obviously hasn't wiped it. Sometimes I get some life by pressing Vol Down + Power whilst plugged into via USB - & it comes back with:
Code:
$ adb devices
List of devices attached
03JAY2VCL7 unauthorized
or
Code:
$ adb reboot fastboot
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
All I need to do is to factory reset it, as the data on the phone has security implications & I need to erase it before it gets scrapped (or, slim chance, repaired).
I had connected it to my workstation to copy lots of files across, & I'm sure that I turned on ADB Debugging & Dev Mode, so I'm not sure why I get "device unauthorized"
Can anyone tell me the keys to press to tell it to factory reset please?
TIA, Justin

OK, possible progress.
I pressed Vol Down then Power, & held everything down for about a minute. ADB no longer showed any devices, but fastboot did as root..!
Code:
[email protected] /home/user $ fastboot devices
03JAY2VCL7 fastboot
so I tried this:
Code:
[email protected] /home/user $ fastboot erase data
erasing 'data'...
FAILED (remote: Fastboot command (erase:) is not allowed when locked)
finished. total time: 0.140s
Ahh, it's locked...!
Code:
[email protected] /home/user $ fastboot getvar all
(bootloader) product:sargo
(bootloader) serialno:03JAY2VCL7
[SNIP]
(bootloader) unlocked:no
OK, maybe this will work?
Code:
[email protected] /home/user $ fastboot flashing unlock
...
OKAY [ 0.143s]
finished. total time: 0.143s
I wonder...
Code:
[email protected] /home/user $ fastboot getvar all
(bootloader) product:sargo
(bootloader) serialno:03JAY2VCL7
[SNIP]
(bootloader) unlocked:yes
OK, that looks good...
Code:
[email protected] /home/user $ fastboot erase userdata
erasing 'userdata'...
OKAY [ 4.619s]
finished. total time: 4.619s
OK, that looked really good. So, my question is now did I manage to erase the data on the phone?
I thought that an OEM Unlock also did a factory reset? Am I right in that? Also, I thought that the "fastboot erase data" removed all of my user data? Am I right in that too?
Basically, am I OK now, is the phone completely erased (as much as I can, under the circumstances)

I see this authorization issue every month when I use adb to sideload updates. When you plug the phone into your computer, it pops up a prompt to "Allow USB debugging" before it is allowed. Once authorized, I am not sure how long the authorization lasts for. I think it may be until the next reboot. But for sure, it is not persistent because every month I have to re-authorize it from the same computer as I did last month.
What I find confusing is that even though I check the box that says to remember the authorization, it still asks every time I connect it. Why does this authorization not persist?
So the problem is that you can't authorize the connection. I have a program called scrcpy that mirrors the phone screen onto your computer and lets you use your computer keyboard and mouse, but it has exactly the same problem as it uses adb so you have the same popup where you have to authorize the connection before it can work.
Maybe when it dries out some the screen will start to work again? This phone is one of the easiest on the market to open up: https://9to5google.com/2019/05/10/google-pixel-3a-teardown/ I think if I were really stuck, I would try removing the screen, draining out any liquid and then gently drying it with a heat gun. You can leave the screen connected while doing this and if the screen starts to work then you can authorize the connection.
I did some more thinking about this and it seems like the best solution might be to try to get the phone booted into recovery mode using the power and volume keys. In this case, there is not an authorization prompt. The problem is that you won't be able to see the screen prompts so you will be working blind. https://www.hardreset.info/devices/google/google-pixel-3-xl/recovery-mode/ "Wide data/factory reset" is probably what you want.
Good luck!