jcase said:
New in 3.1.15
Moto X 2014 support (needs root via MoFo or KingRoot)
Better HTC m9 5.1.x support
MoFo:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
KingRoot (APK version, top download)
http://www.kingroot.net/down
Neither of these root methods were developed by us, but both worked during testing.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2792487
Go show your appreciation to those guys and unlock your bootloader.
I am very exciteeeee!
I downloaded an I am trying to give Sunshine my money, but before I can do that I need a stock 5.1 img with root and without xposed. Where can I find such a jewel?
Edit: Found this IMG hoping it will work, I'll keep you posted.
That IMG does not work FYI, it got closer though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GatorsUF said:
That IMG does not work FYI, it got closer though.
Click to expand...
Click to collapse
Can you submit a support ticket, http://therootninja.zendesk.com and ill help figure this out
So to be clear, it's 45 bucks total (Mofo+Sunshine) and if you're on 5.1 you're SOL?
tekhna said:
So to be clear, it's 45 bucks total (Mofo+Sunshine) and if you're on 5.1 you're SOL?
Click to expand...
Click to collapse
The testing I did was done using KingRoot for temproot. Your mileage may very, but for the time being you need "some" form of root or temproot. If you have root via MoFo, that is fine too.
tekhna said:
So to be clear, it's 45 bucks total (Mofo+Sunshine) and if you're on 5.1 you're SOL?
Click to expand...
Click to collapse
That's what it sounds like. Unless a temproot is created which wouldn't surprise me with the recent stagefright exploit. Just be patient! ?
Sent from my XT1254 using Tapatalk
cadenmiller60 said:
That's what it sounds like. Unless a temproot is created which wouldn't surprise me with the recent stagefright exploit. Just be patient! ?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Ugh the main reason I upgraded to 5.1 was due to the memory leak. Hopefully I can use this in the future.
Sent from my Moto X
beaups said:
The testing I did was done using KingRoot for temproot. Your mileage may very, but for the time being you need "some" form of root or temproot. If you have root via MoFo, that is fine too.
Click to expand...
Click to collapse
MoFo doesn't work on 5.1 though, correct? So does KingRoot work on 5.1 then? Or did you use KingRoot on 5.0?
Will this do the trick?
http://forum.xda-developers.com/moto-x-2014/general/tool-xt10965-0lxe22-46-11-auto-flasher-t3139190
tekhna said:
MoFo doesn't work on 5.1 though, correct? So does KingRoot work on 5.1 then? Or did you use KingRoot on 5.0?
Click to expand...
Click to collapse
KingRoot doesn't work on 5.1.
Sent from my Moto X
Mac of York said:
KingRoot doesn't work on 5.1.
Sent from my Moto X
Click to expand...
Click to collapse
Ah well. So no viable unlock for 5.1 at this point.
@jcase
Would it help to get a rooted system from a XT1095?
cadenmiller60 said:
That's what it sounds like. Unless a temproot is created which wouldn't surprise me with the recent stagefright exploit. Just be patient! ?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
mediaserver runs as the media user, i dont think in our case it will bring us much if any closer to root. The IBM vuln may.
Red_81 said:
@jcase
Would it help to get a rooted system from a XT1095?
Click to expand...
Click to collapse
we are good thanks
I didn't know if the users need a rooted system image pulled to flash. I'm rooted with no other mods to system
Mac of York said:
KingRoot doesn't work on 5.1.
Sent from my Moto X
Click to expand...
Click to collapse
There are posts of it working for other devices. It will fail a couple of times and then just work. Also cases where the phone won't boot anymore. More of the latter now.
Not attempting and I suggest others dont either. Risk outweighs rewards with this being my main phone.
Visi0nofExcellence2 said:
There are posts of it working for other devices. It will fail a couple of times and then just work. Also cases where the phone won't boot anymore. More of the latter now.
Not attempting and I suggest others dont. Risk outweighs rewards with this being my main phone.
Click to expand...
Click to collapse
Kingroot shouldnt cause the phone to stop booting, odd. Thanks for makign the thread btw
jcase said:
Kingroot shouldnt cause the phone to stop booting, odd. Thanks for makign the thread btw
Click to expand...
Click to collapse
Not bootng is horribly ambiguous wording on my part.
chicodelta said:
My shield is running 5.1..1. I tried kingroot 4.5, since others have reported success and now my tablet won't boot past the nvidia screen. Anyone else encountered this issue?
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/general/root-kingroot-t3112722/page4
jcase said:
mediaserver runs as the media user, i dont think in our case it will bring us much if any closer to root. The IBM vuln may.
we are good thanks
Click to expand...
Click to collapse
Ok. Has the droid turbo been tested yet or no? Thanks.
Sent from my XT1254 using Tapatalk
SunShine 3.1.16 is out, better support for MotoX 2014, including custom roms
GatorsUF said:
That IMG does not work FYI, it got closer though.
Click to expand...
Click to collapse
Related
Confirmed working by myself and 2 other users so far.
http://forum.xda-developers.com/showthread.php?t=2771629&page=2#post53170206
I can confirm this method works. I am now rooted with w/p off. Finally!
Ohh Really Now?
Tharkys said:
I can confirm this method works. I am now rooted with w/p off. Finally!
Click to expand...
Click to collapse
Awesome! I'm still trying to read through the post...and still will after getting a response here but....
Will this work with the current OTA that i received about 2-3 weeks ago?
And I have to redo this after rebooting?
I don't even care about putting another rom on it (CM11 would be cool though) but I just wanna terminate the bloatware and get my AirStream App running again!!!
If this works...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can also confirm that write protect is off and I have SuperSU and Safestrap all successfully installed. I tried installing CM11 on romslot-1 but it displayed the droid with the red triangle. Any suggestions on how to get CM11 booting now?
I can also confirm this works. I'm rooted with Write Protection off at 4.4 & 19.6.3.
The exact steps have been posted later on, in the same thread.
lumewolff said:
I can also confirm that write protect is off and I have SuperSU and Safestrap all successfully installed. I tried installing CM11 on romslot-1 but it displayed the droid with the red triangle. Any suggestions on how to get CM11 booting now?
Click to expand...
Click to collapse
I'm not too sure but I think we need specific CM11 (AOSP builds) for SafeStrap or you need a Unlocked bootloader for AOSP Roms.
lumewolff said:
I can also confirm that write protect is off and I have SuperSU and Safestrap all successfully installed. I tried installing CM11 on romslot-1 but it displayed the droid with the red triangle. Any suggestions on how to get CM11 booting now?
Click to expand...
Click to collapse
AOSP based roms require a different kernel. Safestrp cannot flash kernels. No AOSP.
How lucky are you to have confirmed that write protection in fact could be turned off when even the exploit author himself believed otherwise? Great job OP.
Sent from my XT1030 using Tapatalk
zefyx said:
How lucky are you to have confirmed that write protection in fact could be turned off when even the exploit author himself believed otherwise? Great job OP.
Sent from my XT1030 using Tapatalk
Click to expand...
Click to collapse
Thanks, it all happened by fluke I guess I just wanted to make it work that bad haha
Sent from a carrier pigeon
Indeed. Probably should have snagged a scratch-off that day to celebrate!
Sent from my XT1030 using Tapatalk
I concur...
I know I originally asked if this is legit, but after trying it...
It's legit, Safestrap working, rebooted several times haven't lost root!
Do it guys!!! DO IT!!!
Confirmed working on Droid Mini XT1030.
I'm really impressed you found this just by experimentation and not reverse engineering code or anything like that.
Whenever I experiment, it usually ends in bad luck, hard-bricked devices, and tears!
Confirmed!
Confirmed working on my XT1080! Thank you for your effort! :highfive:
Im now rooted with WP off and have safestrap installed on my mini.
Ive had zero luck installing any custom roms and figured it was because I was on 4.4,19.5.3. I reinstalled OTA (19.6.3) , retained root but still am having no luck with Roms.
Can someone point me in the right direction? I can't find any Mini or rom forums but I think the Ultra is compatible so I've been looking around here.
Any help is appreciated , thanks !
Sent from my XT1030 using Tapatalk
patlanta said:
Im now rooted with WP off and have safestrap installed on my mini.
Ive had zero luck installing any custom roms and figured it was because I was on 4.4,19.5.3. I reinstalled OTA (19.6.3) , retained root but still am having no luck with Roms.
Can someone point me in the right direction? I can't find any Mini or rom forums but I think the Ultra is compatible so I've been looking around here.
Any help is appreciated , thanks !
Sent from my XT1030 using Tapatalk
Click to expand...
Click to collapse
Although MAXX/Ultra/Moto X ROMs will boot on your device, you will find there is no sound and you cannot flash them without an unlocked bootloader. Sorry.
At least I have an answer , thanks !
Sent from my XT1030 using Tapatalk
krazie1 said:
I'm not too sure but I think we need specific CM11 (AOSP builds) for SafeStrap or you need a Unlocked bootloader for AOSP Roms.
Click to expand...
Click to collapse
I had the Droid bionic before this phone. dhacker & hashcode made a safestrap flashable cm9/10. It had to be flashed in slot 1. Perhaps if some interest was shown, they would make one for the ultra/ maxx.
Sent from my XT1080 using Tapatalk
does anyone know if towelroot by geohot work on the moto x and droid series?
ceelos218 said:
does anyone know if towelroot by geohot work on the moto x and droid series?
Click to expand...
Click to collapse
You could try but I recall reading in the Towelroot thread that it won't work on Moto and HTC devices since /system is write protected.
Sent from a carrier pigeon
ceelos218 said:
does anyone know if towelroot by geohot work on the moto x and droid series?
Click to expand...
Click to collapse
I couldn't get it to work on a Droid Mini XT1030. Just sits there, never reboots. After a half hour (I have lots of patience), I rebooted manually and it did not have root.
I did not believe until I received it and tried flashing absolutely all firmware out there for 1225/1254/1250 without bricking it. I then moved on to my next step in plan - install any retail version firmware but Verizon. I started the experiment with 4.4.4 first and found that 1225 radio will not work in 1254 (baseband simply cannot be recognised). Then I flashed 1254 radio on top (later with boot.img as well) and this make everything work except Wifi cannot be turned on. Although I don't expect it to work, I tried 1225 5.0.2 firmware with 1254 radio and as expected it does not work.
Honestly I was hoping the 1254 radio + 1225 firmware will work in 4.4.4, which means it should work when 5.1 comes out for 1225. I tried to find related information but there weren't much, maybe due to lack of BL unlocked 1254s out there. I once read someone write about radio.img must go with boot.img but I tried that. Just wondering if any of you experts here have advices for me. Well, I am assuming my phone will not be bricked so I am brave!
@Skrilax_CZ can help you.
http://forum.xda-developers.com/dro.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
He can help you get CM12.1 working with the Verizon radio.
ikpchou said:
I did not believe until I received it and tried flashing absolutely all firmware out there for 1225/1254/1250 without bricking it. I then moved on to my next step in plan - install any retail version firmware but Verizon. I started the experiment with 4.4.4 first and found that 1225 radio will not work in 1254 (baseband simply cannot be recognised). Then I flashed 1254 radio on top (later with boot.img as well) and this make everything work except Wifi cannot be turned on. Although I don't expect it to work, I tried 1225 5.0.2 firmware with 1254 radio and as expected it does not work.
Honestly I was hoping the 1254 radio + 1225 firmware will work in 4.4.4, which means it should work when 5.1 comes out for 1225. I tried to find related information but there weren't much, maybe due to lack of BL unlocked 1254s out there. I once read someone write about radio.img must go with boot.img but I tried that. Just wondering if any of you experts here have advices for me. Well, I am assuming my phone will not be bricked so I am brave!
Click to expand...
Click to collapse
Whatever happens please report your findings back here! I'm curious how well the XT1225 CM12.1 works on your device.
BL unlock ../???
?
Sent from my XT1254 using Tapatalk
Would it be possible for you to upload a picture of your bootloader saying it is unlocked?
Sent from my XT1254 using XDA Forums
Murd0c said:
Would it be possible for you to upload a picture of your bootloader saying it is unlocked?
Sent from my XT1254 using XDA Forums
Click to expand...
Click to collapse
Yes that would be great.
PolishPoet said:
Yes that would be great.
Click to expand...
Click to collapse
I have just taken photos, but looks like I still cannot post until I post 10+ messages. Will write a bit more and do again.
PolishPoet said:
Yes that would be great.
Click to expand...
Click to collapse
ChazzMatt said:
@Skrilax_CZ can help you.
http://forum.xda-developers.com/dro.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
He can help you get CM12.1 working with the Verizon radio.
Click to expand...
Click to collapse
Thanks and have already written to him. Again, I am too new to this forum so am still accumulating my initial 10 posts in order to post under proper topic...
aneeshmbabu said:
BL unlock ../???
Click to expand...
Click to collapse
trikotret said:
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Murd0c said:
Would it be possible for you to upload a picture of your bootloader saying it is unlocked?
Sent from my XT1254 using XDA Forums
Click to expand...
Click to collapse
PolishPoet said:
Yes that would be great.
Click to expand...
Click to collapse
I know not too many would believe, until I can post the photos. Before I reach 10 posts, let me give a bit more information here - this unit was claimed to be unlocked by software, in 4.4.4 it shows UNLOCKED with status code 1, and in Lollipop it shows ENGINEERING. In both versions software version is MODIFIED instead of OFFICIAL. There are some discussion in China and it appears there are three ways to unlock - 1. engineering handset from factory, 2. officially unlocked, 3. software unlocked. The one I have is of the type 3, but as far as I can learnt from the internet, there is no major difference between type 2 and 3, if type 2 will ever exist...
mattlgroff said:
Whatever happens please report your findings back here! I'm curious how well the XT1225 CM12.1 works on your device.
Click to expand...
Click to collapse
Yes, I will certainly try it as soon as I received reply on the radio issue. At the moment I am still trying all I can to try to fix the Wifi cannot turn on problem in my 4.4.4 XT1254 radio + 4.4.4 XT1225 firmware combination. I honestly wouldn't mind using that for a while until I can use 5.1 XT1254 radio + 5.1 XT1225 firmware combination...
My objective is to get rid of Verizon firmware so the system is lighter and that I can have proper GSM call functions such as USSD, and tethering etc. I seem to remember that mixing firmware and radio can be done under the same Android version in the past with other Moto phones... Any suggestions or advices here would be highly appreciated.
Sorry for posting so much in a short time, I need to get to 10 posts and post the photos
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://photos.google.com/photo/AF1QipOBKBcquBHnpn02gN9xCxrXZyhojbRnkltBKWaf
https://photos.google.com/photo/AF1QipPDAZMVfUEEdWLHbVOrJHyuq5Wo06otxJ5xlU3u
unable to view photos said server not found
Yea. I can't see 'em either.
rriffle08 said:
unable to view photos said server not found
Click to expand...
Click to collapse
nijohnson said:
Yea. I can't see 'em either.
Click to expand...
Click to collapse
Oh, just figured out how to do it properly from Google Photo:
https://goo.gl/photos/5yakEUKRusT7sn136
Please see if this is ok now.
Woohooo
So your Turbo was purchased from China?
New PG1 OTA arriving 8/4. 385 meg in size, its the July security update.
From the Sprint Forum:
Samsung Galaxy Note 4 software update - version N910PVPU4DPG1
Features/Enhancements:
Android/Samsung July Security Update
Resolution to lock screen production issue
Updated VoWiFi client
Important Info:
Phased roll-out of the update starts on 8/4/16 and will be completed by 9/5/16
Keep in mind devices receive the update in phases each day. Customer Care cannot tell users when they will exactly get the update. Please do not call asking. Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it easy to root after installing this new update?
Sent from my SM-N910P using Tapatalk
anees02 said:
Is it easy to root after installing this new update?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You can root by installing TWRP using ODIN.
Updated my phone (which is not on Sprint Network as I live outside US) and must say, I'm quite impressed. There are no noticible UI changes but the system feels more snappier than before. I guess the Doze settings have been worked too because of which battery life has improved a tad bit.
Anyone know what Sprint meant by "Resolution to lock screen production issue"?
How can i root if i have this current version can anyone help me?
yairgeniz said:
How can i root if i have this current version can anyone help me?
Click to expand...
Click to collapse
Flash TWRP with ODIN and then flash SuperSU zip through that recovery.
Do you guys capture the download link?
Sent from my SM-N910P using XDA-Developers mobile app
Does anyone have a link to download it. I would prefer to not have to put my phone back to full stock to get to then reroot and set my phone back up.
Used to get lock ups/crashes every day on MM until this update. Haven't had a crash since PG1 flashed. Maybe that's what
"Resolution to lock screen production issue"
meant.
poit said:
Used to get lock ups/crashes every day on MM until this update. Haven't had a crash since PG1 flashed. Maybe that's what
"Resolution to lock screen production issue"
meant.
Click to expand...
Click to collapse
The update seems to be well polished this time! :good:
I'm Stock Rooted Pe2, will a Hotspot mod work? what ABout X posed stuff? I've beeN reading for a ABout a week and Can't figure out How to get X posed or Hotspot to work Consistently So I'm thinking of updating
potna said:
I'm Stock Rooted Pe2, will a Hotspot mod work? what ABout X posed stuff? I've beeN reading for a ABout a week and Can't figure out How to get X posed or Hotspot to work Consistently So I'm thinking of updating
Click to expand...
Click to collapse
Hot-spot mods of previous builds will not work. If you want, you can use pdanet or FoxiFi for it (no need of a rooted phone).
For Xposed, you can flash the zip available on XDA but you will require root for it.
PG1 source code isnt out, so developers will be behind still.
robinhood1808 said:
Hot-spot mods of previous builds will not work. If you want, you can use pdanet or FoxiFi for it (no need of a rooted phone).
For Xposed, you can flash the zip available on XDA but you will require root for it.
Click to expand...
Click to collapse
so xposed will work on pe2? i'd settle for just disabling home button unlock any ole way
potna said:
so xposed will work on pe2? i'd settle for just disabling home button unlock any ole way
Click to expand...
Click to collapse
I did not use Xposed, but it works even on PG1.
robinhood1808 said:
I did not use Xposed, but it works even on PG1.
Click to expand...
Click to collapse
Well you gave me hope and i found some site called devlab that had a tutorial with comments. In the comments i seen mention of an 85.1 alt version that a few were able to install. Short story : I got it installed and im happy on pe2 using the alt version
86 updated version works best. And is newest.
Sent from my 0x1 Note 4...... I love tep
I am on PE1... Could l update to PG1 without problems or I must update to PE2 then PG1?
Sent from my SM-N910P using Tapatalk
anees02 said:
I am on PE1... Could l update to PG1 without problems or I must update to PE2 then PG1?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You can skip updates with Odin. PG1 has been the best MM update to date for me.
Improved battery and Wi-Fi Calling for me.
Sent from my SM-N910P using Tapatalk
New OTA coming in today L29C567B183, I haven't installed it yet but grabbed some screenshots of the changelog.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess the next thread will be: how to get rid of dollhouse ordering alexa
My device: Mate 9 superroot, Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
https://forum.xda-developers.com/mate-9/how-to/mate-9-alexa-built-t3577308
is this the us variant? i have mha-l29c567b138 with no updates available.
wrecklesswun said:
is this the us variant? i have mha-l29c567b138 with no updates available.
Click to expand...
Click to collapse
Yes it's the U.S. variant. What carrier are you on?
Sent from my MHA-L29 using Tapatalk
I use the phone on AT&T although i have Google Fi (Tmobile, Sprint, etc) as well. the carrier makes a difference when updating?
wrecklesswun said:
I use the phone on AT&T although i have Google Fi (Tmobile, Sprint, etc) as well. the carrier makes a difference when updating?
Click to expand...
Click to collapse
Sometimes it does. Just a couple questions though:
1. Are you 100% sure you're on B138 and not B183?
2. Are you able to manually check for updates?
3. Are you checking for updates over LTE, WiFi, or both?
Sent from my MHA-L29 using Tapatalk
spc_hicks09 said:
Sometimes it does. Just a couple questions though:
1. Are you 100% sure you're on B138 and not B183?
2. Are you able to manually check for updates?
3. Are you checking for updates over LTE, WiFi, or both?
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
138 confirmed. Doing manually and auto, and on wifi and cellular.
I have tried on ATT and Tmo. At some point i was receiving the update but it would fail, After about the third time it stopped prompting me to update. I was wondering how to reset the update counter?
wrecklesswun said:
138 confirmed. Doing manually and auto, and on wifi and cellular.
I have tried on ATT and Tmo. At some point i was receiving the update but it would fail, After about the third time it stopped prompting me to update. I was wondering how to reset the update counter?
Click to expand...
Click to collapse
You may end up having to do what I did which was returning to complete stock. Are you currently rooted?
Sent from my MHA-L29 using Tapatalk
lucky.. I am stuck on c636 and have to pay to rebrand lol... no volte for me..
Jaimesco12 said:
lucky.. I am stuck on c636 and have to pay to rebrand lol... no volte for me..
Click to expand...
Click to collapse
That sucks! You can't rebrand it yourself though?
Sent from my MHA-L29 using Tapatalk
spc_hicks09 said:
That sucks! You can't rebrand it yourself though?
Click to expand...
Click to collapse
I think not at least that's what everyone is saying.. it sucks man. I am in the us not Asia lol. Kind of ruins the phone experience for me. Just waiting day by day until it becomes available for free checking every day
Jaimesco12 said:
I think not at least that's what everyone is saying.. it sucks man. I am in the us not Asia lol. Kind of ruins the phone experience for me. Just waiting day by day until it becomes available for free checking every day
Click to expand...
Click to collapse
If you need to use FunkyHuawei to rebrand, let me know. I have 1 token left.
Sent from my MHA-L29 using Tapatalk
spc_hicks09 said:
If you need to use FunkyHuawei to rebrand, let me know. I have 1 token left.
Click to expand...
Click to collapse
How many tokens would I need?
Jaimesco12 said:
How many tokens would I need?
Click to expand...
Click to collapse
Not sure how many it is for rebranding.
Sent from my MHA-L29 using Tapatalk
spc_hicks09 said:
You may end up having to do what I did which was returning to complete stock. Are you currently rooted?
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
I am rooted.
wrecklesswun said:
I am rooted.
Click to expand...
Click to collapse
I don't think you can get OTA's when rooted.
Sent from my MHA-L29 using Tapatalk
spc_hicks09 said:
I don't think you can get OTA's when rooted.
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
I think i know what i did. during the process of rooting, once i acquired root, i was still @ 138 when i was prompted. I realized that the hardware and public zip i hadn't flashed as part of the process, and i grabbed the 183 from some site, and flashed them before the update. so it appears that the os thinks i'm at 138, i maybe @ 183 without the system img... how can i flash 183 manually thru twrp, as it fails when i try.
wrecklesswun said:
I think i know what i did. during the process of rooting, once i acquired root, i was still @ 138 when i was prompted. I realized that the hardware and public zip i hadn't flashed as part of the process, and i grabbed the 183 from some site, and flashed them before the update. so it appears that the os thinks i'm at 138, i maybe @ 183 without the system img... how can i flash 183 manually thru twrp, as it fails when i try.
Click to expand...
Click to collapse
That I have no idea about. Flashing is completely different on this phone compared to what I'm used to. Ever since I used FunkyHuawei to restore mine I haven't even rooted it or anything.
spc_hicks09 said:
That I have no idea about. Flashing is completely different on this phone compared to what I'm used to. Ever since I used FunkyHuawei to restore mine I haven't even rooted it or anything.
Click to expand...
Click to collapse
I also cannot get fastboot to work which makes me suspect something is amiss somewhere... also the e-recovery doesn't work making this worse.
All ya hafta do is Kingoroot it via PC and u done!:good::good::good::good::good:
I'll try it - post your results in this tread people.
---------- Post added at 01:53 AM ---------- Previous post was at 01:20 AM ----------
Zomebodyz said:
All ya hafta do is Kingoroot it via PC and u done!:good::good::good::good::good:
Click to expand...
Click to collapse
Doesn't work - give us information like where you downloaded it from. Are you sure you were not on Fire OS 5.3.1?
I dunno then. I probably am on 5.3.1
This might explain why kingroot has been telling me for nearly a day I have root. I've forced stopped it, cleared cache and data, uninstalled and sometimes it still tells me I have root. However, I haven't connected to the PC to try that way since the new release. BTW no I don't have root...yet.
EDIT: Just tried. No root via PC. Did they do another update in the last 12 or so hours?
See...this is what I have been seeing for pretty much the last 24 hours or so:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No worries though. I am not root yet
tried latest kingroot 5.20 but it doesnt work for me on fire os 5.3.3.0
You guys take the bait way too easily.
Technocian said:
You guys take the bait way too easily.
Click to expand...
Click to collapse
indeed
Technocian said:
You guys take the bait way too easily.
Click to expand...
Click to collapse
Right. Let's just assume everyone is a troll. He very well could've rooted an older version. Maybe not. Everyone here had 4 posts at one point.
DragonFire1024 said:
Right. Let's just assume everyone is a troll. He very well could've rooted an older version. Maybe not. Everyone here had 4 posts at one point.
Click to expand...
Click to collapse
well the topic states he found root for FireOs 5.3.3.0 but he did not deliver any proof, also serveral people tested (me including) and cant confirm. so in this instance its probably safe to say OP is a troll.
l8ixk said:
well the topic states he found root for FireOs 5.3.3.0 but he did not deliver any proof, also serveral people tested (me including) and cant confirm. so in this instance its probably safe to say OP is a troll.
Click to expand...
Click to collapse
Older versions can be rooted via Kingroot.
l8ixk said:
well the topic states he found root for FireOs 5.3.3.0 but he did not deliver any proof, also serveral people tested (me including) and cant confirm. so in this instance its probably safe to say OP is a troll.
Click to expand...
Click to collapse
Really? OP got a little excited and posted what he believed to be a 'win'. A day later he acknowledged the error (kinda). The following sums it up nicely:
DragonFire1024 said:
...Everyone here had 4 posts at one point.
Click to expand...
Click to collapse
Mud slinging serves no purpose; we all make mistakes. Chill.
Davey126 said:
Really? OP got a little excited and posted what he believed to be a 'win'. A day later he acknowledged the error (kinda). The following sums it up nicely:
Mud slinging serves no purpose; we all make mistakes. Chill.
Click to expand...
Click to collapse
well i used the wrong wording by calling op a troll. that was not my intention. although in the end it doesnt really matter if it was intentional or just a mistake by op.
peace
Question...does anyone know what signatures the bootloader accepts on Amazon tablets? I know they are supposed to be official. But what is defined as such...example: Would it accept a signature from Google?
DragonFire1024 said:
Question...does anyone know what signatures the bootloader accepts on Amazon tablets? I know they are supposed to be official. But what is defined as such...example: Would it accept a signature from Google?
Click to expand...
Click to collapse
No. Only from Amazon as far as we know.
savvytechwinner said:
No. Only from Amazon as far as we know.
Click to expand...
Click to collapse
Modify an APK. Run an exploit that way. Trick the CPU into installing an app it still thinks is 'official.' not sure how to gain root that way, but maybe we could modify an APK to be able to reinstall on /sdcard/ so it can uninstall itself. It's not root, but would at least get rid of the apps for a period.
DragonFire1024 said:
Modify an APK. Run an exploit that way. Trick the CPU into installing an app it still thinks is 'official.' not sure how to gain root that way, but maybe we could modify an APK to be able to reinstall on /sdcard/ so it can uninstall itself. It's not root, but would at least get rid of the apps for a period.
Click to expand...
Click to collapse
You can't modify the apk without it modifying Amazon's signature. You can't reinstall system apps either in Fire OS 5.3.3 and above. Although you might be able to for one app, but I am not holding my breath.
savvytechwinner said:
You can't modify the apk without it modifying Amazon's signature. You can't reinstall system apps either in Fire OS 5.3.3 and above. Although you might be able to for one app, but I am not holding my breath.
Click to expand...
Click to collapse
I might have a way, but it isn't pretty. And I learned recently that some think it to be even more unethical than what we are already doing. So I won't post here.
DragonFire1024 said:
I might have a way, but it isn't pretty. And I learned recently that some think it to be even more unethical than what we are already doing. So I won't post here.
Click to expand...
Click to collapse
Sure, what's your way? I might be able to help you out.
If we can read the signature from a stock rom and apply it to SuperSU.zip we could flash it through stock recovery