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?
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 took a bunch of backups before hand, but I put them on my laptop, so they're not on my phone. I've tried connecting my phone to my laptop, but I can't access the filesystem of my phone through my laptop. I can, however, boot my phone into TWRP recovery through a .bat file on my computer. The only thing I've managed to be able to do from there is wipe the phone and flash stuff. The only thing I've got on my phone that's useful is two .zips, the PA 4.4 zip and the Gapps that follow. As far as I can tell, the only thing I need to do to get my phone working again is to get my backup files back onto my phone somehow, but I cannot seem to get that working.
I've tried the ADB push command, but it can't detect my phone, so that's not working.
I'm wondering why the .bat works, as I can tell by the log that it is sending files to my phone! Somehow it manages to do it, but I cannot send my own files. Why is that? Also, looking at the log from previous times, It sent the files with speeds of several MB/s, but now it's only sending them at like 100-200KB/s. Is my SD card damaged?
I've read through a bunch of guides, and several of them states that the stuck boot animation is caused by the cache, so I tried wiping that. However, for some reason, it's begun to say "Error: Operation failed" when trying to wipe it again.
Help please
## Fixed it.
Could you post the .bat file that you used? Sorry if its a bit off topic but you are the only person that I can find with a similar problem as me and I have my phone stuck in the boot animation. I can't get my phone into recovery mode and was hoping that your .bat file could help me. I have a back up in twrp that I could use.
stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
fixed it..wooooohoooooo
Vishnuisgod said:
stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
thank you for the tips ! the tool kit actually worked i had no os (deleted everything).
and used the 9 option (flashing stock) it worked !
To start, I'm using the Verizon VS980.
While trying to get a custom recovery working on the latest OTA version, VS98026A, everything I tried seemed to fail. I used twrp manager to install the latest twrp into my recovery, but at the step where it reboots into recovery I got sent to fastboot instead. No problem, just try again right? Same problem. I did a little digging and it seems the 26A update locked down the bootloader tight, can't even get loki working, but flashing the 12B aboot was supposed to be a workaround. So I flash the 12B aboot through fastboot. Oops. I must have missed a step SOMEWHERE, even though I'm fairly experienced and careful, because now it won't boot.
At this point I'm thinking I'll just bite the bullet and restore it. Nope. Recovery mode is dead now, as is fastboot. I try to connect download mode, and it appears to work (download mode shows on the phone) but the computer doesn't recognize the phone even exists.
I'm a week away from my next paycheck to find a phone to pull the guts out of, and I have a full TWRP backup of all partitions, including EFS. What are my options, if any? Help... please?
(I also read - too late - that freegee is supposed to automatically downgrade bootloader)
No one has any ideas on fixing it?
I'll settle for ideas that will make it impossible to tell if it's rooted, like make it so it won't turn on or at least remove that ugly warranty-breaking "rooted" flag on the recovery warning. I'll just take it in for warranty claim after.
Anyone have any ideas? Maybe wiring the USB to short it out?
I seriously just need to break it, and soon because my employer can't contact me.
As a revelation that may fix/break the phone, I got the computer to recognize the phone. It came up as a bunch of unformatted drives, and one that was readable that contained an "image" folder.
since your computer can detect it now, why dont u try flash kdz using LGFlashtool ?
zekurosu said:
since your computer can detect it now, why dont u try flash kdz using LGFlashtool ?
Click to expand...
Click to collapse
Thanks for the suggestion, but it wouldn't work. It was detecting it as qhusb_bulk, not download mode.
I followed the steps here, http://forum.xda-developers.com/showthread.php?t=2582142, and partway through dd'ing the aboot my phone shut off. I guess the battery died. Now it won't turn on again AT ALL. Just what I wanted, kind of. At least now I can replace it under warranty.
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.