[Q] code name android ics fastboot issue - Nexus S Q&A, Help & Troubleshooting

hey guys, the issue I am having is that I am trying to side load rom manager touch but when I enter fastboot reboot bootloader it just says waiting for device. everything worked fine while running GB but now this. I also tried booting into fastboot and running the command, but still nothing. I downloaded the latest version of pda net. dont know if that makes a difference. also usb debugging is selected in developers options. any ideas?

Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk

gm` said:
Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.

Yes u can via flashboot.
Flashboot recovery newrecovery.img
Sent from my Nexus S using Tapatalk

CaptEvo said:
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.
Click to expand...
Click to collapse
Because is not in fastboot mode
Sent from my Nexus S using Tapatalk

I get that, any idea how to get into fastboot now?

In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc

I would love to do that except when I go into boot loader there is no option for fastboot

albundy2010 said:
In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc
Click to expand...
Click to collapse
Dear lord, I guess I forgot a bunch of stuff. Thanks for refreshing my memory
Got it done.

CaptEvo said:
I would love to do that except when I go into boot loader there is no option for fastboot
Click to expand...
Click to collapse
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S

DarkhShadow said:
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes thats true. But before running the commands run : fastboot devices. If you see a long number youre jn fastboot mode and the drivers are correctly installed.
Then you can run the commands
Sent from my Nexus S using xda premium

Related

[Q]ICS without root and locked bootloader

I updated my i9023 to ICS using the stock recovery. Now I dont have a recovery since the ics update bugged it and my bootloader is locked. How am I supposed to unlock/install cmw/root?
Thx in advance.
andrei.voinea93 said:
I updated my i9023 to ICS using the stock recovery. Now I dont have a recovery since the ics update bugged it and my bootloader is locked. How am I supposed to unlock/install cmw/root?
Thx in advance.
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?t=1396913
I cannot boot in stock recovery to install the zip as described in that post
Sent from my Nexus S using XDA App
andrei.voinea93 said:
I cannot boot in stock recovery to install the zip as described in that post
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Try fastboot & try to flash clockwork.img recovery!
unlock bootloader doesnot work
We all know the standard commands to unlock the bootloader but for some reason on my Nexus S device, the bootloader unlock is not working. Here is what I did,
1. Connect the device and type 'fastboot oem unlock'
2. It brings up a menu to select "No" or "YES" to unlock options...I navigated through volume up key to select "YES" to unlock boot loader.
3. Now I have to restart the device by pressing power button, the POWER BUTTON doesn't respond there by bootloader unlock doesn't complete.
4. It just hangs in bootloader unlock screen forever.
Does anyone faced this issue? why this happens??
please help me out.
Thanks and regards,
-Lakshman
Fastboot oem unlock wont see my nexus. It says its waiting for a device even if i installed the needed deivers
Sent from my Nexus S using XDA App
andrei.voinea93 said:
Fastboot oem unlock wont see my nexus. It says its waiting for a device even if i installed the needed deivers
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You need to be in the boot loader for that to work.
I am
Sent from my Nexus S using XDA App
I've the same Problem. I'm in the bootloader and it says Fastboot Mode but the device is not recognized via USB.
Therefore fastboot is just waiting for devices.
Any suggestions? When my nexus is booted i can connect it als USB-Storage and so on.
I fixed it using the sdk drivers and the fastboot and adb files from the sdk (path/android/platform-tools).
Didn't work for me. I'm always using SDK.
My Bootloader is unlocked. (the little lock ist opened )
I just tried it on a completly different computer. just setted up a new SDK on my laptop.
Am I doing something wrong?
I've USB-Debug Mode enabled.
I boot holding VOL up + Power Button to enter the bootloader
Plug in the USB cable
and then i try ~android-sdk/platform-tools/fastboot flash recovery myrecovery.img
Here my Fastboot says wating for device.
If i'm booted up on my rom i can connect via adb and get a my device via adb devices.
Probably something wrong with my fastboot.exe?

Fastboot not working anymore?

Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Also tried in Ubuntu still no luck >_<
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
bige914 said:
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I am using a Asus Laptop. Thanks for the response!
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
got the same issue guys
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
We are all stuck with this unless we send it to asus for RMA
Sent from my VS840 4G using xda premium
SpyFi said:
Also tried in Ubuntu still no luck >_<
Click to expand...
Click to collapse
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
the problem is not the computer itself, the real problem is that the tablet doesn't get in fastboot mode...
Thank you for the update.
SpyFi said:
Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Click to expand...
Click to collapse
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
matt95 said:
got the same issue guys
Click to expand...
Click to collapse
partypage said:
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
Click to expand...
Click to collapse
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
Try this:
-use unlock tool
-boot tablet into USB MODE
(it will say fastboot mode,waiting)
-using the steps,copying over the fastboot files to one folder, with TWRP as the recovery, run fastboot command.
-done successfully,you be good
Click to expand...
Click to collapse
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
I decided to automate the process of entering commands. Post
philos64 said:
Try this:
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
Click to expand...
Click to collapse
thank you, i'll try this out tomorrow! :good:
no way, i can't get it to fastboot damn it
---------- Post added at 11:45 PM ---------- Previous post was at 11:16 PM ----------
ok i solved the problem just now...
1-reboot the tablet in bootloader while connected to usb
2-use vol down to navigate to the usb mode and then vol up
3-the tablet won't show nothing but actually it is connected
4-proceed to any fastboot command
hope this helps
I had this issue when I first started flashing stuff (although I was flashing CWM not TWRP)
In my experience, if you don't see anything listed in fastboot devices, it doesn't matter because it still flashes.
Just try using the flash command (fastboot -i 0x0b05 flash blah blah blah.blah) and see if it works.
You -should- be able to see your device in "adb devices", and that's really what matters.
Also, what matt95 said is exactly what I do. Whether it shows anything or not, I just flash my stuff. Works fine, but I also don't use fastboot alot because with the new changes to the bootloader, one can flash stock through CWM now without having to fastboot flash it.
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
jm700wx said:
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
Click to expand...
Click to collapse
my solution above didn't help?
matt95 said:
my solution above didn't help?
Click to expand...
Click to collapse
I'm in the same wagon as all you guys, I just tried that and I can't get into fastboot still. Still waiting for device
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
I'm sorted now, I didn't realise that we needed a different command
I was using
Code:
fastboot flash recovery recovery-jb-touch.img
instead of the correct method of using
Code:
fastboot -i 0x0B05 flash recovery recovery-jb-touch.img
This worked perfectly
it's same as this:
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files => Root files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread or TWRP recovery and download this file : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery twrp.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
Click to expand...
Click to collapse

[Q] Reboots no recovery only fastboot

I have a one xl that will reboot after being on for 2 minutes
evita pvt ship s-on rl
hboot-1.14.0002
it is unlocked, but i cant relock it. Every time i try it says fails then reboots. I have also tried flashing twrp and cwm recovery via fastboot, but everytime i try to enter one it hangs on the teamwin screen. I have tried the ruu it reads my phone at first then when it says rebooting to bootloader the phone reboots normaly and get error 107.
Any help would be greatly appreciated.
What method are you using to try to relock the phone? What method are you using to install the mentioned recoveries? Please give as much detailed information as possible.
Sent from my Evita.
To relock i have used fastboot in cmd and typed fastboot oem lock. I have done that 10 times with the same result phone reboots normally and when i reboot back into bootloader it still says unlocked.
To flash recoveries i have used fastboot flash recovery ********.img
fastboot erase cache
fastboot reboot-bootloader
but instead of rebooting to the bootloader it boots normally
What did you do to the phone before all this started happening? Phones don't usually just start doing things like this of their own accord.
Sent from my Evita.
I bought it like this. The last owner said it happend after he installed a rom. I was hopping i could unbrick it with out jtagging it becuase i am still able to fastboot to it.
If you can't get an RUU to work I think jtag might be your only option.
Sent from my Evita.
I've only tried 2.20. I even extracted the system IMG from it but fast boot says it is too large. The only reason ruu won't work is because I can't get my phone to reboot into boot loader. Is there any way I can flash a different boot loader through fast boot.
Just curious, but when you type fastboot devices from the Bootloader, what is the output?
Are you running fastboot oem lock from the bootloader?
Sent from my One X using XDA Premium 4 mobile app
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
keithman2567 said:
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
Click to expand...
Click to collapse
If when you type fastboot devices (while in the boot loader) in your computers command prompt, and it doesn't show your HTC device being attached, that means that your computer is not recognizing your phone. Have you installed the HTC drivers? Do you have the newest versions of fastboot and adb installed?
What OS are you running on your computer?
Sent from my One X using XDA Premium 4 mobile app
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
keithman2567 said:
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
Click to expand...
Click to collapse
Does your device boot into the ROM at all?
Sent from my One X using XDA Premium 4 mobile app
Yes. But only for 2 mins before it reboots.
keithman2567 said:
Yes. But only for 2 mins before it reboots.
Click to expand...
Click to collapse
If you can connect to Google Play store, download recovery tools, if you have time. From there you could try to install a new recovery for your device. With only 2 minutes you will have to be quick though.
Do you have access to your sdcard from your computer?
Sent from my One X using XDA Premium 4 mobile app
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
keithman2567 said:
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
Click to expand...
Click to collapse
Here is the app. Not sure if you'll have time, but you can try
https://www.dropbox.com/s/wa4u565woyrrrlw/de.mkrtchyan.recoverytools-2.apk
Sent from my One X using XDA Premium 4 mobile app
Thank you, but there isn't enough time to even transfer it over
keithman2567 said:
Thank you, but there isn't enough time to even transfer it over
Click to expand...
Click to collapse
Do you have USB debugging enabled in the phone?
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 10:22 PM ---------- Previous post was at 10:15 PM ----------
Have you tried to flash a new ROM from fastboot? It sounds like your recovery partition might have been corrupted.
Sent from my One X using XDA Premium 4 mobile app
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
keithman2567 said:
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
Click to expand...
Click to collapse
Alright, so I have a few ideas.
1. Try flashing a new rom via fastboot. (the following is based on the assumption that you have adb and fastboot in your path)
Flashing a ROM through Fastboot
So Why Do I Need To Do This?
You don't, normally you would flash a ROM through recovery, but why not have another way? Maybe your recovery partition on your phone is corrupt?
Maybe you just want to say "I learned something new!" whatever your reason here are the simple steps:
To start:
Quote:
Quote:
We need to download the ROM of choice to your computer. Once complete find the folder that rom is in and open terminal/cmd to that directory
(quickest way for windows; just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
2. Boot into Recovery via fastboot.
Plug phone into PC, connect with USB cable and have phone in fastboot mode, now open CMD/Terminal in the same directory as your recovery image
Code:
fastboot boot recovery.img
Of course name image correctly to fit command or vise versa
Now you are in recovery of choice within your device without it being flashed to your recovery partition. There is a time and a place for everything, can you think of ways this may help you? Sure you can!
This doesn't actually flash the recovery.img... it will just allow you to boot into it. Make sure that you have a good TWRP version.
The previous quotes were taken from this guide on XDA-University:
http://forum.xda-developers.com/showthread.php?t=2277112

Problem with Nexus Root Toolkit v1.8.4 and nexus5

Hi to all,
I want to install a cwm (the last one) becouse the android update 4.4.4 has erase my recovery.
I run the program, i go to launch and I click Recovery in boot/Flash image.
The program download the last version of recovery anche restart nexus5 in bootloader menu and instal a recovery.
After that restart the phone again and it works perfectly but when I go to recovery mode, it doesn't work. I try more times but doesn't work!
The phone is unlocked and before update 4.4.4 the recovery worked perfectly.
Somebody can resolve thi problem?
Thanks.
Fastboot
moscast said:
Hi to all,
I want to install a cwm (the last one) becouse the android update 4.4.4 has erase my recovery.
I run the program, i go to launch and I click Recovery in boot/Flash image.
The program download the last version of recovery anche restart nexus5 in bootloader menu and instal a recovery.
After that restart the phone again and it works perfectly but when I go to recovery mode, it doesn't work. I try more times but doesn't work!
The phone is unlocked and before update 4.4.4 the recovery worked perfectly.
Somebody can resolve thi problem?
Thanks.
Click to expand...
Click to collapse
Flash through fastboot and see if it works, but that's the wrong section to ask a question..
thunder_bolt96 said:
Flash through fastboot and see if it works, but that's the wrong section to ask a question..
Click to expand...
Click to collapse
ok thanks but can i use this tool?
http://forum.xda-developers.com/goo...tool-nexus-5-multi-tool-3-unlock-cwm-t2509428
The problem is that the link for downloading it does't work.
The firs time that I unlock, and flash recovery and root I used that software.
Can you replace it or give me another link?
Thanks again anche sorry for wonge section....
No. Do NOT use tools like this.
OTA removes root and replaces recovery.
If you want a recovery Download cwm, philz or twrp and fastboot flash recovery image from your pc
If you click the link to the sticky roll-up in my signature, you will find a thread there in section 1 called "adb and fastboot, what is it?". Please read it. You will know everything you need to know
Sent from my Nexus 5 using Tapatalk
moscast said:
ok thanks but can i use this tool?
http://forum.xda-developers.com/goo...tool-nexus-5-multi-tool-3-unlock-cwm-t2509428
The problem is that the link for downloading it does't work.
The firs time that I unlock, and flash recovery and root I used that software.
Can you replace it or give me another link?
Thanks again anche sorry for wonge section....
Click to expand...
Click to collapse
Fastboot flashing a recovery would take less time than it took for you to type out that post.
Thanks all.
I read and I understand that I have to send this commands:
Adb reboot and when device go to bootloader a send:
Fastboot flash recovery recovery. Img
Is it correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app
moscast said:
Thanks all.
I read and I understand that I have to send this commands:
Adb reboot and when device go to bootloader a send:
Fastboot flash recovery recovery. Img
Is it correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Multiple ways to get into the bootloader. Another is hold vol down whilst turning on your phone
Since I suggested you read my adb and fastboot thread, I added a new section about command prompt. It explains that you need to tell cmd where the recovery image is but otherwise correct.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Multiple ways to get into the bootloader. Another is hold vol down whilst turning on your phone
Since I suggested you read my adb and fastboot thread, I added a new section about command prompt. It explains that you need to tell cmd where the recovery image is but otherwise correct.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
moscast said:
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
sweet, and you did it the right way. now honestly, compared to a root toolkits, isnt the right way easy?
moscast said:
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
I'm so glad you took the time to read, understand and do. Now when you have other issues, the knowledge you just learnt will be invaluable.
Sent from my Nexus 5 using Tapatalk

fastboot command "fastboot boot mycwm.img" problem

all dones!!
first i open command in the folder by shift+right click and selecting "open command window here"
usb debugging on
typed "adb devices"
it is detected
typed "adb boot bootloader"
it is gone to download mode
typed "fastboot devices"
fastboot device detected
typed "fastboot boot mycwm.img"
shows download complete
and shows booting.....
here problem starts
it takes a lot time ..
i was taken it 1hour and 14minutes
but nothing happened:crying::crying::crying:
device working fine . boots normally. no damage
but i cant go in the cwm recovery
SHARUK154 said:
all dones!!
first i open command in the folder by shift+right click and selecting "open command window here"
usb debugging on
typed "adb devices"
it is detected
typed "adb boot bootloader"
it is gone to download mode
typed "fastboot devices"
fastboot device detected
typed "fastboot boot mycwm.img"
shows download complete
and shows booting.....
here problem starts
it takes a lot time ..
i was taken it 1hour and 14minutes
but nothing happened:crying::crying::crying:
device working fine . boots normally. no damage
but i cant go in the cwm recovery
Click to expand...
Click to collapse
Is the CWM you're using made for your specific device.
Sent from my SM-S903VL using Tapatalk
SHARUK154 said:
all dones!!
first i open command in the folder by shift+right click and selecting "open command window here"
usb debugging on
typed "adb devices"
it is detected
typed "adb boot bootloader"
it is gone to download mode
typed "fastboot devices"
fastboot device detected
typed "fastboot boot mycwm.img"
shows download complete
and shows booting.....
here problem starts
it takes a lot time ..
i was taken it 1hour and 14minutes
but nothing happened:crying::crying::crying:
device working fine . boots normally. no damage
but i cant go in the cwm recovery
Click to expand...
Click to collapse
Hmm, you forgot to flash CWM recovery, you just typing to boot to recovery, so yeah, ended up with stock recovery.
First run this command ~
Fastboot flash recovery mycwm.img - - once it's success, then this command ~
Fastboot boot mycwm.ing - - Give it some time, it'll boot to CWM.
sachin n said:
Hmm, you forgot to flash CWM recovery, you just typing to boot to recovery, so yeah, ended up with stock recovery.
First run this command ~
Fastboot flash recovery mycwm.img - - once it's success, then this command ~
Fastboot boot mycwm.ing - - Give it some time, it'll boot to CWM.
Click to expand...
Click to collapse
The fastboot boot command should have worked to boot the CWM.img directly without flashing shouldn't it?
I don't have a device that uses fastboot but I've dealt with users that have used fastboot boot to boot an .img without actually flashing the .img. Am I missing something?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The fastboot boot command should have worked to boot the CWM.img directly without flashing shouldn't it?
I don't have a device that uses fastboot but I've dealt with users that have used fastboot boot to boot an .img without actually flashing the .img. Am I missing something?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Oh, I've never used cwm, my all device's have twrp, since we flash twrp [fastboot flash recovery <whatevertherecoveryname.img>] before using the command boot to " recovery.img" thought this would goes with the cwm too. That's why I suggested him.
Never knew that we can boot to cwm without actually flashing it using fastboot command.
Thanks.
sachin n said:
Oh, I've never used cwm, my all device's have twrp, since we flash twrp [fastboot flash recovery <whatevertherecoveryname.img>] before using the command boot to " recovery.img" thought this would goes with the cwm too. That's why I suggested him.
Never knew that we can boot to cwm without actually flashing it via fastboot.
Thanks.
Click to expand...
Click to collapse
I could also be wrong about the specifics of its useage but I have read of testing a .img to see if it's compatible with a device before actually flashing it to avoid bricking since nothing is being written to the device by only booting the .img, then if it works, the user knows they can safely flash it without harming the device or continue just using it temporarily and only boot it when they need it instead of flashing it permanently. If it doesn't work the device can just be rebooted and no harm no foul.
This is one way for users with devices that have no custom recovery for their model to test a recovery from a different model to see if it can be used.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I could also be wrong about the specifics of its useage but I have read of testing a .img to see if it's compatible with a device before actually flashing it to avoid bricking since nothing is being written to the device by only booting the .img, then if it works, the user knows they can safely flash it without harming the device or continue just using it temporarily and only boot it when they need it instead of flashing it permanently. If it doesn't work the device can just be rebooted and no harm no foul.
This is one way for users with devices that have no custom recovery for their model to test a recovery from a different model to see if it can be used.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Whoah, Nice.
Thanks for the tip :good:
sachin n said:
Whoah, Nice.
Thanks for the tip :good:
Click to expand...
Click to collapse
But....
As with all things android, this method does not work on all devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
But....
As with all things android, this method does not work on all devices.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yep
Droidriven said:
Is the CWM you're using made for your specific device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
it is not made for my device
my device is not support permanent flashing.
once i flashed with the same cwm.img.
but it bricked.
before it bricks its works for me
fastboot boot cwm.img
but now it only stuck on booting
in this forum there written that "infocus m2 4g is not permanentaly flashable , you have to port cwm.img each time from pc".

Categories

Resources