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
Related
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.
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
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 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.
Hi
I have a Redmi note 10, i unlocked the bootloader and tried to install the custom recovery Orange fox, i posted this question on the main Orange fox trhead but as i read its no longer being mantained, so i made a separate thread.
what i did is follow a tutorial in which i was instructed to dowload bot the Adb exe, and using the commands to flash the recovery img.
what i did step by step is the following:
1. Unlock bootloader
2. Start fast boot and connect my device to my PC using the original usb cable
3. Download Platform tools and Orange fox recovery
4. Copy the recovery image into the Platform tools folder
5. Type CMD to start the commands screen
6. Used the "fastboot devices" command to find my connected device
7. my device is a A/B type of device, so i typed the following command "fastboot flash boot_b recovery.img"
8. then i typed the command "fastboot reboot recovery"
up until this point it was working, then i was supposed to add the zip file into my phone so i could install it using orange fox
9. i typed "adb push "orange fox file location"/sdcard" and got the following string as an answer: adb.exe: push requires <source> and <destination> arguments
no matter how i tried to string the command i always got back this answer so i tried to manually move the zip file into the Fox folder and it allowed me to install it.
the problem is that im now stuck on recovery mode, cant leave that screen, cant even turn off my phone, i tried rebooting to fastboot, to recovery again, to system and it will always end on the recovery screen, attempted doing a factory reset but im still stuck on the recovery loop, i attempted to flash an stock rom but i was unable to do it, did i brick my phone? is there some way to solve it? would flashing a different custom recovery solve my issue?
Please any help would be appreciated.
if its of any help my device is a redmi note 10, MIUI was 12.5.5.0, global mojito, i ussed the latest version of orange fox when i attempted this