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.
Related
I seemed to have lost my recovery but my phone is otherwise working.
I went from CM13 with TWRP, downloaded OS3 from the official oneplus web download as well as the "optional recovery" on the same page.
I wiped data/system/dalvik/cache and flashed the OS 3 zip.
I then flashed the stock recovery img.
Wiped again.
Rebooted to recovery from TWRP and got stuck with the oneplus logo. Completely non-responsive.
Fearing I had softbricked the phone, I started with ADB, got the Qualcom HUB listing under Device Manager and was about to start the process of updating Qualcom Drivers and running the recovery tool (having not been able to get fastboot to see the device) when a miracle happened and the phone started booting up on its own. After running setup, I rebooted, no problem.
I have since been able to use fastboot oem lock and confirmed the phone is locked (I wanted to get back to stock).
Everything is working fine EXCEPT I don't seem to have any Recovery at all. If I use the Developer Option for Advanced Recovery and boot into recovery, I get the oneplus logo. If I use Vol Down and Power I get the oneplus logo.
I think I have lost my recovery but recognise that I am out of my depth and don't want to stuff up the second chance I was given by trying to flash a recovery (I want stock receovery so I can get OTAs in the future). BTW, I read extensively before I tried this, looking at a number of different sites and followed instructions to the letter (or at least I thought so!).
Could someone who knows what to do please help to get my recovery back? It would be very much appreciated.
Edit: I managed to fix it. You have to use the Qualcomm tool and go back to OS2.2 and then update to OS3. See the link below and follow Method 1, doing everything exactly as set out.
{
"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"
}
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
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 ??
I was wondering if there was a way to unlock the bootloader on the v410 running 4.4.2. I have tried FreeGee and my device freezes and then restarts. I am rooted (TowelRoot) and have SuperSU and Busybox installed. I would like to be able to install TWRP recovery.
newbreedsoftware said:
I was wondering if there was a way to unlock the bootloader on the v410 running 4.4.2. I have tried FreeGee and my device freezes and then restarts. I am rooted (TowelRoot) and have SuperSU and Busybox installed. I would like to be able to install TWRP recovery.
Click to expand...
Click to collapse
I installed TWRP using flashify with no issues.. You might want to try that.
shilofax said:
I installed TWRP using flashify with no issues.. You might want to try that.
Click to expand...
Click to collapse
Which version TWRP are you using? Are you on kitkat? Trying to root and install TWRP
I am a newbie here. But I unlocked my device thru the carrier. What have you been able to use to unlocked boot loader? I have Lollipop 5.02 running on my device.
unlocking v410 bootloader
Repins55 said:
I am a newbie here. But I unlocked my device thru the carrier. What have you been able to use to unlocked boot loader? I have Lollipop 5.02 running on my device.
Click to expand...
Click to collapse
I have been fighting this for a couple of days. It seems that users are downgrading to a previous version 4 of Android in order to unlock the bootloader. I have been unable to make this work personally. Kingroot rooted 5.0.2, but the TWRP recovery ROM will not load. I think it's because the bootloader is still locked.
Yeah I'm having the same issue. If I flash the e9wifi .IMG recovery then boot recovery I get this fastboot screen which I've never seen on this vk410. I can't really use fast boot commands it seems not to respond well I know something is off I'm curious if its my headspace and timing or the tablets.
{
"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"
}
Click to expand...
Click to collapse
lg gpad v410 boatloader
i was able to root with 360
mine has boatloader removed
att has download mode where you might wipe
recovery with linux tools
and use fastboot, on my other phone commands wouldnt work, and it was non-writable
recently while trying to flash the kernel with anykernel2 it opted to fastboot mode, i havent tried any commands my pc is down
i extracted the boot.img after root
put the zlmage in a zip to flash the kernel i borrowed and it booted to fastboot mode
the zip file name is in the other post
id like to know if it works
thanks
No Command @ bootloader
Ive got the LG Uk 410 i flashed the firmware years ago. Im trying to get into the bootloader to cleanwipe so i can upgrade to a more recent CM but bootloader says no command. Ive tried power button, pwr vol up, pwr vol dwn, vol dn & up but i cant get past it can anyone please help? Need to get to clean wipe
one I had boatloader non-functional
but had twrp and rooting/no kernel flashing
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??
i made a mess, i can't install anything, i tried here to do repair installation for sansung a20s software, but it immediately failed, also it doesn't let me exit this screen anymore
{
"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"
}
thanks i solved by flashing the original stock firmware again
To root your device, start by flashing TWRP, which you can find here. The TWRP .tar file goes in the AP slot of Odin.
Once you have TWRP installed, you should be able to flash Magisk, which you can find here.
how installa TWRP, i have error
this trying to put... twrp-3.7.0_9-0-a20.img
I didn't notice that OEM LOCK is ON.
You must unlock your bootloader to flash custom images.
ok i haveTWPR done
but after reload sisytem ...
this is very strange, for an old phone, I don't understand, I've never had all these problems ...
i m crazy
Did you flash vbmeta as well as TWRP? This might be the right file
I have to try again ,,,, but I still haven't figured out if anyone has been successful in rooting this device ,, I sansumg told everyone to do it
then, then yesterday I reflexed the original stok, now so I first do a TWPR and THEN this file that you are providing me?
yesss done good
now I need more help, I put TPWR then The file repairs vbmeta ,, ...., but it tells me that I don't have root permissions yet
do i have to give up?
Did you get a working twrp? Try booting into recovery (twrp) and then flash Magisk-v25.2.apk. If that works, reboot into system and install Magisk-v25.2.apk as an app. Then start the app and it will tell you whether you have root. If it doesn’t work, I don’t know what to do next. You may need to have the Magisk apk on a usb drive or microSD card for it to be visible in twrp.
the problem is that I put the TWPR gives me an error
vbmeta ,, then I put your tar file (
vbmeta_disabled.tar
2 KB · Views: 1) the phone starts, but in recovery I don't see TWPR the android menu looks normal
from this menu I tried to install the magic, but the installation fails
When you install twrp from Odin, disable automatic reboot from Odin options. Once you see that the flashing is completed, reboot the phone by holding vol- and power for 7 seconds, then immediately hold vol+ and power to boot into recovery. Otherwise twrp will get overwritten with stock recovery and you have to try again.
I am thinking that by reviewing the file (vbmeta_disabled) it overwrites the TWPR that I first put ,, in the revvr mod it always starts me with the classic menu
[email protected]
but every time I install a TWPR I have to insert after the file (vbmeta_disabled) because otherwise the phone always restarts with vbmeta error in download mod
Use 7-zip and add vbmeta.img from the tar above to the twrp tar and flash that
no work,,stay that way