I am making this guide because many people are stuck on this older version of Android 10 these were the lucky users who didn't bricked their device but they got stuck on that update because Xiaomi isn't giving OTA to them for some reason due to which they have to manually update their phone using the method I have given below.
For Mi A2 Lite
V11.0.2 → V11.0.10.0
Here Are The Steps
1 - Unlock Bootloader (You May Skip This Step If You Don't Want To Unlock The Bootloader)
2 - Download The OTA for V11.0.10.0
Link: https://bigota.d.miui.com/V11.0.10.0.QDLMIXM/miui_DAISYGlobal_V11.0.10.0.QDLMIXM_55c39d9793_10.0.zip
3 - Copy OTA File In Memory Card
4 - Go To Recovery Mode (Power Button Volume Up) After That You Will See "No Command" Screen Just Hold Power Button Again And Then Press Volume Up Button Two Seconds And Then Free The Button.
5 - Then Select Option "Apply Update From SD Card" And Select The Path Where You Copied OTA File.
6 - Reboot
7 - Successfully Installed OTA V11.0.10.0.QDLMIXM
Now System Is Showing "Your System Is Up To Date"
Enjoy !
I would request the Mods to please pin this post as still there are many users that are stuck on this update and some people don't even know some people who are smart have updated but some don't it care about updates and they are not updating and this update was the one that cause black spots on the bottom area off the screen and it is dangerous these will be the users who are on goodix screen panel as the other variant didn't booted and bricked the phone.
Thanks in Advance.
Proof of people that are still stuck below:
Proof:
Many thanks! I was stuck on 11.0.2 since February. Everything worked fine on your procedure
chf3 said:
Many thanks! I was stuck on 11.0.2 since February. Everything worked fine on your procedure
Click to expand...
Click to collapse
No Problem Bro
I don't know what happened but when I tried to enter in recovery mode I lost my data I was trying to follow these steps but that happened when I pressent power button + volume up button together and enter in the screen warning about unlock bootloader... After that I tried the steps again and everything went good but I had already lost my data.
Whatever, I have my Mi A2 Lite updated and those black spots disappeared, thanks for the post!
mancarv said:
I don't know what happened but when I tried to enter in recovery mode I lost my data I was trying to follow these steps but that happened when I pressent power button + volume up button together and enter in the screen warning about unlock bootloader... After that I tried the steps again and everything went good but I had already lost my data.
Whatever, I have my Mi A2 Lite updated and those black spots disappeared, thanks for the post!
Click to expand...
Click to collapse
I am sorry to hear that your data was lost but that black spots were damaging your device.
I'm having the same problem bro... Is your camera2 api enabled??
mancarv said:
I don't know what happened but when I tried to enter in recovery mode I lost my data I was trying to follow these steps but that happened when I pressent power button + volume up button together and enter in the screen warning about unlock bootloader... After that I tried the steps again and everything went good but I had already lost my data.
Whatever, I have my Mi A2 Lite updated and those black spots disappeared, thanks for the post!
Click to expand...
Click to collapse
I'm having the same problem actually... If i try to go to recovery mode.. it just shows the spinning icon and says erasing... Is your camera2 api enabled?
Yanyan2129 said:
I'm having the same problem actually... If i try to go to recovery mode.. it just shows the spinning icon and says erasing... Is your camera2 api enabled?
Click to expand...
Click to collapse
No, it's not enable... When it showed the spinning icon I just waited to it finished and get to start screen. And I tried again and that time I could enter to the "no command" screen and later to the recovery. I believe that may happen when you don't press well the buttons.. I'm not sure
mancarv said:
I don't know what happened but when I tried to enter in recovery mode I lost my data I was trying to follow these steps but that happened when I pressent power button + volume up button together and enter in the screen warning about unlock bootloader... After that I tried the steps again and everything went good but I had already lost my data.
Whatever, I have my Mi A2 Lite updated and those black spots disappeared, thanks for the post!
Click to expand...
Click to collapse
Hey since you're from Perú and you speak spanish, I'd like to ask you something.
¿Desbloqueaste el bootloader o no? Porque en el post dice que es opcional. Y donde dice "Memory Card" ¿se refiere a que tengo que descargar la actualización OTA en el teléfono, luego transferirlo a la SD y luego hacer el proceso de instalación en Modo Recovery?
ZabbeX said:
Hey since you're from Perú and you speak spanish, I'd like to ask you something.
¿Desbloqueaste el bootloader o no? Porque en el post dice que es opcional. Y donde dice "Memory Card" ¿se refiere a que tengo que descargar la actualización OTA en el teléfono, luego transferirlo a la SD y luego hacer el proceso de instalación en Modo Recovery?
Click to expand...
Click to collapse
No se requiere desbloqueo del cargador de arranque Se necesita tarjeta SD
ZabbeX said:
Hey since you're from Perú and you speak spanish, I'd like to ask you something.
¿Desbloqueaste el bootloader o no? Porque en el post dice que es opcional. Y donde dice "Memory Card" ¿se refiere a que tengo que descargar la actualización OTA en el teléfono, luego transferirlo a la SD y luego hacer el proceso de instalación en Modo Recovery?
Click to expand...
Click to collapse
Hi Zabbex I believe if you want speak on Spanish you have to send a private message. I'm answering in both languages anyway.
I had the bootloader unlocked before I tried this method so I can't confirm that isn't necessary. And yes, you have to download the OTA update (can be from the PC or phone) and move it to your SD and then you can do the procedure.
Spanish:
Yo ten
---------- Post added at 05:12 PM ---------- Previous post was at 05:09 PM ----------
mancarv said:
Hi Zabbex I believe if you want speak on Spanish you have to send a private message. I'm answering in both languages anyway.
I had the bootloader unlocked before I tried this method so I can't confirm that isn't necessary. And yes, you have to download the OTA update (can be from the PC or phone) and move it to your SD and then you can do the procedure.
Spanish:
Yo ten
Click to expand...
Click to collapse
I don't know why my text got cut but anyways..
Yo tenia el bootloader desbloqueado antes de intentar el procedimiento por eso no te puedo confirmar si es necesario. Necesitas descargar el archivo de actualizacion y pasarlo a la SD y luego puedes hacer el procedimiento normal
Proof that people are still stuck on this update and Xiaomi Does nothing.
Thank you, I was wondering what the heck happened since Android didn't update anymore since feb and voilá.
After this update, system detected and installed September update by itself. Got my phone working better now!
Aadil Gillani said:
I am making this guide because many people are stuck on this older version of Android 10 these were the lucky users who didn't bricked their device but they got stuck on that update because Xiaomi isn't giving OTA to them for some reason due to which they have to manually update their phone using the method I have given below.
For Mi A2 Lite
V11.0.2 → V11.0.10.0
Here Are The Steps
1 - Unlock Bootloader (You May Skip This Step If You Don't Want To Unlock The Bootloader)
2 - Download The OTA for V11.0.10.0
/url]
3 - Copy OTA File In Memory Card
4 - Go To Recovery Mode (Power Button Volume Up) After That You Will See "No Command" Screen Just Hold Power Button Again And Then Press Volume Up Button Two Seconds And Then Free The Button.
5 - Then Select Option "Apply Update From SD Card" And Select The Path Where You Copied OTA File.
6 - Reboot
7 - Successfully Installed OTA V11.0.10.0.QDLMIXM
Now System Is Showing "Your System Is Up To Date"
Enjoy !
Click to expand...
Click to collapse
peoplearetalking said:
Thank you, I was wondering what the heck happened since Android didn't update anymore since feb and voilá.
After this update, system detected and installed September update by itself. Got my phone working better now!
Click to expand...
Click to collapse
No Problem Sir
Hi everyone,
If i will update manually, will i lost my data?
okilickap said:
Hi everyone,
If i will update manually, will i lost my data?
Click to expand...
Click to collapse
No, Not if you use the way described above.
Extra help needed
Hi I'm on 11.0.2 with root right now so do i just go ahead and follow the steps or is there any other prerequisites for rooted devices?
thenameisJEFF said:
Hi I'm on 11.0.2 with root right now so do i just go ahead and follow the steps or is there any other prerequisites for rooted devices?
Click to expand...
Click to collapse
Flash fastboot tgz file using MI Flash with savedata option then root again make sure you to uninstall all the modules
Thank you for this tutorial. Mine stuck on 11.0.5 and since then it says not updates found.
Successfully updated straight to 11.0.12. No data loss.
Also despite update file has MIUI in name it is still Android One.
Related
I tried to root my Wifi xoom with 3g files and bricked it. I have the system file that I could probably reload onto it if I could remount it, but right now it's stuck on the "dual-core" screen. I can force it into fastboot by hold the volume down button but my computer still isn't recognizing it. Is there any solution?
Edit: Nevermind, successfully restored...
Warranty? X)
Enviado desde el Motorola Milestone 2
First, sorry for my anxiety to solve this problem. Frankly I would not want to send to technical support, and stay up to 30 days without it. If anyone can help me I would be very grateful. Here the situation:
1) Install the normal sbf JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN
2) Install the nandroid 3.4.2_155-Nand.CEE_DEBLUR
3) Install the fixed sbf 3.4.2_155-Fixed.CEE_DEBLUR
4) To revert to Eclair, install the original uk sbf 2.21
4) And then, the result: the phone don't even turn on.
Already pullout the battery and the sim chip, and nothing happens. I connect to pc, and the led goes white, but nothing happens. I try to go into bootloader, but the phone don't even turn on. The battery is charged, about 80%.
Please, i'm desperate here. Already searched and keep reading, but find nothing that helps me in this case.
You are doing it the wrong way. Turn on the phone the rsd lite will recognise it. Then flash the 3.4.2 sbf back, then root it install recovery, restore 2.21 nadroid and flash a fixed sbf(without cg31 and cg39) not the full sbf. if you flash the full sbf your phone wont boot.
vick33 said:
You are doing it the wrong way.
Flash the 3.4.2 sbf back, then root intall recovery restore 2.21 nadroid and flash a fixed sbf not the full sbf. if you flash the full sbf your phone wont boot.
Click to expand...
Click to collapse
Thank you, vick33, but the phone does not even power on. I really would like to do this.
You wont see anything. The white led only will lit up when you connect it to the pc
ja tentou tirar a bateria fora, dai segurar o botão de volume pra cima, recolocar a bateria e ligar enquanto segura o botão de volume pra cima?
did you try taking out the battery then put it back while holding up the "Volume +" button and then powering up the device?
vick33 said:
You wont see anything. The white led only will lit up when you connect it to the pc
Click to expand...
Click to collapse
In desperation, I decided to connect the phone to the computer again, and that is worked, not even showing anything.
The normal would to show some texts, like ready to flash. But still worked.
Start RSDlite and flash the 3.4.2.155 again, and its ok. Thanks.
Marcio, já tinha tentado tudo isto, mas o Defy nem ao menos ligava, não acontecia nada, por isso achei estranho, e estava meio que desesperado. Mas deu certo, cara, mesmo sem aparentemente ligar o RSD reconheceu e "flasheou" o bichinho. Valeu.
Now, to go back no Eclair 2.21 and a nandroid backup of my rom (Claro Brazil), how to procede? I have only de UK Eclair 2.21, not a Brazilian SBF. I hope I do not **** now.
Thanks
You messed up..
Step 1 was a bad move.
Unfortunately there is no downgrade to eclair.
Revival:
Connect defy to pc, run RSD lite and flash JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN again.
Henceforth must have use froyo.
vazzz said:
You messed up..
Step 1 was a bad move.
Unfortunately there is no downgrade to eclair.
Revival:
Connect defy to pc, run RSD lite and flash JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN again.
Henceforth must have use froyo.
Click to expand...
Click to collapse
Ok, vazzz, I'll continue to use Froyo. The downgrade to Eclair is only for tests purpose.
Thanks to all.
lcesser said:
Ok, vazzz, I'll continue to use Froyo. The downgrade to Eclair is only for tests purpose.
Click to expand...
Click to collapse
Half-measure: made it an 2.21 fixed sbf.
Description: http://forum.xda-developers.com/showthread.php?t=1010315(im used 2.51 fixed sbf and 2.51 nandroid backup)
I did the bootloader oem unlock and the tablet didnt erase anything ? what can i do to restore my xoom i have tried everytning factory reset from android and factory reset from the recovery mode and desnt eras anything stay with the same apps and everything. help please what can i do??
More informations, what region for your MZ604 Europe? Verizon USA?...
I have the same problem, Mine is a Z604 bought in USA, (I'm Argentinian).
I`ve tried making oem unlock which is done ok, then all the ¨fastboot¨ flash boot. img - recovery. img - system. img...... but at the end.... its the same tablet and no data has been erased.: eek:
You can't install the TRW because happens all the same I follow all the septs from the guides... and then i have the fu%$&$ing ¨3e¨ recovery... and nothing has been deleted.: (
In addition, my problem is bigger, the table self reboot in 1 or 2 minutes after loading in android. I mean I can use it for 1 or 2 min, i delet for example a picture and then when it reboots the picture is there..
dont know what to do... Any ideas?!
shadowf17 said:
I have the same problem, Mine is a Z604 bought in USA, (I'm Argentinian).
I`ve tried making oem unlock which is done ok, then all the ¨fastboot¨ flash boot. img - recovery. img - system. img...... but at the end.... its the same tablet and no data has been erased.: eek:
You can't install the TRW because happens all the same I follow all the septs from the guides... and then i have the fu%$&$ing ¨3e¨ recovery... and nothing has been deleted.: (
In addition, my problem is bigger, the table self reboot in 1 or 2 minutes after loading in android. I mean I can use it for 1 or 2 min, i delet for example a picture and then when it reboots the picture is there..
dont know what to do... Any ideas?!
Click to expand...
Click to collapse
You can flash your Xoom with RSDlite 5.4.4 but you need to find the good sbf. file for this
pots22 said:
You can flash your Xoom with RSDlite 5.4.4 but you need to find the good sbf. file for this
Click to expand...
Click to collapse
Hi, NO LUCK. I did it and it didnt work.
i download this file ... VZW_MZ604_signed_IML77.combo.sbf and used the RSDLite5.4.4_MTK_Patch10.msi wich i found it over internet.
It did all de proces till it reboot de xoom but its still with old things and rebooingloop
PD: an other thing is when im getting to recovery on screen apears a laid green andorid with a red triangle on it... y have to press volume up + power and then it gets into de recovery wich is de 3e... :crying:
shadowf17 said:
Hi, NO LUCK. I did it and it didnt work.
i download this file ... VZW_MZ604_signed_IML77.combo.sbf and used the RSDLite5.4.4_MTK_Patch10.msi wich i found it over internet.
It did all de proces till it reboot de xoom but its still with old things and rebooingloop
PD: an other thing is when im getting to recovery on screen apears a laid green andorid with a red triangle on it... y have to press volume up + power and then it gets into de recovery wich is de 3e... :crying:
Click to expand...
Click to collapse
This sbf file not good is Verizon only. try to find this:
HUBWF_W5.H.6.4-20_SIGNED_UCAHUBU01SPLAWIFI_P010_A007_M006_HWwifi_ hubble_AP1FF.sbf
Regions: Argentina, Costa Rica, Dominican Republic, El Salvador, French Guiana, Guatemala, Guyana, Honduras, Jamaica, Mexico, Nicaragua, Panama, Puerto Rico, Suriname
Hello,
I downloaded the latest Malaysk software from the repository, tried installing it with the second method (from "System update") along with wiping flash.
Now this KGL MTCD unit is bricked, there is no response from it, aside from the buttons lighting up.
How to unbrick it?
can you get in to the Recovery?
Never change a running system if you are not knowing what you do
NiTr0Us said:
can you get in to the Recovery?
Never change a running system if you are not knowing what you do
Click to expand...
Click to collapse
Yes, if you can get into recovery you can just flash. In the thread it clearly says that you have to get into recovery BEFORE flashing (because you have to flash twice due to partitioning).
Ask your vendor how you can get into recovery if the usual way (pressing power + reset at the same time, then releasing reset and pressing power a single time again) wont work.
Just get in recovery and use the Wipe data / reset cache option, then flash it again from recovery.
Reboot and enjoy
If I could get into recovery I wouldn't be posting this topic.
Recovery doesn't work.
What now?
TO get into recovery,
when it should boot up, press and hold power.
THen it will force shutdown. Next boot brings up recovery for me!
same here bro
the unit is totaly dead, cant go to recovery...
hashtowent said:
TO get into recovery,
when it should boot up, press and hold power.
THen it will force shutdown. Next boot brings up recovery for me!
Click to expand...
Click to collapse
Like I said, I cannot get into recovery. The unit doesn't boot up at all.
Oh well, I'll just replace the motherboard.
for all of you with bricks. lets do some experiments
Can you guys hook it up to a computer and see if the computer can read it. If you can you should be able to adb the rom back.
http://www.rockchip.nl/downloads/
Make sure you have the drivers. If you can successfully read it then you can use RKTools or adb.
transitoyspace said:
for all of you with bricks. lets do some experiments
Can you guys hook it up to a computer and see if the computer can read it. If you can you should be able to adb the rom back.
Make sure you have the drivers. If you can successfully read it then you can use RKTools or adb.
Click to expand...
Click to collapse
hahahah
i do this work without read you, i came here to post the solution
with the rk3188 drivers + " RK Batchtool" i firm the unit in 3 mins. its works ok
Can you share the steps? I have a bricked unit also.
transitoyspace said:
for all of you with bricks. lets do some experiments
Can you guys hook it up to a computer and see if the computer can read it. If you can you should be able to adb the rom back.
http://www.rockchip.nl/downloads/
Make sure you have the drivers. If you can successfully read it then you can use RKTools or adb.
Click to expand...
Click to collapse
Even if MCU has changed we can recover to factory settings??
Because in my HU i can go to reboot display but appeared the message
Cant mount...../device/block/.../.../(device block required).
I had similar issues
Trimis de pe al meu SM-G930F folosind Tapatalk
---------- Post added at 03:09 PM ---------- Previous post was at 03:05 PM ----------
Fixed by removing the power connector and keeping power button pressed and restored power supply without ACC in order to establish usb connection with my laptop.
By using RK batchtool, I managed to restore my unit.
Trimis de pe al meu SM-G930F folosind Tapatalk
adibxx said:
I had similar issues
Trimis de pe al meu SM-G930F folosind Tapatalk
---------- Post added at 03:09 PM ---------- Previous post was at 03:05 PM ----------
Fixed by removing the power connector and keeping power button pressed and restored power supply without ACC in order to establish usb connection with my laptop.
By using RK batchtool, I managed to restore my unit.
Trimis de pe al meu SM-G930F folosind Tapatalk
Click to expand...
Click to collapse
But I suppose that you loaded on RK batch tool the factory Mcu and firmware right?
Because in my case I can't find factory mcu and seller doesn't know to provide me the factory software.
So with batchtool what can I do?
Qwerty11111 said:
But I suppose that you loaded on RK batch tool the factory Mcu and firmware right?
Because in my case I can't find factory mcu and seller doesn't know to provide me the factory software.
So with batchtool what can I do?
Click to expand...
Click to collapse
Factory firmware failed checksum. So, I used Malaysk ROM. The latest version failed to erase screen, but, the previous one booted successfully. Initially I tries to use recovery and ended up in brick device. Only rear camera was working. The devices stacked to Malaysk ROM screen and no stand by if ACC OFF.
Trimis de pe al meu SM-G930F folosind Tapatalk
Hi there,
Trying to install Malaysk ROM on an MTCD-KGL unit, I managed to get it bricked. As in... no screen, no sound, no Recovery, nothing! Couldn't link it to PC, nothing. The reset + volume button combination did not work for me to enter Recovery. My screen was all dead.
So... After some research, I used "Rockchip Upgrade Disk Tool" v1.4 and the unit booted from the sd card inserted in the GPS slot (Guide here: http://wiki.radxa.com/Rock/SD_upgrading ).
In theory, the unit should have started automatically upgrade from the SD but in my case it presented an error requesting me to remove the sd card. After removal, the unit went to Recovery boot menu. Still a success.
When the Recovery menu appeared, I inserted an sd card with dupdate.img on it in the GPS slot and selected install from menu. Unfortunately, the unit kept saying that it does not find the sd card. Tried the other sd slot but same error.
Success came from USB port. One of the two from the back of the unit, not the one in front. I put the dupdate.img and dmcu.img on an usb stick and inserted in one of the usb ports from the back. The unit recognized the stick and started the update process.
Now the unit is working.
If someone is interested, I can provide MCU and ROM (version from October 2016).
Hope this helps someone.
kufu said:
Hi there,
Trying to install Malaysk ROM on an MTCD-KGL unit, I managed to get it bricked. As in... no screen, no sound, no Recovery, nothing! Couldn't link it to PC, nothing. The reset + volume button combination did not work for me to enter Recovery. My screen was all dead.
So... After some research, I used "Rockchip Upgrade Disk Tool" v1.4 and the unit booted from the sd card inserted in the GPS slot (Guide here: http://wiki.radxa.com/Rock/SD_upgrading ).
In theory, the unit should have started automatically upgrade from the SD but in my case it presented an error requesting me to remove the sd card. After removal, the unit went to Recovery boot menu. Still a success.
When the Recovery menu appeared, I inserted an sd card with dupdate.img on it in the GPS slot and selected install from menu. Unfortunately, the unit kept saying that it does not find the sd card. Tried the other sd slot but same error.
Success came from USB port. One of the two from the back of the unit, not the one in front. I put the dupdate.img and dmcu.img on an usb stick and inserted in one of the usb ports from the back. The unit recognized the stick and started the update process.
Now the unit is working.
If someone is interested, I can provide MCU and ROM (version from October 2016).
Hope this helps someone.
Click to expand...
Click to collapse
Hi,
Before you saved your unit, did button light light up or not? I have same issues like you had, but unfortunatelly I can't debrick my unit. Could you provide me all files (links), which helped you to brought it alive, please? Thanks.
Hello! At my unit, yes the buttons light was on. There is a link in my post and also you can read here: http://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
Hope you solve your problem.
Qwerty11111 said:
But I suppose that you loaded on RK batch tool the factory Mcu and firmware right?
Because in my case I can't find factory mcu and seller doesn't know to provide me the factory software.
So with batchtool what can I do?
Click to expand...
Click to collapse
I had factory firmware but didn't work.
I used the latest one.
Trimis de pe al meu SM-G930F folosind Tapatalk
I did a walkthrough with pics on how i recovered my unit.
https://forum.xda-developers.com/an...nt/eonon-ga6164f-mtcd-rk3188-mtcdkld-t3594368
Hello,
Since a few OTA update, my phone keeps rebooting. Most of the time it was just after I validate the password unlock screen (so I removed it). Now it happen when I load an app like TELEGRAM (FLOSS) or Gallery app or during a skype call or any other app: it's random and anoying...
So the phone suddenly shut down the "google" logo appear then sometimes reboot normally sometimes keep rebooting in loop after 1 second specially if it's charging so I unplug it and it stops loopng.
Then if I can't boot it, I just load TWRP andpress BOOT SYSTEM from there.
I believe it's a software issue because it happened just after an OTA update (maybe around 4 updates ago)
I read 20 threads about reboot, they are very old and all talk about power button issue.
Any clue please?
Thank you
EDIT
Fixed by the following steps:
- put the original ROM with the software Nexus Root Tool kit which is super convenient to put the phone back to default
- do the Google account setup quickly (just put wrong information, ignore everything)
- do another full reset (from setting menu > backup and reset)
My 5x has been doing the same for about a week now. First restart was during a long run on a hot day. Have you had any success in fixing it? Safe Mode doesn't help, and I'm looking to move to October's update and wipe system cache. I'll let you know if that fixes things.
andyhostetler said:
My 5x has been doing the same for about a week now. First restart was during a long run on a hot day. Have you had any success in fixing it? Safe Mode doesn't help, and I'm looking to move to October's update and wipe system cache. I'll let you know if that fixes things.
Click to expand...
Click to collapse
Cannot fix it. I'm going to put the original ROM with the software Nexus Root Tool kit which is super convenient to put the phone back to default and see if the problem persists. If it doesn't, I will wait until LOS 15.1 or /e/ stable release.
I will let you know if the original ROM solve the problem
PURJUJU said:
Cannot fix it. I'm going to put the original ROM with the software Nexus Root Tool kit which is super convenient to put the phone back to default and see if the problem persists. If it doesn't, I will wait until LOS 15.1 or /e/ stable release.
I will let you know if the original ROM solve the problem
Click to expand...
Click to collapse
Result: still reboot... so it's probably a coincidence that since an update this phone reboot. I will change for a FAIRPHONE or try to fix it :
https://www.youtube.com/watch?v=doPuXkQTGbc
https://www.youtube.com/watch?v=tln6d93t1sk
et en attendant, installer un logiciel pour neutraliser le bouton power qd le tel est allumé :
– Installer Volume UnLock : le déverrouillage du mobile se fera par un appui sur le bouton de volume
– Installer Screen Lock : le vérouillage se fera par une petite icone
I did another full reset (from setting menu) after I installed the original ROM and it's been a few hours that I'm not facing the problem anymore.... let's see
PURJUJU said:
I did another full reset (from setting menu) after I installed the original ROM and it's been a few hours that I'm not facing the problem anymore.... let's see
Click to expand...
Click to collapse
The October update didn't fix anything. It seems to do okay while plugged in, but I also noticed that the "USB supplying power to attached device" notification is on often, even with nothing plugged in. I tried cleaning the port. Fastboot still works, but it's hit and miss with USB recognition while powered on. My probable last recourse is to try the 4-core fix for BLOD issues. I'm on my second phone, and I don't know that it's worth it to attempt warranty again if a software fix can prevent the issues. Any thoughts?
Just to let you know that it's been now a few days my phone works very fine with the original rom
root?
PURJUJU said:
Just to let you know that it's been now a few days my phone works very fine with the original rom
Click to expand...
Click to collapse
Did you root after installing the original rom (which version, btw?)? Did you leave your bootloader unlocked?
andyhostetler said:
Did you root after installing the original rom (which version, btw?)? Did you leave your bootloader unlocked?
Click to expand...
Click to collapse
No root needed. The last version provided by nexus root toolkit. Yes I left it unlock because I don't remember how to lock it back and I'm lazy to find the way to lock it! lol!