Related
Hello.
I have a Euro xoom 3G (MZ601).
I had ORIGINAL STOCK(update via ota from 3.0) Android 3.1.
I made a nandroid backup.
I made some flash with tiamat..then restored original from nandroid backup (CWM)
...then problems started..
After restore root was not working anymore (and I can understand this),same for recovery..
..and when I tried ota update to 3.2 it started but infinite loop..so pushed CWM (fro sdk) another flash back to nandroid backup (via CWM).
So now I've 3.1 (from nandroid backup..so it's supposed to be ORIGINAL) with root ( I had to root another time..I did it with pushing of from files from one tutorial in this forum).
The PROBLEM is I'm experiencing many blockages and/or auto-restart..
1) My QUESTION is: i found on this foru a link to MOTODEV to download stock Xoom files(kernel,recovery,..)..and re-lock xoom.
If I do what the tutorial (some page as download on Motodev)say I'll get my Xoom like "just buyed"?
And two more questions if I can:
2) is possible Tiamat (3g xoom version) rom (I tried a lot of different versions..) give me some many problems? Application don't working(like "settings ihas been terminated due to an error" where I click "tiamat setting" tab),problem with wi-fi (I don't care 3G..) etc..
3) I'm te only one having many problem with skype? (Last version)Especially whe trying videocall.. (of course I talk of STOCK Android)
Thank you so mnuch...and happy new year to everyone!
(up..any idea?)
I have a rooted GT-P6210 that was working perfectly fine and last night I updated Busy Box Free from Google Play. Busy Box Free reported an error with the install and shortly after I noticed that my Wi-Fi would no longer connect. It just reports "Error" after trying to connect to Wi-Fi.
I tried re-rooting my device but that didn't fix my Wi-Fi issues. I researched everywhere I could think of to unroot my device but all the threads seem to refer to guides that I don't see and firmware links that no longer work. I managed to find a copy of Odin3-v3.04 (not sure if that is the right version) but I still don't have instructions on how to do it nor do I have the firmware that I need.
I decided I would try going back to factory settings by powering off the device and booting into system recovery. I have done a wipe data/factory reset multiple times but Wi-Fi still doesn't work and I don't even know if that removed the root job I did.
When I plug my device into my PC and run Samsung Kies it reports that I have the latest firmware PDA:LA3 / CSC:LA3 (XAR)
So I am stuck and not sure what to do at this point. I have a pretty useless device that won't connect to Wi-Fi. I don't know if I wait around for ICS and install that if it will fix my problem.
Is there anyone that could help me restore my device to factory settings with actual guides, and provide working links to the firmware I would need?
Thanks for your help,
Bryson
I have an identical problem - albeit with a P6200 supplied by UK mobile network "3"
Busybox tried to update itself from 1.20.0 to 1.20.1 (using "Smart Install")
For whatever reason it failed. From then on, the Wifi wouldn't turn on - the button in the pop-up panel (can't remember what it's called!) going from grey to greyed-out green while trying to connect, and eventually giving up and dropping back to grey again - in control panel the Wifi section then just says "Error".
Also Tethering no longer works... clicking on "Portable Wi-Fi hotspot" gives me "Turning on..." in grey for 15-20 secs and then "Error"
I've not tried a factory wipe/reset or anything yet. Any suggestions?
Many thanks!
I have also had this issue with my Galaxy Tab 7 Plus (GT-P6210) since Monday evening.
When I noticed the problem I was going to try and restore a backup. During that process is when I noticed that I no longer had root access.
This morning I had a friend look at my device and he noticed that the 'Auto Update' was active. I thought I had that deactivated but apparently not. I’m wondering if an update was pushed out that destroyed root and as a result messed with the Wifi access. So far I haven’t gone any further than this.
Those of you having a similar issue, have you also lost root access? I wonder if re-rooting if that would solve the problem?
Kyazuh
I started having the exact same issue two days ago, I've done countless factory resets and same deal, wifi comes up with error when trying to turn on.
I'm using an international p6200
PDA: P6200LUBKL1
Phone: P6200LUBKL1
CSC: P6200LUUBKL2
I've search everywhere for that firmware to try and do a re-install with Odin, but I cant find it.
Update: Just done a full factory reset, and still no Wifi.
Would a full firmware flash sort it? I've found the correct firmware for my UK "3" network P6200 here:
http://forum.xda-developers.com/showthread.php?t=1517934
This is for flashing with Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265
... though I've never used Heimdall - or even flashed a ROM TBH - so a bit hesitant to give it a go......
Update 2:
Just flashed with stock firmware and Odin - all back to normal, Wifi working!!
After much searching around I was finally able to find the correct original firmware for my TAB:
P6200LUBKL1
I found it on a Chinese site: (I cant post links yet lol )
With Google translator, I was able to download the file and flash the TAB using Odin3, everything worked perfectly, and Wifi is working fine again!!
I also had this problem after trying to update busybox,only I also had a random SoD issue that had me constantly rebooting my device. The only thing that managed to fix it was to Odin back to stock. I'm reluctant to root it again, but at least the problem is gone...
If you open the zip that you use to root this device, you will see that it is basically a binary called su and one script that move it to your device and set permissions. If you want to remove the root, you only have to delete this single file,
In some devices is not as easy, what the script do on our update package must be done with exploits, but the result is the same: move su to some folder on PATH, and set permissions.
That is it, there is no chance to be root fault, seems like some problem with busybos. Actually people like to blame root a lot
The same exact thing has happened to me with my P6210. When I put the device to sleep, I usually turn off wifi. This time I forgot and when I woke it up yesterday evening, the BusyBox updater was open. It failed, of course, and now my wifi won't turn on. No MAC or IP address.
EDIT: Used Odin to return to stock. Rerooted (but did not install CWM) and then installed Superuser, updated su binary. Then installed Busybox Installer which then installed Busybox. Stayed away from Busybox, which seems to have been the source of the problem on my device.
my bad..
Just updated Busybox to version 1.20.1 myself using the smart updater without any issues. Got message it installed correctly and wifi still works even after rebooting.
edit: One difference between me and the op is that I didn't use Google Play to update Busybox I used the apps smart install through the app itself.
Model GT-P6210 with LA3 build.
Could someone try to uninstall busybox?
Sent from my DROIDX using Tapatalk 2
I tried to uninstall busy box still no wifi.
In recovery mode I tried to reinstall my previous load from the file I had on my SD Card. Again no luck.
I'm willing to do a wipe on mine and put the original firmware back on. Has anyone done this with P2610? I have been looking through the forums and I have seen a lot for the P2600 but not much for P2610.
Thanks
Kyazuh
Do you have root still? I can give you a copy of my /system/bin and /system/xbin. As you are about to flash it new i think it could worth the shot.
Sent from my DROIDX using Tapatalk 2
Yesterday after I flashed with the stock Rom, wifi was working fine, I rooted the tablet again installed busybox again and have not experienced wifi issues as of yet.
leodfs using RootChecker it showed that I did not have root access anymore.
isalas16 did you flash from the SD Card using the recovery mode? Or did you use a desktop program like Odin or Heimdall? Also do you have the name of the stock ROM file that you used?
I'm on the newb side of things here and I want to make sure I'm using the right process and files.
Thanks
Kyazuh
leodfs, could u send me theses files, I m with the same problem....my gt-p6210 (brazil)....no wifi, ill try fixit...
thanks....
Kyazuh said:
leodfs using RootChecker it showed that I did not have root access anymore.
isalas16 did you flash from the SD Card using the recovery mode? Or did you use a desktop program like Odin or Heimdall? Also do you have the name of the stock ROM file that you used?
I'm on the newb side of things here and I want to make sure I'm using the right process and files.
Thanks
Kyazuh
Click to expand...
Click to collapse
I used Odin3 the filename of the firmware I used is P6200LUBKL1_b.it168.com.tar
VitaZora said:
The same exact thing has happened to me with my P6210. When I put the device to sleep, I usually turn off wifi. This time I forgot and when I woke it up yesterday evening, the BusyBox updater was open. It failed, of course, and now my wifi won't turn on. No MAC or IP address.
EDIT: Used Odin to return to stock. Rerooted (but did not install CWM) and then installed Superuser, updated su binary. Then installed busybox installer which then installed Busybox. Stayed away from busybox, which seems to have been the source of the problem on my device.
Click to expand...
Click to collapse
That did the trick for me. Uninstalling busybox and factory reset did not work. Flashed stock with Odin.
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
Hello all.
I've searched these forums for a bit now, looking for someone in a similar situation; after around 10 pages of 'wrong country' and a loooot of Googling, I can't seem to identify the issue I'm having.
The problem is as follows: I own a Galaxy Express 2 (a rather unpopular device judging by what I've seen across the Interwebs). It came with a stock 4.2.2 ROM when I bought it some time ago. It was rooted within a couple of days - no problems whatsoever. Then the 4.4.2 update came out and I downloaded and subsequently flashed (via ODIN) the one for Vodafone Spain (as it was the only currently available ROM that was Kit Kat). I had noticed a few problems: certain items like LED flashing as notification in Accesibility settings were missing, others didn't work (Smart stay, tap to answer). Not really a problem, but it did raise a red flag. No other problems with the ROM itself, it was very stable.
Attempting to correct this issue, I had flashed 4.4.2 meant for Vodafone Romania (the carrier for where I live seemed the most obvious choice, I was hoping the aforementioned settings might work). They still did not. A few days ago, I got a rather annoying problem where Play Store would crash every single time it attempted to update any app. Naturally, I googled a few fixes, tried those, nothing worked. I had pondered flashing a recent Google Apps pack (like the ones you'd get when flashing CM), but was unsure if I'd do more damage - figured they might not play well if flashed forcefully over the pre-existing stock apps.
I then flashed CM (the release available for Galaxy Express 2, just out of curiosity, and Google Play worked flawlessly, even when updated to the latest version).
TL;DR: Stock 4.2.2 -> Stock 4.4.2 (Spain) (first language appeared as spanish) -> Stock 4.4.2 (Romania) (first language appeared as croatian) -> CM build currently out for Express 2 -> Emergency recovery via KIES 3 flashed another 4.4.2 it seems (but also loaded in Croatian)
The issues I'm currently having:
1) Ever since the Romania Vodafone 4.4.2 install (that would be the second stock ROM I've flashed), the first language I encounter is Croatian and it installs typical bloatware in another language (which I would also imagine would lead me to download incorrect applications from the Market, so I figure if I fix the phone's localization problem, the market will follow)
2) Ghost tapping on the keyboard (not noticed before, was not present on CM, hence I've ruled out a hardware issue, or on any installation previous to CM)
I have tried various fixes: via CWM recovery, tried wiping data/cache/dalvik, formatting /system and /boot before flashing a 4.4.2 for Romania (still loaded in Croatian), via ODIN. I'm fairly certain there's something residual I've mucked up on my phone, because the device identification when I connect it to my laptop via USB is from the previous install (now it has a different name).
IMEI number is fine (read about potential corruption of EFS). Currently, I was going to attempt flashing the stock ROM (4.2.2) from Sammobile, but after so many attempts (and hairs pulled out), I'm not holding out hope that that will fix it.
CSC is fine (correctly identified as CNX, which is the appropriate code for Vodafone, Romania), as confirmed by connecting to KIES.
Eventually, I would like to have 4.4.2 on it, if at all possible. I have a basic understanding of these things - but I can't understand why the phone would be fooled into thinking it's in another country. My assumption is that such information is stored somewhere that isn't wiped between flashing.
Really clueless at the mo'. I wanna try flashing stock, but I fear doing so will fix nothing, and my last hair will fall out - I feel that the problem would affect all installations.
(I wouldn't mind using CM, but it's a big buggy, and I need stability above all else).
It does in fact seem that my problem lies in the CSC. Samsung Kies, being what it is, seems to have incorrectly indicated where I am.
An appstore app has identified my CSC as being VIP (which is one from Croatia). I will attempt to correct this issue via whatever method I can find, and see what happens.
Update: As it happens, I've successfully flashed stock ROM (4.2.2), corrected CSC (and verified it with root explorer, to confirm it's the right one), flashed 4.4.2, it installed all the proper Vodafone apps (in English).
However the odd ghost tapping problem remains: even when holding my finger on the touchscreen, it behaves as if I were tapped eratically everywhere near the original tapping point.
The device name is still read as incorrect when plugged into USB. I am certain this is software related now, or rather, some freakin' leftovers I can't seem to find and clean.
Hi,
This is from the S4 section, so don't use any files from here, but the advice may help perhaps..
http://forum.xda-developers.com/showthread.php?t=2611340
Other than that, I can't find anything relevant on XDA for your device. It could be hardware if flashing stock firmware didn't help. You can ask about it here if you wish,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed