I had a Moto X 2013 Developer Edition (5.1 with XPosed) that recently died. As a stop gap until I can get something newer and nicer I bought a Droid Mini on Ebay. Here is the information on what it came with:
System version: 19.6.3.obakem_verizon.Verizon.en.US
Android version: 4.4
Baseband version: MSM8960PRO_BP_2323.031.111.00R
Kernel version: 3.4.42-gel1d6506-00006-g9ddacc8 [email protected] #1
Build number: SU2-3.3
It looks like my build number is older than those that seem to block unlocks. I was hoping to find a way to at least get root (get XPosed), and at most unlock the bootloader (flash a newer ROM). I am avoiding all system updates just in case they could ruin my chances of an exploit.
I have enabled loading 'other' applications and disabled verifying apps.
I've tried reading some of the threads here - some talk about loading tools like RockMyMoto onto the device and then using Impactor, but Impactor fails to access using telnet as a system level user. I tried installing PwnMyMoto 1.4.3 but I get certificate parse errors. I may be doing something wrong.
Does anyone know which threads I should be using for my build, or if I can't even do anything? I feel sort of lost. Any help would be appreciated.
ohioDroid said:
I had a Moto X 2013 Developer Edition (5.1 with XPosed) that recently died. As a stop gap until I can get something newer and nicer I bought a Droid Mini on Ebay. Here is the information on what it came with:
System version: 19.6.3.obakem_verizon.Verizon.en.US
Android version: 4.4
Baseband version: MSM8960PRO_BP_2323.031.111.00R
Kernel version: 3.4.42-gel1d6506-00006-g9ddacc8 [email protected] #1
Build number: SU2-3.3
It looks like my build number is older than those that seem to block unlocks. I was hoping to find a way to at least get root (get XPosed), and at most unlock the bootloader (flash a newer ROM). I am avoiding all system updates just in case they could ruin my chances of an exploit.
I have enabled loading 'other' applications and disabled verifying apps.
I've tried reading some of the threads here - some talk about loading tools like RockMyMoto onto the device and then using Impactor, but Impactor fails to access using telnet as a system level user. I tried installing PwnMyMoto 1.4.3 but I get certificate parse errors. I may be doing something wrong.
Does anyone know which threads I should be using for my build, or if I can't even do anything? I feel sort of lost. Any help would be appreciated.
Click to expand...
Click to collapse
Your best bet is Sunshine:
http theroot.ninja
I agree. Sunshine and Kingroot are the ways I rooted and unlocked my Droid Ultra on Android 4.4.4 (SU 4.21)
These are the steps I took:
1 ) I downloaded Kingroot and rooted temporarily with that, since Sunshine does a check to see if you're rooted. I was getting an error with Sunshine as it tried to temp root, but it would just restart the phone and nothing happened. This is the work around I found.
2 ) Downloaded Sunshine and let it do all it's tests that it runs, including the workaround in the previous steps
3 ) Bought the access code for $25. If you think about it, it's worth the $25 since a new phone with a newer OS is far more expensive than $25. Therefore you can keep up with the newest OS through free ROMs
4 ) Let Sunshine do it's thing
5 ) Install TWRP, CWM, or Philz
6 ) Have fun
pbarrette said:
Your best bet is Sunshine:
http theroot.ninja
Click to expand...
Click to collapse
xjewpacabrax said:
I agree. Sunshine and Kingroot are the ways I rooted and unlocked my Droid Ultra on Android 4.4.4 (SU 4.21)
Click to expand...
Click to collapse
I did download Sunshine and ran it through the tests - it says that it can get root and could unlock my phone if I paid. I'm surprised it didn't have in-app purchases - I was going to use Google Play but I guess you have to buy from the developers online or send them an Amazon Gift Card? Or maybe there is a way to use Google Play?
ohioDroid said:
I did download Sunshine and ran it through the tests - it says that it can get root and could unlock my phone if I paid. I'm surprised it didn't have in-app purchases - I was going to use Google Play but I guess you have to buy from the developers online or send them an Amazon Gift Card? Or maybe there is a way to use Google Play?
Click to expand...
Click to collapse
The only way that I am aware of is through the app using a debit/credit card. I wouldn't worry about it too much, since this app has been confirmed by multiple people on a myriad of devices as working and legitimate
If there is another way, hopefully someone else can chime in and let you know.
Related
OK, here goes. I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
So, has anyone running COS 12.1 had any luck with Android Pay? Thoughts, comments, suggestions are all welcome.
Hurricane Andrew said:
OK, here goes. I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
So, has anyone running COS 12.1 had any luck with Android Pay? Thoughts, comments, suggestions are all welcome.
Click to expand...
Click to collapse
Yes I have also fyi - there is also another thread talking bout Android pay and what we got it working on and which roms it does not work with. Did you try it with root enabled?
playya said:
Yes I have also fyi - there is also another thread talking bout Android pay and what we got it working on and which roms it does not work with. Did you try it with root enabled?
Click to expand...
Click to collapse
I first tried it with root enabled, then when that didn't work I did the full unroot. I will try with just disabling SU over the weekend and see what happens.
Hurricane Andrew said:
I first tried it with root enabled, then when that didn't work I did the full unroot. I will try with just disabling SU over the weekend and see what happens.
Click to expand...
Click to collapse
yeah with stock no need to full unroot. you can have bootloader unlocked root added and all that. Its just when you set it up make sure its stock root and not by using the supersu zip file. My findings was when I flashed Supersu it did not work but if I flashed stock rom then let TWRP inject root it worked. Of course I unchecked the option in supersu set up Android Pay then found one of those coke machines that take Android pay and tested it out.
As soon as I get my hands on this device I will be looking for vulnerabilities. Please everybody stay toned. ? I won't let you Maxx 2 owners down. I will get together with some brilliant Devs on here and we'll crack this device to its last security wall!! ??
DROID_4_UsEr said:
As soon as I get my hands on this device I will be looking for vulnerabilities. Please everybody stay toned. �� I won't let you Maxx 2 owners down. I will get together with some brilliant Devs on here and we'll crack this device to its last security wall!! ����
Click to expand...
Click to collapse
Placeholders are not allowed.
When you have something in hand you can pm me to move this thread to dev section.
For now belongs to General.
Thank you for your understanding.
DROID_4_UsEr said:
As soon as I get my hands on this device I will be looking for vulnerabilities. Please everybody stay toned. ? I won't let you Maxx 2 owners down. I will get together with some brilliant Devs on here and we'll crack this device to its last security wall!! ??
Click to expand...
Click to collapse
Any progress?
Anybody try kingroot?
I've tried KingRoot, along with several others.
KingRoot
FramaRoot
RootGenius
iRoot
Sunshine
KingoRoot (PC)
KingRoot was almost successful. After several attempts the kernel panicked enough that the SU binary was installed, but it didn't survive reboot.
My bootloader screen still shows the software state as "Modified," so I believe root could be easily achieved for someone with more experience than myself.
Sent from my XT1565 using XDA Free mobile app
This happens with some other devices and kingroot not holding past reboot. My new/used Maxx2 should be here next week and I suppose I can live without root for a while. Surprised to see almost no activity here, figured it would be a more popular device.
BeeRay02 said:
I've tried KingRoot, along with several others.
KingRoot was almost successful. After several attempts the kernel panicked enough that the SU binary was installed, but it didn't survive reboot.
Click to expand...
Click to collapse
Have you tried the latest version of KingRoot released 3-9-16?
NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk
Try this After Rooted with KingRoot:
- Install latest version of SuperSU from PlayStore or Superuser.apk from UPDATE-SuperSU-v2.65-20151226141550.zip
- Open SuperSu -> Update SU Binary -> Click Normal
- Other user management app detected -> *DO NOT REMOVE* -> *Click CANCEL*
- Binary updated Successfully -> *DO NOT REBOOT* -> *Click OK*
- Open SuperSu -> Settings -> Clean Up -> Remove other User Management apps
I just un-boxed my MAXX2 today.
It's not even charged or activated yet, but I will eventually test and report the results.
unaBonger said:
Have you tried the latest version of KingRoot released 3-9-16?
NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk
Try this After Rooted with KingRoot:
- Install latest version of SuperSU from PlayStore or Superuser.apk from UPDATE-SuperSU-v2.65-20151226141550.zip
- Open SuperSu -> Update SU Binary -> Click Normal
- Other user management app detected -> *DO NOT REMOVE* -> *Click CANCEL*
- Binary updated Successfully -> *DO NOT REBOOT* -> *Click OK*
- Open SuperSu -> Settings -> Clean Up -> Remove other User Management apps
I just un-boxed my MAXX2 today.
It's not even charged or activated yet, but I will eventually test and report the results.
Click to expand...
Click to collapse
Not even latest version works I tried already multiple times only goes to 27% and reboots and fails.
Sent from my Galaxy Nexus using Tapatalk
I'm wonder ing if a Razr Blade type root may be possible (enabling the battery saver controls) or maybe the Turbo (Sunshine app). Has anyone looked at the root for the Moto XPlay? It's the same phone, and I know the Maxx 2 is Verizon, but there must be something to work off of.
I like my Android devices to have root. It separates us from the idiotPhones. If there's a dev out there that needs boot records or such, I'll be more than willing to offer mine. Just tell me know how and I'll send it over.
Thank you!
Thanks so much! Any progress?
Anyone tried the rooting techniques on Android 6.0.1 Marshmallow? Everyone I know with the Maxx 2 is still on Lollipop.
cashmaster5 said:
Anyone tried the rooting techniques on Android 6.0.1 Marshmallow? Everyone I know with the Maxx 2 is still on Lollipop.
Click to expand...
Click to collapse
Same
I really wish there was root for this phone. Even just to delete bloatware, but custom roms would be nice too :|
pearlheartgtr said:
It separates us from the idiotPhones.
Click to expand...
Click to collapse
That is the greatest nickname I've ever seen given to iPhones.
JAS_21 said:
I really wish there was root for this phone. Even just to delete bloatware, but custom roms would be nice too :|
Click to expand...
Click to collapse
Agreed
does anyone tried this method? at unlockbootloader.org/tutorial/motorola-droid-maxx-2
its a little fishy, mb someone already tried. It's my last hope before giving up.
vvSaKvv said:
does anyone tried this method? at unlockbootloader.org/tutorial/motorola-droid-maxx-2
its a little fishy, mb someone already tried. It's my last hope before giving up.
Click to expand...
Click to collapse
I definitely wouldn't trust it. The ROM download link leads to a generic /download/rom_partN URL (not specific to Droid MAXX 2) that redirects to downloadsafe.org, and once there it presents one of those "Complete this survey so that advertisers can harvest your email address!" things. Also ScamAdvisor is extremely skeptical of this website. DO NOT TRUST UNLOCKBOOTLOADER.ORG.
JAS_21 said:
I really wish there was root for this phone. Even just to delete bloatware, but custom roms would be nice too :|
Click to expand...
Click to collapse
hi bro !
in my maxx2 Verizon , i have an option in DEVELOPER OPTIONS to enable oem lock or unlock, so i simply asked to you that, can it work with this command "fastboot oem unlock" ?
I'm on
Android security patch lvl ct6 2016
sys version : 24.74.4(update available)
Android ver. : 6.o.1
once it is unlock so we can easily install trwp and easily install root etc.
reply fast !
medoxXx said:
hi bro !
in my maxx2 Verizon , i have an option in DEVELOPER OPTIONS to enable oem lock or unlock, so i simply asked to you that, can it work with this command "fastboot oem unlock" ?
I'm on
Android security patch lvl ct6 2016
sys version : 24.74.4(update available)
Android ver. : 6.o.1
once it is unlock so we can easily install trwp and easily install root etc.
reply fast !
Click to expand...
Click to collapse
Motorola has an option to unlock the bootloader through their website. It won't work with the Droid Maxx 2, since Verizon locks their phones down, I now have a moto G4 plus I bought from Amazon. I used the OEM unlock option to root this device. It works on Verizon, but is not sold by them so it can be unlocked. Most Verizon phones are locked down pretty tight.
JAS_21 said:
Motorola has an option to unlock the bootloader through their website. It won't work with the Droid Maxx 2, since Verizon locks their phones down, I now have a moto G4 plus I bought from Amazon. I used the OEM unlock option to root this device. It works on Verizon, but is not sold by them so it can be unlocked. Most Verizon phones are locked down pretty tight.
Click to expand...
Click to collapse
I know that buddy, but what about this one ????
May i unlock it and than attempt a try ??
Ok so maybe im crazy but maybe im not
I have a Droid Razr MAXX HD (XT926) with kernel 3.4.42-gbd361ac running android 4.4.2
I use this phone without standard service (verizon) and instead with google voice and hangouts on wifi.
I have attempted to root, and unlock the bootloader with no success...
I have tried EVERY exploit in the book..... ive heard from various sources that it is impossible to root or unlock the bootloader on this phone because of an OTA update that i failed to block :V
Today i had a weird idea, in the play store, the Motorola Update Services app reads "update" but when clicked shows that the phone is not compatible with said new version.
I had a look at the permissions the already installed Motorola Update Services app had and they are pretty juicy....
I am wondering if, one of you android whiz's could help me code a fake update for the motorola update services app so i can utilize those permissions and root/unlock the bootloader at will.... that is assumming that the app already has the usable permissions (which im sure of cause its an ota updater)
Can anyone help me?
I use linux quite a bit already but ive never coded an android application....
Note: i cant find anywhere online with a valid download of this application :V maybe someone with a motorola phone could email it directly?
It sounds not as crazy you think!
But maybe there is a way to tell the update app, that you have an older version installed! Did you only got the latest version or can you update a version between the fake version number and the latest?
Maybe it is a way to think about for some developers/hackers... but to find someone he is interested in this device is the next problem! And this is the biggest i think!
And when you really sideload an update, is there an update checking in the running firmware? Maybe there is the real problem!
Gesendet von meinem Classic mit Tapatalk
I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.
No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.
captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?
themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.
Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.
I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper
Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170
I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180
Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...
bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install
Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8
Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks
I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
All -
I have a pair of G900V (Verizon Galaxy S5, his & hers) phones that I bought unlocked, both running G900VVRU2DPF4 build.
I'd like to dump the OEM Verizon apps - I don't want them, don't need them, and they're taking up space I'd like to use for something else, but I can't find them easily in the App Manager (I'm still fairly new to Android - I've been working in Windoze for years, and came up in Unix yonks ago...)
1) Can I strip these apps w/o root access?
2) If I need root access, is there an easy way to do it w/o having to change the firmware rev back & forth? (I did search for the PF4 build, but found minimal to no support on that particular topic WRT rooting.)
Environment:
- Samsung Galaxy S5 SM-G900V
- Android v6.0.1
- Security Patch Level: 01JUN2016
- Baseband Version: G900VVRU2DPF4
- Kernel Version: 3.4.0 ([email protected] #1 SAT 18JUN2016 085000KST)
- Build Number: MMB29M.G900VVRU2DPF4
- SE for Android Status: Enforcing. SEPF_SECMOBILE_6.0.1_0011, 18JUN21016 085445
- Hardware Version: G900V.05
- Security Software Version: MDF v1.1 rel 6; VPN v1.4 rel 6.0
- KNOX Version:
-- KNOX 2.6
-- Standard SDK 5.6.0
-- Premium SDK 2.6.0
-- Customization SDK 2.6.0
-- Container 2.6.0
-- CEP 2.0.1
-- Enterprise Billing 1.2.0
-- OTP: 2.6.0
-- SE for Android 2.4.0
-- SSO 2.5.0
-- Shared Devices 2.6.0
-- TIMA 3.2.002
-- VPN 2.2.4
- Configuration Version: 313.SAM.SMG900V.1
(I've done tech support - I'd rather give you too much information than not enough. But, if I've missed anything you need to know, ask! I'll look it up for you, if you tell me where to find it...)
JDK
EDIT - Although, I just saw the post on FolderMount - I may want to get root access just for that anyhow, even if I don't need it to strip the OEM Verizon apps....
JDKelley said:
I'd like to dump the OEM Verizon apps - I don't want them, don't need them, and they're taking up space I'd like to use for something else, but I can't find them easily in the App Manager
Click to expand...
Click to collapse
So, I don't believe you can remove them without root and unfortunately the Verizon version this phone makes life a little more difficult. You can't root 6.0.1 without unlocking your bootloader, which can only be done on certain variants (there's tons of info/threads in this forum). You can, however, downgrade, root, and then flash a debloated, nonrooted, 6.0.1 ROM. It's a pain in the ass, but not all that difficult and of course you'll lose your settings and have to set everything back up. Again, there are multiple threads with detailed instructions in this forum.
If you go that route, you should definitely check and see if you're able to unlock your bootloader and do so if possible.
tsew2674 said:
So, I don't believe you can remove them without root and unfortunately the Verizon version this phone makes life a little more difficult. You can't root 6.0.1 without unlocking your bootloader, which can only be done on certain variants (there's tons of info/threads in this forum). You can, however, downgrade, root, and then flash a debloated, nonrooted, 6.0.1 ROM. It's a pain in the ass, but not all that difficult and of course you'll lose your settings and have to set everything back up. Again, there are multiple threads with detailed instructions in this forum.
If you go that route, you should definitely check and see if you're able to unlock your bootloader and do so if possible.
Click to expand...
Click to collapse
Oh, FFS. You're telling me that the only way (at present) is to roll the OS /back/ to a previous version, /then/ root them phone, then roll the OS /forward/ again - and all that is IFF the "bootloader" can be unlocked?
Why do people insist on making things so bloody difficult?
JDKelley said:
Oh, FFS. You're telling me that the only way (at present) is to roll the OS /back/ to a previous version, /then/ root them phone, then roll the OS /forward/ again - and all that is IFF the "bootloader" can be unlocked?
Why do people insist on making things so bloody difficult?
Click to expand...
Click to collapse
Yeah, it's frustrating because this would be a decent phone and is capable of much more than Verizon is allowing it to be. Again, it's possible to get to same state that you're currently in (6.0.1, no root) without the oem apps, but you'll have to downgrade, root, then flash a debloated rom. If you're lucky enough to have a phone with a code that starts with 15, go ahead and unlock the bootloader and flash something current.
tsew2674 said:
Yeah, it's frustrating because this would be a decent phone and is capable of much more than Verizon is allowing it to be. Again, it's possible to get to same state that you're currently in (6.0.1, no root) without the oem apps, but you'll have to downgrade, root, then flash a debloated rom. If you're lucky enough to have a phone with a code that starts with 15, go ahead and unlock the bootloader and flash something current.
Click to expand...
Click to collapse
Which code would I be looking at/for?
JDKelley said:
Which code would I be looking at/for?
Click to expand...
Click to collapse
Check out the first post of this thread, it's got all the information you are looking for.
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
tsew2674 said:
Check out the first post of this thread, it's got all the information you are looking for.
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
Sorry been away so long, been busy.
Gah, what a headache this is turning out to be! Now, I'm not sure I want to go thru with it all - perhaps I'll wait until someone comes out with a rooter for 6.0.1, instead. I'm fairly sure I'll screw something up with the rollback-root-rollup process (I think of myself as fairly technically inclined, but I've been known to screw things up on occasion. HARD. Kinda like, "You did /what/ to the entire RAID array? Really? How'd you manage /that/?")