I installed an incorrect custom recovery after rooting with King root. After thinking I did the wrong thing I flashed the bad recovery as my boot.img. So now my boot.img and recovery don't work and I'm on a boot loop. Please help
Rougebot said:
I installed an incorrect custom recovery after rooting with King root. After thinking I did the wrong thing I flashed the bad recovery as my boot.img. So now my boot.img and recovery don't work and I'm on a boot loop. Please help
Click to expand...
Click to collapse
Is your bootloader unlocked!? If yes, then fastboot flash the boot.img and the recovery.img of your stock ROM.
Sent from my Che2-L11 using XDA-Developers mobile app
No it isn't I just used king root! I can't do it from here either can I ?!
Then you have to unlock it first by getting the unlock code from Huawei. Here are the steps...
1. Go to https://hwid5.vmall.com/oauth2/port...huawei.com/en/source/plugin/hwlogin/login.php and login with you Huawei ID CONTINUOUSLY FOR 14 DAYS. Don't have a Huawei ID? Then click on "register".
2. After that, you'll be redirected to the unlocking website. Make sure to check the box below.
3. Next, you'll be seeing 5 boxes. Then...
• Enter your model number in the first box
• Enter you serial number in the second box (Can be found in settings or at the back of your battery)
• Enter your IMEI in the third box (Can be found in settings or at the back of your phone)
• Enter you Product ID in the fourth box (Dial *#*#1357946#*#* in the dialer app to get it)
• And lastly, enter the verification code in the fifth box provided beside it (The verificarion code should be a 4-digit code)
4. After entering all of the required information, click the blue box below of all boxes then you'll end up seeing your unlock code (It should be a 16-digit code)
5. Download and install Huawei Update Extractor, Minimal ADB and Fastboot and the drivers. Make sure that USB debugging is enabled in settings -> developer options.
6. Download also the stock ROM and don't install of course, you don't have a recovery.
7. Open Huawei Update Extractor and extract the update. Make sure to only extract recovery.img, boot.img, and system.img.
8. Move the 3 extracted files to the directory folder of ADB. While in the ADB folder, after moving the 3 files, hold Shift and Right click and select "Open command window here".
9. Get a good working USB cable and plug in your device (make sure the device is powered on and the screen is on as well) and type in and enter " adb devices". A pop-up will appear on your phone asking to authorize. Press okay or whatever positive it says. After authorizing, it'll be displaying a code. Maybe like ••••••••••••• devices. If not, then try adb devices again.
10. Once finished with that, type in and enter "adb reboot bootloader" which will reboot your phone to bootloader.
11. Once in bootloader mode, you'll be seeing a text below saying "PHONE Unlocked" or "PHONE Locked" in red. If it says "PHONE Unlocked", it means the bootloader is unlocked, if it says " PHONE Locked", then your bootloader is still unlocked which means you still have to unlock it. To unlock it, type in and enter "fastboot devices" first and you'll be seeing a code again just like from adb devices. If that code shows up then you're good to go.
12. Next type in and enter "fastboot oem unlock ••••••••••••••••". You'll replace those circles with your unlocking code of course. Your phone will now perform a factory reset and will say " PHONE Unlocked" now. Congratulations!!! You've unlocked your bootloader!!!
13. Now we have to flash the files. If you want to flash the recovery only, then type in and enter "fastboot flash recovery recovery.img" and will say OKAY at the end. If you want to flash the whole system, type in and enter these:
• fastboot flash recovery recovery.img
• fastboot flash boot boot.img
• fastboot flash system system.img
• fastboot reboot
Your phone will now reboot into the system. If it's successful, then congratulations!!!!!
Sent from my Che2-L11 using XDA-Developers mobile app
OMG
My phone isn't che2-l11 it's che2-l12.
Then why did your post says Che2-L11? Anyways, the method is just the same as Che2-L11, only select the UPDATE.APP for Che2-L12 not for Che2-L11. Good luck!
Sent from my Che2-L11 using XDA-Developers mobile app
Ok so I was on the zzkey a website trying to get my unlock code! Then I found out that's a $130 sub key . The reason I was on there was because I can't get my product I'd due to the fact that I'm in a boot loop
Rougebot said:
Ok so I was on the zzkey a website trying to get my unlock code! Then I found out that's a $130 sub key . The reason I was on there was because I can't get my product I'd due to the fact that I'm in a boot loop
Click to expand...
Click to collapse
Bro, you can get the unlock code from emui.com no need to use your phone because yes you are in a boot loop but instead, use another device or a computer.
Sent from my Che2-L11 using XDA-Developers mobile app
Che2-L11
Hey guys i have ended up with a huge problem here.
I am having the bootloop even with a flashed CWM recovery flashed it reboots.
I am allowed about a minute inside the recovery before it reboots.
I also suspect my unlock is not properly done.
If i use getvar command it fails.
However it does say my phone is unlocked at the bottom of the screen.
I should probably flash boot to make it stable so how do i do that and does anyone have any suggestion for what i can do now?
The original Emui recovery doesnt recognize the dl folder with update inside for the original rom.
I would love to get help making this stable again.
Thanks.
I believe i had as old as firmware version B086
it was stuck there which is the reason i tried to root and unlock because it was getting very old and unstable.
Related
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Did you unlocked bootloader first. try to flash it again but this time 3 times in a row without restarting device
It's wrong
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
Should be
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img picture of command prompt
And now it may not boot as you probably replaced boot.img with yours.
Not sure about that.
Try to download stock ROM and start from scratch
Sent from my K10 using Tapatalk
This guide is to help you recover from “The system has destroyed screen” on Redmi Note 7 Pro
I presume the bootloader is unlocked on your device.
The things you need are (Links are provided below):
1: VB meta and Peter’s TWRP (zip)
https://drive.google.com/open?id=1kd9H2cBsjkN-9oa2_6Sj8OlXLTfpRjNN
2: Platform tools (latest)
https://developer.android.com/studio/releases/platform-tools
Install Platform Tools to windows
First turn off the phone, and put it to fastboot mode by pressing the “Power button" and holding the "Volume down button" and release them when the fastboot mode screen appears.
Connect the phone to PC by USB cable, Place the “vbmeta.img” in a folder, hold shift and right click the blank space in the folder and select “Open powershell window here” (command prompt for windows 7)
Type fastboot devices and enter , you will see your device in the list.
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
After flashing vb meta, Its time to flash TWRP to retain the ability to flash rom again. To do that, place the “recovery.img” file in the same folder as “vbmeta.img”. open the powershell again by the method above, enter the command “fastboot devices” to ensure the device is connected. After that, enter the command “fastboot flash recovery recovery.img”, you will get success message below.
Now hold the “Power button” and “Volume up Button” and release the “Power button” as soon as the redmi logo appears while still holding the “Volume up button” till the twrp logo appears.
Flash Rom and you are set.
If you are trying to flash MIUI,
Download latest MIflash tool here and install it on windows.
https://androidfilehost.com/?fid=889764386195900328
Download latest fastboot rom for Note 7 Pro from below link and place the folder on desktop
http://en.miui.com/a-234.html
Open MIflash tool and put device to fastboot (steps to boot to fastboot are above), connect to pc via USB, click the refresh button on the flash tool and start.
The tool takes approx 400-500 seconds to complete , once its finished it will show in a green coloured text that its successfully completed.
Enjoy
DISCLAIMER
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
This Video can also help how to flash Note 7 Pro Using MI flash tool..
https://youtu.be/t8zqIMw-Zsc
i tried but after this step
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
it gives error disable verity unknown command. if i use fastboot flash vbmeta vbmeta.img it flashes sucessfully, i then install custom recovery and that flashess correctly too but when booting to recovery it still says system destoyed.
I recovered from the same issue with a newer fastboot version and LOS Twrp
ustaadg said:
i tried but after this step
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
it gives error disable verity unknown command. if i use fastboot flash vbmeta vbmeta.img it flashes sucessfully, i then install custom recovery and that flashess correctly too but when booting to recovery it still says system destoyed.
Click to expand...
Click to collapse
I got this same issue and then I downloaded the newer fastboot from a third party site. I assume you would had installed ADB and Fastboot systemwide(The one that requires Y as an answer and runs in blue command prompt) That one is like 1.3. You need to install a newer fastboot for this command to work.
I am not sure which one was it that I had but I am adding the link to the same. Newer Fastboot and added vbmeta
Also, I didn't install the Peter's Recovery because I was installing Lineage OS and used the recover_twistloop with wrappedkey for the same
Original Thread Here: LinegaOS16_RN7Pro
One more important thing: I didn't use "fasboot boot <recovery>" for it. I turned off the device and then used "Power Key + Volume Up". At first it didn't work but after one reboot it worked, and this is the only method I am using to go into recovery NOT VIA FASTBOOT or from inside the system. You can try it but it didn't work.
“fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”
P.S: I thought it was verify the first time I saw it.
Also, I really hope you are not going to install MIUI either via Fastboot or Recovery. If you are going to do check roll-back protection. First check your current roll back index and check the rollback in fastboot folder of the Fasboot ROM that you are going to install. More details here. WARNING. MUST READ THIS ARTICLE IF YOU ARE THINKING OF RE-FLASHING MIUI/EUMIUI AT ANY POINT OF TIME.
You will be doomed if you didn't read this. And not in a usual way like a bricked phone. You will need to visit the service center and maybe a month wait for the device to get fixed
Thanks for replying. I downloaded fastboot rom and flashed that with clear all and lock option.
Unlocked again, installed evolution rom and even tried aosipderpfest but whenever I tried installing magisk or after reboot phone stuck on phone is starting and it won't start, I can access settings but nothing else.
Finally wooed everything, installed EU rom then evolution rom. Then magisk now everything is smooth.
I installed the latest IN Global firmware
Now I have the message
"This MIUI version can't be installed on this device" and the unlock is gone
Now when I try with XiaoMiFlash I have error: "Flash xbl error"
And miunlock says 99% This device is not bound to this account
I don't know what to do now
Spleeny97 said:
I installed the latest IN Global firmware
Now I have the message
"This MIUI version can't be installed on this device" and the unlock is gone
Now when I try with XiaoMiFlash I have error: "Flash xbl error"
And miunlock says 99% This device is not bound to this account
I don't know what to do now
Click to expand...
Click to collapse
Xbk eror is related to baseband lock. I saw one video where following was mentioned
Put phone in fastboot mode
In adb use command fastboot oemlock
After that reboot and follow the miflash method with bottom option erase and lock selected. You need to download fastboot rom.
After you set up the device again. Go to developer settings and enable oem unlock and bind the account from there
(bootloader) Device is already locked!
"Flash xbl error"
I tried
violet_images_V10.3.10.0.PFHCNXM_20190725.0000.00_9.0_cn
violet_images_V10.2.5.0.PFHCNXM_20190316.0000.00_9.0_cn
osm bro you just save me thnx alot bruh
I tried to go back to miui11 from pixel experience(10) by flashing a fastboot rom using mi flashtool (clean and lock). the result of flashing is shown as successful but the device is not booting, instead it is showing 'the system has been destroyed'. i tried unlock the device using mi unlock and it unlocked succesfully and booted succesfully . then i locked the device using the command 'fastboot oem lock' and rebooted. but the eroor 'the system has been destroyed is coming'. after several attempts i found that locking bootloader is causing the error. can anybody tell why is this happening and way to succesfully lock my bootloader.
dineshp953 said:
I tried to go back to miui11 from pixel experience(10) by flashing a fastboot rom using mi flashtool (clean and lock). the result of flashing is shown as successful but the device is not booting, instead it is showing 'the system has been destroyed'. i tried unlock the device using mi unlock and it unlocked succesfully and booted succesfully . then i locked the device using the command 'fastboot oem lock' and rebooted. but the eroor 'the system has been destroyed is coming'. after several attempts i found that locking bootloader is causing the error. can anybody tell why is this happening and way to succesfully lock my bootloader.
Click to expand...
Click to collapse
did you found the solution??
i am getting the same error
I have two Redmi Note 7 Pro devices. (Global Devices - A.K.A Indian Variant)
first device is unlocked but no custom rom installed like ever
second device is unlocked with lots of custom rom history
While trying to relock my bootloader with MIFLASH (clean all and lock) and Global firmware 11.0.8
First device firmware flash worked perfectly and bootloader is set to lock state - (Widevine status is L1 )
Second device as stated in OP . Flashing success but device showing "SYSTEM HAS BEEN DESTROYED". If i unlock the bootloader of the device then it boots normally but device is in unlock state (widevine status L3)
I think some modifications might have happened to some system partitions which causes the VBMETA - SRCLIST check failure.
ANY DEVS PLEASE LOOKS INTO THIS ISSUE ...
Yeah someone out there I"m trying to relock bootloader bcoz to get access to my corporate mails , netflix HD content and GPAY
(On other hand magisk is having CTS profile check failure as google changed the approach to check the unmodified system)
please some can you help with the porting of twrp for this phone
even some help with official firmware v217 then we can root with magiusk and recovery image
this phone has the mtk processor MT6765
Infinix hot 8 pliss, i can instal twrp
Yes, help sir ? :good:
Infinix Hot 8 Need Support
Please really need support for root and twrp for this device,, this device is really nice,,
guys again some try and get the firmware v217 so we can extract the boot.img for magisk
i hope a update is coming soon plan to get thta to find this boot.img
online the v174 firmware is not the same
OTA Update for Infinix
X650C-H626DE-P-191005V224.zip
240Mb
capture via usbdebugg
http://www.mediafire.com/file/24dmq3hk7wbu6b3/X650C-H626DE-P-191005V224.zip/file
Mtk(mediatek) processor devices are not supported by custom ROM developers. Don't expect custom rom support for hot infinix 8. Sorry.
Did anyone try Readback in SP Flash tool? So far, I have not been successful in doing so.
got it
To unlock Bootloaded withour error in Fastboot use command
fastboot flashing unlock
and then on the phone select volume up key to acknowledge
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
darylzero said:
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
Click to expand...
Click to collapse
Screenshots
and UPLOAD THE orignal+patched BOOT.img
With complete VERSION INFO
Sent from my Infinix-X650C using XDA Labs
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Thank you very much.
My phone now has root access
Are you installed TWRP Recovery in your device.???
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
Are you installed TWRP Recovery in your device.i want TWRP recovery.can I install TWRP recovery after root my device.tel me.
https://forum.xda-developers.com/android/help/infinix-hot-8-t3986799/post80598837
Check this Thread for complete guide on
* UNLOCKING-BOOTLOADER
* ROOTING
* TWRP
* OPTIMIZATION
* UN-BRICKING
* CUSTOM-ROM
Sent from my Infinix-X650C using XDA Labs
How can I root my infinix hot 8 v x650D
Misbahu said:
How can I root my infinix hot 8 v x650D
Click to expand...
Click to collapse
Same method as I stated above.. just use compatible TWRP
Sent from my Infinix-X650C using XDA Labs
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Papichoolo said:
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Click to expand...
Click to collapse
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
AshhRED said:
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
Click to expand...
Click to collapse
I tried on a different PC with Windows 7, same issue. ADB Loads and detects, but fastboot doesn't.
It shows under ADB Devices but when I type, adb reboot bootloader.
The phone goes into fastboot mode, but isn't detected when using command, fastboot devices.
Drivers and eveything is setup correct on it too.
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.