i am facing problem for unlocking bootloader, so i just thought IF i could install Twrp via EDL mode ??
is this will work if i replace the TWRP.img file with orignal stock "recovery.img" from the "Fastboot ROM" by extracting the Fastboot ROM of my device, and then flash via Mi Flash tool ?
will the recovery be flashed ???
Yes, it´ll work, just flash nougat miui to prevent other stuffs and reboot inmediately to twrp, flash Magisk, format data and it´s needed anti-bootloop (I´m not sure if it does) through twrp, don´t forget to enable USB debugging and OEM unlock just in case.
SubwayChamp said:
Yes, it´ll work, just flash nougat miui to prevent other stuffs and reboot inmediately to twrp, flash Magisk, format data and it´s needed anti-bootloop (I´m not sure if it does) through twrp, don´t forget to enable USB debugging and OEM unlock just in case.
Click to expand...
Click to collapse
Sorry for bringing this old post back.
I tried to replace the original "recover.img" file with TWRP 3.2.3 and flash the Fastboot ROM. However, when I reboot to TWRP (immediately) it shows "The system has been destroyed". If I boot the phone normally it will setup the Mi-Recovery instead.
Any solution for it?
Nobuemon said:
Sorry for bringing this old post back.
I tried to replace the original "recover.img" file with TWRP 3.2.3 and flash the Fastboot ROM. However, when I reboot to TWRP (immediately) it shows "The system has been destroyed". If I boot the phone normally it will setup the Mi-Recovery instead.
Any solution for it?
Click to expand...
Click to collapse
Are you trying to flash TWRP through EDL mode with locked bootloader? if yes this method actually don´t work cause bootloader in newer versions prevents any change to the system. It worked time ago and I did it in other device like Mi Max but now is not possible.
SubwayChamp said:
Are you trying to flash TWRP through EDL mode with locked bootloader? if yes this method actually don´t work cause bootloader in newer versions prevents any change to the system. It worked time ago and I did it in other device like Mi Max but now is not possible.
Click to expand...
Click to collapse
I see. So is there any other workaround way rather than waiting till my unlock request is approved?
Nobuemon said:
I see. So is there any other workaround way rather than waiting till my unlock request is approved?
Click to expand...
Click to collapse
I didn´t find any method working actually in all the net maybe due to newer policies from Xiaomi that don´t accept any modification to the system and refuses to boot.
I´m waiting my second month, they gave me first 720 hours and after that they extended the time to others 720 hours again.
I found a method and flashed in other older Xiaomi devices to install TWRP or a boot rooted through EDL but actually this doesn´t work (system has been destroyed) so I think that maybe is possible to install a bootloader unlocked or eventually a persist partition of an unlocked device; I suspect that the info is allocated in persist partition and requested in the other thread to some user can backup them and upload to try this method but unfortunately no one wants to help (just a guy with other device RN5), I have other ideas to do it but as stated is a weak community.
mohsiin4u said:
i am facing problem for unlocking bootloader, so i just thought IF i could install Twrp via EDL mode ??
is this will work if i replace the TWRP.img file with orignal stock "recovery.img" from the "Fastboot ROM" by extracting the Fastboot ROM of my device, and then flash via Mi Flash tool ?
will the recovery be flashed ???
Click to expand...
Click to collapse
It will not work either your recovery will be replaced by stick recovery every time you boot or phone just failed to boot into anything at all other than bootloader, the very first requirement for twrp is unlocked bootloader that's there for a reason ?
Finally here is solution for this problem now There Is No Need to apply for permission to unlock bootloader
you may find more information here
https://en.miui.com/thread-2932736-1-1.html
mohsiin4u said:
Finally here is solution for this problem now There Is No Need to apply for permission to unlock bootloader
you may find more information here
https://en.miui.com/thread-2932736-1-1.html
Click to expand...
Click to collapse
This thread is from June, there´s nothing new here; since months ago there´s no need to apply to unlock, unlock is done automatically without requesting any reason but after...........720 hours and some users has to wait after that others 720 hours.
Hello.
So only way to unlock bootloader is to wait XXX hours, right? I still need to wait 1 month before unlock.
And after you execute MiUnlock is unlock forever event if you change ROMS?
Thanks in advance.
dark_vader said:
Hello.
So only way to unlock bootloader is to wait XXX hours, right? I still need to wait 1 month before unlock.
And after you execute MiUnlock is unlock forever event if you change ROMS?
Thanks in advance.
Click to expand...
Click to collapse
By now the only way is waiting the time that Xiaomi whims, also ended the time it could be extended without any apparently reason.
Users don´t mention a firmware that can relock devices like happened time ago in other devices, just be careful that if you use MiFlash Tool the option "Flash_all_and_relock" is unchecked.
SubwayChamp said:
...Users don´t mention a firmware that can relock devices like happened time ago in other devices, just be careful that if you use MiFlash Tool the option "Flash_all_and_relock" is unchecked.
Click to expand...
Click to collapse
Better still, just delete "flash_all_lock.bat" and "flash_all_lock.sh" forever. This would ensure that, if you ever forget to uncheck the mentioned box, the flash tool will still never be able to find the script that it needs to do the dastardly deed.
DarthJabba9 said:
Better still, just delete "flash_all_lock.bat" and "flash_all_lock.sh" forever. This would ensure that, if you ever forget to uncheck the mentioned box, the flash tool will still never be able to find the script that it needs to do the dastardly deed.
Click to expand...
Click to collapse
Thx, yes, it´s a way to do it, "fastboot oem lock" it´s at the end of "flash_all_lock.bat" file; in my case I´m very careful when flash some device but for distracted users could work, dificult here will be that if they don´t pay attention flashing less would take precautions before.
SubwayChamp said:
Thx, yes, it´s a way to do it, "fastboot oem lock" it´s at the end of "flash_all_lock.bat" file; in my case I´m very careful when flash some device but for distracted users could work, dificult here will be that if they don´t pay attention flashing less would take precautions before.
Click to expand...
Click to collapse
Absolutely correct! Nothing beats always paying full attention when about to flash anything. But we all know that this often doesn't happen
SubwayChamp said:
This thread is from June, there´s nothing new here; since months ago there´s no need to apply to unlock, unlock is done automatically without requesting any reason but after...........720 hours and some users has to wait after that others 720 hours.
Click to expand...
Click to collapse
same here..
i got same error like wait for 720 hours...
any solution ???
dark_vader said:
Hello.
So only way to unlock bootloader is to wait XXX hours, right? I still need to wait 1 month before unlock.
And after you execute MiUnlock is unlock forever event if you change ROMS?
Thanks in advance.
Click to expand...
Click to collapse
yes u need not to unlock again once u unlock the device
Hello, I know this is irrelevant post but may be u can help me. I have a xiaomi mi5 device. I buy this phone from offline market as second hand used phone.
--- --- --- --- ---
Because of i'm new to xiaomi device so i am unaware of mi account issues so after buy this devuce wants to unlock bootloader but using mi unlock tool it cause error like "Your device is locked with 197****85 and can't be unlock".after searching on net i come to know this device's IMEI associated with other person phone number mi account which is a great problem i dont know who is he. in recovery account mi.com only show his number like +9230******67. i don't know how to reach the owner number. Without reaching to owner seems impossible to unlock. any solution from any senior/junior developer or member.
bot88 said:
Cela ne fonctionnera pas non plus, votre récupération sera remplacée par une récupération par clé à chaque fois que vous démarrez ou que le téléphone ne parvient pas à démarrer sur autre chose que le chargeur de démarrage, la toute première exigence pour twrp est le chargeur de démarrage déverrouillé qui est là pour une raison ?
Click to expand...
Click to collapse
Bonjour j'espère que je ne suis pas là trop tard ce thread date de 2018 enfin voici mon problème je vous demanderai d'utiliser en traducteur pour mon message car traduire le message sur Google traduction le rend incompréhensible . Enfin pour venir à mon problème j'ai un bootloader déverrouillé est j'ai flashé twrp problème j'ai flashé une mauvaise rom est des lors que j'ai fait un reboot recovery l'écran devient noir cl incompréhensible de plus quand j'essaye de démarré mon téléphone en recovery ou fastboot je ne vois rien l'écran est toujours noir je me demande même si le téléphone fonctionne correctement en recovery et un fastboot dès lors que je démarre dans les deux mode mon téléphone est sensé vibré comme quoi il démarre belle est bien mais rien je vois le port Qualcomm 9008 (10) activé je me doute donc que je viens de le brick je suppose qu'il est un mode EDL auriez vous une solution je suis bloqué ?
Miui 13 said:
Bonjour j'espère que je ne suis pas là trop tard ce thread date de 2018 enfin voici mon problème je vous demanderai d'utiliser en traducteur pour mon message car traduire le message sur Google traduction le rend incompréhensible . Enfin pour venir à mon problème j'ai un bootloader déverrouillé est j'ai flashé twrp problème j'ai flashé une mauvaise rom est des lors que j'ai fait un reboot recovery l'écran devient noir cl incompréhensible de plus quand j'essaye de démarré mon téléphone en recovery ou fastboot je ne vois rien l'écran est toujours noir je me demande même si le téléphone fonctionne correctement en recovery et un fastboot dès lors que je démarre dans les deux mode mon téléphone est sensé vibré comme quoi il démarre belle est bien mais rien je vois le port Qualcomm 9008 (10) activé je me doute donc que je viens de le brick je suppose qu'il est un mode EDL auriez vous une solution je suis bloqué ?
Click to expand...
Click to collapse
English is required here. Google Translate (and I think the others too) works very fine, and your message is very comprehensible.
If you managed to enter to EDL mode then you should flash the stock ROM using Mi Flash tool, use the option that in the bottom to do a Clean flash, no need to re-lock bootloader in case you don't want it.
SubwayChamp said:
L'anglais est requis ici. Google Translate (et je pense que les autres aussi) fonctionne très bien, et votre message est très compréhensible.
Si vous avez réussi à passer en mode EDL, vous devez flasher la ROM d'origine à l'aide de l'outil Mi Flash, utilisez l'option en bas pour faire un flash propre, pas besoin de verrouiller à nouveau le chargeur de démarrage au cas où vous ne le voudriez pas.
Click to expand...
Click to collapse
in reality I do not know if I am in edl maiq mode each time I try to start in fastboot or in recovery the screen remains black when I go to my task manager I see: Qualcomm HS-USB QDLoader 9008 (COM10) escque cella means that it is an edl mode because it would not be able to start normally? if so how do you think that I can succeed in unlocking it
Related
Hello, here I have a motorola atrix in gingerbread 2.3.4 Roote with peter's Root Tools.
I found it very slow since few months and I decided to make a factory reset. For this I go in confidentiality - "restore the factory setting". The phone restarts and display "failed to boot 2. Boot is rsd mode".
I removed the battery and resart the phone, he start normally, like before.
I have then turn off the phone, then i start the phone pressing volume - and power, I go in "android recovery", but the same message appeared.
I removed the battery and I restart the phone, the phone start lke before, usually.
So I want to know how to restore my phone to factory settings and erasing all data.
thank you for your help, and soory for the spelling mistakes, because i'm french.
french version
bonjour, voilà j'ai un motorola atrix sous gingerbread 2.3.4, rooté avec peter's Root Tools.
Je le trouvais très lent depuis quelques mois et j'ai décidé de le remettre au valeur d'usine. Pour cela j'ai été dans confidentialité - restauration au valeur d'usine. Le téléphone a rédémarré et à afficher "failed to boot 2. boot on rsd mode".
J'ai enlevé puis remis la batterie et le téléphone s'est allumé normalement quand avant.
Je l'ait alors éteint puis rallumé en appuyant sur volume- et power, j'ai été dans "android recovery", mais le meme message s'est affiché.
J'ai enlevé la batterie puis je l'ait remis, le téléphone s'est correctement allumé comme d'habitude.
Je cherche donc à savoir comment faire pour remettre mon téléphone aux valeurs d'usine et en effacant toutes les données.
Looks like you have a damaged recovery. You cannot do a factory reset "the normal way" without a working recovery.
Since you're rooted, you could try the following procedure from your computer. Untested but should work.
You only type the stuff in bold. Make sure you type the commands exactly as shown.
Code:
[color=grey]>[/color] [b]adb shell[/b]
[color=grey]$[/color] [b]su[/b]
[color=grey]#[/color] [b]toolbox stop[/b]
[color=grey]#[/color] [b]rm -rf /data/*[/b]
[color=grey]#[/color] [b]rm -rf /cache/*[/b]
[color=grey]#[/color] [b]toolbox reboot[/b]
can you explan please ?
Where i do write this code ?
On my computer with the atrix on usb ?
thanks
Command line on your computer, with the Atrix connected via USB.
You need the Android SDK installed (for adb) as well as working drivers for the Atrix (available from the Moto website).
what the utilities of the software android sdk ?
I unrooted my phone since the last message, i must root the atrix before make this operation ?
This is getting too complicated. Since you want to do a factory reset and your phone switches to RSD mode anyway, you should just use RSDlite and flash a stock SBF.
You still need working Atrix drivers though.
what rsd lite ?
How flash a stock sbf ? What is this ?
The bootloader of my atrix is lock. this is a problem no ? I must unlock the bootloader ?
You don't need an unlocked bootloader.
For more information about RSD and SBF please see other threads, this has been discussed countless times. Or simply search on Google.
Hi Guys,
A friend of mine bought a Le Max 2 and he got it with a custom ROM based on the Indian version of 015s.
He has Installed the Couco Recovery V3 and now he has blue led of death. So only blue led and he has fastboot mode, but he can't enter to the installed recovery. We tried the Teamspain 5.8 recovery, the Couco recovery's, but no success.
Please help, how to revive his phone!
Thanks in advance!
Bonjour A tous !
J'ai eu le même problème lors d'une tentative de flash de la rom est j'ai galéré 7 heures pour trouver la solution !
Lorsque le fastboot est opérationnel il faut procéder ainsi :
1 Erase de recovery
2 installer un nouveau recovery.img de twrp ( ex :fastboot flash recovery twrp.img)
3 lancer la commande magique sans quoi rien y fait ex: fastboot boot twrp.img
Attention lorsque je faisait la manip avec un hard reboot cela ne fonctionnait pas !!!!!
Étant un ancien possesseur d'un téléphone mediatek vla la frustration d'avoir du galérer pendant 7h mais quel bonheur de retrouver mon letv après cette panique je ne l'avais pas depuis 24h lol
Pour info dans la procédure de cuoco92 j'avais oublié de copier la rom sur le téléphone mais quel tête en l'air je suis par moment !
Flash recovery from TeamSpain.
[FRANCAIS] J'ai eu le meme probleme
1 - Install le Recovery de TeamSpain via FASTBOOT (fastboot flash recovery recovery.img)
2 - Reboot en mode recovery
3 - connecte ton telephone au PC
4 - Copie une ROM dans ton telephone
5 - Flash la ROM
6 - Reboot
[ENGLISH] I had the same problem
1 - Install the TeamSpain's Recovery via FASTBOOT (fastboot flash recovery recovery.img)
2 - Reboot into recovery mode
3 - connect your phone to the PC
4 - Copy a ROM in your phone
5 - Flash ROM
6 - Reboot
tibcsi0407 said:
Hi Guys,
A friend of mine bought a Le Max 2 and he got it with a custom ROM based on the Indian version of 015s.
He has Installed the Couco Recovery V3 and now he has blue led of death. So only blue led and he has fastboot mode, but he can't enter to the installed recovery. We tried the Teamspain 5.8 recovery, the Couco recovery's, but no success.
Please help, how to revive his phone!
Thanks in advance!
Click to expand...
Click to collapse
try update official rom,you phone will be save.
Hi,
I'm running android 7.1.2.
After the last android update, my touchscreen don't respond after the wake up.
The only thing to do is to reboot the phone. Touchscreen is ok till the next sleeping...
Any advice to fix that trouble ?
Thank you for your help.
Same here
Same here after the 7.1.2 TOS 3191 update.
Touchscreen stops responding at arbitrary times. Mostly when in sleep, but sometimes also while working on it.
A reboot does not help. After some time being off it might just works again.
After rebooting into safe mode it still does not respond to the touchscreen, so I am pretty sure it is not a downloaded app that causes the problem.
gerben2001 said:
Same here after the 7.1.2 TOS 3191 update.
Touchscreen stops responding at arbitrary times. Mostly when in sleep, but sometimes also while working on it.
A reboot does not help. After some time being off it might just works again.
After rebooting into safe mode it still does not respond to the touchscreen, so I am pretty sure it is not a downloaded app that causes the problem.
Click to expand...
Click to collapse
I didn't find the solution. The only thing I've done is changing the screen months ago. It was working fine before the update.
I will try to downgrade and avoid the update, it should work.
j'ai le meme probleme que vous , avez vous reussi a resoudre votre probleme ?
si oui pouvez vous me decrire comment vous avez fait ?
merci
bubu3333 said:
j'ai le meme probleme que vous , avez vous reussi a resoudre votre probleme ?
si oui pouvez vous me decrire comment vous avez fait ?
merci
Click to expand...
Click to collapse
Bonjour, non toujours pas, je ne me suis pas encore lancé dans la réinstallation d'android sans la dernière mise à jour.
Je cherche un tuto simple car je dois le faire faire à distance.
Je vais regarder aujourd'hui.
bricoleout said:
Bonjour, non toujours pas, je ne me suis pas encore lancé dans la réinstallation d'android sans la dernière mise à jour.
Je cherche un tuto simple car je dois le faire faire à distance.
Je vais regarder aujourd'hui.
Click to expand...
Click to collapse
ok moi de mon coté j'y suis depuis 2 jours et je n'ai pas trouvé le moyen de rooté root ce telephone ... si vous avez une idéé avec un tuto , je suis preneur !!
merci
bubu3333 said:
ok moi de mon coté j'y suis depuis 2 jours et je n'ai pas trouvé le moyen de rooté root ce telephone ... si vous avez une idéé avec un tuto , je suis preneur !!
merci
Click to expand...
Click to collapse
Je vais flasher la version android 7.1.1 en suivant ce qui est dit ici : https://forum.xda-developers.com/swift-2/help/wileyfox-2-corrupted-update-to-android-t3628224
Ça devrait fonctionner.
"Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/sho....php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swi...tboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
"
bricoleout said:
Je vais flasher la version android 7.1.1 en suivant ce qui est dit ici : https://forum.xda-developers.com/swift-2/help/wileyfox-2-corrupted-update-to-android-t3628224
Ça devrait fonctionner.
"Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/sho....php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swi...tboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
"
Click to expand...
Click to collapse
impeccable ça marche !!! je me suis aider de cette video
avec le fastboot image https://forum.xda-developers.com/swi...tboot-t3605101
encore merci
bubu3333 said:
impeccable ça marche !!! je me suis aider de cette video
avec le fastboot image https://forum.xda-developers.com/swi...tboot-t3605101
encore merci
Click to expand...
Click to collapse
Salut, tes liens ne fonctionnent pas, peux tu les re-poster (plus particulièrement la vidéo, ça m'intéresse).
Can you please translate the text for me. My father has the same issue and not sure (don't understand) if the suggested fix will work.
bubu3333 said:
impeccable ça marche !!! je me suis aider de cette video
avec le fastboot image https://forum.xda-developers.com/swi...tboot-t3605101
encore merci
Click to expand...
Click to collapse
majo_scigo said:
Can you please translate the text for me. My father has the same issue and not sure (don't understand) if the suggested fix will work.
Click to expand...
Click to collapse
I adviced the guy bubu3333 to downgrade to Android 7.1.1. He said it works now.
I didn't try it because I don't have the phone near me for now (my brother's one).
So try to downgrade your android. Maybe try to updae it again to see if it works ? Or stauw with 7.1.1.
You can follow this :
"You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/sho....php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swi...tboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!"
As described here https://forum.xda-developers.com/swift-2/help/wileyfox-2-corrupted-update-to-android-t3628224
thank you for translation..shame the fastboot image is not there anymore
majo_scigo said:
thank you for translation..shame the fastboot image is not there anymore
Click to expand...
Click to collapse
The fastboot image is still available. It's just the copy/paste link who doesn't work well (i d'ont know why).
https://forum.xda-developers.com/sw...oid-7-1-1-tos118c-fastboot-t3605101?nocache=1
Or Try directly here https://wileyfox.wetransfer.com/downloads/2f0ad86084a45812325a373d94d59e6420170510131221/4faeca
Hi, i just bought this phone last week on Amazon (France) when i received it i immediatly started the process to unlock the device, because i knew that i had to wait for a week (wich i did). Why would i root my phone ? Well because i always install Adaway on my phones, and also because in France it is not legal to record call, so i wanted an idonesian or chinese rom to have that function wich is not included in global roms.
So this evening, i unlocked the device with miflash unlock tool, flashed the twrp that was avalaible (apparently the only one, made for note 9s, but that can work with pro version).
I transfered thoses files to my phone:
miui_JOYEUSEIDGlobal_V11.0.3.0.QJZIDXM_e5c9822122_10.0.zip
miui_JOYEUSEIDGlobal_V11.0.2.0.QJZIDXM_1f0c38d0fc_10.0.zip
miui_CRUX_V12.0.3.0.QFXCNXM_5ece229616_10.0.zip (this one i wasn't sure because it was a chinese rom, and i don't think it was official, but i wanted to try miui12)
And i got an error 7 that said that i have a CURTANAIN device, and can't flash JOYEUSE roms, my bad, i didn't know that, so i downloaded this one : miui_CURTANAINGlobal_V11.0.8.0.QJWINXM_fe48f22bf8_10.0.zip
Of course i started by wiping my data, cache, cache/dalvik, and ended with a factory reset.
I flashed the last rom, and then before reboot the phone, installed Magisk 20.4.
No error, no nothing BUT, after the process, the phone rebooted and shut down instantly.
So i tried to reboot it by pressing Power + Volume Down for a LONG TIME, but nothing, same for Power + Volume Up and Power + Volume Down+ Volume Up. The phone just won't boot
Also when i plug it to my pc, it just bootloop, i can see the Redmi logo for not even 2secs, and shut down immediatly, same if i just charge it..
Amazon will give me a refund if i send it back, they just send me the return process, but i want to try everything i can before that.
Also, if you think that i rather just send it, i will order the same phone again, but still want it rooted, so what can i do to avoid the same problem ?
The only test point solution and an authorized edl account. Or send it to amazon to get it fixed or reimbursed.
Okay, i've rather just send it back to Amazon then.
So, if i order the same device, what should i do to be sure to flash the apropriate twrp and rom ?
Salut ,
Renvoie a Amazon ce sera plus sûre. Je pense qu'une tu lui a injecté une mauvaise rom ce qui l'a brické...
Tu avais quelles spécifications pour ton tel? Car je me pose aussi la question entre Curtana et Joyeuse. Le mien possède un capteur arrière de 64 M pixels en global rom et 4/64 en Ram.
J'attends aussi le délai pour deverouiller mon bootloader.
__________________
Hello, I think youn'd better send it back to amazon because you brick it flashing a bad rom.
What are the specifications of your phone ? I have the same and it is not easy to say if it is a Curtana or a Joyeuse. My phone is a Global version with 64 M pixel camera an 4/64 Ram.
I am also waiting to unlock my bootloader.
Bye
Envoyé de mon Redmi Note 6 Pro en utilisant Tapatalk
ck32 said:
Salut ,
Renvoie a Amazon ce sera plus sûre. Je pense qu'une tu lui a injecté une mauvaise rom ce qui l'a brické...
Tu avais quelles spécifications pour ton tel? Car je me pose aussi la question entre Curtana et Joyeuse. Le mien possède un capteur arrière de 64 M pixels en global rom et 4/64 en Ram.
J'attends aussi le délai pour deverouiller mon bootloader.
__________________
Hello, I think youn'd better send it back to amazon because you brick it flashing a bad rom.
What are the specifications of your phone ? I have the same and it is not easy to say if it is a Curtana or a Joyeuse. My phone is a Global version with 64 M pixel camera an 4/64 Ram.
I am also waiting to unlock my bootloader.
Bye
Envoyé de mon Redmi Note 6 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
Salut, yes c'est ce que j'ai fait du coup, j'ai été remboursé hier, donc je viens tout juste de commander le même modèle. c'est la version Global 64mp et 6gb ram/64gb .
Après honnêtement j'ai pas vraiment fait gaffe pour ce qui est de la version, si c'est une Curtana ou Joyeuse, j'ai juste pris le premier TWRP que j'ai trouvé, et les roms dispos sur le net. Le problème c'est qu'il y a rien qui indique quelle rom est compatible avec quel modèle :/
__________________
Hi, yes that's what i did, i was reimbursed yesterday, so i just ordered the same model. It's the Global version 64mp 6gb ram/64gb .
And honestly, I didn't really pay attention to the version, if it's a Curtana or Joyeuse, I just took the first TWRP i found, and the roms available on the internet. The problem is that there is nothing to indicate which rom is compatible with which model: /
Hi there, today i try to root my one plus 7t pro on adroid 10.
It works great with only magisk i make a fastboot by this app to have a root acces.
I also use TWRP just for backup because when i try to flash with it i have some error failed. I see some post i'm not alone with this device...
I've try to install LineageOS but i don't be very excited about this custom room. I'm begginner in root and install custo rom or kernel.
I'm happy about stock version root but i have the wifi don't work and it really annoying...
Also i have a hub usb-c for use controller to make a private cloud gaming. It works great but my device don't accept to use controller while charging. When i charging in power delivery usb-c the controller is desactivated.
If someone can help me to resolve my problems i will be very happy.
Thanks and sorry for my bad english i hope you will be understand me.
I don't know about the controller, but as for you not having wifi. This is because you are using a patched boot omg that is from a different firmware than your firmware. Please use google and search how to patch your boot img from your firmware in magisk
toolhas4degrees said:
Je ne sais pas pour le contrôleur, mais quant au fait que vous n'avez pas de wifi. Cela est dû au fait que vous utilisez un omg de démarrage patché qui provient d'un micrologiciel différent de celui de votre micrologiciel. Veuillez utiliser google et rechercher comment patcher votre img de démarrage à partir de votre firmware dans magisk
Click to expand...
Click to collapse
thanks it work for WIFI i try it now and WIFI is okay