guyz, pls help me out..
i only need to know how to have a recovery on my newly rooted stock p350..
can someone provide me a link on this?
a very clear step by step tut also would help a lot for a newbie of p350..
pls regard my request..
waiting eagerly..
-salute!
Sent from my GT-S5830 using xda app-developers app
all in one toolkit for p350
[TOOL] LG P350 Optimus Me Pecan Toolkit [ROOT][RECOVERY][UNROOT]
Check the wiki, there's the compete guide...
Sent from my LG-P350 using Tapatalk 2
PecanCM said:
all in one toolkit for p350
[TOOL] LG P350 Optimus Me Pecan Toolkit [ROOT][RECOVERY][UNROOT]
Click to expand...
Click to collapse
the way more easy =)
Softbricked
Hello guys....I am stuck at that same old fastboot screen.
My phone is not being detected
I have inststalled lg usb drivers but not all the sdk tools. I just have fastboot and adb.
Do I need complete sdk tools to detect my phone for fastboot commands?
vaib said:
Hello guys....I am stuck at that same old fastboot screen.
My phone is not being detected
I have inststalled lg usb drivers but not all the sdk tools. I just have fastboot and adb.
Do I need complete sdk tools to detect my phone for fastboot commands?
Click to expand...
Click to collapse
In the wiki you can find all the tools needed to recover from that issue...
Sent from my LG-P350 using Tapatalk 2
dbarrera said:
In the wiki you can find all the tools needed to recover from that issue...
Sent from my LG-P350 using Tapatalk 2
Click to expand...
Click to collapse
I tried everything but the mobile isnt getting detected. I downloaded the drivers 5 times but still phone didnt get recognized. Finally gave it to the service centre and they unbricked it within 5 minutes.
Can you please give me the exact links to all the drivers and softwares needed?
Thanks
vaib said:
I tried everything but the mobile isnt getting detected. I downloaded the drivers 5 times but still phone didnt get recognized. Finally gave it to the service centre and they unbricked it within 5 minutes.
Can you please give me the exact links to all the drivers and softwares needed?
Thanks
Click to expand...
Click to collapse
Lets start at the beginning, where did you download the drivers from?
I downloaded them from several different links including the link given in lg p350 toolkit. But whenever I connect the cable, it installs virtual modem only.
And in fastboot mode, when I give fastboot commands from my pc it just says "waiting for device".
Download the clockworkmod app from the play store and then install custom recovery through it , extremely simple and worked fine for me
Related
hi
i tried to unroot my nexus s and get back to stock following this instructions :
forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/141849-mac-method-root-unroot-unlock-your-vz-galaxy-nexus.html
and i did the unroot , but Unfortunately it hang in google logo and didn't move , and also the same with recovery mode !
BTW , the bootloader now is locked .
and my mobile is 19250GSMH
and my computer is macbook pro ..
please Help me
Use the tool kit. It does all the work for you.
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
Use the tool kit. It does all the work for you.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
The tool kit is for windows only I believe. So u own a GSM version right? If so follow the steps from my video on YouTube. The video was made for my old nexus s 4g but the steps are the same.
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium
^^
it doesn't work :/
what i suppose to do please
thx
Eyaad said:
^^
it doesn't work :/
what i suppose to do please
thx
Click to expand...
Click to collapse
Okay, you have Android SDK, ADB, and Fastboot? You are locked and rooted, yet still on a custom rom?
You need to unlock the bootloader by entering fastboot and then performing:
fastboot oem unlock
Then you will need to flash Google's custom images found here. You will have to place the contents of the compressed file in the same folder where you have adb and fastboot commands. Then you can perform
sh flash-all.sh (or you can flash one by one, whatever you want)
Then you can perform
fastboot oem lock
yeeeeees , i got the sulution and it works
http://forum.xda-developers.com/showthread.php?t=1366806
thx
ok have a gnex had it rooted rommed etc etc Ihave tried every single thing to revert this sum bich to stock for resale and nothing works any help??
PS used both pc and mac, odin, wugfresh, gnex toolkit etc etc
what exactly does not work? any error?
did u tried fasboot to restore the original google stock images?
for an example i just tried the toolkit again and wugfresh it sees my phone says all drivers are installed then i start everything it gets to bootloader mode and then just hangs there saying waiting for device?
AndreaCristiano said:
for an example i just tried the toolkit again and wugfresh it sees my phone says all drivers are installed then i start everything it gets to bootloader mode and then just hangs there saying waiting for device?
Click to expand...
Click to collapse
Try uninstalling the drivers and re install them. Are u in debug bode also?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Try uninstalling the drivers and re install them. Are u in debug bode also?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yea in debug did the uninstall reinstall of drivers
Did you restart the pc after installing the drivers?
Which drivers did you install and what OS is your pc running?
If you open the device manager on your pc and connect the phone in fastboot mode what exactly does it say in the Android tab (name of driver installed)?
Mark.
AndreaCristiano said:
Yea in debug did the uninstall reinstall of drivers
Click to expand...
Click to collapse
You have a driver issue.
Uninstall all GN device drivers.
Get the drivers from here.
Follow these steps to install the drivers.
Follow this to get back to stock.
efrant said:
You have a driver issue.
Uninstall all GN device drivers.
Get the drivers from here.
Follow these steps to install the drivers.
Follow this to get back to stock.
Click to expand...
Click to collapse
I will def give this a shot thanks
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
snapper915 said:
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Did you read the directions?
but sounds like you don't have sdk set up right.....but I don't use tool kits....easy to do yourself without tool kit
Setup sdk
Fastboot oem unlock
Fastboot flash recovery
Flash super user from recovery
Sent from my Galaxy Nexus using Tapatalk 2
Epix4G said:
Did you read the directions?
but sounds like you don't have sdk set up right.....but I don't use tool kits....easy to do yourself without tool kit
Setup sdk
Fastboot oem unlock
Fastboot flash recovery
Flash super user from recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How do i set up sdk. Lol. I thought I had it.
Sent from my Galaxy Nexus using XDA
snapper915 said:
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
You did not setup the drivers correctly. Once the phone boots into the bootloader there is an additional driver that needs to be installed. I forget the exact one but it is included in the toolkit. You probably have some unknown device in your device manager that you need to install the included drivers for in the WugFresh toolkit.
I had the same issue when I first started.
HeCareth said:
You did not setup the drivers correctly. Once the phone boots into the bootloader there is an additional driver that needs to be installed. I forget the exact one but it is included in the toolkit. You probably have some unknown device in your device manager that you need to install the included drivers for in the WugFresh toolkit.
I had the same issue when I first started.
Click to expand...
Click to collapse
Oh ok. Let me look there. Hopefully I can figure this mess out. Lol
Sent from my Galaxy Nexus using XDA
Download PDAnet and install it. This will solve the driver issue. Your issue is that your computer is not recognizing the phone as an ADB interface.
I was having the same problem and corrected it by plugging my phone into the USB port on the back of my PC rather than the one on the front. You can also contact WugFresh for assistance if you still can't figure it out. I had to follow the instructions on manually installing the drivers to my PC.
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah usb debugging is enabled. :crying:
Unplug your phone from computer install the drivers from Samsung's website. (Google USB drivers for galaxy nexus i515) reboot computer and try again. Maybe u should install android SDK with adb and do it manually instead of using a toolkit. Those cause problems.
Sent from my Galaxy Nexus using xda premium
Its a driver problem, for sure. OP, stop being lazy please, learn from this here, and after that, like Zepius says, put your big boys pants on and do it like this
Sent from my Nexus 10 using xda app-developers app
Ohhh the universal naked drivers. I never even thought of that. Actually i did. I have installed them same issue. I have fallowed the instructions in your first link prior to starting this thread. I appreciate the help but your attempt to call me lazy is wrong. Still unable to flash cwm or anything from the computer however i was able to flash cwrm touch today after buying the rom manager premium. Still doesnt explain why i cannot do it from my computer. Mind you i attempted this on my laptop (slackerware) and i did still have issues.
I think it is somthing with the port on my phone ror maybe somthing else. Regardless, im not lazy for i do know where google is and how to abuse all of her abilities. I know where the forum search button is also.
Drivers i have tried.
Naked nexus drivers
Windows native drivers
Slackerware mobile drivers
Samsung drivers
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Sent from my GT-N8013 using xda app-developers app
5imp7y said:
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Click to expand...
Click to collapse
Are you confusing adb with fastboot, or was "adb flash recovery recovery.img" a typo? Anyway, forget the toolkit. Get adb/fastboot binaries from the 101 & FAQ, and try:
1) booted into Android: adb devices
This should list your device with a number. If the list is empty, adb cannot interface with your gnex.
2) booted into the bootloader: fastboot devices
This should also list your device with a number. If the list is empty, fastboot cannot interface with your gnex.
Note that the adb and the fastboot interface are different. If you installed drivers and got adb running, this does not automatically make fastboot working. Boot into fastboot, connect and use device manager to scout for unknown devices. Update using naked driver if necessary.
5imp7y said:
im not lazy
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Click to expand...
Click to collapse
you are lazy. you're relying on a toolkit.
please root your phone the manual way, or at least try fastboot alone so we actually know what the problem is.
Thanks yeah that was a typo. I have the adroid bianarys. Adb and fastboot. I was typing. Fastboot reboot bootloader to try and get gnex tools to see the device. No luck.
Sent from my GT-N8013 using XDA Premium HD app
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
If you know how to root manually, then surely you must know how to boot or flash a custom recovery like twrp or cwm with fastboot.
Sent from my Nexus
Fastboot flash recovery "your recovery img here". Still said waiting for device....
Edit:
so many typos my bad it is hard to type on my phone or tablet with fat fingers.
Seriously though, to the 2 people taking time out of their day to be jerks, grow up im done with this thread.
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
Fastboot flash recover your recovery img here. Still said waiting for device....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host (PC/Mac) and client (device) see and recognise each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Nexus
bk201doesntexist said:
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host and client see each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
BUT! in the gnex tool kit my serial number is displayed...?
5imp7y said:
BUT! in the gnex tool kit my serial number is displayed...?
Click to expand...
Click to collapse
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Let's try and be as friendly as possible when trying to help someone.
Thanks bk201doesntexist for trying to help.
bk201doesntexist said:
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Click to expand...
Click to collapse
if not a driver issue, it must be this.
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.
driver: http://www.samsung.com/us/support/owners/product/GT-I9250TSGGEN#
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