I`m trying to flash new recovery,but i can`t write in sdk tool command line=(
I have to type fastboot flash recovery recovery.img but I can`t(offcourse I start my device in fastboot protocol)
where to write and in which folder I have to put `recovery.img`
sorry for my noob question
I found anything what I want, but now it says that device not found
Put the recovery image in the same folder as fastboot
Sent from my Nexus S using XDA App
but
were is mine fastboot?
I have to flash only recovery
upd
I found anything what I want, but now it says that device not found
Fastboot is either in the tools folder. Go read the quides on how to use fastboot/adb root restore etc. You clearly are currently over your head. All the info is here on the forums the stickies.
ok
but what about error : devices not found ?
I`ve tryed to change usb ports,re-installing drivers what to do?
TechnoManiac97 said:
ok
but what about error : devices not found ?
I`ve tryed to change usb ports,re-installing drivers what to do?
Click to expand...
Click to collapse
Make sure that usb debugging is checked off in settings.
You have two threads and you're just confusing your self.
First you can't flash recovery with just adb without root.
In order to flash a recover you need to use fastboot. The device itself needs to be in fastboot mode/protocol or whatever it is called. It also needs to be unlocked which yours is not.
So forget adb for now. Get the device to show up with the command fastboot devices. Then unlock ( will wipe everything) . Device will reboot. Put it back in fastboot and flash recovery.
My xoom is rooted
Related
last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Hello,
again i need help I have unlocked the bootloader on my Xoom, the i have flashed TWRP and downloaded a Rom and the Gapps. I copied the gapps onto the device and followed instructions which came with the rom. I was instructed to wipe "system" too which i did.
Of course that deleted the downloaded rom and gapps too. Now i have TWRP and was excited to mount USB storage and just copy over again the rom and gapps but unfortunately there is no mount as USB option.
What and how is the smartest way to go about it? I wanted to sideload over ADB but the device is not found. I have really tried everythin in my knowledge, hope someone can help
cheers
Come on guys, really need help here. My kids are killing me for the damn thing
I have same problem.......it's an issue of twrp !
Have you tried a micro sd card? (copy the rom and gapps there from a pc then put it in the Xoom, etc...)
Worst case, you should be able to grab the stock images http://forum.xda-developers.com/wiki/Motorola_Xoom and fastboot flash the device back to stock.
Have the same problem
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
Stock flash doesnt require adb, just fastboot mode. You may need to still install a driver, but if you can boot into recovery then the xoom should also be able to boot into fastboot mode and be recognized by a pc. If the instructions on the link I gave arent enough, I will see if I cant find something tomorrow when I am on a pc.
Sent from my GT-N8013 using XDA Premium 4 mobile app
hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Solved
airesch said:
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Click to expand...
Click to collapse
Hey airesch, thank you for your support. I couldn´t follow yours suggestion because my xoom was not recognizing the PC or MAC. However I discovered that my sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks
Well, that works too, and that was closer to what I originally suggested (tho I didn't expect you had a bad sd card.)
And yes, recoveries generally don't support IMG files directly, you need to have a specially crafted zip to flash those in. IMG files directly are for fastboot/pc tool flashing.
Congrats on fixing it.
hey guys i have a question.. i made a total n00b mistake and now i am not sure what to do..
I have a htc one s
-i rooted the phone and put twrp 2.8 the newest one then i tried to load a custom rom.. i read somewhere on line that you did not need s off to do this so i tried and now everytime the phone boots it loads the htc screen but goes to a black screen which is kind of dim .. anyway my bootloader is unlocked its version 2.15 and i can get back in to my recovery and mount it i tried several roms but none work.. i was wondering if someone here has a stock rom or something that can get my phone to boot in to a os.. i have tried using fastboot to try and s off but everywhere i read it says u need debugging on my drivers are installed correctly but when u do adb devices it shows empty space.. ive tried many drivers even the google generic i cannot get it to work for the life of me... any help will be appriciated
cheers
Sam
Well let's take it easy. There were some things you've missed when reading so that's why you run into problems.
First thing you missed is that YOU MUST FLASH THE KERNEL IN FASTBOOT if you're S-On. That is EVERYTIME you flash a ROM.
Second, when you're in fastboot, you won't have "ADB devices" command working, you'll have to use "fastboot devices" command instead, ADB does not work while in fastboot.
What you'll have to do is like this:
1. Take any ROM you'd like to flash, place it on your sdcard (while you're in recovery you can mount sdcard to be accessible from pc)
2. Extract from the rom and save it on your pc (in the same folder where adb/fastboot commands are, usually /android-sdk/platform-tools) the "boot.img" file that's in the root of the ROM zip. That'll be called generic "the kernel".
3. Flash the ROM in recovery
4. Reboot to bootloader then while still connected to pc via USB, select fastboot mode. On your screen the "fastboot USB" will be shown.
5. Check if fastboot drivers are installed and fastboot commands are working by issuing "fastboot devices" command. If it'll not return your device then check if drivers are installed properly and you are not using an USB 3.0 port on windows 8.1 (were reported some issues with this configuration).
6. Having fastboot working, open command prompt in the location where fastboot is (and where you have saved the boot.img file) and issue the command: "fastboot flash boot boot.img"
7. Reboot
Now your new ROM should boot and work. Pay attention to choose the right ROM for your hboot and don't forget to do these steps EVERYTIME you're flashing a ROM.
If you're still looking for a stock ROM to flash, there's a thread with all RUUs linked, choose the one for your carrier or model type and run that one but I guess you won't need that
Good luck
Sent from nowhere over the air...
My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.
Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?
Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.