I recently updated rm2pro with android 10 system update and I'm trying to flash recovery but it keeps leaving me on "waiting for device" in command window, however it does detect adb device. I don't know if it's missing drivers or what, I tried plenty. I want to switch to custom rom but can't flash recovery and can't find a guide anywhere, hope to see a solution soon.
Related
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.
Don't ask me how this came about but I currently do not have a recovery on my phone.
The phone was running a rooted version of android 4.4.4 (paranoid android I think I had) and when android 5.0 came out I decided to flash it to my phone manually, to do this I used the tools available in android root tool kit. I think I messed it up a bit however as I have no recovery image on the phone.
I am now bored of running stock and want to flash a cyanogenmod ROM onto the phone - hence why I now need a recovery.
I can get my pc to recognise that a fastboot device is connected, but when I try the fastboot flash recovery <recovery.img> command it returns "could not load file". Even though the file is there in the path specified - I'd downloaded CWM recovery.
So I am not sure what I should do, can anyone help me?
I do not have my OEM cable and cannot get the PC to recognise an ADB device is connected, so a solution that gets round this problem would be useful. I'd rather not have to spend money on a new USB cable just for this purpose.
Thanks.
fredcorp6 said:
Don't ask me how this came about but I currently do not have a recovery on my phone.
The phone was running a rooted version of android 4.4.4 (paranoid android I think I had) and when android 5.0 came out I decided to flash it to my phone manually, to do this I used the tools available in android root tool kit. I think I messed it up a bit however as I have no recovery image on the phone.
I am now bored of running stock and want to flash a cyanogenmod ROM onto the phone - hence why I now need a recovery.
I can get my pc to recognise that a fastboot device is connected, but when I try the fastboot flash recovery <recovery.img> command it returns "could not load file". Even though the file is there in the path specified - I'd downloaded CWM recovery.
So I am not sure what I should do, can anyone help me?
I do not have my OEM cable and cannot get the PC to recognise an ADB device is connected, so a solution that gets round this problem would be useful. I'd rather not have to spend money on a new USB cable just for this purpose.
Thanks.
Click to expand...
Click to collapse
I would highly recommend Wug's Nexus Root Toolkit. It can automate any process you need. From what it sounds like it your post, you need to re-install TWRP. With the Nexus Root Toolkit, you can find that option under the "Root" section. Just check the box "Custom Recovery" and press the big "Root" button. Everything is very easy with this program. One thing I would recommend is that you get a very good USB to Micro USB to do this with. That is always the first point of failure in my experience. Good luck!
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:
hi everybody, i hope, that someone can help me,
i thought i should root my Z1 and it was not a problem via windows (via LINUX i couldnt even find the device via "adb devices")
it was not a problem. first i installed twrp, but everytime when i restarted the recoverymenu, twrp went away and the default recovery menu started. so i installed CMR and it was not a problem. so far everything okay. but than i thought i should install the current nighlies of cynagonMOD and the problems started
when i try CMR to installed the current nightlies, i get the error
""this package is for device:Z1 ; this device is jfltexx" nomatter if its the nightly from 13.11.2015 or 14.11.2015
under windows, when i start adb devices, the device will be found
adb devices
List of devices attached
529e86fb device
and when i try to start into fastboot, it is possible. but when i'm in fastboot-modus
i can do anything. nothing happens. whatever i try, i get the feedback "waiting for devices"
any idea? can someone tell me, whats the problem is?
@update: when im in CMR, windows shows my ZUK z1 as GT-I9505 (i guess its samsung right?) how can i deinstall CMR and install TWRP (cause via fastboot its not possible)
Do you use fastboot with the -i switch followed by the device ID?
at the first time yes. but now its not possible. im now really frustrated, cause now im in the boot animation loop and can do nothing. even not able to upload any zip files to restore the zuk cyagon OS . any idea how i can install now the normal version of the phone again? i can only enter CMR
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?