Related
hi ive been looking round how to root my g1 and had no conformation if the UK version g1 are different to root than the US.
can some give me some clarification on how to root them.
thanks in advance
i am a us g1 users so i might be incorrect but i believe that you need to use rc9 or a gold card. if it is rc9, the rest of the method is the same just a different .nbh
porkky said:
hi ive been looking round how to root my g1
Click to expand...
Click to collapse
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480
Afirejar said:
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Hey I’m having some trouble getting to grips with rooting too; there is quite a lot of information (some of it contradictory or at least inconsistent) for someone new like myself to take in. I consider myself pretty tech savvy but my G1 is uninsured and I’m frankly terrified of bricking it as I’ve got a year left on my contract to pay.
Anyway my point being...the guide your pointing to is specifically tailored to US models as are most guides on the net it’s very hard to find anything definitive about rooting the UK models with regard to SPL and Radio, etc. Also, given that this stuff moves soo quickly (which is an amazing testament to the hard work that all the devs and everyone else involved puts in, thank you!) it’s hard to catch up on everything and understand what exactly to do.
One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
seaweeduk said:
One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
Click to expand...
Click to collapse
I'm a little confused with all this too.
I've been to that blog and that seems simple enough.
It should work on this right? -
firmware - 1.5
kernel - 2.6.27 [email protected] #1
Build Number - CRC 1
Now, this means by phone is rooted, (Basically giving me sys admin rather than root user?)
Which in turn means I can install custom ROM images? Is there anything else this allows me to do?
And is all this permement? Or will it go back to the original ROM on the hardware when I hard reboot?
Sorry for all the questions, I got my phone today .
That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.
AdamPI said:
That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.
Click to expand...
Click to collapse
Thanks for the quick reply and I'm not trying to Hijack the thread, (But the OP will probably want to know this too), once I've rooted and installed the new ROM from the boot menu loader thing, how do I go about formatting my SD card to ex2?
I'm looking at this guide - http://forum.xda-developers.com/showthread.php?t=535232
But in this thread - http://forum.xda-developers.com/showthread.php?t=537204 CM himself says not to install APPS2SD. Can you do the format from inside that ROM or does it do it automatically for you?
Yeah cyanogen roms already contain their own method of app2sd, so trying to use another method on top just screws things up.
All you need to do is partition the card, then when you reboot it will see the partition, move your current stuff over and be good to go.
Follow this guide for partitioning from recovery console: http://forum.xda-developers.com/showthread.php?t=534714
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
I have done this and can confirm that this works
Thanks mate!
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.
andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.
Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.
I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post
PM me if you want the process...
xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.
It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?
Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.
Hi !
I would like to warn everybody that the use of the permanent root option of visionary can lead to an unrecoverable brick!
Lately we are facing an increasing number of bricked phones that have been created by an attempt to permanent root the G2 (or Desire Z) using visionary.
While there is still cure for Desire Z phones (even if it is a complicated procedure) there are certain conditions for the G2 where nothing can be done to rescue the phone.
These are the conditions:
- the phone is S-ON and not SuperCID
- the hboot and the recovery are still stock
- the main software version is 1.22
When visionary corrupts the system partition (which it does some times) the phone can not boot anymore. And as there is no original stock rom (PC10IMG.zip) for the G2 that has software version 1.22 or higher the stock rom can not be installed from hboot.
And with the stock recovery there is also no chance to cure the system partition or change the main version in the misc partition.
But even if the brick can be cured for other phones (Desire Z, Desire HD) this is totally unnecessary because the phones can be rooted and freed by methods that do not have any risk at all (even if you do some steps wrong).
The method that I highly recommend to use is the one described on the XDA-wiki at http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD.
This method is constantly maintained and is the most up to date method.
If you really are not able or willing to use adb I would recommend the method described by ianmcquinn in the thread "[GUIDE] Permanent Root with Visionary/gfree (No ADB Required)" at http://forum.xda-developers.com/showthread.php?t=928160
It is less up to date but it uses visionary only to gain temporary root and it uses scripts for the necessary commands so that the risk of bricking the phone by typos in important commands is minimized.
Scotty2 and I (and a lot of other people) tried our best to make the rooting process as easy and risk less as possible and therefore it is very frustrating to see people who bricked their phones by using an unnecessary, outdated and risky method.
Thanks and have fun - Guhl
Update 05/15/2011:
Since football dropped the new gingerbread T-Mobile ROM (see http://forum.xda-developers.com/showthread.php?t=1074391) a G2 bricked by visionary can be cured. (which is a complicated procedure of course)
I think this is/should already stickied however no one seems to read stickies... Thanks for posting the warning again though.
Sent from my HTC Vision using XDA App
On my first G2 I used the visionary method and it messed up after about 2 weeks.
It wouldn't connect to the wireless network.
On my second G2 I used the gfree/rage method and, it has worked just fine.
I'm sure with all the visionary problems people are having, it probably had something to do with mine going bad.
I am waiting on an insurance replacement G2, glad I found this. I rooted mine the very first method that was posted. So does Visionary have a checkbox in the app or something to permanent root? I was using the first release of it.
:edit Just got my G2 from UPS at 1:20, and now at 1:50 I am already flashing CM7 Visionary is great, glad I saw not to do Perm Root attempt though haha
dumb? question
i rooted my g2 a few weeks back, installed the cyanogenmod 7(which seems solid btw) & honestly dont remember the method i used (it took multiple tries over multiple posts/guides/websites) but i recall visionary was involved at some point.
anyhow should i be worried about this thing becoming useless? should i be reinstalling/uninstalling something? are there any precautions i should be taking? is there a way to tell what method i used?
sorry if im cluttering this thread up, i really try not to post if possible(searching usually answers my dumb questions) THANKS! tho
If you're already rooted you should be good. The method that uses VISIONary/Gfree was posted in January, the latest thing that said it could cause any problems was an update on December 23rd, and from what I understand is that you'd have to downgrade a Desire Z... Didn't say anything about a G2. I'm sitting here waiting for UPS then I'll be doing this.
hmm ok, thanks, ill continue to slowly set it up for use than & keep an eye out for additional posts/info on the subject. i sure would hate to doorstop the thing before even using it.
thanks again for the reply
The only issue I've encountered with the way I did was that it says phone number unknown. Quick xda search found you go into Call settings, additional settings, and you can set the phone number in there
Well, I used the Visionary + gfree way to permanent root today, and it went smoothly, on the 1st try, no problems, as of yet. I ran root check and noticed that busybox isn't installed. Is it supposed to be? It was when I was using temp root. Is it ok, to install busybox from the app from the Market?
I got busy box through titanium backup "problems" button
Hi Guhl, I decided to be safe and follow your more highly recommended method to rooting my tmobile g2. This is my first time rooting a phone, the problem is I have a mac... I'm not sure it will work the same way since I don't have a pc... Do you know someway around this? Or some other way I can root my phone on my mac...
Thank you!
one2345shutup said:
Hi Guhl, I decided to be safe and follow your more highly recommended method to rooting my tmobile g2. This is my first time rooting a phone, the problem is I have a mac... I'm not sure it will work the same way since I don't have a pc... Do you know someway around this? Or some other way I can root my phone on my mac...
Click to expand...
Click to collapse
It should be no problem to root your phone on a Mac. The guide to setting up adb in my signature has a section on how to do so on a Mac.
I perm rooted with visionary method the day it came out (I think this was November or October?). Was on cm 6 and now been on cm 7 for a while. No issues at all. Guess I was lucky or people are doing it without being careful.
My friend's G2 seems to be bricked under these conditions. Failed Visionary root. He's counting on me to fix it.
The recovery is stock and it has S-ON. How can I check the version?
Electrodeath0 said:
How can I check the version?
Click to expand...
Click to collapse
You can't.
Just try to install the 1.19 PC10IMG.zip using hboot and you will see. If it installs you'r good if it tells you that you version is to high you are 1.22
Sent from my HTC Vision using XDA App
Whats up everyone?
OK real quick because this has had a little more insight to my situation than what i have been able to find. a guy called me up yesterday and wanted to know if i could root his g2. well apparently.... he attempted to do this on his own and used visionary and messed up his phone. bootscreen heaven. stuck on htc.
Hboot. 0.82.0
radio 26.03.02.26
SHIP S- ON
I have no control over adb.... says device is offline but at least recognized. and shows devid. is this phone a lost cause or can someone toss me a bone without telling me to read this and go here or there?
i have been searching since 5pm yesterday and it is now 1030am.
I have been able to load an update through the stock recovery and it shows that it went well. when it reboots to the screen with the grean circle arrows over the phone, it doesnt seem to take enought time to be loading image or other software. and when its done and reboots, its still stuck on htc screen.
any help would be greatly appreciated and sorry if i cluttered up this thread.
RELEVANCE::::: Visionary
SErooted,
Xperia X10
2.2 Xperia BLISS
2gig data2sd
998mhz
sysctl
2780 Quad
Wish i would have read this 3 hours ago.Tried to perm-root with vision bout 4 months ago and didnt brick, But 3 hours ago tried it again and i semi bricked/bricked it?
This blows i already miss my android .This is definitley a FML post
FMLLLLL!
well new g2x or just a New G2 here i come
I agree with this thread but back then there was only one root tool for the HTC Desire Z or G2 persay. If there is another tool I am unwilling to unroot and reroot again if possible. But I agree that Visionary++ increases the chances of a bricked phone with a percent of about 55%
Rooting a new G2
wrong post, mods please delete
I AM VS4 said:
I agree with this thread but back then there was only one root tool for the HTC Desire Z or G2 persay. If there is another tool I am unwilling to unroot and reroot again if possible. But I agree that Visionary++ increases the chances of a bricked phone with a percent of about 55%
Click to expand...
Click to collapse
If you used Visionary, and it worked, then you don't need to worry about unrooting and rooting again. If there were going to be any problems, it would have happened as you were rooting. If you didn't run gfree, and are not Super-CID, S-Off, then you might want to do that (you still can). But otherwise, you are good to go.
My phone is currently on version 1.19 and I have not had the time to update the phone. But before I do, I just wanted to clarify a couple of things.
First is that at this time turning s-on and applying the OTA update will cause me to lose the ability to go back to S-off unless I send my phone to Jcase again. (Just wanted to make sure this was still the case as it would be the easiest for me.)
Which brings me to my main question. All I have to do to update to the new version is renaming the RUU correctly, put it on my micro sd card making sure that it is formatted to fat32 and reboot the phone. At this point go into TWRP aaaand I’m not sure about the next part. If I was a betting man I would say install, select storage find the RUU and then hit the install image button. Am I correct in this assumption? And I am aware that flashing 2.41 will erase my data and force me out of root but will keep my S-off status.
I know how to fix software issues when things break on computers, but put a phone in my hands and I get extremely nervous that I might brick something. I know it is not having the experience with phones compared to computers and fixing OS issues on a phone is through recovery, but it still scares me a little. Any and all help is greatly appreciated!
WS-99 said:
My phone is currently on version 1.19 and I have not had the time to update the phone. But before I do, I just wanted to clarify a couple of things.
First is that at this time turning s-on and applying the OTA update will cause me to lose the ability to go back to S-off unless I send my phone to Jcase again. (Just wanted to make sure this was still the case as it would be the easiest for me.)
Which brings me to my main question. All I have to do to update to the new version is renaming the RUU correctly, put it on my micro sd card making sure that it is formatted to fat32 and reboot the phone. At this point go into TWRP aaaand I’m not sure about the next part. If I was a betting man I would say install, select storage find the RUU and then hit the install image button. Am I correct in this assumption? And I am aware that flashing 2.41 will erase my data and force me out of root but will keep my S-off status.
I know how to fix software issues when things break on computers, but put a phone in my hands and I get extremely nervous that I might brick something. I know it is not having the experience with phones compared to computers and fixing OS issues on a phone is through recovery, but it still scares me a little. Any and all help is greatly appreciated!
Click to expand...
Click to collapse
Having s-off doesn't prevent you from taking an OTA, so don't bother going back to s-on. Having a modified system (e.g being rooted) or having twrp are things that would block the OTA. And yes, if you're s-on and you update to Nougat, you're screwed.
To answer your question, you got the RUU steps sorta right, just that you don't flash the RUU from twrp, but rather from Download mode. With the correct and properly renamed ruu on the root of your sd card, boot into download mode (hold vol down and power during bootup), and you'll be promoted to begin the procedure.
Tarima said:
Having s-off doesn't prevent you from taking an OTA, so don't bother going back to s-on. Having a modified system (e.g being rooted) or having twrp are things that would block the OTA. And yes, if you're s-on and you update to Nougat, you're screwed.
To answer your question, you got the RUU steps sorta right, just that you don't flash the RUU from twrp, but rather from Download mode. With the correct and properly renamed ruu on the root of your sd card, boot into download mode (hold vol down and power during bootup), and you'll be promoted to begin the procedure.
Click to expand...
Click to collapse
Dang, so close! Thank you for your help! And once again, just so I understand correctly, the 'root' of the sd card is the top level directory, right? And to gain root access back will that require sunshine?
WS-99 said:
Dang, so close! Thank you for your help! And once again, just so I understand correctly, the 'root' of the sd card is the top level directory, right? And to gain root access back will that require sunshine?
Click to expand...
Click to collapse
Yes, root of sd card is top level.
Since you're already s-off (that's the case right? If you're currently not s-off don't update yet!), you won't need sunshine to root. After running the ruu, just flash TWRP, root and be on your merry way.
Also look into making an untouched system backup before you root, which you can restore next time there is an ota available so that you won't need to ruu.
Good luck.
Tarima said:
Yes, root of sd card is top level.
Since you're already s-off (that's the case right? If you're currently not s-off don't update yet!), you won't need sunshine to root. After running the ruu, just flash TWRP, root and be on your merry way.
Also look into making an untouched system backup before you root, which you can restore next time there is an ota available so that you won't need to ruu.
Good luck.
Click to expand...
Click to collapse
Correct, I am already S-off. You guys are the absolute best! Thank you so much for your help!
WS-99 said:
Correct, I am already S-off. You guys are the absolute best! Thank you so much for your help!
Click to expand...
Click to collapse
No worries bud.
Hi, first, I am pretty new to rooting, yet I have done similar things on other devices. Second, here is the info on my android phone:
Samsung galaxy S5 model SM-G900V
Android Version 6.0.1
EMMC: 11xx...
it is a verizon phone so I'm pretty sure the bootloader is locked, and the latest towelroot throws the "this phone isn't currently supported" error on any of the modstrings I use, as well.
I am looking for some more direction on how to root this phone, and would like some help.
TimX24968B said:
Hi, first, I am pretty new to rooting, yet I have done similar things on other devices. Second, here is the info on my android phone:
Samsung galaxy S5 model SM-G900V
Android Version 6.0.1
EMMC: 11xx...
it is a verizon phone so I'm pretty sure the bootloader is locked, and the latest towelroot throws the "this phone isn't currently supported" error on any of the modstrings I use, as well.
I am looking for some more direction on how to root this phone, and would like some help.
Click to expand...
Click to collapse
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
hmm, wondering if any other new verizon android phones will be rootable since I am available for an upgrade
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
I got mine into a 4.4.2 rom and it was successfully rooted w busybox, but I can't install the SU binary or activate safestrap since it seems like I need one to get the other. is there a way around that?
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
Also, I have seen sites claim things like you can root it, such as the one below:
androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
(had to edit out the www. part of the link)
however, they all require doing stuff with odin, and I am still concerned about files being lost.
Trying to get more info on this, I would appreciate any and all help.
TimX24968B said:
Also, I have seen sites claim things like you can root it, such as the one below:
androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
(had to edit out the www. part of the link)
however, they all require doing stuff with odin, and I am still concerned about files being lost.
Trying to get more info on this, I would appreciate any and all help.
Click to expand...
Click to collapse
I find it highly suspicious that this method hasn't been trumpeted here on xda. The broken english doesn't ease my suspicion, either. Personally, I would want to have a disposable phone on hand to try it out, since it hasn't been vetted here first.
Before you do anything, read through the guide linked in my sig to get yourself familiar with the process. If you decide to tackle it, let us know how it turns out.
painiac said:
I find it highly suspicious that this method hasn't been trumpeted here on xda. The broken english doesn't ease my suspicion, either. Personally, I would want to have a disposable phone on hand to try it out, since it hasn't been vetted here first.
Before you do anything, read through the guide linked in my sig to get yourself familiar with the process. If you decide to tackle it, let us know how it turns out.
Click to expand...
Click to collapse
yea I know it seemed suspicious, so I didn't want to try it. However, would you happen to know of any newer androids that can be rooted, particularly verizon ones? I saw the guide but I don't think I can downgrade since I'm on verizon and 6.0.1, and I'm still afraid of losing my data if I do. Thanks for the help.
You can root that phone, there is a guide in the general section: [GUIDE] Root, Bootloader Unlocks, and More!
Look at the cid 11 section. It will erase all of your data though and downgrade you to lolipop. I used that guide on a marshmellow cid 11 Verizon S5 recently and it worked just fine.
Sadly, the bootloader of cid 11 Verizon S5s are still locked. I dont think there is a way yet to root Verizon S5s with cid 11 without losing your data.
Thanks for letting me know! How would I go about backing up my data for this kind of task, in that case? I am pretty sure I do not use verizons cloud services, but i do use their app for messaging.
As long as I can get root access so i can free up some space on my phone and possibly do other stuff in the future as well, it would be great if theres a way to back everything up aside from just copying the whole sd card, particularly things like contacts and text messages in that verizon app. Im fine being on lolipop, and if i can back up my data, i do have my escape method of just ditching this phone and using my upgrade.
Second question: what would be a newer verizon phone that would be rootable on the latest android?
I didn't need the data when I rooted the S5 I had, so I didnt back anything up.
There should be various apps on google play you can use to backup your text messages and contacts. You can manually backup any pictures and other media to a pc or something. I dont think there is much you can do to save your app data without root already. You can probably look up the save loactions of some of your apps and manually backup those.
I dont keep up with phone releases, so I cant reccomend anything.
Sorry I can't be of more help.
Ammalin said:
You can root that phone, there is a guide in the general section: [GUIDE] Root, Bootloader Unlocks, and More!
Look at the cid 11 section. It will erase all of your data though and downgrade you to lolipop. I used that guide on a marshmellow cid 11 Verizon S5 recently and it worked just fine.
Sadly, the bootloader of cid 11 Verizon S5s are still locked. I dont think there is a way yet to root Verizon S5s with cid 11 without losing your data.
Click to expand...
Click to collapse
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
tong6998 said:
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
Click to expand...
Click to collapse
I never said he could have root on marshmellow. Sorry if that was confusing as I never said it exactly. The linked guide says no root on marshmellow in bold near the top. Just wanted to let the OP know he could get root on the phone in some way at least.
To all:
I'm perfectly fine with downgrading. It was just the issue with backing up data which was holding me back there. However, I am still looking into doing this and appreciate the help. I think all I would need now is to know if anyone knows if there is any relatively new verizon phone that could be rooted out of box. Thanks.
If you know little about rooting, I will advice you to read more information about sm-g900v marshmallow root, like rooting with one click rooting software, just try their free trail and see if you can accept. Android Root from RenewAndroid has help me to solve this similar issue before, my device is Samsung S6.
tong6998 said:
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
Click to expand...
Click to collapse
If you compile the Greyhat Root Console for the S5 Device and use a 6.0.1 ROM still exploitable by dirtycow, there is a chance you may be able to adjust the sepolicy on your device enough, or setup supersu manually. I have yet to try this on my MM G900V. But the code is there. It is just down to the device specific commands to run.
People say dirtycow is a tethered/temporal root that only lasts until you reboot the device, but that isn't always the case if you run the right commands in the right order, or have an APP that sets up the temporal root after boot has completed automatically.
Delgoth said:
If you compile the Greyhat Root Console for the S5 Device and use a 6.0.1 ROM still exploitable by dirtycow, there is a chance you may be able to adjust the sepolicy on your device enough, or setup supersu manually. I have yet to try this on my MM G900V. But the code is there. It is just down to the device specific commands to run.
People say dirtycow is a tethered/temporal root that only lasts until you reboot the device, but that isn't always the case if you run the right commands in the right order, or have an APP that sets up the temporal root after boot has completed automatically.
Click to expand...
Click to collapse
My biggest gripe is the native emulated disk-space....I have had LL PB1 rooted on 900V S5 (CID 11) for sometime. But even with de-bloat, tons of lockups, freezing, constantly wiping cache, was hoping a move to MM (with root, hadn't checked in a while hoping bootloader was solved...) would be the savior....
Alas, it seems PB1 rooted is still the way to go as I have an additional "APPS" EXT FORMATTED partition mounted for apps that behave on it...and use APPS2SD and soft-links to keep storage balanced...but it's still a pain...
Now I have that same question, what is panacea?
If I have to get a new phone (pay exorbitant retail price or some "bargain" on ebay) which is the best root-able/boot-load-able or allows for miniSD expansion (hate the finite XXGB storage ever dictates) with space that can all be recognized for Apps+....
Replies bc or otherwise welcome
Col. P.
Adopting MM...
c0lp4nik said:
My biggest gripe is the native emulated disk-space....I have had LL PB1 rooted on 900V S5 (CID 11) for sometime. But even with de-bloat, tons of lockups, freezing, constantly wiping cache, was hoping a move to MM (with root, hadn't checked in a while hoping bootloader was solved...) would be the savior....
Alas, it seems PB1 rooted is still the way to go as I have an additional "APPS" EXT FORMATTED partition mounted for apps that behave on it...and use APPS2SD and soft-links to keep storage balanced...but it's still a pain...
Now I have that same question, what is panacea?
If I have to get a new phone (pay exorbitant retail price or some "bargain" on ebay) which is the best root-able/boot-load-able or allows for miniSD expansion (hate the finite XXGB storage ever dictates) with space that can all be recognized for Apps+....
Replies bc or otherwise welcome
Col. P.
Click to expand...
Click to collapse
I stand corrected... I now see *Storage Adoption* as part of MM, that could be the ticket for me! Obviously it formats the whole SD as EXT format...which is no big deal for me...at that point, since MM is un-rootable....do I take the leap? Will it really improve the S5?
Thanks for listening!
C0l. P.
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
Is it possible to go back to Lollypop version from 6.1
Billy7891 said:
Is it possible to go back to Lollypop version from 6.1
Click to expand...
Click to collapse
Yes
how can you that be done .It is my understanding that downgrades would be blocked. Is there another way?