Related
New to this site but have done days of searches for my problem. Since JB update my bluetooth is not working and I have also found out Airplane mode is messed up also. Both will have slight responses for a short time after booting , then nothing. I down graded back to ICS and I get some functionality and have actually paired a device but does not work correctly. Asus wants the tablet sent back , but it sure seems to me as it is Op system causing all of this. It was working fine before. I am new to messing around with android , So one question is since I down graded to ICS 4.0 does the actual device firmware downgrade completely also ? I see that Bluetooth Version lowered and other versions lowered , but could something else not get back to that version , some type of Bios type settings? ( I was told no Bios in android ,but is there something like it ? )
So does anyone have the same problems , any answers or thoughts ?
Is there a way to erase everything completely and go back to the exact files software , kernals etc. as when in the box it came in.
Sure seems to act like a software driver type problems.
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
I do not want to void any warrenty , but before I send back I want to see if it is Hardware or software.
Thanks
wadea2 said:
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
Click to expand...
Click to collapse
Source code is only useful for software developers. To restore your device as close to factory state as possible, install the full firmware package of your desired version, as you already did when downgrading, and wipe data.
Things not restored by this method:
- device-dependent settings (e.g. serial number, sensor calibration data)
- DRM key
- Partition table
These usually cannot be changed by the user and therefore do not need to be restored anyway.
My main concern is the kernal, I feel that this may be the cause of my problems , if indeed the hardware does not have a problem. So when I restored to ICS , Did the kernal complete revert to factory also ? I understand now that the Kernal is the ( Bios) of Android , takes comands from software and tells hardware what to do . ( Right ? )
I am finding that the "Factory Reset " from from "Setting" does not truely reset all settings ( I set a Sound Setting before Reset , and the same setting was "on" after the reset ), therefore a "Firmware" reset back to ICS may leave the reason my bluetooth and airplane is not working.
So is there a way to use the "blob" with-out rooting or causing a warrenty issue ?
The kernel is part of the full firmware, so it is flashed when you install the firmware. It is the core of the operating system and also contains all the hardware drivers. The PC BIOS would be more comparable to the tablet's bootloader, as it only initializes the hardware and loads the kernel.
Your problem description is completely worthless. If you expect help, state exactly what you did, which error messages appear, and describe in detail what does not work and what you expected.
I thought i expalined better. I will try again. I used my bluetooth on my tablet connected to my phone and sent photos to tablet from phone. All was fine, Did not try and use bluetooth again untill a week later ( 3 days after OTA JB update ) now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Since this happened right after the JB Update , It made since to me it is an update problem. I was wanting to go back to the exact state before update to see if errors were gone. I have re installed ICS and had better response from bluetooth , was able to pair a device but after pairing would not work ( headphones , sound stayed on tablet ) .
With these findings it would lead me to beleave two things , the "Firware install of ICS " left traces of the newer Kernal , that caused the problem or the Tablet hardware is the problem.
does that make more since to you ? Sorry about the first Question. I have let the tablet do the OTA back to JB and still in the same situation. I have an RMA set up , but I just like to know for sure the cause before sending back.
Thanks for you time.
wadea2 said:
now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Click to expand...
Click to collapse
I'm giving up.
Ok, Well thanks for trying ? I do not have any other info. to tell you then my last reply , that is all that I can explain , What is wrong what I did and what I was trying to figure out by process of elimination.
So im trying to remove samsung retail mode and i've tried 5444 as well as M729Q16K8546 to no avail.
How can i remove this? I dont mind any method, whether i have to root it or install a custom rom. The problem is i have searched everywhere to find a root or rom for this specific model and i just cant find any. Thanks in advance.
Build number is LRX22G.G920XXXU1AOC6_LLK
I've also had a demo unit of an LG G3 once. At first I wasn't able to remove the demo unit, what I did was I turned off the phone, and went to stock recovery, from there I chose factory reset.
as for the Galaxy S6
Turn off your Phone
Press Power button + home button + volume up
then it will put you into recovery
then from there choose factory reset.
should work
Can anyoneu share a copy of the build.prop on your S6 sm-g920x?
I've got one of these things too. Once you discover it's not actually a phone, the urgency to solve the ROM problem becomes somewhat less pressing. Anyway, solve the issue, get yourself a mini-phablet, by installing XtreStoLite Deo Mod ROM with UniKernel. (My SM-G920X now identifies as an SM-G925F)
web-star said:
I've got one of these things too. Once you discover it's not actually a phone, the urgency to solve the ROM problem becomes somewhat less pressing. Anyway, solve the issue, get yourself a mini-phablet, by installing XtreStoLite Deo Mod ROM with UniKernel. (My SM-G920X now identifies as an SM-G925F)
Click to expand...
Click to collapse
Can you share how you installed XtreStoLite Rom? Do you have TWRP installed?
Sorry for the delayed reply. Yes, I put TWRP on there, v2.8.7.1. Standard, straight forward Odin install followed by XtreStoLite & Open GApps via a double-ended USB stick (micro at one end). I had no problems that I can particularly remember, was a pretty much straightforward job.
Although it identifies as SM-G925F in Settings / About, it still bootloads as a Live Demo Unit.
All answers can be found here
Hey guys,
The patient is an Android RK3188 5.1 unit from Xtrons for a BMW. The manufacturer is "GS".
After installing basic apps the unit started to really lag, not to mention that the touchscreen stopped working. So I flashed it with a factory MTCD 5.1 KGL rom and the installation went without any problems. After that I had to flash it back to a GS ROM, so I used something I found here on XDA a while ago, namely "GS_NEW4_rk3188_5.1(20160305)".
The installation went without any problems, but the unit then stopped on the "Lollipop" logo. It doesn't go to the car logo after that, just stops dead at the Lollipop screen and that's it.
When I try entering recovery, it works like it should, but the unit blurts out a crapload of info and errors, like the ones you can see in the attached pictures.
Updates don't work anymore.
Please note: I did NOT try to update the MCU on this unit. Only the Android software.
What's the problem with this unit? How to get it back to its normal state?
Picture descriptions:
1 - how recover looks like upon entering it.
2, 3 - sorry for the blurry pictures, but it's hard to snap a good picture of the moving text. You get the idea - a thousand errors or so.
4 - when I try flashing a regular KGL rom that worked on the unit before.
Did you tried this from sd card in GPS slot?
Never had success with that, only from usb drive.
Maybe you try this and it helps...
makes2068 said:
Did you tried this from sd card in GPS slot?
Never had success with that, only from usb drive.
Maybe you try this and it helps...
Click to expand...
Click to collapse
Yes. USB doesn't work.
Test it with another usb stick.
I have the same problems with some of the USB3 32GB Sticks from Sandisk.
SanDisk SDCZ43-032G-G46 Ultra Fit 32GB USB-Flash-Laufwerk USB 3.0 ✓
SanDisk Ultra Dual USB-Flash-USB Stick 32GB USB 3.0 X
Test all USB Ports and formate the sticks fat32
Use stick as small as possible.
Same to gps card. Use 16GM max, and all works as expected. Got some problems with 32gb cards. Took too long to show covers...
So, essentially, the problem here is the SD cards or USB sticks?
I don't think that's the problem.
I know how to update headunits, and it never mattered whether I used this card, that card or that USB stick... in fact, I only use microSD cards for updates, nothing else.
What the problem is is that the update breaks the unit, rendering it impossible to use.
I need to know what is the cause of that, and how to REVERT the damage.
Please read my first post again.
looks like the internal flash memory is broken. From your pics there is a line where the recovery is trying to make a partition and fails. It might be a pain in the ass but try to get xtrons to send you another SOM board.
vinhZ said:
looks like the internal flash memory is broken. From your pics there is a line where the recovery is trying to make a partition and fails. It might be a pain in the ass but try to get xtrons to send you another SOM board.
Click to expand...
Click to collapse
Thanks for your reply.
Can you, or somebody else explain how is it that the unit got screwed when installing a new ROM?
I did not touch the MCU or anything else. The unit is a RK3188 MTCD Android 5.1 one, and I used a different MTCD ROM.
It could be anything, like any flash drive/thumb drive, sometimes they just go bad. It accounts for the slowness when you originally flashed the new rom, then just gave out when you tried to flash again.
Me so nothing I can do
I have had your same issue: follow this guide: https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
Sure that it's a MTCD rom and not MTCB?
When i installed malaysk rom for the first time, i have had the same issue. My hu is a kd one too.
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
dude-nl said:
Sure that it's a MTCD rom and not MTCB?
Click to expand...
Click to collapse
Yes.
@colostro - the recovery card doesn't work.
NaviPR said:
Yes.
@colostro - the recovery card doesn't work.
Click to expand...
Click to collapse
Why does not it work ? You can make a video? We did everything as written here? - https://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
GS_NEW4_rk3188_5.1(20160305) - This firmware from MTCB !!! You have loaded the firmware from another device !!
NaviPR said:
Hey guys,
The patient is an Android RK3188 5.1 unit from Xtrons for a BMW. The manufacturer is "GS".
After installing basic apps the unit started to really lag, not to mention that the touchscreen stopped working. So I flashed it with a factory MTCD 5.1 KGL rom and the installation went without any problems. After that I had to flash it back to a GS ROM, so I used something I found here on XDA a while ago, namely "GS_NEW4_rk3188_5.1(20160305)".
The installation went without any problems, but the unit then stopped on the "Lollipop" logo. It doesn't go to the car logo after that, just stops dead at the Lollipop screen and that's it.
When I try entering recovery, it works like it should, but the unit blurts out a crapload of info and errors, like the ones you can see in the attached pictures.
Updates don't work anymore.
Please note: I did NOT try to update the MCU on this unit. Only the Android software.
What's the problem with this unit? How to get it back to its normal state?
Picture descriptions:
1 - how recover looks like upon entering it.
2, 3 - sorry for the blurry pictures, but it's hard to snap a good picture of the moving text. You get the idea - a thousand errors or so.
4 - when I try flashing a regular KGL rom that worked on the unit before.
Click to expand...
Click to collapse
Unfortunately I have the same issue "block device required " and I haven't found any solution over a month now.
Hope someone help you to find a solution as from my side I disappointed and my device is now decorate my room.
With the described method, you can't enter in recovery mode?!? Did you put sd card into gps slot? Sure?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Hey guys,
I have a similar error but after install the ROM. I have installed malasyk rom MTCD 5.1.1 without problems, but when update the device with my stock ROM i don´t have internal_sd or flash and don´t can install GPS apk.... The device work fine but without internal_sd. If install other time the malasyk ROM the internal_sd appears.
Can you help me how i can mount internal_sd or flash?
Malaysk said:
Why does not it work ? You can make a video? We did everything as written here? - https://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
Click to expand...
Click to collapse
@Malaysk - everything has been done to the letter, as always. I have had successes beforehand with the recovery card.
It just simply doesn't work in this case. The unit doesn't react to the card.
GS_NEW4_rk3188_5.1(20160305) - This firmware from MTCB !!! You have loaded the firmware from another device !!
Click to expand...
Click to collapse
How do you know that it is a MTCB rom?
Same problem to me.
The HU is booting on Lollipop logo, and this is it.
I can flash MCU, but cannot flash ROM.
The device is going in Recovery Mode, but cannot flash ROM.
Also, it cannot be connected to PC, to flash it with RkBatchTool.
When i am trying this: https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
the HU doesnt power on with SD card inserted.
My device was MTCD KGL. IS written on the pCB as well, and i took pictures before first flashing.
Any help is apreciated!
suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?
I don't know the answer to that
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom
lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working
dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???
Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u
Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem
Hey guys,
I have a question for you, cause I am not familiar with the woring of the headunits. I bought an Isudar headunit, but the coreboard gave up (PX30) quite soon. Now I have a Witson coreboard in it and it's working. My problem is, although the headunit is working, the wifi and the usb doesn't. What should I do to syncronize the hardware and software of the headunit. Should I stay with the Isudar MCU and install an Isudar rom to the headunit somehow? If you have any idea, please share with me!
Thanks in advance!
UP
clorid said:
UP
Click to expand...
Click to collapse
Perhaps read through the forums - suggest the MCU cross compatibility thread - and also figure out if it matters which Android MTCD/E ROM could be applied.
I did a firmware update back to the original stock. Unfortunately the wifi and usb still not working. Do you have any idea?
Ok, so I have some news. I did a firmware update back to the original stock rom. Wifi and usb not worked. I randomly find a rom for PX30 and I flashed it to the headunit. The usb started to work, but after a few power on it's not working again. I tried to flash another mcu but it didn't work, so now back to the original. The seller said if I can't power up the head unit's wifi with the stock firmware that's a hardware issue. What do you think?
Can someone help me how can I root the head uni? It's PX30, with GS mcu, running android 9. Unfortunately I don't have wifi and the usb recognises just pendrive. Besides I can use my sd card to copy and use files. Please let me know how to root the device with this conditions! Thanks!