Hi, Im new to all of this and hope anyone could help me out.
I have a problem with my tv box because of installing
SuperSU.
First of all, my box is rooted from factory. Its a beelink gt king. But super su isnt installed like when you root a phone and it shows. So I tried to install it because I needed to hide my root from some apps/games. I installed magisk but I needed this supersu also apparently? Well, anyway I did. And then the problem of the binary occupied appears. So Im googleing some solutions and it says that first you need to install a previous version and then update from play store but in play store there is no more supersu.
But anyway I installed the previous version, asked me to reboot system, I did, and now I have a tv box that is stuck in the logo. Actually not in logo..it passes the beelink logo in about 2 hours, then comes the skull with glowy eyes and thats when it stays. I have waited hours for the skull to change to the homescreen to no avail.
The second problem is I have been trying to reset the box but I just cant do it or the system cant?. Its really stuck. Maybe Im missing something? I dunno. I push the reset button that is at the bottom in this box, then I plug the power cable, wait some time, release...but nothing happens.
What I am doing wrong?
Please help someone.
And can you tell me a method without a PC? Unbelievably I dont have a PC. And this phone cant be rooted or at least is very difficult to root or so they say (a galaxy note 4 verizon).
But at the end it doesnt matter. Whatever it takes to fix this box. Thank you.
GT KING SD Card Update
Hi Hansell1001, I did the same thing and faced the exact same issue. But i happened to have a PC. But i think this can also be done via a Phone and a SD card.
First download the firmware as per your model (As per your serial number under the box) to your phone.
Firmware: For C922X and SA9X and SB9X versions
http://t.cn/A6zQGfda
Firmware: For B922 versions（04.01.2020 add）
http://t.cn/A6ZNxNkM
Firmware: For S922 versions（04.01.2020 add）
http://t.cn/A6ZNxe7R
1. Now extract the content of the zip file.
2. You should see a folder called “sd_card”.
3. Copy the content of that folder (I.e factory_update_param.aml, recovery.img and galilei-ota-eng.xk.zip) to the root of SD Card.
IMPORTANT: (the SD card format must be FAT32)
4. Insert the SD Card to the SD slot at the side of the 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"
}
5. Now remove the power cord of the GT King and with the help of a pin, press and hold the reset button at the bottom and insert the power cord.
6. Hold the reset button for 5 seconds till you see the Beelink logo and then release it. Hopefully you be on the recovery screen.
7. From this screen, select “Apply update from EXT” and select the update zip file.
8. Now the box would update properly and boot you back.
I fixed it
I fixed it more than a month ago. Thanks anyway.
I thought xda was quick.
Hansell1001 said:
I fixed it more than a month ago. Thanks anyway.
I thought xda was quick.
Click to expand...
Click to collapse
Ha ha Yeah but i just got the box in Jan i screwed in March so i was looking for a solution but figured it out myself. So when i saw your post, i thought it would be helpful but guess not. But anyway now this would be helpful to someone who may need it.
So let this be a reference for them
Guys, help! I got a GTKing in November 2020, a couple of weeks ago. It worked for a week or so, then it went into boot loop. Firmware is v 914p0 (dated 21 Oct 2020). I tried several things to no avail:
- When reapplying v 914p0, the device reboots to the boot loop
- When attempting to apply v 913p0or earlier, it says it won't apply an earlier version.
I hope someone will drop in some hint on how to get this @#!* box to work.
Cheers,
-Christos
I can't download that firmware
Fordac
Related
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
ToF_Itachi said:
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
Click to expand...
Click to collapse
While you can (sometimes) install an OTA while your phone is rooted, you should never try to install one when it is fully unlocked (i.e. - custom recovery installed). You edit seems to indicate you fixed it, but if you're still having issues I know there are steps to get out of the bootloop you're experiencing, I just don't have off hand where they're at. Bottom line, if you're root AND unlocked (running twrp), you should never take an OTA as there's no reason for it. You can install one of the fine stock-based roms that have been updated to the latest VZW software and have no risk in doing so. Just for future reference
ToF_Itachi said:
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
Click to expand...
Click to collapse
Follow this command lines and that will or should reboot your phone to before you tried to install the newest update. The same thing happened to me with the last update. Those commands came in handy.
Sent from my Nexus 7 using XDA Free mobile app
Bxrider117 said:
Follow this command lines and that will or should reboot your phone to before you tried to install the newest update. The same thing happened to me with the last update. Those commands came in handy.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Pays to have a copy of LG Flashtool and the stock firmware
See the first post here: http://forum.xda-developers.com/showthread.php?t=2907508
If you have a USB otg cable, you can put the flash...zip file linked in the post on a flash drive, then tell twrp to install that to clear the ota.
Alternately, twrp has a small terminal emulator. Look at the part of the post with the commands listed. Only input the su and two dd command lines, in twrp.
After either of the above, tell twrp to reboot to system.
Once you can successfully get back to your normal system, either freeze "System updates...." or use a file manager to rename the two LGDMSClient files found in /system/app, then reboot your phone one more time.
{
"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"
}
HTH!
Hi, I am trying to root this phone using the guide here: bbs.elephone.hk/thread-9919-1-1.html#.WGr04lzUHIU
However in Windows 10, nothing happens when I hit the download button, and in Linux this error happens when using the files I got from the guide:
{
"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"
}
this is the same PC, with Ubuntu and Windows 10 dual boot
I have tried the fastboot method, but I can't get my bootloader to unlock, the vol up button simply doesn't register on the phone.
So is there any fix? Or am missing something?
Problem solved! Windows 10 doesn't like the drivers provided. However Windows 7 does, so I advise that you keep your Windows 7 install somewhere
Follow this it will explain what you need to do. I had same issue with Windows 10 but rooted my P9000 no problem. I used FlashTools - all the info you need here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
I gave up following tutorials on elephone.hk forum & just followed tutorials from here, but whatever your personal preference - hope it helps ;0)
Need my elephone back
Not sure if this is best placed here???
So....tried to flash my Elephone P9000 using the SmartPhone Flash Tool and all the steps provided tutorial at:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Using Win10 so it took me a while to disable the driver signature enforcement option to get the drivers installed. Got that done and all..so far so good.
Download all the files as the tutorial says...clicked download and connected the phone which was powered off. Up pops a messages "PMT changed for ROM; it must be downloaded."
Google search for this and came across some pages that informed me to click on the 'Format' section in the Flash Tool
Did this and then went back into 'Download' and hey presto, the flash worked and I got the big green tick.
Lovely stuff...until I tried to power on my phone....dead in the water. Power+Volume Up does nothing, power on its own does nothing. I've downloaded loads of instances of the Flash Tool, tried the elephone stock ROM scatter file, recovery image files etc and still nothing. Read loads of similar pages where it's happened to others but just wont work for me!!!!
Can anyone help?
jfk247 said:
Not sure if this is best placed here???
So....tried to flash my Elephone P9000 using the SmartPhone Flash Tool and all the steps provided tutorial at:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Using Win10 so it took me a while to disable the driver signature enforcement option to get the drivers installed. Got that done and all..so far so good.
Download all the files as the tutorial says...clicked download and connected the phone which was powered off. Up pops a messages "PMT changed for ROM; it must be downloaded."
Google search for this and came across some pages that informed me to click on the 'Format' section in the Flash Tool
Did this and then went back into 'Download' and hey presto, the flash worked and I got the big green tick.
Lovely stuff...until I tried to power on my phone....dead in the water. Power+Volume Up does nothing, power on its own does nothing. I've downloaded loads of instances of the Flash Tool, tried the elephone stock ROM scatter file, recovery image files etc and still nothing. Read loads of similar pages where it's happened to others but just wont work for me!!!!
Can anyone help?
Click to expand...
Click to collapse
this usually happends when your flashing with old preloader... try installing CM13 with updated preloader, it should work.
Thanks Ruben, I managed to get the green tick in the sm flash tools using the 'Elephone P9000 Preloader_Lk_Boot_Recovery update' scatter text file.
Phone still wont power on at all and i can't access the sd card to copy across any ROMS so I'm back to square 1 by the looks of it. I'll keep pluggin away at it.
Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"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"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"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 thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...
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 ?)