hi i am trying to install a recovery image like clockwork image but i am unable to do it for some reason and i have tried loads of things to fix it but cant so i wanted some help
i have got sdk installed and i have debug mode enabled on my vega but when i open cmd and go to the C:\AndroidSDK\tools directory all is fine.....when i type adb devices it shows none so i am stuck now because i cant make it find my vega
Hi there
It may be the version of SDK you have. In the latest version adb tools have been moved to platform-tools I think.
BTW even with that information, I'm still not able to boot my Vega into recovery. I just get as far as the unpacking screen.
Let us know how you get on.
Related
cant seem to get this adb going on vista...am trying to get to root but adb just isnt happening, have installed all the correct drivers, the phone is in developer mode but in windows vista when i open command prompt and check adb theres no devices attached? I have checked in device manager and under usb root hub the phone isnt there, it is under portable devices as android phone and trying to update the usb drivers on there doesnt install saying that the current drivers are up to date. I can get into fastboot and the phone is picked up with the usb drivers from the sdk package.
Can anyone help on this? I have tried method 2 of getting to root http://android-dls.com/wiki/index.php?title=Magic_Rooting but the phone just hangs at the vodafone screen (i have to sut the phone down from the fastboot menu as adb doesnt work).
Any help would be appreciated, there was a small update on friday to the phone have they fixed everything or is it just an issue with vista?
Was trying to follow the instructions found here to flash the spl but I'm not sure what it means, I'm sure I'm nto just being thick....
http://forum.xda-developers.com/showthread.php?t=529019
How to flash :
1. Download the appropriate recovery here, and rename it to update.zip.
2. Copy update.zip to the root of your SD-card
3. Switch the Magic to fastboot mode
4. $fastboot boot <moddedrecovery.img>
5. Apply the update
point 1 takes me to RAv1.0G.img, do i just force it to name as a zip file from file extension or physically zip it?
part 2 is fine if I understand part 1
part 3 I'm ok on
part 4, I'm taking it this is the spl file however its a zip package, do i unzip it and place both the hboot.img and the meta folder into the folder i am using for fastboot and adb? the instructions arent very cear for doing this, can anyone correct me if above is wrong?
thanks.
fixed now skipped a whole load of steps and its working lol
So im stucked in the LG logo.
i installed TWRP in kit kat and when i booted it was stuck in the logo.
i can go into recovery or the download mode.
so i tried to use adb sideload but it always says, cannot read update.zip
Is there any other metod? already tried cmd and some toolkit 1.5 to do it but always the same
i tried also to use in download mode the flastool, but doesnt recognize the phone
can u please help???
i found a solution and wanted to share with everyone who could be having the same problem (sorry for my english)
so a couldnt use download mode because my computer wasnt accepting the phone in the lg app (mobile support tool)
in recovery the adb sideload wasn t working and coudnt read the file so what i did was this:
installed sdk manager
and where i had my adb.exe e puted there the rom i wanted to flash.
my path was like this: C:\android\sdk\platform-tools
in my phone i entered recovery mode and didnt select anything else, connected to the computer
in my computer i opened cmd as administrator, i dont know if this is important or not..
then in cmd i wrote the path where the the adb was and in the same place the rom: C:\android\sdk\platform-tools (in my case)
this is the important part, type:
C:\android\sdk\platform-tools>adb push rom.zip /sdcard/rom.zip
rom.zip is the name of the file, you should put the one u have, thean it should take a little, at first it lokes like its doing nothin, just thinking but its really copyng the file to your phone, than it appears the size of the file its just copied and its done, now u gow to your phone and the ropm.zip in in there, now you just have to flash it and reboot.
Dear people of xda,
Recenlty ive receive a FOTA update to my device which runs 4.2.2. Being stupid, i did the update although i had cwm recovery installed on my devices. Now my device keeps bootlooping into cwm without being able to do anything.
Ive read tons of threads talking about this issue but i still cant get my to boot normally.
Yingy in this thread http://forum.xda-developers.com/showthread.php?t=2563527 had the same problem but the only diffrence is my pc cant recognize my device in order to do the adb fix by thecubed.
Im plugging my G2 for the first time in this computer and that is why i think my pc is failing to install drivers. I downloaded and instellad latest driver although windows device manger shows error devices not detected and the end of the process.
In order to fix my phone i just need to make me pc recognize my phone in adb although phone was never plugged before to this pc so i think my G2 wont let it access. I tried installing universal driver such as Pdanet as offered in threat but still when i write adb devices in cmd i get device offline!
Download latest adb drviers, lates lg g2 driver, lg user support tool does not recognize plugged device as well. All me sdk manger tools are patched to latest version.
PLEASE ive tried anything possible. spend like 9 hours and still nothing. i would really appriciate your help.
Thanks.
Edit: here my problem with pdanet drivers, it asks me to allow pc usb debbuging as shown in screenshot below but icant do it since im stuck at cwm recovery!
Solved!
BOOM!! after 12 hours i FINALLY manged to solved this problem. Really simple actually lol.
If anyone come across the issue please do the following:
1. Go to clockwork recovery as always, go to install zip from sdcard, choose install zip from sideload.
2. Plug your phone to pc.
3. Run adb with lastest drivers and sdk tools.
4. At the adb folder press shift+right click and start cmd.
5. write adb devices it should show your device id like this (xxxxxxxxx sideload).
6.Download latest twrp recovery from here http://teamw.in/project/twrp2/197 and if you have open europe version G2 like me download latest version from here: http://techerrata.com/browse/twrp2/g2d802
7.put the zip file in the adb folder, do not unzip it.
8. write in cmd console adb sideload xxxx.zip (xxxx is the name of twrp file).
9. cwm will flash twrp recovery over cwm.
10. reboot in recovery in advanced options.
11. now you have twrp recovery.
12. follow this guide : http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
13. THATS IT!!!
finally after going through this mess, im never using cwm recovery again. twrp is the best
good luck everyone!
Hey guys, with the release of the Android M update for OP2, i had flashed the new rom on my device. However, during the process of flashing the rom, i looked over a step, and didnt flash SuperSU in the process. Hence right now, i have no root nor SuperSU access on my OP2 running Android M.
Everything else seems to be working nicely, although i would really like to reobtain my root access. i have looked online for some options, but i thought the devs and members here could help me out as to what to do. should i undergo and do the entire root process again? Or will the process below be enough to help me regain root access :
"Download the TWRP or CWMR image for your device and save it into the same directory as the ADB / fastboot drivers
Boot into the bootloader. Key-combinations can be found here.
Open the Windows command or Mac terminal and navigate to the direction where the ADB / fastboot drivers are located
Execute the following command: fastboot flash recovery filename.img (with filename.img being the name of the recovery image you downloaded earlier)"
I'd really appreciate much help, as I'm pretty new to this stuff. Thanks!
I really need help, I have tried the following, having TWRP V2.8.5.1 functioning and Fastboot also.
- Through TWRP, tried connecting the PC so I can Flash a ROM from there, but I can't seem to be able to connect the One to my PC so it will let me transfer files through cmd with adb push. My computer is a windows 10 OS with Samsung drivers and Android SDK full installed, still can't get it to work.
- Through Fastboot tried flashing cm-11-20141008-SNAPSHOT-M11-bacon.zip downloaded from Cyanogenmod page and using Oneplus One Toolkit 2.0, even though the Toolkit says the files are there, still phone continues to show 1+ logo and then rebooting.
Please I need some help.
Cheers. and thank you.
Why adb push when you can just copy the file over using a file manager (or a command prompt if you insist) and then flash from the internal storage?
I'm having the same issue but in my case I can boot into recovery or other stuff IF I HAVE THE USB PLUGGED IN
Maybe you can check and and let me know, if I found a solution I'll tell you, hoping the same from you please.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 this could help.