This is the first time it happens to me. I'm not an expert with cellphones, but i think this is a very weird situation.
This is the history. My cousin gave me his Moto X Play as a gift after he went to a local to repair the phone's broken display. It looked good well when i used it at the first time. But, when i tried to root that phone i have noticed a very weird issue....
The phone can't enter to a Fastboot mode when i press the buttons, and when i turn it on, it doesn't seem to have a boot logo. Im not sure about this situation, but im afraid that this phone doesn't have a boot logo, or fastboot menu.
-The phone doesn't seems to be rooted before, or have an another recovery, but i'm not sure about this.
-Everyting in the phone's system seems ok.
-The phone turns on with order (The right time and right boot), there's also the boot animation except that there's no logo.
-I have a little trouble with the phone's speaker, but, thats an another situation.
What can i do about? What do you think this is about? I can't talk with my cousin because his not living in my town, and he doesn't know about this.
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
RogerClark said:
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
Click to expand...
Click to collapse
.....
1. Yes! Pretty sure
2. Yes, the OS runs perfectly
3. I'm not sure about that, it may be
4. Nope
5. Not me, maybe another guy, but the phone doesn't seem to be rooted right now
6. Nope
Anny sugest?
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
RogerClark said:
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
Click to expand...
Click to collapse
I tried those before and nothing. Anything else you can think for me?
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
RogerClark said:
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
Click to expand...
Click to collapse
I have tried, but console says my ADB Device is Offline. What can i do? My ADB Tools are up to date
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
I'll keep that in mind, thanks a lot for those sugestions.
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
UPDATE: It seems i can access to bootloader from the computer, but screen is black when that happens. When i finaly entered to fastboot mode screen was all black and nothing happened. I noticed about this 'cause when i pushed the "+" button phone has restarted with normaly. What do you think about this?
As an extra, these messages apear when i write an ADB comand...
{
"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"
}
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
UPDATE: I've already unlocked the phone's bootloader, but can't flash the TWRP Recovery. When i try it says it was flashed sucessfuly, but, when i enter to recovery mode, it haves the stock recovery.
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
RogerClark said:
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
Click to expand...
Click to collapse
What do you refer with factory configuration? Actualy the phone are supposed to be on Stock. The phone has never unlocked by bootloader, i'm almost sure of that. So, for that reason i suppose the phone had never another rom.
Maybe i can be wrong, but. Why do you thing there are missing files?
Related
I bought a Note 3 clone. Chipset MTK 6572 1.3 GHZ MAli 400 GPU
Single Sim, Air controls, S Pen
The screen was flickering so i decided to Flash another rom. I flashed a ROM and now the phone is bricked. Only Black Screen. I am not able to access recovery either. I had created a backup of my own phone but that i am not able to flash. I get error DRAM failed : 4032. Please help me.
IF you know any rom that would work please let me know. I really need help. Phone is dead
Anybody???
please guys..help..Any ROM??? links..anything..
Guys help please
Try formatting with SP flashtool and flash the ROM again....might work!!!
Aguthadeus said:
Try formatting with SP flashtool and flash the ROM again....might work!!!
Click to expand...
Click to collapse
I have same problem with same specs (maybe:crying and have already flashed about 20 roms and have no luck (always ends with brom error enable dram fail)..
Clone note mtk 6572, ram 512, lcd 5.7"
Almost all people say we just need compatible factory rom and flashed it, but its dificult to find (
I just wonder how do chinesse manufacturer flash the rom for the first time?
Is there any tools?
poerwa said:
I have same problem with same specs (maybe:crying and have already flashed about 20 roms and have no luck (always ends with brom error enable dram fail)..
Clone note mtk 6572, ram 512, lcd 5.7"
Almost all people say we just need compatible factory rom and flashed it, but its dificult to find (
I just wonder how do chinesse manufacturer flash the rom for the first time?
Is there any tools?
Click to expand...
Click to collapse
the solution to the problem is: do a firmware upgrade first and then formats and downloads of it u want in this order, I bet it works if you have already installed drivers
Hey can you please upload the backup file to mega.co.nz? Please, I would be thankful. I have the same phone and if I manage to fix it, I'll let you all know. Thanks.
harry92008 said:
I bought a Note 3 clone. Chipset MTK 6572 1.3 GHZ MAli 400 GPU
Single Sim, Air controls, S Pen
The screen was flickering so i decided to Flash another rom. I flashed a ROM and now the phone is bricked. Only Black Screen. I am not able to access recovery either. I had created a backup of my own phone but that i am not able to flash. I get error DRAM failed : 4032. Please help me.
IF you know any rom that would work please let me know. I really need help. Phone is dead
Click to expand...
Click to collapse
upload pic ... backward sticker under battery and etc
Hi guys,
Similar to me, I got a fake S5 with the chip MTK6572.
Before to "lost" the mobile, the system or even "AnTuTu Benchamark" detected 3GB Ram and 16Gb storage. well this is not subject.
After rooting the phone, I wanted to install a CWM, then I used the ROM Manager application and another app to do the same. I could installed CWM and the TRW. I tried to reboot the phone in recovery mode and any worked. Even if the CWM installed didnt work, the phone started well.
Some minutes later when I was using the phone as usual, the mobile shutdowned, since this moment I cannot start it again.
The only thing that I can do is, to start the "recovery mode", with the button combination vol up + power + home, it just opens normally;
Select boot mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[recovery mode]
[fastboot mode]
[normal mode]
The ADB doesn't work, I tried with Win and Linux, the prompt never find the phone, even if the OS detects that there is something in the USB and I am using the MKT drivers.
I tried more than one tool through the computer (ODIN, sp_flash_tool and adb/fastboot), but no chance.
Well I hope that someone can help us, anyway if you have any recommendation/suggestion, feel free!
Thanks in advance
specs needed.
Please post specs here if you have it from mtk droid tools.. ill help as I fixed my same problem.
MT6572 stuck at "Select Boot Mode" screen...
mdabar said:
Hi guys,
Similar to me, I got a fake S5 with the chip MTK6572.
Before to "lost" the mobile, the system or even "AnTuTu Benchamark" detected 3GB Ram and 16Gb storage. well this is not subject.
After rooting the phone, I wanted to install a CWM, then I used the ROM Manager application and another app to do the same. I could installed CWM and the TRW. I tried to reboot the phone in recovery mode and any worked. Even if the CWM installed didnt work, the phone started well.
Some minutes later when I was using the phone as usual, the mobile shutdowned, since this moment I cannot start it again.
The only thing that I can do is, to start the "recovery mode", with the button combination vol up + power + home, it just opens normally;
Select boot mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[recovery mode]
[fastboot mode]
[normal mode]
The ADB doesn't work, I tried with Win and Linux, the prompt never find the phone, even if the OS detects that there is something in the USB and I am using the MKT drivers.
I tried more than one tool through the computer (ODIN, sp_flash_tool and adb/fastboot), but no chance.
Well I hope that someone can help us, anyway if you have any recommendation/suggestion, feel free!
Thanks in advance
Click to expand...
Click to collapse
FYI, I have recovered the phone
After too many tries, the phone entered in fastboot mode
1. Pull out battery and put back in
2. By holding (Volumen_UP) + (POWER)
3. Plug USB cable into PC
4. I selected: fastboot mode --> before it didnt work this option
5. Phone shows "FASTBOOT MODE"
6. With USB connection still plugged into PC, fastboot reboot-bootloader
7. After rebooting, fastboot continue
The phone started with the default bootloader and finally OS run
MTK 6572 S5 Clone/Fake details
mdabar said:
FYI, I have recovered the phone
After too many tries, the phone entered in fastboot mode
1. Pull out battery and put back in
2. By holding (Volumen_UP) + (POWER)
3. Plug USB cable into PC
4. I selected: fastboot mode --> before it didnt work this option
5. Phone shows "FASTBOOT MODE"
6. With USB connection still plugged into PC, fastboot reboot-bootloader
7. After rebooting, fastboot continue
The phone started with the default bootloader and finally OS run
Click to expand...
Click to collapse
Hi guys,
After recover the phone, I have taken some screenshots with the phone details (using AnTuTu Benchmark). Also I have done a copy of the original ROM (default) for the future.
https://onedrive.live.com/redir?resid=12502AC16380536C!5396&authkey=!ADNAKVaxQ7EWciI&ithint=folder%2c
{
"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"
}
In one of the picture, the storage capacity should be wrong, The "System Storage" total and available.
I guess that the real storage of this phone is:
RAM 3GBSystem Storage 1GBInternal Storage 1.27 GB
Well I don't know what information is true about this phone, and neither how I can figure out the real information.
Do you think that is a good idea to install another ROM over the phone? How can I find a compatible ROM?
Thanks in advance
flash stock backup using SP flash tool
Hi,
I search the recovery.img of Oukitel K10.
I have make OEM Unlock, and I can get fastboot.
I have find many fake websites to hot to do this, but realy don't trust (last time I have brick my K10000 Pro).
The better way is now to "fastboot boot test.img" and see if my phone boot before flash anything.
But I dont find a recvery.img who boot my phone
I have the "fake" ROM (I search inside, and it's seem match as mine)
The other problem is SP flash tools don't want to get me my NVRAM ...
Anyone have root is K10 ? (I have a brick until my device is not root, I don't use it in stock ROM !)
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
So, what did you use to root it?
Yea can u tell us how you did it atep by step. My flashlight its not working andi cant hear a thing on Bluetooth... Need to root this.. or someone else knows how to fix it?
I actually found a step-by-step guide here:
https://www.getdroidtips.com/twrp-recovery-oukitel-k10/
But, i got stuck at downloading the image over my phone,.... i never get green light after flashing....
The phone functions normal, after... because nothing flashed i guess...
And that guide is incomplete, you need to first disable digitally signed drivers check, otherwise the preloader won't work at all...
Did anyone else try it?
What do you guys get?
Mind to share your knowledge? How you obtain your Oukitel K10 rooted cleaned?
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
sergey1369 said:
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
Click to expand...
Click to collapse
I am not able to get to bootloader how to do that? voldown and power button does nothing but restarting phone everytime.
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
sergey1369 said:
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
Click to expand...
Click to collapse
I did turn off the phone then pressed power button and volume down button at a time then kept pressing it till logo came. as soon as I release them .. Phone just get started, instead of going to bootloader
Can anyone share recovery img file? I cant find anywhere.
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
sergey1369 said:
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
Click to expand...
Click to collapse
Thanks a lot for reply .. yes it gives me recovery propmpt
Have you got K10 Recovery? Cant find anywhere. The one link given here. Takes me to other website which need to paid membership and I tried to pay but Cant pay via paypal and developer inbox is full so cant contact him too.
Oh, that's weird, it was free. Here is a copy
Anyone know how install cleaned rom?
I keep getting bootloops as soon as I try to flash Magisk. I have no trouble flashing and starting up TWRP, but after flashing I can´t reboot to system. I also get the warning from my Pc when I connect my phone that it doesn´t recognize it. It reboots fine if I don´t flash anything. Any help? I also tried the steps on page 1 (Bootloader is successfully unlocked).
SuperSu works, but fails Safety Net, that´s why I want Magisk.
k10 ROOT
Hello Friend,
I have a K10 but I have not been able to do the ROOT, can you help me ??
What is the procedure?
FukTheRegister said:
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
Click to expand...
Click to collapse
Hey there and sorry for the late response. What steps did you do so far? Is your bootloader unlocked already? Or are you at the start and this is your first try? If it is your first try, here is a step by step guide on what to do and what you will need.
What you need:
1. The SP Flash Tool and its drivers. You can find them on the Oukitel website or in the internet. Search for SP Flash Tool and download the latest. For the drivers it´s best to get them from Oukitel. Lower right side of their website and then click Latest software Rom and choose the K10.
2. The adb and fastboot drivers. Search them on the internet.
3. Your Smartphone.
4. A computer and the data cable.
5. The SuperSU 2.82 S3 files from chainfire. Again, search them on the internet.
6. The TWRP Image from this thread.
If you have everything, you do the following:
1. If you have used your phone already, safe everything you want to keep on your computer! You will have to erase your data at least once in the process!
2. Turn your phone on and go to settings.
3. Then tap on About your phone and scroll all the way down to see its build number.
4. Tap on that 7 times in a row to get the message: Congratulations you are now a developer. Go back to the settings to see a new option, the developer options.
5. Go to the developer options and tap on allow oem unlock and also tap on enable debugging options.
6. Leave the settings and connect your phone to your computer. Push the SuperSU file to your sd card (Magisk unfortunately does not seem to work and results in a bootloop at least for me).
7. On your computer, go to the folder where you saved the adb.exe and fastboot.exe. Hold shift and open a power shell or command window in there (don´t actually know the steps for a Mac or Linux computer, sry).
8. Now type adb devices and confirm the access on your phone. If your phone doesn´t show up or there is no confirmation message on your phone, type adb kill-server and then adb devices.
9. Once your phone is confirmed, you type adb reboot-bootloader.
10. Now type fastboot oem unlock and press the volume up button on your phone to confirm the bootloader unlock.
11. Your phone will now erase your data (internal storage only, your sd card will not be touched, but may need to be set up and formatted again if it was used to extend the internal storage).
12. On your computer, type fastboot reboot and set up your phone again (just the basics, because you will have to erase it again). Don´t forget to turn on the debugging mode again.
13. Open up the SP Flash Tool on your computer and choose the scatter file from the twrp image (custom recovery). Only recovery should be ticked. Hit the download all button, connect your phone to computer and turn off the phone. Now wait till there is a green hook on your computer. This means, the download has been successfull.
14. Get to recovery mode on your phone by holding the volume up and power button at the same time and choose the first option, then hit the volume down button to enter recovery mode.
15. From here, go to the settings in the upper right corner and choose your language (ignore the message of the password and hit back).
16. Now go to Wipe and format your data.
17. Hit the restart button and press Recovery. Allow it to modify the system and pull the slider.
18. Now go to Install, choose your sd card and press SuperSU. Let it run through the process. Then restart and press system. First time the boot may take a while, so be patient.
19. Set up the phone and enjoy your root.
Magisk 17.1
Magisk 17.1 install AS IS, no warranty, no testing (yet).
!!! You can lose your data or brick your phone !!!
0. Don't try default install or upgrade via MagiskManager - you'll get bootloop.
1. You can try this boot-magisk.img (AIK repacked with force encryption and dm-verity enabled).
It works for me, but I did factory reset before trying.
- boot.img comes from OUKITEL_K10_V12_20180112.rar (I'm not sure about file's source)
fastboot flash boot boot-magisk.img
2. If your phone freeze on Oukitel logo, don't touch it. Wait.
If you stop phone here, you'll lose your data.
There is no way back - it starts data encryption.
3. If it fails, try flashing stock boot back and factory reset your phone.
fastboot flash boot boot.img
That modified boot.img did the trick. What did you modify to make it work?
The forced encryption, however, is annoying. Is there a possibility to undo that?
help ... Oukitel K10
I flash firmware Oukitel K10 by SP_MDT_v3.1828 (Format and Download All). now : looked picture(red font). Phone call ok. please help me. I from Vietnam. Thankyou!
{
"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"
}
Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you
i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.
unparalleled82 said:
i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.
Click to expand...
Click to collapse
Hi Unparalleled82,
So i think i was actually using "adb reboot bootloader " instead of the app at times so ive just tried it using the app however it still doesnt come up as a fastboot device. When i put in the command " fastboot flashing unlocked " i just get " waiting for any device " for ever.
Few things im wondering do you have exacly the same phone as me RealmeGT 5G rmx2202_11_A.25. Its good to know you have done it and the way you did it. Because mines not working the same way ( assuming the models are the same ) im thinking now its a driver issue perhaps .
So when im just doing adb sideload or something when the phone is booted into the OS i dont have the yellow triangles however in this fastboot mode i see 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"
}
Which does indicated a driver issue however when i try to manually install the correct drivers windows tells me its already has the best driver. ( im browsing to the folder where ive downloaded the drivers here )
Ive tried installing them through the legacy hardware option which does install them but phone still doesnt show up in fastboot devices.
Ive also installed the driver using android studios ... you can see google usb drivers ticked.
Ive also googled how to stop windows from automatically installing drivers from windows update then uninstalled my device .. plugged it back in ... then installed them. However thinking now perhaps i should uninstall ... then install the drivers before plugging in the phone ? any ideas ?
Some more info this has reminded me of. Ive tried a different usb cable, a different usb port ( both usb 2.0 ) and a different computer already.
As for the powershell I'm certain i'm using it not the cmd line. I'm holding shift in the correct folder then right click, then open the power shell window.
Any more help would be amazing. Im going to have a look more into fastboot driver problems
I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices
unparalleled82 said:
I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices
Click to expand...
Click to collapse
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.
Piefrag said:
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.
Click to expand...
Click to collapse
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for a better cable
unparalleled82 said:
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for
Click to expand...
Click to collapse
Ahh got you now. So ive tried the cable sent with the phone and now 2 other cables and all of them have the same issue so im thinking its not the cable atm.
Ive seen on youtube a method for rooting it from anotehr phone.... i have no idea if it works but ive bought a usb c too usb c cable to give it a try at least !
Thinking now i may buy another usb A too usb C cable of good quality too make absolute sure its not the cable messing it up.
Piefrag said:
Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you
Click to expand...
Click to collapse
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem
grown_man said:
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem
Click to expand...
Click to collapse
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.
Piefrag said:
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.
Click to expand...
Click to collapse
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers
grown_man said:
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers
Click to expand...
Click to collapse
Thats it ! Thank you so much
My phone is completely messed up right now. All I did was flash spark os (A12) over PPUI (A11) and then my phone didn't boot. I flashed that ROM via fastboot flash tool. I think it was the tool which caused this problem. After so many tries, my phone booted but wifi, sound and many other functions aren't working. Then I tried flashing some other ROM but TWRP/Ofox kept giving some "error 7". Then I tried flashing fastboot ROM with 3 versions of Mi flashtool but it keeps giving some kind of CRC flash error. Please help me I'm too much worried right now.
if you flash through fastboot tool do you see any error (if yes then tell us more about the error )if not and rom starts with some issues try flashing the latest firmware
muneeb rizwan said:
if you flash through fastboot tool do you see any error (if yes then tell us more about the error )if not and rom starts with some issues try flashing the latest firmware
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm getting this error continously
move it to c:\
muneeb rizwan said:
move it to c:\
Click to expand...
Click to collapse
now my phone screen has gone black and it won't turn on. Computer still detects it as I'm hearing some sound
I was flashing fastboot ROM using mi flashtool and it gave me error. When I tried to turn on the phone, it didn't turn on. However, when I connect it to PC, the PC makes some sound. What do I do now?
boot your phone into fastboot mode and then connect it to pc and install this rom
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip/download
extract the zip file and you will see a file (install for first time) open it and if all goes well it will flash the rom
muneeb rizwan said:
boot your phone into fastboot mode and then connect it to pc and install this rom
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip/download
extract the zip file and you will see a file (install for first time) open it and if all goes well it will flash the rom
Click to expand...
Click to collapse
I can't even boot into fastboot mode. Screen stays black no matter what key combo I try
The following steps should put your phone into fastboot.
1) Phone off
2) Connect the USB cable to the computer (not the phone for now)
3) Hold the volume down button only
4) Still hold and connect the USB cable to the phone
Now the telefo should start fastboot mode.
StaryMuz said:
The following steps should put your phone into fastboot.
1) Phone off
2) Connect the USB cable to the computer (not the phone for now)
3) Hold the volume down button only
4) Still hold and connect the USB cable to the phone
Now the telefo should start fastboot mode.
Click to expand...
Click to collapse
Didn't work. I guess EDL mode is my last hope now.
Starting EDL mode can be a problem. At present, perhaps EDL cables no longer work and if the phone does not allow you to enter the EDL by key combinations, the only test points left are on the phone's motherboard. With test points, the question is whether the correct points have already been found. The manufacturer does not inform about them.
What driver is loaded in Windows when the phone is connected?
So the test points are already known:
It works by disconnecting the battery to completely shut down the hardware. Conductively connect the test points (tweezers, scissors) and with the points connected, connect the USB cable plugged into the PC. This activates the EDL mode (sometimes only very briefly). You need to have MiFlash running beforehand and use "refresh" and "Flash" right away. If nothing happens, probably the EDL mode has already been switched off again.
For flash in EDL mode you can normally use MiFlash with ROM for fastboot.
If the Qualcomm HS-USB QDLoader 9008 Windows driver is loaded, this is the EDL mode.
StaryMuz said:
For flash in EDL mode you can normally use MiFlash with ROM for fastboot.
If the Qualcomm HS-USB QDLoader 9008 Windows driver is loaded, this is the EDL mode.
Click to expand...
Click to collapse
I wonder how did my phone boot into edl mode although I never opened its back cover.
And right now the problem is that Mi Flashtool is showing some edl authentication error. How do I resolve that?
First, it is very important to call things by their correct name, otherwise misunderstandings and mistakes in procedure can arise. What do you mean "Mi Flahtool"?
You should have used this:
https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
I think the flashtool version of 2017 works without any problem, coz, recently I unbricked my Poco x2 with this version of flashtool. The latest versions of flashtools are getting errors. And move the flash files to C: partition mandatory
StaryMuz said:
First, it is very important to call things by their correct name, otherwise misunderstandings and mistakes in procedure can arise. What do you mean "Mi Flahtool"?
You should have used this:
https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
Click to expand...
Click to collapse
That's exactly what I used. I even tried the latest version but still no luck.
Shibu Shaji said:
I think the flashtool version of 2017 works without any problem, coz, recently I unbricked my Poco x2 with this version of flashtool. The latest versions of flashtools are getting errors. And move the flash files to C: partition mandatory
Click to expand...
Click to collapse
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
Bro, connect to a VPN , change the language of auth window and bind your mi account details there. And give it a try on tool version 2017.4.25... If nothing works go for edl.
munimjaffer said:
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
View attachment 5504363
Click to expand...
Click to collapse
munimjaffer said:
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
View attachment 5504363
Click to expand...
Click to collapse
Bro, use the same version of flash tool that I mentioned above.. 2017.4.25 with flash all command.
Hello all, I've been trying to install /e/ os GSI on my Redmi Note 11S. I already unlocked the bootloader.
Whenever i tried flashing system.img, (with boot.img patched manually via fastboot, not via a custom recovery), the phone would only boot fastboot. So I tried installing this custom recovery, and patch boot.img from there, but that still wouldn't work (though the recovery at least worked). So I tried installing the stock ROM, and try something else.
I went with latest fastboot EEA image and ran flash_all.sh (worked last time I tried), but this time I got an error (something about partition preloader not found). So I restarted the phone after which it got stuck in this bootloop. Can't boot into fastboot, nor recovery. Instead, the phone keeps flashing the mi logo on and off every 5 seconds. fastboot on my Linux install can't detect the phone. My Windows 10 install can't find it either, though it plays the "device connected" sound followed by the "device disconnected" sound shortly after. I can't turn the phone off either. Windows 10 USB drivers worked, or at least when I was unlocking the bootloader, so I don't think the issue is there. Any idea how to fix this?
Thank you in advance
Edit: Typos. Also I noticed that it only plays the "device connected" and "disconnected" sounds on Windows 10 only when i hold down the power and vol- buttons.
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
{
"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"
}
UPDATE: Managed to get FASTBOOT back, thanks to this kind stranger (system is still unbootable).
UPDATE: IT'S ALIVE! Did a quick install_all.sh on the stock ROM, and it's working again! Thank you all for helping me resolve this problem
no idea
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
warhead1721972 said:
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
Click to expand...
Click to collapse
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
kritomas said:
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
Click to expand...
Click to collapse
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
warhead1721972 said:
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
Click to expand...
Click to collapse
Yes, that's the one, and it won't go into fastboot.
Isn't /e/ Murena GSI just android 10? I am pretty sure it won't work. I had the same problem, but I fixed it by installing stock ROM..
And that /e/ GSI is not actively developed and not even in beta stage (not usable at most cases)
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
soutaminori said:
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
Click to expand...
Click to collapse
Thank you so much, it worked!!!
I think. It's now at least on the FASTBOOT screen, which is progress. And the MIUI recovery is now back as well. While the system is still unbootable, I think I can take it from here. Thank you
Hypeka said:
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
Click to expand...
Click to collapse
That's the first thing I tried, and no luck. But I fixed it now (I think).
Very welcome, Glad to hear that
Note for everyone:
Backup this partition it's very important.
nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img, protect2.img, md1img.img
Thats all partition about imei, security and network configuration for ur device. CMIW.
mtkclient also can do that,
and it's the clue:
Code:
python mtk r nvcfg,nvdata,nvram,persist,proinfo,protect1,protect2,md1img nvcfg.img,nvdata.img,nvram.img,persist.img,proinfo.img,protect1.img,protect2.img,md1img.img
Check ur mtk client folder, now you got the back up.
u can also use this Partitions Backup & Restore this tool don,t need PC for backup and restore, but i'm not really sure can be work perfectly. i just try for boot partition and its worked.
cheeerrss
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
i can't see mtk client log. but maybe driver problem or try to unlock BL again with THIS TOOL
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
I myself did it with the terminal and on Linux. I didn't use the GUI, so I can't help with that. Could you send a higher res picture of the terminal please? We can't really see anything.
If you're doing this on Windows, then my guess is a driver issue (I did have to install a special driver for Windows to work with Fastboot, could be that mtk needs it too).
Hi All,
I unbricked my phone by using fresh release of mtkclient (https://github.com/bkerler/mtkclient).