Database Users

[Q] CWM Won't work properly

Hey everyone,
I am using the DROID RAZR M Utility 1.20, as posted here:
http://forum.xda-developers.com/showthread.php?t=2249773
I also followed the youtube video of it, as posted here:
http://youtu.be/ej7HBxvNPv0 (The video is actually for the Razr HD but the process is basically the same.)
Here is what I did.
Powered up phone in AP Fast Boot, and did step 1.) Flash 4.1.2 Stock System.
Then rebooted phone into Normal Mode (USB Debugger is on) and ran option 5.) Motochopper Root Exploit.
It rooted successfully.
Ten i ran Step 6.) Unlock Bootloader (Motopocalypse), ran the App, and it says it was successful.
Then I Ran step 4. ) Flash CWM Custom Recovery.
after this i rebooted the phone and went into the Recovery mode, but the only thing im getting is the little android on his back with the alert sign:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not sure what to do next? I am trying to load the Cyanogenmod onto this Droid Razr M, but safestrap evidently is not going to do it for me.
Any help is appreciated.
Thanks!

quick update..
Appears that Step6 is not working.
After rebooting into AP Fastboot, it says the Device is Locked.
Anyother tools out there to unlock the bootloader?

RomeoNate said:
Appears that Step6 is not working.
After rebooting into AP Fastboot, it says the Device is Locked.
Anyother tools out there to unlock the bootloader?
Click to expand...
Click to collapse
Motopocalypse is the only tool to unlock the BL. You can find it stand-alone if you do a quick Google search. However, if you were on the latest update, you won't be able to unlock your BL, even if you revert back to the older version. You can root with Motochopper 1.3, though.
Also, that screen is the stock recovery screen. When you're in that screen, hold vol down and tap vol up to get into recovery. If in fact you can unlock your bootloader and you succeed and you flash CWM recovery, you'll need to reboot immediately into recovery so the CWM updater script can finish its install. Otherwise, the stock recovery will override.

So if the phone has ever been updated OTA to the latest version, unlocking the bootloader is a lost cause?
That really sticks because i think this phone was updated.
I have verified the phone is rooted - otherwise safestrap wouldn't work.
So phone is rooted - what your saying is, using that tool - run the CWM Script, then reboot the phone and go directly to the recovery screen, then hold the Volume Down button, then press the Volume Up button..?
I will give this a try.
Thanks!

RomeoNate said:
So if the phone has ever been updated OTA to the latest version, unlocking the bootloader is a lost cause?
That really sticks because i think this phone was updated.
I have verified the phone is rooted - otherwise safestrap wouldn't work.
So phone is rooted - what your saying is, using that tool - run the CWM Script, then reboot the phone and go directly to the recovery screen, then hold the Volume Down button, then press the Volume Up button..?
I will give this a try.
Thanks!
Click to expand...
Click to collapse
Yeah, unfortunately, if it was ever updated, you can't unlock the BL. Even reverting back still won't open the "trusted zone." You can verify if Motopocalypse worked by booting back into the Fastboot screen. It should say the phone's unlocked. If you can get it unlocked, then yeah, immediately power off phone after flashing recovery and then reboot straight into recovery. If script ran as it should, you should boot straight into CWM.

RikRong said:
Yeah, unfortunately, if it was ever updated, you can't unlock the BL. Even reverting back still won't open the "trusted zone." You can verify if Motopocalypse worked by booting back into the Fastboot screen. It should say the phone's unlocked. If you can get it unlocked, then yeah, immediately power off phone after flashing recovery and then reboot straight into recovery. If script ran as it should, you should boot straight into CWM.
Click to expand...
Click to collapse
Well i think im at a dead-end. :-/
Fastboot keeps saying Device is LOCKED. I cannot get it to unlock... Argh!
Any other way ? Is it possible to revert or modify the "trusted zone"?

RomeoNate said:
Well i think im at a dead-end. :-/
Fastboot keeps saying Device is LOCKED. I cannot get it to unlock... Argh!
Any other way ? Is it possible to revert or modify the "trusted zone"?
Click to expand...
Click to collapse
Nope, no way to unlock and the man Dan said there's probably no chance to unlock.

Working root for ze601KL with WW-21.40.1220.1698??????

Anybody knows how to root ASUS Zenfone ZE601Kl with marshmallow???

Same question, I tried to flash TWRP, I see TWRP after flashing, but after restart, I have stock rekavery. Asus Unlock app install? but don't unlock, close with erorr.

after flash stock MM rom then you need to normal boot first then flash TWRP recovery again. because initial boot will be replacing to stock recovery even if you have flash TWRP before initial boot .
after flash TWRP then you can flash supersu zip by TWRP.

I get root, when I flash TWRP I flash PRO-SuperSU-v2.67.zip, before TWRP disappear, so I have stock recovery and root .

sampei said:
after flash stock MM rom then you need to normal boot first then flash TWRP recovery again. because initial boot will be replacing to stock recovery even if you have flash TWRP before initial boot .
after flash TWRP then you can flash supersu zip by TWRP.
Click to expand...
Click to collapse
how can I flash TWRP???

Joxefo said:
how can I flash TWRP???
Click to expand...
Click to collapse
Flash by bootloader or if you already get root then twrp manager or Rashr both available at play store

sampei said:
Flash by bootloader or if you already get root then twrp manager or Rashr both available at play store
Click to expand...
Click to collapse
I haven´t get root, i want to get root.
How can I flash by bootloader???

Joxefo said:
I haven´t get root, i want to get root.
How can I flash by bootloader???
Click to expand...
Click to collapse
Hi Brother, From a Windows PC, in Fastboot mode, flash custom recovery TWRP by using Adb/Fastboot tools and then flash SuperSU zip from Twrp, Thnx, Jesus Bless You.

[email protected] said:
Hi Brother, From a Windows PC, in Fastboot mode, flash custom recovery TWRP by using Adb/Fastboot tools and then flash SuperSU zip from Twrp, Thnx, Jesus Bless You.
Click to expand...
Click to collapse
Thank you [email protected]

I did the flash TWRP , but when I restart it back to stock recovery

LuisRuthes said:
I did the flash TWRP , but when I restart it back to stock recovery
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
not
fastboot boot twrp.img

andrehsu said:
fastboot flash recovery twrp.img
not
fastboot boot twrp.img
Click to expand...
Click to collapse
I did it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Flashing custom recovery doesn't work - I only see a Chinese menu option

After accidentally flashing the wrong MIUI ROM (Prime instead of 4G from Xiaomi's site), I've had problems trying to flash the correct ROM and a custom recovery ROM. The MIUI Updater and Mi Recovery methods just don't work, as all the zip files raise errors. I've now managed to root the device, but all my attempts to install a custom recovery ROM have failed. I've tried various methods, the most recent one being fastboot flashing the recovery.img file. The process acts like it's been successful, but when I try to boot into recovery mode by pressing vol+ and power, I see an interface that looks like a default/factory interface. I've seen it on previous attempts, so I know flashing TWRP has been unsuccessful. Does anybody know what it is and how I can replace it with TWRP?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jsp_1983 said:
After accidentally flashing the wrong MIUI ROM (Prime instead of 4G from Xiaomi's site), I've had problems trying to flash the correct ROM and a custom recovery ROM. The MIUI Updater and Mi Recovery methods just don't work, as all the zip files raise errors. I've now managed to root the device, but all my attempts to install a custom recovery ROM have failed. I've tried various methods, the most recent one being fastboot flashing the recovery.img file. The process acts like it's been successful, but when I try to boot into recovery mode by pressing vol+ and power, I see an interface that looks like a default/factory interface. I've seen it on previous attempts, so I know flashing TWRP has been unsuccessful. Does anybody know what it is and how I can replace it with TWRP?
Click to expand...
Click to collapse
So you can boot into MIUI?
If you can, are you then trying to install a custom recovery and flash another rom?
Which recovery do you go into now?

siddjazz said:
So you can boot into MIUI?
If you can, are you then trying to install a custom recovery and flash another rom?
Which recovery do you go into now?
Click to expand...
Click to collapse
After spending all of yesterday on the issue, I finally managed to fix it late last night. Counter-intuitively, my device required a Chinese ROM rather than a Global ROM. In the end I was able to root the device, eventually flash the correct version of TWRP (there's conflicting advice out there on using the 88047 and 86047 versions) and then eventually flashing a multi-language version of MIUI from Xiaomi.eu. It was a very, very painful experience, though.
Still, if I try to boot into recovery using vol+ and power, like so many guides advise, I'm presented with that unusual menu. I don't know what it is. The only way I can boot into recovery is via MIUI's Updater option. Ideally, I'd like to have the phone do what it's supposed to do when booting to recovery, but I'm just thankful that it's working again. This all came about because Gearbest sold it with their own adware-riddled version of MIUI.

Try VOL UP + VOL DOWN and then the power button.

Cannot restore system, stuck on bootloop

Hey guys,
i recently bought a OP2 from Ebay which is bricked (Stuck on bootloop). The phone wasn't able to boot into Recovery. Only thing worked was Fastboot. I managed to get stock recovery to work using this Guide (Method 3):
https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
Unfortunately it still stucks in a bootloop. I tryed flashing serveral Stock-ROM's. Does anyone know a solution to fix this?
ADB Sideload give me this output (everytime at around 94%)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm kind of new to this.
Greedings
Kynie

Make sure to update the fastboot/bootloader to the newer 3.0/hydrogenos version as all newer ROMs require this to boot.

How can i do this? I have stock bootloader v. 1.0 installed and not able to flash via fastboot cause the phone is locked. Cannot unlock because i'm not able to turn the phone on.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Click to expand...
Click to collapse
Thanks for the information. The OTA zip file do I have already. Sadly I can't find such an utility you are talking about. The only thing I found was a chineese (or I think it's chineese) tool which I already tryed but not worked. This tool just brings the stock recovery v 1.0 to life.
Or do you mean a diffrent tool?

In a similar position to you. Phone was working fine (only received it today and tried to get CM13 on it)
My bootloader is unlocked, but phone will no longer boot up, or go into recovery.
I can get it into FastBoot, but it doesn't show up anymore in ADB devices. When in fastboot, the device shows as "Android Device, Marshall London Bootloader interface"
If I switch the phone off and check Device manager it just shows as unknown device and then windows gives me an error message that its not functioning properly.
I have tried to follow this guide https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
but it won't allow me to update the device driver, even if I turn off signature for drivers.
The only thing I can get to load is Fastboot. I did at one point have a little penguin on the screen, but haven't replicated that again.
Can anyone help? I'm pulling out my hair

Are you sure you didn't just boot it up into fastboot-ish mode? To be able to flash using that tool you mustn't boot up the phone, make sure it's of and hold volume up when connecting the USB cable, this way the phone will enter chinese factory flash mode at which you can flash using the chinese tool. Also the drivers require you to disable driver signature in windows to install since it's not signed.

Got it working in the end. I just ran the application without bothering with the USB driver stuff and it detected the phone. Then flashed the stock rom and it's now booted.
Still can't get CM13 installed, as I get the error 7 in recovery and that's what got me in the mess!
Sent from my ONE A2003 using Tapatalk

I turned driver signature of and installed drivers succesfully. I run the chineese tool and it finishes succesfully but the phone is still in bootloop. This is frustrating...

Hello do you have find à solution ??

[FIX] Asus Zenfone 2 Laser ZE550KL Marshmallow update problem, failed to mount /asdf

I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.

Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.

Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?

hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:

I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?

How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.

Thank you
Thank you sir, this helped me a lot.

recovery link is asking need access plzz help

My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??