Database Develop

Going Crazy/Brick

Here is the story in a nutshell I flashed xdabbeb's bootstack, then his rom. Then I did something stupid such as wipe everything folks, I mean everything. So my phone then restarted and I am able to get into recovery twrp 2.7.
I have tried in twrp to sideload, mount neither which work.
I have my drivers installed it says in device manager when I plug the phone up for download mode
android- galaxy nexus adb
and under ports it says LGE AndroidNet for VZW ADB Interface com41
I tried lg flash tool, tried with old vs98010b rom
pid:
imei:
model:
dll: vs980
bin: vs98010b_13.tot
swv:
swov:
model information check fail!
00000000
I really need help guys, are there any adb commands I can type or are there any drivers I need to install

Ok when i hold the up and plug in it takes me to fastboot
[500] fastboot mode started
[550] udc_start()
[720] reset
[730] portcharge
[740] reset
[750] portcharge
and the device only registers as android under other on my computer
i've installed lg drivers

How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot

timenewton said:
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
Click to expand...
Click to collapse
Download mode is not going to work because the laf partition (this allows for download mode to work) is wiped when you flash xdabbeb's bootstack in favor of fastboot mode.
I suggest you pm xdabbeb; he will guide you on the steps to using the necessary fastboot commands to get your phone working again. He's already helped a few people that were in the same situation as you are in right now.
Fastboot is good because you can write certain partitons at a time without having to .tot and wipe your whole phone.
You could also flash his xdabbeb_vs98024a_laf.zip http://www.androidfilehost.com/?fid=23329332407586639 file in TWRP 2.7 to restore download mode, but you will end up wiping your whole phone by using the LG Flash Tool, even your sd card when you restore your phone.
You said you "wiped everything", I'm not sure if that means your sd card too, if so, then that might be the easiest thing to do since you still have access to recovery. You will need an otg cable and a flash drive to mount the flash drive in TWRP 2.7 and flash the file, unless you can side load the file with adb.
Either way, like I mentioned earlier, it might be a good idea to pm xdabbeb first.

Hey my phone is already wiped even sdcard, but the thing is i cant flash that file because I can not get it on my phone. So ill ask xdabbeb the fastboot commands. Yeah and I read about the otg cable, ordered one of those babies should be here this saturday and hopefully it will mount my flash drive in that case id be golden untill then ill see what mr xdabbeb has to say.
cant sideload
everytime i try to sideload the file it just says cant read file or something like that
And I really appreciate you responding. Always nice to get support from somebody when your just sitting here and your phone seems like it hasnt been working for an eternity. Almost depressing not hearing from anyhbody and just seeing all the views but no replys. Thank you

Hey there...Fastboot is about as basic/simple/reliable as it comes. If you have adb/fastboot set up properly then command is:
fastboot flash <partition> <filename>
for example:
fastboot flash recovery recovery.img
In your case, you claim to have a working recovery (twrp 2.7), but are unable to copy files from your computer to your phone. It sounds like you don't have the proper drivers installed so that you can use adb from recovery. This is a common/known issue with windows and I believe I replied to you in the rom thread already about this, but you need to install/use Koush's universal adb driver and simply copy the rom file over to your phone using the following command:
adb push <filename> /sdcard/
After you have the file there you can flash it as normal in recovery.
If you want to use a kdz/tot method to restore your phone, just download the laf zip file from my thread, extract the laf.img file from the zip, and use the following command to put it in place:
fastboot flash laf laf.img
Then you can go about the tot restore method described in the thread here. You don't need to put the tot file itself on your phone. It just needs to be on your computer.

I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>

timenewton said:
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
Click to expand...
Click to collapse
Wait, I'm confused here a little bit. Are you trying to do sideload mode in TWRP or are you using fastboot mode?
And the command you typed is not correct fastboot flash recovery laf.img...you don't want to do that...this would flash the laf.img in your recovery partition.
xdabbeb referenced two methods to you...one was pushing a Rom to your sdcard and then flashing that Rom in TWRP to get your phone booting...the other was to flash the laf.img file and do a .tot if that's what you prefer.
It seems like you want to do a .tot restore, so do the second method xdabbeb suggested.
Get into fastboot mode and type fastboot flash laf laf.img
Make sure you use the correct laf.img...you can extract it from the zip in my previous post/link.
After this your download mode should be working again.

I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?

Even when i try to flash the laf it keeps saying waiting for device. I have the drivers koushu installed and lg

timenewton said:
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Click to expand...
Click to collapse
Yes, download xdabbeb's laf.img, it's the link I gave you originally. You will have to take out the laf.img file from the zip file that is called xdabbeb_vs98024a_laf.zip
The recovery command he gave was just an example, there was no need for you to use it.
Yes, flashing the laf.img will fix your download mode and you will be able to do the .tot method.

What am I suppose to do about it saying wiating for device, its not detecting it

timenewton said:
What am I suppose to do about it saying wiating for device, its not detecting it
Click to expand...
Click to collapse
That sounds like a driver issue. Reboot your computer and turn off the phone and start again. See if that helps. You can also remove the drivers and re-install...I suggest you reboot your computer every time you install new drivers.
EDIT:
Are you using a newer adb.exe from your android sdk? If you have ioroot25 installed on your computer I suggest you use the folder/files from there. It has a newer adb.exe in there; put your laf.img file in that folder too if you do use that instead, and run the command prompt from within that folder.

Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.

Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible

timenewton said:
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Click to expand...
Click to collapse
timenewton said:
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
Click to expand...
Click to collapse
For me it shows up under "ADB Interface", but I don't have the universal driver installed.
I didn't realize it wasn't installing the driver for you.
You have to get that driver going or you won't be able to get your phone fixed. Maybe try a different usb port or a different computer.

Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?

timenewton said:
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
Click to expand...
Click to collapse
Yeah, it should work. I've read posts by others stating that it works.

Yep just reinstalled the universal drivers, plug phone up into fastboot and still get the same result

Can you perhaps send me that driver you have? Because I know if you have that one and it works for you it SHOULD work for me. Murphs law is killing me. I can pm you my email address

Recovery Mode/Boot Screen Loop

Hi all,
I have an HTC One M8. I bought it used and run a AT&T sim on Straight Talk. Previous owner had rooted it. I was trying to get the 4.4 updates and Sense 6.0.
The phone was already running HD Revolution 12.1 and Android 4.2.2 with TeamWin Recovery Partition v2.5.0.0
I downloaded and installed Android_Revolution_HD-One_71.1.zip.
I've run it several ways:
1. First w/o wiping from TWRP. (Factory reset settings)
2. Installed w/o "Wiping Userdata Partition" and then tried "Wiping Userdata Partition" from the HD Revolution installer.
3. SuperUser by Koush checked.
4. Stops at setting permissions "set_metsdata_recusrsive: some changes failed."
5. Finish
6, Zip Install details say "no MD5 file found".
7. Reboot System and it tells me "Root permissions appear to be lost. Fix root permissions now?" Yes....
Then reboots into white Bootloader screen. Anything selected here takes me to the Recovery page. Anything selected from the REBOOT menu in TWRP takes me to the Bootloader screen.
When this is done it reboots into the white bootloader screen. Any option I pick there takes me to the TWRP recovery.
I'm stumped. Any help /bread crumbs would be appreciated.
Bootloader shows:
**TAMPERED**
**UNLOCKED **
M7_UL pvt ship s-on rh
HBOOT-1.44.0000
RADIO-4A.14.3250.15
OPENDSP-v26.120.274.0202
eMMC-BOOT
May 3 2013, 20:01:28-1
Thanks
TJB

fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.

TWRP 2.6
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Click to expand...
Click to collapse
I'm actually trying to mount the phone so I can see it from the PC update the TWRP. I downloaded openrecovery-twrp-2.7.1.1-m7.img but can't see how to load it to the phone.
PC sees the phone from Device Manager as a Disk Drive but it doesn't show up as a drive under My Computer.
I have Minimal ADB and Fastboot. Am I on the right track?
TJB

BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
Click to expand...
Click to collapse
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB

teebright said:
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
Click to expand...
Click to collapse
You cannot install like that, they have to be flashed via bootloader.
Do you have ABD installed on your PC?
If not you have two options.
OPTION 1
This guide for Windows 7 machine, this is the quickest way IMHO
Download the adb files for your respective PC from here : http://developer.android.com/sdk/index.html
Once you have downloaded the correct one for your PC (i.e. 32 or 64bit) you will be left with a zip FOLDER named something like this adt-bundle-windows-x86_64-20130522.zip (this is for 64 bit machine), Unzip it somewhere on your pc
Locate the unzipped folder and you should have/see the following inside
• Eclipse
• Sdk
• SDFK manager .exe
Open up the sdk folder and you will find 6 folders inside, cut the 'platform-tools’ folder , then double click my computer and then enter the C: drive of your PC. Paste this folder here in the C: drive and rename it Andriod-adb.
Then right mouse click my computer and go properties, then go and click Advance system settings located on left hand side this will bring up system properties box, click the Environment Variables… tab (it will open further details) and locate the Environment Variables list scroll down until you find path, highlight this then click edit.
Click mouse in here and scroll right to the end after the last entry
Type the following ;C:\Android-adb (noting only adding the first ; if not already there), if it is already there just type C:\Android-adb. Then hit Ok then OK again and your ADB should now be successfully setup.
To test this
From the windows start button, and in the search programs and files box type cmd and enter, this should bring up a command window.
Plug in your device and type adb devices, you should see it locate your phone
OPTION 2
Or try this, extract the attached file to your desk. place your recovery img in here and in a blank spot here hold the shift key down and right mouse click this should bring up list allowing you to "open command prompt here" then follow instructions below..View attachment 2850273
------------------------------------------------------------------------------------------------------------------------------------------------------
Once you have ADB working via either of the above sorted from a
1. Command prompt you should be able to type adb reboot boatloader, if you phone reboots into bootloader go to next step
2. Place the recovery image "openrecovery-twrp-2.7.1.1-m7.img " in the same adb folder as downloaded in option 2
3. Open a command prompt from within this folder and then type fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
4. Once sent it should com back to prompt
5. Type fastboot erase cache, then when completed type fastboot reboot
Good luck

fixed!
I fixed it! Per the recommendation I was trying to upgrade TWRP to 2.6.3.3.
I plugged in the phone to the PC via USB and made sure the phone is in FASTBOOT USB mode from the bootloader menu.
I installed "Minimal ADB and Fastboot" on the PC. Running that from the command line (cmd.exe) you type "fastboot flash recovery " then drag the file in. (watch the youtube video "How to install TWRP recovery on the HTC One M8" by ROOTJUNKIE-it will make more sense). In my case it was the 2.6.3 TWRP.img file. That pushes the update to the phone. I already had the HD 71.1 zip on the phone. I installed that via the TWRP install and from there it booted up normally. Had to setup the phone again but my music/pics were still there. Thanks all for the help!

[Root] Root and TWRP for R

Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years

Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.

One more just in case.

Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?

hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.

I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!

hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.

Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.

Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?

adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app

reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.

adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.

tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!

HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!

I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...

zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app

Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there

zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.

Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)

zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.

[Q] Can't Load OS via USB otg or computer, stuck in TWRP.

Ok so I screwed up.
I'm not a developer but i'm familiar with most of the basics. So my m7 was rooted with android revolution 81.0. I was having unrelated problems with calls and also some other small things like a lock screen delay. I decided I was gonna do a system wipe (which I've done plenty of times before with no problems) but this time I forgot to put the OS on the sd card before the wipe. As of now my phone turns on but stays on the HTC screen unless I force it into bootloader and I can also get into TWRP still. I also noticed I wiped the sd card as well by accident so everything is gone. I tried loading the OS via USB OTG but when i go to mount OTG in TWRP I can't select "USB-OTG".I can only select "system" "cache" and "data" I also tried mounting the phone via the computer but it doesn't show up but it does come up on device manager with a yellow exclamation sign next to it. I've heard you can do something with the ADB Sideload but I have no idea how to do that so if that's the answer please explain in detail.
If someone can get it to where I can mount the OTG then I can handle it from there.
Just some details:
S-on
TWRP version 2.6.3.2
I think i've wiped everyting there is to wipe trying to fix this, (
I've been without a phone for a week now and I'm desperate for any kind of fix. I'd greatly appreciate if someone could steer me in the right direction.

Aceboog33 said:
Ok so I screwed up.
I'm not a developer but i'm familiar with most of the basics. So my m7 was rooted with android revolution 81.0. I was having unrelated problems with calls and also some other small things like a lock screen delay. I decided I was gonna do a system wipe (which I've done plenty of times before with no problems) but this time I forgot to put the OS on the sd card before the wipe. As of now my phone turns on but stays on the HTC screen unless I force it into bootloader and I can also get into TWRP still. I also noticed I wiped the sd card as well by accident so everything is gone. I tried loading the OS via USB OTG but when i go to mount OTG in TWRP I can't select "USB-OTG".I can only select "system" "cache" and "data" I also tried mounting the phone via the computer but it doesn't show up but it does come up on device manager with a yellow exclamation sign next to it. I've heard you can do something with the ADB Sideload but I have no idea how to do that so if that's the answer please explain in detail.
If someone can get it to where I can mount the OTG then I can handle it from there.
Just some details:
S-on
TWRP version 2.6.3.2
I think i've wiped everyting there is to wipe trying to fix this, (
I've been without a phone for a week now and I'm desperate for any kind of fix. I'd greatly appreciate if someone could steer me in the right direction.
Click to expand...
Click to collapse
first thing is first, you need to sort out your driver, so when you see "one " with the yellow exclamation mark in your device manager, right click on it and select update driver, select the 2nd option, browse for driver software, again select the 2nd option which is something like let me choose the driver, it may give you a list after that of the type of device connected, select android devices, then select your latest myHTC driver from the list, it will give you some warning about it may not be the correct driver, are you sure you want to install, select yes.
Next, do you know how to use adb and fastboot ?

Seanie280672 said:
first thing is first, you need to sort out your driver, so when you see "one " with the yellow exclamation mark in your device manager, right click on it and select update driver, select the 2nd option, browse for driver software, again select the 2nd option which is something like let me choose the driver, it may give you a list after that of the type of device connected, select android devices, then select your latest myHTC driver from the list, it will give you some warning about it may not be the correct driver, are you sure you want to install, select yes.
Next, do you know how to use adb and fastboot ?
Click to expand...
Click to collapse
I know it involves the command terminal but no, I've never used it before.

Aceboog33 said:
I know it involves the command terminal but no, I've never used it before.
Click to expand...
Click to collapse
still need help?

madboy_maduka said:
still need help?
Click to expand...
Click to collapse
yes yes i dooo

Aceboog33 said:
yes yes i dooo
Click to expand...
Click to collapse
Sorry I had to leave for work, what you need is adb and fastboot files, so download this link and extract it to your desktop https://www.androidfilehost.com/?fid=23329332407580571
Then download either twrp 2.6.3.3 or 2.6.3.4 from the twrp recovery web site, when it's downloaded, rename it to recovery.img for ease and place it in the same folder as adb and fastboot.
You will then need to open a command Windows within that folder by holding control, shift and right mouse click on any white area within that folder, select open command window here.
Make sure your phone is plugged into the computer, and in the bootloader with fastboot usb showing on the screen.
At this point your drivers must be working as per my other post, then issue the following commands one at a time.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery, your usb otg cable should work now for flashing a Rom, be sure to do a full wipe before flashing, your current recovery sounds too old to me for usb otg support.
---------- Post added at 11:09 AM ---------- Previous post was at 11:00 AM ----------
If your still having problems with usb otg cable at this point, take the Rom which you want to flash and again place it in the same folder on your desktop as adb and fastboot, rename it to Rom.zip for ease, put your phone into recovery and then plug it into the computer, with recovery main screen showing on the phone, once again open a command window on your computer from within the adb and fastboot folder and issue the following command
adb push Rom.zip /sdcard/
Takes about 5 mins and will look unresponsive but it will let you know when it's done, unplug your phone when done, wipe and install.

Seanie280672 said:
Sorry I had to leave for work, what you need is adb and fastboot files, so download this link and extract it to your desktop https://www.androidfilehost.com/?fid=23329332407580571
Then download either twrp 2.6.3.3 or 2.6.3.4 from the twrp recovery web site, when it's downloaded, rename it to recovery.img for ease and place it in the same folder as adb and fastboot.
You will then need to open a command Windows within that folder by holding control, shift and right mouse click on any white area within that folder, select open command window here.
Make sure your phone is plugged into the computer, and in the bootloader with fastboot usb showing on the screen.
At this point your drivers must be working as per my other post, then issue the following commands one at a time.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery, your usb otg cable should work now for flashing a Rom, be sure to do a full wipe before flashing, your current recovery sounds too old to me for usb otg support.
---------- Post added at 11:09 AM ---------- Previous post was at 11:00 AM ----------
If your still having problems with usb otg cable at this point, take the Rom which you want to flash and again place it in the same folder on your desktop as adb and fastboot, rename it to Rom.zip for ease, put your phone into recovery and then plug it into the computer, with recovery main screen showing on the phone, once again open a command window on your computer from within the adb and fastboot folder and issue the following command
adb push Rom.zip /sdcard/
Takes about 5 mins and will look unresponsive but it will let you know when it's done, unplug your phone when done, wipe and install.
Click to expand...
Click to collapse
What the guy above me said was right, the problem I think with your phone is drivers I'll upload a link to adv drivers in my next post, basically using recovery (twrp recommend) wipe /data, /cache & /system. Then go to adb sideload which is in the recovery (it should say something like adb server started). Then using adb devices command check if your computer sees your device if not you gotta install drivers for your computer. In device manager on your computer your device should be something like ADB interface if not drivers are not correctly installed. Right click update drivers I'll link it in ma next post
---------- Post added at 10:30 PM ---------- Previous post was at 10:26 PM ----------
Follow these instructions to install the driver http://visualgdb.com/tutorials/android/usbdebug/manualinstall.php

Aceboog33 said:
yes yes i dooo
Click to expand...
Click to collapse
Use this guide. Saved me one time
http://android-revolution-hd.blogspot.ro/2013/12/how-to-copy-rom-zip.html?m=1

Stuck in the middle of CyanogenMod installation on Xperia T

Hello,
I've tried to help a friend in reinstall is Sony Xperia T (lt30p) but got stuck in the middle of CM installation and don’t know how to continue.
I've followed the steps from the wiki (Install_CM_for_mint (I cannot post a link...))
I've unlocked to bootloader and installed the boot.img.
But now I cannot find how to copy the rom files to the Xpria.
When I boot to the recovery I get different menus then written in step 8. I don’t have no "inatall zip" or "mount and storage" I do have "apply update" which gets me to "Apply from ADB" and "chose from sdcard0"
If I go to "Apply from ADB" I see the device in adb devices. When I do adb sideload file.zip I immediately get "error: protocol fault (no status)"
Running adb as admin + adb kill-server does not help.
I've tried to install TWRP so I could mount an usb drive with my OTG cable, but when I go to fastboot mode (power off, connect the usb cable and press vol up until blue led) I don't get anything from "fastboot.exe devices". The "driver software installation" window try to install the "MTP USB Device" but ends up with "Failed" status.
(I had to leave the friend house in which I've installed the boot.img. but I've installed Sony PC Companion_Web for drivers on both my windows 7 and 8)
So now I'm totally stuck:
I have no system for the phone to boot to.
I cannot copy the rom zip file to phone.
I cannot run fastboot to install TWRP.
Please help me
Zohar

zohar_ml said:
Hello,
I've tried to help a friend in reinstall is Sony Xperia T (lt30p) but got stuck in the middle of CM installation and don’t know how to continue.
I've followed the steps from the wiki (Install_CM_for_mint (I cannot post a link...))
I've unlocked to bootloader and installed the boot.img.
But now I cannot find how to copy the rom files to the Xpria.
When I boot to the recovery I get different menus then written in step 8. I don’t have no "inatall zip" or "mount and storage" I do have "apply update" which gets me to "Apply from ADB" and "chose from sdcard0"
If I go to "Apply from ADB" I see the device in adb devices. When I do adb sideload file.zip I immediately get "error: protocol fault (no status)"
Running adb as admin + adb kill-server does not help.
I've tried to install TWRP so I could mount an usb drive with my OTG cable, but when I go to fastboot mode (power off, connect the usb cable and press vol up until blue led) I don't get anything from "fastboot.exe devices". The "driver software installation" window try to install the "MTP USB Device" but ends up with "Failed" status.
(I had to leave the friend house in which I've installed the boot.img. but I've installed Sony PC Companion_Web for drivers on both my windows 7 and 8)
So now I'm totally stuck:
I have no system for the phone to boot to.
I cannot copy the rom zip file to phone.
I cannot run fastboot to install TWRP.
Please help me
Zohar
Click to expand...
Click to collapse
That's what happens when you follow the wiki from CM instead of instructions found here on XDA. A general rule of thumb is to always read up on XDA first .
1.- Search for Flashtool and use that instead of running commands from the command line or terminal.
2,. Install the proper drivers (Google them, or use the ones that come with Flashtool).
3.- If you want to copy files to the phone, remove the SD Memory card and attach it to the computer with an adapter. If that is not possible, go to step 4.
4.- Once you have the proper drivers installed, use Flashtool to fastboot Whiteneo's kernel (boot.img) from his thread, which gives you TWRP and should let you copy files to the phone through ADB, or I think even enable MTP mode (don't know if it's working on T, works on my phone).
OR
5.- If none of the above works, flash a Stock ROM corresponding to your phone (found also in this forum, search for the list of stock ROMs) which enables you to boot up into Stock ROM and copy the files you want to flash. You still need to install drivers though.

Thanks,
I'm so used to my HTC One m7 that don't have a SD card that I totally forgot about it...
Installed the Sony Emma Flashtool which gave to drivers.
Apparently this phone keep restarting all the time. could only install it when connected to the power.
will this: http://forum.xda-developers.com/showthread.php?t=2449242 help to fix the battery problem?
Zohar

I did this modification in the phone battery and now the phone works like new. :good:
Tested it by playing an hour long show for youtube with out any problem. the phone can go down to 8% (stopped there) with out and shutdown.
Zohar

The phone was without use for a long time.
Tried to turn it on but it refuses...
Opened the phone and tested the battery, it was only 0.8V
So doing this workaround for the battery will help you, but keep using the phone on daily basis.

(testing problem....)

(all good!)