Related
Hi together,
I've got a Motorola Photon Q 4g LTE mobile phone and this afternoon I wanted to install CyanogemMod, but whatever I do, I stuck with the following problem:
I can't install any other Custom Recovery. I tried ClockworkMod and OpenRecovery, but I always get the s**t Motorola Bootloader, when I start in Recovery Mode. The Bootloader of my Phone is unlocked via Motorola Website, as told in many other threads.
I know that the users arrrghhh, shabbypenguin and Skrilax_CZ are great experts with firmware and such things, but I'm not allowed to write in developer's forums because I'm new here.
Has anybody got an idea for me, how to geht the Custom Recovery to work?
Btw: I tried to root the phone as well, but that wasn't posible. May be things come together or depend on each other.
Thanks for your help!
When you flash recovery (IE run the fastboot command) is it successful?
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Also, try this.
arrrghhh said:
When you flash recovery (IE run the fastboot command) is it successful?
Click to expand...
Click to collapse
When I flash recovery, I just flash the Motorola given Recovery by Motoroloa Bootloader. The Phone restarts, a logo with the Android Man is shown (stomach opend with some engeniering tools in it) and after about 5-7 Minuten, the system starts normally.
I also managed it to change the "Unlocked Message" into a Motorola Logo by using fastboot flash logo xxxx.bin and I nearly destroyed the flash by flashing an unlikely file. So the phone was shortly out of order because oder "flash failure" (fastboot mode). After that, I managed to flash the "boot.img" file of an CyanogenMod, so the flash was rebuilt and I could use the phone normally.
arrrghhh said:
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Click to expand...
Click to collapse
It shows the connected devices by showing a 8 or 9 ditigt number. It's almost the same view like I connected the phone without fastboot and use "adb devices".
arrrghhh said:
Also, try this.
Click to expand...
Click to collapse
This one I didn't tried yet, because I was so dissappointed of the mismatch with ClockworkMod & Open Recovery. Do you think, that trying this one will help, after two others failed?!
Thanks for you notice and your time. That's very helpful!
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
arrrghhh said:
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
Click to expand...
Click to collapse
Ah ja, now I'm one step closer. I did not know, that the dead Android dude is the sign for stock recovery.
I'll give it this afternoon another try and will report. A bunch of thanks to you at this time!
Hi, it's me again. I managed now the reboot to recovery, by holding the volume up button while doing the "fastboot reboot"-command with the command box. That worked and I could start Photon Q Open Recovery 2.06.
Unfortunately, I did something wrong or so and now the script re-flashed stock recovery again. Nevertheless, I now know how to operate and will do the rest by my own (hopefully).
@arrrghhh: Thank you very much for your help!
So, I finally did everyhting the right way (now with ClockworkMod Recovery), because I now have CyanogenMod running on my Motorola Photon Q
:victory:
@arrrghhh: Thank you very very much!
1) If i want to flash a stock rom what should I use adb sideload or fastboot. I have seen on youtube people using both of these. Are both of these similar or different. Sorry if this sounds stupid but I'm a noob and I'm very confused.
2) Do i have to unlock bootloader for flashing stock rom.
3) Does fastboot oem lock/unlock command works on every android device.
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
arunhebbare said:
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
Click to expand...
Click to collapse
Just for the heck of it, have you tried just booting into TWRP instead of permanently installing, to see if TWRP will even load ok?
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
arunhebbare said:
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
Click to expand...
Click to collapse
I had no problems flashing TWRP with "flash" command afterwards. My notes... http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049
Boot command worked
As an update I tried the fastboot boot recovery.img command and I could reboot and adb reboot onto twrp recovery mode. But when resorting to the volume button mode to recovery I again was presented with stock recovery.
I tried using the fastboot flash recovery command and it seems to have done the job. Now I am able to reboot to twrp recovery using both software and hardware ways.
What still bugs me is that why did not the flash commands work?
Any insight into this will help me understand the nuances of differences between booton and flashing o I have misunderstood them.
fastboot boot recovery.img=boot into recovery once
fastboot flash recovery=flash it permanently
Sent from my Nexus 6 using Tapatalk
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
I don't know if it's same in Moto devices too or not but in Samsung there's a file named installrecovery.sh which replaces custom recoveries with stock on boot.
But once the device has been rooted it can be stopped from doing so.
Maybe this same thing happend with you.
Again this is just mere assumption keeping a samsung device in mind and may be completely wrong logic.
Sent from my SM-A800F using XDA Free mobile app
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
Try using a new usb cable. I have no idea WTF motorola was thinking, including that god-awful charger without a detachable usb. I've seen this problem happen several times, though. When the cable goes bad but still has the actual connection it may not transfer data properly...but since it's connected fastboot doesn't know the file never actually transferred so it reports that it's done.
I bought a 6-pack of Tronsmart USB cables from amazon for $10, and they're absolutely amazing!!! They're made with 20-gauge wires, which are far thicker than those that will come with the phone, no matter what OEM it's from. Fat cable means fast transfer speeds and a longer life, since it will take longer to fray due to its heft.
*** the deal I got is actually back. Last time it only lasted a day, so if you want it, I'd recommend hurrying!!
http://www.amazon.com/Tronsmart-Cha...YYK0/ref=sr_1_7?ie=UTF8&qid=1442849948&sr=8-7
I plan on developing a TWRP recovery for my phone (which doesn't have one ATM) In order to do this, I need to run tests on my device to see if it will work or not. I know flashing a custom recovery that isnt compatible/is corrupted, etc can brick your phone but would simply booting a custom recovery cause any issues? So I would just run fastboot boot twrp.img, Would that brick my phone if it doesn't work or would it just go back into fastboot mode/reboot itself? I'm pretty sure it wouldn't cause a brick but I'm a bit of a newbie so I need some confirmation.
Drysauce said:
I plan on developing a TWRP recovery for my phone (which doesn't have one ATM) In order to do this, I need to run tests on my device to see if it will work or not. I know flashing a custom recovery that isnt compatible/is corrupted, etc can brick your phone but would simply booting a custom recovery cause any issues? So I would just run fastboot boot twrp.img, Would that brick my phone if it doesn't work or would it just go back into fastboot mode/reboot itself? I'm pretty sure it wouldn't cause a brick but I'm a bit of a newbie so I need some confirmation.
Click to expand...
Click to collapse
Most likely not UNLESS u modify your system using the recovery
areallydumbperson said:
Most likely not UNLESS u modify your system using the recovery
Click to expand...
Click to collapse
Well I dont plan on modifying my system immediately after I get a good boot. But I plan on seeing what works and what doesn't and going from there. Though "most likely not" isn't enough for me. I may just run some tests on my old xiaomi phone and try to boot a samsung exynos TWRP recovery on it and other things, guaranteed failure, but will see if I can manage to brick it, just by booting.
Each recovery, so also a custom recovery like TWRP, simply is menu you can select some actions that operate on Android OS. All these actions internally are based on ADB and / or Fastboot commands. Means you can achieve same results when directly running ADB and / or Fastboot commands.
jwoegerbauer said:
Each recovery, so also a custom recovery like TWRP, simply is menu you can select some actions that operate on Android OS. All these actions internally are based on ADB and / or Fastboot commands. Means you can achieve same results when directly running ADB and / or Fastboot commands.
Click to expand...
Click to collapse
Is that so, I never knew that. But what about flashing zip files? like for example if I were to flash a custom recovery, or Gapps, etc. how would one go about doing this through fastboot, where you cannot flash zips.
A lot if not all stock recoveries need a signed zip package if you want to flash
Drysauce said:
Is that so, I never knew that. But what about flashing zip files? like for example if I were to flash a custom recovery, or Gapps, etc. how would one go about doing this through fastboot, where you cannot flash zips.
Click to expand...
Click to collapse
Flashing ZIPs is done via ADB, not via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload LINEAGEOS.ZIP
adb reboot
jwoegerbauer said:
Flashing ZIPs is done via ADB, not via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload LINEAGEOS.ZIP
adb reboot
Click to expand...
Click to collapse
Thank you!
jwoegerbauer said:
Flashing ZIPs is done via ADB, not via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload LINEAGEOS.ZIP
adb reboot
Click to expand...
Click to collapse
But don't stock recoveries only allow zips made officially by the manufacturer to be flashed??
AFAIK Android's Stock Recovery only allows to flash Update-ZIPs, not any ZIPs. Update-ZIPs by nature are provided by OEM / carrier. But I may err, as always ...
areallydumbperson said:
Most likely not UNLESS u modify your system using the recovery
Click to expand...
Click to collapse
If I do boot into the custom recovery, is there still a chance that my os will be corrupted / phone will be (soft)bricked?
Having problems booting into TWRP recovery by using power/volume keys on phone.
I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "adb reboot recovery" I get TWRP recovery.
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine. So, I have a way to boot into TWRP, but it requires me to have a computer and usb cable available. I'd like to boot into TWRP using the phone keys.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.
BigZ1 said:
Having problems booting into TWRP recovery by using power/volume keys on phone.
I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "adb reboot recovery" I get TWRP recovery.
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine. So, I have a way to boot into TWRP, but it requires me to have a computer and usb cable available. I'd like to boot into TWRP using the phone keys.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.
Click to expand...
Click to collapse
Your device might be an A/B partition device, your OS that you're using and stock recovery may be installed in one of those partitions and TWRP may be installed in the other. This may be causing the stock recovery to boot with the buttons and TWRP may be booting because it is responding to adb in a way that stock recovery does not.
How to fix? Not sure, but, if your device is rooted, you can install a Terminal Emulator app then open the app when you want to boot into recovery and type the following commands:
su (press enter, grant superuser if prompted)
Then type:
reboot recovery (press enter)
Terminal emulator works almost exactly like ADBshell and can run the same commands as ADB shell, you just have to remove the "adb" and "adbshell" part of the commands. In the example above, the comnand in adb would be "adb reboot recovery" but in Terminal Emulator, it is just "reboot recovery". The same would be true for any command that begins with "adb" or "adbshell". You can also try running any other adb or adbshell commands that you might need in the same way in Terminal emulator directly from within the device instead of having to use a PC to run them. You can also flash TWRP(or any other partition/.img) using Terminal emulator by using dd commands to put whatever .img you need/want into any partition that you want. But, you must specifically identify exactly which partition the .img is supposed to be in, if you flash the wrong .img to the wrong partition, it will brick the device. You absolutely MUST use the correct .img and you absolutely MUST flash it to the correct partition.
Or, if your device actually is an A/B device, try seeing if you can identify which partition is which and which one your currently installed operating system is installed in and which partition the stock recovery is installed in then see if you can flash TWRP onto the partition where your stock recovery is installed then try booting into it using the buttons, do not boot into system before booting into TWRP, using the buttons, after flashing TWRP, immediately power the device off then try using the button combo to boot into TWRP.
Thank You Droidriven. You have provided enough info for a reasonable work around.
BTW, I didn't understand what you meant by "I DO NOT PROVIDE HELP IN PM" Would you please explain that? What is PM? If I am doing something wrong in my post, let me know, as that is not my intent.
Using a terminal emulator and using superuser commands does indeed work, to boot directly into TWRP. So, after trying the terminal emulator, I installed an app from Google Play Store called Simply Reboot. It will boot directly into TWRP, no problem!
I don't think I have an A/B partition device. The LG K7 was introduced in 2016, so it's pretty old. I've tried searching the internet, but I can't find any reference to A/B partitions on it. If you have any ideas how I could find out for sure, please let me know.
I have another theory, and would appreciate feedback from you, or others reading this post. I remember watching some youtube video on custom recovery, where they talked about two different ways to control what happens when you use the phone keys to boot into recovery. One is to load an image into the recovery partition. The other is to modify the boot image so that the boot process points to another partition that has the stock recovery image. I might not have that 100% as I am no expert on this stuff. Anyway, maybe somebody can comment on this.
One last thing. Now that I have a terminal emulator, and am only marginally proficient in Linux commands, can anybody suggest what commands I would use to try and figure out where the TWRP image got loaded, vs. where the stock recovery image is located?
Once again, Thanks for all the help!!!!!!