I used the one click method to root my xoom europe wifi and it worked and all was well.
Then I saw the thread on updating it to 3.1 required the stock system img.
So I reflashed the stock img and rebooted.
I got stock in a bootloop. I couldn't get back fastboot access. All I could get into was recovery through adb.
So I tried a factory restore and it worked but now I have no wifi. I see an error message when I click on wifi settings.
If anyone could help me fix this problem I would be greatful. Thanks!
There are a number of reasons that you could be getting a n error but the only time I've seen it myself was when I was changing the wpa_supplicant file out for one that could see ad-hoc networks and I needed to fix the permissions on the file. I don't know if it's the same cause but this fixed the error in my wifi, start by installing root explorer and navigate to system/bin mount as read/write then scroll down to the very bottom and long hold on the wpa_supplicant file then choose permissions and make sure all three boxes in the first two rows are checked and the first two on the last row. If that doesn't do it I don't know what to suggest. Admittedly it's a long shot but it's worth a try.
So I managed to use the restore and relock setting on the one click xoom which failed to boot it.
I then tried rooting it again and I was able using fastboot to get it up and running. Wifi and All...
However my UK Xoom now thinks it is a 3G US Xoom - and it is telling me I have updates to install which I am sure
will fail because it is not a stock Xoom.
I don't mind having it think it is a US Xoom however I would love to be able to update it as it asks.
Seeing as restoring to stock last time caused me to lose wifi (I didn't have wifi until the custom kernal wifi drivers where reinstalled by the
root software)... How can I go about updating now?
Related
I am overjoyed to see that there is finally an official gingerbread update that I can flash, and then a CM7 for this kernel, that doesn't have any bugs that are too annoying. However, it's been a while since I became an expert on flashing my old LG Eve. Is there a thread somewhere that outlines exactly how to do this for this exact phone and mod?
I've got a D2G, with Fission ROM. the phone is unlocked and rooted. I have an original ROM saved to flash to the phone if need be. Everything I would ever need is backed up using Titanium Backup. I've downloaded the GB update and CM7. I think I'm ready to go.
Questions:
- Is there a thread that answers all this already?
- Am I going to run into any problems being unlocked or rooted?
- Does the phone revert back to being locked once the new GB is installed? That would not be good considering I'm in Canada, not on Verizon. I bought my phone unlocked so I don't know how to just unlock it again.
- I remember using nandroid before to make a complete backup of the contents of my phone so that if I screwed up I could just go back to it seamlessly. Same thing this time around?
- I'm not completely illiterate here though, so I'm going to give it a go and you can just correct me where I am wrong. First, put the CM7 and GB files on the SD card. then do a nandroid backup of the phone. Clear data, clear cache. Then use clockworkmod to flash the GB update. then use clockworkmod again to flash CM7. then use clockworkmod again to flash gapps. Start up phone, do a complete restore with Titanium and I'll have all my apps and settings, call history and texts back. I'm probably wrong somewhere in all this, but where?
If there's not already a comprehensive thread on this, let this be it!
You will need to SBF to stock to be able to install the update.
Refer to the following for some instructions:
http://droid.koumakan.jp/wiki/SBF
http://droid.koumakan.jp/wiki/4.5.607_Firmware
http://droid.koumakan.jp/wiki/CyanogenMod
Ok, I read these all over about 5 times. So in a nutshell, these are the steps:
- use rsdlite to put your phone back to the stock firmware 2.4.330
- unroot and remove cwm
- use android recovery to install gingerbread 4.5.607
- root again and install cwm again
- use cwm to install cyanogen and gapps.
Correct?
Also, I am running fission. According to my system info it is firmware 2.4.3. I would rather skip step 1 and just install gingerbread. I am guessing I can't, but please confirm.
Sent from my DROID2 GLOBAL using XDA App
You don't need to unroot and remove CWM after flashing the SBF.
Otherwise everything's correct.
You cannot install the official Gingerbread firmware update onto a phone that is not running stock unrooted 2.4.330 without CWM and with all bundled software intact.
Note: if you need to backup your applications and configuration data, you can do so with CWM. Make a backup under Fission, then perform all those steps above, and once you're running CM7 on 4.5.607, use CWM's advanced restore feature to only restore /data.
So here I am in Gingerbread on my D2G (already further than I thought I'd get!) and you would think it would be smooth sailing from here... except I can't root it now! Is there a different technique for rooting in Gingerbread? I used Z4 before, and it worked in seconds.
OK, I figured out how to root using another thread. and when i am in adb shell I get "#" and not "$" after entering a string of commands.
But, apps think that I'm not rooted. All I need is to install CWM, but it runs into errors, presumably because I am not rooted.
The phone is in some sort of weird half-rooted state.
really weird experience with rooting. I realized that I hadn't done the additional steps where you push superuser to the phone and a couple other commands. So I did that, and then root check said i was rooted. I rebooted, and adb shell was acting like I wasn't rooted! yet root check still said I was. I was able to flash CWM and reboot, and then install CM7. Everything seems great!
except, right from the start I was getting repeated FCs for com.android.phone.
I remember that there's an issue with needing to reboot after switching to GSM... so I'm trying that now. Let's hope that stops the FCs.
So what ended up happening was, I rebooted and stopped getting the FCs for the phone after switching to GSM. So that is good. However, aside from the two minor bugs that I was prepared to live with, this is happening now:
- I have phone and SMS service, just no data. Wireless works fine, and so do GPS and Bluetooth to my knowledge.
- When attempting to select a network to register on, I get the dreaded “Your SIM card does not allow connection to this network” message. I have tried doing this with data/roaming enabled/disabled and with “only 2G” selected. I have also tried a couple of tips I found online such as removing the battery for 15 minutes and also getting a new SIM card.
- At first I was able to enter new APNs, but they wouldn’t save. I hit menu, then save, but it goes back to the APN screen and none are listed. Now, what happens is, if I hit menu, then “add new apn”, nothing happens.
I went into the telephony.db file to manually enter my APNs, and it seems that they are already there, which is good. I re-entered them all manually using sqlite anyway. This did not work. I also noticed that Verizon was listed with a “1” in current, which probably means that Verizon is my current APN. So I removed that 1 and placed it on all my rogers APN entries. Still, nothing is saved at the APN screen in settings, and I can’t enter them through that screen, either. And no data.
Suppose it turns out that this is just a bug with CM7 right now and it’s unusable for me. Obviously I don’t want to go all the way back to Fission on Froyo when I can use gingerbread. How far back into this process do I have to go? Can I just flash GB and it will overwrite CM7?
Did you make a CWM backup of your freshly installed Gingerbread? If so, just restore.
If not, I don't see how you're going to “just flash Gingerbread” without SBF'ing to 2.4.x.
Well, I have done a lot of testing and troubleshooting. I went back to the start of this whole process, and I backed up my APNs and fully tested the phone at every turn, and my conclusion is that CM7 is not friendly to APNs. There was no problem with stock Froyo or stock Gingerbread. With the working APNs that I had, I was able to use data on both. Once CM7 was installed, it was a no go.
I used a couple of apps to backup my APNs both in Froyo and Gingerbread prior to installing CM7, and when CM7 inevitably didn't allow me to use data, I tried to restore my APNs using these programs as well. They say that they worked, and it's true that if you go into root explorer the APNs are there as you entered them or restored them using a program. But it seems these APNs are not going to work unless you actually see them at the APN page in settings. And nothing I have tried up to this point has been able to make any APN show up at that screen.
I think the “Your SIM card does not allow connection to this network” message at the network operators screen, as well as my inability to enter APNs, are 100% related. I also bet there is a simple solution to it!
If anyone has any ideas about how to make an APN stick, and how to force a phone to start using it, please let me know. I'll also post this at the CM7 forum.
I'm fairly new to ROMs (this is my second). I have followed the instructions and successfully installed the ROM, modem, and update.
2 questions:
1) Wifi does not work (will not turn on). I had wifi problems on my last ROM. I have reinstalled this ROM numerous times today thinking something must have failed since wifi does not work. This seems to be unique to me since I can't find anything in the thread regarding wifi problems. Any suggestions?
I've gone so far as to use darkside superwipe as suggested in a different thread. Still can't get wifi to turn on (just sits with "Turning Wi-Fi on..." message on screen). Never errors out, just stays like that.
2) ROM Manager: Fix permissions fails. I get the following error when I select fix permissions: "An error occurred while attempting to run privileged commands!" Any suggestions?
Thanks so much for the help!
You should post your question in the ROM thread. The developer (seanscreamz) or one of the other testers will see it and be able to address your problem and help you out.
I can't post in the Dev section yet. 6 more posts and I will ask there.
starting over...
Ok, I figured I might as well make sure that my wifi woes are not a hardware issue. I've reverted back to stock Skyrocket OS to make sure wifi is available and working in stock form.
Following this link http://forum.xda-developers.com/showthread.php?t=1342348, I reverted to stock and I can confirm that wifi works in stock form.
I've also reformatted my sd card in case there is any chance a corruption on it would cause my problems.
Now going to reinstall SkyICS...
bored4long said:
Ok, I figured I might as well make sure that my wifi woes are not a hardware issue. I've reverted back to stock Skyrocket OS to make sure wifi is available and working in stock form.
Following this link http://forum.xda-developers.com/showthread.php?t=1342348, I reverted to stock and I can confirm that wifi works in stock form.
I've also reformatted my sd card in case there is any chance a corruption on it would cause my problems.
Now going to reinstall SkyICS...
Click to expand...
Click to collapse
Are you on CWM touch?
have you went into the busybox app and clicked install?
wifi broken again
I have followed these instructions here http://forum.xda-developers.com/showthread.php?t=1321582 to regain root. After getting root, I installed ROM Manager and selected "Fix Permissions". On reboot, I lost the ability to connect via wifi.
Did I miss a step?
Thanks again for holding a n00b's hand!
AT&T Samsung Galaxy S II Skyrocket Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1383
You have to install busy box
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
john: I'm sure you mean well, but I don't know what your intent was with your posted link.
crazyD: digging your avatar. I'm currently trying to decide between a G26 and XD9sc...
btw, installed and ran busybox. not sure what it did for me. I also updated ROM manager to latest. Accidentally initiated a backup from ROM manager. Will see if wifi is back after that has completed.
Edit: wifi still errors, won't connect. I'm not clear what steps I may have missed or screwed up between being stock to rooted. I will revert back to stock again and try again...
Are you running juice defender? Its giving me problems with my wifi connection!
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm not running Juice Defender. At this point, I'm trying to revert back to stock form again with working wifi.
Edit: ok, reverted back to stock by doing the following
1) reboot into CWM recovery
2) factory reset x3
3) clear cache x3
4) format system x3
5) clear dalvik x3
6) format emmc x3
7) restart and pull battery
8) boot into download mode
9) push stock tar (k0kane) via Odin3 v1.85
I now have wifi again!
So now I get to try to get back to SU and CWM without losing wifi...wish me luck.
still have wifi!
OK, rooted and CWM installed. I still have wifi, which is good. I'm afraid to select 'Fix Permissions' for fear that will break my wifi.
I'm going to install Sky ICS now and see what happens.
sky ics and wifi!
OK, It took a few attempts, but I now have SKY ICS installed and wifi is still working.
I've installed the base ROM and the modem...not the updated yet. My download speeds are terrible, but at least I have wifi. I think the data speeds get better on the update.
Sean's instructions say to let the phone "cache and settle". I have no idea what that means...so will try to wait 10 minutes or so before installing the update.
bored4long said:
OK, It took a few attempts, but I now have SKY ICS installed and wifi is still working.
I've installed the base ROM and the modem...not the updated yet. My download speeds are terrible, but at least I have wifi. I think the data speeds get better on the update.
Sean's instructions say to let the phone "cache and settle". I have no idea what that means...so will try to wait 10 minutes or so before installing the update.
Click to expand...
Click to collapse
My uneducated guess with the data speeds is the modem for UCLE2. I haven't had the chance to go to LTE on SKYICS yet, but data is definitely slower on "4g" networks.
Sent from my cm_tenderloin using Tapatalk 2
quick update
Here is a quick update:
I spent some time redownloading all my apps and in general setting up the phone. I then ran the SKY-ICS update. Everything seemed to be working great.
As an added bonus, the email app in SKY-ICS syncs with my employer's exchange server! Which is so awesome. The stock ROM, and the last gingerbread ROM I had on the Skyrocket would not connect to our exchange server. I was very pleasantly surprised by that functionality.
I then lost wifi again. Wifi seems to be unpredictable and I'm not sure if it is hardware or software related. I again have wifi this morning, but didn't for the last two days. Also, my phone won't restart, it appears to get stuck in a powerdown state.The haptic buttons stay lit, but the screen is blank. I have to pull the battery to get it to restart.
But overall, I'm very happy with the performance and functionality of SKY-ICS. I will do some digging on the restart problem.
I recently rooted my WiFi xoom using a combination of methods. One was with lord aio tool. One step was to flash an update zip file. Somehow I overlooked that. Is it needed? Solved: needed to give root access.
Now my stock launcher freezes and I have to reboot to get it to run for a few minutes before it freezes again. Not sure why?
When in eos r6 recovery, I try to wipe delvik cache and i get unknown path not found or something along those lines. I've read its fine, but is it still wiping?
sanity29 said:
I recently rooted my WiFi xoom using a combination of methods. One was with lord aio tool. One step was to flash an update zip file. Somehow I overlooked that. Is it needed?
Also I flashed wingray 112 and then updated to 113. Now my stock launcher freezes and I have to reboot to get it to run for a few minutes before it freezes again. Not sure why. I reflashed 112 and seems to be fine now. I do understand its a nightlies and i do know the difference. Just wondering if others had a similar issue?
When in eos r6 recovery, I try to wipe delvik cache and i get unknown path not found or something along those lines. I've read its fine, but is it still wiping?
Click to expand...
Click to collapse
Which zip file did you skip? Did you flash the Gapps zip file after flashing the rom? If you forgot to do that, you would have a lot of missing or non-functional apps and force closings.
The file not flashed was the update.zip file when doing manual root via lordaiotool's post. I message him and it was what gave you root. Funny as I had root even without it.
My biggest issue is that the stock launcher keeps not responding. A pop up comes up saying "launcher not responding" with options to wait or ok. I almost always need to reboot, but that doesn't last long till the launcher fails again, That is my biggest issue and not sure why? I haven't messed with anything as I setup the xoom as I had it before I rooted.
Why not PM the creator of the rooting tool you used? I'm not familiar with how it functions.
Unlocking and rooting the xoom is no longer the issue.
I'm currently running wingray 112 and the stock launcher keeps freezing up. Not sure why.
I did pm the creator about the update file and that is how I found out what its for.
Just wipe everything and start again.
Not being an ass, but if you have backups this shouldn't be a problem anyway.
That's what I was thinking I might do.
So,.... messing about as we do, trying to get an app to work that wont work on rooted device, I installed voodoo to temporarily hide my root and it seemed to work.
but now I cant regain root access. 1: Not sure if voodoo is the issue
2: tried all fixes that I could find on here and nothing working for me
Not really an issue at the mo and I'm sure theres a work around but as a quick fix / quick question
Can I just Flash a new custom rom while I no longer have root access?
I was going to try a different rom anyway. and don't mind losing data, apps etc
just need to know that I can flash without root and not going to get stuck somewhere
Cheers
You'll have to root again then flash.
mgalea1981 said:
So,.... messing about as we do, trying to get an app to work that wont work on rooted device, I installed voodoo to temporarily hide my root and it seemed to work.
but now I cant regain root access. 1: Not sure if voodoo is the issue
2: tried all fixes that I could find on here and nothing working for me
Not really an issue at the mo and I'm sure theres a work around but as a quick fix / quick question
Can I just Flash a new custom rom while I no longer have root access?
I was going to try a different rom anyway. and don't mind losing data, apps etc
just need to know that I can flash without root and not going to get stuck somewhere
Cheers
Click to expand...
Click to collapse
You can flash everything if you have a Custom recovery Installed eg : CWM or TWRP, Because both has Root enabled by default, even if the Rom doesn't have Root that doesn't mean your recovery doesn't have root, If the rom only doesn't has Root, you Recvoery has.
That means you still can flash everything. (I recommend to use the lastest version if you have a old version)
no custom rom installed
i had rooted my phone but for clearing up internal memory i did a factory reset.
After that i noticed my wifi stopped working and i had sort if partial root(root explorer worked but titanium backup didnt).
In order to correct that i tried to manually update the su binary by replacing the original with the latest one.once i did that i lost root completely.
T_T now i am stuck up with a non root phone without wifi working.
I tried flashing it but that also requires root.
Any help will be appriciated
my phone is spicemi280(stock)
please give a solution
hey guys i despirately need a solution to my problem
I had rooted my phone but after some time for clearing up
internal memory i did a factory reset.
After that i noticed my wifi stopped working and i had sort of
partial root(root explorer worked but titanium backup didn't).
In order to correct that i tried to manually update the su
binary by replacing the original with the latest one.Once i did
that i lost root completely.
Now i am stuck up with a non root phone without wifi
working.
I tried flashing it but that also requires root.
Tried rerooting it with superoneclick(used the same method to
root earlier) but it returned access denied
Any help will be appriciated
my phone is spicemi280(stock)
anyone,
someone,
no one
:'(
Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with a modded Galaxy S3 phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
pchemerys said:
Anyone here with a modded Galaxy S3 phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
Click to expand...
Click to collapse
i have no explanation for what happened, actually never heard it happen before.
why not try to re-root and see what happens. if that doesn't work, i would think your only option would be to flash it clean and start over.
Reroot. Or unroot then reroot.
yeah i was thinking that might have to be done.. was hoping not and that this was some sort of known or fixable issue...but may have no choice..will wait another couple days to see if i find anything and do it if no other option..
pchemerys said:
yeah i was thinking that might have to be done.. was hoping not and that this was some sort of known or fixable issue...but may have no choice..will wait another couple days to see if i find anything and do it if no other option..
Click to expand...
Click to collapse
well, i haven't seen any root methods that require wiping the phone, so why wait to try re-rooting?
I would try a new busybox with kinguser and reroot.