I was running CyanogenMod 10.1.x versions, using ROM Manager to upgrade as new ones were available. However, when I tried to upgrade to 10.2.1 it kept rebooting every several minutes, showing the new bootup screen with the rotating arrow. I tried upgrading to version 11...M9 also with ROM Manager and now it only comes up in recovery mode (CWM v6.0.3.1). There seems to be no way to finalize the installation. I can't sideload from the PC, since, although DeviceManager shows "Google Galaxy Nexus ADB Interface," I do not see any entries in Device Management or in the Explorer, so I can't offload a full backup, nor can I use adb to sideload the new CM. I can't instal from the internal sdcard, since it starts with "...Installing /sdcard/update.zip" and then can't find it - it comes up with the "(no such file or directory)."
Since (except for Device Manager) nothing on the PC recognizes a connection with the Nexus 10, I'm pretty much out of options. I can do a complete "wipe data/factory reset" I suppose, but would like something not so drastic (given no backup). When I look at CWM's display of mounted and unmounted storage, sdcard is unmounted and won't mount. I've even done a full wipe and factory reset, with the same results.
A brand-new install of the Samsung USB Drivers 1.5.33.0 through Skip's app now results in an error message when I reattach the tablet saying the driver install failed. I still show the device in Device Manager.
I have Skip's Universal Android Toolkit v1.0.2 and it seems to recognize that a Nexus 10 is connected, but can't do anything to it (it expects you are originally booted to Android, not recovery.
This is my first Samsung device, so I'm totally unfamiliar using Odin and haven't figured out how to use it to correct the problem.
It seems that, if I can sideload a copy of CM 11, I should be okay, but all roads look closed.
Any ideas?
I'm locked in a loop.
'
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Thanks - will keep trying.
demkantor said:
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Click to expand...
Click to collapse
I downloaded the latest Android SDK with platform tools and put the cm zip file in the directory with adb.exe. On the tablet, in ClockworkmMod Recovery, I selected "install zip from sideload." The tablet went into sideload mode and instructed me to type "adb sideload <filename>. So I typed: "adb sideload cm-11-20140805-SNAPSHOT-M9-manta.zip" and hit the enter key. The PC reported 100% downloaded. The tablet listed:
Restarting adbd...
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I'm at least communicating between the PC and tablet, but the update is still failing. Any hope of trying to flash standard ROM, re-root, and start again?
You need to update your recovery, grab the latest TWRP or CWM .img for manta and flash in via fastboot first, then boot to new recovery then flash ROM
Thanks, I grovel at your feet!
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Beartooth01 said:
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Click to expand...
Click to collapse
Great to see @demkantor help get you back up and running ..
@Beartooth01 Can you plz add "SOLVED" to the thread title
Thx Josh
Related
Is there a way to flash a factory image to the thrive using android recovery via pressing volume up and power button and selecting the middle option which takes you to the menu to install.zip from sd card, I get that far and it gives me an error (e verification failed) I do not have root or Clockwork, and cannot install either do to the system/xbin file being deleted so the tool has nowhere to instal the ROOT and it says File Location Does Not Exist when Trying to add the xbin files.
So Is there a "Signed" stock rom available that I can just install from the sd card via the "Stock Android Recovery"
If anybody has a signed stock android Toshiba Thrive Rom that I can restore to the device without ROOT or CLOCKWORK that would be awesome and I would be most greatfull!!!
No, there is no signed stock image available. You can flash the stock ROM, but you will need to flash ClockWorkMod recovery onto the device and load the stock image available on thisone.org or thatone.com.
Now the Clockwork Recover Mod and The Clockwork Recover Tool from marketplace are two separate entities as I understand it, so I can flash the recover mod without root correct? I'm going to give it a run and keep you posted.
DaveNavy said:
Now the Clockwork Recover Mod and The Clockwork Recover Tool from marketplace are two separate entities as I understand it, so I can flash the recover mod without root correct? I'm going to give it a run and keep you posted.
Click to expand...
Click to collapse
The one on the market will not work with the Thrive. YOu will need to get my Easy Flash Tool from thisone.org or thatone.com. It hase a version of ClockWorkMod recovery that will work with the Thrive. YOu are correct that you do not need to eroot to install it. You do need to knoiw that you have to go back into recovery before the device boots or the ROM will replace the recovery with the stock version.
all back to stock and updated to the. 11 update, thanks so much
issues
update: *deleted*, figured it out.
Need help with Toshibe Thrive
I have a Toshiba Thrive 10.1 (with 32GB RAM) that recently quit on me. All it will do for me now is boot up to the splash screen (the one saying it's a Toshiba and such) and then stops doing anything other than showing that screen. I've tried the data/factory reset option, but that doesn't change anything (it still boots to the same point and locks up). The factory reset ROM's I've tried all fail at "Verifying update package..." with the error "E:signature verification failed" followed by aborting... I've been able to fix computers since Win 3.1 (yeah, showing my age a bit) up until now with no real problems, but Android is a different animal... I've tried the "Thrive USB ADB" utility, Toshiba Easy Flash utility, and a few different factory reset ROM's... All have failed....
Also worth saying.... When trying the Easy Flash Tool and doing exactly as it says (except for not being able to tell the device to go into USB debugging mode), all the utility seems to do is sit and wait for my device.
What I may need is a step-by-step, get this file, do this thing, type of help...
Keeblerdawg said:
I have a Toshiba Thrive 10.1 (with 32GB RAM) that recently quit on me. All it will do for me now is boot up to the splash screen (the one saying it's a Toshiba and such) and then stops doing anything other than showing that screen. I've tried the data/factory reset option, but that doesn't change anything (it still boots to the same point and locks up). The factory reset ROM's I've tried all fail at "Verifying update package..." with the error "E:signature verification failed" followed by aborting... I've been able to fix computers since Win 3.1 (yeah, showing my age a bit) up until now with no real problems, but Android is a different animal... I've tried the "Thrive USB ADB" utility, Toshiba Easy Flash utility, and a few different factory reset ROM's... All have failed....
Also worth saying.... When trying the Easy Flash Tool and doing exactly as it says (except for not being able to tell the device to go into USB debugging mode), all the utility seems to do is sit and wait for my device.
What I may need is a step-by-step, get this file, do this thing, type of help...
Click to expand...
Click to collapse
There isn't one, it needs nvflashed back to stock, it will work provided there is no emmc damage/failure which does happen occasionally. There's only a few people with the Toshiba files to flash it back fresh, shoot me a pm and I'll help you out with that.
Sent from my Nexus 7 - JBSourcery 4.5
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Did you make a backup? You can also use any of the multiple toolkits available to you to reload the stock ROM. Also, questions should be in the QA section to avoid clutter.
Sent from my Nexus 7 using xda premium
graydiggy said:
Did you make a backup? You can also use any of the multiple toolkits available to you to reload the stock ROM. Also, questions should be in the QA section to avoid clutter.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
can you show me the tools (i am a noob at android) or maybe help me in skype or team viewer?
Get an OTG cable and load the Nexus 7 factory image from a USB drive.
kevinperyea said:
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Click to expand...
Click to collapse
Do you have the stock charger? That cable works for connecting to PC.
http://forum.xda-developers.com/showthread.php?t=1766475
This is your best bet.
Boot into recovery and mount then copy across your chosen Rom from your pc and flash
Sent from my HTC One X using xda premium
Easy way out
kevinperyea said:
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Click to expand...
Click to collapse
i always use this method to flash roms as it cuts the hassel of copying the rom into the device for flashing and its very easy actually......just Follow these Steps.. :fingers-crossed:
Download Wug' Nexus Toolkit
Install it and Boot your device into TWRP recovery
Now (assuming that you have Proper Nexus 7 drivers) Open the Toolkit and connect you device to the PC.
Now click the launch button under "Advanced Utilities"
On your device click advanced and the ADB Sideload.
Check mark Wipe Dalvik Cache and Wipe Cache and Swipe to start Sideload.
Now on your PC, click 'sideload update' under "ADB Sideload Update".
Click ok in the next pop-up and now Browse to the custom Rom that you want to flash.
The rom will be uploaded to your device temporarily for flashing and then it will be DELETED once it is Flashed.
This can take upto 30minutes depending on your computer's SPEED.
The rom will be flashed and the device will boot up.
I AM NOT RESPONSIBLE IF YOUR DEVICE BREAKS, OVER HEATS, OR YOU SPILL COFFEE ON IT. DO THIS AT YOUR OWN RISK..!!!
HIT THANKS IF I HELPED...
hassam_tariq2003 said:
i always use this method to flash roms as it cuts the hassel of copying the rom into the device for flashing and its very easy actually......just Follow these Steps.. :fingers-crossed:
Download Wug' Nexus Toolkit
Install it and Boot your device into TWRP recovery
Now (assuming that you have Proper Nexus 7 drivers) Open the Toolkit and connect you device to the PC.
Now click the launch button under "Advanced Utilities"
On your device click advanced and the ADB Sideload.
Check mark Wipe Dalvik Cache and Wipe Cache and Swipe to start Sideload.
Now on your PC, click 'sideload update' under "ADB Sideload Update".
Click ok in the next pop-up and now Browse to the custom Rom that you want to flash.
The rom will be uploaded to your device temporarily for flashing and then it will be DELETED once it is Flashed.
This can take upto 30minutes depending on your computer's SPEED.
The rom will be flashed and the device will boot up.
Click to expand...
Click to collapse
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Username invalid said:
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Click to expand...
Click to collapse
Hey....Cool Down Bro..
Everybody has different opinions about everything and i am not imposing it, I am just suggesting.
Username invalid said:
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Click to expand...
Click to collapse
This wouldn't help at all considering that it looks like OP panicked and did a full internal wipe.
OP, if you have TWRP working I would suggest booting into TWRP, going to Advanced > ADB sideload and then find the ROM zip you were trying to install, then open up command prompt and use adb sideload <path-to-zip> (how exactly you go about doing this last step depends on where you get adb-- any of the previously linked toolkits should include an adb.exe file though that you can run).
Rirere said:
This wouldn't help at all considering that it looks like OP panicked and did a full internal wipe.
OP, if you have TWRP working I would suggest booting into TWRP, going to Advanced > ADB sideload and then find the ROM zip you were trying to install, then open up command prompt and use adb sideload <path-to-zip> (how exactly you go about doing this last step depends on where you get adb-- any of the previously linked toolkits should include an adb.exe file though that you can run).
Click to expand...
Click to collapse
I was replying to the other persons comment, not to the OP. Obliviously he would not be able to connect his device to the computer and use a toolkit.
I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.
Kirbyscream said:
I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.
Click to expand...
Click to collapse
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.
abaaaabbbb63 said:
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.
Click to expand...
Click to collapse
Took awhile to get ADB drivers to work (fastboot was recognizing it fine)... pushed over the .zip file and just installed it, and everything works great! Thank you!
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
taodan said:
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
Click to expand...
Click to collapse
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
And yes to answer your question it is a multiROM patch for TWRP
sropedia said:
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
Click to expand...
Click to collapse
Do you have "USB debugging" checkbox, in Developer Options, checked? Also, try reboot your PC and reconect your phone to see whether it shows up as a storage device.
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
playya said:
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
Click to expand...
Click to collapse
I did a full wipe like I usually do. I would use a different version of TWRP if I knew how to change it from within TWRP. I have a follder titled ROOT that I keep all my ROMs and whatnot in, but the problem is that literally none of the folders in my internal storage are showing up from within TWRP. I can't check to see if USB debugging is enabled because theres no operating system on my phone; like I said, I did a full wipe. The fact that no folders show up also means that it doesnt recognize the backup I had. My computer still won't recognize my phone as a storage device after mounting in TWRP. Maybe I'm doing something in the wrong order? Restarting my computer didn't help.I really need to get my phone working on ANY ROM, and I appreciate all the help so far
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
brickwall99 said:
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
Click to expand...
Click to collapse
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
freebee269 said:
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
Click to expand...
Click to collapse
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
brickwall99 said:
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
Click to expand...
Click to collapse
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
freebee269 said:
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
Click to expand...
Click to collapse
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
brickwall99 said:
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
Click to expand...
Click to collapse
that's because you have no adb connection. no connection = no pushing files. that's why i said you need to get adb working first.
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
brickwall99 said:
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
Click to expand...
Click to collapse
good news. hope you get up and running now. still update your twrp.
freebee269 said:
good news. hope you get up and running now. still update your twrp.
Click to expand...
Click to collapse
Okay I got the ROM transferred and I have installed it successfully.
Using this one: http://forum.xda-developers.com/showthread.php?t=2598361
But when I reboot it goes straight to recovery.
A factory reset fails. I'm only able to advanced wipe of system/data, also it fails when I wipe cache or dalvik.
So I've tried wiping system/data, then installing the ROM again, and it just reboots straight back to recovery.
I sideloaded TWRP 2.6.3.5 for tmobile. Verified it shows 2.6.3.5 TWRP now. I'll try to sideload/install the ROM again.
Edit: When trying to factory reset it says failed to mount cache.
Okay so I have successfully installed the ROM with TWRP 2.6.3.5 and when I reboot it still goes straight into recovery.
What next?
Thanks
Edit: Is there perhaps something wrong with the bootloader, or what? I'm thinking part of the issue is because I can't mount or wipe cache/dalvik?
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
rawb123456 said:
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
Click to expand...
Click to collapse
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Any luck? I tried flashing CM11 on TWRP 2.6.3.2 (per XDA instructions) and it failed. Now I am stuck in recovery and can't ADB new recovery
brickwall99 said:
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Click to expand...
Click to collapse