So I used the guide on Condi's AiO tool to get ICS rooted and everything said it was going fine and root was successful and everything but then I installed it and it was a custom file and everything, it even said "Installing root" and then "Successful" but I am not rooted so what is up with that?
The system update button even still shows up...
ChristianTW said:
So I used the guide on Condi's AiO tool to get ICS rooted and everything said it was going fine and root was successful and everything but then I installed it and it was a custom file and everything, it even said "Installing root" and then "Successful" but I am not rooted so what is up with that?
The system update button even still shows up...
Click to expand...
Click to collapse
Maby you've forgotten to put in your sd card xD. i had the same stupidity re do the steps again, maby that works you could give it a try and if it wont work and you dont want root access anymore just apply the update and wait for the ics update and also wait if devs can root ics, remember you could have a chance that you get a kernel 9 or above with "3.2.1 release 2" and will not be able to gain root anymore.
Mahaco said:
Maby you've forgotten to put in your sd card xD. i had the same stupidity re do the steps again, maby that works you could give it a try and if it wont work and you dont want root access anymore just apply the update and wait for the ics update and also wait if devs can root ics, remember you could have a chance that you get a kernel 9 or above with "3.2.1 release 2" and will not be able to gain root anymore.
Click to expand...
Click to collapse
No, it was definitely on the SD card. It even went through the update and everything. I tried redoing the steps but I no longer have root so they failed. I definitely do want root, but either way I don't have it.
On my 3.2.1 I have kernel revision #1...
ChristianTW said:
No, it was definitely on the SD card. It even went through the update and everything. I tried redoing the steps but I no longer have root so they failed. I definitely do want root, but either way I don't have it.
On my 3.2.1 I have kernel revision #1...
Click to expand...
Click to collapse
I had the same, but there is an easy way to fix it.
It's because you had SuperSU... Didn't you?
sebarkh said:
I had the same, but there is an easy way to fix it.
It's because you had SuperSU... Didn't you?
Click to expand...
Click to collapse
Nope, I did not... I used SuperUser...
So if i get it right your on 3.2.1.r2 now without root?
If you havn't fixed this already there might be a solution for you try this:
1. Connect your tab.
2. Enable usb debugging.
3. Open device manager
4. Disable SONY TABLET S
5. Start Condi's 2.7 AiO Tool
6. Choose option 1 for root.
7. Press enter so your device will reboot.
8. look in device manager list and wait until SONY TABLET S re-appears
9. If it appears then you must enable it again and wait for the AiO tool to finish.
This might work just give it a try!
YF,
Mahaco.
Mahaco said:
So if i get it right your on 3.2.1.r2 now without root?
If you havn't fixed this already there might be a solution for you try this:
1. Connect your tab.
2. Enable usb debugging.
3. Open device manager
4. Disable SONY TABLET S
5. Start Condi's 2.7 AiO Tool
6. Choose option 1 for root.
7. Press enter so your device will reboot.
8. look in device manager list and wait until SONY TABLET S re-appears
9. If it appears then you must enable it again and wait for the AiO tool to finish.
This might work just give it a try!
YF,
Mahaco.
Click to expand...
Click to collapse
Hello,
Thank you for your reply, unfortunately I am actually on ICS without root. It is quite annoying because all of the root files are there but it still says I am not rooted. I can even use the hacked recovery file, unfortunately signature check is not disabled so I can't reinstall the rooted ICS file...
~Christian W.
ChristianTW said:
Hello,
Thank you for your reply, unfortunately I am actually on ICS without root. It is quite annoying because all of the root files are there but it still says I am not rooted. I can even use the hacked recovery file, unfortunately signature check is not disabled so I can't reinstall the rooted ICS file...
~Christian W.
Click to expand...
Click to collapse
Auch, Thats a bummer then its not possible to obtain root acces which you already knew, but that means that the rooting process whas half finished, that it has installed the Super User app but not changed any permissions or values,
too bad you cant see where it went wrong, but i think the devs will find out how to deal with the "Unrootable kernels"
Too bad i didn't helped you at all,
YF
Mahaco.
ChristianTW said:
Hello,
Thank you for your reply, unfortunately I am actually on ICS without root. It is quite annoying because all of the root files are there but it still says I am not rooted. I can even use the hacked recovery file, unfortunately signature check is not disabled so I can't reinstall the rooted ICS file...
~Christian W.
Click to expand...
Click to collapse
There are two scenarios - one - please check /system/bin/ directory - if there is 'tempsu', and /system/xbin/ if there is 'busybox' - if yes, then just let me know.
Second scenario - you've created custom update, then accidentally flashed 'decrypted_update.zip' - without root etc.
br
condi
condi said:
There are two scenarios - one - please check /system/bin/ directory - if there is 'tempsu', and /system/xbin/ if there is 'busybox' - if yes, then just let me know.
Second scenario - you've created custom update, then accidentally flashed 'decrypted_update.zip' - without root etc.
br
condi
Click to expand...
Click to collapse
Unfortunately it is not there, but when I was installing the update it said "Installing Root" and it showed the condi tool logo and everything...
Related
After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
did not have a problem with ryans one touch lag fix that also takes care of root
I'm having the same problem. Also new to this so I'm sure it's going to be something simple. But it's dricing me crazy. I'm sooo close. Anyone with advice it would be much appreciated.
sorry I forgot to say that I have the Epic 4g
aaconteh said:
After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
Click to expand...
Click to collapse
The Superuser app from the market isn't going to give you superuser privileges without the phone being rooted. That's why you are rooting the phone in the first place.
As I've made a habit of experimenting with every ROM known to man I've gotten this down to a routine when it comes to flashing and re-rooting. And a big part of my routine is using TGA_Gunnman's handy One Click ROOT Windows application (also a mac version available in the same thread)...
http://forum.xda-developers.com/showthread.php?t=739300
Just use it and follow the instruction. Biggest thing is to make sure the phone has USB Debugging enabled and that the internal and external SD's are NOT MOUNTED. Just click the ROOT ME button, look in the shell window to see that the update.zip has been pushed successfully, use the vol rocker keys to select REINSTALL PACKAGES, and reboot.
It's never failed for me so far, and I've re-rooted dozens of times now.
Best of luck!
DemDonkies said:
sorry I forgot to say that I have the Epic 4g
Click to expand...
Click to collapse
The root method for the Epic4g is a tad different...and located in another forum...
http://forum.xda-developers.com/showthread.php?t=770388
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
twomoses said:
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
Click to expand...
Click to collapse
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
upndwn4par said:
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Click to expand...
Click to collapse
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
twomoses said:
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
Click to expand...
Click to collapse
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
upndwn4par said:
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
Click to expand...
Click to collapse
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
twomoses said:
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
Click to expand...
Click to collapse
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
I don't know the answer to your question since most users root, unlock, then flash a ROM. If it were me, I would try to root as if it were GB 236.
upndwn4par said:
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
Click to expand...
Click to collapse
That is correct. I ended up having to kill the terminal emulator too. It just sits there with nothing displaying.
I ran root checker, and all I get is the loading circle in the middle that says "Please wait for Root Check to complete. System appears to be running very slow." Nothing else was running slow, so I rebooted my phone again.
I don't know what changed, but now I have root again! Many thanks upndwn4par!
My guess is clearing data in Manage Applications did the trick. Anyway, glad it is working!
Another method for checking if you are rooted properly.
EDIT: nevermind, now I see it's been discussed already. :stupid:
Off topic: I seriously want to borrow your signatures tho!
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
USB Debugging stays on usually because I don't connect my phone to a computer I don't know.
When this started, I was still getting the toast messages saying access granted, but it wasn't actually working. Somewhere along the line of steps it started working again tho.
twomoses said:
Off topic: I seriously want to borrow your signatures tho!
Click to expand...
Click to collapse
Absolutely!
upndwn4par said:
Absolutely!
Click to expand...
Click to collapse
Done!
Solved: This fixed my problem!
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
So, props to you Sabbelknoken! I suddenly lost root again the same way I had before. I came back through this thread to revisit my steps, and I found that my USB Debugging was off. (I think I turned it off so one of my computers would stop asking me for the drivers. Not important.) I turned it on and it immediately began working!
Just wanted to concur...
Thanks to Sabbelknoken!! I had this same problem with my Droid Charge running Tweaked 3.0. Nothing was getting root and everything was hanging on "Gaining root access..." I tried SuperSU, re-installing Titanium Backup, Superuser, SuperSU, Superuser Update Fixer, Root checker, I cleared data, rebooted several times...over and over.
Then sure enough, my dang "USB Debugging" was not checked. Checked it, and now I'm happily rooting again. *whew* Thought I was going to have to re-Odin my ROM. Ick.
Thank again everyone!
su losing root usb debug etc
I too get su issues from time to time. mostly with stock roms when i flash a fruitcake or gingerbread. and recently one of the leak roms. just type d su in terminal emulator an got $ instead of #. I hope that means im properly rooted . I have a couple of one click root apps on my computers just incase i need to reroot. one is superoneclick 2.33 shortfuse and the other is motofail. then i make sure to install busybox and upate the binary. i also have su update fixer, superuser elite, and supersu. as well as rootchecker.
two thing I did not know were that 1. usb debugging is not just for transferring files or connecting to the computer. I used to turn it off sometimes and then wonder why superuser had problems. 2. how to see you are rooted by typing su in terminal.
From what i understand the one click methods are not ideal as they do not always work. but I usually try them first . If they are outated and dont work i end up rooting by command prompt. some times it woul take me cloose to an hour trying different things. never knew it was usb debugging turned off that causes most root failures. Did some reading and realized that if i allow su permission for terminal emulator, then type su again i get#. good to know.
activate USB debugging
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
Thanks for that simple tip. I was having the same problem, the "Allow" dialog didn't appear for any application request and Root Checker was only saying: "Device seems to be running really slow"
I was 2 or 3 days looking for the solution to this problem, because it is my first time rooting and I can't believe something as simple as activating USB debugging is not really explained in the rooting guide I used.
I hope that now Titanium and ROM Toolbox Pro work properly.
Greetings all!
I have been a long time user, first time poster, but have rooted my phone many times with success, however after a mini update today, the rootkit I used last time kind of worked, however most of the root functionality no longer works. I assume im just using an out of date rootkit.
Model: GT-i9300
Android Version: 4.1.2
Baseband: i9300BVELK1
Build: JZO54K.i9300XXELLA
The device does say modified but the apps still function as if it isn't rooted.
I am on Orange France Telecom living in France, using the handset from Orange. Which software download do I need to get the root working correctly please? I have checked alot of the guides but all point to what I assume is an out of date rootkit.
Thank you for your response in advance.
You can try updating the binaries from within the app.
And please don't ask questions in General
Glebun said:
You can try updating the binaries from within the app.
And please don't ask questions in General
Click to expand...
Click to collapse
How do I do that please? I am concerned I will break my phone if I mess too much. Very much a beginner with rooting outside of the guides.
Go to the superuser app and do it there
Glebun said:
Go to the superuser app and do it there
Click to expand...
Click to collapse
I may have been unclear, I don't know what the phrase "updating a binary" means. Thank you for taking an interest in helping though.
Also the version of the root software was Odin 1.64 I think (working from memory as not at home right now).
Bastrion said:
I may have been unclear, I don't know what the phrase "updating a binary" means. Thank you for taking an interest in helping though.
Also the version of the root software was Odin 1.64 I think (working from memory as not at home right now).
Click to expand...
Click to collapse
Does anyone have any advice on how to fix this please? I am sitting at home now and I think I was using 1.85 Odin not 1.64. Why does my device say modified but still won't give me root access to apps etc.
Bastrion said:
Does anyone have any advice on how to fix this please? I am sitting at home now and I think I was using 1.85 Odin not 1.64. Why does my device say modified but still won't give me root access to apps etc.
Click to expand...
Click to collapse
You should root using this its ptobably the best and easiest way
http://forum.xda-developers.com/showthread.php?t=1957273
Download the zip from post 3 extract the MD5 file and flash via odin 1.85 is ok
Ok...
The problem being is that the root hasn't worked. I get through the root, but each time in the past, it does some file verifying where it says "verifying 1 of 145 files" or something similar, and then adds SUser and CWM - It doesn't do this after this root, and the phone, while saying rooted, won't work as a rooted phone. All my unlicensed apps now fail to load.
I really think that the micro update installed via KIES today needs a new rootkit. I tried the above update, and all that did was delete the Super User app too >_<
Thank you for your patience so far. This stuff is very complicated outside of the normal rooting.
Bastrion said:
The problem being is that the root hasn't worked. I get through the root, but each time in the past, it does some file verifying where it says "verifying 1 of 145 files" or something similar, and then adds SUser and CWM - It doesn't do this after this root, and the phone, while saying rooted, won't work as a rooted phone. All my unlicensed apps now fail to load.
I really think that the micro update installed via KIES today needs a new rootkit. I tried the above update, and all that did was delete the Super User app too >_<
Thank you for your patience so far. This stuff is very complicated outside of the normal rooting.
Click to expand...
Click to collapse
If you use CF Auto Root and lose SU just download SU from the market, this one
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&feature=search_result#?t=W251bGwsMSwyLDEsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0.
CF Auto root doesn't contain CWM you need to install that seperately or install TWRP recovery
ag4751 said:
If you use CF Auto Root and lose SU just download SU from the market, this one
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&feature=search_result#?t=W251bGwsMSwyLDEsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0.
CF Auto root doesn't contain CWM you need to install that seperately or install TWRP recovery
Click to expand...
Click to collapse
Ok so made a bit of progress, got the SuperSU on there again, but apps still function as unlicensed. This was all working fine until the update this morning, but at least we are progressing.
Still haven't solved it. Some apps work, some don't. I even tried Lucky Patcher, no joy.
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
stubbadub said:
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
Click to expand...
Click to collapse
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
bjorn96 said:
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
Click to expand...
Click to collapse
I have just run the Easyroot Tool again and this seems to have solved it. :good:
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
My bootloader came unlocked on the phone. I bought the phone when it was released. I rooted and when 4.4.4 firmware was released it initially failed to update OTA. I had to remove the dual recovery. The OTA then worked fine and i still had root. However i could not mount the /system folder as R/W/. I just ran easyroot again and this solved it.
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
NC not working happened to me too. But only in niaboc79's version (and by this I mean the Russian OTA). I also tried the OTA and all was good. But after that I lost my root and tried to restore it (I ran the restore-mount script). This script messed things up. Instead of looking into that, I tried different approaches (niaboc79's / .314+root+script) except check if it was because of the the script .
If you have root now, install the dualrecovery and dirty flash for example shockss pre-rooted .267 and run the script. Stock .267, everything working but pre-rooted. Ow and 4G icon = LTE icon.
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
pec0ra said:
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
Click to expand...
Click to collapse
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
stonegroover said:
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
Click to expand...
Click to collapse
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
pec0ra said:
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
Click to expand...
Click to collapse
I still have 'some root', my Adaway still works but it won't load new/updated hosts, BusyBoxPro won't install, etc. I tried what you did, just ran the two lines of code but it said I didn't have permission when I tried to run the second line. Did you get that error? If you did, how did you get past that?
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