Database Info

[Q] PLEASE HELP ME, Urgent :(

Hello,
I have Samsung Galaxy Note 10.1 ( Old version ) .
I got a problem with my device
I can`t turn it on anymore, when I hook it up with USB plug into ( PC ) or ( Power Adapter ) I got the following screen :
{
"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"
}
so I thought its not charged.
But then I left it to charge full ( 3 - 4 hours or maybe more ) but when I turn it on the welcome screen shows and stucked forever like following :
I tried to reset the factory and data and cache and everything inside BOOT list ( into "Power + Voulme up " menu ) but nothing happen too and the welcome screen still keep stucking .
What can I do ?
Some people told me I should put a new ROM/Software into it
But what is true ? and where is the problem ?
Please HELP !

I can't see any of the pictures you have put in your post. Have you tried reflashing your current rom onto your Note 10.1 with Odin? That usually fixes problems like this and it lets you keep your data.

link6155 said:
I can't see any of the pictures you have put in your post. Have you tried reflashing your current rom onto your Note 10.1 with Odin? That usually fixes problems like this and it lets you keep your data.
Click to expand...
Click to collapse
I am not familiar with Odin nor reflashing and stuff .

m4xst4r said:
I am not familiar with Odin nor reflashing and stuff .
Click to expand...
Click to collapse
1. Find the firmware for your device base on it's model number: http://www.sammobile.com/firmwares/
2. Download Odin onto your computer and run it.
3. Get your tablet and when it's turning on, hold the power button and volume down button until you get to the warning screen.
4. Press volume up to continue to download mode and plug your tablet into your computer via USB
5. On your computer, make sure Odin says "Added!". Load the firmware as a PDA into odin and press "Start". Do not unplug your tablet until the process has finish.
6. Android should begin to update and once that's done you should be good to go.

G5 Brick - have only fastboot and most commands won't work.

Here is what I get when trying to install twrp again:
{
"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 was trying to follow the instructions in this thread: https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Every time I tried to reboot, I just went back to TWRP. From some googling I got it in my head to try a different /system format. While doing so, my phone froze. Being impatient, I pulled the battery after ~30 minutes of no progress. Now I'm here: no recovery, and a gimped fastboot. Yes, I'm an idiot, but please help.

J.Campbell said:
Here is what I get when trying to install twrp again:
I was trying to follow the instructions in this thread: https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Every time I tried to reboot, I just went back to TWRP. From some googling I got it in my head to try a different /system format. While doing so, my phone froze. Being impatient, I pulled the battery after ~30 minutes of no progress. Now I'm here: no recovery, and a gimped fastboot. Yes, I'm an idiot, but please.
I would use LG Bridge to get you back to a good working condition, and start over with root.
Click to expand...
Click to collapse

J.Campbell said:
Here is what I get when trying to install twrp again:
I was trying to follow the instructions in this thread: https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Every time I tried to reboot, I just went back to TWRP. From some googling I got it in my head to try a different /system format. While doing so, my phone froze. Being impatient, I pulled the battery after ~30 minutes of no progress. Now I'm here: no recovery, and a gimped fastboot. Yes, I'm an idiot, but please help.
Click to expand...
Click to collapse
LG Bridge would definitely be the way to go. You have to start the phone in d/l mode. If you don't know how to get to download mode, it's very easy. WIth the power turned OFF, hold volume up and plug in the usb cable. Next run lg bridge and click on the 'refurbish' button and GO! Good luck bro...
Eric

Recovery px5 wondefoo android 9

I cannot reach recovery on my unit. It has no physical buttons. Can anybody explain how to reboot into recovery?

Bertkeuter said:
I cannot reach recovery on my unit. It has no physical buttons. Can anybody explain how to reboot into recovery?
Click to expand...
Click to collapse
Is it an MTCD type or variant of?

Yes it is MTCE_HXD

If you have an RST hole, then the video tutorial is here:

Thanks for the video. I have tried the reset procedure as you showed in the video. However, even after waiting 30+ seconds nothing happens. Maybe wait longer or another way to get into recovery mode.

I have tried your method. What I noticed is that it does not shutdown but goes on black immediaty. In your video it shows "shutting down". SO this method does not work on my pX5 unit. Any suggestions?

Press and hold until the buttons flash. Then release and press again briefly.

I tried. Even waited 30 seconds. But nothing happens.

So I don't know, it's a standard procedure, try to write a seller, maybe he has a different way. I read somewhere that instead of pressing RST a second time, he pressed power. Or watch videos on youtube, use the search engine and enter recovery PX ...

There is one more option. If you manage to install the Hal9k firmware, recovery is in the toolbar below the power button:
[ROM][PX5][PX6][PX30][Pie][9.0] Hal9k Mod v4 for MTCD/E head units with Android 9/8/6
This version is deprecated. The new version is here MCU version: MTCD_ХХХХ, MTCE_ХХХХ, MTCP_ХХХХ Firmware version: 4.0.0 (01.02.2020) Version of the latest OTA update: 4.2.2 (06.02.2022) About firmware: Firmware for car head units on the...
forum.xda-developers.com
{
"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 have done some more testing:
1st: The RST button seems to directly power off the unit (instead off shutting down).
2nd. Using the power button (not physical). This only puts in in standby and does not shutdown.
I think not getting into recovery has to do with the buttons not working like described in the for to go into recovery mode.

SOM Flash issue?

So, after a couple of months running Android 10 without any issue, my MTC-D PX5 screen froze yesterday, and after a power off/on the screen never came back to life, but the panel lights did, showing a low-level boot-loop.
I tried to abort the booting process... no luck. Then I inserted the SD I used to upgrade to Android 10. Screen came back to life, Android 10 logo first, then showing the circle with the "preparing to upgrade" and then this:
{
"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"
}
ERROR:do_rk_firmware_upgrade-->GetFlashInfo failed!
Any idea how to recover from here?
This is related to the SOM firmware, right? not the MCU...
@marchnz Do you think that your USB on-the-go HW mod to connect a PC directly to the SOM would help solving this?
Any help is welcome !!!!
:-(
Max

maxiauer said:
So, after a couple of months running Android 10 without any issue, my MTC-D PX5 screen froze yesterday, and after a power off/on the screen never came back to life, but the panel lights did, showing a low-level boot-loop.
I tried to abort the booting process... no luck. Then I inserted the SD I used to upgrade to Android 10. Screen came back to life, Android 10 logo first, then showing the circle with the "preparing to upgrade" and then this:
View attachment 5623185
ERROR:do_rk_firmware_upgrade-->GetFlashInfo failed!
Any idea how to recover from here?
This is related to the SOM firmware, right? not the MCU...
@marchnz Do you think that your USB on-the-go HW mod to connect a PC directly to the SOM would help solving this?
Any help is welcome !!!!
:-(
Max
Click to expand...
Click to collapse
If SD card method doesn't work, double check the files used and SDcard.
If SD card just won't work, use OTG / PC-SOM

Help to fix S7 bad flash

Hi Everyone Thans for having me Im stuck
My s7 froze and wouldnt do anything I managed to turn it off ,then it wouldnt boot ,after clearing the cashe and rebooting system it almost started but kept going to the android falling over ,
I read the options to sort this and tried to flash twrp recovery I seemed to go ok but when the phone rebooted it went to the An error has occured while updating the device software screen ,
I have tried smart switch but it does not see /connect the phone ,I can with a bit of messing with the buttons get from the An error /use the emergency recovery function screen to the ODIN Mode screen and the phone connects to odin But when i try to re flash the boot loader it flashes to the end then fails .
Am I right thinking Its the boot loader I need to get on 1st to get any further ?
Can anyone point me in the right direction ?
If ive posted in the wrong place please can you move
{
"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"
}

Sounds to me, like part of the storage may have suddenly failed or been damaged, causing your device to lock up and after a reboot, triggering this unusual state. Part of the bootloader is likely not getting read or written to properly, so installing fails only after partially writing to the device, and it refuses to boot. You could try a repartition and complete installation - that might also make it worse though. I've seen the blue screen of mild annoyance many times - not sure about the falling android, was there any text? If so, what did it say? The firmware does contain screens for various diffrent panic states, resembling the one you mentioned. I would encourage you to do some more research on those and look for patterns in the way it fails - or doesn't - when flashing other parts of the firmware package. Don't even bother with SmartSwitch - in my experience, it fails at anything the errors tell you to use it for. Also, simple issues like a faulty cable or the wrong firmware can often be overlooked - so make sure those are fine before starting to experiment.