Related
Hi,
I want to root my xperia z1 compact.
As i read, there are few steps that i need to take before rooting my device - backup TA partition, installing CWM, rooting the device.
Both of the CWM/TA backup require that the device will be rooted but if i will root my device without backing up the TA partition i cant go
back and reinstall the stock rom.
What is the correct order of the rooting process?
If the rooting process will get done correctly can i reinstall my stock rom back(for warranty issues)?
What are the downside for rooting - i want it mainly for Titanium backup and the Lba apps?
Thanks for any help!
http://forum.xda-developers.com/showthread.php?t=2642081
http://forum.xda-developers.com/showthread.php?t=2634196
If you follow the guide, you should be able to root without Unlocking Bootloader (Which will cause you loosing TA if you Unlock bootloader first)
So, the best way is to Root (Without unlock bootloader) which is in the guidance, then Backup TA, then you can unlock bootloader if you like (to install ROM or other tweaks).
For myself i just need root so i kept the Bootloader lock and have a backup TA just in case.
thermalboyz said:
http://forum.xda-developers.com/showthread.php?t=2642081
http://forum.xda-developers.com/showthread.php?t=2634196
If you follow the guide, you should be able to root without Unlocking Bootloader (Which will cause you loosing TA if you Unlock bootloader first)
Click to expand...
Click to collapse
If i understood correctly, i will be flashing other rom(previous version in which the root witout unlooking bootloader exploit exsist), to my device.
what will be the effects on my device? will i lose my current device configurations - apps/settings/localization/...? where this change wil be noted?
The process is very complicated and with a lot of "Brick" possibilities, will a more noob friendly version should be expected soon?
Yes you will lose your data as stated in the guides. There isn't really any brick potential, if you screw something up you should always be able to start over again.
As long as there is no other exploit, there won't be an easier method.
cohena said:
If i understood correctly, i will be flashing other rom(previous version in which the root witout unlooking bootloader exploit exsist), to my device.
what will be the effects on my device? will i lose my current device configurations - apps/settings/localization/...? where this change wil be noted?
The process is very complicated and with a lot of "Brick" possibilities, will a more noob friendly version should be expected soon?
Click to expand...
Click to collapse
Hi,
I've rooted my Z1C successfully 2 weeks ago with this guide: http://forum.xda-developers.com/showthread.php?t=2642081
At step 18 you had to do a factory reset... You should always create a backup. But you're are right, this guide could be more noob friendly
I wish there were some screenshots or more detailed explanations, because after I flashed the first file, I only could see a black screen, a white symbol photo of the Z1C with some japanese (?) characters and the phone doesn't do anything... Can't turn off, can't exit this screen... I was shocked until I see a home screen
D_R_Z_87 said:
[..] But you're are right, this guide could be more noob friendly
I wish there were some screenshots or more detailed explanations, because after I flashed the first file, I only could see a black screen, a white symbol photo of the Z1C with some japanese (?) characters and the phone doesn't do anything... Can't turn off, can't exit this screen... I was shocked until I see a home screen
Click to expand...
Click to collapse
If you have some concrete tips I'll be happy to edit the guide
zxz0O0 said:
If you have some concrete tips I'll be happy to edit the guide
Click to expand...
Click to collapse
Hi,
in my situation it would have been helpful to know following things:
- is it ok to rename the downloaded .ftf files from .zip to .ftf ? --> in my case it was ok, because the windows explorer automatically saves the .ftf file as .zip (also .apk files). --> in your guide, post #8, you wrote that this is not ok.
- as i already wrote in my last post, i thougt my phone got bricked after flashing the first file...
- i got stuck at step 13, installing dualrecovery and got the message "Waiting for device to connect" - in my case everything was configured right on my computer, already checked your tips, but it doesn't work until the fifth restart of my phone... maybe you should also suggest a few restarts when the phone would not be recognized
i've rooted several samsung and google nexus devices, but this phone...
but in general, your guide is really good and helped me!
zxz0O0 said:
If you have some concrete tips I'll be happy to edit the guide
Click to expand...
Click to collapse
I will take few days to better understand the process and then i will follow the guide's suggestions, i will post my experience
using the guide after the hopefully successful ending....
Two questions:
how do i do a "factory reset"?
I have no data to lose, so data loss is not an issue for me....
At the hopefully successful ending of the guide which rom do i have?
I want to get back the same device experience i begen the rooting process with....
cohena said:
I will take few days to better understand the process and then i will follow the guide's suggestions, i will post my experience
using the guide after the hopefully successful ending....
Two questions:
how do i do a "factory reset"?
I have no data to lose, so data loss is not an issue for me....
At the hopefully successful ending of the guide which rom do i have?
I want to get back the same device experience i begen the rooting process with....
Click to expand...
Click to collapse
Great :good:
I rooted and unlocked the bootloader right after I bought the phone so data loss was also not a problem for me.
Factory reset is located in Recovery Menu under 'Wipe data/factory reset'.
In the end you will have an unbranded UK firmware with root access. There isn't really any difference.
zxz0O0 said:
In the end you will have an unbranded UK firmware with root access. There isn't really any difference.
Click to expand...
Click to collapse
What do you mean there is no difference?
What are the diffrences between firmwares? what does firmware means- kernal maybe?
I need to understand if having the uk firmware will cahnge my current "device expereince" - gui, localization. preinstalled apps, or it is
just a change to the os itself without any imapct on the current user interface.
cohena said:
What do you mean there is no difference?
What are the diffrences between firmwares? what does firmware means- kernal maybe?
I need to understand if having the uk firmware will cahnge my current "device expereince" - gui, localization. preinstalled apps, or it is
just a change to the os itself without any imapct on the current user interface.
Click to expand...
Click to collapse
Pretty sure there is no difference in the kernel. There might be a difference in the pre-installed apps or modem, I don't know your current rom so I can't answer that. In the end you won't notice any difference.
cohena said:
Hi,
but if i will root my device without backing up the TA partition i cant go back and reinstall the stock rom.
Click to expand...
Click to collapse
Yes you can!
cohena said:
If the rooting process will get done correctly can i reinstall my stock rom back(for warranty issues)?
Click to expand...
Click to collapse
Yes.
cohena said:
What are the downside for rooting
Click to expand...
Click to collapse
NON!
cohena said:
what does firmware means- kernal maybe?
Click to expand...
Click to collapse
Firmware is basically the OS, Gingerbread, Icecream Sandwich, Jellybean, Kitkat, and the main difference between a UK ROM and a Global ROM for example might only be one or two apps at the most.
cohena said:
I need to understand if having the uk firmware will cahnge my current "device expereince" - gui, localization. preinstalled apps, or it is
just a change to the os itself without any imapct on the current user interface.
Click to expand...
Click to collapse
Sony's UI looks the same on an ROM (that is the same Firmware), and if you need to flash a new ROM to root then chances are you will loose whatever you haven't backed up.
zxz0O0 said:
Pretty sure there is no difference in the kernel. There might be a difference in the pre-installed apps or modem, I don't know your current rom so I can't answer that. In the end you won't notice any difference.
Click to expand...
Click to collapse
Thanks for your help so far...
The preinstall apps does not concern me - most of them i will remove anyway...
The modem part sounds problematic....
My build is 14.2.A.1.114, where can i found the rom/modem version data?
cohena said:
Thanks for your help so far...
The preinstall apps does not concern me - most of them i will remove anyway...
The modem part sounds problematic....
My build is 14.2.A.1.114, where can i found the rom/modem version data?
Click to expand...
Click to collapse
You don't need to care about that... Just follow the guide you won't notice anything different.
If you are scared so much you could create a ftf of your stock rom (there are guides on the forum).
zxz0O0 said:
You don't need to care about that... Just follow the guide you won't notice anything different.
If you are scared so much you could create a ftf of your stock rom (there are guides on the forum).
Click to expand...
Click to collapse
Let summerize the procedure so far :
1. I will create a ftf image of my stock rom using the guide that i found, here :
http://forum.xda-developers.com/showthread.php?p=35910775
in the "How to backup your Sony Ericsson Xperia firmware using Update Service and the FlashTool" video.
In that guide the end result is a ftf file and the root guide asks for zip file, how can i get the zip file from the ftf one?
2. I will root my xz1c as the guide suggests here :
http://forum.xda-developers.com/showthread.php?t=2642081
3.ABOUT THAT I AM NOT TOO SURE : on step 19 on sub step 1, i will instal my device ftf instead of the uk one and continue
with the rest of the other 2 sub steps.
Am i correct?
If i am flashing back my device rom or the uk rom at the end of the procedure and both roms are unrooted, how come the device is rooted?
After rooting the device how can i unroot or reroot if needed - i will have to go all the way again?
No.. I meant that you can create a ftf of your stock rom if something would be wrong with the UK one you could flash your old one.
But this won't even happen because the ROMs are almost the same! I don't understand what you are scared about.
There are people from many countries using this UK firmware and no one complained yet.
zxz0O0 said:
No.. I meant that you can create a ftf of your stock rom if something would be wrong with the UK one you could flash your old one.
But this won't even happen because the ROMs are almost the same! I don't understand what you are scared about.
There are people from many countries using this UK firmware and no one complained yet.
Click to expand...
Click to collapse
Ok, so no going back....
After having my device rooted with the uk rom, how cam i localize(keyboard, lang, cell operators, etc....),
the device to my country?
And again with the logical question - if at the end of the process i am flashing an unrooted rom that i flashed at
the beginning of the guide, how can the device be rooted?
I have just been notified that my device is going to get updated to Android ver 4.4.2(KitKat) today/tomrrow, does it changes anything regarding the root procedure?
cohena said:
Ok, so no going back....
After having my device rooted with the uk rom, how cam i localize(keyboard, lang, cell operators, etc....),
the device to my country?
And again with the logical question - if at the end of the process i am flashing an unrooted rom that i flashed at
the beginning of the guide, how can the device be rooted?
Click to expand...
Click to collapse
You just select your language in android, like you normally do
UK firmware does not mean there is only english. There are still all languages available.
In the end you are flashing a zip file (step 19.1), that zip file has root installed.
I am working on updating the guide for KitKat.
zxz0O0 said:
You just select your language in android, like you normally do
UK firmware does not mean there is only english. There are still all languages available.
In the end you are flashing a zip file (step 19.1), that zip file has root installed.
I am working on updating the guide for KitKat.
Click to expand...
Click to collapse
You right!
We need root our lovely Z1c device...
zxz0O0 said:
I am working on updating the guide for KitKat.
Click to expand...
Click to collapse
Ok, so Should i upgrade to kit kat or wait for the root guide?
Hey guys,
Been searching for a few days now ive tried several root methods
the ones from playstore like
Kingroot
Kingoroot
Kingoroot desktop
Its a galaxy tab a6 running android 5.1.1
Build number LMY47V.T280XXU0APB6
All of the above say they can root it but they all failed
I have seen posts on forums such as this one offering custom roms for the device so I must assume there is a root somewhere and I just cant find it.
Any help would be extremely apreceated
ilikenoodles321 said:
Hey guys,
Been searching for a few days now ive tried several root methods
the ones from playstore like
Kingroot
Kingoroot
Kingoroot desktop
Its a galaxy tab a6 running android 5.1.1
Build number LMY47V.T280XXU0APB6
All of the above say they can root it but they all failed
I have seen posts on forums such as this one offering custom roms for the device so I must assume there is a root somewhere and I just cant find it.
Any help would be extremely apreceated
Click to expand...
Click to collapse
Nope, no root for this device until an exploit is found.
Where is this custom rom you speak of?
I don't remember sorry
Is it likely one will be found a exploit I mean ?
ilikenoodles321 said:
I don't remember sorry
Is it likely one will be found a exploit I mean ?
Click to expand...
Click to collapse
I've tried everything possible so far to obtain root.
Hopefully eventually one of the apps like Kingroot will work.
Why the heck Samsung locked the bootloader on this device I have no bloomin idea!
Me either no contactless pay as no cellular so why ?
I got mine direct from Samsung and the bloat is horrific
8gb model and over half of it is unusable and without a root an sd card isent really much help
In essence I have gta sa installed and can't put anything else on its infuriating!
ilikenoodles321 said:
Me either no contactless pay as no cellular so why ?
I got mine direct from Samsung and the bloat is horrific
8gb model and over half of it is unusable and without a root an sd card isent really much help
In essence I have gta sa installed and can't put anything else on its infuriating!
Click to expand...
Click to collapse
It's still possible to customize the stock rom.
I have made some modifications to it and flashed no issues.
This means it can at least be debloated.
How would I do that exactly nothing I have tried has worked
Did you try with kingroot desktop?
mihailrusia said:
Did you try with kingroot desktop?
Click to expand...
Click to collapse
I did indeed.
mihailrusia said:
Did you try with kingroot desktop?
Click to expand...
Click to collapse
Like I said I have already tried all methods.
---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------
ilikenoodles321 said:
How would I do that exactly nothing I have tried has worked
Click to expand...
Click to collapse
Tried what?
Like all the things in android to move data and apps they all greyed out.
Cant u download the stock rom for a device modify it on your computer then flash it to your device ?
IS that a thing?
ilikenoodles321 said:
Cant u download the stock rom for a device modify it on your computer then flash it to your device ?
IS that a thing?
Click to expand...
Click to collapse
That's what I'm referring to. I have modified the stock rom image and reflashed it.
sweet! is there a guide to doing this im confident I can its just ive never done it before.
ilikenoodles321 said:
sweet! is there a guide to doing this im confident I can its just ive never done it before.
Click to expand...
Click to collapse
You're going to need to use Linux, recommend Ubuntu.
ashyx said:
That's what I'm referring to. I have modified the stock rom image and reflashed it.
Click to expand...
Click to collapse
ashyx said:
You're going to need to use Linux, recommend Ubuntu.
Click to expand...
Click to collapse
I've just bought a SN 280 Tab A6 and I've been looking to root it to be able to take off some of the apps I don't use.
Is there any root, twrp or cusmom ROM for this device?
Thanks
---------- Post added at 13:51 ---------- Previous post was at 13:50 ----------
ilikenoodles321 said:
sweet! is there a guide to doing this im confident I can its just ive never done it before.
Click to expand...
Click to collapse
Any news ?
gugas123 said:
I've just bought a SN 280 Tab A6 and I've been looking to root it to be able to take off some of the apps I don't use.
Is there any root, twrp or cusmom ROM for this device?
Thanks
---------- Post added at 13:51 ---------- Previous post was at 13:50 ----------
Any news ?
Click to expand...
Click to collapse
Did you even read this thread? :banghead:
ashyx said:
It's still possible to customize the stock rom.
I have made some modifications to it and flashed no issues.
This means it can at least be debloated.
Click to expand...
Click to collapse
Hello ashyx
I have the sm-T285m. Yes, I could not root it using the usual programs out there. Any way to inject root into the system image and then reflash it through odin? (as you mentioned you have managed to debloat it-maybe a dumb question as am sure you already looked into it) I recall trying to do such a thing on Huawei Mediapad x2 when there was no root but ran into issues after I accidentally overwrote my entire windows o/s and disk with linux and then gave up (had to extract files from image, add the su then recompile something like that?...from memory over a year back and was only my first and only foray into linux) The odin tar files are separate ones for modem, system, bootloader etc.
Thanks
mac231us said:
Hello ashyx
I have the sm-T285m. Yes, I could not root it using the usual programs out there. Any way to inject root into the system image and then reflash it through odin? (as you mentioned you have managed to debloat it-maybe a dumb question as am sure you already looked into it) I recall trying to do such a thing on Huawei Mediapad x2 when there was no root but ran into issues after I accidentally overwrote my entire windows o/s and disk with linux and then gave up (had to extract files from image, add the su then recompile something like that?...from memory over a year back and was only my first and only foray into linux) The odin tar files are separate ones for modem, system, bootloader etc.
Thanks
Click to expand...
Click to collapse
I already tried prerooting the system image.
It wont boot because the boot.img needs to be patched and you can't patch the boot.img on a bootloader locked device.
I even asked Chainfire if there was any other way and he said no.
ashyx said:
I already tried prerooting the system image.
It wont boot because the boot.img needs to be patched and you can't patch the boot.img on a bootloader locked device.
I even asked Chainfire if there was any other way and he said no.
Click to expand...
Click to collapse
Thanks Ashyx...you mentioned you managed to debloat it. I tried ext4unpacker (maybe archaic now though recall it worked on 5.0.2) to separate the system.img into components but could not. I am interested in editing system image
(A) change dpi (increase the lcd density to 380 or so to get things bigger),
(B) change system font (put in a preferred ttf font),
(C) remove many unneeded (for me) google apps from the system folder, and
(D) enable mobile data auto on off for mms via the features.xml or others.xml. Do you think these could be done (you already mentioned the debloat).
typically i managed to get all of the above done if rooted.
Any advice appreciated on how to do this unpacking and repacking.
Thanks
does this help? opensouce kernel?
(again maybe preaching to the choir but thought I'd ask-not knowledgeable here but posting if it helps in getting to a semi-rooted type state somehow)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t285
btw i 'managed' to get oem unlock to show as checked permanently...does that mean the bootloader is unlocked now? (cross flashed through odin the 285 on my 285m the system CP file...and reverted back to 285m-no difference though in network as modem was still 285m as was partition and BL-reflashed the BL as well separately for 285m-after all this shows oem unlock checked-when i got the device new it was unchecked)
edit...from what it appears, it means it CAN be unlocked, yes? but not actually unlocked?
http://forum.xda-developers.com/showpost.php?p=67361863&postcount=9
mac231us said:
Thanks Ashyx...you mentioned you managed to debloat it. I tried ext4unpacker (maybe archaic now though recall it worked on 5.0.2) to separate the system.img into components but could not. I am interested in editing system image
(A) change dpi (increase the lcd density to 380 or so to get things bigger),
(B) change system font (put in a preferred ttf font),
(C) remove many unneeded (for me) google apps from the system folder, and
(D) enable mobile data auto on off for mms via the features.xml or others.xml. Do you think these could be done (you already mentioned the debloat).
typically i managed to get all of the above done if rooted.
Any advice appreciated on how to do this unpacking and repacking.
Thanks
does this help? (again maybe preaching to the choir but thought I'd ask-not knowledgeable here but posting if it helps in getting to a semi-rooted type state somehow)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t285
btw i 'managed' to get oem unlock to show as checked permanently...does that mean the bootloader is unlocked now? (cross flashed through odin the 285 on my 285m the system CP file...and reverted back to 285m-no difference though in network as modem was still 285m as was partition and BL-reflashed the BL as well separately for 285m-after all this shows oem unlock checked-when i got the device new it was unchecked)
edit...from what it appears, it means it CAN be unlocked, yes? but not actually unlocked?
http://forum.xda-developers.com/showpost.php?p=67361863&postcount=9
Click to expand...
Click to collapse
It wont make any difference. Enabling OEM unlock doesn't unlock the bootloader.
You still wont be able to flash unsigned boot or recovery images.
It will only allow you to flash an unsigned system image.
I use Ubuntu to mount and edit Ext4 images.
You can use the windows or Linux version of simg2img to convert the sparse image to raw then mount in Linux
Tbh Samsung need to provide an unlock for this device like they do for the Chinese devices as there is no reason why this device should have a locked bootloader.
Hi,
Is it possible to downgrade to 7.1.2 and have my phone completely stock?
I mean like it was, no rooted or something else..
Now I have the latest oreo version from google.
Thanks
thanasisglt said:
Hi,
Is it possible to downgrade to 7.1.2 and have my phone completely stock?
I mean like it was, no rooted or something else..
Now I have the latest oreo version from google.
Thanks
Click to expand...
Click to collapse
Yes just flash latest 7.1 bullhead image and then relock bootloader and you will have your device like stock but why would you downgrade?!
Yes just flash latest 7.1 bullhead image and then relock bootloader and you will have your device like stock but why would you downgrade?!
Click to expand...
Click to collapse
My device is slower than 7.1.2 and also I don't like the layout.
Is there any guide how to do that?
Thanks
thanasisglt said:
My device is slower than 7.1.2 and also I don't like the layout.
Is there any guide how to do that?
Thanks
Click to expand...
Click to collapse
Sorry to answer hours after but I didn't got any notifications...
So, download,
platform tools : https://developer.android.com/studio/releases/platform-tools
Latest 7.1.2 build : https://dl.google.com/dl/android/aosp/bullhead-n2g48c-factory-45d442a2.zip
Then exctract the content of the 7.1.2 build in the platform tools folder then connect you smartphone to your PC in bootloader mode (vol down + power button).
Finally in the platform tools folder you will find a file named flashall.bat, simply execute it and you are done, your device will be on stock 7.1.2
PS: This guide was done assuming you know how to lock and unlock your bootloader if not...tell me ? (kidding happy to help ? ).
francos21 said:
Sorry to answer hours after but I didn't got any notifications...
So, download,
platform tools : https://developer.android.com/studio/releases/platform-tools
Latest 7.1.2 build : https://dl.google.com/dl/android/aosp/bullhead-n2g48c-factory-45d442a2.zip
Then exctract the content of the 7.1.2 build in the platform tools folder then connect you smartphone to your PC in bootloader mode (vol down + power button).
Finally in the platform tools folder you will find a file named flashall.bat, simply execute it and you are done, your device will be on stock 7.1.2
PS: This guide was done assuming you know how to lock and unlock your bootloader if not...tell me (kidding happy to help ? ).
Click to expand...
Click to collapse
Thanks a lot for the guidance!
Unfortunately, I don't know how to unlock and lock the bootloader. I 've never done this before and always had my device stock. Any advice would be helpful!
Thanks
thanasisglt said:
Any advice would be helpful!
Click to expand...
Click to collapse
Read the instructions.
thanasisglt said:
Thanks a lot for the guidance!
Unfortunately, I don't know how to unlock and lock the bootloader. I 've never done this before and always had my device stock. Any advice would be helpful!
Thanks
Click to expand...
Click to collapse
NOTE : unlocking bootloader will erase all your data!!!
NOTE 2 : If you lock your bootloader without the factory image flashed you will brick your device so no more usable!!!!! So personnaly I don't recommand you to do that because you don't need that to return on Android 7 it's just a "security" for your data.
NOTE 3 : read this guide too because it's more complete and what you are going to do is a bit risky(I speak for locking bootloader) , really! Don't want a message saying "you forgot this line, my device is lost ? ...".
So let's start fun things ?
Go in developer options and enable oem unlock and USB debugging.
Then reboot in bootloader mode and connect your device to your computer.
After that open the prompt command from the extracted platform tools folder by right clicking in this folder with the maj key down.
In this command windows write the following line:
fastboot oem unlock
Or .\fastboot oem unlock if your are on windows 10 (windows is blue instead of black).
When the bootloader is unlocked you can flash a custom recovery then instal a ROM/kernel or flash the factory image.
When you have flashed the factory image (stock ROM...) you can lock the bootloader with this line(same method)
fastboot oem lock (add .\ for windows 10).
Tell me if you need further help ? .
francos21 said:
NOTE : unlocking bootloader will erase all your data!!!
NOTE 2 : If you lock your bootloader without the factory image flashed you will brick your device so no more usable!!!!! So personnaly I don't recommand you to do that because you don't need that to return on Android 7 it's just a "security" for your data.
NOTE 3 : read this guide too because it's more complete and what you are going to do is a bit risky(I speak for locking bootloader) , really! Don't want a message saying "you forgot this line, my device is lost ...".
.
Click to expand...
Click to collapse
Thanks again!
I have to lock the bootloader if I downgrade because bank apps don't work if the device is not stock as far as I know..
other than that I don't mind to be unlocked and playing with custom roms..
thanasisglt said:
Thanks again!
I have to lock the bootloader if I downgrade because bank apps don't work if the device is not stock as far as I know..
other than that I don't mind to be unlocked and playing with custom roms..
Click to expand...
Click to collapse
That's actually not true, at least I think as I don't use bank apps that don't accept that my bank app is accepting root too ?
But seriously, from where did you catch the info?
francos21 said:
That's actually not true, at least I think as I don't use bank apps that don't accept that my bank app is accepting root too
But seriously, from where did you catch the info?
Click to expand...
Click to collapse
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!
thanasisglt said:
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!
Click to expand...
Click to collapse
Android layout can be changed easily and having latest Android security offer security and latest features and performances patchs, anyway it's your decision.
thanasisglt said:
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!
Click to expand...
Click to collapse
Just keep in mind that unlocking the bootloader and flashing the original rom will NOT result in a rooted phone. If you do the this and relock the bootloader, then your phone will be in a totally stock NON ROOTED state. So any concerns that you have regarding root don't apply here.
I am still on 7.1.2 too because of the performance/lag issues in 8.1
... I never upgraded... Is it still really that bad in 8.1 ? Or better with latest patches?
Sent from my [device_name] using XDA-Developers Legacy app
_giwrgos_ said:
Just keep in mind that unlocking the bootloader and flashing the original rom will NOT result in a rooted phone. If you do the this and relock the bootloader, then your phone will be in a totally stock NON ROOTED state. So any concerns that you have regarding root don't apply here.
Click to expand...
Click to collapse
Hi,
my device got bootlooped. Warranty expired 20 days ago and the cost was too high to repair.
So, I followed an online tutorial, flashed my phone and came back to life.
The issue is that the bootloader is unlocked and I cannot use android pay (it says that the device is somehow altered)
Although banking apps work normally.
Is it ok to relock the bootloader?
(what if the device get bootloop again? / is it possible to brick my device? / could I use another way to bypass and activate android pay?)
Thanks
thanasisglt said:
Hi,
my device got bootlooped. Warranty expired 20 days ago and the cost was too high to repair.
So, I followed an online tutorial, flashed my phone and came back to life.
The issue is that the bootloader is unlocked and I cannot use android pay (it says that the device is somehow altered)
Although banking apps work normally.
Is it ok to relock the bootloader?
(what if the device get bootloop again? / is it possible to brick my device? / could I use another way to bypass and activate android pay?)
Thanks
Click to expand...
Click to collapse
Firstly let me tell you that I am assuming that you have flashed an official stock rom, if you didn't then just ignore what I am saying!
I never heard of anyone bricking the device just by locking the bootlader. The worst thing that can happen is to get a bootloop indeed, but if you just unlock the bootloader again then it should be fixed. Bricking the device just by locking the bootloader sounds totally impossible to me at least. I don't know if there is another way to bypass this and activate android pay but even if there is personally I will not have trusted it.
Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further
Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?
Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms
Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.
I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help
bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?
Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?
Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.
Hi --
Old Galaxy Tab Pro 10.1 running kitkat. I am using CF Auto Root to root it via Odin and I get the "pass" in Odin but then it just reboots into the existing OS and Supersu is not on the device. The instructions I have been following say that you should try again but switching off the "auto reboot" in odin. I did that, but it just remains in download mode. The instructions said to take out the battery...which, not really an option for the tablet.
I believe I followed all other instructions: I have the correct CF Auto Root file for my build; I have the drivers from Samsung ...
Any advice is appreciated.
tojotojo said:
Hi --
Old Galaxy Tab Pro 10.1
Click to expand...
Click to collapse
Which one?
tojotojo said:
running kitkat......
Click to expand...
Click to collapse
So you want to keep that?
If not why don't you flash TWRP and Lineage?
bmwdroid said:
Which one?
So you want to keep that?
If not why don't you flash TWRP and Lineage?
Click to expand...
Click to collapse
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
I see.
Imo it's necessary 1st of all to make sure it's on latest stock to have latest bootloader.
Flashing TWRP with Odin is extremly easy.
Here is a post/thread although written for S4 valid for most others as well.
Written a how-to myself as well but the english part is not as up-to-date as the german is.
tojotojo said:
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
Click to expand...
Click to collapse
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
bmwdroid said:
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
Click to expand...
Click to collapse
Great, will give this a shot later today. Appreciate the help!
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options. Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
tojotojo said:
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options.
Click to expand...
Click to collapse
As I said: not on this old device
tojotojo said:
Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
Click to expand...
Click to collapse
Just use Odin to flash latest TWRP,
Reboot to that TWRP,
Wipe everything plus "Format Data"
Flash suiting ROM and test if it works
reboot to TWRP and flash Gapps fitting this ROM version (I prefer Bitgapps ARM)
Be happy
@tojotojo remember that Odin can only flash .tar and .tar.md5 files
TWRP.....img are to flash later in an old TWRP to get a newer one.
you need check off auto-reboot. it still in dload-mode, then press power to reboot and just as you see it starts boot press recovery-mode key combination to enter recovery. if you are slow, tab will load default system without ur root and recovery. i hope this help you.