Database Develop

[GUIDE] upgrade / root Gingerbread / Froyo, flash custom roms July/05

I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.​
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
​
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update​
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress​
What you need if you want to root your Gingerbread rom:​
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:​
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:​
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x​
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me​
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!​
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!​
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:​
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954​
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:​
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!​
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:​
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy ​
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless ​
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753​
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:​
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"​
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017​
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759

Nice, thanks!

OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.

madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update

TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course

well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)

timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..

If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App

Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?

Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App

nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.

Sorry for newb question... What does S-OFF mean?

Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files

timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough

There is another recovery available from GOAPK with Reboot function that works.

can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery

I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk

With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S

Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully

So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .

Something about TWRP recovery

Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!

luvu4evermore said:
Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!
Click to expand...
Click to collapse
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
If you want to use a custom kernel, you must choose one that works with your rom type and version. For example, ElementalX kernel will only works for Sense or GPE rom (stock or custom). The version of ElementalX required depends on your android version so newer doesn't mean better, you need the right one. Flashing a custom recovery is done using twrp recovery. When installing the custom kernel, you can choose the features you want to be installed so if you don't want a specific feature that the kernel offers, its not a problem. The write-protection is removed by default.
If using the twrp file manger, boot in twrp select "advanced" ---> "file manager"
Then to move a file, select it (tap on it) then it will open another menu. Select "move" then select the location you want to move it to. There is also a chmod menu to edit the files permissions.

alray said:
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
Click to expand...
Click to collapse
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...

luvu4evermore said:
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...
Click to expand...
Click to collapse
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager

alray said:
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager
Click to expand...
Click to collapse
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!

luvu4evermore said:
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!
Click to expand...
Click to collapse
Yep sorry, should have mentioned that, you always have to mount the partition you want to access when using a recovery. Some are mounted by default, but /system isn't.

alray said:
Yep sorry, should have mentioned that, you always have to mount the partition you want to access to when using a recovery.
Click to expand...
Click to collapse
Nah, still thanks a lot,

luvu4evermore said:
Nah, still thanks a lot,
Click to expand...
Click to collapse
you're welcome :good:

Canadian S5 (900W8) 5.1.1 Oficial Update

Koodo Mobile: http://downloadmirror.co/android/tq/G900W8VLU1COI4_G900W8OYA1COI4_KDO.zip
SaskTel: http://downloadmirror.co/android/tr/G900W8VLU1COI4_G900W8OYA1COI4_BWA.zip
Virgin Mobile: http://downloadmirror.co/android/ts/G900W8VLU1COI4_G900W8OYA1COI4_VMC.zip
Bell Mobil: http://downloadmirror.co/android/tt/G900W8VLU1COI4_G900W8OYA1COI4_BMC.zip
Rogers: http://downloadmirror.co/android/tu/G900W8VLU1COI4_G900W8OYA1COI4_RWC.zip
Telus: http://downloadmirror.co/android/tv/G900W8VLU1COI4_G900W8OYA1COI4_TLS.zip
Fido Mobile: http://downloadmirror.co/android/tw/G900W8VLU1COI4_G900W8OYA1COI4_FMC.zip
Source: http://www.theandroidsoul.com/downl...1-update-g900w8vlu1coi4-with-root-info-85381/

Nice, which I've would I download for Wind Mobile?

If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?

Spacemonkie4207 said:
Nice, which I've would I download for Wind Mobile?
Click to expand...
Click to collapse
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.

hexavoodoomal said:
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
Click to expand...
Click to collapse
Where can I find the proper apn settings?

Zehlek said:
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Click to expand...
Click to collapse
use odin in pc

Spacemonkie4207 said:
Where can I find the proper apn settings?
Click to expand...
Click to collapse
Google it.

Whats new ?
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures

brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I have 900M so i cant install, maybe anyone can post anything, but 99% sure didnt have themes
Enviado de meu SM-G900F usando Tapatalk

brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I think it is more under the hood updates
Sent from my SM-G900W8 using Tapatalk

Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.

daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
Only with custom kernel
Enviado de meu SM-G900F usando Tapatalk

Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
☺

daroco said:
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
Click to expand...
Click to collapse
The way I usually root is to flash CF-Auto-Root-kltecan-kltevl-smg900w8.tar using odin. Can you try that?
I haven't updated yet until I'm sure root is there as I gave the phone to my wife.

thanks

Still bootloops when I flashed CF-Autoroot. it also installed the original recovery from another BL version. I reflashed TWRP and cleared cache and dalvik (not that I expected it to do much) but still the same. restored a nandroid and I had all kinds of apps FC. End result was to factory reset the phone to be in a stable condition. If this was a car I could get this damn thing running right! I should have learned more about programming while I was in school...... 2 kids and a mortgage I have no time for it now.

[HOWTO] Root your 5.1.1 G900W8VLU1COI4 firmware
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results. [...]
Click to expand...
Click to collapse
mauriicio21 said:
Only with custom kernel
Click to expand...
Click to collapse
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
-------------------------------------------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rooted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data

_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions/symlinks list from your 5.1.1 firmware. I require it to be well prepared with my custom firmware for G900F. I believe that Android 5.1.1 for G900F is just a matter of a few days.
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Do you Know how can i get spanish on this Vertion plz. ? @_alexndr

_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Hope this helps, thanks for your help.
Here you go!

Just confirmed the camera can shoot in RAW format

HTC One mini 2 shut down while editing .system

I have rooted my phone, root checker said it was fine and supersu works fine.
But I can't edit system files through esFileExplorer (in root mode) and other way (by entering in twrp recovery).
I think it's not done the root, but idk what can I do. Should I root it again?
I wanted for disabling LPA in build.prop.

gregvp00 said:
I have rooted my phone, root checker said it was fine and supersu works fine.
But I can't edit system files through esFileExplorer (in root mode) and other way (by entering in twrp recovery).
I think it's not done the root, but idk what can I do. Should I root it again?
I wanted for disabling LPA in build.prop.
Click to expand...
Click to collapse
Which ROM are you on ?
Have you enabled Root Access>Apps & ADB in Developer Options ?

TryllZ said:
Which ROM are you on ?
Have you enabled Root Access>Apps & ADB in Developer Options ?
Click to expand...
Click to collapse
I had rooted with TWRP and Windroid Universal Android Toolkit.
And Apps & ADB is ~disabled~ (READ BELOW)
-----Update-----
Agh, wrong-
Apps & ADB option is not in my Developer Options,
I confused it with "Verifying Apps via USB" <---- (cause it said that it verify with ADB/ADT)

gregvp00 said:
I had rooted with TWRP and Windroid Universal Android Toolkit.
And Apps & ADB is ~disabled~ (READ BELOW)
-----Update-----
Agh, wrong-
Apps & ADB option is not in my Developer Options,
I confused it with "Verifying Apps via USB" <---- (cause it said that it verify with ADB/ADT)
Click to expand...
Click to collapse
If you are on CM or LOS this option will exists in Developer Options..
Do you have access to Developer Options in your current ROM ?
Which ROM are you on ?

TryllZ said:
If you are on CM or LOS this option will exists in Developer Options..
Do you have access to Developer Options in your current ROM ?
Which ROM are you on ?
Click to expand...
Click to collapse
Nope, I have developer options activated and doesn't exist ~
Stock Android 4.4.2

gregvp00 said:
Nope, I have developer options activated and doesn't exist ~
Stock Android 4.4.2
Click to expand...
Click to collapse
These options only exists in CM & LOS.
As I recall correctly, it's not possible to edit every file despite gaining root access in stock ROM, the work around to this is to copy the file to another location in your phone or into your PC, edit it, then copy the edited file into the phone to a different location, then rename the original file (as backup incase of failure) to anything else, then use TWRP to overwrite or copy the file into system directory using advanced feature, then restart device for changes to take place, if even after restart the changes did not take effect then you will have to use CMD to overwrite the file, the latter should work as I have tested it before.

tryllz said:
These options only exists in CM & LOS.
As I recall correctly, it's not possible to edit every file despite gaining root access in stock ROM, the work around to this is to copy the file to another location in your phone or into your PC, edit it, then copy the edited file into the phone to a different location, then rename the original file (as backup incase of failure) to anything else, then use TWRP to overwrite or copy the file into system directory using advanced feature, then restart device for changes to take place, if even after restart the changes did not take effect then you will have to use CMD to overwrite the file, the latter should work as I have tested it before.
Click to expand...
Click to collapse
https://puu.sh/A5hVB/08fef7d0ef.png
~~~~~~
I did it like you said but I still couldn't overwrite/copy the file into system through TWRP -> Advance
https://puu.sh/A5irV/5959e6aa53.png
By moving I had that error, but by copying it says successful although later I saw that It didn't overwrite anything
-----UPDATE-----
INFO::: ROOT ACCESS/ADB/SELINUX
http://puu.sh/A5joV/e136a8cb87.jpg
http://puu.sh/A5jpe/4cdb3e186c.jpg

..

gregvp00 said:
https://puu.sh/A5hVB/08fef7d0ef.png
~~~~~~
I did it like you said but I still couldn't overwrite/copy the file into system through TWRP -> Advance
https://puu.sh/A5irV/5959e6aa53.png
By moving I had that error, but by copying it says successful although later I saw that It didn't overwrite anything
-----UPDATE-----
INFO::: ROOT ACCESS/ADB/SELINUX
http://puu.sh/A5joV/e136a8cb87.jpg
http://puu.sh/A5jpe/4cdb3e186c.jpg
Click to expand...
Click to collapse
In that case the only option remains is to flash the file through CMD.
This should help https://stackoverflow.com/questions/22166770/permission-to-write-system-etc-on-android-4-3?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
You could also try to apply full permissions to edit to the folder and the file you are trying to access and edit..

[Root][SM-T590] Samsung Galaxy Tab A 10.5 (2018) root tutorial

Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.

Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn

J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology

J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?

stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions

User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)

any solutions, followed steps but no root

I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)

I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.

Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.

IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time

mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too

IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510

mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup

There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all

For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.

kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?

vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked

kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.

kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?