Hello XDA, I've been trying to solve this problem on my own for months now, but I haven't been successful, so I'm posting now in the hopes of having someone help.
About three months ago, I was browsing through my Tumblr feed when all of a sudden, my phone (a Samsung Galaxy Express, GT-I8730) shut off on its own. It wouldn't turn back on.
So of course I started to panic, but I tried plugging it into a PC. Windows found it as something like Qualcomm QHSUSB Download Mode. I did some research, and came upon @darkspr1te's "brixfix" tool, which I modified to work with my phone. I tried using it to no avail, so I did even more research. Turns out this happens to the S3 a lot (something about a bug in the eMMC firmware?), and people have recovered from it by using a special SD card onto which a dump of working bootloaders from another exact same device is copied.
So I tried that method, asked for a bootloader dump from one of my fellow I8730 users here on XDA, and burned the dump onto my spare 8GB Class 2 SD card. (I've read somewhere that one must use Class 10, but I can't afford to buy a new card. I later read on the same forum that slower, smaller cards are fine as long as they are able to contain the first 200MB of the bootloader dump.
I popped the card into the phone, switched it on, and it greeted me with this 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"
}
I assumed that this was normal, and so proceeded to Odin-flash the bootloaders (aboot, sbl1-3, tz) and the whole system (system, boot, recovery, modem, hidden, cache) onto the phone. It rebooted and hung at the splash screen, so I rebooted it into recovery mode; thinking that the ROM must have gotten corrupted somehow.
However, when I would normally see the recovery screen, Odin Mode greeted me with the message
Could not do normal boot.
Click to expand...
Click to collapse
Followed by the usual Odin info:
ODIN MODE
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Click to expand...
Click to collapse
I tried flashing SYSTEM again at this point, but Odin Mode gave me
ODIN: flash read failure
Click to expand...
Click to collapse
and rebooted. I put it in Download Mode again, scoured the internet for a PIT file, and tried repartitioning; to which Odin Mode responded with
SECURE CHECK FAIL: PIT
Click to expand...
Click to collapse
I don't have the money for a new phone, let alone a JTAG box, so I'm at a loss as to what to do next. (And someone just released a working Lollipop ROM for my device, so I'm really excited to get this thing to work again. :good
My device info (accurate as of the last time I was able to use it properly):
ROM: CyanogenMod 11.0 (M8)
Kernel: 3.4.0 CM stock
Region: XSP (I8730DXAMC3, I8730OLBAMC3)
Click to expand...
Click to collapse
I also opened it up (it's out of warranty) and listed down all info I could find:
Component Type: Name [Associated Markings]
Digital Signal Processor: QCOM WCD9304 [OVV NFK60000 A824801]
Accelerometer: Invensense MPU-6051M
eMMC: SanDisk [SDIN7DU2-8G 3067DFW46OPP CHINA]
NFC Controller: NXP PN547 [47601 4T35109 N+ D12521Y]
RAM: SAMSUNG [310 K4P8G304EB-GGC2 GKA6579P]
GPIO: QCOM PM8917 [OVV 3R29988 AU25201 07]
WLAN/BT: Broadcom BCM7320 [KY4U]
Click to expand...
Click to collapse
Any help would be appreciated.
Related
Hi, my friend's s3 is stuck on a bootloop (I guess)
I tried flashing through odin an official stock rom from the Philippines downloaded from SamMobile
(I9300XXUGNA5_I9300OLBGNB1_XTC)
but it always failed first attempt was like 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"
}
http://dl-1.va.us.xda-developers.com/2/8/1/3/6/3/2/s3.jpg?key=Tj5GRb3UvyE4DodynB_WbA&ts=1403537759
it was stuck for a long time and it failed
second was
http://dl-1.va.us.xda-developers.com/2/8/1/3/6/3/4/s31.jpg?key=SoUMDDJWbJAdsxo0EWL5Iw&ts=1403537810
I retried many times (restart pc, changing ports, and install drivers)
and one thing I noticed is when I connected the phone to pc the wondersharego software says
http://dl-1.va.us.xda-developers.com/2/8/1/3/6/3/3/s32.jpg?key=nNYeD2yvhQubpdRUDHobWQ&ts=1403537810
but the thing is on the battery slot the sticker said its GT-I9300
NOTE this is a Original product by Samsung (I know how to identify one)
I can only enter Download mode
by the way there are some small texts written on the upper left of the screen
Product Name: (blank)
Custom Binary Download : No
Custom Binary : Samsung Official
System Status : Custom
what should be the problem? I honestly don't have any ideas left
chaosreign09 said:
Hi, my friend's s3 is stuck on a bootloop (I guess)
I tried flashing through odin an official stock rom from the Philippines downloaded from SamMobile
(I9300XXUGNA5_I9300OLBGNB1_XTC)
but it always failed first attempt was like this
http://dl-1.va.us.xda-developers.com/2/8/1/3/6/3/2/s3.jpg?key=Tj5GRb3UvyE4DodynB_WbA&ts=1403537759
it was stuck for a long time and it failed
second was
http://dl-1.va.us.xda-developers.com/2/8/1/3/6/3/4/s31.jpg?key=SoUMDDJWbJAdsxo0EWL5Iw&ts=1403537810
I retried many times (restart pc, changing ports, and install drivers)
and one thing I noticed is when I connected the phone to pc the wondersharego software says
http://dl-1.va.us.xda-developers.com/2/8/1/3/6/3/3/s32.jpg?key=nNYeD2yvhQubpdRUDHobWQ&ts=1403537810
but the thing is on the battery slot the sticker said its GT-I9300
NOTE this is a Original product by Samsung (I know how to identify one)
I can only enter Download mode
by the way there are some small texts written on the upper left of the screen
Product Name: (blank)
Custom Binary Download : No
Custom Binary : Samsung Official
System Status : Custom
what should be the problem? I honestly don't have any ideas left
Click to expand...
Click to collapse
Blank product name usually means you need a new motherboard..You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I doubt it will work..I suggest service repair
tallman43 said:
Blank product name usually means you need a new motherboard..You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I doubt it will work..I suggest service repair
Click to expand...
Click to collapse
Thanks for that! I downloaded another stock from another country but it still not working
Currently downloading that restoration package hope it will work
tallman43 said:
Blank product name usually means you need a new motherboard..You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I doubt it will work..I suggest service repair
Click to expand...
Click to collapse
I downloaded it from the thread ... the 4.3 one ... there's only 4 files the pit file is missing so I can't use it
flashed other stocks still not working
Search that thread, the pit file has been posted several times.
Sent from my GT-I9300 using Tapatalk
The product name is wrong alr. Most probably wrong file flashed by user.
Sent from my GT-I9300 using XDA Free mobile app
Hi All! I just got a new phone... It's a Chinese phone with no apparent brand.
Unfortunately I tried to root it and while using SP Flash Tool and MK Droid Tools I bricked it , Now i've been trying for days flashing different roms for similar phones in the hopes that one will work. One kinda worked but was the wrong resolution and I couldn't use it... I don't even remember which one it was.
Before doing this I tried to back up my images, but I am an idiot and didn't do it right. I have a scatter file and some other images from my original rom... but nothing beyond the recovery partition. Here's the list of files I have from the original phone:
MT6572_Android_scatter.txt
preloader.bin
MBR
EBR1
uboot.img (renamed to lk.img)
boot.img
factory_NONmodified_recovery.img
nvram.bin
pro_info
protect_f
protect_s
seccfg
I have also attached the scatter file in case anyone finds it useful.
If anyone can help me find the missing files or a different factory image, I'd greatly appreciate it! Below are specific details about the phone... maybe there's one that you guys know about that fits it? Also, if i try a different rom... which parts of my original rom should I still flash in, and which parts of the new rom should I flash?
Thanks alot!!
{
"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"
}
Here's what I got, including details from the FCC
2ADBRK968 by Shenzhen Kaliho Technology Development Limited for smart mobile phone
Product: smart mobile phone, Marketed as MTK6572 solution 3.5inch cheap 3G android smart phone K968
Trade Name: KALIHO, K-CEL, K-TEN
Model Number:K968
Serial Model:A600
Screen: TFT 3.5" HVGA(480x320) Capacitive touch screen
Operation System: Android 4.4.2
Features: 3G, Bluetooth, Email, WiFi, FM Radio, MP3 Playback, QWERTY Keyboard, Touch Screen, Dual Sim Card, Auto Focus, Built in Flash
Processor: 1.3 GHz Dual-Core Processor
Chipset: MTK6572
RAM: 256MB
ROM: 2GB
Cameras: 0.3MP+0.3MP Front/Back Cameras (I actually think the back one is 2MP)
Frequencies: WCDMA 2100/850MHz (1900 Optional) and GSM 850/900/1800/1900MHz
Dual-Sim card slot
External Memory: MicroSD up to 32GB
Click to expand...
Click to collapse
FCC Page: http://fccid.net/number.php?fcc=2ADBRK968&id=477292#axzz3RxdczcMd
Product Info/sale: http://oemfone.en.alibaba.com/produ..._5inch_cheap_3G_android_smart_phone_K968.html
I think it might take a while till i get any response, so still trying myself.... I'm looking around to see if anyone has a working phone that is like mine, but until then I'll still try roms for devices similar to mine, but i have a question, maybe I should post it on a new thread?
How do i find out what's going on whie the device is booting? it gets to the splash screen, i can get to recovery as well, but I want to know what's going on during the boot process... adb logcat does nothing but say -waiting for device-
Is there another way?
Thanks again!
I wasn't sure wether I should create a new post or just reply here, so i just went with reply
After looking I was finally able to get a dump of the stock rom from someone with an identical phone, and in the spirit of openness, I'd like to share it with you guys if anyone ever needs it.
Link: http://www.mediafire.com/download/9zkfz9n7hyiy8k6/A600_MT6572_ForFlashtoolFromReadBack.zip
You can flash this rom using SP Tools. Also, the phone will not boot immediately after flashing this rom... first you need to start the phone in (bootloader?) mode by holding the vol. Down and power. Once you're there do a factory wipe... technically this should be done in recovery mode, but idk how to do it with this rom because there's no "Yes" option when recovery asks you if you're sure about a factory wipe. Maybe it's hidden with some sort of key combo? idk, do it how you prefer.
Well, thanks, if you have questions let me know
After some months of use , one day i turned on my android box and suddenly after loading it will give a black screen and there is nothing else after that, i tried to reinstall firmware through a SD card but it stuck in the installing/loading with a "x" on the android green man.
Now i would like to ask for a help from someone that is familiar with unbricking, i'll provide pictures of my H96 so you can see it from inside and tell me HOW CAN I SHORT CUT or whatever i need to do. (because i saw different hardware and different devices)
May i use 9.0 android version?
This is my android box:
{
"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 hope the pictures of my android box will help you so you can guide me in the process of unbricking and about the short cut where should i press.
Short the following 2 pins. Good Luck.
ath156 said:
Short the following 2 pins. Good Luck.
Click to expand...
Click to collapse
I got a partition error... i tried almost every firmware... what could be the problem?
argosc said:
I got a partition error... i tried almost every firmware... what could be the problem?
Click to expand...
Click to collapse
Download the correct firmware from here:https://www.h96tvbox.com/content/6-Firmware-upgrade
Probably you have LPDDR3 memory so ONLY this firmware is suitable for your TVbox. If you had 8DDR3 type of memory you could use both firmwares (those for 8DDR3 & LPDDR3).
Also please describe how you exactly are using USB Burning Tool and the short pins method (the whole sequence).
ath156 said:
Download the correct firmware from here:https://www.h96tvbox.com/content/6-Firmware-upgrade
Probably you have LPDDR3 memory so ONLY this firmware is suitable for your TVbox. If you had 8DDR3 type of memory you could use both firmwares (those for 8DDR3 & LPDDR3).
Also please describe how you exactly are using USB Burning Tool and the short pins method (the whole sequence).
Click to expand...
Click to collapse
Actually i don't use short pins, because when i connect my h96 to the PC via the USB cable it automatically gives a connection success, so i just use some firmware, i used the firmware from the official site, but still doesnt work , it always get stuck at 9%.
argosc said:
Actually i don't use short pins, because when i connect my h96 to the PC via the USB cable it automatically gives a connection success, so i just use some firmware, i used the firmware from the official site, but still doesnt work , it always get stuck at 9%.
View attachment 5246915
Click to expand...
Click to collapse
1. Did you try the official Android 9.0 version (stock firmware) for the LPDDR3 memory as I told you above?
It is this version https://drive.google.com/drive/folders/16qCsIFbGDSgopwJ3zEBQ4iLC_wLEbLVV
So did you try this version?
2. If after trying number (1) your TVbox is not brought to life, this means that it is hard bricked and your best option is the "short pin" method.
ath156 said:
1. Did you try the official Android 9.0 version (stock firmware) for the LPDDR3 memory as I told you above?
It is this version https://drive.google.com/drive/folders/16qCsIFbGDSgopwJ3zEBQ4iLC_wLEbLVV
So did you try this version?
2. If after trying number (1) your TVbox is not brought to life, this means that it is hard bricked and your best option is the "short pin" method.
Click to expand...
Click to collapse
I have the same problem and the same box.... did you manage to solve it?
the stock firmware links are down
Hi,
I have a big problem.
My brother tried to root my Xtrons Px6 rk3399 gs. with Su user. He updated superuser. Now the radio is in the boot loop and it won't start. He then tried a new firmware to bottles which does not work either, the radio only shows the logo. I get into recovery. I just do not know how to go on:-(
it's the Xtrons PQ80UNV
Sorry for my english.
Greez
{
"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"
}
TF? Why would you want to root that?
Did you try factory resetting?
He said it would be better. then you have more options. Because of some sound patch, I don't know much about it. Factory reset? I pressed Restet button but no change. It doesn't just start the boot logo from Vw.
I don't even get to the Adroid. Only in recovery.
Did a wipe, but it still doesn't start.
You chose wipe cache partition. I meant "Wipe data/factory reset"
Try choosing it.
If your brother is the one who did this as you say, if it's me I'd force him to fix it or at least pay for it.
I tried that too. I also tried the original firmware here, but always the same.
Yandex
Finds everything
yadi.sk
Yes, that's right, he's currently doing assembly work. I'm really desperate :-(
What I noticed is that with every firmware I install it is always the same recovery version.
voxdie said:
What I noticed is that with every firmware I install it is always the same recovery version.
Click to expand...
Click to collapse
Can I ask how did you root it?
Unfortunately, I don't know. I only know that an rk3399 mcu was previously a gs version
voxdie said:
Unfortunately, I don't know. I only know that an rk3399 mcu was previously a gs version
Click to expand...
Click to collapse
I don't believe you can root a device and suddenly you forget about it...
Do you have unlocked bootloader? You may need to flash the stock ROM if you can find it.
It works again, I have now flashed the img instead of the ota. Now it works again. Great. Thank you so much for your help
voxdie said:
It works again, I have now flashed the img instead of the ota. Now it works again. Great. Thank you so much for your help
Click to expand...
Click to collapse
I don't think I did anything but happy to see everything work out fine.
Make sure your brother doesn't do something like that again.
NO, he can't get to this radio anymore .. thanks again
the UNIT you have, looks almost the same as ICE/HU/PBX89UNV ( except mine has android 9 ) XTRONS ? 64GB -4GB ?
correction- there are multiple versions of this exact same unit. (even one with a qualcomn)
yours has the HDMI out pigtail ?
firmware link -
word instruction -
codes to ENABLE DEVELOPER OPTIONS
To start debugging, enter adbon in the factory settings input password box
if you want to change the factory settings, boot image, etc,, enter 126 in the factory settings input password box.
may i ask fellow members , to root this ,
unlock boot-loader,
flash updated BOOT.img (magisk patched)
-- because this is android 9, do i need a BLANK VBMETA flash?
funny fact--- this unit, will BOOTLOOP if you put a 512GB micro SD card in the slot, it boot loop cycles..
(anything above 128GB causes issues )
the micro SD slot for MAP/GPS , --- can we use this for anything else ?
and does anyone know of there are any custom roms and or TWRP already built for this > (this should share similar/same across a few brands ?)
The device is a Moto G7 Plus with a freshly unlocked bootloader and running on off of a "fastboot boot twrp-3.6.0_9-0-lake.img" which appears to be the latest from twrp.me
See screenshot image and recovery.log attached
Any help would be greatly appreciated as I've not been able to come up with a solution.
Thank you!
Samson
{
"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"
}
Could it be an issue with the new twrp build? Have you tried booting and flashing the older 3.5.2 version?
Teo S. said:
Could it be an issue with the new twrp build? Have you tried booting and flashing the older 3.5.2 version?
Click to expand...
Click to collapse
Hey Teo, oddly enough, TWRP flashed successfully despite the error message. I guess the error message has something to do with A/B slot conditions which I'm still not totally understanding. I know that the Moto G7 (not the plus) requires some copy-partitions-AB.zip according to an install guide that I'm using. Again, is good to go, unfortunately I hard bricked after flashing Lineage 18. I was told that I needed latest OTA for the device which I thought was already on there. I connected the device to wifi and tried to run update just before flashing TWRP but updates failed to download. So for now, I'm just another "Brick in the Wall" lol. Noob level 5000, sucks.
The G7 plus also requires a copy-partiosions-AB.zip to prevent bricking from different software on the 2 slots. It can be found somewhere here on the forum. Also there is a way to flash the latest OTA manually via fastboot. A guide can also be found somewhere here on the forum. You can download the OTA images from lolinet (https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/).
Teo S. said:
The G7 plus also requires a copy-partiosions-AB.zip to prevent bricking from different software on the 2 slots. It can be found somewhere here on the forum. Also there is a way to flash the latest OTA manually via fastboot. A guide can also be found somewhere here on the forum. You can download the OTA images from lolinet (https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/).
Click to expand...
Click to collapse
Thanks again Teo. Question : is there a way to unbrick the device if it won't even power up? I've tried every key combo that I could find but can't even get a charging status when I connect it to power. I think it's now certifiably hard bricked. Dunno
TallDarknSamson said:
Thanks again Teo. Question : is there a way to unbrick the device if it won't even power up? I've tried every key combo that I could find but can't even get a charging status when I connect it to power. I think it's now certifiably hard bricked. Dunno
Click to expand...
Click to collapse
Are you using the cable/charger it came with?
Have you tested with a different cable?
jockovonred said:
Are you using the cable/charger it came with?
Have you tested with a different cable?
Click to expand...
Click to collapse
factory cable / charger only, no other cables. I sent the device to a dev for kicks, see if he can un-brick it. Not holding my breath though. Stat tuned . .