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
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Chimpdaddy said:
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Click to expand...
Click to collapse
you can try ot yourself,.but i reckon it will give you error while applying update.
Rootk1t said:
you can try ot yourself,.but i reckon it will give you error while applying update.
Click to expand...
Click to collapse
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Chimpdaddy said:
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Click to expand...
Click to collapse
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
bjrmd said:
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
Click to expand...
Click to collapse
I know, so lazy, if I wait long enough 4.4 will come around and that might keep root!
Nobody's read a successful account of this working then? I may as well just try it and see...
Possibly
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed.
I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root.
If you have CWM or TWRP installed then it won't let you update.
adielee said:
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed. I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root. If you have CWM or TWRP installed then it won't let you update.
Click to expand...
Click to collapse
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Cat McGowan said:
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Click to expand...
Click to collapse
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Rootk1t said:
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Click to expand...
Click to collapse
I would also recommend to flash a pre-rooted 4.3 from scratch for performance and less issues, but if you have a lot of apps installed and everything set up the way you want it can be a pain in the a$#.
Also the OP doesn't want to flash. But if he can it means that the OTA won't install because he has a custom recovery.
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2)
It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
adielee said:
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2) It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
Click to expand...
Click to collapse
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Nope
Cat McGowan said:
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Click to expand...
Click to collapse
Well, I tried it, thinking the worse that could happen is that it would abandon the install, but unfortunately it went right through and upgraded to 4.3 and I lost root
I'd put it into OTA survival mode but not into system/apps. I had no xposed or recovery anything, just root.
So there we go. Thanks for the discussion guys, hope this is useful to someone else.
How do I root it in 4.3? Any ideas?
Try this
http://forum.xda-developers.com/showthread.php?t=2703774
Sent from my SGP311 using xda app-developers app
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
I was able to accomplish a Full Root on the latest OTA update on the phone.
Previously I was running Stock 4.4.4 KitKat with SuperSu and had issues with the OTA, since I had removed Apps.
I installed the Stock 4.4.4 ftf to the phone using the flashtool.
Then was successful in receiving the Prompt to update.
After Update, I installed. "Kingroot" for android. just google it. NOT KINGOROOT or any other.
After running kingroot, King User was installed.
In my experience, no other root method will achieve full root. I was not happy with using Kinguser, since i was a Supersu fan. But anytime I successfully removed kinguser, to swap for Supersu, I had lost partial root access, and could not uninstall apps. I could only Freeze.
I also tried Superuser, but only kinguser allowed me to fully uninstall bloatware, and other apps from the phone.
Just thought I would share.
Thanks, Iambedook. Every experience helps. Kingoroot got me into trouble once before in the past.
Can you flash back to 4.4 from 5.1.1?
iambedook said:
I was able to accomplish a Full Root on the latest OTA update on the phone.
Previously I was running Stock 4.4.4 KitKat with SuperSu and had issues with the OTA, since I had removed Apps.
I installed the Stock 4.4.4 ftf to the phone using the flashtool.
Then was successful in receiving the Prompt to update.
After Update, I installed. "Kingroot" for android. just google it. NOT KINGOROOT or any other.
After running kingroot, King User was installed.
In my experience, no other root method will achieve full root. I was not happy with using Kinguser, since i was a Supersu fan. But anytime I successfully removed kinguser, to swap for Supersu, I had lost partial root access, and could not uninstall apps. I could only Freeze.
I also tried Superuser, but only kinguser allowed me to fully uninstall bloatware, and other apps from the phone.
Just thought I would share.
Click to expand...
Click to collapse
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Astoras said:
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Click to expand...
Click to collapse
Yes, you can revert back to 4.4.4 through Flashtool. Doing so though, you will not have Advanced Calling or the refreshing Lollipop UI. Also, unless you do something about it, you will be promptly reminded all the time to update to 5.1.1.
GigaSPX said:
Yes, you can revert back to 4.4.4 through Flashtool. Doing so though, you will not have Advanced Calling or the refreshing Lollipop UI. Also, unless you do something about it, you will be promptly reminded all the time to update to 5.1.1.
Click to expand...
Click to collapse
Giga,
If I use this method to root 5.1.1., can I install dual recovery and Camera 2 and the FM tuner app? I'd also like the updated flashlight you put together but don't see that as a separate install. Should I wait or go ahead with this method for root?
Thanks, Pat
pvcdroid said:
Giga,
If I use this method to root 5.1.1., can I install dual recovery and Camera 2 and the FM tuner app? I'd also like the updated flashlight you put together but don't see that as a separate install. Should I wait or go ahead with this method for root?
Thanks, Pat
Click to expand...
Click to collapse
You may root, but I would advise against anything else. the Z5 Camera is most likely not compatible for our phones on 5.1.1, and neither is the FM Tuner. It's a whole lot I can't touch base on yet.
Astoras said:
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Click to expand...
Click to collapse
I was able to flash back to 4.4.4 after i messed things up, but after going back to 4.4.4 i am struggling to get back to 5.1.1. The updates are not appearing, stating I am at the latest version.
I would also like a confirm if this. Because I'm sitting around and waiting for a rooted 5.1.1 copy for the phone. Im on 5.0.2 right now and all is working good but still waiting. Thanks all.
I'm going to see if I can root after upgrading to 5.1.1, but I have the stock firmware just incase.
Just uploaded a rooted twrp backup with real superuser ++++much more
Tigerhoods said:
Just uploaded a rooted twrp backup with real superuser ++++much more
Click to expand...
Click to collapse
Wow!!! That sounds great, thanks Tiger
thals1992 said:
I'm going to see if I can root after upgrading to 5.1.1, but I have the stock firmware just incase.
Click to expand...
Click to collapse
Just an FYI, after I needed to revert to 4.4.4. I was struggling to receive updates to get back to 5.1.1. I had to use the Flashtool, 3-5 times to get the correct update prompts to appear. If anyone else had similar issues when reverting back, let me know, but re flashing repeatedly worked for me.
Tigerhoods said:
Just uploaded a rooted twrp backup with real superuser ++++much more
Click to expand...
Click to collapse
Wow,
Download url please
immtu said:
Wow,
Download url please
Click to expand...
Click to collapse
Just scroll down to the z3v dev section.
I was actually able to flash the stock ftf coming 5.0.2. I had to flash it with default options the first time with it failing. I then found that I have to basically flash noting to clear the error on the phone by checking everything in exclude and the other exclude box where it shows its not displaying any files in the middle of the window.
Once that went through, I was able to upgrade from stock to .44 and then the the two updates for 5.1.1. After all that I reset to factory again to test on rooting the phone. I was too, able to obtain root with King Root. I was able to install zxrecovery and xposed with no problems. I'm actually used to King Root as I had to use it on the Verizon branded 7" tablet that didn't have any other possible methods previously. I also found that Busybox was slightly out of date (difference of 2.0) and installed to /sbin which wasn't too big of an issue.
Beyond that my phone seems to get pretty warm and typically complains about not charging even on a 2 Amp charger.
Can you tell me how you avhieved root because i want it but i can't revert to kitkat for some reason (flashtool won't recognise the update file) and I'm on lollipop. I've tried kingroot(app version) and it didn't work,tried reverting didn't work and tried all the framaroot,towelroot and such apps but none worked. I want working root,xposed and twrp. I can't find any way to do it please help.
Zandermc3 said:
Can you tell me how you avhieved root because i want it but i can't revert to kitkat for some reason (flashtool won't recognise the update file) and I'm on lollipop. I've tried kingroot(app version) and it didn't work,tried reverting didn't work and tried all the framaroot,towelroot and such apps but none worked. I want working root,xposed and twrp. I can't find any way to do it please help.
Click to expand...
Click to collapse
Try King root again. I used their apk on the phone. It rebooted once at 30%, but when I got back in the app after the reboot, it successfully rooted the device.
thals1992 said:
Try King root again. I used their apk on the phone. It rebooted once at 30%, but when I got back in the app after the reboot, it successfully rooted the device.
Click to expand...
Click to collapse
Well when i tried i did it 3 times and it failed,never rebooted. I have z3 international or 6603 i think
Zandermc3 said:
Well when i tried i did it 3 times and it failed,never rebooted. I have z3 international or 6603 i think
Click to expand...
Click to collapse
Thats why then. This is only for the Z3v the Verizon variant.
Hi there,
New to the forum. After several hours of reading and searching, I became bewildered enough to decide to register and post .
This thread looked promising. I'm currently on rooted 4.4.4 with this phone. I also have a custom recovery installed. Im trying to get to 5.1.1. As of right now, I assume my only option is to wait for a 5.1.1 ftf so that I can update, because the OTA updates won't work (phone reboots into the custom recovery and the update is interrupted).
Is there an easier way to get the OTA? Or am I stuck waiting for an ftf?
To be clear, my goal is to be on 5.1.1 with root. But at this point I don't think I can get to 5.1.1 at all.