Hello , first sorry for my english but i m french, secondly , i post on the xda forum to try to find a solution to my problem and i Hope Solène ca hello me. I have an Archos 97c with broken screen that i was given , i have changed thé screen and it works fine but when i reboot it , that was impossible to find thé unlocking diagram , so i did a hard reset, and then it was impossible to registre a New mail adress , so i decided to flash a New firmware . I found a New one that i flashed with SP flashtool and it works but it must not be exactly the right one because thé screen works , i have a back light and preloader recognized by flashtool but nothing boot and i havent Access to recouvert anymore . M'y questions are : IS that Anyone have thé right rom or does Anyone Can help me to repair this ? I Hope that everyone understand what i Wang to Say.
up ! is there anyone to help me ????
edit: there s something new , yesterday i wanted to try a trick with the pc but it was the wrong usb cable and when pressing key combinations , the tablet tells something that i dont ear but i just understand at the end " touch the screen" so since , i try to do it again and irealized that I could take screenshots with volume down and power , i see the light and the creen is fonctional because i can turn off or reboot
by touching the screen a bit randomly ...
Tu as trouver une solution a ton problème ai la même tablette que toi et j'ai flasher avec le firmware Archos 97c Platinum a 994 mb et c'est la merde mon écran est devenu noir avec pixel je vois qu'il redémarre et je l'éteint cœur toi au hasard si ta trouver la solution contact moi par Messenger laurentvaituahelme ou par mail [email protected]
Related
Hello everybody !
I have done a very very big mistake !!!
I flashed my hd2 with that wonderful ROM core cell v4.1. Everythings were OK....
I just change the language into french. The mobile has to restart and then it doesn't boot...
That's my fault because i didn't check my radio before and i think that my radio wasn't enough recent...
And now it doen't boot ! It stay at the firt page "cell series get you connected"
Can you help me PLEASE ???
Mickael
salut,
as tu essaye de flasher ta radio en mettant ton hd2 en mode bootloader? (demarrer en laissont le bouton volume bas appuyé)
Oui j'ai essayé en formatant ma micro sd en 32 bits et en prenant une rom renommé leoimg.nbh --> rien ne se passe
Apres j'ai juste mis sur la sd une radio 2.0.8 je crois et toujours pareil...
J'ai suivi quelques forums mais ca n'a rien changé, je reste bloqué sur la premiere page de presentation...
Merci pour ton aide.
kael61 said:
Hello everybody !
I have done a very very big mistake !!!
I flashed my hd2 with that wonderful ROM core cell v4.1. Everythings were OK....
I just change the language into french. The mobile has to restart and then it doesn't boot...
That's my fault because i didn't check my radio before and i think that my radio wasn't enough recent...
And now it doen't boot ! It stay at the firt page "cell series get you connected"
Can you help me PLEASE ???
Mickael
Click to expand...
Click to collapse
Switch phone off, then hold volume down button in and switch on (will boot into multi coloured screen), connect to pc and when "usb" shows on screen then flash the correct radio. There is no need for the device to boot up first for this to work.
When i hold volume down button and switch on i don't have multi colored screen i just have the firt page before booting :
HTC
smart mobility
CELL series
Get you connected
Are you sure you are holding the Volume down button in and keeping it pressed down while switching the phone on? Unless your volume button is not working it should boot into the bootloader (multi coloured) screen.
pull off the sd card before hold volume down and start the phone
DAY 1:
hello,
i tried to install custom rom on bobarry k10se tablet (chinese tablet) has mediatake processor.
1) I wrongly did boot recovery with twrp image file with flashify mobile apk-- its showing bootloop only
2) then at recovery mode I tried to do wipe data and then wipe partion then I tried to install rom from sdcard but it shows - installation aborted.
3) at last i did back up & restore in recovery mode.. god.. its stuck to the flashing green robot screen and wont do anything else.
Please help me what should I do now, after starting the tablet it shows green flashing robot with written "installing system update" and nothing happnes.
I know I have done lots of mistake and tried to install custom RR 5.8.0 which failed.
DAY 2:
i think its hard bricked now. its like switched off. if i connect to the pc via usb, there is only connecting-disconnecting sound.. nothing else happens.
i used sp flash tool with similar kind of firmware, the result shows- s_ft_unable_dram_fail (4032).
Can someone give me bobarry k10se tablet stock ram (mtk6580, android 5.1, 4gb ram)
pls help me
please help to find similar kind of stock rom for my tablet
none is here to help me out???
Bonjour, j'ai un problème de démarrage sur ma tablette Bobarry elle me marque Boot error et je ne sais plus quoi faire,j'ai essayé quelques tuto mais rien alors je compte sur vous merci d'avance Wiwi 66.
Garreau said:
Bonjour, j'ai un problème de démarrage sur ma tablette Bobarry elle me marque Boot error et je ne sais plus quoi faire,j'ai essayé quelques tuto mais rien alors je compte sur vous merci d'avance Wiwi 66.
Click to expand...
Click to collapse
please use the English language
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Hi, I am also looking for BOBARRY K107SE 4G LTE stock rom. Any help will be appreciated. Regards.
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
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: /
good evening I have an x96q box stuck on the x96q boot logo when I put it the firmware by sd card the green bar progresses by a quarter and does not move the box flashes blue. can you help me.
bonsoir j ai un boitier x96q bloqué sur le logo démarrage x96q lorsque je le lui mets le firmware par carte sd la barre verte progresse d un quart et ne bouge plus le boitier clignote en bleu.pouvez vous m aider .Merci
guisel2003 said:
bonsoir j ai un boitier x96q bloqué sur le logo démarrage x96q lorsque je le lui mets le firmware par carte sd la barre verte progresse d un quart et ne bouge plus le boitier clignote en bleu.pouvez vous m aider .Merci
Click to expand...
Click to collapse
Bonsoir and welcome to XDA,
English is the preferred language in the forums, you can use google translate.
Hello all i also have but bricked X96Q . when i plug my box in PC with 100% good USB cable (it was working with another box in past) and drivers are installed, i try it in Win7 and also Win10 , i always get some results and it is: Sound i turn device in PC and it is detected and in 2sec another sound device is disconnected.
SW used is: LiveSuitPack1.11
Please help.
guisel2003 said:
good evening I have an x96q box stuck on the x96q boot logo when I put it the firmware by sd card the green bar progresses by a quarter and does not move the box flashes blue. can you help me.
bonsoir j ai un boitier x96q bloqué sur le logo démarrage x96q lorsque je le lui mets le firmware par carte sd la barre verte progresse d un quart et ne bouge plus le boitier clignote en bleu.pouvez vous m aider .Merci
Click to expand...
Click to collapse
You have had to wait longer time until the green bar has moved until the end. it takes about 10 minutes. If you stop before, I guess the box is bricked.
sakalsk said:
Hello all i also have but bricked X96Q . when i plug my box in PC with 100% good USB cable (it was working with another box in past) and drivers are installed, i try it in Win7 and also Win10 , i always get some results and it is: Sound i turn device in PC and it is detected and in 2sec another sound device is disconnected.
SW used is: LiveSuitPack1.11
Please help.
Click to expand...
Click to collapse
Which firmware did you have installed?