I fried my one s a few days ago and just got the replacement. I went to htcdev.com and put in my new identifier token, got my bin, went to flash and got
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
and i thought ok maybe i messed up and used the old. I deleted all the bins, cleared cache on browser, and re-ran fastboot oem get_identier_token
it gave me something different... i thought ok i ****ed up some how, put the new one in to htcdev, got a bin flash, same thing...
i just sat here and spammed get id and its different every single time and none of the bins are working.
it came with hboot 2.15; but i was running this on the last phone (although i was s-off..) i did a quick forum search for "oem get-identifier_token" and didnt really see anything useful..
am i ****ed? whats the way ahead? thanks!
here's some possibly relevant info; this is a straight up latest **** from tmous phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.531.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24YW402012
(bootloader) imei: 359902042972202
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3979mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
scratch that, i was trying to do this at work on a windows box; i got home and did it on my linux laptop and it worked fine.. strange.. never tried doing anything in windows before :/
See if your bootloader is unlocked
Sent from my Nexus 7 using Tapatalk HD
Okay so, I was being all in awe because this was my first root, and I did it, but here's the messy bit, I kept installing ROMs and it felt messy so I went into TWRP (Version: 2.6.3.0) and I sort of went into advanced restore/reset options and I checked off everything. Bad idea by the way. So to sum it up this far, I uninstalled the operating system. The original backup of the original stock ROM was on the phone, it's now lost. I've been trying for days to fix it, and I know I messed up big , I re-locked the phone and I cannot get it to unlock again, so I lost access to TWRP, and I just want my phone back.. When I try to flash anything, from my experience anyways, it says (in this example, the TWRP img file, for recovery),
"C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.065s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.073s"
Really, I just want the stock ROM and for this all to be over. If someone could possibly help me, I'd love it. The phone is also AT&T, and the SIM card is disabled for the most part, it's an old phone from my (almost) uncle. As for the info I could get from fastboot:
"C:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34SW909721
(bootloader) imei: 354439053939734
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4221mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 3.872s"
Sorry for the spam bit, please help? I'm honestly lost. If this problem does get resolved, and I'm honestly not sure it will, I'm also interested in a good, stable Lollipop ROM for my HTC One M7. Thanks! :fingers-crossed:
Hi,
You have already made a post here on same topic. Please do not create multiple threads of same topic. wait for experts to answer your questions.
Thread Closed.
First I bought a rooted HTC m7 and i managed to delete it "unroot it".
1- the first problem is the 3g connection it comes up for about 10 seconds and then it disappears for about 4 second and it comes back again.
2- the Second problem is some time when I try to make a call I can't hear the other phones ringing and the other person can't hear me and this happens some time and to fix this I need to reboot the phone.
3- And the WiFi speed seems to be slower than the connection and when I asked a repair man he told me that it might be the prerooted system could be the cause of these problems.
4- And I noticed that I don't have the system update option.
All I am asking is how to make it to stock rom with OTA "over the air updates".
Because I have been looking for a solution and all of the suggestions and tutorials got me confused.
And you should also know that the phone is sprint i knew it because of the reference in the back of it "pn0720000" and I live in Algeria
These are my phone's info
----------------------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 2.03.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: I can see the numbers
(bootloader) imei: I can see the numbers
(bootloader) meid: I can see the the numbers
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3803mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Tell me if you need any other info.
Please help me I am confused.
I was going to use this RUU file but I was afraid to brick the phone this is the name of the file
RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10 it ends with dot exe
Brhou said:
First I bought a rooted HTC m7 and i managed to delete it "unroot it".
1- the first problem is the 3g connection it comes up for about 10 seconds and then it disappears for about 4 second and it comes back again.
2- the Second problem is some time when I try to make a call I can't hear the other phones ringing and the other person can't hear me and this happens some time and to fix this I need to reboot the phone.
3- And the WiFi speed seems to be slower than the connection and when I asked a repair man he told me that it might be the prerooted system could be the cause of these problems.
4- And I noticed that I don't have the system update option.
All I am asking is how to make it to stock rom with OTA "over the air updates".
Because I have been looking for a solution and all of the suggestions and tutorials got me confused.
And you should also know that the phone is sprint i knew it because of the reference in the back of it "pn0720000" and I live in Algeria
These are my phone's info
----------------------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 2.03.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: I can see the numbers
(bootloader) imei: I can see the numbers
(bootloader) meid: I can see the the numbers
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3803mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Tell me if you need any other info.
Please help me I am confused.
I was going to use this RUU file but I was afraid to brick the phone this is the name of the file
RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10 it ends with dot exe
Click to expand...
Click to collapse
Post your question in the HTC One M7 Q&A forum.
forum.xda-developers.com/htc-one/help
You can flash the stock firmware to restore it to full unmodified stock. To find out how, do a Google search for:
"Return to stock HTC One M7 Sprint"
That should find your firmware, the tools needed and instructions.
Sent from my SCH-I535 using Tapatalk
Hello dear XDA users,
today I am looking for some help to get my HTC One M8 working again.
Let me explain my situation:
So a year ago or so, I decided to root my phone to unlock it's full potential. I wasn't really experienced, since it was
the first time I did it, so I just follwed a tutorial and used this rootkit. It worked well and my phone was rooted. Since then, I didn't really pay
much attention to it and decided not to mess around with it anymore. Recently I wanted to update my phone, since I
didn't do that since I had rooted it, because it wouldn't let me. I think I may have been because I had TWRP instead of the default recovery. Well, I wanted to remove that and naive me decided just to press the factory reset. After that, some strange things started to happen. First of all, my phone wasn't rooted anymore, which to be honest, I kind of expected. When I plugged it into my computer and tried getvar all, it didn't show my version-main anymore and sometimes not even my CID. Also, my TWRP folder wasn't showing anymore. I tried to use TWRP to repair the all partitions and also tried formatting data, but to no avail.
I want to restore the phone to a state where bootloader is locked, it's not rooted, where it's S-ON and it's OS is up-to-date.
I've been searching for a way to fix my problem for 4 days now, but I havn't found any way.
Getvar output, in case that helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT46KWM09326
(bootloader) imei: 357871053391945
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.033s
iDubstep said:
Hello dear XDA users,
today I am looking for some help to get my HTC One M8 working again.
Let me explain my situation:
So a year ago or so, I decided to root my phone to unlock it's full potential. I wasn't really experienced, since it was
the first time I did it, so I just follwed a tutorial and used this rootkit. It worked well and my phone was rooted. Since then, I didn't really pay
much attention to it and decided not to mess around with it anymore. Recently I wanted to update my phone, since I
didn't do that since I had rooted it, because it wouldn't let me. I think I may have been because I had TWRP instead of the default recovery. Well, I wanted to remove that and naive me decided just to press the factory reset. After that, some strange things started to happen. First of all, my phone wasn't rooted anymore, which to be honest, I kind of expected. When I plugged it into my computer and tried getvar all, it didn't show my version-main anymore and sometimes not even my CID. Also, my TWRP folder wasn't showing anymore. I tried to use TWRP to repair the all partitions and also tried formatting data, but to no avail.
I want to restore the phone to a state where bootloader is locked, it's not rooted, where it's S-ON and it's OS is up-to-date.
I've been searching for a way to fix my problem for 4 days now, but I havn't found any way.
Getvar output, in case that helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT46KWM09326
(bootloader) imei: 357871053391945
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.033s
Click to expand...
Click to collapse
Hello,
You can read here Stock backup collection thread pr try [tutorial] How to get back on stock with TWRP Stock Nandroid Backup and read the entire threads carefully.
If you still run into issues, please post your query here [HELP THREAD] HTC One M8 - Ask any questions here!, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
My Pixel 3's battery was starting to swell up, so I bought a new one from ifixit. Installation was pretty easy, but when I got the new battery in and powered on, it went into Fastboot mode. Here's what I see:
Code:
Product revs: blueline MP1.0(ROW)
Bootloader version: b1c1-0.3-6863019
Baseband Revision: g845-00146-201008-B-6891496
Serial number: [redacted]
Secure-Boot: PRODUCTION
NOS-production: error
DRAM: 4Gb Micron LPDDR4X
UFS: 128GB Micron
Device-State: error!
Boot-slot: a
Enter Reason: failed to load/verify boot images
Using the Fastboot menu to reboot into either Rescue or Recovery brings me right back to the Fastboot menu.
I dabble in Android development, and so I already have the Android SDK and it's up to date.
Here's the output of all the things I've tried:
Code:
fastboot.exe flash bootloader bootloader-blueline-b1c1-0.3-6863019.img
Sending 'bootloader_a' (8517 KB) OKAY [ 0.299s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
fastboot flashing unlock
FAILED (remote: 'Error getting device locked state No Response')
fastboot: error: Command failed
fastboot flash radio radio-blueline-g845-00146-201008-b-6891496.img
Sending 'radio_a' (71452 KB) OKAY [ 1.809s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
fastboot flashing unlock_critical
FAILED (remote: 'Invalid argument unlock_critical')
fastboot: error: Command failed
fastboot wipe-super
Sending 'system_a' (264 KB) OKAY [ 0.118s]
Writing 'system_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
fastboot boot .\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.604s]
Booting FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
fastboot update image-blueline-rq1a.210105.003.zip
--------------------------------------------
Bootloader Version...: b1c1-0.3-6863019
Baseband Version.....: g845-00146-201008-B-6891496
Serial Number........: [redacted]
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.059s]
Checking 'version-bootloader' OKAY [ 0.059s]
Checking 'version-baseband' OKAY [ 0.057s]
Setting current slot to 'a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Here's the output of fastboot getvar all:
Code:
C:\Users\DJ\AppData\Local\Android\Sdk\platform-tools>fastboot getvar all
(bootloader) product:blueline
(bootloader) serialno:[redacted]
(bootloader) variant:SDM UFS
(bootloader) max-download-size:0x10000000
(bootloader) slot-suffixes:_a,_b
(bootloader) version-bootloader:b1c1-0.3-6863019
(bootloader) version-baseband:g845-00146-201008-B-6891496
(bootloader) secure-boot:PRODUCTION
(bootloader) secure:yes
(bootloader) hw-revision:MP1.0
(bootloader) is-userspace:no
(bootloader) slot-count:2
(bootloader) current-slot:a
(bootloader) unlocked:error
(bootloader) nos-production:error
(bootloader) off-mode-charge:1
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) battery-voltage:4377
(bootloader) battery-soc-ok:yes
(bootloader) snapshot-update-status:none
(bootloader) storage-vendor:MICRON
(bootloader) storage-model:128GB-UFS-MT
(bootloader) storage-rev:9QSN
(bootloader) citadel-fw:error
(bootloader) auto-shutdown:0
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd:0x2000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc:0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore:0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp:0x80000
(bootloader) partition-type:system_a:raw
(bootloader) partition-size:system_a:0xB0000000
(bootloader) partition-type:system_b:raw
(bootloader) partition-size:system_b:0xB0000000
(bootloader) partition-type:product_a:raw
(bootloader) partition-size:product_a:0x12C00000
(bootloader) partition-type:product_b:raw
(bootloader) partition-size:product_b:0x12C00000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a:0x30000000
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b:0x30000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a:0x4000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b:0x4000000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a:0x5000000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b:0x5000000
(bootloader) partition-type:apdp_a:raw
(bootloader) partition-size:apdp_a:0x40000
(bootloader) partition-type:apdp_b:raw
(bootloader) partition-size:apdp_b:0x40000
(bootloader) partition-type:msadp_a:raw
(bootloader) partition-size:msadp_a:0x40000
(bootloader) partition-type:msadp_b:raw
(bootloader) partition-size:msadp_b:0x40000
(bootloader) partition-type:klog:raw
(bootloader) partition-size:klog:0x400000
(bootloader) partition-type:metadata:raw
(bootloader) partition-size:metadata:0x1000000
(bootloader) partition-type:userdata:raw
(bootloader) partition-size:userdata:0x1BCA7FB000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a:0x380000
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-size:xbl_config_a:0x20000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b:0x380000
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-size:xbl_config_b:0x20000
(bootloader) partition-type:ALIGN_TO_128K_1:raw
(bootloader) partition-size:ALIGN_TO_128K_1:0x1A000
(bootloader) partition-type:cdt:raw
(bootloader) partition-size:cdt:0x20000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr:0x100000
(bootloader) partition-type:modemcal:raw
(bootloader) partition-size:modemcal:0x200000
(bootloader) partition-type:uefivar:raw
(bootloader) partition-size:uefivar:0x100000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec:0x4000
(bootloader) partition-type:aop_a:raw
(bootloader) partition-size:aop_a:0x80000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a:0x200000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a:0x80000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a:0x200000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a:0x80000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a:0x80000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a:0x80000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a:0x20000
(bootloader) partition-type:qupfw_a:raw
(bootloader) partition-size:qupfw_a:0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a:0x10000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a:0x800000
(bootloader) partition-type:storsec_a:raw
(bootloader) partition-size:storsec_a:0x20000
(bootloader) partition-type:aop_b:raw
(bootloader) partition-size:aop_b:0x80000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b:0x200000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b:0x80000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b:0x200000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b:0x80000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b:0x80000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b:0x80000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b:0x20000
(bootloader) partition-type:qupfw_b:raw
(bootloader) partition-size:qupfw_b:0x10000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b:0x10000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b:0x800000
(bootloader) partition-type:storsec_b:raw
(bootloader) partition-size:storsec_b:0x20000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2:0x1A000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist:0x2800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1:0x200000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2:0x200000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg:0x200000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc:0x20000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo:0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip:0x100000
(bootloader) partition-type:spunvm:raw
(bootloader) partition-size:spunvm:0x800000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits:0x1000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv:0x100000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs:0x800000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti:0x200000
(bootloader) partition-type:ImageFv:raw
(bootloader) partition-size:ImageFv:0x200000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash:0x4000
all:
Finished. Total time: 9.252s
I've spent at least 4 hours on this, combing through at least a dozen threads here and on reddit, searching Google for people who have had similar problems, but haven't found a solution that works for me. Everything is getting me the error getting device locked state No Response. Doing any of the flash commands and trying slot b or all slots hasn't changed anything. Same error when it tries to set the slot.
I found one thread where someone let their battery drain on the Fastboot menu, then plugged back in and charged and it worked. I tried that and no dice.
I also tried swapping back to the old battery just to try it (obviously not a permanent solution since the old battery is a spicy pillow), and still dead.
At this point, I'm fairly sure the phone is bricked, but I'm praying someone knows something else for me to try. If I can't get this fixed by Sunday, then I guess my next question is...Galaxy S20 or Pixel 5 for my Google Fi?
Were all the connectors properly connected if you had to remove any?
ESD exposure can cause hardware damage; was it dry and were you wearing a wool sweater with leather shoes when you tore it apart?
Sort of joking but if you can sense static electricity it's already enough to cause damage. Incircuit ESD sensitive components however are better protected than free standing ones ie if you disconnected ribbon cables.
-or-
The firmware may have got corrupted.
blackhawk said:
Were all the connectors properly connected if you had to remove any?
Click to expand...
Click to collapse
Yeah. The only connectors I had to remove were the wireless charging coil, power button, fingerprint scanner, and of course the battery itself.
ESD exposure can cause hardware damage; was it dry and were you wearing a wool sweater with leather shoes when you tore it apart?
Click to expand...
Click to collapse
No. Just sitting in my office chair, bare feet. Cotton clothing. Heh. While no, I didn't take any extra ESD precautions, I don't exactly have a high-static environment.
The firmware may have got corrupted.
Click to expand...
Click to collapse
I assume that likely means bricking.
Is it possible one of the connections is bad?
Take a hard look at it. The micro connectors are easy to damage if you're not careful.
My knowledge of flashing these devices is near zero so I can't be of any help with recovery.
If a hard reset doesn't get it it's either hardware and/or corrupted firmware.
blackhawk said:
Is it possible one of the connections is bad?
Take a hard look at it. The micro connectors are easy to damage if you're not careful.
My knowledge of flashing these devices is near zero so I can't be of any help with recovery.
If a hard reset doesn't get it it's either hardware and/or corrupted firmware.
Click to expand...
Click to collapse
I looked at it through the lit magnifying glass I use for soldering. The connectors all look fine.
I've basically resigned myself to buying a new phone, though I've been agonizing over paying $700 for a Pixel 5 and getting a beautiful Android experience, or paying $400 for a Galaxy S20 and getting amazing hardware, but supposedly full of bloatware. Though about getting an S20 and flashing LineageOS to it (I haven't used a custom ROM since the OG Droid days, where I tried out CyanogenMod), but apparently the S20 Snapdragon is still considered unsupported.
Sohcahtoa82 said:
I looked at it through the lit magnifying glass I use for soldering. The connectors all look fine.
I've basically resigned myself to buying a new phone, though I've been agonizing over paying $700 for a Pixel 5 and getting a beautiful Android experience, or paying $400 for a Galaxy S20 and getting amazing hardware, but supposedly full of bloatware. Though about getting an S20 and flashing LineageOS to it (I haven't used a custom ROM since the OG Droid days, where I tried out CyanogenMod), but apparently the S20 Snapdragon is still considered unsupported.
Click to expand...
Click to collapse
Did you solder to the battery or mobo?
If you solder to the mobo you need to be fast and be skilled at soldering. A temp controlled iron is almost imperative as is lead based solder preferably fine gauge 60/40 rosin core. Mobos can be multilayered meaning interior layers with fine traces. These can be heat damaged.
It's either a double sided surface mount or a multilayered PCB.
I was more concerned with other connections. However you see the potential for damage if you soldered to the mobo.
I would try reflashing the firmware. May not be damaged at all but it won't load until the firmware is fixed. It's powering on so that's a good sign... you just need to play with it some more.
Yes, Samsung has bloatware. Some like Samsung Pay and Knox you can't fully disable; permanently set as system administrator. Most all others can be disabled with a package disabler or ADB commands. Bixby goes bye-bye first, lol.
Samsung is the most customizable non rooted phone there is. From hundreds of free Galaxy Store themes and icon packs, to the Good Lock family of customization apks and more.
My 10+ screens are gorgeous; just the way I want it to look. The level of control is mind boggling.
If you get a Samsung get one with an SD card slot; having a data drive is the only way to go.
I'm running on Pie; Q is not as usable and wastes cpu cycles. My 10+ is fast, stable and fun but it took a lot of effort on my part to sort it out.
With Pie you have more tools to track down battery/bandwidth hogs, with Q or 11 it will be harder.
Right now I would not buy any of the lastest Samsung models. Maybe next year will be better.
Worse Android has been nose diving with/since Q; seems Goggle is hell bent on controlling everyone and everything it can.
Google is now quit an ugly big sister.
I didn't do any soldering on the phone. I probably should have left out the detail that I normally use the magnifying glass for soldering.
I would try reflashing the firmware
Click to expand...
Click to collapse
As mentioned in the first post, that's what I've been trying to do, but it all fails. Any commands with fastboot that actually attempt to write fail with an error getting device locked state No Response error.
Bixby goes bye-bye first, lol.
Click to expand...
Click to collapse
Definitely.
I'm still leaning towards the Pixel 5.
I've accepted the phone as bricked, and my wife came up with a plan that I really should have thought of sooner that solves my S20 vs P5 dilemma. -_-
She's been wanting to upgrade from her Pixel 3 to a Galaxy S20, since she tends to store a lot of music, photos, and videos on her phone and wants the expandable storage. So she's going to upgrade to the S20, and I'm going to take her Pixel 3, which I will likely upgrade to a Pixel 6 later down the road.
I ordered her S20 last night with expedited shipping, and it should arrive tomorrow or Wednesday.
any solution? The exact same thing happened to me to change the battery
andyhack said:
any solution? The exact same thing happened to me to change the battery
Click to expand...
Click to collapse
Nope. :-(
I accepted the phone as dead and took my wife's Pixel 3 when she got a Galaxy S20.
Sohcahtoa82 said:
Nope. :-(
I accepted the phone as dead and took my wife's Pixel 3 when she got a Galaxy S20.
Click to expand...
Click to collapse
Meh sometimes it's better to cut your loses
:c
out of curiosity did anyone check the volume down was not stuck
Sorry to revive an old thread, but the same thing happened to me as well.
I was pretty sure I will not be able to do anything, exactly like you said, no commands were working.
At this moment I was on Boot-slot: b.
What's weird is that after a series of restarts, it somehow booted to rescue mode, and I was able to use the official Google Pixel Repair Tool. And for a while there, I got my phone back. Didn't start to use though, I had a feeling it was not reliable.
After a couple of days I saw that my phone was not charging, even though it was plugged in.
I was pretty certain that if I restart it, it would be broken again, but I took a change and tapped restart.
It again went into fastboot mode, but now it's in Boot-slot: a.
Since then, I never managed to get to rescue mode again...
The only thing I hate about the whole situation is that I didn't enable OEM-unlocking when it magically worked again. :|
I am new in this forum. I have some questions about this forum. These questions are shown below:
My question is about this thread. If you have any information about this thread. Please quote me and solve my problem.
A new update, since yesterday I obsessed a bit about this. I left the phone on the wireless charger most of yesterday and the phone kept being locked in fastboot mode. Before going to bed, I tried RESCUE MODE again. And surprise, the phone booted to rescue mode, with the green android.
Immediately I connected the phone to the computer and managed to reinstall the software using Google's Pixel Repair online app. Now the phone is working.
Interestingly, it booted on slot-b. So slot-a must still be corrupted.
But the first thing I did was to enable unlocking and unlocked the bootloader. So now, even if it happens again, I will be able to reinstall software at any time.
So @Sohcahtoa8, maybe if you still have the device, you'll be lucky like I was.
geojoking said:
A new update, since yesterday I obsessed a bit about this. I left the phone on the wireless charger most of yesterday and the phone kept being locked in fastboot mode. Before going to bed, I tried RESCUE MODE again. And surprise, the phone booted to rescue mode, with the green android.
Immediately I connected the phone to the computer and managed to reinstall the software using Google's Pixel Repair online app. Now the phone is working.
Interestingly, it booted on slot-b. So slot-a must still be corrupted.
But the first thing I did was to enable unlocking and unlocked the bootloader. So now, even if it happens again, I will be able to reinstall software at any time.
So @Sohcahtoa8, maybe if you still have the device, you'll be lucky like I was.
Click to expand...
Click to collapse
When you get your phone back, the data that was there before will be lost?