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!
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel
sloanster said:
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel
Click to expand...
Click to collapse
Thanks for your reply. I have been flashing straight from the phone's memory, but I would still like to know what I can do to get the adb method working for future reference. If I accidentally get to a point where I can't boot properly and I don't have an available backup on the phone, I want to be able to flash from my desktop.
Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
I had similar problems with TWRP. I ended up searching around Google and found some drivers that worked. Some keywords I used were the Hardware ID(s) that the unknown device gave to Windows, and "twrp". It's just using a different version of ADB or something, and Windows doesn't like it. I'm out of time for today, but I'm sure you'll find it. Look for google results that take you either to XDA or over to TWRP's website.
Hi All,
Hope all are doing well. I'm posting this message on behalf of those people who are facing the most irritating problem currently(those who wants to root their devices on latest CM 12S lollipop 5.0) is:
Custom recovery image not updating, it shows recovery is updated message but when boot into recovery, the phone shows original recovery only, also it gives error of signature verification while applying root package (started pc with signature mode off) and its not rooted.
The following process are done by maximum users.
1. Installing the adb drivers correctly. Even we also used the manual methods to install adb drivers and it went well.
2. Also checked in the device manager. The Android ADB interface is there.
3. Tried Yureka All in one tool box and also manual method. 0% success.
4. Tried CWM and TWRP recovery. 0% success.
Pleas note that, rooting process went well in Kitkat (CM 11S) but not in Lollipop (CM 12S).
You will find lots of posts claiming can't replace custom recovery after bootloader unlock. But we didn't find a single or multiple way to fix this. So, What to do now? There is always a way to make this right. Please help.
das.palash89 said:
Hi All,
Hope all are doing well. I'm posting this message on behalf of those people who are facing the most irritating problem currently(those who wants to root their devices on latest CM 12S lollipop 5.0) is:
Custom recovery image not updating, it shows recovery is updated message but when boot into recovery, the phone shows original recovery only, also it gives error of signature verification while applying root package (started pc with signature mode off) and its not rooted.
The following process are done by maximum users.
1. Installing the adb drivers correctly. Even we also used the manual methods to install adb drivers and it went well.
2. Also checked in the device manager. The Android ADB interface is there.
3. Tried Yureka All in one tool box and also manual method. 0% success.
4. Tried CWM and TWRP recovery. 0% success.
Pleas note that, rooting process went well in Kitkat (CM 11S) but not in Lollipop (CM 12S).
You will find lots of posts claiming can't replace custom recovery after bootloader unlock. But we didn't find a single or multiple way to fix this. So, What to do now? There is always a way to make this right. Please help.
Click to expand...
Click to collapse
**********************************************************************************************************************
now go to this thread download software from this thread only. there are two thread for this tool but i prefer you to go to this one.
GUIDE
using above tool unlock bootloader.
and go for step 4(which flash twrp recovery)(this will create folder in your mobile)
now
download and copy this recovery file in your adb folder LINK
now go to adb folder
now press and hold shift button and right click on empty space there you will see open cmd , click on it cmd will open
now copy below code (this is for CM12 only)
Code:
fastboot -i 0x1ebf flash recovery recovery_twrp.img
anow right click in cmd and click on paste.
hit enter and after a while you will se 'Okay ' message at the end.
bingo you have flasher recovery :highfive: :good:
Ok guys, I pretty much hit a wall here so any help would be appreciated. I got manta with Dirty Unicorns 9.5 rom up and running great. Rom slows down, see a new version, all apps are auto backup'd with Titanium, rebooted to TWRP2871, wiped all but media, tried to install rom.... 1st error ...unable to mount system --tries install indefinetly... no rom
2nd error.... tried SkipSoft ToolKit to install stock rom and start from scratch... fail, cause i cant install drivers, cant turn on USB debugging, and/or device isnt detected in recovery and download mode.
3rd error.... in still working recovery i found philz recovery and install it... says it formatted system partition but also cannot install rom.
4th error.... can't connect with adb and fastboot, cant install drivers etc.
I refuse to dump unlocked device with working download menu and recovery.
Pretty much the same as people in this thread: https://code.google.com/p/android-developer-preview/issues/detail?id=1105
Any thoughts?
Hello domagoj_zg,
please try this Drivers:
koush/UniversalAdbDriver ยท GitHub
If your Tablet will be detected, write this command:
Code:
fastboot erase system
Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me
Format data?
What your twrp version ? your twrp version must be version support 11.
You cant flash Magisk via TWRP. It doesn't work, Install the magisk App
Wrong place to ask this stuff