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!
Hello all,
I initally used the Wugz root toolkit to unlock, install drivers and root my device. I flashed CWM and a ROM. Once I flashed the ROM, it wouldn't boot, but would flash the google logo, go black, then go to the google logo and open up CWM again.
I searched for backups, they were gone. So I tried a few things and now I can't even get to CWM.
All I can get to is the Recovery menu and Stock Recovery. My computer won't recognize the device in adb fastboot but will recognize it when I put it into sideload from the stock recovery.
I've tried to flash the 4.1.2 and 4.2.2 images from the Google developer website but when it verifies the installation package it says installation aborted.
Is there any way I can fix this just from the Stock Recovery sideload? Is this hopelesss?
Take a look at this THREAD
Nico_60 said:
Take a look at this THREAD
Click to expand...
Click to collapse
Thanks. I did try this first, I must have messed it up somewhere. I'll try it again. Not sure if it'll work without the device being recognized under fastboot.
To know if it's recognized type "fastboot devices" but if the driver were already installed it must be ok
Whew got it to work. Thanks.
New to XDA so sorry if i posted this in the wrong place
But recently i received a new phone, an LG Stylo 2 Boost Mobile. It recognized fine while it was on through adb, but when i turned it off and booted into recovery, it wouldn't be recognized by adb, nor fastboot, and when i tried to "reboot into bootloader" it only restarted the whole phone into its normal boot. Adb sideload worked but i had no idea what files to try due to a locked bootloader and no stock ROMs found anywhere. I tried kingroot and it didn't have any ways to get an instant root. Im running Ubuntu and the phone is on 6.0.1 Marshmallow. Any ideas out there? I'd be sure to give them a try
The phone would only be accessible in recovery via the adb sideload option with stock recovery.
What exactly are you trying to accomplish?
es0tericcha0s said:
The phone would only be accessible in recovery via the adb sideload option with stock recovery.
What exactly are you trying to accomplish?
Click to expand...
Click to collapse
I'm trying to unlock the bootloader so i can flash a new recovery then root won't be hard to achieve, but when i try to access the phone in recovery mode, it doesn't recognize whatsoever. I thought there would be something i could do with sideload to somewhat downgrade the system and gain some type of bootloader, but that didn't work. Is there someway i can flash a custom recovery?
Don't believe there are any options for unlocking the bootloader or a custom recovery for that phone. According to what I could find in a quick search, there is root available but only on the software update ending in ZV3.
https://forum.xda-developers.com/lg-g-stylo/help/boost-mobile-lg-stylo-2-lgls775-t3388675
Alright, thanks for the info, wasn't sure if there was a way around it or not
Hi
I've been trying to go back to stock android using this post. I downloaded both the stock image and recovery.img, but I was stuck in a bootloop, constantly booting into TWRP. I tried one of two different images until H87020A finally worked. I flashed it using LG's download mode and LGUIP/Uppercut. I setup my phone etc, and then flashed H87020G using LGUIP/Uppercut. Now I'm on a working version V20G.
The only thing that doesn't work is recovery. I first tried the stock recovery that comes with the KDZs, but it keeps saying "No command" when I boot into recovery. Then I flashed latest TWRP (3.2.3) using fastboot and it showed succesful, but when booting into it I keep getting the "no command" error.
So now I have a few questions:
1. How can I get TWRP working on it? Should I keep flashing with fastboot until it works?
2. How can I extract a stock recovery imgage from the 20g KDZ I flashed? I tried using this extractor tool to get the DZ and finally the recvery.img, but there is no recovery.img. It consists only of recovery_10246.bin and recoverybak_20614.bin (and of course a bunch of other files, but none of them are called recovery)? I want to use the closest stock recovery.img to the KDZ I'm using so that there are no issues. I found one from V20B from Westworld24, but I'm not sure if that works fine with my version of Android.
3. Assuming I get TWRP to install, then flash the stock recovery using TWRP, can I then simply run "fastboot oem lock" in fastboot or do I need to do something else? Is it essential to flash a clean ROM first or can I just do it over the KDZ I flashed?
The reason I want to do this is because I wanna sell it on rebuy.com and I'm not sure whether they're fine with an unlocked phone. Also, when starting the LastPass app for the first time it says that it seems that my phone is rooted, so basically I'm not on a fully stock phone, which I want to be on when selling it.
Thanks in advance.
I have a Grand Prime Duos (SM-G530H), currently running an Android version 4.4.4 and I wanted to install a custom ROM to have a higher version of Android. (Tried installing LineageOS 17.1 from itexpert.120, but any custom ROM with a higher version of Android would do)
Problem 1: No custom recovery seems to work.
I installed the TWRP app and tried to flash 4 different versions of their recovery images (from twrp-3.7.0_9-0-fortuna3g.img to twrp-3.4.0-0-fortuna3g.img) and all of them resulted in a unless glitched gray recovery screen.
I also tried the CWM app but it fails to download a recovery image for the device, tried looking online for a image file but didn't find one either.
In the end I reverted the recovery to the default one that I had backed up.
Problem 2: ADB works but fastboot doesn't.
I downloaded the ADB tools to try and flash the ROM from my computer instead. The ADB commands work, but when the device enters recovery mode the fastboot commands don't work. ("fastboot devices" doesn't even list the device)
Went to check the drivers. Most tutorials say to open the device manager and look for the phone device with an exclamation mark and update the driver with ones downloaded from the official site. To my surprise the device doesn't show up at all in the device manager (not even with an exclamation mark). Trying to install the drivers anyway says it's already installed.
The Odin software showed the same problems, detects the device when it's on, but doesn't detect it when in recovery mode.
Problem 3: Error when installing directly through the recovery mode options.
This probably wouldn't work for technical reason I'm not aware of, but I went and tried anyway. On the default recovery mode there are 2 options, apply update from ADB and apply update from external storage. Tried both, the first using the command "adb sideload <lineage rom file>" and the second using the ROM file in a SD card. Both begin to unpack and install the file but after a while throw an error "E: failed to verify whole-file signature", then the device boots to the usual OS.
So, is there anything else I can try? any other recovery images or hacks that won't give me the glitched recovery that TWRP had? Or another method to install a ROM without fastboot? Maybe using another file format in problem 3?
OBS: the device is rooted and has no "OEM unlock" options in its settings
delete the samsung usb drivers and install an older version. only way you can flash custom recovery is with odin. only way to flash custom rom is with custom recovery. fastboot and sideload wont work, this isnt a nexus
You think the reason why the custom recovery was glitched is because it was flashed through the TWRP app and not Odin? Seems unlikely. Is there any non-TWRP recovery image for my model you can point me to?