Related
Le smartphone SPV M1000 alias Qtek 2020 sous PocketPC 2003 Phone Edition est équipé de la technologie Bluetooth. Cette technologie utilise un pilote qui permet de la faire fonctionner, malheureusement sur ces smartphones, c'est la pile Microsoft qui a été choisie. La pile Bluetooth de Microsoft est très basic d'un point de vue fonctionnel mais également très instable avec certains périphériques à l'image de certaines oreillettes ou GPS Bluetooth.
Les meilleurs drivers Bluetooth toutes plateformes confondues sont ceux proposés par la société WidComm, celle-ci équipe notamment les PocketPC HP IPAQ et souffre de très peu de problème de compatibilité. Ces fameux drivers sont maintenant disponibles pour le SPV M1000/Qtek 2020 et corrige de nombreux bugs comparé à la pile Bluetooth de Microsoft mais apporte également de nombreuses fonctionnalités à l'image de l'accès réseau via Bluetooth...
********************
Sur un autre forum un gars du nom de JRC a posté un truc super pour aider encore plus voici ce qu'il dit :
Marche terrible plus qu'a trouver le moyen de virer les restes de l'ancienne pile BT de Microsoft car maintenant j'ai deux icones BT sur la page Aujourd'hui !
****
un autre gars réponds à cette question par : Il faut supprimer la clé \HKLM\Services\BTIcon
Et JRC de répondre à ceci :
Salut, j'ai fait un petit CAB qui installera la pile BT de WidComm avec en plus :
- suppression de l'icone Bluetooth de l'ancienne pile dans les paramètres.
- modification des textes présents en allemand vers de l'anglais !
http://perso.wanadoo.fr/smartease/Stack_Bluetooth.cab
Merci a JRC.
que ceux et celles qui l'ont essayé nous donnent leur avis ici même
Merci d'avance
Is this a new version that Do work also with Bluetooth headset or just an easier version to install ??
C'est une nouvelle version qui fonctionne avec les oreillettes bluetooth ou juste une version plus plus simple a installer ?
A++
FL
try and see by yourself. And post over here what you see and if that work for you.
That's a so great answer ..
Thanks a lot, now I know what this forum has been made for !!
this the best I can do
Fred Lemas said:
That's a so great answer ..
Thanks a lot, now I know what this forum has been made for !!
Click to expand...
Click to collapse
This is the best answer I can do so fare.
Why don't you try it ? If it goes bad you can allways do a Hard Reset and comeback online with a backup. It won't hurt.
And then comeback here and tell us what you see and what you feel.
Can you do that?
PS: If I have more info, let me tell you, I will post it here ASAP. So fare I don't. For some people it's working (depend always on there BT devices and brand) for some others it's not working. What else can I say ??
It's allways best to try and see if it feet your needs.
I hope that answer make you feel better.
PS Again: with 4 posts in 5 months you can't critisize much. Involve yourself a little more and things will goes better I guess.
Hi. I've just installed it on my spvm1000 with the 1.72wwe imate rom :
- the bluetooth file transfert work
- i was not able to create a network connection (maybe i don't know how ?)
- i setup an activesync connection with the widcomm but i can't make an activesync synchronisation.
- don't try the bluetooth header cause I haven't got one.
JRC, if you are here can you help an old smartphony user ?
Does anyone know if the Widcomm stack supports handsfree profile?
Because for me this is the major lack of the Bluetooth stack in XDAII....
Re: this the best I can do
bruxelles5 said:
Why don't you try it ? If it goes bad you can allways do a Hard Reset and comeback online with a backup. It won't hurt.
Click to expand...
Click to collapse
Thanks a lot for this advice, but if I was in a position of doing this today I wouldn't have asked ! In fact I do not have this week the 4 hours that my device current setup needs to come back to work from a hard reset, so that's why I posted in this forum, just in case of someone what around there for any help or good mood talking...
bruxelles5 said:
PS: If I have more info, let me tell you, I will post it here ASAP. So fare I don't.
Click to expand...
Click to collapse
So in fact your previous answer whas simply a joke meaning "I don't know" ... ok got it now... Belgium to French to English translations should have altered the thinking....
bruxelles5 said:
For some people it's working (depend always on there BT devices and brand) for some others it's not working.
Click to expand...
Click to collapse
That could be an interesting point because we have conducted many experimentations here with many build of the Widcom stack on the Qtek and none as ever showed a way to have audio routed to ANY bluetooth device. So if you hace examples of device that seems to have worked .. just let us know...
bruxelles5 said:
PS Again: with 4 posts in 5 months you can critize much. Involve yourself a little moore and things will goes better I guess.
Click to expand...
Click to collapse
Never be sure to know what and who you are talking to, you don't know me or my different nicknames and what I'm doing in this PDA area...But if you really think that the capabilities are directly linked to the number of post in this kind of forum that is nice of you...
Re: this the best I can do
Fred Lemas said:
Thanks a lot for this advice, but if I was in a position of doing this today I wouldn't have asked ! In fact I do not have this week the 4 hours that my device current setup needs to come back to work from a hard reset, so that's why I posted in this forum, just in case of someone what around there for any help or good mood talking...
Click to expand...
Click to collapse
Why don't you use a program called "Backup PLus" or "Sprite Backup" from http://www.spritesoftware.com/products/products.html
You can allways backup in your SD card, all your settings, programs etc... and you can restore everything in less than 3 minutes (usually 1.5 min )
I used to reinstall all programs and settings one by one, until I found this Sprite Backup.
Maybe you can look at this first, before you decide to try the BT update.
So long
BT Headset works!
It works!! Hurray!
Re: this the best I can do
bruxelles5 said:
Why don't you use a program called "Backup PLus" or "Sprite Backup" from http://www.spritesoftware.com/products/products.html
Click to expand...
Click to collapse
Thanks, I know those and have already used them, but right now we are in custom software evaluations and we can't mix the setup with other software ...
Re: BT Headset works!
NeoCole said:
It works!! Hurray!
Click to expand...
Click to collapse
can you give more informations ?
what brand, what profile, does it give you auto-answer ?
Thanks
A BRUXELLES5 :
Marche nickel
Merci pour tes bons soins
Salut
for me it doesn't work
it is really great installer but I still get those "insufitient driver memory" errors
anyway, really nice job
p.s.
je reve d'une possibilite a utiliser ce widcomm stack sur mon xda
Re: this the best I can do
Fred Lemas said:
So in fact your previous answer whas simply a joke meaning "I don't know" ... ok got it now... Belgium to French to English translations should have altered the thinking....
Click to expand...
Click to collapse
I allways remember what people say about French (don't forget I'm French also) "they think they are the center of the world and they think they know everything"
I have this kind a complain anytime since I'm in Belgium.
Actually there is a Joke over here in Belgium (I will write it in French it's more fun)
Savez vous pourquoi les autoroutes ne sont pas éclairées en France?? Parce que les Francais se prennent pour des lumieres
A mediter
Be a little more "COOL" look at other posts, they all say "thank you" or "don't work but thanks anyway" etc.............
Forum are here to help as much as they can, people post what they see, what the think is maybe good..............and other people try, post reply, suggestion, BUT NEVER COMPLAIN.
**********
Voici un post trouvé sur un autre forum a propos du stack BT et du CAB :
Pour moi le cab fonctionne très bien mais pour cela il faut supprimer pas mal de référence à la stack BT de Microsoft. Malheureusement un fichier CAB n'est pas capable de supprimer une clé dans la base de registre donc ce cab est du bricolage faudrait faire un truc propre avec un exe qui supprime les anciennes références. Je pense que je vais me lancer lorsqu'on aura une pile BT WidComm pour PocketPC Phone Edition car celle-ci n'est malheureusement destiné qu'aux PocketPC d'où de nombreux problèmes avec les oreillettes.
Et le gars de conclure :
PS : Je ne participe pas trop sur xda dev car je trouve l'ambiance surtout francophone très mauvaise....
Comme quoi, il va falloir faire un effort messieurs les Francophones.
So long brother
i-mate 1.72
I have no idea what half of you are talking about (lets all post in our native language) but I tried this Widcomm BT stack and could not get the audio streaming to the BT headset (nokia HS-3W) to work even though it switched off the MP audio and said that it was connected to the headset.
Playing around with the settings frooze the PDA. When resetting the device it went completely dead, even hard-reset was not working (which I never experienced before). After I removed the battery for some time it finally started again with a fresh install of WM2003.
Was this BT-stack expected to be compatible with the i-mate 1.72? (I see only HP references at Widcomm) If so I will try again. I really want the audio/voice over the BT headset for TT navigation.
Anyway thanx for the post.
Ronald
Re: this the best I can do
same thing here (insuffecint memory driver )
any help will be greatfull
how can i active the original BT in the tray bar ?
Insuficient Drivers Memory pb... the solution I found...
Insuficient Drivers Memory pb... the solution I found...
Simply deactivate the MS BT. When you install the widcomm stack you don't remove the MS one.
SO go to the Bluetooth parameters in the panel control "Parameters" UNcheck everthings and clic start, deactivate the MSBluetooth.
Reset the PDA and it should work.
Best regards,
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
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
English
Hello, I have a big problem.
I wanted install LineageOS on my Samsung Galxy S3 LTE with TWRP.
And I don't know how, but my internal memory partition was removing.
I don't know how remake this partitions...
I maked an backup of Android 4.0, but when I start the backup, he says "Invalid partition"
Please Help, me
FRANCAIS:
Bonjour, j'ai un très grand problème.
J'ai voulu installer LineageOS sur mon Galaxy S3 avec TWRP.
Et je ne sais comment, les partitions de la mémoire interne ont disparu.
Je ne sais pas comment recréer des partitions.
J'ai crée une sauvegarde Android 4.0 du téléphone, mais lors de la récupération, il me dit qu'il n'existe pas de partitions.
SVP aidez-moi, c'est urgent !
What is the phone's model number?
Quel est le numéro de modèle du téléphone?
GT-I3905
GT-i9305: https://www.gsmarena.com/samsung_i9305_galaxy_s_iii-5001.php ?
English
This is my phone, but what can I do with this link ?
I search a method for remake the partitions, i have lost all in my phone and Android 4.
I just have Fastboot and TWRP to use ....
Francais
Ceci est bien mon téléphone, mais que puis-je faire avec ce lien ?
Je recherche une méthode pour refaire les partitions, j'ai tout perdu dans mon téléphone, et le système d'exploitation.
Je sais juste utiliser Fastboot et TWRP ...
gigi_dsss said:
GT-I3905
Click to expand...
Click to collapse
gigi_dsss said:
This is my phone, but what can I do with this link ?
I search a method for remake the partitions, i have lost all in my phone and Android 4.
I just have Fastboot and TWRP to use ....
Click to expand...
Click to collapse
I included the link because you said the phone was a GT-I3905 and my link is for the GT-i9305.
You need to try and flash a stock Samsung ROM with a PIT file for the GT-i9305.
English
And where can I found the ROM and the .pit file ?
Francais
Et où puis-je trouver la ROM et le fichier .pit ?
Put file thread: https://forum.xda-developers.com/ga...fo-i9305-pit-file-flash-analysis-pit-t1950591
Stock firmware can be found at sammobile.com, updato.com, or samsung-firmware.org.
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: /