Related
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can't downgrade now due to the bootloader update.
KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X
KidJoe said:
Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
Not to nag, but probably important to correct... you CAN'T downgrade now.
Updated last night. I did it cause I wanted to be on latest and greatest, plus I think the camera does take better low-light pictures now.
Schaweet said:
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.
cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
Not much different, you can always update everything but motoboot and gpt so you can still downgrade if you don't like...
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
FWIW, The only things I notice are that USB OTG works in 4.4.2 and static in bluetooth headphones when using wifi is gone.
Schaweet said:
You don't have root unless you put the custom recovery back on there.
Click to expand...
Click to collapse
I beg to differ. Root Explore, Greenify, Wifi Tether for Root... all work, as do going into system and renaming files, and downloading/installing the hosts file in AdAway from BigTinCan.com (which survive power off/on, so helps to tell me write protection is still disabled).
On an unlocked bootloader, once you have rooted, you can use whatever recovery you like.
Now, for LOCKED bootloader on the X which are rooted via RockMyMoto or SlapMyMoto without using MotoWPNoMo, you might need to keep that "recovery trick" in place so you can boot with write protect disabled. In that case you would loose the ability to boot with write protect disabled (which makes root useless) when you put stock recovery back on, but that is different and doesn't "unroot" you.
---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------
Mike7143 said:
Not to nag, but probably important to correct... you CAN'T downgrade now.
Click to expand...
Click to collapse
You are right. that is a Typo that I need to fix!!!
cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
It took me about an hour to do the update because I am a novice and had to do a bunch of stuff first but I did it and my phone is back to its current state...except now I am using the xposed wifi tether instead of the hack (And the xposed one is better). So it was worth it just to have the latest and get rid of that wifi mod that i never liked to begin with. Apparently the upate makes battery life better but my battery life was already awesome considering I came from Gnex. So I guess the question is why not update? If you know what you are doing it shouldnt take 5-10 minutes.
from what people are saying it seems 4.4.2 makes a huge difference for battery life, i don't have it yet on my xt1058 so i can't say for sure...
Yeah I really only root for the tether hack and tibackup. Both of which I've used less and less since I got this phone. I've never had any issues with the phone and battery life is awesome so I'll probably just wait for some more feedback on the update before I go through the hassle of doing it.
How do you get rid of the unlocked bootloader message? Just flashing logo.bin?
jawest12 said:
How do you get right of the unlocked bootloader message? Just flashing logo.bin?
Click to expand...
Click to collapse
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
CartlandSmith said:
If you are rooted and locked on 4.4 using SlapMyMoto and MotoWPNoMo, can you downgrade to 4.2.2 and use PwnMyMoto then RockMyMoto then SlapMyMoto 0.5c to get the "recovery trick" back? Or is the ability to do that gone once you have used MotoWPNoMo?
Click to expand...
Click to collapse
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.
KidJoe said:
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.
Click to expand...
Click to collapse
Thank you for the response. Where can I download your logo.bin to flash?
tcrews said:
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.
Click to expand...
Click to collapse
For a n00b,,,,,English please?!
jawest12 said:
Thank you for the response. Where can I download your logo.bin to flash?
Click to expand...
Click to collapse
See the "edit" section of Post #150 in this thread -> Moto X Boot Logos The post also has info how they were made and a link to a zip that contains a little more than 25 LOGO.BIN files, and matching BMP's so you can see what they look like first (or use to flash clogo if you have never unlocked your bootloader). they do include the 0-3% battery indication too.
I'm using Logo-prettydev2.png.bin included in the zip file.
PennyKnight said:
For a n00b,,,,,English please?!
Click to expand...
Click to collapse
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.
tcrews said:
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.
Click to expand...
Click to collapse
Also for noobs, how do I flash the stock recovery?
Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app
zackiv31 said:
Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
No. Flashing Recovery does NOT erase data. Using RSDLite to flash an entire SBF/XML file (without editing it) will erase data.. or giving the following command via PC with your phone in fastboot mode will erase data... mfastboot erase data
KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
How do I undo the entitlement apk. I tried to reverse it but messed it up.
Not good at that stuff.
Thanks
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Thanks..
ro xl123 said:
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
Click to expand...
Click to collapse
Follow the NUMEROUS instructions already posted. There are some in my signature
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
Click to expand...
Click to collapse
No, that's why every guide says to downgrade
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
Click to expand...
Click to collapse
Yes, messing with the bootloader can lead to a hard brick, yes you need root to backup the TA
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Click to expand...
Click to collapse
Follow the link in my signature to get that done
ro xl123 said:
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
Click to expand...
Click to collapse
The answare are spread over here, why do not take some more time to read?
ro xl123 said:
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
Click to expand...
Click to collapse
To root your Z1 (C6906) you have to downgrade to .534 Firmware, Install DualRecovery, Ungrade to Pre-Rooted Kitkat by NUT.
ro xl123 said:
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
Click to expand...
Click to collapse
No way! You have to downgrade then upgrade to pre-rooted version.
ro xl123 said:
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
Click to expand...
Click to collapse
Is not dangerous. You brick phones just doing mistakes. You don't have to Unlock Bootloader to gain Root. So skip this part.
ro xl123 said:
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Click to expand...
Click to collapse
Download the lates DualRecovery for Z1 which have CWM, Philz and TWRP Recovery, all 3 in one. Just run the application from PC and install to phone, but you have to be on .534 FW.
Start reading here:
http://forum.xda-developers.com/showthread.php?t=2711982
---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
@gregbradley ..LOL..
Thanks all. Thank you for your help.
eclyptos said:
The answare are spread over here, why do not take some more time to read?
To root your Z1 (C6906) you have to downgrade to .534 Firmware, Install DualRecovery, Ungrade to Pre-Rooted Kitkat by NUT.
No way! You have to downgrade then upgrade to pre-rooted version.
Is not dangerous. You brick phones just doing mistakes. You don't have to Unlock Bootloader to gain Root. So skip this part.
Download the lates DualRecovery for Z1 which have CWM, Philz and TWRP Recovery, all 3 in one. Just run the application from PC and install to phone, but you have to be on .534 FW.
Start reading here:
http://forum.xda-developers.com/showthread.php?t=2711982
---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
@gregbradley ..LOL..
Click to expand...
Click to collapse
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
ro xl123 said:
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
Click to expand...
Click to collapse
Nothing, because you cannot flash it as you do not have a recovery yet///
Please follow the instructions in my signature, they are correct
gregbradley said:
Nothing, because you cannot flash it as you do not have a recovery yet///
Please follow the instructions in my signature, they are correct
Click to expand...
Click to collapse
So what is usb flash mode then?
when asked to enter flashmode hold the volume down button on your (Turned off) phone and attach the usb cable
ro xl123 said:
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
Click to expand...
Click to collapse
This is why the people get confused. Downgrade to .534 first, then install DualRecovery, then follow the Instruction from that link to get to your Firmware Rooted.
I think @[NUT] should add this steps on his threads for people like you who start from not rooted .681, .757 and so on.
eclyptos said:
This is why the people get confused. Downgrade to .534 first, then install DualRecovery, then follow the Instruction from that link to get to your Firmware Rooted.
I think @[NUT] should add this steps on his threads for people like you who start from not rooted .681, .757 and so on.
Click to expand...
Click to collapse
Well, I tought Sony would be just like Samsung, after all they are both androids is what I tought. Well, it's diffrent :/ Anyways I got to make sure about the things I do, because they may end up as bad things such as brick or etc.
I got it now, it's almost done.
Back in S4, all I had to do was to take the phone into Odin mode, then flash tar.md5's via odin, and it was all over, I installed cwm and rooted without downgrading and so. I feel sad that Xperia wasn't like. Well it's a great phone tough..
thanks alot everybody!
ro xl123 said:
Well, I tought Sony would be just like Samsung, after all they are both androids is what I tought. Well, it's diffrent :/ Anyways I got to make sure about the things I do, because they may end up as bad things such as brick or etc.
I got it now, it's almost done.
Back in S4, all I had to do was to take the phone into Odin mode, then flash tar.md5's via odin, and it was all over, I installed cwm and rooted without downgrading and so. I feel sad that Xperia wasn't like. Well it's a great phone tough..
thanks alot everybody!
Click to expand...
Click to collapse
It's very easy to Root the Z1, if I will had a chance in 5 minutes all will be done and the pain gone.
eclyptos said:
It's very easy to Root the Z1, if I will had a chance in 5 minutes all will be done and the pain gone.
Click to expand...
Click to collapse
Well, yeah but the downgrading part kind of sucks. Anyways, after installung recovery, it's all easy
ro xl123 said:
Well, yeah but the downgrading part kind of sucks. Anyways, after installung recovery, it's all easy
Click to expand...
Click to collapse
Just put the .534 FW in Flashtool Folder and flash it. Then connect to PC and use the Installer to install Dual recovery...the rest you know...
BTW, wipe everything any time you flash anything (Data, Appslog, Cache) to execute a clean installation. Yes, you will lose your data, but better be safe instead have issues later.
eclyptos said:
Just put the .534 FW in Flashtool Folder and flash it. Then connect to PC and use the Installer to install Dual recovery...the rest you know...
BTW, wipe everything any time you flash anything (Data, Appslog, Cache) to execute a clean installation. Yes, you will lose your data, but better be safe instead have issues later.
Click to expand...
Click to collapse
So, having root and recovery without unlocking bootloader in version .757 OFW is not possible? The thing is, I don't really want to unlock the bootloader, but i really want to have root privilleges, recovery mod is optional tough, i tought i could root easily with using CWM. So what I want is not possible?
ro xl123 said:
So, having root and recovery without unlocking bootloader in version .757 OFW is not possible? The thing is, I don't really want to unlock the bootloader, but i really want to have root privilleges, recovery mod is optional tough, i tought i could root easily with using CWM. So what I want is not possible?
Click to expand...
Click to collapse
So you just telling me that you did not understood a single word from what we already told you, great!
Follow the 3 steps provided by @gregbradley
eclyptos said:
So you just telling me that you did not understood a single word from what we already told you, great!
Follow the 3 steps provided by @gregbradley
Click to expand...
Click to collapse
No, I understood but kinda didn't wanted to.. :/
I already downgraded, rooted and installed recovery. Then I updated to stock rom 757 back, thinking that I could simply root using recovery. Anyways, after I updated, I couldn't get in to recovery mode, because the one I installed was without unlocking bootloader, I simply installed firmware based recovery. I don't really think about unlocking bootloader, the TA codes and stuff kinda scares me.. I did took backup of my TA tough. I just need to have root in OFW Kitkat. I can do without recovery (which i can't install because of bootloader). But root is essential. :/
ro xl123 said:
No, I understood but kinda didn't wanted to.. :/
Click to expand...
Click to collapse
You did NOT.
Downgrade, install DualRecovery, upgrade with the Pre-Rooted .757 using the method for LOCKED Bootloader by NUT here: http://forum.xda-developers.com/showthread.php?t=2711982
Start from the line How to update to 14.3.A.0.757:
DONE.
eclyptos said:
You did NOT.
Downgrade, install DualRecovery, upgrade with the Pre-Rooted .757 using the method for LOCKED Bootloader by NUT here: http://forum.xda-developers.com/showthread.php?t=2711982
Start from the line How to update to 14.3.A.0.757:
DONE.
Click to expand...
Click to collapse
OHHHHHHH... I'm so sorry, really. Now I understood it. Thanks alot man.. !! I love you :laugh:
ro xl123 said:
I love you :laugh:
Click to expand...
Click to collapse
I love you too.
I see an OC5 on swappa. Can I root and update to OF3 securely with this? What is the least time consuming to root?
When you root it let me know i have the at&t s5 on lollipop been told its unrootable
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
I used one click root for the root. But the bootloader stays locked on at&t s5, so their are two options that i know of. One, use odin and the correct tar to unlock it which is risky, or use an app called safestrap. Thats what I did.
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
Stonecold. I believe you have to revert back to 4.4.2 to root. But it can be done.
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
stonecold36067 said:
When you root it let me know i have the at&t s5 on lollipop been told its unrootable
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
I believe you have to revert to 4.4.2 to root. But it can definitely be rooted. I have an at&t s5 with superuser. I used one click root for the root.
It wont downgrade
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
My baseband is ng3. I had sucess using oneclick. But I am still on kitkat. Research how to use odin3 to revert your phone. I think I read something about that. Revert then root. Its impossible to root a phone unless on stock rom. Well, I believe it is.
est.mcmlxxvii said:
My baseband is ng3. I had sucess using oneclick. But I am still on kitkat. Research how to use odin3 to revert your phone. I think I read something about that. Revert then root. Its impossible to root a phone unless on stock rom. Well, I believe it is.
Click to expand...
Click to collapse
revert my phone to what? Your language is very ambiguous.
If you didn't have root before OTA 5.0 (Lollipop) you can't go back, you can't use safestrap, can't use Odin AND CANT ROOT YET. A locked loader won't allow you to use Odin to flash, and no root means can't get safestrap.. 1 click root only works before OTA 5.0 UPDATE. There is always a way but not yet.
ttom85 said:
If you didn't have root before OTA 5.0 (Lollipop) you can't go back, you can't use safestrap, can't use Odin AND CANT ROOT YET. A locked loader won't allow you to use Odin to flash, and no root means can't get safestrap.. 1 click root only works before OTA 5.0 UPDATE. There is always a way but not yet.
Click to expand...
Click to collapse
So if I root before then, then update to a custom Lollipop ROM I am good?
Also please hit REPLY
zetsui said:
So if I root before then, then update to a custom Lollipop ROM I am good?
Also please hit REPLY
Click to expand...
Click to collapse
There are a few threads on here how to get root, then upgrade to lollipop and keep root. Then you can still use safestrap to change loaders and roms. Safestrap just simply interupts the boot sequence(before the loader). I'm guessing once you upgrade, your loader will be locked also, so to change anything you'll have to have a back up on safestrap with the previous version, and unlocked loader... so you can go back and forth. I'm not sure of everything possible since my lazy ass never got root access before the update, so I'm sol for now. I'm planning on getting a new phone soon and giving this s5 to my wife anyway.
ttom85 said:
There are a few threads on here how to get root, then upgrade to lollipop and keep root. Then you can still use safestrap to change loaders and roms. Safestrap just simply interupts the boot sequence(before the loader). I'm guessing once you upgrade, your loader will be locked also, so to change anything you'll have to have a back up on safestrap with the previous version, and unlocked loader... so you can go back and forth. I'm not sure of everything possible since my lazy ass never got root access before the update, so I'm sol for now. I'm planning on getting a new phone soon and giving this s5 to my wife anyway.
Click to expand...
Click to collapse
Safestrap because it comes before the bootloader? Why not TWRP? Does twrp not come before the bootloader? Man I don't want anything to have to do with bootloaders again 3 years of solid rooting and dev experience and two GS3s in one day to ****ing updating the bootloader
zetsui said:
Safestrap because it comes before the bootloader? Why not TWRP? Does twrp not come before the bootloader? Man I don't want anything to have to do with bootloaders again 3 years of solid rooting and dev experience and two GS3s in one day to ****ing updating the bootloader
Click to expand...
Click to collapse
Bootloader is and has been locked, safestrap was the only recovery we had because it wasn't a traditional recovery in the sens that it didn't replace the stock one. With lollipop it broke, if you downgrade your kernel you can get it to work, but other than that you have to use flashfire which is not a recovery but simply a flashing tool. Twrp and any other recovery will not work, and any non-touchwiz based roms(aosp, aokp, cm) will not work, you have to use only touchwiz based ones and no custom kernels.
Sent from my Tw5ted SM-G900A using Tapatalk
Rakuu said:
Bootloader is and has been locked, safestrap was the only recovery we had because it wasn't a traditional recovery in the sens that it didn't replace the stock one. With lollipop it broke, if you downgrade your kernel you can get it to work, but other than that you have to use flashfire which is not a recovery but simply a flashing tool. Twrp and any other recovery will not work, and any non-touchwiz based roms(aosp, aokp, cm) will not work, you have to use only touchwiz based ones and no custom kernels.
Sent from my Tw5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
no aosp at all or just non-touchwiz aosp wont work? man **** samsung and att. i mean this was the entire allure of the phone say over an iphone. Seems like so many constraints for flashing compared to the GS3. Retarded.
who do I donate to that is working on rooting this pos?
I'm looking to pick up a new S5. What version/baseband number should I look for that is still rootable?
Let me know when orbif you find out. I want mine rooted too
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
I have engineering root kernels for g920a, g925a and g928a, I can get full root but after I reboot gets stuck at boot animation
So I need an experience dev that builds kernels to help me out with this
Contact me via PM
Due to the locked boot loader i don't think it's possible but i could be wrong
schhy said:
Due to the locked boot loader i don't think it's possible but i could be wrong
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=o5-JI1vhgfs
thatotherguy.. said:
https://www.youtube.com/watch?v=o5-JI1vhgfs
Click to expand...
Click to collapse
Link yields this...
tibere86 said:
Link yields this...
Click to expand...
Click to collapse
The guy who posted the video removed it, thinking that Samsung will patch the exploit (?).
EDIT: he's selling it for $700/phone. He already rooted G920AZ, G920A, G928A running Lollipop 5.1.1.
shichemt said:
The guy who posted the video removed it, thinking that Samsung will patch the exploit (?).
EDIT: he's selling it for $700/phone. He already rooted G920AZ, G920A, G928A running Lollipop 5.1.1.
Click to expand...
Click to collapse
I'm not sure why he removed it, Samsung can't patch anything without having the files, he's selling it for 700 for all phones, but I have them myself and it's not full root access witch I'm working on
thatotherguy.. said:
I'm not sure why he removed it, Samsung can't patch anything without having the files, he's selling it for 700 for all phones, but I have them myself and it's not full root access witch I'm working on
Click to expand...
Click to collapse
Any news on the G890A Active? Would be nice to have root. Not sure how much different it is besides battery and active button.
Sent from my SAMSUNG-SM-G925A using Tapatalk
thatotherguy.. said:
I have engineering root kernels for g920a, g925a and g928a, I can get full root but after I reboot gets stuck at boot animation
So I need an experience dev that builds kernels to help me out with this
Contact me via PM
Click to expand...
Click to collapse
You have the "engineering root kernel" or engineering sboot, aka bootloader?
If you have the sboot all you need is a sepolicy patched kernel for the device to boot.
Edit: Here is the G920A_OJ7_Sepolicy_Patched_Kernel.tar.md5 which should allow the device to boot with a rooted system assuming what you have is the engineering bootloader for the G920A OJ7 build. Warranty bit may be tripped.
muniz_ri said:
You have the "engineering root kernel" or engineering sboot, aka bootloader?
If you have the sboot all you need is a sepolicy patched kernel for the device to boot.
Edit: Here is the G920A_OJ7_Sepolicy_Patched_Kernel.tar.md5 which should allow the device to boot with a rooted system assuming what you have is the engineering bootloader for the G920A OJ7 build. Warranty bit may be tripped.
Click to expand...
Click to collapse
I have engieering KERNEL , engineering sboot wouldn't root the phone, you need a kernel to do that..
thatotherguy.. said:
I have engieering KERNEL , engineering sboot wouldn't root the phone, you need a kernel to do that..
Click to expand...
Click to collapse
An eng sboot is an unlocked bootloader so the sky is the limit, e.g. custom recovery, kernel, root.
Never heard of an eng kernel but it would likely have to be permissive to allow you to push in root via sbin.
Is it permissive?
My rooted G920A 5.1.1 OJ7 reads "-eng" after the kernel version (paid $40 for remote root, I do not have the file). No troubles at all, reboots fine... Maybe somebody else also working on these?
Apexseal said:
My rooted G920A 5.1.1 OJ7 reads "-eng" after the kernel version (paid $40 for remote root, I do not have the file). No troubles at all, reboots fine... Maybe somebody else also working on these?
Click to expand...
Click to collapse
Cool...is there a link to the engineering kernel? Also, does it read enforcing under SE for Android Status?
Yes it says enforcing in Security Enhancements.
---------- Post added at 12:07 AM ---------- Previous post was at 12:02 AM ----------
I don't know about the engineering kernel, I got it rooted remotely. Doing some "googling" I found a site that sells OL2 engineering FW for $25 (supossedly engineering fw).
Apexseal said:
My rooted G920A 5.1.1 OJ7 reads "-eng" after the kernel version (paid $40 for remote root, I do not have the file). No troubles at all, reboots fine... Maybe somebody else also working on these?
Click to expand...
Click to collapse
You don't have full root, download root checker and try, if you have full root your phone would get stuck, the kernel is mainly meant for a program that unlocks phones but needs root to do it
Sent from my SAMSUNG-SM-G925A using Tapatalk
thatotherguy.. said:
You don't have full root, download root checker and try, if you have full root your phone would get stuck, the kernel is mainly meant for a program that unlocks phones but needs root to do it
Sent from my SAMSUNG-SM-G925A using Tapatalk
Click to expand...
Click to collapse
how do you installl it?
clip3009 said:
how do you installl it?
Click to expand...
Click to collapse
Bootloader slot in odin...
---------- Post added at 03:37 PM ---------- Previous post was at 02:54 PM ----------
thatotherguy.. said:
You don't have full root, download root checker and try, if you have full root your phone would get stuck, the kernel is mainly meant for a program that unlocks phones but needs root to do it
Sent from my SAMSUNG-SM-G925A using Tapatalk
Click to expand...
Click to collapse
That is correct, I just checked with root checker. I guess an engineering bootloader would make it boot again? Unless the newer "eng" ones are locked also.
Apexseal said:
Bootloader slot in odin...
---------- Post added at 03:37 PM ---------- Previous post was at 02:54 PM ----------
That is correct, I just checked with root checker. I guess an engineering bootloader would make it boot again? Unless the newer "eng" ones are locked also.
Click to expand...
Click to collapse
An engineering, unlocked bootloader will allow you to flash a patched kernel that will allow the device to boot with traditional root, i.e. a modified system.
I did some googling yesterday and thought I came across an eng G920A sboot.bin, aka bootloader (the website mistakenly called it an eng kernel). If its legit it should do the trick once paired with the patched kernel, aka boot.img, I previously posted. But I don't own a G920A so can't test.
muniz_ri said:
An engineering, unlocked bootloader will allow you to flash a patched kernel that will allow the device to boot with traditional root, i.e. a modified system.
I did some googling yesterday and thought I came across an eng G920A sboot.bin, aka bootloader (the website mistakenly called it an eng kernel). If its legit it should do the trick once paired with the patched kernel, aka boot.img, I previously posted. But I don't own a G920A so can't test.
Click to expand...
Click to collapse
I own one and since now own a Nexus 6P, it just sits around doing nothing. More than happy to test. Worst case I'm back to stock via Odin. Point me to the files and I'll test. I'll already tried this route once and lost root trying so I'm willing to do it again.
metalcated said:
I own one and since now own a Nexus 6P, it just sits around doing nothing. More than happy to test. Worst case I'm back to stock via Odin. Point me to the files and I'll test. I'll already tried this route once and lost root trying so I'm willing to do it again.
Click to expand...
Click to collapse
Cool... I will pm you some stuff.
I have a Turbo with UDP and still have stock 4.4.4. I have the Sim card from my old RAZR Maxx in it that I trimmed down to the correct size (not sure if that makes a difference). I want to root for 3 main reasons - 1. WiFi hotspot. 2. Do away with some bloat. 3. Stop Ota screen that pops up every day.
I know the first thing I need to do is mofo root. I just want someone's suggestions who has already rooted. I still want a reliable phone without any weird glitches or something I constantly have to fool with. If I can stick with the 4.4.4 and just make those changes that would be OK with me. Or if someone knows a good smooth operating ROM to use please point me in the right direction. Thanks
Mofo is not the current root method... Sunshine is, and it's a better option overall. Also, if you're still on 4.4.4 you need to update to Lollipop to run Sunshine. I see no reason to stick to 4.4.4, either. I recommend catching up on the various threads about this, as they probably answer your questions, for the most part.
My personal choice is to stay with the stock ROM because I have heard of too many issues with Bluetooth and VoLTE on the CM-based ones. You could consider CF's ROM which is based on stock, if you want to move away from "stock".
EDIT: A few links to get you started:
http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
http://forum.xda-developers.com/droid-turbo/development/roms-t3347701
Forwarning - the latest OTA for SU4TL-49 will permalock (for now, at least) the bootloader, so DON'T apply that update - the first thread details that info as well.
Mofo Root/Kitkat 4.4.4 went out over 7 months ago (November 2015), when Sunshine team found an exploit for Snapdragon 805 devices and 5.1 Lollipop to unlock the bootloader.
With 5.1 and Sunshine you can have REAL root and TWRP custom recovery.
Just be very careful and do NOT update to SU4TL-49. That's the most recent update (pushed out in May 2016) where Verizon finally closed the Sunshine exploit.
There's a link in Development to flash SU4TL-44, which works with Sunshine.
Once your bootloader is unlocked, then you can update to SU4TL-49. It can't lock it back. It just prevents it from being unlocked.
Additonal Droid Turbo Root Info - XT1254 - QuarkSecurity Patch level 2016-04-01
Requirements; Unlocked Bootloader, Sunshine(Latest) SuperSU, TWRP Manager. Additional Suggested; Rom Manager(Helpful) Titanium Backup(Helpful) If you have updated to 23.21.49.quark_verizon.verizon.en.US vzw, (Tested only on this stock rom) and you do not have root, as long as you unlocked your bootloader, there is an EASY rooting method. I always reset first for testing, but you probably do not have to.......1: download and install Sunshine. Run Sunshine. When it gives you "temp root", minimize the app, (remember not to have any options set to kill when out of focus) download and install SuperSU, Set the following options in SuperSU, Enable Superuser, Default Access GRANTED, Enable SU DURING BOOT, Make sure Mount namespace seperation is checked, Turn OFF tapjacking protection, )can be re-enabled after process is finished, INSTALL SuperSU into /system, Trust System User, Enable PRO(Pseudo). Shut the phone Down. Restart. You have root. Now install TWRP manager, install the recovery suite, setup as you see fit. Optional, but useful, if you use a terminal as I do, install Sudo installer using the recovery install. Optional/ Titanium Backup is nice for people who play with roms, and root, etc....Rom manager is also very useful. Remember in most cases, if you have an option that does not specifically say DROID TURBO, or has the turbo hardware id, the DROID MAXX options usually work. Hope someone other than me has fun with this....:0) Remember, UNLOCK THE BOOTLOADER FIRST. This whole thing is mainly directed at the people who already unlocked the bootloader, and then upgraded somehow, and lost root.
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
this DOES work with SU4TL-49!
SXRXNRR said:
Requirements; Unlocked Bootloader, Sunshine(Latest) SuperSU, TWRP Manager. Additional Suggested; Rom Manager(Helpful) Titanium Backup(Helpful) If you have updated to 23.21.49.quark_verizon.verizon.en.US vzw, (Tested only on this stock rom) and you do not have root, as long as you unlocked your bootloader, there is an EASY rooting method. I always reset first for testing, but you probably do not have to.......1: download and install Sunshine. Run Sunshine. When it gives you "temp root",
This whole thing is mainly directed at the people who already unlocked the bootloader, and then upgraded somehow, and lost root.
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
this DOES work with SU4TL-49!
Click to expand...
Click to collapse
Uhmm... it does NOT work with SU4TL-49.
Lots of people have said even with unlocked bootloader, Sunshine no longer gives temp root with SU4TL-49 installed.
Read this thread:
Help Needed From XT 1254 Developers Please
http://forum.xda-developers.com/moto-maxx/help/help-xt-1254-developers-please-t3390557
It's specifically from an XT1254 user with an unlocked bootloader, who installed the OTA SU4TL-49 and no longer could get TEMP ROOT. Luckily, once we figured out he had an unlocked bootloader, he just had to install TWRP to get permanent root!
If you already have an unlocked bootloader, the best way is to get root is to go ahead and install TWRP and then root,
I don't understand the people who unlocked their bootloader prior to SU4TL-49 and did not then go ahead and permanently root their phones... But apparently they are out there. They were constantly using Sunshine temp root and now with SU4TL-49 that no longer works.
Worked on mine. Want pics?
It worked on mine. Want pics of it????
ChazzMatt said:
Uhmm... it does NOT work with SU4TL-49.
Lots of people have said even with unlocked bootloader, Sunshine no longer gives temp root with SU4TL-49 installed.
Read this thread:
Help Needed From XT 1254 Developers Please
http://forum.xda-developers.com/moto-maxx/help/help-xt-1254-developers-please-t3390557
It's specifically from an XT1254 user with an unlocked bootloader, who installed the OTA SU4TL-49 and no longer could get TEMP ROOT. Luckily, once we figured out he had an unlocked bootloader, he just had to install TWRP to get permanent root!
If you already have an unlocked bootloader, the best way is to get root is to go ahead and install TWRP and then root,
I don't understand the people who unlocked their bootloader prior to SU4TL-49 and did not then go ahead and permanently root their phones... But apparently they are out there. They were constantly using Sunshine temp root and now with SU4TL-49 that no longer works.
Click to expand...
Click to collapse
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
I did exactly as stated, it is perm root. I dont know why you would challenge that? Im sitting here with it? With sudo terminal, twrp, titanium root, etc....im not delusional dude.
ChazzMatt said:
Uhmm... it does NOT work with SU4TL-49.
Lots of people have said even with unlocked bootloader, Sunshine no longer gives temp root with SU4TL-49 installed.
Read this thread:
Help Needed From XT 1254 Developers Please
http://forum.xda-developers.com/moto-maxx/help/help-xt-1254-developers-please-t3390557
It's specifically from an XT1254 user with an unlocked bootloader, who installed the OTA SU4TL-49 and no longer could get TEMP ROOT. Luckily, once we figured out he had an unlocked bootloader, he just had to install TWRP to get permanent root!
If you already have an unlocked bootloader, the best way is to get root is to go ahead and install TWRP and then root,
I don't understand the people who unlocked their bootloader prior to SU4TL-49 and did not then go ahead and permanently root their phones... But apparently they are out there. They were constantly using Sunshine temp root and now with SU4TL-49 that no longer works.
Click to expand...
Click to collapse
---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------
Seriously, I read these posts, and tried anyway. It worked. Isnt that what we are supposed to do? share our finds?
SXRXNRR said:
It worked on mine. Want pics of it????
Click to expand...
Click to collapse
Yes, I would like to see pics, considering that the developer of Sunshine (who is a professional security researcher) said himself that it would not work on SU4TL-49. That, along with the many, many reports of people saying that it does not work on SU4TL-49, cause reason for suspicion.
And yes, XDA is for sharing findings, but only if those findings are valid and do not lead to other people doing things that they will regret based on bad advice.
SXRXNRR said:
It worked on mine. Want pics of it????
I did exactly as stated, it is perm root. I dont know why you would challenge that? Im sitting here with it? With sudo terminal, twrp, titanium root, etc....im not delusional dude.
Seriously, I read these posts, and tried anyway. It worked. Isnt that what we are supposed to do? share our finds?
Click to expand...
Click to collapse
OF course you have TWRP, because you installed TWRP with an unlocked bootloader. But you probably didn't get temp root with SU4TL-49 first. You got root from TWRP.
All I'm questioning is getting temp root first with SU4TL-49 installed -- on an XT1254 with unocked bootloader which had previously never had TWRP or other permanent root before that.
If you got managed to get temp root first with SU4TL-49 first (and had never installed TWRP or rooted before), you must have a magical phone. @jcase would be very interested.
What would you show me pics of? You've already installed TWRP and rooted -- which can be easily be done with an unlocked bootloader and TWRP. Showing us pictures of that doesn't show us anything.
If you have an XT1254 with an unlocked bootloader and no root, the best way is to go ahead and install TWRP custom recovery and root. (You can only unlock your bootloader with Sunshine prior to instaling SU4TL-49.)
I dont need kudos from anybody. I shared because I did it. On a factory reset turbo, that was updated. I dont care if you dont believe either. makes no difference to me. Obviously posting here is grounds for attack. I was simply sharing, It worked. Consider the conversation closed. I wont be sharing anything here. TWRP was installed AFTER the temp root. Running sunshine and seeing TEMP root achieved, I installed SuperSU as stated, then TWRP manager, etc...Im a 45 year old security geek. I take offense with your attitude. I wouldnt post it if the steps didnt work. Thanks for the friendly atmosphere. Really. Maybe I do have a magical phone. WTFK?
ChazzMatt said:
OF course you have TWRP, because you installed TWRP with an unlocked bootloader. But you probably didn't get temp root with SU4TL-49 first. You got root from TWRP.
If you got temp root from SU4TL-49 first, you must have a magical phone. @jcase would be very interested.
What would you show me pics of? You've already rooted your phone and installed TWRP, which can be easily be done with an unlocked bootloader and TWRP. Showing us pictures of that doesn't show us anything.
All I'm questioning is getting temp root first with SU4TL-49 installed -- with no TWRP or other permanent root before that. If you have an unlocked bootloader, the best way is to go ahead and install TWRP and root. At that point, you had already unlocked your bootloader prior to SU4TL-49.
Click to expand...
Click to collapse
He probably has the su44 bootloaders
SXRXNRR said:
I dont need kudos from anybody. I shared because I did it. On a factory reset turbo, that was updated. I dont care if you dont believe either. makes no difference to me. Obviously posting here is grounds for attack. I was simply sharing, It worked. Consider the conversation closed. I wont be sharing anything here. TWRP was installed AFTER the temp root. Running sunshine and seeing TEMP root achieved, I installed SuperSU as stated, then TWRP manager, etc...Im a 45 year old security geek. I take offense with your attitude. I wouldnt post it if the steps didnt work. Thanks for the friendly atmosphere. Really. Maybe I do have a magical phone. WTFK?
Click to expand...
Click to collapse
See the previous post above from Sunshine dev. The "magical" part is you are somehow the exception if you had an unlocked bootloader, no permanent root, and installed the OTA. It won't work for most other people. Somehow you installed SU4TL-49 update but not the bootloader that goes with it. You must still have the SU4TL-44 bootloader.
Now that you are telling more details "On a factory reset turbo,", it's becoming clear you had root, TWRP installed before. What you are doing has been described in detail before in the thread (from May) I'm quoting below. It's nothing new, nothing fantastic.
But what you seemed to be describing at first was using Sunshine to get temp root when you never had permanent root before (and I wasn't the only one who thought so) . That scenario is impossible.
Posting here is not grounds for attack. We just don't believe you did something no one else has been able to do, without explaining why you were able to do it. Especially when there's no proof at each step, but an easy alternative explanation (TWRP, then root) if you really installed the complete SU4TL-49 update. There's been many, many people including myself who have done stuff, then said, "I'm not sure the exact steps I did to get here." With only 1 post prior to this, we have to question your seeming amazing story.
Now that you have added more details, all you did was re-flash TWRP on an unlocked bootloader phone that already had root and TWRP previously. That's been described since May, see thread quote below. It's for people who previously had root, re-set their phone to install the update. Then afterwards, yes, you can get temp root back with Sunshine. But the important part is at some point you already have permanent root prior to installing the OTA. See steps 11-16, as well as the trouble shooting.
New OTA Available for Droid Turbo
http://forum.xda-developers.com/droid-turbo/general/ota-available-droid-turbo-t3378576
TheSt33v said:
DO NOT UPDATE IF YOUR BOOTLOADER IS LOCKED AND YOU WANT TO UNLOCK IT AT SOME POINT
DO NOT UPDATE IF YOUR BOOTLOADER IS LOCKED AND YOU WANT TO UNLOCK IT AT SOME POINT
DO NOT UPDATE IF YOUR BOOTLOADER IS LOCKED AND YOU WANT TO UNLOCK IT AT SOME POINT
Small update to build SU4TL-49. Not Marshmallow. Claims "security patches and improved network performance."
How to Update with an Unlocked Bootloader
The update will only work if you have a 100% unmodified stock rom and recovery menu. If you're on CF's rom and you want to update to the latest version of that, see his page for details on how to do that.
1. Backup all data. Just in case. Definitely do this if you're coming from CM13 or RR. I don't remember if the OTA wipes your data or not.
2. Download this SU4TL-44 100% stock flashable zip here: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
3. Download the SU4TL-44 stock recovery menu here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8
4. Boot into TWRP.
5. Flash the file you downloaded in step 2 by selecting Install and browsing to the file.
6. In TWRP, select Install, followed by install image, and select the recovery image that you downloaded in step 3. Tell it to flash it to recovery, and flash it.
7. If you're coming from CM13 or RR, do a factory reset in TWRP. If you're coming from a modified stock rom, I still recommend this, but it's not mandatory.
8. Reboot to recovery to confirm that you see the stock recovery menu (a dead android with the words "no command").
9. Boot the phone normally. If TWRP offers to install SuperSU, say no.
10. The OTA update should appear. Take it and let it do its thing.
You now have a 100% stock, bootloader still unlocked, SU4TL-49 phone. If you want TWRP back so you can start flashing stuff again, keep reading.
11. Download and install Sunshine from here: http://theroot.ninja/
12. Download your preferred version of TWRP. The current stable version is here: https://dl.twrp.me/quark/. If you want baybutcher27's modded version that includes lots of handy additional features, you can get that here: http://forum.xda-developers.com/showpost.php?p=66877208&postcount=116
13. Download Flashify from the play store.
14. Open Sunshine and follow the instructions until it gains temp root. Disregard the message that says it isn't compatible with SU4TL-49.
15. Open Flashify, select Recovery Image, then browse to the version of TWRP that you downloaded in step 11. Flash it.
16. Reboot to recovery. You should see TWRP's lovely smiling face staring back at you.
How to Install the SU4TL-49 Modem Only
1. [HIGHLY RECOMMENDED] Flash the modded TWRP I mentioned earlier, select backup, backup only your modem.
2. Flash Computerfreek274's modem package that you can get here: https://www.androidfilehost.com/?fid=24545070682210570
3. If you have GPS or other modem-related issues, try flashing this to fix them: https://www.androidfilehost.com/?fid=24531035584725320
4. If you decide you don't like the new modem, restore the backup you made in step 1.
Troubleshooting
Issue: You followed all of the steps, but you still get an error when you try to take the OTA.
Solution: Backup your data and perform a factory reset using the stock recovery menu. You can do this by rebooting to recovery like you do when you want to boot TWRP, and when you see the "no command" screen, hold the power button and press volume up. Then select factory reset and do it.
Click to expand...
Click to collapse
TheSt33v said:
Yes, I would like to see pics, considering that the developer of Sunshine (who is a professional security researcher) said himself that it would not work on SU4TL-49. That, along with the many, many reports of people saying that it does not work on SU4TL-49, cause reason for suspicion.
And yes, XDA is for sharing findings, but only if those findings are valid and do not lead to other people doing things that they will regret based on bad advice.
Click to expand...
Click to collapse
Just like in your thread I quoted, it's clear now he had root, TWRP installed prior to a factory re-set to install SU4TL-49. He didn't initially disclose it was a factory re-set, and that he had previous permanent root and TWRP.
Perhaps unintentionally, he made it seem he only had unlocked bootloader and had been using Sunshine to get temp root. At least that's how I read it. Now with SU4TL-49, temp root will no longer works in that scenario. But if you've already gotten permanent root, TWRP and install the update -- even with a factory re-set -- you've made enough changes that Sunshine will still work to give you temp root.
At that point, yes Sunshine will still give you temp root -- just like you posted in your thread. To me, and it's my opinion only it seems your steps, downloading TWRP from Quark thread, using Flashify would seem simpler. You have TWRP and then can use TWRP to get root.
Once we know all the facts, his experience is not fantastic and if he had just read your thread we could have skipped the drama.
ChazzMatt said:
Just like in your thread I quoted, it's clear now he had root, TWRP installed prior to a factory re-set to install SU4TL-49. He didn't initially disclose it was a factory re-set, and that he had previous permanent root and TWRP.
Perhaps unintentionally, he made it seem he only had unlocked bootloader and had been using Sunshine to get temp root. At least that's how I read it. Now with SU4TL-49, temp root will no longer works in that scenario. But if you've already gotten permanent root, TWRP and install the update -- even with a factory re-set -- you've made enough changes that Sunshine will still work to give you temp root.
At that point, yes Sunshine will still give you temp root -- just like you posted in your thread. To me, and it's my opinion only it seems your steps, downloading TWRP from Quark thread, using Flashify would seem simpler. You have TWRP and then can use TWRP to get root.
Once we know all the facts, his experience is not fantastic and if he had just read your thread we could have skipped the drama.
Click to expand...
Click to collapse
Oops