Database Users

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 ??

unlock bootloader for v410

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

[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??

SM-g935df hang with boot screen

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.

Android 12 GSI Works on the 2019 Onn 8" Tablet (ONA19TB002)

UPDATE - Android 12.1 Works!
I have the original 2019 release of the Onn 8" tablet. I decided to mess around with some GSIs. I managed to get the phh AOSP 12 GSI to work fairly well on the tablet.
I first unlocked the bootloader. I then flashed on the modded vbmeta image. I proceeded to flash the system-squeak-arm64-ab-vndklite-vanilla system image. It seems to be important to use the vndklite file as it allows you to modify system. I had to resize the system partition with some instructions I found. I then was able to flash NikGApps core. The system doesn't seem to boot without setting a property.
The system then booted, but with some flickering. The flickering can be solved by enabling Disable HW Overlays. To use Magisk, I had to use the Securize option after patching the boot image. The option seemed to force a factory reset as well. It is fairly slow, but the tablet has always been pretty slow. Sadly videos don't seem to work, as YouTube only shows a black screen with audio.
Here are some screenshots.
{
"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"
}

did you do this through twrp, fastboot or SP flash tools? Where/how did you get a modded vbmeta file? sorry for all the questions, im just curious as i also would like to flash another gsi onto mine

Mayday_Channel said:
did you do this through twrp, fastboot or SP flash tools? Where/how did you get a modded vbmeta file? sorry for all the questions, im just curious as i also would like to flash another gsi onto mine
Click to expand...
Click to collapse
I used Fastboot to flash the GSI images. I used TWRP to resize the system partition and flash NikGApps. This XDA article has a guide on how to flash a GSI and has the VBMeta img.

thanks man

did you do "fastboot flash system gsi.img"
or "fastboot flash super gsi.img"? system doesnt exist on my 3562

Mayday_Channel said:
did you do "fastboot flash system gsi.img"
or "fastboot flash super gsi.img"? system doesnt exist on my 3562
Click to expand...
Click to collapse
I'm assuming you have an Onn tablet that came with Android 10+. You probably need to reboot into fastbootd. You should be able to do it with fastboot reboot fastboot.

yep, already tried fastbootd, ill keep troubleshooting and ask questions when i hit a wall

Pix12 said:
I'm assuming you have an Onn tablet that came with Android 10+. You probably need to reboot into fastbootd. You should be able to do it with fastboot reboot fastboot.
Click to expand...
Click to collapse
why not adb reboot bootloader?

Android 12.1 works!
The 12.1 phh GSI just came out under prerelease. It seems to work on the Onn 8. It's really good that it works because 12.1 was made for tablets/foldables. Monet works without any modifications too. The default launcher seems bugged though. Screenshots are attached.

Any chance the TrebleDroid 13 (Lineage, Pixel Experience, etc) images have fixed any of these issues? HW Overlays likely has a performance hit and for me broken video playback is the deal breaker.
I have the original ONA19TB003 if that matters.