Hello, I will show you the method that I use to unbrick my nubia red magic 3s, also works for 3
and this is the message that we will find:
1-we occupy having a USB of at least 4 gb, and OTG USB
2-have the ADB drivers installed and fastboot I recommend V1.3 https://forum.xda-developers.com/showthread.php?t=2588979
3-first you have to put the device in fastboot mode, this is achieved by having the phone completely turned off,
turn on and at the same time press the volume down key, with this we will be in fastboot mode
4-download the file recovery.img this is the factory recovery I will leave 2 versions one for the filmware of the 3s and the other for the 3 and copy it to the adb folder
Recovery 3s V114 Nort America:
http://www.mediafire.com/file/17kxwkxzz4yjiis/recovery.img/file
Recovery 3 V118 Nort America rename the file to recovery.img before going to the adb folder:
http://www.mediafire.com/file/u3n1kumg0m4f6wk/3recovery.img/file
5-download the filmware that corresponds to your device https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
6-connect the device to the computer and open a cmd window inside the adb folder
and we execute the following commands:
"fastboot devices" omit the quotes
"fastboot oem nubia_unlock NUBIA_NX629J"
"fastboot flash recovery recovery.img"
7-You can now disconnect your device from the computer, now copy the filmware that I previously downloaded to the root of the USB, now connect the USB to the device using the OTG USB
with the volume up / down buttons navigate to the option to restart in recovery mode
8-within recovery choose the language and proceed to install the filmware through disk
9-on the first reboot your device might get stuck in boot logo, but don't despair if this happens hold down the shutdown button until the device turns off completely, now turn it on and hold down the volume down button to enter fastboot mode again, browse again and reboot the device in recovery mode
10-inside recovery make factory reset and reboot, finally it will have come out of brick:good:. and you can use this guide to customize your device:
https://forum.xda-developers.com/red-magic-3/themes/dark-theme-navigation-gestures-global-t4080157
This was the solution I found, I hope it will serve you very much
Something strange happen to my red magic 3s , practically every 7 months i should buy one cable because charge less (mA) so the first time i did buy the phone with the (normal default charger) + the (Quick charger 3.0 with the usb type-c cable for spare) , this this Quick charger cable did work for 7 month because afther did start with the less charger like 200 (mA), so i did buy another usb type-c cable and did work , so 15 day ago this cable did start again with less charger, so i did buy another cable and in this while i did use the (default charger cable) and strange thing did happen , the default charger that was new did charger good like 3.000 mA for 1 day , the next day did start to charger less, and this is impossible because i did use this charger cable just 6 day , because this charger was for spare and i did use just when i waited shipment of the package for the other cable , so today i did get the new cable , i did try and charger less mA i dont believe really , so i did try all the charger with the new cable but same problem less mA, so i remembered had the adpater universal rampow that charger to 1a 2a for phone and tablet and i did use for years with my old iphone and android device , so i did put the new cable to port 2a and the magic thing happen again , charger less (mA) like every one , but afther 10 sec the screen block and the phone reboot ,when did reboot work fine but if i put to charger will get blocked screen and reboot , so i say "omg i can t charger more if will block and reboot while charger " so i did try to reset the phone , i download the roms Europe & Asia: V212 on the root folder and install local, when did get 100% this did happen "Device is corrupt. It can't be trusted and will not boot" so i did think omg what going on , practically if you put one charger or one cable not original will brick your phone , but the problem is if i put the cable on windows for install a new roms , windows will not detected the new hardware so i can t use adb or another thing, and i want remember that this default cable it new i did use like 6 day ,so now I'm thinking what can i do for unbrick the phone and afther discovery the problem about the less mA .
cacaocaca said:
Something strange happen to my red magic 3s , practically every 7 months i should buy one cable because charge less (mA) so the first time i did buy the phone with the (normal default charger) + the (Quick charger 3.0 with the usb type-c cable for spare) , this this Quick charger cable did work for 7 month because afther did start with the less charger like 200 (mA), so i did buy another usb type-c cable and did work , so 15 day ago this cable did start again with less charger, so i did buy another cable and in this while i did use the (default charger cable) and strange thing did happen , the default charger that was new did charger good like 3.000 mA for 1 day , the next day did start to charger less, and this is impossible because i did use this charger cable just 6 day , because this charger was for spare and i did use just when i waited shipment of the package for the other cable , so today i did get the new cable , i did try and charger less mA i dont believe really , so i did try all the charger with the new cable but same problem less mA, so i remembered had the adpater universal rampow that charger to 1a 2a for phone and tablet and i did use for years with my old iphone and android device , so i did put the new cable to port 2a and the magic thing happen again , charger less (mA) like every one , but afther 10 sec the screen block and the phone reboot ,when did reboot work fine but if i put to charger will get blocked screen and reboot , so i say "omg i can t charger more if will block and reboot while charger " so i did try to reset the phone , i download the roms Europe & Asia: V212 on the root folder and install local, when did get 100% this did happen "Device is corrupt. It can't be trusted and will not boot" so i did think omg what going on , practically if you put one charger or one cable not original will brick your phone , but the problem is if i put the cable on windows for install a new roms , windows will not detected the new hardware so i can t use adb or another thing, and i want remember that this default cable it new i did use like 6 day ,so now I'm thinking what can i do for unbrick the phone and afther discovery the problem about the less mA .
Click to expand...
Click to collapse
First of all unbrick your device via unbrick tool by edl mode if you can after that try to tranfer to cn rom and try again your experiments i think. Because cn rom has more AI features instead of global.
And someone please help me plss
First of all my phone is unlocked,
I can use adb, my phone work smothly with every version of rom, the problem is my device can't recognised in fastboot. Not in win 7/win 10 and also afrer turn the driver signatures off it can't.
Device manager act like nothing connected to pc when it is in fastboot mode, i also try cn rom ,unbrick via local update to asia , unbrick via edl mode to asia etc... So if anybidy can help please tell me, i am gettting tired by searching for solution.
RoseRahman said:
First of all unbrick your device via unbrick tool by edl mode if you can after that try to tranfer to cn rom and try again your experiments i think. Because cn rom has more AI features instead of global.
Click to expand...
Click to collapse
how can i transfer if windows dont want detect the phone and i did install all the driver
cacaocaca said:
how can i transfer if windows dont want detect the phone and i did install all the driver
Click to expand...
Click to collapse
Try to enter in 9008 mode
i did but windows doesn t detect nothing
cacaocaca said:
i did but windows doesn t detect nothing
Click to expand...
Click to collapse
Then it should be hardbrick and i think the QDL ports are need to be sort in the motherboard to unbrick it, i think try service centre is the best way now.
I did talk with service center already I wait
cacaocaca said:
I did talk with service center already I wait
Click to expand...
Click to collapse
Wait untill they reply but i think they will say motherboard failure which i think not possible, but if they successfully unbrick it then it will be a good news for you.
Motherboard failure or not them will fix it and the phone it still in warranty , I from Italy and the warranty from europe it 2 years, has passed 1 years and 2 months still, I don’t know still if I should to tell to them that I did use another charge when did happen that , but the charge I think it not the real problem , because I did use this charge with my old iPhone 6s to 2 ampere , and the red magic support also the charge to 3 ampere so I don’t think it the the problem , maybe them have some script where if I use another charger will happen that.
cacaocaca said:
Motherboard failure or not them will fix it and the phone it still in warranty , I from Italy and the warranty from europe it 2 years, has passed 1 years and 2 months still, I don’t know still if I should to tell to them that I did use another charge when did happen that , but the charge I think it not the real problem , because I did use this charge with my old iPhone 6s to 2 ampere , and the red magic support also the charge to 3 ampere so I don’t think it the the problem , maybe them have some script where if I use another charger will happen that.
Click to expand...
Click to collapse
Which Room you used?
lilo_ind said:
Which Room you used?
Click to expand...
Click to collapse
The official roms eu 212
What if may device is lock? It will unlock may device or end up hardbrick may device because its lock? Or working on unlock and lock device? May rm3s is lock and not root. Im scared please help me
mojako09 said:
What if may device is lock? It will unlock may device or end up hardbrick may device because its lock? Or working on unlock and lock device? May rm3s is lock and not root. Im scared please help me
Click to expand...
Click to collapse
Unlock for permission to root, if you want to lock without brick u must wipe cache data system then flash your rom then reboot to recovery then install rom again
pablo2005 said:
Hello, I will show you the method that I use to unbrick my nubia red magic 3s, also works for 3
and this is the message that we will find:
1-we occupy having a USB of at least 4 gb, and OTG USB
2-have the ADB drivers installed and fastboot I recommend V1.3 https://forum.xda-developers.com/showthread.php?t=2588979
3-first you have to put the device in fastboot mode, this is achieved by having the phone completely turned off,
turn on and at the same time press the volume down key, with this we will be in fastboot mode
4-download the file recovery.img this is the factory recovery I will leave 2 versions one for the filmware of the 3s and the other for the 3 and copy it to the adb folder
Recovery 3s V114 Nort America:
http://www.mediafire.com/file/17kxwkxzz4yjiis/recovery.img/file
Recovery 3 V118 Nort America rename the file to recovery.img before going to the adb folder:
http://www.mediafire.com/file/u3n1kumg0m4f6wk/3recovery.img/file
5-download the filmware that corresponds to your device https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
6-connect the device to the computer and open a cmd window inside the adb folder
and we execute the following commands:
"fastboot devices" omit the quotes
"fastboot oem nubia_unlock NUBIA_NX629J"
"fastboot flash recovery recovery.img"
7-You can now disconnect your device from the computer, now copy the filmware that I previously downloaded to the root of the USB, now connect the USB to the device using the OTG USB
with the volume up / down buttons navigate to the option to restart in recovery mode
8-within recovery choose the language and proceed to install the filmware through disk
9-on the first reboot your device might get stuck in boot logo, but don't despair if this happens hold down the shutdown button until the device turns off completely, now turn it on and hold down the volume down button to enter fastboot mode again, browse again and reboot the device in recovery mode
10-inside recovery make factory reset and reboot, finally it will have come out of brick:good:. and you can use this guide to customize your device:
https://forum.xda-developers.com/red-magic-3/themes/dark-theme-navigation-gestures-global-t4080157
This was the solution I found, I hope it will serve you very much
Click to expand...
Click to collapse
Can i do this using a macbook? And if im successful with the unbrick can i install global rom even tho cn rom was the original rom of my phone?
RoseRahman said:
And someone please help me plss
First of all my phone is unlocked,
I can use adb, my phone work smothly with every version of rom, the problem is my device can't recognised in fastboot. Not in win 7/win 10 and also afrer turn the driver signatures off it can't.
Device manager act like nothing connected to pc when it is in fastboot mode, i also try cn rom ,unbrick via local update to asia , unbrick via edl mode to asia etc... So if anybidy can help please tell me, i am gettting tired by searching for solution.
Click to expand...
Click to collapse
facing the same damn problem phone is not getting detected in fastboot mode everywhere else it works now iam stuck in global rom without root
pablo2005 said:
Hello, I will show you the method that I use to unbrick my nubia red magic 3s, also works for 3
and this is the message that we will find:
1-we occupy having a USB of at least 4 gb, and OTG USB
2-have the ADB drivers installed and fastboot I recommend V1.3 https://forum.xda-developers.com/showthread.php?t=2588979
3-first you have to put the device in fastboot mode, this is achieved by having the phone completely turned off,
turn on and at the same time press the volume down key, with this we will be in fastboot mode
4-download the file recovery.img this is the factory recovery I will leave 2 versions one for the filmware of the 3s and the other for the 3 and copy it to the adb folder
Recovery 3s V114 Nort America:
http://www.mediafire.com/file/17kxwkxzz4yjiis/recovery.img/file
Recovery 3 V118 Nort America rename the file to recovery.img before going to the adb folder:
http://www.mediafire.com/file/u3n1kumg0m4f6wk/3recovery.img/file
5-download the filmware that corresponds to your device https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
6-connect the device to the computer and open a cmd window inside the adb folder
and we execute the following commands:
"fastboot devices" omit the quotes
"fastboot oem nubia_unlock NUBIA_NX629J"
"fastboot flash recovery recovery.img"
7-You can now disconnect your device from the computer, now copy the filmware that I previously downloaded to the root of the USB, now connect the USB to the device using the OTG USB
with the volume up / down buttons navigate to the option to restart in recovery mode
8-within recovery choose the language and proceed to install the filmware through disk
9-on the first reboot your device might get stuck in boot logo, but don't despair if this happens hold down the shutdown button until the device turns off completely, now turn it on and hold down the volume down button to enter fastboot mode again, browse again and reboot the device in recovery mode
10-inside recovery make factory reset and reboot, finally it will have come out of brick:good:. and you can use this guide to customize your device:
https://forum.xda-developers.com/red-magic-3/themes/dark-theme-navigation-gestures-global-t4080157
This was the solution I found, I hope it will serve you very much
Click to expand...
Click to collapse
dude thanks a lot you saved my phone. the best alternative for the unbrick tool(EU)
Related
After installing cyanogenmod 10 nightly with cwm my battery began to act weird - it showed 0% charge and the phone turned off as soon as i plugged the charger off. I've read that this can be caused by CWM and that i have to install Amon Ra recovery in order to fix it. However, i wasn't able to enter fastboot mode, so i've decided to write the img directly using from adb shell
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/amonrarecovery.img
reboot recovery
(yes, now i understand that it is dumb, but i wanted to do it faster, without reading all tutorials).
it gave me the error that it cannot write there.
after that the phone won't turn on or enter recovery/download/fastboot mode. the only signs of life - omap 4430 usb device blinking in the device manager(i've installed the required drivers).
as far as i understand - if i'll be able to enter fastboot mode - i'll be able to flash normal bootloader back and install any rom.
But there's no LGE CDMA usb serial port showing in device manager, no matter what pc, cable or key combination(volume up, volume up+power, etc) i use. - it was the same even before i've erased bootloader.
besides when i use wkpark's omap4boot - i get error 121 on the second stage responce (i've tried the EMU version - still no luck)
seems that using OMAPflash is my only option now, but i can't seem to find examples of it's usage. One guy on this forum said that he revived p920 by dumping the firmware from a working p920 and then flashing it back on his device starting from 0000 memory address. maybe someone could upload his or stock firmware obtained this way?
i've tried using LG mobile support tool but it seems not to be able to detect the device (tried holding vol up)
maybe you guys can advice me something else?
PS this is a NOT FOR SALE device, if that changes something
thanks in advance.
Tried to install AmonRa recovery on my phone. No change, still no charging.
Sent from my LG-P920 using xda premium
alexisrozkov said:
After installing cyanogenmod 10 nightly with cwm my battery began to act weird - it showed 0% charge and the phone turned off as soon as i plugged the charger off. I've read that this can be caused by CWM and that i have to install Amon Ra recovery in order to fix it. However, i wasn't able to enter fastboot mode, so i've decided to write the img directly using from adb shell
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/amonrarecovery.img
reboot recovery
(yes, now i understand that it is dumb, but i wanted to do it faster, without reading all tutorials).
it gave me the error that it cannot write there.
after that the phone won't turn on or enter recovery/download/fastboot mode. the only signs of life - omap 4430 usb device blinking in the device manager(i've installed the required drivers).
as far as i understand - if i'll be able to enter fastboot mode - i'll be able to flash normal bootloader back and install any rom.
But there's no LGE CDMA usb serial port showing in device manager, no matter what pc, cable or key combination(volume up, volume up+power, etc) i use. - it was the same even before i've erased bootloader.
besides when i use wkpark's omap4boot - i get error 121 on the second stage responce (i've tried the EMU version - still no luck)
seems that using OMAPflash is my only option now, but i can't seem to find examples of it's usage. One guy on this forum said that he revived p920 by dumping the firmware from a working p920 and then flashing it back on his device starting from 0000 memory address. maybe someone could upload his or stock firmware obtained this way?
i've tried using LG mobile support tool but it seems not to be able to detect the device (tried holding vol up)
maybe you guys can advice me something else?
PS this is a NOT FOR SALE device, if that changes something
thanks in advance.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=44532338&nocache=1
Make sure you did this
If the LG COSMO appears in device manager install driver for her by select update driver then select browse my computer for driver {install driver Manual} and select Install driver from "inside folder have drivers"(omap4boot-for_optimus-v1.22 modified by XcachorroX®\usb_drv_windows) then try again step 2 flash fastboot
i resurrected lg p920 not for sale con omap4boot 1.25 option emu
http://www.youtube.com/watch?v=dHZ_RJCyrxk&feature=youtu.be
Praise be he did it. And I wholeheartedly and apologize for my frustration.
Since Xiaomi and Micro$oft released a public ROM of Windows 10 Mobile for Mi4, the curiosity drives me to try it. But I felt so uncomfortable after successfully installed win10 on my mi4.
So I decided go back to Android roms. But sh*t happened - my mi4 got bricked during the flashing.
Phone won't boot with black screen and no boot options. Holding any buttons (including power button + volume down more than 2 minutes) won't work.
The pc can not recognize a USB device after it is plugged in (in both Windows XP and Windows 8.1).
Then I plug it into my Mac OS X with a VirtualBox of Windows 7 OS inside.
The USB devices shows a unknown device of id 05C6:F006.
I did a lot of googling of 05c6:f006 which seems to be 05c6:9008 and something Qualcomm related.
And the most important thing is to make my computer to recognize it.
So things I need to figure out:
Is my phone hardware damaged or software damaged (hard bricked or soft bricked)?
Do I need to disassemble it?
How can I make my pc to recognize it ?
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
My phone was recognized as a USB input device, VID_05C6&PID_F006, seems to be Qualcomm_QHSUSB 9008 related
I have exacly the same probleme here, do you have find any solution ?
If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works
xiaomi mi4 lte not turn on
darkmaster566 said:
If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works
Click to expand...
Click to collapse
Good evening. I have a problem with my Xiaomi 4 lte, after trying to return from 6 to android 4.4 android after this tutorial : ]Now the phone does not start, if you stick to connect to PC loaded or red LED flashes once and the computer sounds like something I plugged in but not afiseaja nimicc device. He is charged for 24 hours and not start and MIFLASH program is not found
Mi4w hard brick
darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
Hey! I had bymistakely flashed wrong partition and tried flash in miii 6.3.3 ROM....
Now my device is bricked....Whenever i connect to charger the red light blinks....And when connected to pc....The red light comes.....But no drivers come on my pc...Means its to recognising.....Can you help me please????
Hello to everybody.
I have a problem with my mate8.
After flash rom on TWRP phone will not boot. Only a black screen (phone off), no logo, no bootloop. Twrp recovery does not run, eRecovery not run.
Phone does not react to any combination of volume + - and power. After connecting to the PC is still in fastboot mode. Even with the battery disconnected.
Rayglobe knife or SRKtool performs unbrick but the phone will not boot, it is still only in fastboot. TWRP or eRecovery installs, but will not boot.
Fastboot commands some works, adb commands says "device not found " , "waiting for device" or remote: command not allowed.
It is possible to install UPDATE.APP via fastboot?
Bootloader is unlocked and FRP locked. I can not turn on USB debugging.
Is there any way to recover your phone, or is totally dead?
Helps DC Phoenix?
Thanks for any ideas.
EDIT: Solved. Using DC Phoenix, unbrick and phone works again.
How??? My phone is dead also l29 c158
I CAN GET TO FAST BOOT.....FLASHED ALLTHAT T I CAN BUT NO RESULT....I PURCHASED CREDITS ON DC PHOENIX BUT TILL NOW NO RESULT AS IT CANT RECOGNIZE MY PHONE...
My phone was still in fastboot mode, so it was easier.
I followed instructions (Huawei Mate S flashing in fastboot by DC Phoenix on YouTube) .
My version is NXT-L29 C432.
I downloaded the official firmware C432 B320 and DC Phoenix performed a flash.
It was then a little problem with the battery, but unplugging, turning on the phone without the battery and then reconnect the battery managed to turn the phone on. Then I flash the firmware update.app in stock recovery and the phone is alive.
Spent 15 euros, but better than brick.
I would try to support dc phoenix. It might help.
Thank you...After trying to flash new firmware by DC phoenix.....My phone is completely dead.....NO power working....I think I must search for a new phone....anyway .......just I advise everyone to be careful when rooting Nougat.....
When connecting a charger flashes red, or does not respond at all?
premda said:
When connecting a charger flashes red, or does not respond at all?
Click to expand...
Click to collapse
NO response at all....no repose to charging or PC at all...
basimzanaty said:
NO response at all....no repose to charging or PC at all...
Click to expand...
Click to collapse
Windows Device Manager does not detect the attached device?
He is probably dead :crying:
My mate 8 NXT -L29 is completely dead.I updated to noughat B563 and i found out my Bluetooth was not working completely,then i tried to downgrade it to B500 ,the update got 99% and then phone got switched off.No waking up no matter what.I tried the hard reset too with all combinations of voume and power button but no response.BUt when i connect my phone to PC Huawei suite opens up but cannot access. I removed the battery and then inserted it , still no life.Please give me a solution.
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
I corrupted my phone's root/system/etc files and when I restarted it, it wouldn't turn on and got stuck on the realme logo. i hold my phone vol+ and - and power key and when the realme logo comes up, i release the power key, i think download mode opens, but it usb device is faulty for 1-2 seconds and disappears immediately, meanwhile in device manager it shows unknown device for 1-2 seconds and disappears. After 10-15 seconds there is a usb connection sound but nothing happens. I can send adb commands but I have to confirm the confirmation window but I cant.
Please help me, how can I fix it?
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Renate said:
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Click to expand...
Click to collapse
Yes, I get the unauthorized message as below. If I can somehow authorize it, I will be able to enter fastboot mode and flash the stock rom.
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Okay, I'm trying
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
mvikrant97 said:
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
Click to expand...
Click to collapse
I updated with Driver Booster, no luck.
I only tried the front USB ports, do I need the back ones? There are 2 2.0 and 1 3.0 port on the front
The computer is new so I don't think it's defective, the phone is charging and I was using it before it went brick.
I also modified the boot file to install a new GSI and used the following guide.
Spoiler
First, you need to unlock fastbootd:
1. Download the stock ROM version 91: Download and extract the .pac file Link
2. Install the SPD research tool and drivers: GDrive
3. Open it
4. Click on the single gear icon
5. Select the .pac file of the stock rom
6. Wait until it loads
7. Click on the two gear icon
8. Find BOOT in the list
9. Right-click on the path next to it
10. Download here and select boot_r1.img
11. Click OK and then click the arrow icon
12. Turn off your phone
13. Press and hold Power + VolumeDown until you see the text "Downloading"
14. Release the buttons after seeing
15. Wait until you see the text "Passed"
16. Click on the Stop icon, disconnect your phone and turn it on
[/ISPOILER]
@leanord Can you help me?
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Renate said:
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Click to expand...
Click to collapse
I don't fully understand your question, but I have the stock recovery, I didn't install TWRP, and I installed dotOS 5.2 as GSI. I think I corrupted the fastboot, download mode boot files in the root files. I will take it to the service center, but if you have a solution, you can write, I don't want to give money.
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Renate said:
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Click to expand...
Click to collapse
It may have been disabled or because I corrupted system files.
Wanted? I came, to flash the phone, you do not need to press anything except the volume keys, the power button is only a catalyst, you need to hold it down until the screen goes out, and then just Keep the volume - and flash as usual, the main thing is to keep it immediately plugged into the PC with a ready-made flasher
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Luuukie said:
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Click to expand...
Click to collapse
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
leanord said:
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
Click to expand...
Click to collapse
SP Flash Tool doesn't see my device so I can't flash it. If you mean Fastboot, I can't get into it.
By the way, that font that's showing up in my UsbLog is UGLY.
I readjusted things, you can download a new copy that is prettier.
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Renate said:
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Click to expand...
Click to collapse
I'm sorry, I don't know that much. But if you tell me the steps how to do it, I can do it.
@leanord when installing GSI, I flashed boot_r1.img from your Realme C21Y GSI installation guide, did you disable fastboot or something?