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
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/
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.
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??
hello..SM-g935df suddenly battery low while updating firmware.now its hang with boot screen.FRP lock also on.I tried many firmware (7.0 and 6.0.1 etc)all firmware fail at flashing "recovery.img" in odin.in recovery mode i can see like below image.
{
"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 reset the device.now its show like this image.please help me
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
JeffDC said:
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
Click to expand...
Click to collapse
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here result firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1
geeth said:
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result View attachment 4345010
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here resultView attachment 4345011 firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1View attachment 4345042
Click to expand...
Click to collapse
Head over to the OP's post and ring him up. I think after the first flash, as I get it, you have to somehow run the .bat file in adb, It is the .bat file that deletes the Persistence file/partition, where, as he explains, the FRP (Google enctypted file) is held. Once that is out of the way, FRP should be gone, then flash back your stock BL, or leave it on the U (Universal) BL if you wish?
That's my understanding. I don't think the OP's been around his post for several months. We are hoping he returns to answer and clarify some questions.
Hi. I am facing an issue with my oneplus 2 device, I wanted to make it boot multiple ROMs so searched on google about this and I found a thread on this website only, and in that thread, there was a recovery and zip file given to flash so I booted into TWRP recovery and flashed the zip file first and then recovery and then reboot-->recovery, after that oneplus logo with "powered by android" text came and for 5 mins nothing happened. I connected the phone to my computer and typed the fastboot command-"fastboot reboot recovery", it reboot and stuck at the same state as before, then I used-"fastboot reboot", it rebooted into the oxygen os which was installed on it. then I flashed the original TWRP recovery using its official app as my phone was rooted. After that, I again tried to flash the multirom recovery but this time I flashed the recovery first and then the zip file but the same happened. I again booted into the rom and flashed the original TWRP recovery using the app and then I got to know on the internet that I should first shutdown the phone after flashing multirom recovery and then reboot it in the recovery and then flash the zip file, so I did the same but to my bad luck this time also same happened and this time I am not able to boot into the rom also and I am only now able to use fastboot and to the very worst my bootloader has also got locked I don't know how but it was unlocked last time but when I saw in fastboot it was saying that bootloader is locked. Please help me to fix my phone I have attached the multirom recovery file and the link to the thread. Please tell me if you all want any other info I will try to provide you that.
LINK TO THE THREAD:-
[MOD][FEB-28][TESTING] MultiROM v33 for OnePlus 2
TLDR: MAKE A BACKUP. Seriously. Downloads in second post. Flash recovery, then kernel, then MultiROM. A kernel with the kexec-hardboot patch doesn't exist as of now. It is being worked upon be me Introduction This is a port...
forum.xda-developers.com
{
"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"
}