Hi
I've searched for a solution but didn't find one for my problem so...
I was trying to flash an updated kernel through Kernel Manager application and then it said it cannot complete task and asked me to reboot system.
I then entered into the recovery and flashed the kernel manually.
When rebooted system I got the message "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
So naturally I thought maybe it lost the recovery so I went and flashed CWM recovery 3.0.2.5 (had 3.0.2.4 when all this happened) through fastboot and that went OK.
I then entered the recovery to make sure the recovery flashing went OK and pressed Restart system now.
But then it started the bootloader and the same message appeared "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
I repeated that process few times and same thing.
The strange thing is when I select "REBOOT BOOTLOADER" and it boots into bootloader I see "FASTBOOT MODE" in red at the top. But when I try to reboot the phose I see the message to the top again.
How can I get out of this?
Hi guys,
I've got the same problem, although I don't know if it IS a problem.
I'm running v7.0.0-NS and I'm going to upgrade to v7.0.3 ... just searching for instructions!!!
~AndrewGoldy
since I am able to enter the recovery Im trying to restore an earlier backup. Not sure it this will do anything since my problem is in the bootloader area.
If this makes my phone to start up normally then I really dont understand this.
*** I think that I've just fixed it ***
I opened up "Rom Manager v4.2.0.2", and then selected the option to "Flash ClockworkMod Recovery"
Once it had downloaded "ClockworkMod Recovery v3.0.2.4", I selected the option to "Reboot into Recovery".
That worked.
It now says "Fastboot Mode" when I boot into the Bootloader.
Success!!!! (I think)
Well it just finished restoring the backup.
It seems it solved the problem on mine to since it passed the bootloader and the boot animation is on.
I really cant understand this.
I've done the same but the Recovery Stil nor Bootloader works. However it does say Fast boot mode now instead of no boot or recovery img. But still can't flash or back up a rom!
Correction i got it work after flashing to oldest recovery that was an option
I fixed this problem (Nexus S) by reverting to an older (3.0.2.4) CMRecovery, just go down to the last option "All ClockworkMod Recoveries" and Flash an older version (mine was not working with 5.0.2.0).
Hi! Anyoane can help me ?
I disconnected by accidently the USB cable while the phone was at the ClockWorkMod Recovery v5.0.2.0/-mounts and storage/-mount USB storage, and after that ( adb , fastboot and usb died).
I installed Stock OTA 2.3.6 I9023 for my Nexus S I9023. During the day phone closed and no longer wanted to open (even replace the battery). After more hours the phone is open , adb and usb works not for a long time after several attempts ( during this time I managed it to root and install CWM 5.0.2.0 back)
I flashed ICS Kwiboo v3 . After reboot the phone began to froze , and shortaly closed.
Because the phone will no longer open I tried in CWM all ( wipe data:fact, wipe cache, wipe dalvik, format/all ) .
Now if reboot system on CWM I have Fastboot Mode - No Boot or Recovery IMG
but if I reboot bootloader or power off when is opened is just Fastboot Mode .
Adb , fastboot and mount USB still no work. ( I have SDK 14 on windows7 installed, all the driver for Nexus S was updated).
Because the PC not recognized my phon I can't install another ROM or CWM.
( When USB cable connecting on the phone it's charge the battery only!).
Thanks for your advice!
No recovery img & fastboot devices -> nothing
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
saychand said:
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
Click to expand...
Click to collapse
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Thank you guys for your replys.
surdu_petru said:
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
Click to expand...
Click to collapse
1. I removed the battery for 10mn. When I come back to the bootloader "ADB devices" doesn't return a device, so it doesn't see my phone. But when switched on, it can see it.
2. Yes, it is. There is the SuperUser app, and when apps ask for root, I can allow or deny. And the lock state is 'unlocked'
akabadnews said:
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
Click to expand...
Click to collapse
I tried the latest, the oldest, the versions inbetween... nothing. I have the latest version of CWM and I reflashed the last Recovery from the app.
I can't flash another ROM, because I need recovery mode for that ; and my problem is that I can't access recovery indeed... :/ I feel like I need A to do B, and B to do A.
"No boot or recovery img": doesn't it mean that I should put some file somewhere ? I hope it would be that simple.
Do you have other ideas ?
---------- Post added at 01:33 PM ---------- Previous post was at 01:24 PM ----------
AllGamer said:
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried several time, flashing different versions of CWM recovery. I've returned to bootloader -> recovery dozens of time and I still have the "no boot no recovery img". I'll try again.
All the threads which speak about it and mention to flash another rom -> yeah thanks, but I can't access recovery
Threads mentioning fastboot -> I tried with different drivers (including 1.0 and 4.0), but fastboot won't see/talk to my device
Do you see something else that I didn't try ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:33 PM ----------
I also tried this which seems to be a good step
http://forum.xda-developers.com/showthread.php?t=1356319
Basically it says
adb shell
SU
flash_image recovery /sdcard/filename.img
But like the guy in thread, I have memory errors "mtd: read error at 0x00000000 (out of memory)" then write errors, then "failed with error: -1" and "error writing recovery"
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
saychand said:
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
Click to expand...
Click to collapse
THANKS! This helped A TON!
I did the PDA installation again, and for some reason this seemed to fix my inability to access recovery.
Agreed on Rom manager, I updated CWM through rom manager and I believe that's what buggered up my recovery, as I have never had trouble accessing it before I did that.
But again, a big THANKS for that suggestion!
Hi,
I just unlocked and rooted my Nex 10 today, installed a custom recovery and everything done by the book.
I did it a couple of times, even three cause every time I installed the recovery CWM or TWRP it worked right after I installed it.
Then I rebooted the tablet, tried to get back into the recovery, and always dead droid
Can someone please tell me what am I doing wrong???
Also can I install the latest SuperSU version??
Thanks
When you say by the book where your steps
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And then you choose recovery it works, you flashed a ROM, then booted to ROM but when you boot back to recovery it has been replaced with stock?
It sounds like you may have ran the wrong command like
fastboot boot nameofrecovery.img
In this case you would not overwrite existing recovery with custom
Sent from my Nexus 7 using XDA Premium 4 mobile app
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
x0nar said:
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
Click to expand...
Click to collapse
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You have to install marshmallow firmware first.
Best option would be to go back to the working TWRP version, flash oxygenos, reboot to Oxygen once, flash new recovery in fastboot, reboot recovery, flash rom
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't know if this does anything different, but here's what worked for me
1. Ensure that device enters into fastboot mode
2. "fastboot flash recovery recovery.img"
3. **IMP** After your flashing is successful, directly enter the device into recovery mode by pressimg Power (+) Vol Down button.
4. Now a TWRP prompt shall appear asking your permit for modifications, swipe yes.
Note that: I'm not sure if this makes a difference, but earlier I rebooted after Fastboot and then entered into recovery, but the key was to directly enter into recovery after fastboot.
Let me know if that works for you.
I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
you can try this
ajyotirmay said:
I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
Click to expand...
Click to collapse
Get into the fastboot mode try again unlock your oem
'fastboot oem unlock'(volume up on your phone and select yes ) --->'fastboot format userdata' now flash the twrp recovery the link is below try this it may work worked fine for me and dont know really why the updated twrp is not flashing
My Google Drive link for TWRP recovery:-https://drive.google.com/file/d/0BylQ6RZ2mIP_cElxMzFoRVEyRDg/view?usp=sharing
Hello, i installed dotos custom rom and gapps after flashed TWRP without root access (i don't want to root my device), all was good, the custom rom work good, so to day i manage to reinstall the same rom with another time gapps (the cause is for delete some application), all was good , and i read that it's good to make a hard reset for that the rom work nicely (i do it from the setting), i do it but after that the smartphone reboot and stuck on TWRP, i reboot the system from TWRP but don't work, it open all the time TWRP, the recovery menu disaper (i use the key volume"-" and power button don't work it don't enter to the recovery mode), i can only boot to bootloader from TWRP and access fastboot mode:
=>fastboot mode
=>unlocked
i use "fastboot continu" to access system but sim don' work in this way. so i come to you for help, i want that the system work like before, thank for your patience and help.
Reboot into fastboot mode
Have at least minimal ADB interface and fastboot drivers installed
Use a command prompt to cd to ur fastboot drivers normally C:\adb
in the same folder have your TWRP recovery image.
Then use the command fastboot flash recovery [twrpfilename.img]
Then fastboot reboot
Hold power and vol down and once in the boot loader use volume up to select recovery then press power to boot into the recovery mode
Have magisk on your SD card or go to reboot and TWRP will root your device you must never try to unroot a custom ROM because at some point they will all fail and you'll be in this problem.. i have hundreds of different custom ROMs from Android 4 to 8 and not one of them has been flawless they all have issues and big problems in the end, like operating system breaking glitches your best off sticking with stock firmware and modded and debloating urselg