So somehow my HTC One m7vzw was wiped completely of everything from the ROM, system and data to recovery image, etc. Now I cant access the developers options to turn USB Debugging on. Is there anyway to recover from such an ordeal?? HELP PLEASE !!!!!!
aaronpw0621 said:
So somehow my HTC One m7vzw was wiped completely of everything from the ROM, system and data to recovery image, etc. Now I cant access the developers options to turn USB Debugging on. Is there anyway to recover from such an ordeal?? HELP PLEASE !!!!!!
Click to expand...
Click to collapse
There is an ADB push option in TWRP which should let you put a ROM on the phone using:
adb push PUTROMENAMEHERE.zip /sdcard/.
or
You should be able to RUU something back onto the phone. Try to get to fastboot by rebooting to the bootloader from TWRP. Then you can use something like:
http://forum.xda-developers.com/showthread.php?t=2485319 Firmware update if needed
http://forum.xda-developers.com/showthread.php?t=2437436 RUU image
or
Alternatively, if you have an OTG cable you should be able to select a flash drive as a source media in TWRP.
I had a similar issue a few days ago when I wiped everything including my internal storage without even thinking how am I going to get the rom.zip back on the card (all my previous phones had SD cards).
In order to avoid flashing RUU I used sideload in TWRP to load rom directly through ADB. the only issue I had was with the drivers because for some reason my PC wouldn't recognize the phone (even though I used the same PC to root it) so I downloaded universal drivers that I found somewhere on the XDA.
unfortunately I don't have the links saved but if you search sideload and universal drivers I'm sure you'll find it.
aaronpw0621 said:
So somehow my HTC One m7vzw was wiped completely of everything from the ROM, system and data to recovery image, etc. Now I cant access the developers options to turn USB Debugging on. Is there anyway to recover from such an ordeal?? HELP PLEASE !!!!!!
Click to expand...
Click to collapse
To activate Developer Options, go into Stettings, then About Phone, then find Build Number. Press Build Number seven times.
jpradley said:
To activate Developer Options, go into Stettings, then About Phone, then find Build Number. Press Build Number seven times.
Click to expand...
Click to collapse
You must have misread his post. Everything was wiped. There is no way to go to settings, etc. There is no rom.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Your options are to boot it to the bootloader manually by holding power and volume down, then go to fastboot and push a recovery to it, from there you can also push a Rom to your storage and then use recovery to install your Rom.
Sent from my HTC6435LVW using Tapatalk 2
I tried installing a couple recoveries. A new TWRP and also CWM Recovery(hoped that worked since was the most recent recovery I used.
Sent from my XT907 using XDA Premium 4 mobile app
aaronpw0621 said:
I tried installing a couple recoveries. A new TWRP and also CWM Recovery(hoped that worked since was the most recent recovery I used.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once you have a recovery on there now just push a Rom using fastboot. Then boot into recovery and install Rom or if you already have a Rom on the internal storage just boot recovery and go from there.
Sent from my HTC6435LVW using Tapatalk 2
When I try using adb sideload in twrp the progress bar just keeps spinning.
Sent from my XT907 using XDA Premium 4 mobile app
Instead of side load can't you push a rom through the pc in fastboot? Drivers on your pc may not be working properly with sideload.
Sent from my HTC6435LVW using Tapatalk 2
I have nothing on internal. Like I said all is wiped
Sent from my XT907 using XDA Premium 4 mobile app
you can try
You will need to reboot to recovery and enter fastboot
not sure if this is exact so research it lower case and caps are needed the way they are done in tuts i used copy and paste then edited
enter command prompt window change to where your adb stuff is
fastoot devices if you get a response with sn great
fastboot oemRUU
fastboot flash zip imagename.zip where imagename is the rom you want to put on
for recovery it is like
fastboot flash recovery imagename.zip where imagename is your custom recovery
aaronpw0621 said:
I have nothing on internal. Like I said all is wiped
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I got it to get into recovery. I ended up using a HTC ONE all in one kit. So I got a stock like ROM and radio and firmware to get me going. Thing is now is when I try to sideload any ROM I keep getting stuck in either a bootloop or at the Boot Image. I still have SuperCid. I tried using the how-to on changing "mid" so that way I can use any variant ROM. But apparently I dont have a way to re-zip files So now going trying to sideload CM10.2 with GAPPS. Thing is is what I do sideload I cant find in storage. I just cant figure out why a few ROMS I had before now wont boot past the boot animation or just wont flash. PLEASE HELP
how did u make out with cm 10?
just checking in
Related
My phone was just downloading a file and now it won't boot past the green HTC logo white screen. The last rom I was using was one of mikroms. I have tried to restore from a backup as well as flashing a new from via recovery. I get an error during installing boot.img- I even get errors when recovery boots up. I posted images of my hbootand recovery. Any help would be greatly appreciated.
Use a newer recovery. I recommend 4EXT recovery touch. Also, you're probably gonna have to flash a new ROM. You also don't need to manually flash the boot.IMG since you're s-off.
Sent from my KangBang'd out vivow
tylerlawhon said:
Use a newer recovery. I recommend 4EXT recovery touch. Also, you're probably gonna have to flash a new ROM. You also don't need to manually flash the boot.IMG since you're s-off.
Sent from my KangBang'd out vivow
Click to expand...
Click to collapse
I already tried installing a new from, what I was saying is that error about installing boot.img happened when it was trying to install the from via recovery. For right now I'm just trying to get the phone to boot up. I don't think a different recovery will make that happen
scottyh73 said:
I already tried installing a new from, what I was saying is that error about installing boot.img happened when it was trying to install the from via recovery. For right now I'm just trying to get the phone to boot up. I don't think a different recovery will make that happen
Click to expand...
Click to collapse
Well considering yours is super outdated, it could be. Older recoveries may not work right all the time. Thus being why they released later versions.
Sent from my KangBang'd out vivow
Dude, even if you don't think a diffrent recovory will help just do it anyway. You can't break your phone anymore than it already is.
Sent from my HTC Incredible 2 using xda app-developers app
Had this happen a while back. Had to run a stock ruu, then reload recovery, then flash super user for root.
Sent from my ADR6350 using xda app-developers app
You're on an old radio, too. Probably the recovery is the culprit, though.
Sent from my vivow using xda app-developers app
Thanks for all of the suggestions guys. I'll try to flash a new recovery tonight and if that doesn't work I'll try updating radios. I'll post back with results. Cheers!
Well Im basically stuck. My computer will not recognize the inc. I have never synced this device up with this computer when it was up and running. Only with my rezound. Either way when the device is connected adb will not recognize the device as well as the computer will not recognie the usb device. Every file i try to push to it in bootloader i get error messages that device was not found. Tried fastboot flashing a new recovery as well as new radios but no luck. Ive also reinstalled htc sync, then removed. Recognizes my rezound no problem
if you have a micro->sd card adapter, place the recovery onto the root of it then go into CWM and install from sdcard, see if that works
JehC said:
if you have a micro->sd card adapter, place the recovery onto the root of it then go into CWM and install from sdcard, see if that works
Click to expand...
Click to collapse
Are you saying to install the new recovery zip, in recovery? I didn't think you could do that, and it didn't work. I've tried flashing new radios but it gets stuck on the very last part of the update and freezes until I take the battery out.
scottyh73 said:
Well Im basically stuck. My computer will not recognize the inc. I have never synced this device up with this computer when it was up and running. Only with my rezound. Either way when the device is connected adb will not recognize the device as well as the computer will not recognie the usb device. Every file i try to push to it in bootloader i get error messages that device was not found. Tried fastboot flashing a new recovery as well as new radios but no luck. Ive also reinstalled htc sync, then removed. Recognizes my rezound no problem
Click to expand...
Click to collapse
It should recognize it in recovery, did you try that it just bootloader
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
It should recognize it in recovery, did you try that it just bootloader
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I only tried in the boot loader. So you're saying connect it to the computer while in recovery, and then run the fast boot flash recovery command?
scottyh73 said:
I only tried in the boot loader. So you're saying connect it to the computer while in recovery, and then run the fast boot flash recovery command?
Click to expand...
Click to collapse
Install drivers, turn phone on by holding down volume plus power, then go into recovery, then plug phone to PC. Should be recognized now.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 04:04 PM ---------- Previous post was at 04:03 PM ----------
Type adb devices to check afterwards
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
Install drivers, turn phone on by holding down volume plus power, then go into recovery, then plug phone to PC. Should be recognized now.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 04:04 PM ---------- Previous post was at 04:03 PM ----------
Type adb devices to check afterwards
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
The computer does recognize the device when i go into recovery. Then when i run the flash recovery command through adb it says waiting for device. It will not show sending recovery though until i go into bootloader on the device. Then adb shows "okay" and "writing recovery....." It will show this forever until i unplug the device.
Try adb wait for device after that
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
Try adb wait for device after that
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
not quite sure exactly what you mean by that...just keep waiting while it says waiting for device while in recovery? I waited about 20 minutes..then tried waiting another 30 minutes while it was saying "writing recovery" while in bootloader
So im pretty sure the device is just done for at this point. I decided to just try to flash the device back to stock with this http://forum.xda-developers.com/showthread.php?t=1599767.. This also just got stuck on the recovery section. Should i just give up? lol
I did a factory reset on my galaxy nexus. I also by mistake erased my internal SD card. So now my phone only boots as far as the google screen because there is not ROM to boot into and when you connect to a computer it doesn't recognize the phone. How do I get a rom on my phone so it works again.
Thanks
Sent from my HTC-X710a using XDA Premium App
AshleyPem28 said:
I did a factory reset on my galaxy nexus. I also by mistake erased my internal SD card. So now my phone only boots as far as the google screen because there is not ROM to boot into and when you connect to a computer it doesn't recognize the phone. How do I get a rom on my phone so it works again.
Thanks
Sent from my HTC-X710a using XDA Premium App
Click to expand...
Click to collapse
Can you boot into fastboot? (Hold the power button and both volume buttons). I would boot into fastboot and reflash the Stock images. Also want to specify which variant you have.. GSM or CDMA if CDMA, verizon or Sprint?
Factory reset from stock or a custom recovery will not wipe the system partition. If you formatted the system partition from a custom recovery you can boot back into the custom recovery and adb push a ROM to your sdcard
Install the drivers on the computer. Then put the phone in fastboot mode like uber mentioned. Then push the rom to the phone and flash it in recovery. If you didnt install a recovery either, youll need one of those too.
Yeah hard to tell by her post if her bootloader is unlocked or not. I didnt think it was possible to wipe system without unlocking the boot loader and flashing a new recovery. Which means she needs knowledge of fastboot to even set that up.
The more i read the OP the more it sounds like unless she bought a used rooted phone off ebay. This thing is stock and just needs to boot to stock recovery and perform a factory reset from there. And that her system is fine.
With then phone off, hold down both volume buttons. Then hold down the power button, once it boots , use the volume keys to cycle and the power button to select. Navigate to recovery and perform a factory reset.
Sent from my Galaxy Nexus using Tapatalk 2
Lol i just fixed this on my brothers phone, Odin a stock tar, then reroot/install and CWM
Sent from my Galaxy Nexus using Tapatalk 2
Fire n mage said:
Lol i just fixed this on my brothers phone, Odin a stock tar, then reroot/install and CWM
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No.
Thanks for all the replies. My bootloader is unlocked. I'll give it a try and let you know how it turns out, thank you
Sent from my HTC-X710a using XDA Premium App
Also my phone was rooted and GSM
Sent from my HTC-X710a using XDA Premium App
AshleyPem28 said:
Also my phone was rooted and GSM
Sent from my HTC-X710a using XDA Premium App
Click to expand...
Click to collapse
Doesn't matter if its GSM or rooted. Fastboot is independent.
I can boot into fastboot and clockworkmod recovery, but the SD storage is blank. The computer won't recognize the phone. I can't seem to fix it and it's driving me crazy not having a phone. Please help!!
Sent from my HTC-X710a using xda premium
Plug in your phone via USB, in Fastboot mode.
Does it show in the device manager? It might not be called 'Galaxy Nexus', might be called something Fastboot related. It might be in the USB section.
XP:To open Device Manager, click Start, and then click Control Panel. Click Performance and Maintenance, and then click System. On the Hardware tab, click Device Manager.
7: Hit windows key, type in "Device Manager"
If there's a yellow triangle next to the device, the drivers on your PC may be not working correctly.
If it is working correctly, the easiest option is to load the Galaxy Nexus Toolkit, and flash stock ROM.
You installed the drivers as mentioned I take it?
AshleyPem28 said:
I can boot into fastboot and clockworkmod recovery, but the SD storage is blank. The computer won't recognize the phone. I can't seem to fix it and it's driving me crazy not having a phone. Please help!!
Sent from my HTC-X710a using xda premium
Click to expand...
Click to collapse
[HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
Take a look at step A. Install the drivers. Note you should also be able to set up the adb drivers while your phone is booted into a custom recovery.
follow the instructions here: https://developers.google.com/android/nexus/images
Install the drivers, then flash the stock image in fastboot, nothing to it.
Whoa there are females on this forum!!!!????? <Sound of a hundred myths shattering>
But anyway, why dont u just flash fastboot stock images?
Whoops, ninja'ed.
psycho2097 said:
females
Click to expand...
Click to collapse
Pluralizing the word is likely over-optimism on your part :laugh:
CMNein said:
Pluralizing the word is likely over-optimism on your part :laugh:
Click to expand...
Click to collapse
Damn, it's getting sexist!
Mach3.2 said:
Damn, it's getting sexist!
Click to expand...
Click to collapse
Well its bound to when there's 40k males n 40 females(i m taking 1-2 per current device)
THIS. IS. NEXUS.
Ash just install the drivers for the galaxy nexus, download a rom like aokp (the "maguro" version is the gsm version. Dont flash "toro" versions those are for cdma ) and then push it to the sd card using fastboot. All those steps are listed in a lot of posts in great detail by the author mskip and are stickied in the dev section here. Just read his posts for questions or drivers . Its all pretty straight forward once you read the right posts. Id avoid using any toolkits though, its all fairly simple stuff. And dont worry about the geeks here being surprised about seeing females. Some of them have never left the basement before. ( no offence guys , i got no problem with the homosexuals )
Sent from my Galaxy Nexus using Tapatalk 2
Hi,
I rooted LGOG LS970 using fiddy619's tool here on xda. I rooted successfully but was not able to enable DIAG mode using command line commands; So I unlocked its bootloader using GAIO V1.5 and then I installed custom recovery from it and after successful completion DIAG enabling commands got working. Then I extracted its MSL and unlock code using CDMAWorkshoptool; I used that code to enter into DIAG mode service code security and it worked perfectly; I got very happy to get MSL so easily. Everything was working fine until I restarted phone; and from there onwards first it booted with LG start-up music but screen was blank even after few minute while I waited. So I restarted it and it went to blank screen again after showing LG logo when I restarted it; So I restarted again this time it shown Fastboot screen where details were visible but options was not visible later on came to know they were there but was out of screen area. So I randomly selected voulume Up and Down and tried combinations using power button it restarted several times and then at one time I got into Clockworkmode. Then GAIO was able to detect phone till then so I did 'Restore Unlock Stock boot.img' in hope to make it work again but nothing changed. I tried mounting /sdcard in CWM but it gives error 'Error mounting /sdcard!'. CWM version is 6.0.1.5. I can access sdcard using ADB commands and I tried to copy .zip ROM file to it using push command and file copied successfully but when I list files using ls in ADB shell it shows nothing in sdcard. I'm also not able to recognize why CWM is not able to mount /sdcard while I am able to access it in ADB shell. I can't flash new ROM too because it doesn't have ROM file on SdCard and I am not able to put .zip Rom on sdcard though ADB or special ADB sideload method of CWM. When I execute 'adb sideload LS970ZV7.zip' it shows adb command help list. Adb version is 1.0.29 and I checked that it supports ADB sideload. I know it is kind of soft-bricked. But I am able to use CWM and Fastboot but I cannot use Fastboot commands from my windows command prompt; it says waiting for device on every command.
When I mount '/system' in CWM; GAIO v1.5 recognizes the phone and says Root Status- Rooted and Device Unlocked: Locked. Windows detects the mobile and installs drivers. I tried formatting /sdcard from CWM but it gives error. I have attached screenshots of GAIO and windows detected devices of phonen and adb commands. The software information screenshots were taken before it got soft-bricked.
If anyone have any idea how to recover from this state..?
The problem is with jellybean you must use the freegee the app to unlock because if new boot.IMG. here is a flash able zip. Adv push it and flash it and you should be good.
http://downloads.codefi.re/shelnutt2/optimusg/sprint/ZVBboot-freegee.zip
Sent from my LG-LS970 using xda app-developers app
thanks
Shelnutt2 said:
The problem is with jellybean you must use the freegee the app to unlock because if new boot.IMG. here is a flash able zip. Adv push it and flash it and you should be good.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Hi, Thanks
I never did a flash of boot.img and after a brick I am very skeptical to do anything more. One more guy funkym0nk3y told to use Lgnpst to restore it. I am trying to find safest way coz I dont want to make it more worse. I am reading more on freegee flashing.
Shelnutt2 is the one who made freegee so it's probably not going to cause you any problems.
Sent from my LG-LS970 using xda app-developers app
ABurningFalcon said:
Shelnutt2 is the one who made freegee so it's probably not going to cause you any problems.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Ohh thanks.
I didn't know that. So I'm going to do a flash now. Thanks for this info and thank you Shelnutt2..
Shelnutt2 said:
The problem is with jellybean you must use the freegee the app to unlock because if new boot.IMG. here is a flash able zip. Adv push it and flash it and you should be good.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I am not able to adb push it to /sdcard or any other partition such as emmc which is accessible from adb shell.
The file gets copied to device but I cant access /sdcard in CWM and for /emmc partition I am able to push it but cant access it in CWM in emmc it goes to Clockworkmode folder on emmc and doesnt show the file I put on it.
Any other idea please...
You need to push it to /data/media.
Sent from my LG-LS970 using xda app-developers app
Shelnutt2 said:
You need to push it to /data/media.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Ok, Thanks will try and let you know.
Shelnutt2 said:
You need to push it to /data/media.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Hi,
Pushed ZVBboot-freegee.zip successfully to /data/media. But how to flash it as Im not able to use fastboot in command prompt its not detecting device. So how to flash this boot ROM?
Shelnutt2 said:
You need to push it to /data/media.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Hi,
Pushing to /data/media wasn't working so pushed it to clockworkmod folder of /data/media. Successfully completed install from internal SD card. Now phone is going into recharge mode as it wasn't previously going previously. Not able to boot it as its restarting coz its not charged from many days. But after few seconds of recharge animation of white battery getting filled it screen gets blank. Can I do same flashing for ZVB ROM also...? And if yes in same way as I did for boot.img..?
sgk14 said:
Hi,
Pushing to /data/media wasn't working so pushed it to clockworkmod folder of /data/media. Successfully completed install from internal SD card. Now phone is going into recharge mode as it wasn't previously going previously. Not able to boot it as its restarting coz its not charged from many days. But after few seconds of recharge animation of white battery getting filled it screen gets blank. Can I do same flashing for ZVB ROM also...? And if yes in same way as I did for boot.img..?
Click to expand...
Click to collapse
Leave it in recovery to charge, although you should be able to boot into the ROM. You might just want to lgnpst if you keep having trouble.
Sent from my LG-LS970 using xda app-developers app
Shelnutt2 said:
Leave it in recovery to charge, although you should be able to boot into the ROM. You might just want to lgnpst if you keep having trouble.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Hi, Thank you for that.
It was restarting continuously after showing LG boot animation so I left it to charge on charger.
And after sometime connected it to PC usb to check and restarted it and it booted into OS..
So now its working properly and it got like factory reset as It was showing first time guide layovers but still its rooted as DIAG is enabled already and SuperSu is installed.
But I think I messed internal SD card structure its showing folders I never seen before and my old data files are gone I know it mu\ight be cause of kinda reset but new file structure looks odd to me but I will format internal card. Still I am very happy that it got working now...
Thank you very much for help.
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Aireon said:
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Click to expand...
Click to collapse
mount the sdcard inside the recovery and copy the rom
Mr Hofs said:
mount the sdcard inside the recovery and copy the rom
Click to expand...
Click to collapse
Sorry, I'm completely new to this. Do you mean normal recovery from bootloader or a custom recovery that I should of done but completely skipped due to my ignorance? (I also haven't unlocked bootloader so I'm assuming that's a misstep as well?)
Because all I get when I do the normal recovery is a picture of a phone with a red triangle and "!" combo.
Thanks
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Mr Hofs said:
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Click to expand...
Click to collapse
Thanks for the tips!
After a while of toiling to try and unlock the boot loader manually and getting stuck at the load error for Unlock_code.bin, I found Hasoon2000's tool, so he is my god for now.
My query that I have is, Do I need a custom recovery like ClockWorkMod to create a nandroid back up? Because all I get when I try to go into recovery from the bootloader is this (img attached, not mine because I don't have another camera in the house but luckily I managed to find one on google img.)
I can't find anything saying that I do need a custom recovery, but then again it's not working when I try without one, so I'm not too sure where to go from here.
Thanks again
Please read carefully what i write, i know exactly what to do !
You need a custom recovery !
Sorry to be back again so soon but I'm stuck again, haha.
When I try to flash cwm I get "error: cannot load 'recovery.img'". When I try to use Hasoon2000's tool kit to do it for me it doesn't work either as it just says device not found and in the second command window it says that it can't load it's .img file either.
The recovery.img is in the same location as fastboot. My phone is in Fastboot in bootloader.
I'm typing "r:\Android\adt\sdk\platform-tools\fastboot flash recovery recovery.img". Trying to auto complete recovery.img using tab does nothing (if that might indicate some sort of problem).
The only thing I can think of is that the MTP drivers never install properly but I read on this forum that it shouldn't affect fastboot.
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ah, I probably should of said it earlier, sorry. I'm using windows 7.
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
If javaj jdk is just normal java then yes. In programs and features it's called Java 7 Update 45?
Do you mean the phone drivers on my PC?
Edit: Noticed jdk was the dev kit. Downloaded and installed. Will try again.
Edit2: Still not working, same errors.
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I just updated the phone drivers (without HTC sync) from http://forum.xda-developers.com/showthread.php?t=2376761 to 4.2.0.001 from the 4.0 version I had that HTC sync had installed previously for some reason.
Shows up in fastboot devices now. Still doesn't show up in adb devices. Still getting the can't load recovery.img error.
Would it be worth it to try doing it on another computer?
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ok so I still couldn't do it manually on the other computer. Got the same errors as with the first. I tried flashing with Hasoon2000's tool again and noticed that it was trying to flash CWM.img while the recovery for it was actually called recovery.img. Renamed it to CWM.img and it flashed perfectly.
I assume it would of done the same on the original PC I tried it on.
No idea why it wouldn't work when I tried it manually, but yolo. Hasoon2000 is love. Hasoon2000 is life.
Holy hell Hasoon2000 has saved me again.
I flashed the kernal by accident and it got stuck in boot. So i just sideloaded the rom in H2K's tool and everything turned up Milhouse.
Yay congrats
Sent from my GT-I8190 using xda app-developers app
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Mr Hofs said:
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Click to expand...
Click to collapse
Hmmm, I'm not sure what it would of been as a tried flashing recovery.img.img as well. But everything worked out well in the end .
Thank you both the help.
Glad to hear that it worked
Sent from my GT-I8190 using xda app-developers app
I put TWRP Recovery on my LS970 and tried flashing the Liquid Jelly Bean ROM on and it ended up with just pure stress. Before I flashed it I had wiped the dalvik and normal cache and even factory reset it before flashing and it said it installed correctly. I restarted my phone (and I do have an unlocked boot loader and recovery of course) and it was stuck on the Google unlocked boot picture. I tried flashing it again and Ive used LGNPST and LG Flashtool and none helped. I was wondering if there is a possible solution to this perhaps I could send a flashable zip through my computer? Please help
ETR174 said:
I put TWRP Recovery on my LS970 and tried flashing the Liquid Jelly Bean ROM on and it ended up with just pure stress. Before I flashed it I had wiped the dalvik and normal cache and even factory reset it before flashing and it said it installed correctly. I restarted my phone (and I do have an unlocked boot loader and recovery of course) and it was stuck on the Google unlocked boot picture. I tried flashing it again and Ive used LGNPST and LG Flashtool and none helped. I was wondering if there is a possible solution to this perhaps I could send a flashable zip through my computer? Please help
Click to expand...
Click to collapse
So do you have recovery or fastboot now? If you LGNPST you should be locked and have stock recovery.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
So do you have recovery or fastboot now? If you LGNPST you should be locked and have stock recovery.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It has TWRP recovery and has fastboot. When I try LGNPST its stuck at 1% and it says verifying files. I waited 30 minutes and it was still there.
ETR174 said:
It has TWRP recovery and has fastboot. When I try LGNPST its stuck at 1% and it says verifying files. I waited 30 minutes and it was still there.
Click to expand...
Click to collapse
Do you have any other roms on your SD? If not, try to adb sideload a stockish ROM. Adb sideload is on first page of this. http://forum.xda-developers.com/showthread.php?t=2082084
Edit. Have you tried reflashing your ROM? This time wipe system, dalvic, cache, and data. NOT INTERNAL data. That's your SD.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Do you have any other roms on your SD? If not, try to adb sideload a stockish ROM. Adb sideload is on first page of this. http://forum.xda-developers.com/showthread.php?t=2082084
Edit. Have you tried reflashing your ROM? This time wipe system, dalvic, cache, and data. NOT INTERNAL data. That's your SD.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I only have that and GApps. And for adb you have to have usb debugging on right? I dont.
ETR174 said:
I only have that and GApps. And for adb you have to have usb debugging on right? I dont.
Click to expand...
Click to collapse
You'd said you had liquid installed and LGNPST failed, so liquid should still be installed. So in recovery, wipe those 4, flash liquid then gapps and see if it works. Then we'll go from there.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Ok. Ill give you pictures of the end processes too.
Edit: Well I cant give you pictures but I wiped the four and my phone is stuck on the Google unlocked boot.
ETR174 said:
Ok. Ill give you pictures of the end processes too.
Edit: Well I cant give you pictures but I wiped the four and my phone is stuck on the Google unlocked boot.
Click to expand...
Click to collapse
So you did the wipes, installed liquid, installed gapps, then rebooted and are stuck. Do you have ADB installed? If so DL this TWRP. http://www.androidfilehost.com/?fid=22909751817929287.
Extract the recovery image using 7zip.
Boot your phone into fastboot/bootloader Then cd to the folder the image is in. Then issue this command.
"fastboot flash recovery recovery.img"
You may need to do this first. "fastboot erase recovery" then "fastboot flash recovery recovery.img"
If your not comfortable doing this, just google fastboot and you'll find info on how to do it. This thread seems pretty thorough. http://forum.xda-developers.com/showpost.php?p=41374534&postcount=1
Then go here, http://forum.xda-developers.com/showpost.php?p=36270473&postcount=1 to ADB sideload a Stockish Rom
If this doesn't work then you'll probably end up having to use LGNPST
engine95 said:
So you did the wipes, installed liquid, installed gapps, then rebooted and are stuck. Do you have ADB installed? If so DL this TWRP. http://www.androidfilehost.com/?fid=22909751817929287.
Extract the recovery image using 7zip.
Boot your phone into fastboot/bootloader Then cd to the folder the image is in. Then issue this command.
"fastboot flash recovery recovery.img"
You may need to do this first. "fastboot erase recovery" then "fastboot flash recovery recovery.img"
If your not comfortable doing this, just google fastboot and you'll find info on how to do it. This thread seems pretty thorough. http://forum.xda-developers.com/showpost.php?p=41374534&postcount=1
Then go here, http://forum.xda-developers.com/showpost.php?p=36270473&postcount=1 to ADB sideload a Stockish Rom
If this doesn't work then you'll probably end up having to use LGNPST
Click to expand...
Click to collapse
Thanks but I really dont understand adb. What needs to happen on the phone end in order to use adb? And for the computer?
ETR174 said:
Thanks but I really dont understand adb. What needs to happen on the phone end in order to use adb? And for the computer?
Click to expand...
Click to collapse
Read that link above and it explains adb and fastboot
But if you're not comfortable with that then just LGNPST
Go to the teeny bin thread under "Additional info" and follow the LGNPST walkthru.
engine95 said:
Read that link above and it explains adb and fastboot
But if you're not comfortable with that then just LGNPST
Go to the teeny bin thread under "Additional info" and follow the LGNPST walkthru.
Click to expand...
Click to collapse
Oh I forgot to mension that I did flash teeny bot with LGNPST but this cane with the SBL. Should I download a different version and try flashing again with LGNPST?
ETR174 said:
Oh I forgot to mension that I did flash teeny bot with LGNPST but this cane with the SBL. Should I download a different version and try flashing again with LGNPST?
Click to expand...
Click to collapse
Ok now we're getting somewhere.
When you used teeny bins, it installed the wrong version of TWRP to use with KK Roms. In your recovery is the version 2.6.0.0?
The easiest way to change that recovery is to use fastboot and install a KK version 2.6.3.3. You can find those in the TWRP thread or the root guide under Working recoveries.
You can also use CWM recovery if you want
So follow what is posted above, install a KK recovery, then you should be able to install Liquid.
engine95 said:
Ok now we're getting somewhere.
When you used teeny bins, it installed the wrong version of TWRP to use with KK Roms. In your recovery is the version 2.6.0.0?
The easiest way to change that recovery is to use fastboot and install a KK version 2.6.3.3. You can find those in the TWRP thread or the root guide under Working recoveries.
You can also use CWM recovery if you want
So follow what is posted above, install a KK recovery, then you should be able to install Liquid.
Click to expand...
Click to collapse
I mean I used Freegee to unlock the bootloader and install TWRP Version 2.6.0.0 and from what it sounds like there is a lot of problems with it. Could I flash CWM or a newer version of TWRP with LGNPST?
If you use LGNPST you'll be back to Factory stock. Recovery included. There's no way to install another recovery until to root/unlock
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
If you use LGNPST you'll be back to Factory stock. Recovery included. There's no way to install another recovery until to root/unlock
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well do you know any reason why it stays at 1% verifing files? Or any fixes to it?
ETR174 said:
Well do you know any reason why it stays at 1% verifing files? Or any fixes to it?
Click to expand...
Click to collapse
Are you selecting the right DLL? Using either ZVB or ZVC bin?
Other than that, I don't know. Maybe you need to uninstall then reinstall the LG drivers or LGNPST.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Are you selecting the right DLL? Using either ZVB or ZVC bin?
Other than that, I don't know. Maybe you need to uninstall then reinstall the LG drivers or LGNPST.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont know let me go check. I thought it had something to do with the phone not the dll or bin files.
It must be the bin file because I flashed teeny bin just fine with the dll
Im an idiot. Turns out that the firmware was in a cab file which was supposed to be extracted into a bin file. It got deleted to I downloaded a stock bin from your android file host profile and Im going to flash in just a minute and tell you the results.
ETR174 said:
Im an idiot. Turns out that the firmware was in a cab file which was supposed to be extracted into a bin file. It got deleted to I downloaded a stock bin from your android file host profile and Im going to flash in just a minute and tell you the results.
Click to expand...
Click to collapse
No worries. I can't remember where that bin file gets extracted to, but if you're downloading the bin that's fine too. I forgot to mention that ZVC is the most current, but if you have ZVB that's fine if you're gonna run CM/AOSP
Sent from my LG-LS970 using XDA Premium 4 mobile app