Related
This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.
NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update
UPDATED:
OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
My path.
1) Stock with root mentioned in this dev section
2)restored CW backup
3)used CW to install the update mentioned in this thread.
No problems so far.
After reading this thread again I went to stock and stock kernel. Rooted and gold again.
I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
Thanks!!!
Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this.
tats_06 said:
This is going to be simply a collection of links with important points...
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 1: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 2: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you don't care about root and want to install the OTA update manually >> SCH-I500.DI01 Update
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
Click to expand...
Click to collapse
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
Let me clarify that. If that's the case, I can update the OP.
Restored, updated and Rerooted
All is well. No problems so far.
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
namebrandon said:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
Click to expand...
Click to collapse
Thanks for heads up...first post updated.
Bump.... Back to top till this gets stickied!
wasupwithuman said:
Bump.... Back to top till this gets stickied!
Click to expand...
Click to collapse
Thanks! I just reported it too to request for sticky.
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
azalvarez03 said:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
tats_06 said:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
Click to expand...
Click to collapse
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
Ok...looks like root went thru...working on cwm recovery now.
OK, recovery installed successfully...running a backup right now.
Should I test restoring? Or should I assume I am safe?
Rooting after OTA update.
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
If you have CWM installed, you always have root via adb, which means you can get your root apps working.
If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.
Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.
Thanks in advance
Hi, for the past months, ive been having trouble updating my s3 from 4.3 to whatever thr next update is. I rooted my phone but then unrooted it by super su, i then confirmed it by downloading root checker and it said my phone is not rooted. However, i still had access to xposed installer. I thought xposed installer only worked when rooted. Its weird. Whenever i go to settings and click system update, it undergos the process but then all of a sudden the android guys like dead and it says "error" also my battery life is charging super slow and i think its cause the system update i cant download
Help pleaseeeeee
Thanks!
http://forum.xda-developers.com/gal...ck-updates-t1710613/post27407556#post27407556 follow this guide ,also you need to download triangle away to set your binary count to default . Did you checked if in download mode it says official ?
Username 30 said:
Hi, for the past months, ive been having trouble updating my s3 from 4.3 to whatever thr next update is. I rooted my phone but then unrooted it by super su, i then confirmed it by downloading root checker and it said my phone is not rooted. However, i still had access to xposed installer. I thought xposed installer only worked when rooted. Its weird. Whenever i go to settings and click system update, it undergos the process but then all of a sudden the android guys like dead and it says "error" also my battery life is charging super slow and i think its cause the system update i cant download
Help pleaseeeeee
Thanks!
Click to expand...
Click to collapse
1. re-root it;
2. use triangle away, whatever else to make it official in download mode
3. forget about unrooting. Perform factory reset.
4. flash the resurrection ROM (factory mode ROM), 5 files, with PIt and repartitioning
effect: you;re clean, stock and ready for OTA.
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
It is amazing with most of the searching I have done about this update, VS98026A, on how they say that this is the KitKat 4.4.4 update. When it isn't and we are still at 4.4.2.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
Rooted vs98024a and did OTA to vs98026a and still have Root. Pretty neat we didn't lose Root.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
lukester01 said:
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
Click to expand...
Click to collapse
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
wait for new ioroot?
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
RobertVanHagar said:
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
Click to expand...
Click to collapse
lukester01 said:
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
Click to expand...
Click to collapse
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Stump root worked on LG G2 26A
Stump root worked. It auto used the brute forth method like you said. Thanks.
Finally I can program my bluetooth call button back to use google now voice search instead of LG voice command.
snellc001 said:
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Click to expand...
Click to collapse
I used stump root successfully on my 26A as well.
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
Simply remove the modified mobile hotspot from system/app. That should allow you to take the OTA
Sent From The Trail Of Untold Truths
you will not be able to take any OTA if you add a custom recovery
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
If you add a custom recovery you will not be able to take any OTA updates.
lukester01 said:
If you add a custom recovery you will not be able to take any OTA updates.
Click to expand...
Click to collapse
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Correct, you don't need one. Note however you won't be able to do image (nandroid) backups/restores or flash images. So be very careful with your root privileges ?
Sent from my VS980 4G
custom recovery
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Custom recovery allows you to flash roms, make nandroid backups, and do several other things. But it will make the phone so that you cannot get OTA updates. To apply updates when you have a custom recovery you will have to wait for someone to make the OTA update into a file you can flash.
TWRP
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
MFR73 said:
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
Click to expand...
Click to collapse
I'm not familiar with TWRP commands, but sounds to me like the update tried to install by booting to recovery, but since it was not the stock recovery it could not update. Having a custom recovery in my experience has always made it so you can not take OTA updates. You would use the LG Mobile Support Tool to "upgrade recovery", that will basically restore the stock recovery. You will lose root. But you can update to 26A, and then use Stump root to get root again.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
had that happen
nicknjg88 said:
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
Click to expand...
Click to collapse
Look back a page. I had the same problem. You need to use the LG Mobile Support Tool and upgrade your recovery. Then take the over the air update. Then root again using Stump root.
I got the 0x1111004 error, and then the 0x1117008 error when trying to take the 25B and 26A update. I tried removing all of my framework and changes, but it didn't seem to help. Resorted to full KDZ wipe to 24A, then ioroot before taking the 26A update. It updated just fine and now I'm running the latest. Now to remove all the bloatware and restore my backups...
I'm hoping they don't push out any more OTA anytime soon unless it's L.
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin
Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or other
First step is to root your phone using King Root. This is the only known root to this day for the Mega 2 AT&T version that has the locked bootloader. It also wasn't known until a few days ago. It does not require a computer. Go to your security section in your phone settings and check unknown sources. Download King Root, run it and even without rebooting you will have root within a few minutes.
Here is the link where I found King Root right here on XDA. So I feel good posting the link.
*http://forum.xda-developers.com/fire-phone/general/root-4-6-1-unlocked-gsm-phone-t3104621
In the first post at the end is the attachment. Be sure you use 4.0.0.233 because that's the one that worked for me. I attached the Root King 4.0.0.233 file at the bottom of this post.
It goes on to mention how to replace king root with supersu. I haven't tried to replace king root because it works fine like it is. If someone wants to try it let me know.
Also during my testing I tried to install a zip from my stock bootloader and it wiped my whole phone back to stock. I assume any changes we make to this rom can not be done flashing a zip because of the locked bootloader. After it wiped everything I still had root though. The root application was the only application left on my phone besides the stock bloatware. If you want to remove Root King you need the app so I guess it's good that the app stays unless you uninstall using its own app.
Now we can install Titanium Backup. Run it close it then go back and (pay for if you haven't done it before) get Titanium Backup Pro key that will allow you to freeze apps. So you can freeze all the apps that will try to update your phone.
You can also remove all the bloatware.
After days of trying different apps to get hotspot to work I found this on another forum. Rather then posting a link (to another site) I have made this shortened version from the original and have given credit to Max Lee. If you want the original thread that includes photos of each step then Google search the title I copied below.
This was not originally written for the Mega 2 but it works perfectly on our Mega.
How to Get Free Wifi Tether on Rooted Android! [AT&T, T-Mobile, Sprint, Verizon]
BY MAX LEE · JULY 2, 2014
Step 1. Download Xposed Installer and Xposed XTether APK files.
Download:
Download Xposed Installer APK
*http://repo.xposed.info/module/de.robv.android.xposed.installer
Download Xposed XTether APK
*http://repo.xposed.info/module/com.dym.motoxtether
*Step 2. Install both APK files.* You may have to check “Unknown Sources” ON under Settings->Security.
*Step 3. Once both apps installed, open Xposed Installer app then press “Framework”.
*Step 4. Hit “Install/Update”.* This will install Xposed Framework.* You can also uninstall it later down the road when you don’t need it anymore if you want.
*Step 5. Make sure you hit “Grant” or “Allow” when Superuser request window pops up!
*Step 6. Hit “Cancel” when installation is done.* Do not reboot yet!
*Step 7. Go to “Modules” in Xposed Installer app.
*Step 8. Make sure Moto Tether is checked ON.* This is actually the XTether app.
*Step 9. Once rebooted, try turning on your Wifi Tether Mobile Hotspot.* It should now be working without annoying messages from your carrier!* Congratulations!
My added steps.
* Step 10. To turn on hotspot you need to go to settings and press Tethering and Wifi Hotspot then press Mobil hotspot, finally slide the switch to on.
Go to Play Store and get HotSpot Toggle by Mehdy Bohlool.
This will make a widget you can put on you home screen to make it easy to turn on and off the hotspot without going through all those other steps each time you want to turn it on and off.
Install it then go to your widgets, find the HotSpot Toggle, grab it and drop it onto your home screen.
I am going to reserve this space incase later I need to add something.
what is ur firmware?I have a G750a on baseband G750AUCU3A0FA did not work...............neither any root method
thank you for the post anyway
I'm in the same page as you. I have the same baseband, and it appears that may have "fixed" whatever exploits others have found. I went so far as to fill up my phone with apps so it doesn't have enough room to download the AT&T updates anymore. I cannot stop these automatic updates without root. I've tried several Kingroot versions, including the one from this post. I've tried Towelroot with several different options. I sure wish I could get this thing rooted. The sandboxed SD card kills my emulation.
mine is updated as well and no root option is working at the moment which totally sux
Any1's able to share an ADB dump or the whole 5.1.1 firmware? :highfive:
I updated mine to 5.1.1 in hopes that one of the root methods would start working. Still no go with either Kingroot or Towelroot. I'd give the dump a try, but I don't think we can get an ADB dumb without root can we? If so, I would mind giving it a shot.
No root before modification of kernel itself (my opinion)
I still don't understand why you posted the chinese version of Kingroot...it just doesn't make sense...
joe zack said:
what is ur firmware?I have a G750a on baseband G750AUCU3A0FA did not work...............neither any root method
thank you for the post anyway
Click to expand...
Click to collapse
4.4.4 G750AUCU1ANL1
I am glad I Rooted mine before my phone updated to Android 5.0 I have had the same issue with some gs4 att phones that I didn't get Rooted before they updated to lollipop. I was able to root 2 of these mega 2s by doing it before they updated to lollipop.
nycmon said:
I still don't understand why you posted the chinese version of Kingroot...it just doesn't make sense...
Click to expand...
Click to collapse
Back then when this root was first discovered only Chinese was available.
spottarget said:
mine is updated as well and no root option is working at the moment which totally sux
Click to expand...
Click to collapse
The gs4 that used to be unrootable if it was updated to lollipop, has now been able to root using a newer version of kingroot. Try again to root your att mega 2 on lollipop using one of the latest kingroot. A new bonus now is if you do get root from kingroot you can buy Supersume from the playstore and it will remove kingroot and replace it with supersu automatically. There is a free method to manually replace kingroot with supersu also.
joe zack said:
what is ur firmware?I have a G750a on baseband G750AUCU3A0FA did not work...............neither any root method
thank you for the post anyway
Click to expand...
Click to collapse
I am on build NL1 with android 4.4.4 .
Also have you ever accepted the security policy update?
Well i'm using SAMSUNG GALAXY MEGA 2 SM-G750A used KingRoot V4.8.0 got Temp only Root as Root would be gone via Root Checker after Reboot.
I used Supersu-me-v6.7 as posted above to replace Kinguser, Supersu installed fine including updating binary's but upon reboot I am now in a BOOTLOOP!!!
I Can get into Download Mode and Stock Recovery I have Wiped my CACHE & Tried a Factory Reset But still in a BOOTLOOP!!!
I Guess I am stuck for now with no Stock Odin Rom or Update available as I Am on 5.1.1 Any Help Or Ideas Fella's??
Nucklez said:
I updated mine to 5.1.1 in hopes that one of the root methods would start working. Still no go with either Kingroot or Towelroot. I'd give the dump a try, but I don't think we can get an ADB dumb without root can we? If so, I would mind giving it a shot.
Click to expand...
Click to collapse
Use Flashify Bro.
and upload the whole firmware on any website. .
Must needed bro plz help
bigwilly1976 said:
Well i'm using SAMSUNG GALAXY MEGA 2 SM-G750A used KingRoot V4.8.0 got Temp only Root as Root would be gone via Root Checker after Reboot.
I used Supersu-me-v6.7 as posted above to replace Kinguser, Supersu installed fine including updating binary's but upon reboot I am now in a BOOTLOOP!!!
I Can get into Download Mode and Stock Recovery I have Wiped my CACHE & Tried a Factory Reset But still in a BOOTLOOP!!!
I Guess I am stuck for now with no Stock Odin Rom or Update available as I Am on 5.1.1 Any Help Or Ideas Fella's??
Click to expand...
Click to collapse
Oh man, I did almost the exact same thing. Only difference is that I used a script instead of Supersu-me. I am too stuck in a boot loop, and cannot get Odin, Kies 2.6, Kies 3 or Samsung Smart Switch to work. Every time I get this error on my phone in download mode: "SW REV. CHECK FAIL. DEVICE: 3. BINARY: 1"
This is the script I used to turn my phone into a boot loop:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Anyone that can upload honestly the whole firmware 5.1.1 G750A??.
Please, S3/N2 can run TW 5.1.1 with this system dump.
Thanks in advance.
Have a nice day.
Here guys to anyone who wants it I found a PIT file for the SM-G750A Mega II hope this can help out some way.
Can i get pit file for samsung galaxy mega 2 (SM-G7508Q). I am not finding that file nowhere in internet and my flashing is showing "Get PIT mapping" in odin. plase do help mee
Can i get pit file for samsung galaxy mega 2 (SM-G7508Q). I am not finding that file nowhere in internet and my flashing is showing "Get PIT mapping" in odin. plase do help mee
Click to expand...
Click to collapse
SIMPLE Bro just query GOOGLE SM-G7508Q Pit File Download!!!!!!!!
"It's Not Free So Get The Wallet Out" Good Luck To You.........
Ok for those having issues of bootloop, there are easy ways to fix this.
If you are able to flash via Odin, just flash any firmware version on top of the one you have.
The device will probably boot normally, but will have issues inside OS. This issues should be fixed once you boot in recovery mode and wipe data/factory reset + wipe cache. BACKUP your suff in windows before you do the factory reset, just ignore the bugs in case they happen and backup your sutff viaSamsung Kies3/Smartswitch or normal windows browsing.
After your phone is back to normal, you can update to latest firmware again OTA WIFI, Odin, Kies/Smartswitch, SamFirm etc.