Related
Not sure if this belongs over here in Q/A as a new thread, or if I should append this to shabbypenguin's root thread. I am attempting to root my Photon Q following shabbypenguin's method. I downloaded the latest SDK bundle, installed latest Motorola drivers, successfully unlocked the bootloader.
I can't seem to get any recovery images to flash correctly at this point, though. When I run "fastboot flash recovery cwmrecovery.img" I get the following output:
Code:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 2.363s]
finished. total time: 2.885s
Not sure if "Variable not supported" is a normal message or not, but otherwise it appears to have completed successfully? But when I reboot into recovery mode, I always get the android with a red triangle screen, like this. I have tried flashing shabbypenguin's CWM recovery image, the latest TWRP recovery image, and the stock recovery image linked to in this thread. Same result every time; red triangle screen.
My phone is running the updated OTA build (77.8.10). Is that what is hindering my ability to flash and root successfully? Not sure where else I could have gone wrong. The only other thing I can think of is that before starting with all this, I did have encryption enabled on the phone. But before unlocking the bootloader and attempting to flash CWM recovery, I performed a factory reset to remove the encryption.
UPDATE: it doesn't actually seem like the recovery images are getting flashed at all. At first I thought something was being corrupted (given the red triangle).
But if I press the Up/Down Vol buttons on that screen, I get the Android system recovery utility menu. So if a recovery flash had occurred, this would have been overwritten, right?
I'd be grateful for any suggestions of what to try at this point.
i've never seen that bootloader message before, but it seems like your recovery might be getting flashed back to stock when you reboot. another guy had this issue, you might hopefully be able to solve it by reading this short thread here:
http://forum.xda-developers.com/showthread.php?t=2017748
edit; in short, you could try rooting with Motofail2go: http://forum.xda-developers.com/showthread.php?t=1940594, then use your SU priviledge to rename recovery-from-boot.p to recovery-from-boot.bak,(in /system), then reflash recovery of choice and it should stick.
Thanks yogi! That was indeed my problem as well. I hadn't come across that thread in my initial searching, so I really appreciate your ultra fast response and the sage solution you figured out in the earlier thread. You rock!
Ah, glad that worked for you also! I'm not sure why some people have had to do that, while I don't think I ever did(I have a file named recovery-from-boot.bak, but I don't think I actively renamed it). I am also not sure why we have have an unlockable bootloader, yet without a 3rd-party exploit, some people are getting stuck
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Rangerbry said:
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ah ok, i figured something was renaming that file. The thing is, is there a way to boot straight into recovery from the bootloader? I've always had to boot into the system and then adb reboot recovery.
just hold up like normal after
fastboot reboot
ah yes ok, i guess people should do that after flashing recovery so they can get SU flashed before losing their recovery. and we'll see if Shabby's SU zip still disables that recovery file. i guess that's sort of standard procedure on phones in general, but i don't think i ever did that on this device.
Nice, thanks! Yeah, I was booting back in to system and doing adb reboot recovery as well. The couple blog write-ups I was following weren't clear on that aspect, but then, using the hardware buttons to force it directly to recovery makes perfect since; wondering why I didn't think about that at the time.
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Alex42rus said:
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Click to expand...
Click to collapse
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Hinyo said:
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Click to expand...
Click to collapse
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Alex42rus said:
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Click to expand...
Click to collapse
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
If you are having issues with recovery not sticking, there is a thread right below yours which addresses this.
Especially see this post from kabaldan.
arrrghhh said:
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
Click to expand...
Click to collapse
Yes, I am tring, but when I do it, I have "variable not supported" message.
Console:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery twrp-hdr
ecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6678 KB)...
OKAY [ 0.502s]
writing 'recovery'...
OKAY [ 1.960s]
finished. total time: 2.465s
C:\adt-bundle-windows-x86_64\sdk\platform-tools>
Alex42rus said:
Yes, I am tring, but when I do it, I have "variable not supported" message.
Click to expand...
Click to collapse
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
arrrghhh said:
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
Click to expand...
Click to collapse
>Stock OTA update contains /system/etc/install-recovery.sh that will re-flash the recovery to stock any time you boot the android system.
>Boot to custom recovery first before starting the android system after the update
This path realy help me! I go to recovery by presing power + up after recovery.
> and remove this script by using the console or adb shell:
adb shell not connected, and I not find console in recovery, but before reboot recovery ask me to remove "re-install recovery"
great thanks !
Had the same problem trying to flash TWRP to my XT926. Flashing multiple versions of CWM or TWRP gave the same results. (bootloader) variable not supported, but flashing would still appear to proceed ok. However the recovery was always jacked somehow. The only thing that would flash correctly (even with the error) was the stock recovery.
I was using minimal adb & fastboot. Clued in off of a thread off of droid rzr forums (cannot post url due to my new user status) I FINALLY realized I needed to replace the included AOSP binaries with the motorola ones.
Upon replacing the binaries flashing proceeded without error & TWRP was installed & running correctly.
So as this thread came up most of the time when searching for solution to my error, I hope this reply helps.
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Sent from my XT926 using XDA Free mobile app
4ndr01dpilot said:
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Click to expand...
Click to collapse
Thanks for this tip. I used the fastboot version from Motopocalypse instead of my standard ADB installation version, and the variable message stopped appearing. :highfive:
I was puzzled for days being stuck in endless "Flashing recovery ..."
In the end I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.
Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?
n.N.n. said:
Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?
Click to expand...
Click to collapse
do you reboot into recovery when done or straight to OS
playya said:
do you reboot into recovery when done or straight to OS
Click to expand...
Click to collapse
The guide says to unlock bootloader, reboot to os, change settings, flash recovery, reboot, root.
But after your input, I did try it without the complete reboot and it worked. But shouldn`t a flashed recovery be persistant?
Edit: Did a second reboot, now there is the stock recovery again =/ But the root persisted.
[Q] Cannot enter recovery after flash of TWRP
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon
Have tried several recovery images
timmaaa said:
Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes, I have tried both TWRP 2.7.1.0 and 2.7.1.1 and Stock-recovery.img from 2008-12-31 - they all freeze in Android prompt when I try to boot in recovery mode. The only difference being, that only TWRP 2.8.0.1 causes the prompt to tyrn blue and then fade away.
The device just displays the Android [1+ said:
logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.
Trie advanced reboot to recove - no luck
habnzrot said:
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.
Click to expand...
Click to collapse
When I select reboot - recovery, I just get a brief message that 1+1 is rebooting and then it freezes in the Android prompt as before.
Re: can't flash a recovery that will work
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Success, finally
driftt said:
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.
Click to expand...
Click to collapse
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
Thanks milesman, but as you can see from the post above, the using the Philz image was successful. However, your suggestions may help other people, since the process really seems not to be robust.
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
TorkelJensen said:
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
I've had my OPO for a couple of weeks now and have had this problem all along. It took until today that i found this thread with someone having the exact same problem as me. After flashing a LOT of different recoveries (and different versions) I too noticed the only recovery I could successfully enter is Philz (although not all versions). I would prefer TWRP as recovery, but as long as I have one that is working that's good enough! It does however annoy me that almost nobody else has this problem. It makes me believe there is something wrong with the device. Flashing recovery in fastboot is always successful according to the logs. Erasing recovery in fastboot before flashing new one did not solve the problem either.
Before unlocking the bootloader, installing recovery and rooting, I updated the device from 33R to 38R. I now regret not doing that before updating...
I uploaded two videos showing the artifacts. The videos were recorded right after installing openrecovery-twrp-2.8.1.0-bacon.img from goo.im.
Since I haven't posted that much on XDA before I wasn't allowed to post links, please copy and paste.
youtu.be/jYJUfOOjaUE
youtu.be/GYcSjUKpOaE
Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
As written in the first post by n.N.n. this problem is not related to this option. The checkbox is unticked and recovery doesn't get replaced by CMs stock, it fails to boot.
Couldn't flash any recovery until I unchecked the "update CM recovery" option in the developper, thanks for the tip ! I didn't think this was also protecting the recovery !
I've had same exact probem when flashing twrp 2.8.x.x from fastboot or twrp. As a last resort I gave Flashify a go and to my surprise, it worked.
I had the same problem, but PhilZ's lastest (6.58.8 as of now) worked for me. I wonder why this is happening to some of us, but I'm glad I sorted it.
Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
Thanks, that solved the problem for me! I've flashed TWRP and CWM, but after rebooting into recovery mode there was always the CM stock recovery. After unchecking this in the dev settings it worked as it should.
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This worked for me thanks.
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This doesn't work for me.
erasing 'recovery'...
OKAY [ 0.026s]
finished. total time: 0.026s
Still stock recovery after flashing TWRP. Why is this so weird?
The Update thing in Developer is unchecked.
My other OPO was perfect
---------- Post added at 02:32 PM ---------- Previous post was at 02:19 PM ----------
TorkelJensen said:
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
This works for me.
Click to expand...
Click to collapse
After installing Custom Recovery (mine id TWRP), turn off the handphone. After that, do directly the boot to recovery (On/Off Button + Volume Down). DO NOT do the normal start, since the system will erase the custom recovery (and instal the "standard" recovery)
Hi Folks,
Disclosure: No responsibility taken or accepted in any form if the following process failed.
As forum rules prevented me from posting links try to understand how to find referred files.
1. Prepare a PC with Windows 7 installed and the automatic Windows driver update lookup function possibly disabled.
2. Download BETA-SuperSU-v2.49.zip (appr. 4 MB, from chainfire eu and copy it to the phone's SD card or to an external micro SD card.
3. Download the latest stock ROM and flash tool packed together (e.g. 'Be-Touch-2_150702_s7yler.zip') from needrom com . Search for ulefone-be-touch-2.
4. Download TWRP recovery image file from needrom com . Search for be-touch-2-twrp-2-8-7-0.
Extract the rar archive and rename recoverye.img to recovery.img
5. Extract 'Be-Touch-2_150702_s7yler.zip' and replace the recovery.img file in the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\software" folder with the one from the TWRP archive (see point 2).
6. Install the MTK chipset driver (it works on Win7 only at the present time):
- Navigate to the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\Driver Auto Installer" folder.
- Open a Command Window to see what happens on the command line.
- Run Install.bat with real Administrator priviledges (in most cases Run as Administrator may not be enough - refer to UAC).
- Wait until the driver installation is finished. You will see on the screen if the drivers were installed successfully (e.g. "Driver install done").
7. Flashing ROM
Notes:
- Flashing ROM will wipe all your data. If you have not done a backup before you will permanently lose your data!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
a/ Open the Be-Touch-2_150702_s7yler\One Key Flashing folder and run SP_Facility_DL_Tool.exe
b/ Turn off the phone, take out the battery, press the Scan button in the SP_DownLoad window then connect your phone to the PC via USB.
c/ After the text "N/A+COM(x)" appears on the left hand side of the window disconnect your phone, reinsert the battery, press the Start button and reconnect your phone via the USB cable.
d/ Wait until the flashing utility finishes updating the phone (e.g. the process bar shows 100 % on yellow background and "DL OK" can be read to the left of the process bar).
8. After flashing, enter the TWRP custom recovery: press vol up + power to boot for a few seconds then install BETA-SuperSU-v2.49.zip from your (external) SD card.
9. You are done with rooting.
Fastboot
litokraz said:
- Flashing ROM will wipe all your data if you have not done a backup before!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
Click to expand...
Click to collapse
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Yes you are right. The method I described above also updates to the latest(?) Ulefone ROM as of 02-07-2015.
Even you can flash a Carlive recovery (tried and works) based on the downloadable from the "Ulefone Be Touch 2, 5.5 Inch Full HD, Metal Frame, MT6752 64-bit, 3050mAh Battery" thread Post #76. Carlive (originated from CWM) lacks the annoying splash screen which is included in TWRP.
UPDATE: Never mind, I got it. WooHoo
Guys, how do I get to Fastboot mode on my BE Touch 2? I tried power + volume down, yet it takes me to chinese menu I do not understand.
Odesláno z mého Be Touch 2 pomocí Tapatalk
Thank you Litakraz .... Good job done ... works like charm ..well explained
marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
PS : /!\ AVOID TO UPDATE YOUR DEVICE OR YOU WILL BE BLOCKED ON THE ULEFONE LOGO !!! /!\
dkpiit said:
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
Click to expand...
Click to collapse
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???
Heshamvido said:
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???
Click to expand...
Click to collapse
Yes, just download and install adbdriver[DOT]com/downloads/
Thanks to the OP for the guide. I am now rooted & the phone is working perfectly.
Now just waiting for cyanogenmod to be released for it & I'll be a happy man.
Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update
Darkstar2r1 said:
Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update
Click to expand...
Click to collapse
I am curious on that too! Did you get it running?
I will try a different recovery.... hope that works.
hi guys..
anyone has NVRAM for this device..? it is black screen now but it is working..
Are there any tools around for rooting Spectrum on the R7Plusf?
W1F1 said:
How am I able to root project spectrum on the Oppo R7 Plus?
Thanks in advance!
Click to expand...
Click to collapse
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
EximusCode said:
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
Click to expand...
Click to collapse
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
W1F1 said:
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
Click to expand...
Click to collapse
Bingo my friend. If you want the links you need only ask. :good:
EximusCode said:
Bingo my friend. If you want the links you need only ask. :good:
Click to expand...
Click to collapse
The links would be fantastic, thanks so much!
W1F1 said:
The links would be fantastic, thanks so much!
Click to expand...
Click to collapse
Will post them ASAP
Thanks!
W1F1 said:
Thanks!
Click to expand...
Click to collapse
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
EximusCode said:
Will post them ASAP
Click to expand...
Click to collapse
I'm sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
EDIT: Whoops disregard that I managed to download it.
W1F1 said:
I'm so so sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
Sorry again.
EDIT: Sorry disregard that I managed to download it.
Click to expand...
Click to collapse
Hope it works for you like it did for me :good:
EximusCode said:
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
Click to expand...
Click to collapse
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
W1F1 said:
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
Click to expand...
Click to collapse
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
EximusCode said:
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
Click to expand...
Click to collapse
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
W1F1 said:
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
Click to expand...
Click to collapse
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
EximusCode said:
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
Click to expand...
Click to collapse
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
W1F1 said:
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
Click to expand...
Click to collapse
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
EximusCode said:
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
Click to expand...
Click to collapse
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
W1F1 said:
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
Click to expand...
Click to collapse
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
EximusCode said:
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
Click to expand...
Click to collapse
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
W1F1 said:
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
Click to expand...
Click to collapse
Okay, good luck
Disclaimer
Code:
/*
*
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
*
*/
GUIDE OF HOW TO INSTALL TWRP RECOVERY ON ZENFONE MAX (Z010D & Z010DD)1º Step:
- You need an Unlocked Bootloader:
- for SD410 (MSM8916/Z100D).
- for SD615 (MSM8939/Z10DD).
2º Step:
- You need minimal adb fastboot.
3º Step:
- You need to download TWRP Recovery:
- for SD410 (MSM8916/Z010D).
- for SD615 (MSM8939/Z100DD).
Put the recovery on the folder of minimal adb fastboot and rename it to recovery.
4º Step:
Run the Minimal Adb and Fastboot as adminstrator.
5º Step:
Go to Bootloader (CSC MODE) mode on your phone (Press and HOLD Volume Up Key+Power Key) enter the following commands:
Code:
[SIZE="2"]fastboot devices[/SIZE]
If you see a serial then you are you ready to flash the recovery to flash you need to do the follow command:
Code:
[SIZE="2"]fastboot flash recovery recovery.img[/SIZE]
6º Step:
After flashing the TWRP recovery, you should boot directly into recovery by holding Volume Down+Power Button do not allow device to boot into the stock rom at first boot, otherwise stock recovery will be restored!
Credits:
To the developers!
Reserved
shirofficial said:
After flashing the TWRP recovery, you should boot directly into recovery by holding Volume Down+Power Button do not allow device to boot into the stock rom at first boot, otherwise stock recovery will be restored!
Click to expand...
Click to collapse
So what to do after I booted into Recovery first. Can I go back to stock rom afterwards?
Sayan44 said:
So what to do after I booted into Recovery first. Can I go back to stock rom afterwards?
Click to expand...
Click to collapse
Yes you can. :good:
bro my device is asus zenfone max asus z010d snapdragon 410 version
https://androidfilehost.com/?fid=745849072291687209
is the above linked recovery correct for my device??
krishna8691 said:
bro my device is asus zenfone max asus z010d snapdragon 410 version
https://androidfilehost.com/?fid=745849072291687209
is the above linked recovery correct for my device??
Click to expand...
Click to collapse
Yes it is :good:
I have already rooted can i just flash the recovery through app
hi sir.. i just wanna adk the solution for the error 404? i can't install the twrp in my unit.. what i need to do? the adb can't detect my phone..
shirofficial said:
Yes it is :good:
Click to expand...
Click to collapse
Hi bro I am tharun twrp is not installing properly in my ASUS...what to do for that?
Hy Sir
After Twrp Flash
When I try to boot into Twrp ,phone freezes at Asus logo & next time when I try to boot into Twrp by restarting boots into stock recovery
Tried a lot of time ,did lot's of attempts
Please help me
Hello can anyone please help me,
I followed every thing but it's asking for password when I boot into recovery then press cancel and wipe the phone (factory reset). Via twrp as I saw in one website but next time when I reboot it's I "Qualcomm diagnostic mode 9006" please help me to come out of this it's my friend phone
Thank you
how do I boot into recovery from CSC mose ..power up + vol. down donot lead anywhere ..lomg pressing power buttton results in rebooot
I cant go to twrp after done flash img from adb
After done flash twrp img file through adb on asus z010d by pressing vol up and power key i cant go to twrp . My screen goes of the exact time twrp open. What should i do?
Anybody help me please
My watsapp number is
+917012088399
Is it necessary to root the device first before flashing twrp ?
Because as I flashed twrp image, and then booted firstly into it, and when I tried to reboot my device in stock ROM, it got stuck in Asus logo, I can't start my device anymore ... Please help devs
I have an error
adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (18036 KB)...
OKAY [ 0.570s]
writing 'recovery'...
FAILED (remote: can't flash unsigned image)
finished. total time: 0.731s
i don't know what to do, please..
tuananhtd09 said:
I have an error
adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (18036 KB)...
OKAY [ 0.570s]
writing 'recovery'...
FAILED (remote: can't flash unsigned image)
finished. total time: 0.731s
i don't know what to do, please..
Click to expand...
Click to collapse
This is probably because you didn't do step one first. Step one unlocks the bootloader so you shouldn't receive this error when you try to flash recovery. If you can't do step one because android is out of date then you need to update android first. If you can't update android then welcome to the club, you probably have a cn recovery and need to update to ww. This can be down following these instructions assuming you have a z010d/sd410/8916 https://ainotech.com/how-to-flash-firmware-asus-zenfone-max-zc550kl-root-custom-twrp-recovery/ Follow the instructions for AFT.
However now I'm stuck on the bit everyone else is stuck on. Once TWRP is flashed, how to boot directly to that instead of android first??
EDIT: I figured it out. It's because this build of twrp 3.2 and even 3.1 is broken for this device. Flashing twrp 3.0 works fine but of course that doesn't support many modern custom roms so it doesn't really help.
Sharft 6 said:
This is probably because you didn't do step one first. Step one unlocks the bootloader so you shouldn't receive this error when you try to flash recovery. If you can't do step one because android is out of date then you need to update android first. If you can't update android then welcome to the club, you probably have a cn recovery and need to update to ww. This can be down following these instructions assuming you have a z010d/sd410/8916 https://ainotech.com/how-to-flash-firmware-asus-zenfone-max-zc550kl-root-custom-twrp-recovery/ Follow the instructions for AFT.
However now I'm stuck on the bit everyone else is stuck on. Once TWRP is flashed, how to boot directly to that instead of android first??
EDIT: I figured it out. It's because this build of twrp 3.2 and even 3.1 is broken for this device. Flashing twrp 3.0 works fine but of course that doesn't support many modern custom roms so it doesn't really help.
Click to expand...
Click to collapse
oh, thanks. because i didn't do step one first
and now i had a problem bigger @@
https://forum.xda-developers.com/as...ow-to-fix-updating-partition-details-t3867714
you should install the downloaded app on the step number 1 in order to get along with the other steps.
:good: