Hey i got my Redmi 6 hard bricked after updating to Pie version while still having Oreo Recovery. I was in system then the phone rebooted and was vibrating for like 15 hours with a pause for 1 second every 15 seconds. There are 2 signs of life: 1. LED when charging 2. When holding power button i can pause the vibration for a second time.
No matter what combinations of Vol or Power i'll use, it will still vibrate-loop.
Edit: Solved, big thanks to djpsycho666.
Hey, could you help me out. I am having the same issues. Thanks!
Xiaomi Redmi 6 Hard Brick
How did djpsycho666 help you fix your Xiaomi Redmi 6? Did you have to pay him to fix it?
I have the same issue, how did djpsycho666 fix it????
Dutch Cortar said:
How did djpsycho666 help you fix your Xiaomi Redmi 6? Did you have to pay him to fix it?
Click to expand...
Click to collapse
I don't know how he fixed it, but definitely not for free.
TanRayCz said:
Hey i got my Redmi 6 hard bricked after updating to Pie version while still having Oreo Recovery. I was in system then the phone rebooted and was vibrating for like 15 hours with a pause for 1 second every 15 seconds. There are 2 signs of life: 1. LED when charging 2. When holding power button i can pause the vibration for a second time.
No matter what combinations of Vol or Power i'll use, it will still vibrate-loop.
Edit: Solved, big thanks to djpsycho666.
Click to expand...
Click to collapse
happens exacly the same to me, how did you solved it»?
thanks
It may not work for you, but for me dismantling the phone and unplugging the battery did the trick
TanRayCz said:
It may not work for you, but for me dismantling the phone and unplugging the battery did the trick
Click to expand...
Click to collapse
Like what does disconnecting the battery do? Is it not enough to unload it to the end so that it behaves as if it were not there? In my opinion, you need to have an authorized account, which is absurd because these are our phones and we don't have them, only a few people have them, it was my last phone xiaomi.
burzaa4 said:
Like what does disconnecting the battery do? Is it not enough to unload it to the end so that it behaves as if it were not there? In my opinion, you need to have an authorized account, which is absurd because these are our phones and we don't have them, only a few people have them, it was my last phone xiaomi.
Click to expand...
Click to collapse
It keeps draining the battery under 0%, you can notice the vibrations getting weaker but never stopping, after replugging to usb vibrations will regain full power again. In my opinion it acts as CMOS battery. In my case my battery was so undercharged that the phone took 5 minutes until it lighted up
TanRayCz said:
It keeps draining the battery under 0%, you can notice the vibrations getting weaker but never stopping, after replugging to usb vibrations will regain full power again. In my opinion it acts as CMOS battery. In my case my battery was so undercharged that the phone took 5 minutes until it lighted up
Click to expand...
Click to collapse
Disconnecting the battery does nothing. There are still only vibrations, no fastboot or anything else just black screen and vibration
burzaa4 said:
Like what does disconnecting the battery do? Is it not enough to unload it to the end so that it behaves as if it were not there? In my opinion, you need to have an authorized account, which is absurd because these are our phones and we don't have them, only a few people have them, it was my last phone xiaomi.
Click to expand...
Click to collapse
Hello Noob question - what is an authorised account? I've seen people talk about it when I was searching how to unbrick my Redmi 6! I'm getting an error 0xC0060005 in SPTool, and I think it's because I don't have an authorised account? What is it? I have my bootloader unlocked btw.
Tech_Expert said:
Hello Noob question - what is an authorised account? I've seen people talk about it when I was searching how to unbrick my Redmi 6! I'm getting an error 0xC0060005 in SPTool, and I think it's because I don't have an authorised account? What is it? I have my bootloader unlocked btw.
Click to expand...
Click to collapse
Let me guess you don't have a fastboot? just vibrations? error 0xC0060005 means that you do not have an authorized account. This account can be accessed by authorized services and only a few users can find one in this forum and one on 4pda. And they will help you, but I don't know for free. Since August I have been looking for a way to bypass error 0xC0060005 and find no solution.
burzaa4 said:
Let me guess you don't have a fastboot? just vibrations? error 0xC0060005 means that you do not have an authorized account. This account can be accessed by authorized services and only a few users can find one in this forum and one on 4pda. And they will help you, but I don't know for free. Since August I have been looking for a way to bypass error 0xC0060005 and find no solution.
Click to expand...
Click to collapse
Yes, just vibrations
Do all Xiaomi mediatek devices need an authorised account? And how come some versions of SP Flash that I can find online do not include the Mi Account signin window? Can you link me a proper SP Flash with signin support
reflash with sp flash tool ?!
Im in the same situation after flashing the boot sector. now i try to re-flash with sp flash tool but have error with the scatter file.
Boundary Check Failed: rom_end_addr >= next rom beigin_addr.
ROM(system): rom_end_addr(0x0000000130aadc23)!
Next ROM(cache): m_begin_addr(0x0000000111800000)
[HINT]:
Please select a valid load or ask for help!
Click to expand...
Click to collapse
If I ignore the message I've got a new error message :
ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00
Click to expand...
Click to collapse
Tech_Expert said:
Yes, just vibrations
Do all Xiaomi mediatek devices need an authorised account? And how come some versions of SP Flash that I can find online do not include the Mi Account signin window? Can you link me a proper SP Flash with signin support
Click to expand...
Click to collapse
I think all xiaomi phones without a fastboot will require an authorized account. This is due to their privacy policy. Even on Qualcomm processors, edl mode is blocked. Read here https://miui.blog/redmi-note-5/fix-arb-bricked-without-edl-whyred/. Even it did not work for everyone. Although I did not read about all the phones but certainly before buying another one I will read first if you can pick up a phone from a hard break without an authorized account. Here you have a splash toot https://drive.google.com/file/d/1x_aw56afOJGUsxu-oM-YSvNaOsEOF0NL/view I am not the author of this. Unpack it by clicking 5 times because it is deep. The original splash tool does not contain the "mi" folder because it is not only for xiaomi phones. DA & AUTH are on the hovatek forum but they don't give anything because we don't have authorized accounts. If you find a solution, share it.
---------- Post added at 09:35 AM ---------- Previous post was at 09:28 AM ----------
olivv17 said:
Im in the same situation after flashing the boot sector. now i try to re-flash with sp flash tool but have error with the scatter file.
If I ignore the message I've got a new error message :
Click to expand...
Click to collapse
There is https://drive.google.com/file/d/1x_a...aOsEOF0NL/view splash tool and scatter for redmi 6. and https://drive.google.com/file/d/1SLRIBwBBj3zGtnuWneQoqnTV8hc24aGB/view for redmi6a. Dump 5 times because it's deep.It doesn't work without an authorized account but maybe you will find a solution.
How to unbrick Redmi 6 without authorized account?
rusiu559 said:
How to unbrick Redmi 6 without authorized account?
Click to expand...
Click to collapse
If you don't have a fastboot, you won't do anything without an authorized account.
burzaa4 said:
If you don't have a fastboot, you won't do anything without an authorized account.
Click to expand...
Click to collapse
How to get authorized account?
---------- Post added at 09:33 PM ---------- Previous post was at 08:49 PM ----------
burzaa4 said:
If you don't have a fastboot, you won't do anything without an authorized account.
Click to expand...
Click to collapse
How to get authorized account?
rusiu559 said:
How to get authorized account?
---------- Post added at 09:33 PM ---------- Previous post was at 08:49 PM ----------
How to get authorized account?
Click to expand...
Click to collapse
you have to pay someone who has such an account you will find it in this forum.I won't fly because I don't know if it's effective. others say it helps.
please let me know how u fixed this issue. thank you in advance
Related
Some time ago I bought a Honor 6 bricked by a firmware upgrade.
I done some reading, I asked friends but I couldn't fix it. I opened a topic here and many people tried to help me. Nothing worked... I contacted some experienced people from this, and a Romanian forum, but no success. I was trying to fix it for 2 months now.
Eventually, I came across a solution made by DC-Unlocker Team.
I bought some credits to be able to run the solution and with a few mouse clicks my phone was repaired. Now it works perfectly. I do have some questions to ask about several issues in Honor 6, but let me describe how I fixed my phone with this solution.
I would like to underline that I am in no way related to the DC-unlocker Team.
The software can repair most of the Honor firmware problems:
Bricked phones, bootloop, stuck in fastboot mode
It can write full firmware update.app in fastboot mode
Can flash phones with locked bootloader or FRP. (No need to get the bootloader unlock code)
The whole procedure is detailed here, but let me describe the steps which I took. I also attach few screenshots of the process.
1. Make sure, that you install Huawei Hisuite (for drivers), or Universal ADB driver.
2 Enter fastboot mode on the phone and connect it to your computer. Remove the SD card if there is one installed in the phone.
3. Check if computer detects the phone is fastboot mode, run fastboot devices command
4. The firmware repair process will need 15 credits (which will cost 15 euro). You can buy the credits here
Credits are deducted immediately, but you can flash the same phone any time you want for 72 hours.
5. After you buy the credits, download the software client here
Supported models and features here
6. Start the program. It will ask your credentials for the DC-unlocker server. You receive those credentials when you buy the first time credits.
7. In the DC Phoenix software, select fastboot mode, select "App files" tab.
8. Carefully chose the update.app for recovery. Be careful, not to flash a different hardware variant (in a H60-L12 flash only H60-L12 firmware and so on). Not doing so will probably break your phone forever. The program does not check compatibility, nor the phone in this mode.
9. Open the update app by clicking right end of the line "Update file".
10 Click "Update". Program will unpack the update.app and will start to flash all the chosen img packs.
Here I got really scared, because first write was unscuccessful, I got this message: "PTABLE partition UPDATE ... FAILED
I thought that I threw away my money. But program managed really well: "Activating Backdoor: DONE"
After this step, everything went well: "Writing device finished OK"
11. Power cycle your phone. It should start normally.
12. On the dc-unlocker site they say: "Then you need to repeat flashing, but now in upgrade mode". I did not ran this step. I made a full factory reset and started OTA upgrades. Phone is now version: EMUI4.0.1_H-60-L12_6.11.1.
It has Android 6, EMUI 4.0.1.
At one moment I thought that is better to go back to a previous version and flashed an older tested firmware, it worked without any problems..
Although my experience is limited to this phone only, I recommend this solution. Please feel free to ask, I will try to answer any questions.
So the software deactivates itself after 72h?
zinko_pt said:
So the software deactivates itself after 72h?
Click to expand...
Click to collapse
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
But is there any refund in case it doesn't work?
zinko_pt said:
But is there any refund in case it doesn't work?
Click to expand...
Click to collapse
No, there are no refunds, but if you have a phone with only firmware error and you chose the right firmware, there are big chances that the program will recover your phone.
But if security damaged, you will need factory file.
method 2 can help in 99% cases, but only if there 100% compatible file.
They have only H60-L04 factory file.
Repairing by this method, will erase phone security data (simlock, IMEI and other numbers)
You will lose all numbers!, IMEI will be 0000000000000000
You can repair missing numbers with third party software, like HCU client
You can use DC-unlocker credits on HCU client, software will require 8 credits for repair service.
Thanks. When there's no other solution it might be handy.
i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?
Split74 said:
i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?
Click to expand...
Click to collapse
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos
janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
U shouldn't need to do this to flash back to stock. Sounds like a scam
Tmobilefan906 said:
U shouldn't need to do this to flash back to stock. Sounds like a scam
Click to expand...
Click to collapse
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.
janos666 said:
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.
Click to expand...
Click to collapse
It was my OPINION dude. Didn't mean to offend.
Tmobilefan906 said:
It was my OPINION dude. Didn't mean to offend.
Click to expand...
Click to collapse
Yep, the SW works OK ..
First it extracts the IMG files from the UPDATE.APP - same as Huawei Update Extractor. Then it flashes all IMG files (+-) using fastboot - but here is the catch.. it uses an undocumented feature of fastboot:
fastboot.exe oem backdoor get
And then generates the necessary unlock file/sequence which it then feeds to the phone using:
fastboot.exe flash slock XXX_Unlockcode.bin
So indeed it does work - I've used it, you can go between EMUI3.1 and 4.0/0.1 no problem - if we knew how to generate the unlock file for the "backdoor" - we would be all set However we don't and the generated file changes with every "oem backdoor get" request..
But 15EUR seems almost reasonable for this (I'd prefer 10EUR hehe) - otherwise, we would need to use parted and dd the necessary partitions which is more dangerous and we don't have a large enough community of users to dump the necessary partitions..
janos666 said:
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos
Click to expand...
Click to collapse
It worked! Fail on normal flash the It issued that damn BACKDOOR install and now i'm back!
Got only 2 "problems":
1. I got 2 IMEI CODES
2.I can't see all my internal storage:
I tried a wipe internal storage + factory reset with emui rec and with twrp, but nothing. TWRP say something like: Can't wipe ..data/... No such directory
Inviato dal mio PE-UL00 utilizzando Tapatalk
I will think about this issue, but a quick idea is: you could try a full firmware update from SD card with the 3 button method and a factory restore after.
Happy to hear that buddy... I threw away a honor 6 about two months ago, was stuck in fastboot for more than a month, if had it, I am sure, this would have fixed it.:crying:
Another Honor 6 saved with this method, this time a H60-L02
I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app
I can confirm i fix my Honor 6 hard brick with Dc Phoenix
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Lukalion said:
I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It was impossible for my L02 to be fixed using unbrick fuction of multi tool
You did not do the step i said in Edit
Sent from my H60-L04 using XDA-Developers Legacy app
My phone is nokia3.1plus,ta1104
i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
did u unlock the bootloader or root your phone?
if yes then its normal just wait for the countdown to end
thisbearisdrunk said:
did u unlock the bootloader or root your phone?
if yes then its normal just wait for the countdown to end
Click to expand...
Click to collapse
It's not the root warning, it's the fdp partition damaged warning!
dugu1248 said:
It's not the root warning, it's the fdp partition damaged warning!
Click to expand...
Click to collapse
I don't really know what's that but usually these kinds of warning appear if u unlocked bootloader or root Ur device
thisbearisdrunk said:
I don't really know what's that but usually these kinds of warning appear if u unlocked bootloader or root Ur device
Click to expand...
Click to collapse
If the warning doesn't have "g.co/ABH" URL displayed, but "please check lock status", then your FDP (not FRP) partition is corrupted, and you may have to replace the motherboard. Understand?
dugu1248 said:
If the warning doesn't have "g.co/ABH" URL displayed, but "please check lock status", then your FDP (not FRP) partition is corrupted, and you may have to replace the motherboard. Understand?
Click to expand...
Click to collapse
After 30 seconds, what happens? Does the phone boot? I think I agree with @thisbearisdrunk...that it's normal if the bootloader is unlocked. Where are you getting "g.co/ABH", FDP,and FRP from? I don't see those anywhere in your screenshot. Not that I am capable of helping you in any way, but I am curious.
If the phone boots and runs fine after the 30 second warning , then it's just the manufacturer covering his butt since you unlocked the bootloader.
If it, in fact, doesn't boot like the screen says, then you need help beyond what I can offer. Find the correct firmware and reinstall it, I guess.
mn1968 said:
After 30 seconds, what happens? Does the phone boot? I think I agree with @thisbearisdrunk...that it's normal if the bootloader is unlocked. Where are you getting "g.co/ABH", FDP,and FRP from? I don't see those anywhere in your screenshot. Not that I am capable of helping you in any way, but I am curious.
If the phone boots and runs fine after the 30 second warning , then it's just the manufacturer covering his butt since you unlocked the bootloader.
If it, in fact, doesn't boot like the screen says, then you need help beyond what I can offer. Find the correct firmware and reinstall it, I guess.
Click to expand...
Click to collapse
It just shutdown all the time, cannot boot. Reinstall stock firmware already,all passed, but the phone still shows that warning, after 30s it just shutdown, cannot load system.
How did it get to that state? Did you unlock the bootoader? Try rooting somehow? If under warranty, get it fixed/replaced.
mn1968 said:
How did it get to that state? Did you unlock the bootoader? Try rooting somehow? If under warranty, get it fixed/replaced.
Click to expand...
Click to collapse
Unlock failed ,the fdp partition damaged. Now it cannot boot.
dugu1248 said:
Unlock failed ,the fdp partition damaged. Now it cannot boot.
Click to expand...
Click to collapse
I don't know what's FDP partition I tried googling but still didn't find
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
dugu1248 said:
Unlock failed ,the fdp partition damaged. Now it cannot boot.
Click to expand...
Click to collapse
But what I was able to find was if u tried to flash something and something went wrong then there can be problem with partition getting corrupt
thisbearisdrunk said:
I don't know what's FDP partition I tried googling but still didn't find
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
But what I was able to find was if u tried to flash something and something went wrong then there can be problem with partition getting corrupt
Click to expand...
Click to collapse
Yes, downgrade from andoid 9 to android 8.1,it happens. The fdp.img must be ta-1104's. No one backup and release it.
dugu1248 said:
Yes, downgrade from andoid 9 to android 8.1,it happens. The fdp.img must be ta-1104's. No one backup and release it.
Click to expand...
Click to collapse
https://www.blogthetech.com/flash-file-nokia-3-1-plus-firmware-download-stock-rom/
This website has the android 8.1 firmware and tutorial on how to flash it
See if it helps
thisbearisdrunk said:
https://www.blogthetech.com/flash-file-nokia-3-1-plus-firmware-download-stock-rom/
This website has the android 8.1 firmware and tutorial on how to flash it
See if it helps
Click to expand...
Click to collapse
Helpless. I have tried all the rom from android 8.1 to 9, flashed all the firmware, all passed (successful),but that warning still shows, the phone shutdown after 30's , never boot.
dugu1248 said:
Helpless. I have tried all the rom from android 8.1 to 9, flashed all the firmware, all passed (successful),but that warning still shows, the phone shutdown after 30's , never boot.
Click to expand...
Click to collapse
I tried searching but I was not able to find ta-1104 firmware and I have the same model
I will try asking Nokia chat support
---------- Post added at 08:34 AM ---------- Previous post was at 07:59 AM ----------
dugu1248 said:
Helpless. I have tried all the rom from android 8.1 to 9, flashed all the firmware, all passed (successful),but that warning still shows, the phone shutdown after 30's , never boot.
Click to expand...
Click to collapse
r u able to boot into recovery or fastboot?
thisbearisdrunk said:
I tried searching but I was not able to find ta-1104 firmware and I have the same model
I will try asking Nokia chat support
---------- Post added at 08:34 AM ---------- Previous post was at 07:59 AM ----------
r u able to boot into recovery or fastboot?
Click to expand...
Click to collapse
Fastboot must be,or you can't flash rom. Recovery, never to be
dugu1248 said:
Fastboot must be,or you can't flash rom. Recovery, never to be
Click to expand...
Click to collapse
I asked in Nokia chat support they said that the device must be taken to nearby service centre
thisbearisdrunk said:
I asked in Nokia chat support they said that the device must be taken to nearby service centre
Click to expand...
Click to collapse
They said you must change the motherboard, yes? It can be fixed, but the nokia support won't release the solution.
dugu1248 said:
They said you must change the motherboard, yes? It can be fixed, but the nokia support won't release the solution.
Click to expand...
Click to collapse
They didn't say motherboard but yea it can be fixed all we need is the firmware but they won't give it
Does Ur pc recognise the device in fastboot mode?
Because when I connect my phone to pc in fastboot mode it doest recognise and the device does not show up in CMD when I type fastboot devices
hi I cant post in the other thread so i just posted here, by the way I've installed the latest system update yesterday which is the Realme UI 1.0 but there are so many bugs, I tried the q2p and p2q but the realmeui recovery can't seem to find the files (on internal storage only) so I can't proceed to downgrade, all it shows are random letters and numbers, anyone here willing to help me? I can't stand the bugs and the draining of my battery with my realme 5 pro now thanks.
This recovery has many bugs. We can't use internal memory for flashing any thing.
I always copy rom, gapps, magisk in the sdcard.
bahuy2003 said:
This recovery has many bugs. We can't use internal memory for flashing any thing.
I always copy rom, gapps, magisk in the sdcard.
Click to expand...
Click to collapse
but can I flash the ozip from sd card? seriously these guys are making it more complicated to mod your own device
You can flash OZIP rom if you use recovery Q (not realme 5 pro).
Sir remove you screen lock..then u can...I has tried it !
Niezammm said:
Sir remove you screen lock..then u can...I has tried it !
Click to expand...
Click to collapse
ill try later, tnx sir
mandarayaako said:
ill try later, tnx sir
Click to expand...
Click to collapse
so im glad i didnt do the q2p flashing because i figured out that it was only for realme 3 pro, though im still waiting for another fix, service center wont even downgrade their device because this is only sub brand of oppo, anyone if you know even how to unlock bootloader for realme ui please help
mandarayaako said:
so im glad i didnt do the q2p flashing because i figured out that it was only for realme 3 pro, though im still waiting for another fix, service center wont even downgrade their device because this is only sub brand of oppo, anyone if you know even how to unlock bootloader for realme ui please help
Click to expand...
Click to collapse
Really? Oppo service center wont downgrade realme 5 pro? Damn im planning to go at my nearest oppo service center to apply for a downgrade because realme ui sucks, not good at rhythm games.
Btw i email a service center they told me that as long as i have the requirements i can apply for a downgrade might as well take a shot and go to the my nearest service center
Ayachii said:
Really? Oppo service center wont downgrade realme 5 pro? Damn im planning to go at my nearest oppo service center to apply for a downgrade because realme ui sucks, not good at rhythm games.
Btw i email a service center they told me that as long as i have the requirements i can apply for a downgrade might as well take a shot and go to the my nearest service center
Click to expand...
Click to collapse
have you asked if it's really free? im planning to do so too
asd
Ayachii said:
Really? Oppo service center wont downgrade realme 5 pro? Damn im planning to go at my nearest oppo service center to apply for a downgrade because realme ui sucks, not good at rhythm games.
Btw i email a service center they told me that as long as i have the requirements i can apply for a downgrade might as well take a shot and go to the my nearest service center
Click to expand...
Click to collapse
yes that's what they told me, I even brought all my receipts and the warranty card, if ever you make them downgrade your device could you please tell me here? because im gonna file a complaint. thank you.
mandarayaako said:
yes that's what they told me, I even brought all my receipts and the warranty card, if ever you make them downgrade your device could you please tell me here? because im gonna file a complaint. thank you.
Click to expand...
Click to collapse
I just called Oppo's service centre here in Australia and they said they will do it if I send or walk in the device.
In my case, I'll wait to see if there is any alternatives as I don't want to spend $25 just for shipping, I'm in another city.
bahuy2003 said:
You can flash OZIP rom if you use recovery Q (not realme 5 pro).
Click to expand...
Click to collapse
Do you mean flashing through the stock file manager or realme recovery?
How do I know if I have realme Q or realme 5 pro?
All of realme service center here in Philippines is closed due to this pandemic and now i found the problem why i cannot play rhythm games,
Its because of this realme 5 pro ghost touch for god sake even my asus zen3 max a potato phone i can mobile games just fine, i swear this is my first and last buying of realme phone.
The only thing i could do now is wait...
I should"ve just buy a xiao mi instead of this phone
"Sign"
zedzded said:
Do you mean flashing through the stock file manager or realme recovery?
How do I know if I have realme Q or realme 5 pro?
Click to expand...
Click to collapse
in realme UI realme 5 pro recovery,u can flash .ozip too,i have try it today,but i put in sdcard coz in internal it cant be read.i had download firmware colosOS6 ( i forget the version ),when i try flash through stock file manager,nothing happen but when i try using recovery it work :laugh:,but it wont work,its stuck......:crying: try many time to reboot the phone,its work but its came back again to installer command.
finally when i push n hold the vol up+vol down+power button,my phone restart again,i wait it about 2mnt,at last my phone came back to normal.
i think its impossible to downgread or maybe theres is option for that until now
Ayachii said:
All of realme service center here in Philippines is closed due to this pandemic and now i found the problem why i cannot play rhythm games,
Its because of this realme 5 pro ghost touch for god sake even my asus zen3 max a potato phone i can mobile games just fine, i swear this is my first and last buying of realme phone.
The only thing i could do now is wait...
I should"ve just buy a xiao mi instead of this phone
"Sign"
Click to expand...
Click to collapse
You can discuss the address issue in private chat.. I thought I'll find anything useful here!!
---------- Post added at 11:53 PM ---------- Previous post was at 11:49 PM ----------
nesta526 said:
in realme UI realme 5 pro recovery,u can flash .ozip too,i have try it today,but i put in sdcard coz in internal it cant be read.i had download firmware colosOS6 ( i forget the version ),when i try flash through stock file manager,nothing happen but when i try using recovery it work :laugh:,but it wont work,its stuck......:crying: try many time to reboot the phone,its work but its came back again to installer command.
finally when i push n hold the vol up+vol down+power button,my phone restart again,i wait it about 2mnt,at last my phone came back to normal.
i think its impossible to downgread or maybe theres is option for that until now
Click to expand...
Click to collapse
I've tried installing the stock firmware from sdcard but through normal recovery you cannot downgrade the version. It's only meant for upgradation!!
hammad.mohsin said:
You can discuss the address issue in private chat.. I thought I'll find anything useful here!!
---------- Post added at 11:53 PM ---------- Previous post was at 11:49 PM ----------
I've tried installing the stock firmware from sdcard but through normal recovery you cannot downgrade the version. It's only meant for upgradation!!
Click to expand...
Click to collapse
btw have you figure out how to downgread to ColorOS 6 exccept go to service center?
The only way to downgrade is to go to service center
Its less headache than searching and doing random stuff
Its free of charge just bring in your proof of purchase or a warranty card or imei sticker
killerhaha100 said:
The only way to downgrade is to go to service center
Its less headache than searching and doing random stuff
Its free of charge just bring in your proof of purchase or a warranty card or imei sticker
Click to expand...
Click to collapse
yes but im my case they wont do it, ive sent email to realme about it but no reply yet, even so we are under quarantine ant cant get out of our town, and this may take a while
mandarayaako said:
hi I cant post in the other thread so i just posted here, by the way I've installed the latest system update yesterday which is the Realme UI 1.0 but there are so many bugs, I tried the q2p and p2q but the realmeui recovery can't seem to find the files (on internal storage only) so I can't proceed to downgrade, all it shows are random letters and numbers, anyone here willing to help me? I can't stand the bugs and the draining of my battery with my realme 5 pro now thanks.
Click to expand...
Click to collapse
Remove encryption
Hello! My device wifi just stopped turning on, and I did reset networking config but that didn't solve the problem, so I reset It. Now I have a device with no networking at all, and now it's also locked because I didn't sign out of my xiaomi account. I wanted to unlock the device and try another rom to see if that solves the problem, but I can't do that since I need first activate the device.
About the device:
-No root
-No developer options enabled
-Wifi doesn't toggle on
-Sim card is not recognized (already tried other ones, in both slots)
-Xiaomi assistance doesn't want to help me at all (neither the seller btw)
I hope you guys could help me. I'm very frustrated because it's a recent new phone :c
It maybe hardware issue
Nitin Rai said:
It maybe hardware issue
Click to expand...
Click to collapse
I'm praying not to be :c
vhviveiros said:
I'm praying not to be :c
Click to expand...
Click to collapse
Are you able to unlock phone. If yes then you can test the things through QC test by typing this in dialer *#*#64663#*#*
Nitin Rai said:
Are you able to unlock phone. If yes then you can test the things through QC test by typing this in dialer *#*#64663#*#*
Click to expand...
Click to collapse
I cant unlock it :c
But before messing with this lock, I tried to test wifi but without success...
As mentioned in a thread, an update could solve the problem, but I need to unlock the bootloader
vhviveiros said:
I cant unlock it :c
But before messing with this lock, I tried to test wifi but without success...
As mentioned in a thread, an update could solve the problem, but I need to unlock the bootloader
Click to expand...
Click to collapse
Have you thought about EDL or Test point method. I think it is the last option
Nitin Rai said:
Have you thought about EDL or Test point method. I think it is the last option
Click to expand...
Click to collapse
That one in settings > about phone > kernel press x5 > wifi
vhviveiros said:
That one in settings > about phone > kernel press x5 > wifi
Click to expand...
Click to collapse
By EDL, I mean a kind of brute force to flash ROM. Used mainly when hard bricked. As you don't have unlock permission you have to use this method to flash Factory ROM. You can find Instructions in YouTube videos for "Redmi Note 6 pro EDL flashing guide Test point method"
Nitin Rai said:
By EDL, I mean a kind of brute force to flash ROM. Used mainly when hard bricked. As you don't have unlock permission you have to use this method to flash Factory ROM. You can find Instructions in YouTube videos for "Redmi Note 6 pro EDL flashing guide Test point method"
Click to expand...
Click to collapse
Thaanks! I'll try It later and tell you if that solves my problem hahah
vhviveiros said:
Thaanks! I'll try It later and tell you if that solves my problem hahah
Click to expand...
Click to collapse
Ya. Tell us and Good luck
Nitin Rai said:
Ya. Tell us and Good luck
Click to expand...
Click to collapse
Thank you!
I've just bought a smartphone repair toolkit from Amazon, and I'm waiting for it because I don't have the needed tools to open the device and do the EDL by myself. It might get here around next week, and when done, I say if that worked.
Nitin Rai said:
Ya. Tell us and Good luck
Click to expand...
Click to collapse
I tried the EDL test points, but the device doesn't vibrate and turn on :c
EDIT: I was doing it wrong, I need firstly to connect the pins, and juts then connect the USB cable. I was doing the opposite hahaha
Windows Device Manager does recognize it, but Mi Flash still doesn't recognize the device on refresh, giving the error "length cannot be less than zero". I'm doing some search.
vhviveiros said:
I tried the EDL test points, but the device doesn't vibrate and turn on :c
EDIT: I was doing it wrong, I need firstly to connect the pins, and juts then connect the USB cable. I was doing the opposite hahaha
Windows Device Manager does recognize it, but Mi Flash still doesn't recognize the device on refresh, giving the error "length cannot be less than zero". I'm doing some search.
Click to expand...
Click to collapse
Try using another flash tool like Qfil
Nitin Rai said:
Try using another flash tool like Qfil
Click to expand...
Click to collapse
I read somewhere that the cause could be USB 3.0. So I tried on my laptop, and the flashing worked! Now networking is up again!!!
Obs.: I used the latest global stable ROM
Thank everyone for helping <3
Oh. Noice!
Nitin Rai said:
Oh. Noice!
Click to expand...
Click to collapse
Now I just don't want how to make as solved... is there a way? And a way to say that you helped to solve it
vhviveiros said:
Now I just don't want how to make as solved... is there a way? And a way to say that you helped to solve it
Click to expand...
Click to collapse
You can just edit the post and write solved if that's possible. No need to write my name..lol
vhviveiros said:
I read somewhere that the cause could be USB 3.0. So I tried on my laptop, and the flashing worked! Now networking is up again!!!
Obs.: I used the latest global stable ROM
Thank everyone for helping <3
Click to expand...
Click to collapse
Could you write your source, im nota ble to flash my phone in EDL mode, due to authentification issue ...
xer094 said:
Could you write your source, im nota ble to flash my phone in EDL mode, due to authentification issue ...
Click to expand...
Click to collapse
Actually, after flashing a new rom, after 12h the wifi issue returned, and I used this tool: https://www.xiaomitool.com/V2/
I used the option to flash an official rom, followed the app steps, and after the download finished, it couldn't be installed because of a bug So I repeated the steps, but instead of downloading again, i used the already downloaded rom (it is in the app installation folder). Then, success! Has been 2 days with no problem
About the auth itself, even by using EDL, after the reboot, I was prompted again by the mi account... So if you don't have the account, I'm afraid I can't help you... :c
I used this tutorial for the EDL: https://www.youtube.com/watch?v=7WfOprRVQww
My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
LinhBT said:
My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
Click to expand...
Click to collapse
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
rodken said:
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
Click to expand...
Click to collapse
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
LinhBT said:
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
Click to expand...
Click to collapse
It seems that your device is a candidate for a replacement if you cannot enter EDL.
rodken said:
It seems that your device is a candidate for a replacement if you cannot enter EDL.
Click to expand...
Click to collapse
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
LinhBT said:
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
Click to expand...
Click to collapse
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
This I know, but it applies for 8T more than OP8 since op8 only have one LPDDR4 variant, and also in the ops extracted image, there was only 1 xbl and xbl_config image, none xbl5. Thats why I feel weird.
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
LinhBT said:
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
Click to expand...
Click to collapse
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Daniha said:
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
Click to expand...
Click to collapse
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
rodken said:
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Click to expand...
Click to collapse
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
LinhBT said:
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
Click to expand...
Click to collapse
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
LinhBT said:
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
Click to expand...
Click to collapse
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
rodken said:
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
Click to expand...
Click to collapse
Sure man, just like before, based on the information I have from our forum, I was successfully restore a dead OP 8T TMO with Testpoint trick after few months after it bricked. That thread, I believe still somewhere at 8T Forum
Daniha said:
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
Click to expand...
Click to collapse
Pls kindly re-check my reply at #12
Anyone? Anyone have any information pls!!!
LinhBT said:
Anyone? Anyone have any information pls!!!
Click to expand...
Click to collapse
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Xryphon said:
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Click to expand...
Click to collapse
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
LinhBT said:
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
Click to expand...
Click to collapse
There is an interesting write-up regarding your issue.
Not to mention that there is the possibility of corrupting the Param Partition that will cause EDL to not function under the MSM Tool with the old param mismatch.