Ever since rooting with superboot method. I lost my wifi. Is there a way to fix this?
mojonation1487 said:
Ever since rooting with superboot method. I lost my wifi. Is there a way to fix this?
Click to expand...
Click to collapse
My guess is you used a boot.img that is not compatible with the rom your running. example, you still running 2.3.0., and you used a 2.3.1 superboot boot.img, or vise versa. Can't always mix and match.
Related
So I've got a stock FRF85B setup. I'd like to be able to run some rooted apps, mainly something like SetCPU. Do I have to run a custom ROM or can I just obtain root and then install what I want?
clickwir said:
So I've got a stock FRF85B setup. I'd like to be able to run some rooted apps, mainly something like SetCPU. Do I have to run a custom ROM or can I just obtain root and then install what I want?
Click to expand...
Click to collapse
if apps requiring root are all you want, yes.
if flashing custom ROM or kernel are what you are looking for, you need custom recovery as well.
I got a file called 'update-nexusone-FRF85-root-signed.zip'. Can I just rename that to update.zip and do like I was doing for the other updates 2.1->FRF50, FRF50->FRF72 etc?
clickwir said:
So I've got a stock FRF85B setup. I'd like to be able to run some rooted apps, mainly something like SetCPU. Do I have to run a custom ROM or can I just obtain root and then install what I want?
Click to expand...
Click to collapse
have you unlocked you bootloader?
clickwir said:
I got a file called 'update-nexusone-FRF85-root-signed.zip'. Can I just rename that to update.zip and do like I was doing for the other updates 2.1->FRF50, FRF50->FRF72 etc?
Click to expand...
Click to collapse
+1... thanks
clickwir said:
I got a file called 'update-nexusone-FRF85-root-signed.zip'. Can I just rename that to update.zip and do like I was doing for the other updates 2.1->FRF50, FRF50->FRF72 etc?
Click to expand...
Click to collapse
If that is the (about)530KB update then you can do it that way if you want to go the long route.
You can get the already rooted custom ROMS like kang-o-rama frf85b final and flash them through custom recovery. Then you will be on 85b.
Also, here is the full update from 2.1. It took me from t-mobile stock 2.1 (edr79) to frf85b, but it works from most ROMS. This one you change to update.zip and go through stock recovery...If you haven't received it yet OTA.
Post #291
http://forum.xda-developers.com/showthread.php?t=712902&page=30
fineiwill89 said:
have you unlocked you bootloader?
Click to expand...
Click to collapse
No I have not. It's stock except for I've applied the google provided updates as they came out.
@adambenjamin The file I have is 2.9MB. How is it the long route?
My current understanding is I just rename this to update.zip, reboot into stock recovery, apply and reboot. There's more to it maybe? I think this is the one provided by Lox...? maybe.
Yes just rename update.zip with astro and boot into recovery just like the manual update process.
Well I tried it. Apparently there's more to it.
I got an error saying it's not a signed update. So I posted in the thread in the DEV section about it and we'll see what everyone says. Some people seem to be saying they need a custom recovery to run this, but can't put a custom recovery on because they need root first. I don't know.
No root for me.
If this helps at all I pulled some info from this guide to cobble something together. I already had my bootloader unlocked and I am unsure if the same method will apply to you as you are coming from stock. This also assumes you use a mac. Ignore the fluff about custom radios and images etc - this guide isn't specific to FRF85.
If you aren't urgent about this, I would hold off until you get better direction. If you don't mind tinkering around with your device then maybe this can get you in the right direction.
http://theonda.org/articles/2010/03...-performance-boost-and-some-serious-geek-cred
I wouldn't touch a mac with a 10 foot pole... unless I got a running start
I'm tempted to just wait for Cyanogen Mod 6 and go with that. There doesn't seem to be any easy way to get root. It seems complicated enough that I'd rather go with a full unlock, custom recovery and custom rom.
The method in the dev section works perfect on frf85b. I've got root with stock rom and stock recovery.
N1 w/ XDA App
How I was trying to root my phone by was unsuccessful.
Now I am trying to figure out away to erase the files that I pushed on my phone. I am trying to get the phone to the factory settings.
How would I do that???
btw can i root a version 2.2??
eax05 said:
How I was trying to root my phone by was unsuccessful.
Now I am trying to figure out away to erase the files that I pushed on my phone. I am trying to get the phone to the factory settings.
How would I do that???
btw can i root a version 2.2??
Click to expand...
Click to collapse
What method did you use to attempt at root?
What files did you push?
And yes, you can root 2.2
omarsalmin said:
What method did you use to attempt at root?
What files did you push?
And yes, you can root 2.2
Click to expand...
Click to collapse
I used the ATB method i think
This is perhaps a general Android question and one I have not found the magic search terms to find an answer. Before I mess with this phone, I'd like stock images of boot.img, recovery.img, and the OS itself. Is this possible without root?
I did a full adb backup (including shared stuff, system) but it's unclear if that will restore the phone to a factory state including the images above.
If anyone has any direction for me, much appreciated. Not getting far on my own. Thanks!
jaymzz said:
This is perhaps a general Android question and one I have not found the magic search terms to find an answer. Before I mess with this phone, I'd like stock images of boot.img, recovery.img, and the OS itself. Is this possible without root?
I did a full adb backup (including shared stuff, system) but it's unclear if that will restore the phone to a factory state including the images above.
If anyone has any direction for me, much appreciated. Not getting far on my own. Thanks!
Click to expand...
Click to collapse
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
C.Sweat said:
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
Click to expand...
Click to collapse
If anyone has that I9505G stock firmware to flash with Odin, I'd love to have it...
C.Sweat said:
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
Click to expand...
Click to collapse
Thanks - this is what I'd like to do, but I don't have the stock images to be able to do this. Also I don't have the ability to use Odin - I'm limited to its Linux counterpart heimdall which may explain the disconnect if Odin offers that service and heimdall does not. This is my first serious foray into Samsung - I'm missing some context I think.
I did locate "S4GE_v4_422.zip" which is supposed to be the stock ROM but it's obviously de-odexed and rooted. That may be fine for my use, but not necessarily a way back to day 0.
And I'd be happy to share the stock firmware if I can locate or download it from my phone.
Thanks for your help!
ack154 said:
If anyone has that I9505G stock firmware to flash with Odin, I'd love to have it...
Click to expand...
Click to collapse
Sorry, but im not sure where to find an Odin flashable Google Edition stock firmware (I can only find the flashable rom). Good luck
jaymzz said:
Thanks - this is what I'd like to do, but I don't have the stock images to be able to do this. Also I don't have the ability to use Odin - I'm limited to its Linux counterpart heimdall which may explain the disconnect if Odin offers that service and heimdall does not. This is my first serious foray into Samsung - I'm missing some context I think.
I did locate "S4GE_v4_422.zip" which is supposed to be the stock ROM but it's obviously de-odexed and rooted. That may be fine for my use, but not necessarily a way back to day 0.
And I'd be happy to share the stock firmware if I can locate or download it from my phone.
Thanks for your help!
Click to expand...
Click to collapse
No problem at all. Heimdall, like Odin, can flash the stock firmware as well. You can find the carrier specific flashable firmwares here
I think this is it...
http://forum.xda-developers.com/showthread.php?p=43500355
Not in a position to mount from work and see if it's rooted or not, but if I were bricked I don't think I'd care!
jaymzz said:
I think this is it...
http://forum.xda-developers.com/showthread.php?p=43500355
Not in a position to mount from work and see if it's rooted or not, but if I were bricked I don't think I'd care!
Click to expand...
Click to collapse
That's as close as we have right now. And yes, it is rooted. Mine prompted for SuperSU install as soon as it booted.
ack154 said:
And yes, it is rooted. Mine prompted for SuperSU install as soon as it booted.
Click to expand...
Click to collapse
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
stumbows said:
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
Click to expand...
Click to collapse
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
acejavelin said:
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
Click to expand...
Click to collapse
I didn't take a backup as TWRP broke during the process but the root worked. I am only on 6.0 so is that ok to resolve? I can't see the baseband details at the moment as I am boot looping due to trying to follow another guide on resolving my issues. Trying to load a stock rom on to my device through TWRP now. Will report back soon.
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
stumbows said:
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
Click to expand...
Click to collapse
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
acejavelin said:
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
Click to expand...
Click to collapse
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
stumbows said:
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
Click to expand...
Click to collapse
Nope... Not a clue, sorry.
My phone keeps bugging me to install OTA update for krack vulnerability. I tried and it sent my phone to boot loop and now I have it restored. My phone has xposed installed. What is the best course of action? I would like to update but if that's not possible can I at least stop having the message show up each time I unlock my phone?
You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.
thorin0815 said:
You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.
Click to expand...
Click to collapse
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.
twoplustwo said:
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.
Click to expand...
Click to collapse
Is it a good idea to avoid security updates? No, it isn't. Is it clever to avoid updated drivers? No, it isn't (at least in most cases).
You should have informed yourself about the backdraws of rooting your phone before you did it. You need to be completely on stock firmware without any changes
to the system files to be able to use an OTA for updating your phone. This is needed to be safe the OTA update works the way it should.
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.
thorin0815 said:
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.
Click to expand...
Click to collapse
How can this be done? I don't know what to search for in these threads?
twoplustwo said:
How can this be done? I don't know what to search for in these threads?
Click to expand...
Click to collapse
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
thorin0815 said:
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.
twoplustwo said:
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.
Click to expand...
Click to collapse
Same procedure as on other stock rom versions): you need ElementalX kernel to be flashed and afterwards your desired root method(magisk is recommended).
Guides like this are valid https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918