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.
Related
i have a samsung captivate i897.
i bought it sim free and unlocked from the states but i'm in the UK.
i recieved it already rooted running cyanogen mod and miui and have had it for 8 months. its worked perfectly the whole time.
until the past month i'd say its been radomly forcing closs on nearly everything.
i havent installed any new software or roms or anything or even dl any new apps so i cant figure out what would be causing the problem.
i tried checking for updateds on the muiu and it runs android 2.3.7
i'm not a tech person at all so i spoke to one of the tech guys at my local phone shop and he said i should try a factory reset.
so i guess i'm asking a few questions here:
1) does anyone have any idea what might be up with my phone?
2) can someone elplain to me the easiest/safest way to fix it?
please bear it mind i am a total noob at this tech stuff. i'll try to understand and cooperate as much as i can with those so kind to help me, but i'd really appreciate if people would help/point me in the right direction instead of giving me a short blunt answer which assumes i know all this tech stuff then locking my thread.
If it's already rooted & running a custom ROM, then you probably already have a custom recovery installed (probably clockworkmod). 1st thing would be to boot into recovery & do a backup. Then, you can try flashing any ROMs you want / factory reset / whatever, and restore your backup if you don't like the results.
-- Sent from my TouchPad using Communities
how do i know if i have clockwork mod installed (i've never seen it before, but then again if its on the boot menu where i've not been before)
for booting into recovery i just long press the power button (at least it works like this on my phone) > reboot > recovery > ok
then what should happen after i press "ok" ?
also just to state (if it helps) the options i get for rebooting are: normal, hot boot, bootloader & recovery.
i dont really feel confident to be flashing roms (mainly because i dont really know how/which are stable etc) on the other hand i do need to fix it. guess i'd like to try the factory reset first though..... under the assumption its slightly easier.
i thought factory reset would restore the phone back to stock settings? but the guy in the phone shop said it wouldnt? (not sure how reliable he is ;] )
found this thread here which seems kinda similar
http://forum.xda-developers.com/showthread.php?t=1264177&page=3
have tried uninstalling some apps to see if it helps.
the thing is with the problem is seems to occur randomly. the phone will work like perfect again for a few days then boom starts forcing close yet again.
only time will tell.
hi, i just got my tablet back from repairs and i asked them to install ICS if they had to reset the firmware, and they did. now my problem is that i want to update to the 4.2 JB that came out (while my ASUS was in repairs for 3 WEEKS) but i can't. when i try to update, it just says "no update found". i have already talked to their "experts" and he just kept saying "oh, it come to your tablet when it ready" I have also tried to download the update from their site, but then when it tells you what version you need by looking at the build number, i noticed mine was IML74K.WW_epad-9.4..... and shouldn't it be something more like US_epad-9.4.....? i tried to install it anyways but it never detected it on the sd card. so then i tried to just use fastboot and flash it to the device, but when i entered the boot menu, THERE WAS NO OPTION!! In fact, there was only 2 options, wipe data, and boot android. there was no usb or RCK (or whatever it was) option. i also have several other problems, but i'll leave them for another day and another post, sense they may be related
Any help would be awesome sense it's obvious I'm not going to get much help from ASUS. Let me know if you need any other info too!
Thanks in advanced!!
Jake
Snakester15 said:
hi, i just got my tablet back from repairs and i asked them to install ICS if they had to reset the firmware, and they did. now my problem is that i want to update to the 4.2 JB that came out (while my ASUS was in repairs for 3 WEEKS) but i can't. when i try to update, it just says "no update found". i have already talked to their "experts" and he just kept saying "oh, it come to your tablet when it ready" I have also tried to download the update from their site, but then when it tells you what version you need by looking at the build number, i noticed mine was IML74K.WW_epad-9.4..... and shouldn't it be something more like US_epad-9.4.....? i tried to install it anyways but it never detected it on the sd card. so then i tried to just use fastboot and flash it to the device, but when i entered the boot menu, THERE WAS NO OPTION!! In fact, there was only 2 options, wipe data, and boot android. there was no usb or RCK (or whatever it was) option. i also have several other problems, but i'll leave them for another day and another post, sense they may be related
Any help would be awesome sense it's obvious I'm not going to get much help from ASUS. Let me know if you need any other info too!
Thanks in advanced!!
Jake
Click to expand...
Click to collapse
The stock 4.2 (10.6.1.8) has an assert that will only allow it to be installed from 10.4.2.20. If memory serves me correctly ICS does not have the usb icon until unlocked. Also the new 4.2 bootloader only has three icons - no usb.
Are you unlocked? Most units that come from repair are not and can't be unlocked.
With all the unresolved issues on 4.2 I would not put it on my tablet at this time. There are many bricks waiting for a resolution.
thanks, that helped fix it!
tobdaryl said:
The stock 4.2 (10.6.1.8) has an assert that will only allow it to be installed from 10.4.2.20. If memory serves me correctly ICS does not have the usb icon until unlocked. Also the new 4.2 bootloader only has three icons - no usb.
Are you unlocked? Most units that come from repair are not and can't be unlocked.
With all the unresolved issues on 4.2 I would not put it on my tablet at this time. There are many bricks waiting for a resolution.
Click to expand...
Click to collapse
I downloaded the 4.1 firmware and it detected it and installed it right away. I don't know why they couldn't tell me that when I called, but it fixed the problem. And I know you said not to, but I installed 4.2 anyways because I was too curious, and I have personally found no problems and like the new features.
I want to use guaranty for my tablet so What should I do to turn my rooted device to official state.
Full story:
Touch screen stopped working and I can work only with pen. I searched web and tried some solutions such as factory reset, but didn't help.
So i think it's a hardware issue and I want to turn it in for repair. But the problem is I've rooted my device with odin(probably with custom Rom) and my binary counters shows 2.
Please guide me how to roll back to official state
P.S. If anyone can help to solve the touch screen issue, I prefer to have my device rooted.
Download and run Triangle |Away from the Play store .
Run TA
Boot to download mode flash stock rom for your phone reboot factory reset.
ardalan_o said:
I want to use guaranty for my tablet so What should I do to turn my rooted device to official state.
Full story:
Touch screen stopped working and I can work only with pen. I searched web and tried some solutions such as factory reset, but didn't help.
So i think it's a hardware issue and I want to turn it in for repair. But the problem is I've rooted my device with odin(probably with custom Rom) and my binary counters shows 2.
Please guide me how to roll back to official state
P.S. If anyone can help to solve the touch screen issue, I prefer to have my device rooted.
Click to expand...
Click to collapse
Post # 2 covers the restore but I have seen many posters with pen issue just like yours and it appears that you could have caused the problem somewhere in your Rooting and or the installation of the custom ROM.
Do a search there are lots of people with the same condition and I believe it is rooting and or user MOD's related.
Good luck.
.
Tanx JJegan, It worked smoothly:victory:.
But still I have the touch screen issue kkretch .
Now I am realy convinced that it is hardware. but thank you for the tip man.
Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope
Good morning, I've been on the phone for two days now that's crazy ... and everything is clear to touch where I should not surely hehe
I comment a little to see if you can throw me a handle, either to put the phone right or neck.
I had a rom on my cell phone for maybe 4 or 5 months and the only thing that a couple of weeks or so ago every time I went in the car or with the bike when using bluetooth calls failed, so I started looking in internet and I saw that many rom failed in that, because I decided to put another rom. All good, but the same mistake followed and the one that did not vibrate added up. Well now I have been trying to try different but yesterday there is no way, you can see that I made a small brick. After talking for some comments on YouTube, he told me that it could be that he has damaged binary, (I do not know what it is), they told me to download to Android 6.0
The question is yes, I tried a firmware (the only one that I could install with odin, the rest always fails) and I have now the phone that works half, because it still does not vibrate, every time I turn on I have to enter key wifi and some more things , not counting the andorid that I have haha that is outdated.
Testing with Odin to install other firmware now I get on the mobile, secure check fail bootloader. (I understand that it may be that the bootloader is blocked) but I do not know how to unblock it either, I have the developer options enabled with debugging usb and OEM.
I have also tried to install with Odin the TWRP and it comes out that if it has been installed correctly but then I try to get in and out fail and restart.
I have seen that there is a guide here for TWRP but it is for android 7.0 ... so I do not think it's good either.
After this billet ... does anyone give me a hand?
Thank you very much in advance!
PD: I add, right now I have the J710FXXU5BRC3 version but J710FXXS3AQG1 runs too. both with android 6.0
PD2: another mistake, is that when I go to flash it puts: sw rec. check fail. device 5, binary 3