Related
Hello,
This is the third time I've asked you for help. This time it is, it always concerns google pixel C. Everything worked so well. But today, by simply taking a picture, the device turns off and on again on the google logo. Then the android robot with a red alert appears. the word "No command" just below. I can navigate the recovery. But impossible to go into "android recovery" with the menus to apply sideload ota.... I sincerely think it is brick and I'm really very afraid that I won't be able to use the guarantee despite having locked the bootloader before. I was on the official Android 7.1.2 software. The adb and fastboot commands detect the tablet. But I can't unlock the bootloader or flash... I have no idea what to do, I could use your help please!!!!!!!!
Hawkeye5 said:
Hello,
This is the third time I've asked you for help. This time it is, it always concerns google pixel C. Everything worked so well. But today, by simply taking a picture, the device turns off and on again on the google logo. Then the android robot with a red alert appears. the word "No command" just below. I can navigate the recovery. But impossible to go into "android recovery" with the menus to apply sideload ota.... I sincerely think it is brick and I'm really very afraid that I won't be able to use the guarantee despite having locked the bootloader before. I was on the official Android 7.1.2 software. The adb and fastboot commands detect the tablet. But I can't unlock the bootloader or flash... I have no idea what to do, I could use your help please!!!!!!!!
Click to expand...
Click to collapse
Have you tried this?
"Turn off GOOGLE PIXEL C. Press and hold together : Power Button + Volume Down until Logo appear at LCD screen. If we see the menu at LCD screen, choose Wipe Data/Factory Reset with Volume Button to select and use Power Button to ok or enter."
Are you sure I can do that? Because I had downgraded Android from version 8.1.0 to 7.1.2 because I had a problem with 8.1.0. Therefore I had unlocked the bootloader etc.... So the data had been erased! If I do a wipe data/Factory reset will it work at least at 90/95% ? Despite having only installed the Factory image (without OTA) can it work without doing a bootloop or other...?
braunie said:
Have you tried this?
"Turn off GOOGLE PIXEL C. Press and hold together : Power Button + Volume Down until Logo appear at LCD screen. If we see the menu at LCD screen, choose Wipe Data/Factory Reset with Volume Button to select and use Power Button to ok or enter."
Click to expand...
Click to collapse
Well, I tried and I always fall back on the page with the robot and the inscription "no command" just below. I'm sad ?
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
braunie said:
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
Click to expand...
Click to collapse
The bootloader is locked. This is the end. Is there any advice I can try to send it to the after-sales service?
braunie said:
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
Click to expand...
Click to collapse
Tell me, the OTA file is used to apply an update, right? Because I tried to do this manipulation but by downloading Exactly the same software and it didn't work. So if I try with a more recent version of Android, it should work, right?
Hawkeye5 said:
Tell me, the OTA file is used to apply an update, right? Because I tried to do this manipulation but by downloading Exactly the same software and it didn't work. So if I try with a more recent version of Android, it should work, right?
Click to expand...
Click to collapse
Sorry, but I don't know this. If the bootloader is locked I have no further idea.
Maybe somebody else has an idea???
braunie said:
Sorry, but I don't know this. If the bootloader is locked I have no further idea.
Maybe somebody else has an idea???
Click to expand...
Click to collapse
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Perfect!
---------- Post added at 03:20 PM ---------- Previous post was at 03:20 PM ----------
Hawkeye5 said:
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Click to expand...
Click to collapse
So I may ask you for help if I have the same problem
Hawkeye5 said:
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Click to expand...
Click to collapse
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Jmash79 said:
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Click to expand...
Click to collapse
Hi, if your device is a C pixel, you can try to check it out here: https://developers.google.com/android/ota
To sum up, my problem was the following: suddenly, my tablet could no longer boot on android but on the page where the robot was displayed with a red panel and the indication "no command".
And the solution was the following: being on Android 7.1.2 I had to download Android 8.1.0 for the "update" to work. So I followed all the steps indicated by the site I provided you. That is, having Fastboot and adb working, then putting the.Zip file of your android in the same folder as adb and Fastboot. Then you follow the different steps shown on the site to download the ota image. My explanation is not great so if you have a question about something specific let me know. And if you can send screenshots of your worries it will help.
Good luck with that!
Jmash79 said:
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Click to expand...
Click to collapse
Hi, if your device is a C pixel, you can try to check it out here: https://developers.google.com/android/ota
To sum up, my problem was the following: suddenly, my tablet could no longer boot on android but on the page where the robot was displayed with a red panel and the indication "no command".
And the solution was the following: being on Android 7.1.2 I had to download Android 8.1.0 for the "update" to work. So I followed all the steps indicated by the site I provided you. That is, having Fastboot and adb working, then putting the.Zip file of your android in the same folder as adb and Fastboot. Then you follow the different steps shown on the site to download the ota image. My explanation is not great so if you have a question about something specific let me know. And if you can send screenshots of your worries it will help.
Good luck with that!
Translated with www.DeepL.com/Translator
As a beginner I was looking for ways to get away from the Google dialer and the phone recording restrictions. Read that the Indonesian ROM had the miui dialer and tried to flash an official Indonesian rom on my new Redmi Note 8. The result was not good. After flashing, using the XiaoMiFlash tool and a tweak to bypass the mismatched-image-error (https://forum.xda-developers.com ... r-fastboot-t3638653, the phone remained in Fastboot mode. I have probably tried to boot a Gingko image on a Willow phone.
When trying to restart it just blinks briefly and turns of. The same in fastboot mode: just briefly buzzes and shows the the fastboot screen and then turns off. Guess it is bricked.
Is there any way to restore it to original global rom?
the same problem with you
NoviceDK said:
As a beginner I was looking for ways to get away from the Google dialer and the phone recording restrictions. Read that the Indonesian ROM had the miui dialer and tried to flash an official Indonesian rom on my new Redmi Note 8. The result was not good. After flashing, using the XiaoMiFlash tool and a tweak to bypass the mismatched-image-error (https://forum.xda-developers.com ... r-fastboot-t3638653, the phone remained in Fastboot mode. I have probably tried to boot a Gingko image on a Willow phone.
When trying to restart it just blinks briefly and turns of. The same in fastboot mode: just briefly buzzes and shows the the fastboot screen and then turns off. Guess it is bricked.
Is there any way to restore it to original global rom?
Click to expand...
Click to collapse
the service center have no idea, they said the phone must change motherboard:crying:
dugu1248 said:
the service center have no idea, they said the phone must change motherboard:crying:
Click to expand...
Click to collapse
Hi, I had a similar issue and I sent it to the service center. Was the fix too expensive for you?
SonXiaomi89 said:
Hello !
I ran into the same problem, and I solved it!
inbox me. I can help you to solve this problem.
Click to expand...
Click to collapse
why not post it here so everyone can get it ???
repair it on service center
SonXiaomi89 said:
Hello !
I ran into the same problem, and I solved it!
inbox me. I can help you to solve this problem.
Click to expand...
Click to collapse
Why not post it here, so everyone can get it ???
That's what the forum is for.
NoviceDK said:
As a beginner I was looking for ways to get away from the Google dialer and the phone recording restrictions. Read that the Indonesian ROM had the miui dialer and tried to flash an official Indonesian rom on my new Redmi Note 8. The result was not good. After flashing, using the XiaoMiFlash tool and a tweak to bypass the mismatched-image-error (https://forum.xda-developers.com ... r-fastboot-t3638653, the phone remained in Fastboot mode. I have probably tried to boot a Gingko image on a Willow phone.
When trying to restart it just blinks briefly and turns of. The same in fastboot mode: just briefly buzzes and shows the the fastboot screen and then turns off. Guess it is bricked.
Is there any way to restore it to original global rom?
Click to expand...
Click to collapse
I got the same here. Did you fix it?
I flashed my RM5 with the CN ROM shortly after receiving the phone due to the software limitations of the NA ROM shipped on the device. With the CN ROM I successfully used face unlock. Now after flashing to the newly released global (v3.11) I get an error when trying to register my fingerprint (attached).
Steps taken:
1. Re-flashed CN ROM and attempted to register fingerprint and got the same error
2. Re-installed the new global v3.11
3. Flashed global recovery, boot, splash, parameter, then wiped data & cache. Factory reset. Still get the same error
Interesting to note that upon setup the phone said the fingerprint sensor was on the back.
JerryYin said:
You should find the person who gives you the phone. The fingerprint calibration data will lost only when you try to unlock the bootloader
Click to expand...
Click to collapse
Looks like the community is solving the problems again: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
terrapin4 said:
I flashed my RM5 with the CN ROM shortly after receiving the phone due to the software limitations of the NA ROM shipped on the device. With the CN ROM I successfully used face unlock. Now after flashing to the newly released global (v3.11) I get an error when trying to register my fingerprint (attached).
Steps taken:
1. Re-flashed CN ROM and attempted to register fingerprint and got the same error
2. Re-installed the new global v3.11
3. Flashed global recovery, boot, splash, parameter, then wiped data & cache. Factory reset. Still get the same error
Interesting to note that upon setup the phone said the fingerprint sensor was on the back.
Click to expand...
Click to collapse
You need to lock the bootloader to make it work, this will wipe your phone however. It says the fingerprint is on the back because the devs didn't bother fixing the typo in the setup.
rat7lol said:
You need to lock the bootloader to make it work, this will wipe your phone however. It says the fingerprint is on the back because the devs didn't bother fixing the typo in the setup.
Click to expand...
Click to collapse
Same thing after BL unlock/wipe. Same thing after BL relock/wipe
Are you sure you're using the correct command? There's "fastboot oem nubia_lock NUBIA_NX659J" and "fastboot flashing lock".
"fastboot flashing unlock" breaks the fingerprint
rat7lol said:
Are you sure you're using the correct command? There's "fastboot oem nubia_lock NUBIA_NX659J" and "fastboot flashing lock".
"fastboot flashing unlock" breaks the fingerprint
Click to expand...
Click to collapse
Yup I'm using "fast boot flashing (un)lock". I've unlocked and relocked now.
Sent from my NX659J using Tapatalk
terrapin4 said:
Yup I'm using "fast boot flashing (un)lock". I've unlocked and relocked now.
Sent from my NX659J using Tapatalk
Click to expand...
Click to collapse
Have you tried "fastboot flashing relock"
relock not lock
zayidhs said:
Have you tried "fastboot flashing relock"
relock not lock
Click to expand...
Click to collapse
Yes, it only accepts "fastboot flashing lock".
In any event, no matter if I unlock/relock the bootloader on the CN Rom or switch to the global ROM and do the same the fingerprint error persists. I even installed TWRP again and formatted data and did everything all over again.
Looks like I'm stuck with either face unlock only on CN or no fingerprint on global.
Really appreciate all the help though!
terrapin4 said:
Yes, it only accepts "fastboot flashing lock".
In any event, no matter if I unlock/relock the bootloader on the CN Rom or switch to the global ROM and do the same the fingerprint error persists. I even installed TWRP again and formatted data and did everything all over again.
Looks like I'm stuck with either face unlock only on CN or no fingerprint on global.
Really appreciate all the help though!
Click to expand...
Click to collapse
We need @JerryYin to supply an unbrick tool. Sounds like a partition has been wiped permanently. Only an unbrick tool will reflash all proper partitions.
VZTech said:
We need @JerryYin to supply an unbrick tool. Sounds like a partition has been wiped permanently. Only an unbrick tool will reflash all proper partitions.
Click to expand...
Click to collapse
No, the unbrick tool won't help. you need re-calibration the fingerprint sensor.
JerryYin said:
No, the unbrick tool won't help. you need re-calibration the fingerprint sensor.
Click to expand...
Click to collapse
Do you have any suggestions on how to fix this?
terrapin4 said:
Do you have any suggestions on how to fix this?
Click to expand...
Click to collapse
Like Jerry said, the fingerprint sensor needs to be re-calibrated.
In the factory
With nubia
Sorry
terrapin4 said:
Do you have any suggestions on how to fix this?
Click to expand...
Click to collapse
For now you have to send the phone back to service center to perform the fingerprint recalibration.
I thought it's software issue not hardware issue , yesterday I checked my friend rooted phone it was work excellent but when I updated it and rooted again it want work again
@JerryYin
Currently I'm getting the "Loss of fingerprint calibration data" message when I try to add a fingerprint. This advises me to contact Nubia's after-sales service via the number "4007006600". This device is provided to me directly by Nubia engineers.
I've just tried to run the calibration and have gotten two errors - one being that the number of bad pixels is abnormal (even though the results are below the threshold), and the other being an "Unknown Error" message
Screenshots of results here: https://photos.app.goo.gl/NpfpDUDgSkMmAc187
gamebenchjake said:
@JerryYin
Currently I'm getting the "Loss of fingerprint calibration data" message when I try to add a fingerprint. This advises me to contact Nubia's after-sales service via the number "4007006600". This device is provided to me directly by Nubia engineers.
I've just tried to run the calibration and have gotten two errors - one being that the number of bad pixels is abnormal (even though the results are below the threshold), and the other being an "Unknown Error" message
Screenshots of results here: https://photos.app.goo.gl/NpfpDUDgSkMmAc187
Click to expand...
Click to collapse
You need to relock tge bootloader. Or send back to customer for re calibration
JerryYin said:
You need to relock tge bootloader. Or send back to customer for re calibration
Click to expand...
Click to collapse
Hi @JerryYin, The bootloader is locked (never unlocked). The device was sent directly by Nubia Engineering, so I can't send it back (no purchase receipt etc).
The issue seems to be that the device never passes the "CALBRATE_CHECKBOX" test, though everything else passes. If you could provide some insight into what this test is checking, I can finish calibrating it myself
gamebenchjake said:
Hi @JerryYin, The bootloader is locked (never unlocked). The device was sent directly by Nubia Engineering, so I can't send it back (no purchase receipt etc).
The issue seems to be that the device never passes the "CALBRATE_CHECKBOX" test, though everything else passes. If you could provide some insight into what this test is checking, I can finish calibrating it myself
Click to expand...
Click to collapse
You should find the person who gives you the phone. The fingerprint calibration data will lost only when you try to unlock the bootloader
Can someone help me, I need better clarification on some things.
So the first set of steps involve:
1) 'call' *#9959* and turn off the 'performance'
2) click 'start' and leave to phone/screen alone aka no touching it whats so ever, then I get the following text in image 1.
Now the steps after that have me confused on some things:
Step 2
3) Click 'Next' and the screen will dim abit
Do I have to leave the screen alone or do I have to put my finger immediately after hitting 'next'?
Cause I saw posts about leaving it alone and others saying to put my finger(thumb).
If I put my finger on the screen it gives me an error '0x3A self-exposure abnormal' (as in image 2);
but if I leave it alone it'll give me 'Auto_Exposure' & 'Flesh' tests succeeded (image 3)
I NEED clarification here, am I doing this part wrong by not having my finger on the Fp scanner.
Now for step 3, I have to:
4) click on 'Next' and the phone will do the 'Dark' and 'Dark-Base' tests. The should be left alone here as well. (Image 4)
I need to be in a dark room for this, correct?
Now for the final step
6) Click 'Next' and put my finger back to the screen on the blue FP scanner(?)
When I do this; I end up with '0x14 the number of bad pixels....' (image 5)
Any help is very up appreciated.
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
foobar66 said:
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
Click to expand...
Click to collapse
Unfortunately the phone is supposed to have a working bootloader
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Ouch ...
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Android Flash Tool
flash.android.com
Also doesn't work?
Morgrain said:
Android Flash Tool
flash.android.com
Also doesn't work?
Click to expand...
Click to collapse
Nope...
Thibale said:
Nope...
Click to expand...
Click to collapse
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Morgrain said:
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Click to expand...
Click to collapse
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
yes but you need to be able to communicate with your phone from your pc.....if you cant access fastboot then how will you change partition?
Thibale said:
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
Click to expand...
Click to collapse
The only special tools we have are either the pixel repair tool or the android flash tool. If both can't get you fastboot / firmware flashing, that's it. Hardbrick. Google Pixels don't have "special" hardbrick solving tools, like older OnePlus had. You need to contact Google.
Ok I'll get in touch with my local reseller on Monday then...
Thibale said:
Ok I'll get in touch with my local reseller on Monday then...
Click to expand...
Click to collapse
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
WOW. So even holding volume down and power until you see the fastboot screen wont work? sometimes you have to hold it for a while. I say that because when the December firmware came out I accidentally flashed the wrong region but was able to access bootloader and so was able to rescue myself. So sorry dude. That really sucks.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
Yes worst case we'll have for repair but they could have implemented a simple device id check on their script prior flashing anything, especially for the bootloader.
Anyway, I'm alive, in a good health and it's just a phone
niko26 said:
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Click to expand...
Click to collapse
You can flash gobbledygook to your phone if you're not careful. You can flash a non-Google phone's image. Flashing just flashes what you tell it to flash.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
That sucks. I'm sure you know now, always go straight to the source for everything if possible, firmware, platform tools, drivers, BIOS / UEFI (for computer).
SDK Platform Tools
Get the Google USB Driver
Pixel 6 Pro Factory Images
You can also Google for official pixel firmware and the top search result is what the want. I know it doesn't help you now. Good luck with your phone!
Morgrain said:
After having played around with the January patch (came from December Europe A4 firmware that was pulled), it seems that the FP scanner got even faster and more reliable, even though it's not stated in the patchnotes. Maybe it's just placebo.
Click to expand...
Click to collapse
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
roirraW edor ehT said:
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
Click to expand...
Click to collapse
I noticed how faster it was before I saw everyone else posting about it, so at least no placebo on my end. Hope you find the same.
I know that you tried to get into Fastboot. Pixel 6/6P also has a Recovery mode. I can get to it from a working phone.
I would think that there is someway to boot into Recovery mode from a dead phone via button combos.
Thibale said:
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Click to expand...
Click to collapse
Hy, how did you flashed? Via adb sideload or?
vrda08 said:
Hy, how did you flashed? Via adb sideload or?
Click to expand...
Click to collapse
factory image with modified flash-all.bat
I'll do the exact same process when I'll get my phone back but this time I'll check the image name at least 3 times
hi
i have realme 8 5g (rmx3241).i flashed a corvus gsi but it comes with bootloop.so,i decided to flash stock rom.but this error comes" status brom cmd send da fail" while trying to solve that error I mistakenly format the phone , now the phone is not coming up again. I was able to solve the that error and decided to flash the firmware now it bringing up verified boot enabled. My major problem about it is the fact that the phone is not even coming up again please help
please reply
i have the same problem we need dump for this model thanks
how to?
awzx_77 said:
i have the same problem we need dump for this model thanks
Click to expand...
Click to collapse
awzx_77 said:
i have the same problem we need dump for this model thanks
Click to expand...
Click to collapse
what have to dumb
Good afternoon, after the ota software update, the display stopped working, just a black screen, but the system sounds are there. I tried to restore the official firmware via flashtool, it didn't help. Rmx3242 . The display is original, not replaceable
rentest said:
Good afternoon, after the ota software update, the display stopped working, just a black screen, but the system sounds are there. I tried to restore the official firmware via flashtool, it didn't help. Rmx3242 . The display is original, not replaceable
Click to expand...
Click to collapse
You have to flash the stock rom including the ocdt.img, I had the same problem.
Did you ever solve your problem ? I'm experiencing something similar, the phone won't boot or charge
I've got something similar. The phone turn on, barely, and immediately turns off again. Gives a tiny vibration and turns off.
Only when on the charger, if it's not on the charger, no boot whatsoever.