Unable to get into recovery [Solved] - OnePlus 8T Questions & Answers

So today I tried out a couple of different custom OS´s for my OP8t all worked fine until I wanted to install a different OS again.
I was somehow not able to get into the lineage OS recovery, I tried flashing both 18.1-20211025 and 18.1-211028 which both flashed without issue but I still could not boot Into the recovery.
Then I tried twrp 3.5.2_11-0 but same problem here.
All my phone does is, show the startup logo for 0.5 seconds then the message about the unlocked bootloader and then it just shows the startup logo again.
What I have tried to fix the issue:
-Boot into recovery via fastboot
-Boot into recovery via key combination
-flash the stock recovery + boot image
-MSM Download Tool (the device shows up but when clicking start it shows an error message 1: open serial device failed 2: automatic detection of ddr failed)
-Followed this guide
Kinda helpless right now :/
I would be happy if anyone could help me solve this problem
PS. attached the MSM logs below

Your MSM log doesn't show a connection to your phone. Attached are a screenshot and MSM log that you would get if you get a successful connection to the MSM Tool and do nothing else.
I suggest you go back to the MSM Tool thread and make sure you've:
1. Installed the Qualcomm device driver properly
2. Followed the usage instructions properly.

BillGoss said:
Your MSM log doesn't show a connection to your phone. Attached are a screenshot and MSM log that you would get if you get a successful connection to the MSM Tool and do nothing else.
I suggest you go back to the MSM Tool thread and make sure you've:
1. Installed the Qualcomm device driver properly
2. Followed the usage instructions properly.
Click to expand...
Click to collapse
Hi thank you for your suggestion, I have solved this issue now.
I made sure, that I completely follow the guide and also downloaded the MSM on the official OP site and now it flashed on the first try.
So probably it was me who just didn´t follow the guide ;D
Thank you again for your help and have a nice day.

Related

ulefone Power 2 Development and Support

Ulefone power 2 Development and Support-
Basic Device Details-
Display- 5.5 inch
OS- android 7.0 Nougat
Chipset - MT6757T
RAM- 4GB
Disclaimer-
Code:
i am not Responsible for any damage to Your Device..
official Firmware-
https://drive.google.com/drive/folders/0B8NC4kBpjQhYV1lWOEtYWThRRms
twrp Recovery-
https://drive.google.com/open?id=0B1aXJDZjE8bvM0h0aTVEOEdBS1U
SP Flash tools and Driver-
https://drive.google.com/folderview?id=0B6O3B5Tc7Wr9ZzgxQmcyNmNoX00
Magisk-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
No verity opt-Encrypt-
https://www.androidfilehost.com/?fid=673368273298927206
extras-
Greenify for Battery-
http://m.hiapphere.com/apk-com.oasisfeng.greenify
Build.prop tweaks-
[Must Backup official before try-
https://forum.xda-developers.com/attachment.php?attachmentid=4248841&stc=1&d=1503381757
Guide-
Flash Firmware-
1. Install Vcom Driver Run SP flash tools, Load Scatter File , Check Everything and then click Download, as soon as connect your Switched off Phone.
Flash twrp-
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
or use inbuild script
if you have Scatter then you can Flash with SP flash tools.
Root-
flash Magisk via twrp or you can also use Supersu 2.78XX.
Mod-
Will be added Soon....:good:
version- 3.00XX
Credit- XN Logos
Donation- https://Paypal.me/droiddeveloper
Please Don't create mirror Without the Link of This Page.
I tried it but it didn't work. twrp is installed but my phone doesn't boot into the system anymore. When I reboot it goes back to Twrp and then the touchscreen doesn't work anymore. I have to connect an USB-mouse. But it still doesn't boot.
When I try to flash or wipe sth it says "unable to mount"
I had to flash the original software again with SP Flash Tools
No flash No verity encrypt to Disable boot verification
XN Logos said:
No flash No verity encrypt to Disable boot verification
Click to expand...
Click to collapse
sorry but what does that mean?
So i used your TWRP Recovery, normally it should work and it does but why is my data shown as 0.
Thank you too. Please help
where is the scatter file?
gasperoni said:
where is the scatter file?
Click to expand...
Click to collapse
no Scatter included use Fastboot, or You can take scatter from ROM.
Ok but where is the recovery image file to flash via SP Flash Tools? I only see an exe-file saying "flash recovery" and a 12.6MB file called "rk" but it's shown me as a mp4-file
it worked!!! Thank yoU!! @gasperoni, just start "Flash Recovery.exe" and do what is written in the window. It's really easy.
i have include a Script which have ability to unlock bootloader and then flash twrp, if you flash with SP flash tool your Device not bootup because bootloader is Loacked. so Simply use Given Instruction Not SP flash.
any custom ROM
non yet
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Unlucky25 said:
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Click to expand...
Click to collapse
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
kylebutler said:
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
Click to expand...
Click to collapse
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash softwhttps://forum.xda-developers.com/usercp.phpare says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
pavelmracek said:
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
Click to expand...
Click to collapse
Thank you very much for this! That tool works flawlessly unlike the ulefone garbage.
On another note... anyone know if there is source code for the power 2 to be found somewhere or did the dev just port another recovery somehow? I tried a while back just porting twrp by swapping files but i couldn't get the image to repack with the kitchen tool so i gave up.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Unlucky25 said:
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Click to expand...
Click to collapse
Uh, i never even bothered to think about imei as it just worked without doing anything.
ml11ML said:
Uh, i never even bothered to think about imei as it just worked without doing anything.
Click to expand...
Click to collapse
ok nevermind, i found a solution..yeyy
so if anybody stumples across here, who has no IMEI set, CDS information in MTK mode and no rooted phone... u can set your IMEI in MTK engineering mode under "GPRS"!

One plus 6 completly bricked

Hi everyone,
I'm quite new to unlocking and rooted phone, but I've read many many post on this forum but nothing worked....
Here what's happening;
Few days ago I wanted to Recover from TWRP a backup that I've made. I launch the recovery from TWRP (important details, it was a backup that I made from slot B in twrp....) in slot A.
So yes I indeed restore a slot B recovery into the slot A in TWRP.....
And I tried to reboot after that..... and the problems begins !!
I just have a blackscreen with a blue light, nothing happened..... Same thing If i try to boot into recovery mode.....
Since I tried many many things but nothing worked...... I can't boot into TWRP from fastboot.
When I'm trying that:
Code:
fastboot boot twrp-3.2.2-0-enchilada.img
The phone just reboot and got stucked on the screen with one plus logo and the text "fastboot mode" below the logo.....
I read all these post below and everything I tried (erase all data, change the active slot on fastboot mode......)didn't work:
https://forum.xda-developers.com/oneplus-6/help/oneplus-6-os-twrp-stuck-fastboot-screen-t3870989
https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-rooted-help-please-t3851802
This one I didn't really understand exactly what needed to be done but I guess I need to boot into a custom recovery as well:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Even tried that but it didn't unbrick the phone:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I tried to boot into another recovery, but same thing not working/booting;
Code:
fastboot boot blu_spark_r65-oos-pie_op6_9a5f932e4.zip
So I'm desesperate and really really need help !!:crying::crying:
Does anyone can help me step by step or has a solution please?
I can access to fastboot mode that is the only think I can do and the bootloader is unlocked.
Go and see there :
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
You'll get your phone like it comes out of the box.
yep, do this:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
I had the same problem with my OP3. i cant get past the fastboot screen. after i tried the tool everything was back to normal. but i had to oem lock after it to boot up.
Also use the official twrp for a fully functional backup and restore
Thank you all for your reply !
I've tried to follow the process from the link but the MSMTool is not finding my OP6 and I've uninstall in the Device Manager as indicated:
HTML:
plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug
But When I go into safe mode and re-plug, I can't do this part because I don't have this information....
HTML:
Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process
I tried on 2 different PC (Windows 10 and 7) but nothing worked so I can't used the MSMTool
You have to use it in safe mode to install the unsigned drivers. It only works when you see the device as something like 9800 in your device manager.
Dont worry if it fails a few times. I had to do this 8 times on my OP3 till it was successful.
You can also use this guide:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
The steps are the same

oneplus 8t(tmo) hardstuck in fastboot mode

Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
lostneedfound said:
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
Click to expand...
Click to collapse
WiFi not working because the boot.img you flash is not match your system version.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
ULTRAJC said:
WiFi not working because the boot.img you flash is not match your system version.
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot oem edl results in FAILED (remote: unknown command). tried it in minimal adb and fastboot and platformtools.
and that is the guide ive been following. however i keep getting partition issues.
lostneedfound said:
and that is the guide ive been following. however i keep getting partition issues.
Click to expand...
Click to collapse
Fastboot unbrick guide didn't work for you?
Maybe continue to try the key combination, open device manager, if you see devices name: …QDLoader 9008(driver installed) or …QHUSB_BULK(driver not install). That's EDL mode.
Some guide suggest this two command may work:
"fastboot reboot edl"
"fastboot reboot-edl"
Also can try "fastboot boot recovery that have adb.img" then use command "adb reboot edl".
okay so i none of that worked just continues to say unknown command or unknown partition. with the qual com i dont see anything otherthan android device for phone related stuff in the device manager. is there something ican do to get these partition errors to go away? last night i wasn't having any trouble with them and now they are everywhere and i really dont understand why becuase i hardly flashed anything last night. today i started flashing stuff from the guide you recommended/the one ive been using all this time and thats when the partition errors started and now im seeing them everywhere and i followed the guide down to the dime.
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
lostneedfound said:
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
Click to expand...
Click to collapse
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
nujackk said:
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
Click to expand...
Click to collapse
Exactly @nujackk ,
I have found the most likely reason for an "unknown command" message to a newer fastboot command is an old fastboot.exe version.

How to go back to stock OxygenOS on OnePlus 7

So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?
Fuwlz said:
So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?
Click to expand...
Click to collapse
Hello, did you follow the instructions here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3954325/
?
Yes, MSM tools just doesn't work
Me too, I can't start this EDL mode, it just goes straight to fastboot.
I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.
WookieTookie said:
I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.
Click to expand...
Click to collapse
Hi,
Just experiencing the same. I would like some help pls !
Tried LineageOS. Not stable enough on OP7 so I want to go back to OOS.
Got OnePlus 7 - 1903 model EU, so I believe it's GM57BA that I have to deal with.
Tried fastboot methods, not successful. I followed this post. Tested this on linux.
Encountered "Flashing is not allowed for Critical Partitions" even though I got :
Code:
❯ fastboot flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
❯ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Device was stuck during boot (left it about an hour to try, nothing happened).
At some point I faced Qualcomm Crashdump Mode Screen.
Now I think the only option is to go for MSM method but not available for linux, so I switched on windows.
Instructions on this post seem pretty clear but when I plug the phone on PC, device is not recognized, don't know why I can't install phone driver properly (but probably not important at this stage).
Qualcom drivers are installed but I can't get my phone to boot on "EDL mode" ?
vol - and vol + while shutting down/powering on the device, plugged/unplugged to PC (tried few combos).
So device is not recognized and I can't run MSM Enum.
I have probably missed something... if anyone could give a hint on how to do that, I would greatly appreciate it.
Ok so I finally found a way to solve my issue.
Followed instructions from this video.
Basically I had to disable driver signature enforcement on my pc. This allowed me to properly boot on EDL and detect the device using MSM.
Hope this will help

Can a "Hard-bricked" android phone be restored if there's still access to Download mode?

I accidentally installed the wrong ROM on my phone, and now it's unresponsive (nothing happens when I try to turn it on, not even a vibration)
But I managed to access Download Mode (aka EDL, right?).
Can I restore it if I have the Scatter file and the Stock ROM?
Thanks in advance
MediaTek devices have preloader mode, EDL mode is for Qualcomm
Not sure what device you're talking about, but try to look for an "unbrick tool" or an "unbrick guide"
I "semi hard-bricked" my OnePlus 3T a while ago, and there was this leaked Qualcomm tool that you could use to flash the factory ROM the phone came with from Download Mode.
aIecxs said:
MediaTek devices have preloader mode, EDL mode is for Qualcomm
Click to expand...
Click to collapse
Does the fact that I can communicate and flash via Download Mode (SP Flash Tool) mean that I didn't lose my preloader? I'm kinda stuck trying to flash the Stock ROM (demanding verified image files, even though I'm using the original firmware for flashing... probably)
Lada333 said:
Not sure what device you're talking about, but try to look for an "unbrick tool" or an "unbrick guide"
I "semi hard-bricked" my OnePlus 3T a while ago, and there was this leaked Qualcomm tool that you could use to flash the factory ROM the phone came with from Download Mode.
Click to expand...
Click to collapse
I'll check the guides online, hopefully I'll find one that'll help.
mouradsme said:
demanding verified image files, even though I'm using the original firmware for flashing
Click to expand...
Click to collapse
I've also had issues previously with trying to flash stock images on Samsung phones. Not sure if you have country-specific images, if you do, try giving all of them a shot. I'm from Hungary, and a locally bought Samsung phone only came to life after flashing a Spanish factory image.
you need to (by)pass SLA/DAA authentication
Now I managed to bypass protection, and got the successful flash message from SP Flash Tool.
But I still can't solve the issue (Phone still only responsive from BROM)
For reference I'm using the global version of RMX3171 (Realme Narzo 30A) based on MT6768, and the Stock ROM is available online.
I flashed every partition (Provided in the Stock ROM), and Now it is booting, showing the logo + a message "Download not completed Error Code 0x992566 " and then it reboots after a minute or so -_-
I think that means you did not flash all partitions (some not included in Download)
In the other thread someone mentioned "Format All + Download" very bad idea never do this.
did you try unlocking bootloader from mtkclient like suggested in that thread?
mouradsme said:
Hello,
Can someone share their nvdata & nvram + oppo_custom?
I seem to have formatted mine, and need them to recover my Narzo 30A.
Click to expand...
Click to collapse
https://androidmtk.com/use-sn-write-tool
https://www.hovatek.com/forum/thread-116.html
aIecxs said:
https://androidmtk.com/use-sn-write-tool
https://www.hovatek.com/forum/thread-116.html
Click to expand...
Click to collapse
I came across the tool, but I failed to enter into Meta Mode.
I'm trying to make my phone boot to the system, then I'll try restoring my IMEI's using MTK Engineering app.
Thanks for links though
mouradsme said:
I accidentally installed the wrong ROM on my phone, and now it's unresponsive (nothing happens when I try to turn it on, not even a vibration)
But I managed to access Download Mode (aka EDL, right?).
Can I restore it if I have the Scatter file and the Stock ROM?
Thanks in advance
Click to expand...
Click to collapse
There is no such thing as a "hard bricked" device that can still boot into TWRP. A hard bricked device is completely dead and shows no kind of activity or function. It won't charge, it won't boot into any kind of mode and can't make a connection to PC, makes no sound when connecting to PC and it won't appear in device manager when connected to PC.
A device that can boot into download mode but not its other modes is just a softbricked device.

Categories

Resources