After installing the "15 seconds adb installer", I shift clicked the folder with my twrp file, "twrp-3.0.2-0-tbltetmo.img" to open the command prompt and type in "adb reboot bootloader" , causing my screen to go into boot loader mode. [ e.g. image ] ]So far, everything is going well, according to this guide.. However, the problem is the next step. Once in boot loader mode, i type in "fastboot flash recovery twrp-3.0.2-0-tbltetmo.img" . Instead of masses of text appearing, I instead receive the message: "Waiting for device." To be honest, I think my problem lies in the fact that before i went into boot loader mode, my phone was detected by my pc, but after it shifts to boot loader mode, it stops being detected, this causing the "waiting for device" message. However, even though I know the cause, I can't find any means to fix it after searching for hours. Also, yes, I enabled allow unknown sources and usb debugging. I've also went to T-Mobile's website to install their usb driver.
Jordan Miles said:
After installing the "15 seconds adb installer", I shift clicked the folder with my twrp file, "twrp-3.0.2-0-tbltetmo.img" to open the command prompt and type in "adb reboot bootloader" , causing my screen to go into boot loader mode. [ e.g. image ] ]So far, everything is going well, according to this guide.. However, the problem is the next step. Once in boot loader mode, i type in "fastboot flash recovery twrp-3.0.2-0-tbltetmo.img" . Instead of masses of text appearing, I instead receive the message: "Waiting for device." To be honest, I think my problem lies in the fact that before i went into boot loader mode, my phone was detected by my pc, but after it shifts to boot loader mode, it stops being detected, this causing the "waiting for device" message. However, even though I know the cause, I can't find any means to fix it after searching for hours. Also, yes, I enabled allow unknown sources and usb debugging. I've also went to T-Mobile's website to install their usb driver.
Click to expand...
Click to collapse
Possibly the cable. Not sure if the USB drivers you got from T-Mobile's website are the same as the one that TEKHD posted in his Tutorial thread for rooting...but I use those and with my original cable. (sometimes with my Xbox One charge cable) Hope that helps.
I know that if I use a a cheap or thin cable, I get problems.
SiNJiN76 said:
Possibly the cable. Not sure if the USB drivers you got from T-Mobile's website are the same as the one that TEKHD posted in his Tutorial thread for rooting...but I use those and with my original cable. (sometimes with my Xbox One charge cable) Hope that helps.
I know that if I use a a cheap or thin cable, I get problems.
Click to expand...
Click to collapse
Thanks for your reply. I gave up using the usb cable method to connect to adb. Instead, I just flashed it with Odin, which works (strangely, even though my device still didn't appear under "Computer")
Hi,
Last Sunday (5) my phone turns off with 25% battery and just don´t turn on.
I was with the stock Oxygen OS.
Now when i turn it on, the oneplus logo appears and the next "screen" that should be the android or any other OS loading, just don´t appear. It just go to black and turn off.
Reading the Threads here about "OP3T Bricked" they all requests to hold volume up, and connect the usb cable.
The problem is when i do it, the driver just pop up at Device Manager List, and few seconds later it disappears.
(Try it using 4 different computers (Desktop win7 , laptop win7, laptop win 10 and desktop winxp) and 2 original OP cables.)
I had read a lot of informations that you share here in forum, but no tips helps to solve this issue.
So i contact the OnePlus support, they give me some links to download 2 encrypted files that looks like the files you guys shares here (One is the driver and the other is some kind of unbrick tool called MSM).
They connect at my computer and as soon they see that my driver just pop up and disappear, they stop the process and said to me to send the device to one support center.
Probably i will do it, but first i want to guarantee that its nothing i can do here.
So I try to reach my phone throw ADB and fastboot commands.
When at the screen of Fastboot I have some information about the phone and the last line said:
DEVICE STATE - LOCKED
using the command adb devices, we don´t find anything.
using fastboot devices, my device is listed by the serial number.
Should be possible to recover it using fastboot commands ?
There is a way to analyze my phone throw fastboot commands? Something like "all hardware is ok", like the memory, battery, etc ?
Best Regards
I have encountered the same issue while I was playing around with a beta oreo rom the name of which I wouldn't not want to mention here. Got my phone bricked and it wouldn't boot to recovery. Only fastboot was accessible so what I did was just flash the blusaprk v45 recovery and after booting I was finally successful in booting my phone into recovery where I wiped system, data, cache and dalvik without internal storage and flashed a nougat rom. Thankfully I was able to revive my phone and that solved my issue.
UPDATE:
I try to use the fastboot commands, but to do it i must use "fastboot oem unlock"
And guess what?! i can´t ...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.023s
Click to expand...
Click to collapse
So a lot of answer for the people who get this fail is to use the MSM tool .....
Any tips ?
Have you read THIS thread? Try to follow exactly those instructions...
jonsat said:
Have you read THIS thread? Try to follow exactly those instructions...
Click to expand...
Click to collapse
Hi Jonsat,
Yes, i tested and as i said, i can´t do it because the driver don´t still at device manager list.
So, the problem was solved, i need to use the OnePlus Support and converge them to use the files like "my method":
The Regular method is:
1) Hold volume +
2) When holding, plug the phone at PC
3) The device should appear at device manager, so you can run tools like MSM
This method does not work for me because my device doesn't still at device manager list, it just pops up and disappears.
So to make it work i need to:
1) Turn off the phone
2) Hold power + Volume +
3) Plug the phone
4) The phone should start with fastboot menu
5) Select recovery mode
6) hold volume +
Now the driver still on device list.
Using this solution, the files that we see here in forum does not work.
Need to use the files from OnePlus Support, MSM3.08 + OnePlus3T_A56(A57, or newer) + Driver Qualcomm signed 24/04/2013.
Thanks you
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
jonsat said:
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
Click to expand...
Click to collapse
Glad to help
Hello, I have a Razer Phone 2, yesterday I uploaded a ROM on it, everything seems to have installed after whether the phone displayed a notification "Your device is corrupt. It can’t be trusted and may not work properly." then the notification disappeared and the phone will appear on the Razer powered android logo . after pressing vol - and the phone switch, the bootloader starts but I can not do anything in it, neither recovery mode nor wipe userdata, after clicking them, it returns to the razer logo and stands I looked and tried everything but I can't do anything about it, is this the end of the phone or is there any chance to get it back?
Thank you for your help and sorry for the spelling (translator)
lukkiii96 said:
Hello, I have a Razer Phone 2, yesterday I uploaded a ROM on it, everything seems to have installed after whether the phone displayed a notification "Your device is corrupt. It can’t be trusted and may not work properly." then the notification disappeared and the phone will appear on the Razer powered android logo . after pressing vol - and the phone switch, the bootloader starts but I can not do anything in it, neither recovery mode nor wipe userdata, after clicking them, it returns to the razer logo and stands I looked and tried everything but I can't do anything about it, is this the end of the phone or is there any chance to get it back?
Thank you for your help and sorry for the spelling (translator)
Click to expand...
Click to collapse
Flash stock following instructions on Razer Developer portal
jonchance_84 said:
Flash stock following instructions on Razer Developer portal
Click to expand...
Click to collapse
He follows the instruction and when entering the commands, <waiting for device> is shown . I have installed all the drivers
lukkiii96 said:
He follows the instruction and when entering the commands, <waiting for device> is shown . I have installed all the drivers
Click to expand...
Click to collapse
Installing drivers while phone is in fastboot mode too. Do checks while booted with adb devices and then boot into fastboot then run fastboot devices. If you get a device on each one, script should work. The pc sees a different device for each mode.
jonchance_84 said:
Installing drivers while phone is in fastboot mode too. Do checks while booted with adb devices and then boot into fastboot then run fastboot devices. If you get a device on each one, script should work. The pc sees a different device for each mode.
Click to expand...
Click to collapse
I think it's a hard brick, no command works, I guess I'll give up, is there any Razer service in Europe that could repair it for a fee?
lukkiii96 said:
I think it's a hard brick, no command works, I guess I'll give up, is there any Razer service in Europe that could repair it for a fee?
Click to expand...
Click to collapse
Could be a Win10 2004 build issue. Some have had luck either using an older win7 machine or loading up a linux vm in win10. U can let it take control of usb ports. It all stems from usb drivers in windows.
Don't know about service in europe. Im in Texas.
jonchance_84 said:
Could be a Win10 2004 build issue. Some have had luck either using an older win7 machine or loading up a linux vm in win10. U can let it take control of usb ports. It all stems from usb drivers in windows.
Don't know about service in europe. Im in Texas.
Click to expand...
Click to collapse
I followed your advice and used a computer with windows 7 everything flashed everywhere ok, only now when the phone turns on the message pops up "your device i corrupt. It can't be trusted and may not work properly" if something went wrong ?:crying:
Edit:It was enough to use the command fastboot flashing unlock_critical and everything works as it should, thanks a lot for your help, best regards
I'm a newbie at this but managed to stumble through installing CM 14.1 on my LG G2.
Phone: LG G2 VS980
CyanogenMod version: 14.1-20161207-unofficial-phoenix-vs980
Kernel version 3.4.0-crdroid-g0f70b4b
TWRP v2.8.6.3 (I don't know how this version got installed, I started out with a 2.7 version and upgraded to a later version but this is the version I see after I got CM installed).
Latest version of ADB and Fastboot from the platform-tools download.
I'm trying to make the phone automatically turn on when plugged into a charger using the " fastboot oem off-mode-charge 0" command .
ADB commands work fine.
If I issue the command "adb reboot bootloader" when the device is booted in CM I get rebooted into a black screen with the following:
"Firmware Update Do not unplug the USB connection until the process is complete." There is a progress bar that remains at 0%.
Any fastboot command I issue returns "waiting for any device". I have to hold down the phone power button for several seconds to exit this screen and then the phone reboots normally.
If I issue the "adb reboot bootloader" command when the phone is in TWRP or I select Reboot - Bootloader from TWRP the phone just reboots into CM.
What am I doing wrong?
Thanks
I'm not too familiar with this phone, but all that I know is that it is in download mode, which is not the same as a bootloader. As a lot of android phones aren't the same as each other, I am not aware of how to boot into a bootloader of this phone.
I will say though, if it is anything like a Samsung phone, then it probably does not have a bootloader and the only way to interface with this mode is through the LG Flash tool found here: https://lgflash.com/LGUP/
Don't take my word for it, but it is possible that this is the case. Again, I don't have any idea how the phone works or anything, but this is possibly the solution.
NTGDeveloper said:
I'm not too familiar with this phone, but all that I know is that it is in download mode, which is not the same as a bootloader. As a lot of android phones aren't the same as each other, I am not aware of how to boot into a bootloader of this phone.
I will say though, if it is anything like a Samsung phone, then it probably does not have a bootloader and the only way to interface with this mode is through the LG Flash tool found here: https://lgflash.com/LGUP/
Don't take my word for it, but it is possible that this is the case. Again, I don't have any idea how the phone works or anything, but this is possibly the solution.
Click to expand...
Click to collapse
I believe I'm in download mode when I'm seeing the black Firmware Update screen. I'm not trying to flash a ROM at this point so I don't think the LGUP program will be helpful.
If there is a another way to get my phone to turn on when power is applied to the USB cord I'm open to it.
RKCRLR said:
If there is a another way to get my phone to turn on when power is applied to the USB cord I'm open to it.
Click to expand...
Click to collapse
Perhaps by modifying whatever starts when it's charging.
Charging animation for example...
The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.
Any fastboot command I issue returns "waiting for any device".
Click to expand...
Click to collapse
1st thing of all things in order to run Fastboot commands is you have to run command
Code:
fastboot devices
what establishes the USB connection. As long as the connection isn't established Fastboot throws message "waiting for any device".
BTW:
Booting into device's bootloader ( FYI: each device has a bootloader ) requires in addition to the well-known Fastboot driver the Android USB Driver got installed, too. This driver is OEM ( brand/model ) specific, you have it to obtain from OEM - mostly offered on their website.
jwoegerbauer said:
The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.
Click to expand...
Click to collapse
Not the same really - and LGs aren't Samsungs, or whatever either...
One maybe could try emptying LAF partition ("nuking"). Some more drastic ways also suggest it for boot as well. But IDK, is it worth the trouble really? And even if one could get into the fastboot, that command might not work after all...
jwoegerbauer said:
The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.
Click to expand...
Click to collapse
The way I get into download mode is to hold the volume up button and plug in the USB cable with the phone off. When I do this I briefly see a screen that says Download with a blue hashmarked bar below it. It then goes to a screen that says "Firmware Update Do not unplug the USB connection until the process is complete." with zero percent progress.
Should I be able to issue fastboot commands when the phone is at that screen?
RKCRLR said:
Should I be able to issue fastboot commands when the phone is at that screen?
Click to expand...
Click to collapse
Nope.
CXZa said:
Not the same really - and LGs aren't Samsungs, or whatever either...
One maybe could try emptying LAF partition ("nuking"). Some more drastic ways also suggest it for boot as well. But IDK, is it worth the trouble really? And even if one could get into the fastboot, that command might not work after all...
Click to expand...
Click to collapse
I'm trying to repurpose the phone as a dedicated Android Auto "server" and would like to be able to leave it connected to my car. It would be really useful to have the phone turn off when there is no USB poser and turn on when there is USB power.
If I make a backup of the Boot and System partitions within TWRP would that allow me to restore my LAF if I nuke the LAF and something goes awry?
RKCRLR said:
to have the phone turn off
If I make a backup of the Boot and System partitions within TWRP would that allow me to restore my LAF if I nuke the LAF and something goes awry?
Click to expand...
Click to collapse
>to have the phone turn off
Could it be there some app for such? IDK, maybe...
>If I make a backup
Nope again, The LAF has a partition of it's own. To backup use lglaf.py or LGUP having the dump option enabled or extract it from kdz if available.
CXZa said:
>to have the phone turn off
Could it be there some app for such? IDK, maybe...
>If I make a backup
Nope again, The LAF has a partition of it's own. To backup use lglaf.py or LGUP having the dump option enabled or extract it from kdz if available.
Click to expand...
Click to collapse
This is probably a bridge too far for my skill level.
Is there a work around like putting it into a deep sleep that will let the battery to last for days or weeks but wake up when the USB has power?
RKCRLR said:
This is probably a bridge too far for my skill level.
Is there a work around like putting it into a deep sleep that will let the battery to last for days or weeks but wake up when the USB has power?
Click to expand...
Click to collapse
There's probably a way to do this via root and there will probably be some app that lets you do this. Other than that, you'll have to dig around and see what you can find.
Thread cleaned and moved to Verizon LG G2 section
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
PLEASE SEE "TROUBLESHOOTING" AT THE END OF THE GUIDE FIRST IF YOU HAVE PROBLEMS IN THE PROCESS BEFORE ASKING!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
VIDEO GUIDES
FOR LINUX METHOD CLICK HERE - Credits to @bx2_nero
Windows Method
Requirements:
Bypass Tools Pack - (SPFLASH TOOL, DRIVER AND BYPASS FILES)
Decrypted OFP (OPPO FIRMWARE PACKAGE) Files:
FULL FIRMWARE - INCLUDES THE "USERDATA" PARTITION, HENCE LARGER.
B.53 - Mega - Google Drive - Mirror3
B.37 - Mega - Google Drive 2
B.23 (First RUI Update for the device) - Mega - Google Drive - Mirror3
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
NOU (NO USERDATA) FIRMWARE - FOR PEOPLE WITH LIMITED DATA PLAN.
B.53 - Google Drive - Mirror 2
B.37 - Google Drive - Mirror 2
B.23 - Google Drive - Mirror 2
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
Please read an explanation of what is userdata partition and how different is this from other firmware here.
Note: All files with available links above are tested.
Python (Must add to PATH during installation, see screenshot if you don't understand)
libusb-win32 - Having Issues? Use this.
{
"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"
}
Make sure to choose the last option.
1)Open command prompt by running cmd,
enter
python -m pip install pyusb pyserial json5
After the installation, you can re-run the command. If it looks like the screenshot above you're ready to go to next step.
after the installation leave CMD.
2) Go to driver folder, find the .inf file right click and press install.
3)Download this file and install it, after installing plug your phone to PC by connecting your phone to PC while doing Vol+- . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.)
If you had a problem here, please check the end of the guide for it's fix.
5)Go into Flash Tool folder and open the SPFlash tool, after that choose scatter file and also if not set, set your download -agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
After flashing it should look like this. Download has been complete. Enjoy!
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
Spoiler: TROUBLESHOOTING - FAQ AND FIXES
POSSIBLE ERROR: "Verified boot enabled."
There are 2 fixes to this.
1st Method (DIRECT FIX):
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
2nd Method (WORKAROUND):
If you're getting this error, and you are SURE you used "Download Only" mode, there's a way to get rid of this. First, load the scatter then untick/deselect partitions listed below.
opporeserve2,
cdt_engineering,
my_custom,
special_preload,
userdata,
super,
After running brom.bat and flashing all partitions except the ones listed above, your phone will be able to reboot to stock recovery. Now select " Power Off" option then go run brom.bat, bypass authorization and then flash partitions listed below from SPFlash Tool.
super,
dtbo,
userdata
Your device will be able to boot into system after this if you have followed steps correctly.
POSSIBLE ERROR: Issues while disabling protection;
Power off your device Restart the process from 2nd step.
POSSIBLE ERROR: Issues while flashing;
Power off your device, you will need to do the bypass again. Check your USB Cable, there might be a disconnection. If not, start from 3rd step and make sure you did everything right.
Spoiler: FOR PEOPLE WHO WANT TO DOWNGRADE AND FOR PEOPLE WHO WERE ON EU VERSION
So, welcome to hell(!).
For people who want to downgrade:
If you want to downgrade to any version you would like, just use the B23 file as it is the oldest ofp file i could find for extracting process. If you were on EU version before (Any version starting with A) download ozip from here(for EU) , here(for Global) and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
For people on EU who want to unbrick:
So, you can use any version starting with B and it should work. It works in my case, i was on A.48, i flashed B53 and over that flashed B23. No probs at all. If you want to return to EU rom (starting with A) download ozip from here and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
Thanks --
https://github.com/bkerler/oppo_decrypt for decryptor.
https://github.com/MTK-bypass for creating the tool.
Thank you for your efforts. Can you add the decrypted A34 file?
mercan01 said:
Thank you for your efforts. Can you add the decrypted A34 file?
Click to expand...
Click to collapse
Hello! I wasn't able to find factory package (ofp) files for any version that makes sense for versions starting with A. (EU). There are A11 and A08 which according to update trackers, did never exist and the A.11 package is %50 larger than all the other files weirdly. I have contacted owner of some sites that do upload files like these and they asked for money. If it's a resonable price i will get it, decrypt it and upload here! If you were able to find any versions starting with A, feel free to message me on telegram (@ctivity) or email me!
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
mercan01 said:
Hi, I have a website that publishes A24 version only. https://www.getdroidtips.com/realme-6-software-update/. It gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello again. According to the site you have just sent, A.11 is the first update to EU version. I was thinking it was a mistakenly uploaded file, since userdata partitions are for some reason 9gb with this one instead of 3. If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work. Unfortunately, these files you sent in the link are ozip files and update packages while ofp files are firmware packages and they include everything. There are only 2 ofps -decrypted and not decrypted- available for now starting with A(EU), A08 (first ever firmware for EU) and A11(first update to EU version).
Hello again. Yes, I noticed there was an ozip file and deleted it.
daeSundae said:
If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work.
Click to expand...
Click to collapse
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
Hello! I'm sorry for the inconvenience I have tried flashing A11 file and it caused several problems just like in your case, however if you didn't select "Format All+ Download" mode you should be able to recover your phone. So, I had the exact same issue today and due to that I will be removing the A11 file from the links. Also, never forget to select Download Mode only! Several people bricked today and their IMEIs, Serial Numbers are all gone! Never select anything else than Download Mode!
So the solution is to download B53 decrypted files, load the scatter and untick listed partitions
opporeserve
,cdt-engineering,
mycustom,
special-preload,
userdata,
super
and then start the flashing in download mode. Now, you might be wondering "How am I going to go into the download mode again?" It's very simple. All you have to do is to keep pressing on Power and Vol- for some time and then, connecting to the pc with both volume buttons pressed while brom.bat is running. If you get an error, just reinstall device filters and that should fix the problem, then you can start downloading. After downloading these partitions to the phone, you will be able to see a boot animation and as well as a realme logo. Reboot to recovery, power of your device and then go into download mode again and flash userdata, dtbo and super partitions this time around. It should boot into system. However, the version will be B.53 but you can use the latest ozip (A.48), flash it from recovery and then format your data. It will bring you back to EU version.
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
So, i just read your reply again.
"Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device."
i dont think it's an issue caused by the device. Can you install oppo drivers from this link and let me know what happens afterwards? Or if you're fast enough you might prefer going into device manager by right clicking on Windows button and uninstall it's driver? I will also request you to start from step 2 to ensure installing drivers. I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
mercan01 said:
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello! I have uploaded B23 files both on google drive and mega. It should work for you, it is working for me at the moment. I also was on A48 firmware and both B23 and B53 versions worked without a problem.
daeSundae said:
I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
Click to expand...
Click to collapse
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt. Do you know if your phone has any charge or not? Can you try different volume and key combinations? A broken firmware shouldn't make the BROM Download mode inaccessible.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to
use "fastboot reboot" command. Please keep pressing vol - button if you can while rebooting if it works. That should, if possible reboot you into recovery.
Also as you said, keeping pressing on power and vol+ buttons don't work in this state. In fact, in this state nothing visually works, there is no screen output and I'm actually pretty sure it's the same for begonia (RN8 PRO). You will need to ~ if it's detecting it as a fastboot device need to use minimal ADB and fastboot tools to get rid of that state. I didn't have the same issue as you though. While I was in same state, I kept on pressing on Vol - and Power buttons for around 30-40 seconds (obviously without a response from the device) and after that pressed both volume buttons and connected device to PC. Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
MTK Bypass Universal
My screenshots were used in this post. I don't mind
MEGAFON929 said:
MTK Bypass Universal
My screenshots were used in this post. I don't mind
Click to expand...
Click to collapse
I'm sorry for not letting you know Dinolek. I tried to create a guide but my Windows is Single Language and since it's not global version or something I cannot change its language. I had to find an English screenshot. If it's a problem, I'll just remove them.
No, I'm not Dinolek. I just talked to him and he accepted my instructions. Let the screenshots lie, I don't mind.
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt.
Click to expand...
Click to collapse
Sounds reasonable and I hope it's true.
daeSundae said:
Do you know if your phone has any charge or not? Can you try different volume and key combinations?
Click to expand...
Click to collapse
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
daeSundae said:
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to use "fastboot reboot" command.
Click to expand...
Click to collapse
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
daeSundae said:
Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
Click to expand...
Click to collapse
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Can you try ADB reboot command on Linux? As it is identifying as a fastboot device?
cmfan said:
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Click to expand...
Click to collapse
If it's detecting a fastboot device, the device isn't dead. What I'm guessing is that your device is working, and on fastboot mode but since there's no display output in this state it will only show a black screen. Can you do ADB devices command? Im guessing adb reboot requires authorization though, but it's worth trying. What I will be requesting from you is to try pressing (and keep pressing on) different key combinations while device is in that state for like a minute or so, for example keep pressing on Vol- and power for a minute then switch to Power and Vol+ for a minute and then keep pressing on both volume buttons and connect device. Can you also see the results after plugging your device into charge and letting it stay for around a minute? I know these might make no sense technically, but in my opinion randomness is your best friend to get rid of situations like this..
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Hello. again. So, i have asked few people about your situation. Conclusion is, if none of these work you will need to wait until battery wears off and device turns itself off, i'm afraid. I will ask you to not use your phone for like a day and not to keep it connected to a computer for a long time. After making sure it powered off (which, i'm guessing there is actually no way to do that) make sure to prepare the brom.bat file plug in your device with VOL+ - combo and go on. Before doing this make sure to Device Manager > Action > Add Legacy Hardware > Next > Install the hardware that I manually select from a list (Advanced) > Show All Devices > Have Disk > Choose the cdc-acm.inf > Choose Mediatek USB Port and install it to not waste time. I hope your problems will be fixed. I have confirmed that BROM mode shouldn't fall into an inaccessible state because there's no efuse.ini blown. It must be there, but you're probably stuck in a mode that doesn't allow doing anything for some reason.