Database Info

my phone freeze and restart itself

Hello,i turn of my phone and after 2 hours i open it. From that moment my phone crashes ( freeze ) all the time and restart itself,i already change rom i flashed "A850_23.10.2013_RUS_by_linerty" and "A850-Stock-S123" but nothing happend,what can i do ???

dinossp said:
Hello,i turn of my phone and after 2 hours i open it. From that moment my phone crashes ( freeze ) all the time and restart itself,i already change rom i flashed "A850_23.10.2013_RUS_by_linerty" and "A850-Stock-S123" but nothing happend,what can i do ???
Click to expand...
Click to collapse
If you have flash those roms without installing anything and you always have that problem, then i sounds like a hardware problem...

GreatApo said:
If you have flash those roms without installing anything and you always have that problem, then i sounds like a hardware problem...
Click to expand...
Click to collapse
yes i think that too.
do you know if i can find parts ( like mtk chip) in market?

dinossp said:
yes i think that too.
do you know if i can find parts ( like mtk chip) in market?
Click to expand...
Click to collapse
If you have the phone less than 6 months you can contact your Chinese seller (but be careful with the day because if the 6 months pass they will not replace it + you will be charged with the mail).
I am not a Phone Engineer so i can't help you change your chips (and you do not know if that is the problem...), plus, do you have the equipment to do so?
If i where you i would try a local phone repair shop, ask for the charge and decide if you want to fix it or take a new phone.

ok maybe i will repair my phone in local shop.
thank a lot for reply :good:

could be kernel's problem??? (i dont know much about kernel)

dinossp said:
could be kernel's problem??? (i dont know much about kernel)
Click to expand...
Click to collapse
I do not thing so... there are not custom kernels for our phone yet and i am not sure but flash tool may flash that too.

GreatApo said:
I do not thing so... there are not custom kernels for our phone yet and i am not sure but flash tool may flash that too.
Click to expand...
Click to collapse
i solve the problem.
a smd from audio jack circuit was dead i just removed and my phone is back to life now (my audio jack is dead but i will try to fix it as soon as possible).
thanks again for your help :good:

dinossp said:
i solve the problem.
a smd from audio jack circuit was dead i just removed and my phone is back to life now (my audio jack is dead but i will try to fix it as soon as possible).
thanks again for your help :good:
Click to expand...
Click to collapse
hi dinossp,
could you give me more details on how you fix the phone?
i have the same problem and not fixed yet. i had changed to other rom but still no luck.
it keeps freezing and restarting
thank you

Cannot get bootloader to work on PX3 MTCD with 7.1.2

Hi, have a PX3 MTCD unit with 7.1.2. It is a unit with only a screen and a separate system box, no buttons, only reset button. It's got 3 USB female cable connections as a HOST.
Managed to get in with SDK/adb. In factory settings first put in 'abdon' (otherwise USB connection stays as a HOST and won't work) and the PX3 turned up on my windows PC. Also debugging in developers menu.
By the way, the rooting command in factory settings '*#hct#root# does not work, it says 'wrong password'.
Problem with 'developers menu' is that it is not standard in the system menu and cannot be activated the normal way (tipping built number). With Totalcommander I have to activate developer settings every time after a system start.
Can get into recovery with the command 'adb reboot recovery'. But then I cannot use adb(SDK) anymore. It does not see the device, not with adb or fastboot. The windows PC can see the PX3 but not as a normal usb connection. In windows devicemanager it is to be seen as a separate Rockchip USB connection??
Then did 'adb reboot-bootloader', it restarts but I get a black screen. Also, adb (SDK) does not see any device? Windows does see the device as mentioned above.
Also tried Kingoroot with the windows PC and on the system but it only makes a halfroot.
Can anybody help?
My goal is I want to make a backup ROM image before installing the Malaysk 7.1.2 ROM. The stock ROM for my unit is not available. Asked them in China but they do not respond.
This is the unit I have:
https://nl.aliexpress.com/item/Quad...lgo_pvid=835f065f-22af-4a45-9a17-704a7ccdeaf5
It looks exactly as the one from Seicane:
https://www.seicane.com/android-hd-...hd-1080p-video-steering-wheel-control-s018848

After searching on the net I'm one step further. Downloaded Rockchip drivers and a softwaretool called AndroidTool. This tool can make a romdump.
After giving the bootloader command (and a black screen) I can connect with AndroidTool and it recognizes the PX3 unit and can read the ID.
So, somehow I'm in bootloader mode but with a blackscreen and SDK/adb not working.
I have to read first how to make the romdump with AndroidTool and going to try this week.
All help is welcome.
Next day:
Did a successful Romdump :laugh:

Nice work dude! I was having trouble getting ADB to work right over USB or WiFi, so I gave up on the backup. Luckily I found a clean updated stock rom for my unit and just went ahead and flashed Malaysk's.

And installed Malaysk Rom

pgee said:
With Totalcommander I have to activate developer settings every time after a system start
Click to expand...
Click to collapse
Can you explain this more? I cannot get into Developer Settings on a Px3 MTCD 7.1.2 either and don't know how to do it with TotalCommander.
Thanks

mbr11 said:
Can you explain this more? I cannot get into Developer Settings on a Px3 MTCD 7.1.2 either and don't know how to do it with TotalCommander.
Thanks
Click to expand...
Click to collapse
Hi,
Developers settings is hidden and I think USB debugging standard is already on. But I'm not sure about this, so I found this way to activate it.
In Total Commander's menu there's a white + (see image), choose this and you get a menu to add/edit button:
Choose function type; App start
Write the following in Command; settings:com.android.settings:.DevelopmentSettings
No parameters needed
Then hit OK/apply
If you did it correct there will be a new button (mostly the map button) in the menu on the bottom. Push it and you will be in the developers settings menu.

mbr11 said:
Can you explain this more? I cannot get into Developer Settings on a Px3 MTCD 7.1.2 either and don't know how to do it with TotalCommander.
Thanks
Click to expand...
Click to collapse
please, you can explain the process.
I have factory image HLA 7.1.2., Mercedes Benz class E. I can upload it if needed.
Regards,

xirix22 said:
please, you can explain the process.
I have factory image HLA 7.1.2., Mercedes Benz class E. I can upload it if needed.
Regards,
Click to expand...
Click to collapse
What part do you want me to explain?
Got a Rom update from the manufacturer yesterday, also a mcu update, thanks.

pgee said:
What part do you want me to explain?
Got a Rom update from the manufacturer yesterday, also a mcu update, thanks.
Click to expand...
Click to collapse
Hi again, I can not install the drivers. I have w10. You can send me the driver package. The computer does not recognize the unit.
You can help?
Thank you
Sorry for the English (google)

xirix22 said:
Hi again, I can not install the drivers. I have w10. You can send me the driver package. The computer does not recognize the unit.
You can help?
Thank you
Sorry for the English (google)
Click to expand...
Click to collapse
I did it with windows 10.
Try this https://freeandroidroot.com/download-rockchip-driver-assistant/

pgee said:
I did it with windows 10.
Try this https://freeandroidroot.com/download-rockchip-driver-assistant/
Click to expand...
Click to collapse
Thanks for the reply. But I still can not install the drivers

xirix22 said:
Thanks for the reply. But I still can not install the drivers
Click to expand...
Click to collapse
What's your goal? If it is a Romdump there are enough stock Rom's available.
I recently got a stock Rom from the manufacturer for my HLA unit. Also a update for the MCU.

pgee said:
I recently got a stock Rom from the manufacturer for my HLA unit. Also a update for the MCU.
Click to expand...
Click to collapse
I have a HLA unit but i have no stock rom. Where did you downloaded it?

kekoha said:
I have a HLA unit but i have no stock rom. Where did you downloaded it?
Click to expand...
Click to collapse
Asked Seicane with the chat function on there site. I still have that Rom if you want it.
To download nupdate en dmcu:
https://drive.google.com/open?id=1DG_G_zn1E57rmo9zv_8PhtCz2238-VjM
https://drive.google.com/open?id=1BL6xsRBw7av5Oxke_nMWybCsiuBjkxl_

pgee said:
Asked Seicane with the chat function on there site. I still have that Rom if you want it.
Click to expand...
Click to collapse
Thanks! I've downloaed both files. My unit MCU version is MTCE_HLA_V2.67_3. Do you have de same version? I'm having some USB ports issues...

kekoha said:
Thanks! I've downloaed both files. My unit MCU version is MTCE_HLA_V2.67_3. Do you have de same version? I'm having some USB ports issues...
Click to expand...
Click to collapse
Hi, I don't know and can't check because I sold the car.
USB, see reaction 16 november 2017 on debugging the USB.

how do i connect it to my computer if there is 2 female connectors i have the rockchip px3 tesla style screen for qx50
---------- Post added at 07:07 AM ---------- Previous post was at 07:03 AM ----------
pgee said:
What part do you want me to explain?
Got a Rom update from the manufacturer yesterday, also a mcu update, thanks.
Click to expand...
Click to collapse
i dont get it i have a rockchip px3 tesla style screen qx50 and i want to connect to my w10 pc but the screen has 2 female connectors

Stuck on bootscreen PX5

Hi Guys,
I have managed to get my Android Head unit stuck on the bootscreen....
I was busy to get root acces on the unit which look like it succeeded. But sadly enough I update the binaries of SuperSU.
This resulted a head unit which gets stuck on the bootscreen.....
It is a Dasiata PX5 with 2g ram and 16gb rom memory. I know Hotaudio has a few posts with updates / files in it.
Is that the only way to revive the unit ? and if so which files need to be installed? the MCU or the System update?
I managed to get in to the recovery menu so I think there is still hope.

Aussi said:
Hi Guys,
I have managed to get my Android Head unit stuck on the bootscreen....
I was busy to get root acces on the unit which look like it succeeded. But sadly enough I update the binaries of SuperSU.
This resulted a head unit which gets stuck on the bootscreen.....
It is a Dasiata PX5 with 2g ram and 16gb rom memory. I know Hotaudio has a few posts with updates / files in it.
Is that the only way to revive the unit ? and if so which files need to be installed? the MCU or the System update?
I managed to get in to the recovery menu so I think there is still hope.
Click to expand...
Click to collapse
You will need to reflash the system from recovery, whats your MCU?

Octane70 said:
You will need to reflash the system from recovery, whats your MCU?
Click to expand...
Click to collapse
ugh I tried updating with one of these files but it doesnt go past the verify the package part when installing new system package...
Now I am stuck in the recovery screen. Can I still fine out what MCU I have ?

Aussi said:
ugh I tried updating with one of these files but it doesnt go past the verify the package part when installing new system package...
Now I am stuck in the recovery screen. Can I still fine out what MCU I have ?
Click to expand...
Click to collapse
How about your specs of the unit? I believe it may say it in the top of the recovery?

Yeah sorry about that. I still have the link to the deal on AliExpress gonna find it in a second.
Attached is a photo of the unit in recovery mode
I have tried this update :
Blue UI HA_PX5_8.0_ota(20180705）
from this page on XDA
https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155
Now looking at the picture it is stating something with HCT instead of HA which mentoined in the 1 I downloaded
here is the link
https://www.aliexpress.com/store/pr...885.html?spm=2114.12010608.0.0.55d77540QOk2e9

Aussi said:
Yeah sorry about that. I still have the link to the deal on AliExpress gonna find it in a second.
Attached is a photo of the unit in recovery mode
I have tried this update :
Blue UI HA_PX5_8.0_ota(20180705）
from this page on XDA
https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155
Now looking at the picture it is stating something with HCT instead of HA which mentoined in the 1 I downloaded
here is the link
https://www.aliexpress.com/store/pr...885.html?spm=2114.12010608.0.0.55d77540QOk2e9
Click to expand...
Click to collapse
You could try the HCT ota on the same page you linked.

Octane70 said:
You could try the HCT ota on the same page you linked.
Click to expand...
Click to collapse
Chips,,,,,, tried that one too by SD card but that one also hangs on veryifing package :/
Could the device be bricked and not whiling to update anymore.....
Edit:
Pfeeeewww it worked seems that I just need alot more patience hehe.
although it is now a complete differente interface than which I had

Aussi said:
Chips,,,,,, tried that one too by SD card but that one also hangs on veryifing package :/
Could the device be bricked and not whiling to update anymore.....
Edit:
Pfeeeewww it worked seems that I just need alot more patience hehe.
although it is now a complete differente interface than which I had
Click to expand...
Click to collapse
Ah good to hear, same with mine when i updated to the newest firmware, i just started using ffc Launcher.
yes, takes along time in the verifying process, i usually walk away for 10 to 15 minutes.

Thanks for the support man ! Gonna try some rooting again tomorrow

No sound at ALL on my OP6

Greetings, everyone. So I got an OP6 a few days ago from someone I know and it has two problems - first one is that there is no sound at all from the phone, the speakers, the headphone jack, even audio through bluetooth don't work (when trying to play audio through bluetooth the phone starts lagging like hell). Second is, the fingerprint reader doesn't work too, there is no option in the system, only on the first setup screen (after a reset) where it doesn't work anyway.
The guy said it happened after an update. I tried re-flashing it many times because it kinda looks like like a software issue, but nothing help. Diffrent roms, stock or not, doesn't matter, tried unbrick tool, no luck aswell. Disassembled the phone in the end to check for water damage or loose cables, but even that didn't help, everything seems normal inside. And it's pretty wierd to have 2 separate things not working at all.
There is no official support for Oneplus in my country, the phone is imported so getting an official repair is not an option. Anyone got any idea what I should be looking into?
Thanks.

Guy you switch off the mute button over the power, press down and voil

Toni Moon said:
Guy you switch off the mute button over the power, press down and voil
Click to expand...
Click to collapse
Thanks for the advice, but don't you think I tried that before physically disassembling the phone?

Gottylol said:
Thanks for the advice, but don't you think I tried that before physically disassembling the phone?
Click to expand...
Click to collapse
Well.. we had people that didn't try it...so no point in thinking and skipping questions...

have you tried to reflash the whole stock rom with using fastboot images ?
I've got that problem too before, it's becaused I flash a stereo sound mod, and updating the software. and I lost all of my sounds.

Azhar_Fahry said:
have you tried to reflash the whole stock rom with using fastboot images ?
I've got that problem too before, it's becaused I flash a stereo sound mod, and updating the software. and I lost all of my sounds.
Click to expand...
Click to collapse
Interesting, did you not have any sound at all too? From the speakers as well as headphone jack?
But yes, I tried to flash from fastboot, even did the unbrick tool which seems like the best method to get a complete factory reset. I'm not sure if there's some part of the firmware that can still be corrupted even after flashing though the tool.

Gottylol said:
Interesting, did you not have any sound at all too? From the speakers as well as headphone jack?
But yes, I tried to flash from fastboot, even did the unbrick tool which seems like the best method to get a complete factory reset. I'm not sure if there's some part of the firmware that can still be corrupted even after flashing though the tool.
Click to expand...
Click to collapse
yep. no sound at all.
Btw here's the link that I use to unbrick my phone
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page1
hope it helped.

Azhar_Fahry said:
yep. no sound at all.
Btw here's the link that I use to unbrick my phone
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page1
hope it helped.
Click to expand...
Click to collapse
Thanks, I'll try again later just to make sure.

Sadly, didn't work again. Flashed all the partitions that can be flashed with that tool, but still got no sounds, so probably it's a hardware issue in the end, but it's hard to imagine what exactly is broken.

OnePlus 8 IN2010 Super-Hardbricked. Need information!

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.