I've been trying to install LineageOS on an old Swift and it's been quite a saga.
I first tried about a year ago and gave up. This time I wasn't surprised to have to try several USB cables to find one that the phone would talk to, but that was just the start.
The installation guide doesn't tell you that it won't boot into recovery mode unless the cable is plugged in. Having got it into recovery mode, it won't talk to adb with any of my cables, even though I had previously managed to update the recovery, so I decide to try loading it from SD. The SD card from the phone wouldn't mount and I thought it might be defective as the laptop kept wanting to reformat it. After I changed the SD adapter I was using with the laptop it had no more issues with the laptop. but still wouldn't mount in the phone. Changing the SD card as well got me past that, but now I'm completely stuck.
I tried the nightly for 27th Jan. It failed to verify. I checked it with sha256sum and it was correct. I tried again with the nightly for 29th Jan, but that also failed to verify although sha256sum also suggested that it was correct.
Has anyone else managed to load those images? Is there any check I can do other than sha256sum?
I gave this phone away 2 weeks ago, so it's unlikely to get Lineage OS now.
Related
After flashing fresh's new fresh toast kernel over fresh 0.5.3, my usb stopped working. The LED turns on when plugged in and it charges, I just can't mount SD, ADB doesn't detect it, etc. It's happened before and last time I followed http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=695243 that guide to fix it. I tried it this time a few times with no success. I even restored my nandroid from right after I rooted and following the guide still didn't work. Any suggestions/help would be appreciated.
that has happened to me when I was messing around with my rom and removed some things I shouldn't have. My resolution was wiping everything and flashing a new rom.
crazy and odd as it sounds, it happened to me and I was going crazy trying to figure it out. I gave up and the next day went to plug another phone into the same usb cable and the computer didn't recognize it either. I left the computer on all night so it hadn't been turned off since I had the problem on my evo.
Sure enough, I rebooted the computer, it recognized the evo and was able to mount the drive.
So, if you haven't tried, reboot your computer.
I have a new Evo and it came with the latest radio installed. Because of that I did the unrevoked3 root process. While trying to get Fresh Evo in place I have really knackered this phone.
After it has booted it no longer sees the SD card. It also doesn't charge over USB unless I have it plugged into a wall socket. The PC doesn't detect the phone at all.
I've tried other SD cards and it doesn't fix the problem. I have also tried other Android phones and cables and it is only this phone that no longer works.
Any suggestions on how to recover? Any recovery that requires that I go into recovery will not work. (Did I mention that I can boot into hboot, etc, but not recovery?) Anything that might try to use USB won't work either. I can put a PC36IMG type file in place and fastboot will scan it. However the few I've tried haven't got me anywhere.
Try this: http://forum.xda-developers.com/showthread.php?t=695243
I lost my SD and USB after I rooted, but that got me back on track
Success! Or at least in part.
Thanks mistersquirrle.
The USB still doesn't work but I'll try it again and see if that fixes things. These things often take a few tries...
vanstrien said:
Success! Or at least in part.
Thanks mistersquirrle.
The USB still doesn't work but I'll try it again and see if that fixes things. These things often take a few tries...
Click to expand...
Click to collapse
I think that my USB took more than one try, not sure. Glad I could help though, I keep that link on my bookmarks, just incase
BTW, edit the post if you can and put [FIXED] if you get it all good, so it's not misleading
I did it a couple more times and it finally took. Thanks!
Here's the issue for me. My computer is not recognizing my properly, or it could be the only way around. The phone only charges, and is never picked up as a usb disk drive. I have confirmed that it's a problem with my phone itself, as my friend's EVO 4G, hooked up to my computer using the same cable, connects and is recognized as a disk drive just fine. We tried swapping out microSD cards to see if it could be something with that, and his phone was still picked up fine with my microSD in it. I think my phone may be partially rooted.
I tried SimpleRoot 1.47.651.1 on my phone at my friend's house a few days ago (4-click method), and for some reason, it never completed. His computer would pick up my phone as a disk drive perfectly fine, but on the last step (reboot and scan) it would never finish, even after letting it sit for a few hours; step 3 was saying something about not being able to identify the correct cache from the browser or something like that. I'm thinking that the partial root may've flubbed up the phone?
Right now, I'm trying to look up which root method my friend tried to work on my phone. It involved PC36IMG.zip and an update named s-u-*something*. I'm still new to the EVO, not like the Droid. Anyway, that root method failed for some reason (no errors in HBOOT, but never asked if I wanted to reboot). I've tried to factory reset, and nothing. I got my phone sitting here while I'm scratching my head trying to figure out what to do. I'm well-versed in ADB, but if my computer can't pick up my phone properly, it's all for naught. Anyone have any ideas to get me on the right foot? I can still pop out the microSD and put it into the computer directly, too. Sorry for the tl;dr candidate.
Quick update/bump.
I upgraded my phone to OTA Froyo, and now USB debugging shows up, but I don't get the "Connect to PC" menu still. Is this phone fubared?
HTC Sync not recognizing phone
I was having the same problem with 2 Evos. The phone would accept a charge from the USB port and the computer would even install the driver sometimes. Then nothing. I tried again last night after I pulled the 2.2 update and it worked! I think HTC might not have had Windows 7 Starter edition covered until this update.
Here's the thing, I'm on Windows 7 Ultimate x64. I'm having this problem on 2 EVOs, also. I've updated them both to stock 2.2 OTA, and still nothing. =/
I did just read on here somewhere that a fix was to delete the drivers for the phone and sd card and reinstall them.
Edit: I had switched to a different (charge-only) cable halfway through and not realized it. Switched back and the phone was recognized again.
Steps:
I unlocked my bootloader with Wug's toolkit.
I installed the zips that it asked me to (that it put on my SD card).
I updated SuperSU
I got a notice to update the SuperSU binary.
SuperSU binary won't install via Play.
Tried to install via TWRP and recovery isn't twrp, seems to be stock recovery (thought I installed it, maybe not)
Now the toolkit won't recognize my device. neither will windows. It gives me the USB noise but won't show the device in the folder list and defaults to USB for Charging. I can change it but it doesn't make it recognizable.
I'm trying ot back out and try again but the toolkit says it finds the device but that it's listed as "offline". When I toggle the USB debugging, it doesn't ask me to fingerprint my computer.
When I try the "soft brick" option to flash from the bootloader, the script reports a failure "data transfer failure (unknown error)", then says "rebooting into bootloader..." and does nothing else BUT my phone's bootloader still says "downloading..." When I reboot, the script throws another failure and says "waiting for device". when I bootload into it again and connect, the script throws more failures.
I've been on this for 4 hours, getting pretty fatigued (through the night on a weekend when family is visiting. yes, I'm an idiot for trying this procedure but the 5 went so smoothly I was optimistic).
try reinstalling the drivers. also the OEM-lock option in the dev-settings may help bringing you back to step one.
I was halfway through installing the drivers when I quit for sleep last night.
I'm using the LG-Mobile-Driver_v3.14.1.exe package, and the installer says it installed successfully, but windows says that MTP and PCI Simple Communications Controller had "No driver found", so the device doesn't show up in my drive list and wugfresh won't detect it.
I've removed all Google, LG, MTP, and Nexus drivers in USBDeview, but can't seem to figure this out.
I was able to get the drivers installed on my wife's system, so I'll open another thread about this if I can't get them to work.
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
oubravs2b said:
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
Click to expand...
Click to collapse
so, the reason my computer stopped recognizing the phone was that I switched to a charge-only cable without realizing it. Switched back and the phone recognized fine.
The weird thing is, the charge-only cable worked fine for data xfer on my wife's system.
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
carnagex420x said:
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
Click to expand...
Click to collapse
Do you have ADB set up? if not, now may be a good time and through ADB try download a factory image.
carnagex420x said:
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank. I ended up deleting all of the partitions but now i cant even see the device at all.
Click to expand...
Click to collapse
Connect it to a PC again and check the USB mode your N7 is in.
If it is, or if you can make it work in, USB mode 9006 then follow this post. The linked N7 image is from my 32GB Hynix but you can use it to restore boot on any eMMC and adjust it later. While you do not see the partitions anymore, you may be able to access the device to restore the image.
If it is USB mode 9008 then your only recovery option is JTAG or hardware programming of the eMMC chip.
Good luck, it is still fixable :good:
the device still appears completly lifeless however i am able to get the device to show up as
Code:
Bus 002 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
but im not sure how to go about getting fastboot yet, i get that i can dd an image to it i guess but im pretty sure i only have the 16GB not the 32, wjich i cant seem to find.
After playing with it for a couple hours and reading the entire Unbricking thread, the spot im stuck at now is the 9008-9006 mode switch. I have the QPST software and drivers working right and i get the NAK error but i follow the directions and cant get it into 9006 mode...
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
ramon.hugo said:
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
Click to expand...
Click to collapse
When you can boot into recovery you are good to go. Use a pendrive and an otg cable and flashthe rom from pendrive.
Already tried that ... Also impossible.
Try this way,
Connect to Computer
Use NRT then pess root, your Device will restart in TWRT then you can put the file in and reinstall.
You may be running into flash wear issues. This device is about 4 years old at this point, a similar thing started happening to the 2012 models. Don't blame the ROM, blame the NAND chip in your tablet.
I have a busted USB port so prefer to recharge via wireless. Sometimes wireless charging keeps disconnect and reconnecting if it's on so I need to shut it off.
I did that and now it just hangs at the Google screen as well.
If I hold Vol down I dont get twrp but the general bootloader. Any choice seems to just reboot it.
I think I'm screwed as well.
Prior to this my pc doesnt detect via USB at all, just charges it.