Database Develop

How do I root the frk76 OTA update?

I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.

SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.

SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)

Don't know what the above means
Does 2.3.1 work without modification?

While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?

Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!

sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?

envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.

Pete has a stock rooted FRK76 Rom on his website, fyi

My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.

flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.

I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.

Is there a RUU i can run to unroot my phone?

YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.

stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one

YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site

Nexus 7 wifi constant reconnect after 4.3 upgrade

Hi,
I had a rooted first gen Nexus 7 running under stock 4.2. It was pretty good. I rooted it and had TWRP.
I upgraded to 4.3 OTA, and then rerooted using the wugfresh toolkit. Now my wifi keeps reconnecting every few seconds to every minute. I seem to be the only one reporting this issue. I'm kind of a Android newbie. Would my best chance of fixing this issue be to go back to stock 4.2? How do I downgrade? I still have TWRP, but I'm not sure if that helps.
I'm kind of an Android newbie - I only follow the guides out there, don't really know what I'm doing.

What version of the toolkit did you use to reroot? The old version's root is not meant for 4.3.

Username invalid said:
What version of the toolkit did you use to reroot? The old version's root is not meant for 4.3.
Click to expand...
Click to collapse
Try using the latest version of the toolkit, if that doesn't work and you absolutely need root then add it to your rom yourself by flashing the latest SuperSU from Chainfire, i'm sure you can find the latest version with a bit of digging.

Try DroidWall to stop things connecting that you don't want to connect. I've used it for a long time on my GS2/N7 and it's been great. Also there is an option WiFi - settings- Advanced- Scanning always available, is this turned off/un checked?

easy life said:
Try DroidWall to stop things connecting that you don't want to connect. I've used it for a long time on my GS2/N7 and it's been great. Also there is an option WiFi - settings- Advanced- Scanning always available, is this turned off/un checked?
Click to expand...
Click to collapse
Not relevant to the OP. The problem is the system Wi-Fi, not individual apps. The scanning always available setting doesn't cause reconnections either, since it just leaves the antenna live to passively grab SSID data when the device is sleeping.
OP, Wi-Fi's been a bit flaky on this device with 4.3 in particular, but a clean flash has resolved most of the trouble for me.

Wipe Clean and ReROM and ReRoot
Ive been running 4.3 OTA and rooted with chainfires .zip in TWRP
I would suggest since you have root to back up with Titanium Backup. Backup your apps and data then use Wug's toolkit to flash back to stock clean. Then root with the new version of the toolkit and all should be well! Then restore your apps and data with TiBu again!
Good Luck!

freddy0872 said:
Ive been running 4.3 OTA and rooted with chainfires .zip in TWRP
I would suggest since you have root to back up with Titanium Backup. Backup your apps and data then use Wug's toolkit to flash back to stock clean. Then root with the new version of the toolkit and all should be well! Then restore your apps and data with TiBu again!
Good Luck!
Click to expand...
Click to collapse
EDIT!!! My Nexus was in MTP mode instead of the camera mode. That's why I couldn't ADB.
I don't really need to backup any apps on it. No apps I want to back up. But, I just tried the latest 1.6.8 of Wug's toolkit, and I couldn't get the ADB working! Weirdest thing. I had it working just the other day!
So...now I'm stuck. I can see the button on Wug's toolkit that let's me flash the factory 4.2.2 rom, but since ADB isn't working, I can't do anything. I've got USB debug mode checked. I've tried going through the driver install process a few times now. I don't know what's going on. Using the original USB cable. When I plug the tablet in, I see the ADB mode message on the windows task bar.
Ugh.

Lost root and gapps wont work!

So my G5 Active was rooted and I had all of my mods and root apps etc. but then one day an at&t update appeared so since i had safestrap and multiple backups i wanted to see if supersu's survival mode worked... Well it did not work so the i went to reboot my phone and the safestrap boot screen didn't popup nor can i go into the safestrap recovery installer and boot into safestrap by clicking "boot into safestrap". So not the end of the world i don't desperately need root (even though i would like it back) but the playstore cant connect to the internet. I have tried re-installing and uninstalling updates. So this is really annoying and in my opinion a big problem but when i went to my workplace the next day and i connected to the Wifi at my workplace it worked again so then i realized that the only difference between my wifi and my offices wifi is that my offices wifi uses a proxy. So then i though it was the host file since i was having this problem right before i lost root and updated gapps and i had adaway. I cant access the host file without root and i tried using ADB push/pull and when i try to push it back it says read only interface so now I'm really stuck and help wold be much appreciated. Thank for taking the tome to read this.

I believe you have to ODIN back to before the update and then block the update, I haven't seen anyone say this is successful but what I understand it should be.
http://forum.xda-developers.com/showthread.php?t=2799754

Thankyou
thepktrckt said:
I believe you have to ODIN back to before the update and then block the update, I haven't seen anyone say this is successful but what I understand it should be.
http://forum.xda-developers.com/showthread.php?t=2799754
Click to expand...
Click to collapse
It work!!! Thanks

thepktrckt said:
I believe you have to ODIN back to before the update and then block the update, I haven't seen anyone say this is successful but what I understand it should be.
http://forum.xda-developers.com/showthread.php?t=2799754
Click to expand...
Click to collapse
I did exactly that last night. I used ODIN to downgrade to Build ANE4 after the OTA update installed Build ANG3 on my Galaxy S5 Active. I had to do a factory reset afterward because my stock email app was repeatedly crashing. But towelroot worked and I'm back to normal with the OTA update frozen by Titanium Backup.

"Error: device not found" when in Recovery - can't figure it out

Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!

@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..

cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.

try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)

apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.

Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.

teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.

Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?

apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.

Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer

Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!

apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.

Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well

Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.

Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.

apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks

su for remix not working and its diag mode (read cdma/qpst)

I know there is not much support for the remix, though it's essentially a mini 2...too. I have it s-off and unlocked. I have twrp recovery on it. The all in one utility on one of these threads didn't work well for twrp so I flashed it via fast boot. I've tried running the utility for gaining root but nothing shows up in twrp under sdcard. I have pushed it to another folder, I find it and flash the zip file but even though it says it finished fine, when I reboot nothing is there. Weak sauce2 works fine, but that's just temp. I want permanent root.
That said anyone know how to enable serial/modem communication to cdma/qpst on the remix? I've been trying forever. Im trying to backup the prl.

jobzombi said:
I know there is not much support for the remix, though it's essentially a mini 2...too. I have it s-off and unlocked. I have twrp recovery on it. The all in one utility on one of these threads didn't work well for twrp so I flashed it via fast boot. I've tried running the utility for gaining root but nothing shows up in twrp under sdcard. I have pushed it to another folder, I find it and flash the zip file but even though it says it finished fine, when I reboot nothing is there. Weak sauce2 works fine, but that's just temp. I want permanent root.
That said anyone know how to enable serial/modem communication to cdma/qpst on the remix? I've been trying forever. Im trying to backup the prl.
Click to expand...
Click to collapse
I had the same issue today and was able to chat with the creators of Sunshine. They are super helpful and offer great support for their product. It took me a few tries but I have root. After you flash the latest version of Chainfire's supersu HERE , you have download the app from the playstore.
Not sure if this was related but right before I did the steps above, I switch over the the Nova launcher. One of the creators told me the stock blinkfeed launcher may give issues.

on1wheel said:
I had the same issue today and was able to chat with the creators of Sunshine. They are super helpful and offer great support for their product. It took me a few tries but I have root. After you flash the latest version of Chainfire's supersu HERE , you have download the app from the playstore.
Not sure if this was related but right before I did the steps above, I switch over the the Nova launcher. One of the creators told me the stock blinkfeed launcher may give issues.
Click to expand...
Click to collapse
How exactly did you accomplish it? Did you push su from recovery mode? I've been trying from just regular, ready to make calls, mode. Did you run a script or do it all manually? xbin or bin? I know some people like symbolic links to xbin/su within bin.

jobzombi said:
How exactly did you accomplish it? Did you push su from recovery mode? I've been trying from just regular, ready to make calls, mode. Did you run a script or do it all manually? xbin or bin? I know some people like symbolic links to xbin/su within bin.
Click to expand...
Click to collapse
I flashed the zip I linked above in TWRP recovery. You can connect your phone to a computer or download the supersu from your phone. After it is flashed, go to the play store and download the supersu app. I thought flashing would install the app on my phone but it didn't. After installing the app, pen it and it will prompt to install the binaries. After that I had root.
I'm not sure what you meant by xbin, bin, or symbolic links. I don't deal with any of that.

on1wheel said:
I flashed the zip I linked above in TWRP recovery. You can connect your phone to a computer or download the supersu from your phone. After it is flashed, go to the play store and download the supersu app. I thought flashing would install the app on my phone but it didn't. After installing the app, pen it and it will prompt to install the binaries. After that I had root.
I'm not sure what you meant by xbin, bin, or symbolic links. I don't deal with any of that.
Click to expand...
Click to collapse
OK, thanks. The Zip usually takes care of all that. I was having no success with a the zip file provided in the Windroid toolkit, so I was trying to push the same su that the toolkit downloaded to the phone and was trying it manually. I tried it with the one Weaksauce puts in the xbin folder as well temporarily. Both didn't work. I'll give this a go.
Thank you again!

Your welcome. I didn't use any of the methods you mentioned. I waited for the Sunshine 3 release to work and then tried the newest supersu zip. That did it. Now I'm waiting for a dev to port a rom to the HTC One Remix.

on1wheel said:
Your welcome. I didn't use any of the methods you mentioned. I waited for the Sunshine 3 release to work and then tried the newest supersu zip. That did it. Now I'm waiting for a dev to port a rom to the HTC One Remix.
Click to expand...
Click to collapse
I'm currently working on figuring out how to port it. Doesn't look like it should be too hard, but we'll see.

Txjacob said:
I'm currently working on figuring out how to port it. Doesn't look like it should be too hard, but we'll see.
Click to expand...
Click to collapse
I'll check back regularly. Which rom are you planning on porting. CM?

Successfully unlocked and s-off with sunshine. Then used su installer by the same guys for root yay! Now just waiting for devs to make or either port some Roms for the remix.

diag?
Was anyone able to get diag working on this phone yet?
I'm assuming after root you could use this program to get into usb settings and enable it:
https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite
But could someone confirm?