A lot of these I'm sure are general but since the HTC 10 is what I have and I'm using firmware and ROMs from within this subforum I thought this would be the most appropriate place to post. I have rooted/unlocked all of my (non-Nexus) phones over the years and like to think I have a moderate amount of experience with the process, but this is driving me up the wall and my searches for similar problems are turning up nothing but unrelated issues. My HTC 10 is unlocked and S-Off. I was running the ROM from this thread (the 6.0.1 version) for quite some time but stopped using the phone due to unrelated issues (screen is too big, can't get over the polarized screen and not being able to use the phone with sunglasses on). I'm now trying to sell it and therefore trying to get current firmware and a stock ROM onto it so potential buyers are not freaked out about modifications to the phone. I'd like to leave it unlocked and S-Off though.
I am able to successfully flash the firmware (from this thread), and have been going back and forth between the full stock ones and the ones with TWRP built in. As of right now the phone has no bootable ROM and I have been unable to load one. I can successfully get into Download, Recovery, and Fastboot modes. I see that I have three main paths to potentially flashing a stock ROM:
- Repair/Upgrade via HTC Sync with the phone in download mode
- Load the ROM onto the phone's SD card and use TWRP to flash
- Use ADB to sideload the ROM directly from Windows
My problems with these three options are thus:
- HTC Sync does recognize the device when put in Download mode. It even successfully downloads the update it perceives the phone needs. But at 20%, it claims the phone has too low of battery (it doesn't, it's locked at 100% and has been plugged in the whole time) and quits. It does this regardless of whether I select Upgrade or Repair. Tried multiple times, with both stock recovery and TWRP. I found one other case of this, and the only response was the OP saying he just sent his phone back to HTC. I don't think this is an option for me because it has sat unused basically since I bought it over six months ago.
- The phone does not read the SD card. Other devices read it just fine, but I don't have any SD card reader that can directly talk to my computer to do the file transfer through. I have not found any guides that allow me to mount the SD card without having a bootable ROM. Maybe this is where I simply don't know enough about ADB/TWRP and someone can point out a simple solution? I'm hopeful.
- I can get the phone into Recovery and then into "Sideload" mode. But trying to run "adb devices" or "adb sideload 2PS6IMG.zip" returns some variation of the following (the 31 and 39 are always there, sometimes it had more detail and sometimes it has less):
>adb server version (31) doesn't match this client (39); killing...
>error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
>This application has requested the Runtime to terminate it in an unusual way.
>Please contact the application's support team for more information.
I can't find anyone having these errors in this combination, but from what I can gather it's somehow tied to not having an up-to-date version of ADB... but I keep going and downloading the absolute most recent one (either from one of the threads here or Android Studio) and it just doesn't work. If I use one of the HTC_fastboot packages instead to try running the commands I just get "cannot read 'sideload'". I assume there is some kind of package or library missing from those directories.
Really I will take advice on troubleshooting any of these three angles, or one I have not though of. I'm sure all of the problems are stemming from one very annoying source but I just don't know what else to try. Thanks for any help you can offer.
I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.
Valdair0 said:
I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.
Click to expand...
Click to collapse
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.
Tarima said:
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.
Click to expand...
Click to collapse
Make sure it's named 2PS6IMG.zip
Thanks guys, it seems to be working okay now. It was upgrading to 7.0 when I left the house this morning. I'm going to flash stock recovery one last time tonight and hopefully it will be set.
Related
I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:
Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck
Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app
olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you
I have been running CM 11 on my XT907. A 2/10/14 update installed and a day or so later the phone went into some really bizarre read only state. I can boot the phone, but it constantly crashes on gapp and acore processes, I can get into settings but do very little. ADB does not seem to be able to load, when I try to run things that need ADB the phone constantly goes online and offline. I can boot into fastboot and run RSDLite and Matt's utility. They both actually run like they are writing back the original images(no errors) but the phone reboots to CM11. I am running CWM 6.0.4.4, very little I can do here. Anything I try to flash runs but doesn't actually apply. I tried Moto WP Nomo and it just says what are you doing here, I am assuming because it isn't written for the 907. I am stuck at this point, phone has been a brick for a month. Can I just replace the internal SD card at this point...or take it out and format in my PC and start over? I am done trying to unbrick this thing at this point.
Wp no mo will work on the m. Jcase said it would. Search my post in the related thread. It is your only hope. There is a xt926 user in q & a same issue.
I have tried to run it on multiple PC's at home and I have no idea what the problem is but it bombs out. It gets past the update check(which errors out if you are behind a FW), it gets into ADB mode because I get the prompt on the phone to accept it the connection...but then it comes back with something like "Why are you doing here? Why me????? Why?????" Or something to that effect. While I appreciate the developer who wrote the app, the error checking messages he built into are ridiculous. I have read other posts on the utility who get cryptic messages from doing basic things like not running it out of the right working directory.
Morning
I had a corrupt TWRP 2.8.6.1 and then removed it using flashify CWM. That removed the ROM AND recovery, Now I have an 'empty' phone with the secure boot message. I have tried what seems to be the only resolution http://forum.xda-developers.com/showthread.php?t=2432476 (back to stock) but the tool doesnt recognise my phone. I have the google drivers installed and the LG drivers and have switched between both. After the small white writing saying 'security boot error' the PC scans loads of drives before stopping. I then see my phone with the file 'image' in it. Within that are lots of scary looking files called adsp, cmnlib and modem. So there is some detection... However unfortunately (and perhaps critically) adb does not see the device.
This is clearly a serious issue and maybe beyond some of the biggest brains on here. However if someone does have an idea, could they help me (and guide me through it like I'm a 10 year old ) Otherwise this will probably become a fake phone for my 7 year old!
Any ideas please?
Hello,
I'm looking for help. I wish I could ask on the development page, but I don't have access to do so because of my low post count.
I've had a problem with my HTC Bolt screen. I made a video of the problem and put it on youtube:
https://www.youtube.com/watch?v=1eR5NFDcnvU
I thought it may be a problem with the firmware/stock rom that is loaded with bloatware, so I decided to tinker with rooting, etc...
First thing I did was gain root using this method:
https://forum.xda-developers.com/bolt/how-to/root-supersu-v2-78-sr5-s-off-sunshine-t3513048
Then I downloaded and ran Sunshing to get S-off.
I then tried to install a new Rom, but it wouldn't install, giving the " E:footer is wrong .. E: signature failed" on the android recover.
The phone on my screen continued to glitch, so I tried to go back to stock using the RUU as described here:
https://forum.xda-developers.com/bo...t-htc-bolt-1-17-651-11-updated-t3502778/page4
but the process hung when trying to install a new rom using the RUU . I assume this happens because of the same "E:footer is wrong .. E: signature failed" problem when I try to flash a ROM.
Please help. I can't boot up into the system and am new to this. Also, if you can point my problem to the developers, that would be great.
recovery screen shows this:
*** Software status: Official ***
*** Unlocked ***
*** S-Off ***
This looks good to me to give me access to flashing, but the error keeps getting in the way.
Thanks,
Marc
what recovery are you using?
when you reboot to download mode and use fastboot, type fastboot devices. Does the serial number and fastboot show up?
what method are you using to RUU?
I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?
marcram said:
I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?
Click to expand...
Click to collapse
Is the screen always black, or intermitting?
in download mode
fastboot oem lock( it will say relocked and not Locked though)
OK, thanks. Maybe some chmod can solve it. Sprint is charging since it is more than 20 days old. Going to HTC instead since under their warranty.
The problem is intermittent, but is getting worse with each hour. Others are having the same issue.
I've been seeing the same issue with the display not waking since the .22 update...it's very intermittent on mine though, maybe 10% of the time...I haven't been able to narrow it down.
did u flash twrp recovery before flashing a ROM?
Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.
marcram said:
Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.
Click to expand...
Click to collapse
no, twrp is best installed by flashing it in download mode, u cannot flash a ROM via stock recovery, only custom recovery(twrp)...https://forum.xda-developers.com/devdb/project/?id=18340#downloads
Thanks, twrp did the trick. But with 3 different roms, I'm still having screen blackout issues. Going to need help getting back to locked and s on after RUU. Guess I'll start a new thread for that.
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
alajoy said:
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
Click to expand...
Click to collapse
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Teet1 said:
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Click to expand...
Click to collapse
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
alajoy said:
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
Click to expand...
Click to collapse
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Teet1 said:
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Click to expand...
Click to collapse
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
alajoy said:
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
Click to expand...
Click to collapse
Yeah fastboot screen was removed in newer versions. But that's at a software level of the phone. On your computer, the adb and fastboot commands are universal. It's usable on Mac, Linux and windows. The tools used for the phone like miflash or axon7tool are made for windows though and you kinda need those to fix bricked phones. There's a way to force push the twrp image into the recovery partition via adb but I don't know what the name of the recovery partition is
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
AnonVendetta said:
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
Click to expand...
Click to collapse
By name i meant the path, are you sure that's the path for our device? I tried that once and it was not that. Either way he is able to do it
@Teet1: Yeah, I'm sure, but not on all 3 paths. /dev/sde14 may be correct or not, depending on firmware/boot stack that is installed (or the presence of a vendor partition, which might change the paths). But the other 2 should be as I listed.
Just open a root file manager and see for yourself. I use Total Commander, which also shows symbolic links (the one with "bootdevice" in the path is really just a symlink to 624000.ufshc). Getting the recovery path from the example with "bootdevice" in the name should also work on almost any device running Android, and will generally point to the recovery partition. You can see the paths in TWRP too, but TWRP doesn't show symlink (but you should be able to see them if you use the right commands in any terminal, like TWRP's terminal).