Related
After a lengthy discussion with some developers on this board, I'm going to try and see if it is possible to create a Gold Card for the Prophet.
This is a very low level process, so ONLY try to follow along if you really know what you are doing !!!
So, what are we going to do ? well, create an SD image to be able to un-brick a Prophet (hopefully)
As this SD image will try to circumvent the bootloader security it is called a Gold Card.
We will use itsme typhoonnbfdecode.pl to create this image. (Thx to itsme for his great tool set !)
Creating a "normal" SD Image isn't that hard, to trick comes when you need to fool the bootloader and bypass the security.
Steps:
1. Find out what your docuniqueid is (is not be needed, but nice to have anyway)
2. Find out what your cardid is
3. Change the first two digits of the cardid to 00
4. Find out which -p keys to use (my guess is tornado)
5. Extract IPL/SPL/GSM/OS/SPLASH from a original ROM for the correct model (G3 or G4)
6. Use typhoonnbfdecode.pl to create and SD image (gold card)
7. Test the sucker in my bricked G3
So, let's try to get something working:
I will skip step 1 for now as Its not needed.
2. To get the cardit we need to read a memory dump from another Prophet with the sd card inside
pmemmap -s 0x06000000 -w deviceexe.mem -p 0x10000000-0x12000000
we are dumping the section of memory where device.exe is running (you can check this with pps)
In this memory dump we search for the unicode string 'Memory Card'
This is where I am at the moment, as the above was done on another HTC device I think I need to search for a new mem location where the cardid is stored.
So any people reading this that know another way of getting the sd cardid, let me know.
Example cardids:
# 55 4500 accf6300 55 3832314453 4453 03 'UE...c.U821DSDS.' .. my minisd
# 3f 5100 09531f40 03 424d383231 4e49 18 '[email protected]' .. my kingston
# 3f 3c00 65ba4764 07 3832314453 4d54 02 '?<.e.Gd.821DSMT.' .. my daneelec
# 00 4200 0f588942 41 4238323153 4150 01 .... bjorns sdcard
glad to help you
glad to help you un-brick your phone but need more details on these steps.
I am not a programmer so you'll have to explain more.
I do generally pick up these things quick, but will need to point me in the right direction.
AbuYahya said:
glad to help you un-brick your phone but need more details on these steps.
I am not a programmer so you'll have to explain more.
I do generally pick up these things quick, but will need to point me in the right direction.
Click to expand...
Click to collapse
Don't worry, I will update as I find out more
Hi,
Few months back I tried to make one for my Device but was unsuccessfull as I was not able to get DOC uniqueID and finding SD Card's unique ID is hell of a JOB.
So I Quit at that time but after seeing your post, I am again feeling energetic.
However the only method I know is as under.
Dont remember the exact location but will let you know (Taken somwhere from XDA Forum)
Finding out the docuniqueid
it is in memory at 0x8e01509c:
pmemdump 0x8e01509c 0x10
alternatively you can use this:
pdocread -l
Finding out the cardid (this is more difficult)
first find out the section of device.exe with pps usually it is 0x06000000. then save this section to a file using:
pmemmap -s 0x06000000 -w deviceexe.mem -p 0x10000000-0x12000000then in this memory dump, search for the unicode string 'Memory Card':
findstr "Memory Card" deviceexe.memthen dump the memory starting 0x18 bytes before where memory card was found:
dump deviceexe.mem -o 0x90a2a0 -l 0x90this results in something like this:
0090a2a0: 53 42 44 53 ec 00 00 00 f0 6f b7 03 00 00 00 00 SBDS.....o......
0090a2b0: 68 ea 8f 00 00 00 00 00 4d 00 65 00 6d 00 6f 00 h.......M.e.m.o.
0090a2c0: 72 00 79 00 20 00 43 00 61 00 72 00 64 00 00 00 r.y. .C.a.r.d...
0090a2d0: 63 00 65 00 30 00 00 00 00 00 00 00 00 00 00 00 c.e.0...........
0090a2e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090a2f0: 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 ................
0090a300: 30 b1 90 00 68 bf 90 00 70 12 b5 03 5c a9 00 80 0...h...p...\...
0090a310: ff 00 00 00 00 55 45 00 ac cf 63 00 55 38 32 31 .....UE...c.U821
0090a320: 44 53 44 53 03 ab 40 40 92 ff 4f fa fe c0 83 59 [email protected]@..O....Ynote: that the SBDS signature needs to be there.
the 16 bytes starting at 0x90a315, 55 45 00 ac ... etc are the cardid.
DoCtOr_X said:
Hi,
Few months back I tried to make one for my Device but was unsuccessfull as I was not able to get DOC uniqueID and finding SD Card's unique ID is hell of a JOB.
So I Quit at that time but after seeing your post, I am again feeling energetic.
However the only method I know is as under.
Dont remember the exact location but will let you know (Taken somwhere from XDA Forum)
Finding out the docuniqueid
it is in memory at 0x8e01509c:
pmemdump 0x8e01509c 0x10
alternatively you can use this:
pdocread -l
Click to expand...
Click to collapse
If you look at my post above you can see I'm doing the same
however, pdocread on a bricked phone obviously doesnt work, however the docuniqueid MIGHT not be needed.
for cardid is trickier, as the cardid seems to be hidden on a different memory location then normal (read, older devices)
I'm trying serveral things to get to this
I just bought a new cardreader, so I can continue testing this
Hi,
Wish u best of luck but unfortunately I have no success.
Any Success ????
working on something that might get us a working gold card
stay tuned
Ok, it's possible to create a gold card, meaning, that I can create an SD that will lower the sec level to 0
This is nice, however doesn't help (yet) with the G3/G4 wrong SPL problem.
But it is one step closer as it is now confirmed that you lower the sec level using this method.
Next step will be to see if I can "update" an existing G3 SD Image with the cardid of my card and get it to boot.
I know it might not make sence what I'm saying now, but it's just an update on the progress made so far, and yes I will update the first post with a how to.
more later.
Nice, keep up the good work!
Well Done, I am really amazed.
Thanks & please keep it up.
So am I understanding that right you need another htc which is working to get the cardid? Is it possible to get all that done just with a regular cardreader plugged into the computer?...
cr0ssy said:
So am I understanding that right you need another htc which is working to get the cardid? Is it possible to get all that done just with a regular cardreader plugged into the computer?...
Click to expand...
Click to collapse
It MIGHT be, but I haven't tried that yet
Huh they are very similar
Hi Jesterz so far I have the same problem as you are with my dev g3
with spl from g4
So did you get your device to boot or what ideas do you have
Maybe this will help us Customize_rom_PDAMobiz_Editon_Upgrade_Rom_for_IPLSPL_2.15.0001_v.1.02
Help
Dear Jesterz, could You please help me.I used your RUU-Prophet-g4-AKU2.2-2.20-2.47.21-Jester-r1 to flash my G3 so i did not read carefully your post. It passed but device stills in bootloader mode. Is it possible to solve my problem and how.I have not other prophet to make goldcard. Tnanks in advance
mjankovic said:
Dear Jesterz, could You please help me.I used your RUU-Prophet-g4-AKU2.2-2.20-2.47.21-Jester-r1 to flash my G3 so i did not read carefully your post. It passed but device stills in bootloader mode. Is it possible to solve my problem and how.I have not other prophet to make goldcard. Tnanks in advance
Click to expand...
Click to collapse
Now u must also wait for GoldCrad project....
Yes thank you very much doctor_x so would you please let me know where it is finish and where i can find it
Hi,
If I'm not missing anything, there are actually two types of ID's for SD cards:
1. "Hardware ID", that is truly low-level and is provided by the card manufacturer.
You can use Pocket Mechanic to read it, but I have no idea how you can manage to change it. Please let me know if you have a solution on this one.
2. Let's call it "software id" - an id that you get after your card is formatted (something like a partition id) - you can use a card-reader and some software like Acronis Partition Expert to read and change it.
mjankovic said:
Yes thank you very much doctor_x so would you please let me know where it is finish and where i can find it
Click to expand...
Click to collapse
The main person involved in this project is "Jesterz". I was about to gaveup when jesters started new effort and infused new spirit in the project.
Now lets hope it works but uptill now no breakthrough.
I read somewhere that I dont have to SUPER CID to install a 3rd party ROM, or perhaps our WM6 ROM
"Here is how I got the rom to install without the devauth error.
1) use a hex editor on the rom file and search for the devauth.exe string e.g. 44 00 65 00 76 00 41 00
2) between the "devauth" and the "exe" you will see the hex "00 2e".
3) swap these bytes around so they are "2e 00" instead of "00 2e".
4) This will keep te same checksum but will not allow the devauth.exe to run. well it work in my case at least"
Hope it works
Click to expand...
Click to collapse
Will the above method works? because my phone is still under warranty, and i dont want to void it so early
Hi,
I've been trying to connect my Imate jamin with blackberry connet (BES) in vain... I've read that it works... but even the best explanation leaves me stunned (me a Nube) could some one help me solve the mystery??? the write-up from the forum is also attached (green fonts) below... This seemed to have worked for universal...
OK folks, I've got it done. BBC is finally working in WM6 on my Universal...
I was able to prove my theory about the pseudo random os version string. If you have the right string, BBC will work with every ROM.
Here are the steps you need to do in order to get it working (shown on the example of WM6 (J.Wright's last ROM 2.01.08 and BBC 2.1.2.31):
1. Use the famous HTC64 Extended ROM Tool to decode the .nbf from the above ROM
2. Open the resulting .fat (or .nba) file with your favorite HEX-Editor
3. Search the follwing hex value (there will be two locations for this, you have to edit both of them)
4F 3F A0 E3 02 30 83 E3 45 2F A0 E3 05 10 A0 E3 02
4. Change it to:
C3 30 A0 E3 02 30 83 E3 45 2F A0 E3 05 10 A0 E3 01
5. Save the changes to your .fat (or .nba) file
6. Use the famous HTC64 Extended ROM Tool again to encode the file back to a .nbf file (ignore the warning about to big .fat file)
7. Flash the .nbf to your device
8. After flashing use a registry editor and go to the following key:
HKLM\System\Versions and edit the Aku string from .0.0.0 to .2.0.0
9. Reboot and install the blackberry connect client
10. From here on do the same steps that nessecary on a normal BBC install
11. You're done..it should work now
The above hex-magic patches the coredll.dll from OS Version 5.2.318 to 5.1.195. In combination with BBC Version 2.1.2.31 this will result in a pseudo random os version string that is allowed to connect to the blackberry network.
Have fun!
Cheers
Pls help... my work demands That I go back to BlackBRICK!!! I guess I am a PPC fan
Pls help!!!
Can someone pls help...
I got a new Photon Q from USA
This is my first CDMA phone
I am trying to get it on Reliance CDMA network INDIA.
So, i am trying to edit settings via QPST
Accidently i selected NAM2 which was blank, No settings and phone numbers.
Now phone is trying to start with NAM2 and now it stuck on "Starting Service".
Only phone settings are access able form sliding bar, but IMEI, ESN are blank and baseband is unknown.
Phone is unrooted and running on Stock 4.1.2
Is there any way to get NAM1 back?
will Stock firmware flashing restore it?
This, almost exactly, is happening to me. See thread: forum.xda-developers.com/showthread.php?t=2436869&page=1
Stuck at Starting Services. I don't have a mobile carrier, that is fine, I only use Wifi. But Wifi and BT are both not working. If I hit ON, they turn back off instantly. Cna go to notification bar and settings only, homescreen won't appear, apps won't run. Thanks to anyone for any help!
It is not the same as you didn't use QPST and your phone isn't screwed.
Back to your thread, there you'll get an answer.
@lovepreet39, I'll look into QPST (again, so not my first time) but I won't try anything out, so I will only guess what you could do.
QPST is a powerful tool, trying anything around there might break the phone.
Epicenter714 said:
This, almost exactly, is happening to me. See thread: forum.xda-developers.com/showthread.php?t=2436869&page=1
Stuck at Starting Services. I don't have a mobile carrier, that is fine, I only use Wifi. But Wifi and BT are both not working. If I hit ON, they turn back off instantly. Cna go to notification bar and settings only, homescreen won't appear, apps won't run. Thanks to anyone for any help!
Click to expand...
Click to collapse
Please quit cross-posting. You've already created a thread dedicated to your issue, which is really all you needed - cross-posting dilutes the community effort, and we have quite a small community here.
I just flashed firmware again with RSD lite. Now phone booting properly and all features are available.
But it becomes useless because IMEI and MEID becomes zero.
I tried QPST, CDMA TOOL, CDMA Workshop
But i unable to restore MEID.
Please any body here tell me how to restore MEID/IMEI
What happens if you select NAM1 again?
Have you made a backup of your configurations? (That was the first thing I did.)
Loader009 said:
What happens if you select NAM1 again?
Have you made a backup of your configurations? (That was the first thing I did.)
Click to expand...
Click to collapse
Now NAM1 and NAM2 both are blank, i have a NV item backup but restoring it does not do anything.
Is there any way?
I want my ESN/IMEI/MEID back.
It is a new phone and now it becomes useless.
Update, It is connecting to wifi, but not receiving any data, a mark on wifi is blinking on wifi symbol.
Same wifi is working on my HTC one x
Theoretically you could try to modify the MAC-Adress of wifi and bluetooth etc. (just make sure it begins with the right symbols from the manufacturer).
This is only a temporary solution. (Mine begins with 80:96:B1:XX:XX:XX for both, wifi and bluetooth.)
My IMEI isn't printed anywhere if I remove the backplate. (Also not under the battery and the plastic plate.)
So if nobody knows where it could physically be, then there might be no way to get it. Except if you have the boxing, there is a chance that it's printed somewhere there.
If you have a backup, there may be a way to get it from there, I made both backups, the simple one (49KiB - modified, 48KiB unmodified) and the EFS-backup (496KiB - modified, no unmodified EFS-backup).
I'll test some programs from QPST and post the results.
edit: I might have found "part" of the IMEI.
Using the QCNView program from the QPST software pack I found a partial match to my IMEI.
Load the program, load your backup (make a backup of your backup! Just in case.)
Expand the "NV Items:" and scroll down to item #550 "NV_UE_IMEI_I".
Code:
Adress 0 1 2 3 4 5 6 7 8 9 a b c d e f
NV_UE_IMEI_I 0: ab cd ef gh ij kl mn op qr st uv wx yz AB CD EF
This is a hex-styled code table. The first line "Adress" isn't shown, it's for orientation.
My IMEI is partially build out of this table: _fghijklmnopqr_
Those two underlines "_" are not given in this table.
I think the first number is for the manufacturer and the last for variations. (You might have to research further for this.)
This way you have your IMEI nearly completely. But I'm not sure for MEID and ESN.
First number is 9 (it starts with "99") and last number is checksum (see Wiki), it's present only in IMEI and not MEID.
There is no problem with wifi MAC address, it is connecting without any problem, but not receiving any data.
and i have original box with original MEDI/IMEI on that.
But problem is that CDMA tools are failed to restore that.
Please first tell me what happens to wifi, why it is not receiving data?
and is there any way to restore original MEID/IMEI?
Keep in mind i know original MEID/IMEI
If the MAC address is given correctly you should receive data over Wifi.
I don't know any reason why it shouldn't work since it has nothing to do with the rest.
Maybe the whole SoC is a bit malfunctioning as some data is missing and... I can just guess, I'm not a pro in linux or android.
I'll look into QPST later again, maybe there is a way to type the MEID in somewhere.
(I have to flash between cm10.2 and stock JB, that's why I don't do it right away.)
Yay, double post!
I researched a bit, we need access to the "nvm" folder withing the EFS Explorer.
The "open sesame door" trick does not work, so I have no idea how to get access.
I'm searching for another solution but I think I won't find anything useful.
edit: Maybe this will work -> http://www.letitgrow.co/forum/viewtopic.php?f=40&p=183
Not tested. QXDM -> http://d-h.st/FW5 (Tested it right now, it's really for WinXP >.< Internet Explorer 6 or higher is needed O_O)
edit2: Using QCNView I also find "NV item: 1943" "NV_MEID_I". (Only in full EFS backup!)
The question is, how to get it on the phone. Maybe it will work to make a full EFS backup, modify (somehow, texteditor?) the file and reflash it.
But i do not have a EFS partition backup
I only have NV items backup.
and i already tried QPST on stock 4.0.3, It is not working.
I also tried Bluetooth, It is connecting to other devices, but not receiving any files/data.
This clearly shows there is something corrupted.
may be EFS partition is corrupted.
Any one here please give me a EFS partition backup and guide how to restore it.
For backup and restore you may use QPST Software Download.
Type in the SPC and choose the location for the file.
The program is self explanating, if you don't understand something, just ask.
I agree that something have to be corrupted but for now we should try to get MEID (and maybe ESN) back working.
With some luck the SoC needs these data to function correctly. If not, we may need to dig deeper.
But my knowledge was (at the beginning) only changing the UMTS used frequencies (that's what I used QPST for).
So I'm on explore and try. (And I'm using google to search for ways to restore ESN/MEID.)
Please note, a modification of the full EFS backup may not work, I'm sure there are some checksums somewhere to prevent corruption.
But that's the only way I see, without access to the nvm folder within the EFS Explorer.
As soon as the MEID/ESN/IMEI is working correctly again I recommend to flash the FXZ file, this may be enough to get everything working again.
edit: Please note, any backup withing QPST (especially EFS and NV items) may contain MEID/IMEI/ESN.
You should never share it unless you know what you are doing. That's why I do not share my backups.
I am india, if you are living outside india, then please share ESF with me via email.
Sharing is safe if you are not in india.
and i am on stock refresh rom.
Full name : asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US.xml
Now Connected to QPST, please tell me how to backup and restore.
Update: 1
i mada a backup
in QCNviewer, first item indicare ESN, but all zeros
Mobile Properties:
ESN: 0x00000000
Phone Model: 255 [Unknown Model]
NV Major: 0
NV Minor: 0
SW Version: M8960A-AAAANAZM-1.0.103205
Client Name: QPST Software Download 2.7.0.264
NV item: 0 [NV_ESN_I], index 0
NV_ESN_I 0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NV_ESN_I 1: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NV_ESN_I 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NV_ESN_I 3: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NV_ESN_I 4: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NV_ESN_I 5: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NV_ESN_I 6: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NV_ESN_I 7: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
and "NV item: 1943" "NV_MEID_I not found
Update 2
I checked my old original backup which is made by NV-items_reader_writer
NV item: 0, have some values which is non zero.
and NV item: 1943 is also present and have non zero values.
So, i tried to restore with NV item r/w
Complete items - 1922
But after restore it alerts
1915 items has been restored sucussfuly
My phone number and some other settings return to old.
But MEID/IMEI is still zero
Update 3
I tried CDMA tools and also tried to restore NV items.
But Unable to restore MEID/IMEI
I think it is due to Locked nvm folder.
Is there any way to unlock it?
I'm sorry but I won't share my EFS backup.
As I said you could try to modify your EFS backup with a hex editor.
This way you would modify the ESN and MEID and try to flash it back.
Please tell me which hex editor you use so I can give you the exact position of MEID and ESN.
You will modify these and look if the modification is a success.
If it's not, a modified EFS backup won't work.
Theoretically an unmodified backup may work, but I won't give my EFS backup.
I guess (as you too) that the nvm folder is locked and modifications on IMEI/MEID/ESN are not possible at the moment.
The trick (earlier) was to make a folder called "open sesame door" at root and then reboot but I tried this and it don't work.
You are right this trick is a fail for Photon Q.
As, i said i tried to restore my old backup which has IMEI,MEID,ESN.
But failed.
I think some nv items like MEID,IMEI,ESN are only readable, not writable.
The only way is to make them writable.
Only a linux/android can tell how a folder can be unlocked.
Phone is not accepting IMEI/MEID from original backup, so HEX editor is also use less.
Main problem is that NV item 1943 is missing from the phone.
Update 1:
I am not a expert
But this is my imagination
If we can find efs partition via ADB in pc
and then edit and replace it.
I searched google, there are some guides for efs fix via adb for samsung.
We can also chmod folder and files in adb.
So, may we chmod nvm partition in adb?
i think a root is required for that
We can simply use some commands
like cp, pull, push
what do you think?
That is an idea but I doubt that it will work.
Still worth a try.
Maybe this will help you to find out which partition your are looking for
-> http://forum.xda-developers.com/showthread.php?t=1959445
Looking at this tutorial (thx zodiac12345 for posting it) -> http://www.cricketusers.com/sprint-...-q-4g-lte-cricket-talk-text-mms-internet.html
There is a Video under "Send NV Items / QPST" and at 4 minutes he is going to do something I didn't do.
I don't know what for he is doing it but it seems to be necessary.
Maybe this will unlock the nvm folder but I haven't tested it. (Too lazy to flash Stock again.)
My mobile phone is Xiaomi 5s plus (natrium) , no repair, It was a little slow with MIUI 9, so I changed to Lineageos 15.1, there is allways "no emergency calling" notification with Lineageos15.1(it turned out that is because of my china-unicom sim card) , so I change back to MIUI 9 again. the flash process was a little slow with miflash.exe, normal before is about 200s, but this time is about 400s, and all the later flash with miflash.exe is slower than the normal(from 400s to 1000s).
Now there is a new and serious problem! the phone will became very very slow suddenly, during problem, when I make a call, it was so slow that I must wait about 10 second or more before I input next number. both with MIUI OS and Lineageos, but when I "format" the whole internal storage under TWRP and install a clean ROM or simply reboot, the phone works fine.
who can do me a favour and tell me, Is this phone's UFS flash have bad sector? or something else problem?
Nothing is wrong with your phone since you stated that making a clean flash fixes it for you. Also you should flash latest developer firmware in order to use LineageOS without having problems. Also unencrypted storage might be more efficient."Format Data" from TWRP for unencrypting your storage.
Sent from my Xiaomi MI 5s Plus using XDA Labs
khanjui said:
Nothing is wrong with your phone since you stated that making a clean flash fixes it for you. Also you should flash latest developer firmware in order to use LineageOS without having problems. Also unencrypted storage might be more efficient."Format Data" from TWRP for unencrypting your storage.
Click to expand...
Click to collapse
Thanks for your reply.
I have download the miui 9 -8.1.4 version Rom, LineagOS 15.1 is based on this version, I have flashed this version modem pack only, ortherwise, Lineageos15.1 can't be installed. this time I'll make a full official rom flash and clear all data with miflash.exe.
I have had many tries, the phone still random suddenly hangs, after problem happens, I must format whole data parition under twrp and reboot, then the phone works like a charm. I doubt there are some bad block on system partition. so I delete this partition (/dev/block/sde39), and create another one on /dev/block/sda15 (original sda15 is userdata, now became sda16),but no use.
acording to dmesg log, maybe the problem is on sda,not on sde?
...........
[ 356.430125] sd 0:0:0:0: [sda] CDB:
[ 356.430129] Write(10): 2a 00 00 79 25 00 00 00 80 00
[ 356.430145] ufshcd 624000.ufshc: UPIU[10] - issue time 326208897 us
[ 356.430151] ufshcd 624000.ufshc: UPIU[10] - Transfer Request Descriptor [email protected]
...........
here is the full dmesg log file View attachment dmesg_log_hangs.zip
who can do me a favour?
tournet said:
I have had many tries, the phone still random suddenly hangs, after problem happens, I must format whole data parition under twrp and reboot, then the phone works like a charm. I doubt there are some bad block on system partition. so I delete this partition (/dev/block/sde39), and create another one on /dev/block/sda15 (original sda15 is userdata, now became sda16),but no use.
acording to dmesg log, maybe the problem is on sda,not on sde?
...........
[ 356.430125] sd 0:0:0:0: [sda] CDB:
[ 356.430129] Write(10): 2a 00 00 79 25 00 00 00 80 00
[ 356.430145] ufshcd 624000.ufshc: UPIU[10] - issue time 326208897 us
[ 356.430151] ufshcd 624000.ufshc: UPIU[10] - Transfer Request Descriptor [email protected]
...........
here is the full dmesg log file View attachment 4517789
who can do me a favour?
Click to expand...
Click to collapse
got the same issue with my friend's Mi5 (not S Plus) that turned out the PowerIC is broken & need replacement...