Database Info

Problems with sim card,signal.... could this be wiped partitions?

Hi, i recently got my xa screen shattered and i found another exactly same xa as mine but with signal problems (network not recognised and fails to make any calls, register to gsm)... becouse i bought it cheap and by the looks it's new XA i decided to revive it somehow, i tried to flash firmware newer and same version 33.2.A.4.70. Customization : RU but that didn't solve it. i then unlocked my bootloader, flashed boot and twrp recovery , booted in recovery and find out that some partitions is wiped. i believe this is the problem. im uploading pictures of partitions. can i somehow restore them? i mean i got 2 x fs3111 phones tho my shattered is with android 7 and locked bootloader, but if this is an issue i can solve and fix this phone i can downgrade to same version android 6, unlock, twrp it backup my partitions and restore it in phone that has wiped partitions, or maybe u can tell me better options? im uploading photos of wich partitions lost, take a look XX
AND i took its cover off and looks like it's new and no internal damage to components, i believe it's related to partitions somehow.... tho i'm not expert of android phones ... could that be? xx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Where are u from?, I believe the problem isnt with the partition, maybe the phone is reported by imei, so you have this particular problem, for now on, use the motherboard of your previous phone, to make it work.

Google Pixel stuck on bootlogo.

Hi! I can buy a Pixel from my friend. Pixel stuck on bootloader, shows "your Device software can't be checked for corruption.." I don't know what's happened to him. Can I repair this? Or it's hardware issue.? Or Just flash stock and lock bl/ flash custom ROM? Thanks for help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

LisekDH said:
Hi! I can buy a Pixel from my friend. Pixel stuck on bootloader, shows "your Device software can't be checked for corruption.." I don't know what's happened to him. Can I repair this? Or it's hardware issue.? Or Just flash stock and lock bl/ flash custom ROM? Thanks for help
Click to expand...
Click to collapse
could you post a bigger picture?

LisekDH said:
Hi! I can buy a Pixel from my friend. Pixel stuck on bootloader, shows "your Device software can't be checked for corruption.." I don't know what's happened to him. Can I repair this? Or it's hardware issue.? Or Just flash stock and lock bl/ flash custom ROM? Thanks for help
Click to expand...
Click to collapse
This is the bootloader unlock warning screen from what I can make out from the horrible quality of this image.
Describe what the device is actually doing, this isn't enough to work from and/or troubleshoot the issue further.
In theory it shouldn't be a hardware issue, you could probably just flash the factory image via fastboot and it should work fine given the hardware isn't damaged but we have no knowledge of whether it's the hardware or software which is at fault.

Broken manufacturer logo

Hello, somehow I can't post in the Q + A forum so I'll try my luck here
I bought a broken GT-N8020 a few years ago (bricked / stuck on boot). I made several attempts to get the device working again, one of which replaced the manufacturer's logo with a white static screen. Since I didn't know if I could save the device at all, I ignored it at the time and tried other fixes.
I now have a lineage rom running on the device, but the first screen after switching on. (should be "Samsung") is still white. After a few seconds it switches to the normal lineage boot animation and starts normally.
Can someone tell me what file I destroyed back then and how I can get the screen back to the manufacturer's logo?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I think the file is Param.bin Its part of the Bootloader .
Bootloader can be flashed separate through Odin if you can find one ,
Search forum .

Moved the thread to Q&A.
Cheers
Didgeridoohan
Forum Moderator/Developer Relations

Javic1106 said:
Can someone tell me what file I destroyed back then and how I can get the screen back to the manufacturer's logo?
Click to expand...
Click to collapse
This remembers me on broken eMMC , have seen this screen hundred times.
But at first, try to flash BL from a 4 part firmware.

Flashing the Bootloader fixed it.
Thanks!

[Help] Bricked on a glitch screen but odin mode works

Hi people, I have a Galaxy Note 10.1 (N8000), and since a few years ago is stored because from one day to another stopped working, when you turn on normally the screen is something like interference, has no movement, there is no sound of the system, just stays like that and occasionally restarts, but if Odin mode works "normally", I tried to flash the system in several ways and following various tutorials but nothing has worked yet. At some point it was taken to a "technician" to be checked, but the answer he gave was that the whole motherboard had to be replaced.
Does anyone know if this has a solution?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

JPFeliciano said:
Does anyone know if this has a solution?
Click to expand...
Click to collapse
The eMMC needs to be replaced, I'm doing this as a professional, don't know if theres a store which can do this in your country.

Open the tab and see if the flex cable from the screen is still properly seated in the connector. If not, open the lock and reinsert the flex cable from the screen correctly and close the lock again.

uwe.stemke said:
Open the tab and see if the flex cable from the screen is still properly seated in the connector. If not, open the lock and reinsert the flex cable from the screen correctly and close the lock again.
Click to expand...
Click to collapse
You can see, that the download mode looks normal.
It's the typical picture, if theres no data readable from the param partition,
mostly defective eMMC.

Any idea how to unbrick MXQ-EP-2-V1.0

Please help with how to unbrick MXQ-EP-2-V1.0.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Is it softbricked or hardbricked?

xXx yYy said:
Is it softbricked or hardbricked?
Click to expand...
Click to collapse
Not sure of the difference the two, maybe you can explain but there is no lights

Geek17 said:
Not sure of the difference the two, maybe you can explain but there is no lights
Click to expand...
Click to collapse
Want to bridge using paper clip

Hardbricked means a hardware component got defective, softbricked means either Android OS or device's bootloader got corrupted.

xXx yYy said:
Hardbricked means a hardware component got defective, softbricked means either Android OS or device's bootloader got corrupted.
Click to expand...
Click to collapse
Ok thanks I understand now. So with device if I press the reset switch within the av port and connect USB cable nothing happens. Software doesn't detect any bootloader.

Hi, if still works, you must to short circuit the point that show you in the picture, the board go to maskrom mode. (the secuence must be, press an hold reset button, keep and hold the shortcircuit and connecto the usb male to male on to computer), i use RKdevtool for install RK322XMiniLoaderAll_V2.32.bin and reboot. Now is in LOADER mode, so you can flash a firmware normally. Any doubts just send it.
My BOARD.
MXQ-EP-2-V1.0
RK3228A
8GB/128GB
WIFI SV6152P