DRM keys restored !!! - Xperia Z General

i have used many custom roms but atlast i came back to stock rom and when i flashed the stock rom, my DRM keys restored itself. i have to do nothing. happpy!!!!

How do you see your drm is restored?
Send with tapatalk pro

jindal_bharat said:
i have used many custom roms but atlast i came back to stock rom and when i flashed the stock rom, my DRM keys restored itself. i have to do nothing. happpy!!!!
Click to expand...
Click to collapse
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!

If you did not backup your ta partition when u first rooted the keys are gone forever.

androidfreak70 said:
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
Click to expand...
Click to collapse
daniel2728255 said:
If you did not backup your ta partition when u first rooted the keys are gone forever.
Click to expand...
Click to collapse
+2
Kinda useles to open a new thread about that in my case !
Send from my XZ With My Own Personal Modified MoonWalker SuperB !

androidfreak70 said:
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
Click to expand...
Click to collapse
then what r drm keys for ?
as my be2, xloud, trackid, ota updates everything is working .

Check the service menu: dial *#*#7378423#*#* (i.e. *#*#SERVICE#*#*) and choose 'Service tests' > 'Security'. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
DRM keys are unique for each device, so they are not contained in any firmware download. Once they are erased, there is no way to get them back, unless you made a backup of the Trim Area (TA) before unlocking your bootloader.

jindal_bharat said:
then what r drm keys for ?
as my be2, xloud, trackid, ota updates everything is working .
Click to expand...
Click to collapse
DRM keys for warranty only
Those days and other things work when the TA partition restored not DRM keys
Xperia™ Z (C6602) with Tapatalk!

Ok thanks man
Sent from my C6603 using XDA Free mobile app

DRM restored
Mine was also restored.
Tho the mess over here, on a Xperia Z2, was absolutely a little mistake that costed the phone's life: I changed dpi setting under /system/build.prop and couldnt get the phone to startup properly (bootloop). So to get it connected to the PC, the only exit was to unlock the bootloader and flash some 3rd party recovery mode. By doing so I knew I was gonna lose DRM keys, TA Partition was gonna be screwed... anyway, I had to do it. So I got into the OS partitions, I copied (too late) the TA Partition that was still there, and I could make a backup of not much things... the recovery did some backup, I'll check later its contents. Very complicated to explain details of what I did, but after it, to get the phone back working, I downloaded a brand new stock firmware, which also restored my TA Partition and my DRM keys somehow...
I made a test. I used a tool (Backup-TA-9.11) that downloaded from the phone the new TA Partition. And then I compared it to the old one (using same tool), and I saw that the old one was totally f***d up!
I'm also happy I have my DRM Keys back with the TA Partition working!
Good luck people

mandibox said:
Mine was also restored.
Tho the mess over here, on a Xperia Z2, was absolutely a little mistake that costed the phone's life: I changed dpi setting under /system/build.prop and couldnt get the phone to startup properly (bootloop). So to get it connected to the PC, the only exit was to unlock the bootloader and flash some 3rd party recovery mode. By doing so I knew I was gonna lose DRM keys, TA Partition was gonna be screwed... anyway, I had to do it. So I got into the OS partitions, I copied (too late) the TA Partition that was still there, and I could make a backup of not much things... the recovery did some backup, I'll check later its contents. Very complicated to explain details of what I did, but after it, to get the phone back working, I downloaded a brand new stock firmware, which also restored my TA Partition and my DRM keys somehow...
I made a test. I used a tool (Backup-TA-9.11) that downloaded from the phone the new TA Partition. And then I compared it to the old one (using same tool), and I saw that the old one was totally f***d up!
I'm also happy I have my DRM Keys back with the TA Partition working!
Good luck people
Click to expand...
Click to collapse
HOW did you do that? are you sure about that? please check your service test/security if both first three lines are Ok.

xerwudjohn said:
HOW did you do that? are you sure about that? please check your service test/security if both first three lines are Ok.
Click to expand...
Click to collapse
Hello!
Sorry for the late response
I now figured out the DRM Keys are not really restored.
At the time I did not know about them, and lost them by mistake.
But I found another post that kinda helped me getting them back: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672

Apollo89 said:
Check the service menu: dial *#*#7378423#*#* (i.e. *#*#SERVICE#*#*) and choose 'Service tests' > 'Security'. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
DRM keys are unique for each device, so they are not contained in any firmware download. Once they are erased, there is no way to get them back, unless you made a backup of the Trim Area (TA) before unlocking your bootloader.
Click to expand...
Click to collapse
Man I restored them twice and it still gives me the :/
Sent from my C6603 using XDA Free mobile app

One question, is it possible to have your DRM keys intact with a locked bootloader, and be able to access fastboot?
I know for a fact that in Flashtool, it stated that fastboot features were accessible.
So, this whole time I thought that I might have accidentally unlocked my bootloader until I came across this thread.
I remember when I first got the phone, I was unable to access Fastboot mode due to a locked bootloader, but now I am able to.
Code:
20/001/2015 19:01:57 - INFO - Device connected with USB debugging on
20/001/2015 19:01:57 - INFO - Connected device : Sony Xperia Z
20/001/2015 19:01:57 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
20/001/2015 19:01:57 - INFO - Android version : 4.4.2 / kernel version : 3.4.0-perf-g32ce454 / Build number : 10.5.A.0.230
20/001/2015 19:01:57 - INFO - Checking root access
20/001/2015 19:01:58 - INFO - Root Access Allowed
20/002/2015 19:02:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
20/002/2015 19:02:28 - INFO - Device will soon enter fastboot mode
20/002/2015 19:02:28 - INFO - Device disconnected
20/002/2015 19:02:41 - INFO - Device connected in fastboot mode
20/002/2015 19:02:45 - INFO - Device Status: FASTBOOT mode
20/002/2015 19:02:47 - INFO - Fetching fastboot version info from connected device
20/002/2015 19:02:47 - INFO - FASTBOOT version info: [ version: 0.5 ]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-NEVERMIND, just tried flashing XzKernel-26 by alnikki25k, and it didn't boot.

Personally, I can't understand how other people is possible to bring their DRM keys without having TA-Partition. It's all fictive information and I'm totally sure, that no one have restored DRM keys within new ROM installation. And I can bet 100% that it doesn't matter - is it STOCK or CUSTOM ROM. Your DRM Keys aren't going to be restored within new ROM. It's impossible. The only way to get your DRM keys back is to restore your own TA-Partition (flashing any other person's TA-Partition will definitely brick your device), where DRM keys are located at.
Locking your bootloader doesn't restore your DRM keys. All you can do for now is to temporarily get some functions working only with some MODS, which are located somewhere in XDA.

my drm keys are lost after re locking BL. now i want to unlock it again but it fails every time i enter the unlock code.. is this because of lost drm keys? any assistance please?

Related

[GUIDE] Download ANY firmware customization from Sony & create an FTF with Flashtool

[GUIDE] Download ANY firmware customization from Sony & create an FTF with Flashtool
Part A: changing your customization number to download a different firmware customization (optional)
Requirements:
Rooted Xperia smartphone with locked bootloader:
- For firmware versions 10.1.A.1.350 and 10.1.A.1.434, use goroh_kun root exploit
- For firmware versions 10.1.1.A.253, 10.1.1.A.307 and 10.3.A.0.423, use perf_event root exploit and remount-reboot fix
Build Prop Editor
The customization number of the firmware you want to download (see list, only customizations for the same phone model)
Start BuildProp Editor.
When a Superuser request pops up, tap 'Grant' or 'Allow'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At the first start, a backup of 'build.prop' will be created automatically, which can be restored in case of any problems.
Scroll down to 'ro.semc.version.cust' and tap it.
Change the value to the customization number of the firmware you want to download.
When asked to reboot, tap 'No'.
Tap 'ro.semc.version.cus_revision' and change the value to 'R1A'.
When asked to reboot, tap 'Yes'.
Part B: downloading firmware with Sony PC Companion
Requirements:
Sony PC Companion
Xperia smartphone with locked bootloader
Delete this folder if it already exists:
- Windows XP: C:\Documents and Settings\All Users\Application Data\Sony Mobile\Update Engine\db
- Windows Vista/7/8: C:\ProgramData\Sony Mobile\Update Engine\db
Start Sony PC Companion.
Case A: new software version available
Click 'Update'.
Click 'Accept'.
If you only want to download the firmware without updating, disconnect your phone as soon as the "Downloading software..." screen appears.
If you disconnected your phone, this window will appear, which you may close. Otherwise your phone software will be updated.
Case B: no new software version available
Click 'Your Phone / Tablet is up to date'.
Click 'repair my phone / tablet'.
Click 'Next'.
Repairing your phone will delete your personal data and settings. If you don't want this, see step 6. Click 'Continue'.
Tick the checkbox and click 'Next'.
If you only want to download the firmware without repairing, disconnect your phone as soon as the "Downloading software..." screen appears.
If you disconnected your phone, this window will appear, which you may close. Otherwise your phone software will be repaired and your personal data will be lost.
Part C: creating an FTF file with Flashtool
Requirements:
Flashtool
Firmware files from Sony PC Companion or Sony Update Service (see part B).
Start Flashtool or Flashtool64 (for 64-bit Windows).
Click 'Tools' > 'SEUS Decrypt'.
Select the 'Source Folder' (copy-pasting this path will not work):
- Sony PC Companion (Windows XP): C:\Documents and Settings\All Users\Application Data\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony PC Companion (Windows Vista/7/8): C:\ProgramData\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony Update Service (32-bit Windows): C:\Program Files\Sony Mobile\Update Service\db\13740270\blob_fs
- Sony Update Service (64-bit Windows): C:\Program Files (x86)\Sony Mobile\Update Service\db\13740270\blob_fs
Move all 'Available files' to 'Files to convert' by selecting them and clicking the right arrow button.
Click 'Convert'.
Enter the following details:
- Device: your phone model, e.g. 'C6602', 'C6603', 'C6606' or 'C6616' for Xperia Z (see 'Settings' > 'About phone' > 'Model number').
- Branding: can be found in the first columns of these tables by looking up the customization number, e.g. 'Customized US'.
- Version: the build number of the firmware, e.g. '10.1.1.A.1.307'.
Move all files from 'folder list' to 'Firmware content' except *.ta files (e.g. simlock.ta, preset1.ta, cust-reset.ta, ...) by selecting them and clicking the right arrow button.
Click 'Create'.
When you see 'Bundle creation finished', your FTF will be in 'C:\Flashtool\firmwares'. If your combination of device/branding/build is not yet available on xda-developers forum, please be so kind to share it (see part D).
To save about 2 GB of disk space, delete this folder:
- Sony PC Companion (Windows XP): C:\Documents and Settings\All Users\Application Data\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony PC Companion (Windows Vista/7/8): C:\ProgramData\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony Update Service (32-bit Windows): C:\Program Files\Sony Mobile\Update Service\db\13740270\blob_fs
- Sony Update Service (64-bit Windows): C:\Program Files (x86)\Sony Mobile\Update Service\db\13740270\blob_fs
Part D: sharing your FTF on xda-developers forum
Upload your FTF to a file host. I use Dev-Host for this purpose, but it only supports files up to 512 MB, so I use WinRAR to pack my FTF with the following options: 'Compression method' = 'store' (since FTF is already compressed), 'Split to volumes, size' = '512 MB'. Of course you can use a different file host and archiver if required. Please note that Google Drive, Dropbox and Box all have bandwidth quotas, so your shared files may be disabled if they are downloaded too much.
Create a new thread on xda-developers forum in 'Xperia Z General' and include at least the following information:
- Device
- Build number
- Android version
- Customization version
- Region
- Branding
- Download links
Here is an example: [STOCK ROM][FTF] Xperia Z (C6603) 10.1.1.A.1.253 Generic BE (Unbranded/Belgium)
If this post was helpful, don't forget to click the 'Thanks' button.
Is a locked bootloader really necessary for step A?
Coirpre said:
Is a locked bootloader really necessary for step A?
Click to expand...
Click to collapse
Not really for part A, but it is required for part B (because Sony Update Service will only work with a locked bootloader) and part A is useless without part B
However, if your bootloader is unlocked, you can use "Flash tool for Xperia™ devices" (Sony Emma).
Apollo89 said:
Not really for part A, but it is required for part B (because Sony Update Service will only work with a locked bootloader) and part A is useless without part B
However, if your bootloader is unlocked, you can use "Flash tool for Xperia™ devices" (Sony Emma).
Click to expand...
Click to collapse
even after restoring a TA-Backup? sorry, I'm still new to the way sony handles this...
Coirpre said:
even after restoring a TA-Backup? sorry, I'm still new to the way sony handles this...
Click to expand...
Click to collapse
After restoring your TA-Backup (or doing a relock with Flashtool) and flashing a stock ROM, you can use Sony Update Service again.
Apollo89 said:
[*]If you just want to download the firmware without flashing it to your phone: watch the download progress very closely. When the end is near, start holding the USB connector. As soon as the download is completed (see screenshot), IMMEDIATELY DISCONNECT YOUR PHONE. Timing is crucial here. If you disconnect it before downloading is finished, the download will stop. If you disconnect it too late, you might lose data. I used this method several times without losing any data. My experience is that the download progress bar suddenly goes to 100%, before you would expect it, so be prepared!
Click to expand...
Click to collapse
Thank you for your guide.
I just want to add that with "PC companion", I disconnected my phone before the end of the downloading and it didn't stop. I make my own .253 FTF without problem.
Somebody could confirm ?
LedFanatic said:
Thank you for your guide.
I just want to add that with "PC companion", I disconnected my phone before the end of the downloading and it didn't stop. I make my own .253 FTF without problem.
Somebody could confirm ?
Click to expand...
Click to collapse
You're right!
When restoring with PC Companion, you can disconnect your phone during the download.
The downloaded files will be in 'C:\ProgramData\Sony Ericsson\Update Engine\db\13740270\blob_fs'.
The only thing I'm not sure of, is if PC Companion also downloads the full image when updating?
I will download my next update with PC Companion. If the files are the same as with Sony Update Service, then I will update this guide.
Apollo89 said:
You're right!
When restoring with PC Companion, you can disconnect your phone during the download.
The downloaded files will be in 'C:\ProgramData\Sony Ericsson\Update Engine\db\13740270\blob_fs'.
The only thing I'm not sure of, is if PC Companion also downloads the full image when updating?
I will download my next update with PC Companion. If the files are the same as with Sony Update Service, then I will update this guide.
Click to expand...
Click to collapse
What I can tell you is that I made my 253.ftf and 253.zip from an updating PC companion process between .434 to .253. But I didn't compare if the files are the same as with SUS. I use flashtool to flash the ftf and TWRP to recovery flash the zip and didn't have problem...
As soon as the .307 will be available here in France, I will try to reproduce the same process and let you know
Changing build.prop not worked for me
Sony update service downloads same customization version - before change file.(phone restarted after change)
relicks said:
Changing build.prop not worked for me
Sony update service downloads same customization version - before change file.(phone restarted after change)
Click to expand...
Click to collapse
Are you sure you changed the right value? There are multiple entries with your customization number in build.prop, but it's (only) this one you should change: 'ro.semc.version.cust='. After changing this value, save and close build.prop and open it again to check if it has been saved correctly. Also, did you delete the folder 'C:\Program Files (x86)\Sony Mobile\Update Service\db' before starting Sony Update Service?
Apollo89 said:
Are you sure you changed the right value? There are multiple entries with your customization number in build.prop, but it's (only) this one you should change: 'ro.semc.version.cust='. After changing this value, save and close build.prop and open it again to check if it has been saved correctly. Also, did you delete the folder 'C:\Program Files (x86)\Sony Mobile\Update Service\db' before starting Sony Update Service?
Click to expand...
Click to collapse
Yes i am sure. "ro.semc.version.cust" was 1270-7689 (generic UK), and i changed it to 1271-5145 (generic Turkey). And i duble check the value after save it, delete db folder.
relicks said:
Yes i am sure. "ro.semc.version.cust" was 1270-7689 (generic UK), and i changed it to 1271-5145 (generic Turkey). And i duble check the value after save it, delete db folder.
Click to expand...
Click to collapse
That's very strange. I successfully downloaded three other customizations by using this method. A guy who PM'd me was also able to change from 'Generic UK' to 'Vodafone UK' by following this guide. Are you sure SUS was downloading 'Generic UK' again?
Apollo89 said:
That's very strange. I successfully downloaded three other customizations by using this method. A guy who PM'd me was also able to change from 'Generic UK' to 'Vodafone UK' by following this guide. Are you sure SUS was downloading 'Generic UK' again?
Click to expand...
Click to collapse
I think you need to change also the id for ro.product.name=
And ro.semc.version.cus_revision=
That what i did to make it work.
Sent from my C6603 using xda premium
gm007 said:
I think you need to change also the id for ro.product.name=
And ro.semc.version.cus_revision=
That what i did to make it work.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
I didn't have to change those values, but something just came to my mind: I had ro.semc.version.cus_revision=R3A and I downloaded firmwares with R4A, R6A and R11A (all higher).
The guy who changed from 'Generic UK' to 'Vodafone (UK)', changed from R14A to R16A (also higher), but he said he first tried to change to 'Generic ES', which is R5A (lower), and it didn't work.
When I check the latest firmware versions with the URL you can find here (see browser bookmark), I get an empty response if the 'cdfVer=' in the URL is higher than the one of that customization, so I always use cdfVer=R1A there.
This will probably also do the trick here!
@relicks, could you try to change your values to this (without changing anything else):
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R1A
and see if that works? I think it will
Apollo89 said:
I didn't have to change those values, but something just came to my mind: I had ro.semc.version.cus_revision=R3A and I downloaded firmwares with R4A, R6A and R11A (all higher).
The guy who changed from 'Generic UK' to 'Vodafone (UK)', changed from R14A to R16A (also higher), but he said he first tried to change to 'Generic ES', which is R5A (lower), and it didn't work.
When I check the latest firmware versions with the URL you can find here (see browser bookmark), I get an empty response if the 'cdfVer=' in the URL is higher than the one of that customization, so I always use cdfVer=R1A there.
This will probably also do the trick here!
@relicks, could you try to change your values to this (without changing anything else):
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R1A
and see if that works? I think it will
Click to expand...
Click to collapse
nope
It says Your phone has already latest firmware.
relicks said:
nope
It says Your phone has already latest firmware.
Click to expand...
Click to collapse
Does Sony Update Service still offer the option to do a factory reset? I have had this problem where factory reset wasn't even available anymore.
I had to restore the original build.prop from my backup, then I rebooted and SUS gave the factory reset option again.
After that, I modified build.prop again, rebooted and then it worked.
If that still doesn't work, you can try this:
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R7A
Don't forget to do a full reboot each time you change something in build.prop and delete the SUS db folder.
relicks said:
nope
It says Your phone has already latest firmware.
Click to expand...
Click to collapse
Close pc companion and use update service.
Sent from my C6603 using xda premium
Apollo89 said:
Does Sony Update Service still offer the option to do a factory reset? I have had this problem where factory reset wasn't even available anymore.
I had to restore the original build.prop from my backup, then I rebooted and SUS gave the factory reset option again.
After that, I modified build.prop again, rebooted and then it worked.
If that still doesn't work, you can try this:
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R7A
Don't forget to do a full reboot each time you change something in build.prop and delete the SUS db folder.
Click to expand...
Click to collapse
Thanks mate, it is now ok.:good:
But question, it was .434 before after do these things it downloads .253 and i loose root. Is it possible download .434 same customization number for rooting?
relicks said:
Thanks mate, it is now ok.:good:
But question, it was .434 before after do these things it downloads .253 and i loose root. Is it possible download .434 same customization number for rooting?
Click to expand...
Click to collapse
What did the trick? You just tried again with 'R1A'? Or did you use 'R7A'?
No, unfortunately it is not possible to download previous firmware versions from Sony. You can only downgrade if you can find the right FTF file online.
Nice share thanks
Xperia p LT2II
Engima v8.3
sliding xp kernel

[SOLVED] TA PARTITION and FLASHTOOL clarification required

ok so I have a locked bootloader Xperia Z and was in the process of flashing an FTF from here. I have read that an unlocked bootloader would ruin the TA partition containing BA2 / DRM keys. I did not unlock the bootloader but when I flashed using flashtool I am not really sure if I ticked the Exclude (TA) from under the EXCLUDE. Does this mean that I erased the TA partition If anyone of you could be kind enough to tell me....
1. How do I know if BE2 is still working?
2. How do I know if I still have the DRM keys?
Thanks in advance and sorry for my noob question.
Alcatrazx said:
ok so I have a locked bootloader Xperia Z and was in the process of flashing an FTF from here. I have read that an unlocked bootloader would ruin the TA partition containing BA2 / DRM keys. I did not unlock the bootloader but when I flashed using flashtool I am not really sure if I ticked the Exclude (TA) from under the EXCLUDE. Does this mean that I erased the TA partition If anyone of you could be kind enough to tell me....
1. How do I know if BA2 is still working?
2. How do I know if I still have the DRM keys?
Thanks in advance and sorry for my noob question.
Click to expand...
Click to collapse
Flashtool will never erase or overwrite the DRM keys and other important details in your TA partition, even if you don't tick 'TA' under 'Exclude'.
1. When switching BE2 on/off, you will clearly see the difference on pictures in your Album app.
2. Go to your service menu (dial *#*#7378423#*#*) > Service tests > Security. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
Apollo89 said:
Flashtool will never erase or overwrite the DRM keys and other important details in your TA partition, even if you don't tick 'TA' under 'Exclude'.
1. When switching BE2 on/off, you will clearly see the difference on pictures in your Album app.
2. Go to your service menu (dial *#*#7378423#*#*) > Service tests > Security. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
Click to expand...
Click to collapse
Perfect and straight to the point So no need to tick the exclude TA then ?
One last question is there some way of unlocking booloaders which are locked from carriers?
Alcatrazx said:
Perfect and straight to the point So no need to tick the exclude TA then ?
Click to expand...
Click to collapse
Correct!
One last question is there some way of unlocking booloaders which are locked from carriers?
Click to expand...
Click to collapse
No, if you have a bootloader that is not allowed to be unlocked (by carrier), then there is no way to unlock your bootloader sorry.
Apollo89 said:
Flashtool will never erase or overwrite the DRM keys and other important details in your TA partition, even if you don't tick 'TA' under 'Exclude'.
1. When switching BE2 on/off, you will clearly see the difference on pictures in your Album app.
2. Go to your service menu (dial *#*#7378423#*#*) > Service tests > Security. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
Click to expand...
Click to collapse
Nice info
Sent from my C6603 using xda premium

Root, Backup TA, Unlock bootloader and more! The ultimate Xperia Z1 guide

The Ultimate Xperia Z1 Guide​
== Information ==
On this thread I'll post information about Rooting, Backup of TA, Flashtool, recovering from softbrick etc. So this thread is aimed to provide as much usefull info as possible.
== General information about Xperia Z1 ==
You can check all specifications here: Sony Mobile
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Part 1, 2, 3 & 4: Downgrade, Root, backup TA and unlock the bootloader​
== Part 1: Downgrading the Xperia Z1 ==
To be able to root your Xperia Z1 when it has Jellybean 4.3fw or later you need to downgrade it first to be able to use a rooting toolkit, you can succesfully downgrade by downloading this ftf:
- Torrent: 14.1.G.1.534 torrent
- XDA DevDB: 14.1.G.1.534 downgrade FTF
All you need to do to downgrade to a working 14.1.G.1.534 is flashing this ftf in Flashtool. If you don'tknow how to flash an ftf move to the part about FlashTool in this guide
== Part 2: Rooting the Xperia Z1 ==
It seems rooting at the moment will work with a tool called 360rot, you can download it here: 360 root homepage. this tool sadly is in chinese language, I'll try to find out which rooting method it uses ot create an English exploit.
You can also use vroot, I'll discuss this one too
VRoot guide:
- You need to download vroot here: vroot homepage
- Install vroot, I just clicked next, next, next until it finished installation I don't understand Chinese, but I rooted my phone
- Open up vroot and connect your Xperia Z1, you need to get something like this:
- Click the green button to start rooting
- When it finished you're phone will restart and you'll get this:
_ Voila, your phone is now rooted
For now this is the guide I made, thanks to @yeeson for helping me with translating the chinese and giving me screenshots for root 360
- Download and open 360 root
- You'll get a prompt about needing to close the following conflicting service before continuing: adb.exe
- turn on usb-debugging in settings => developer options, and connect your phone
- Open 360 Root again, at this time the upper left corner shows a red font but it isn't to root:
- Click the green button in the bottom right corner, this button is to start rooting your device:
- Progress bar will advance automatically, it can restart a few times, just let it do it's magic!
- When it finished, on top there will be a message: Congratulations, rooting was succesfull:
- To get Root permissions, click the green button in the bottom right corner again now.
- Then the top left corner displays a blue font, this means you are rooted:
== Part 2: Backup TA ==
To backup your TA partition you can use this wonderfull tool created by @DevShaft
You can find it here: [Tool] Backup TA v9.7 for Windows
== Part 3: Unlock your bootloader ==
Unlocking your bootloader means you'll be ablet to flash custom kernels and more roms, like CM, AOKP, PAC and all other source based roms. What you need is a pc with adb acces.
You can download the adb files:
- Windows: Will add these later
- MAC: Will add these later
WARNINGS:
This procedure will wipe the /data partition of your phone, so you will loose all your stored data, settings. SDCARD will BE WIPED!!!
For Xperia™ devices released 2013 or later (for example Xperia™ Z and Xperia™ Z1), the SD card of your device will be formatted and you will lose all content (for example photos, music, videos) when you unlock the boot loader.
Click to expand...
Click to collapse
- DRM keys WILL be lost during this process
Unlocking the bootloader isn't a difficult process, just follow the steps:
- Go to the official sony site for unlocking the bootloader and follow instructions there: Unlock Xperia Bootloader
Part 4: Flashtool​
== Information ==
Flashtool is a tool that allows you to flash FTF files on an Xperia device, this is a powerfull toool when your device is bricked. I'll make this a thread for:
- How to install it?
- How to use Flashtool? (2nd post)
- How to recover a soft bricked device? (3rd post)
== Downloads ==
- Download flashtool for you operating system from the official FlashTool site: Download FlashTool
- Download the XZ1 device folder I created: Xperia Z1 device files Will upload this later
== Installation ==
- Run the installer or unpack the archive for Linux and Mac
- [Optional] Windows uers can go to C:/FlashTool/drivers to have a nice wizard to install fastboot & adb drivers and also drivers for other devices
- Copy the downloaded device file archive to C:/Flashtool/devices
- Open up flashtool, go to "devices => manage => import" and choose the device file you downloaded
- Installation finished!
== Some basics before starting ==
- Entering Flashmode:
* connect your powered off device while holding volume down to pc​- Entering Fastboot (bootloader) mode:
* connect your powered off device while holding volume up to pc​
== Install an FTF file ==
FTF files are the regular Sony firmware files, installing them is quite easy and powerfull to recover a soft bricked/semi-bricked device.
- You need to put your ftf file in C:/Flashtool/firmwares before flashing it
- You can start by clicking on the "Flash" icon, it's the left icon in the icon bar
- You'll get a prompt asking you to go to "Flashmode" or "Fastboot mode", choose Flashmode
- The following screen should look like this:
- Red: Firmware selector to selct the firmware you want to flash
- Blue: this will display the firmware content
- Green: Wipe options, you can choose to wipe certain things here
- Purple: Exclude options, this is to exclude content like kernel or baseband from flashing
- Orange: verification check, you don't need to edit this option
Click to expand...
Click to collapse
- Click the Flash button to flash the FTF
- Wait for the prompt and connect your device in Flashmode
== Use Fastboot toolkit ==
- You can start by clicking on the "Flash" icon, it's the left icon in the icon bar
- You'll get a prompt asking you to go to "Flashmode" or "Fastboot mode", choose "Fastboot" this time
- You'll get the following screen:
The options you'll use most would be:
- Flask kernel
- Flash a system.img file
Click to expand...
Click to collapse
Part 5: recover a soft-bricked device​
Here is my brand new video showing how to root and install the newest recovery on bootloader locked Android 4.4. Xperia Z1
Sorry, but where is Part 3 unlocking the bootloader?
I ordered today the Z1.... hope it will come asap,meanwhile thank you for your guides!
jlevy73 said:
Sorry, but where is Part 3 unlocking the bootloader?
Click to expand...
Click to collapse
I'm not constantly behind my pc, I have a life too I'll add it later today
Sent from my C6603 using xda app-developers app
nice to see development moving along quickly for this device. i have high hopes for it.
thanks for your contributions.
so how did we get a root method already? nice guide, the fact that this is here so early on definitely gives me hope for an awesome dev scene never owned a sony device before
I don't see Xperia Z1 listed http://unlockbootloader.sonymobile.com/supported-devices here.
So does it still mean that bootloader unlock is possible?
wis3m0nkey said:
I don't see Xperia Z1 listed http://unlockbootloader.sonymobile.com/supported-devices here.
So does it still mean that bootloader unlock is possible?
Click to expand...
Click to collapse
not sure but op may have been referring to this?
Can you provide some notes to backing your DRM information before unlocking the bootloader in part 3 of your guide?
wis3m0nkey said:
I don't see Xperia Z1 listed http://unlockbootloader.sonymobile.com/supported-devices here.
So does it still mean that bootloader unlock is possible?
Click to expand...
Click to collapse
Yeah, it's possible
Sent from my C6603 using xda app-developers app
rooted successful with the root tool,and backuped th TA ,Z1 is perfect now
great thx!
Yep, when I was in the Sony store if you put this code into the phone, *#*#7378423#*#*, then Service info > Configuration > Rooting Status. Bootloader unlock allowed said "Yes" so it can be rooted no problem.
Great news.... Thanks guys
Inviato dal mio GT-N7100 con Tapatalk 4
wow
Root
Just to confirm if root using 360 can be performed on locked bootloader?
Thanks for confirmation everyone
Sent from my Nexus 7 using XDA Premium 4 mobile app

[ROM] HUAWEI Ascend W1-U00 | v1.32 | Now available !!

Hi all
I would like to everyone present the first Custom Windows Phone 8 ROM for HUAWEI Ascend W1-U00.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Informations
Windows Phone 8.1 GDR1
Build 14219
Dev unlock
Interop unlock
All capabilities
Changed size partitions :
MainOS - 2,1 GB
Data - 1,5 GB
Additional
Can enable mass storage mode
Searching updates PfD
without dev account and app from market.
Available 51 Langs
ar-SA
az-Latn-AZ
be-BY
bg-BG
ca-ES
cs-CZ
da-DK
de-DE
el-GR
en-GB
en-US
es-ES
es-MX
et-EE
fa-IR
fi-FI
fil-PH
fr-CA
fr-FR
he-IL
hi-IN
hr-HR
hu-HU
id-ID
it-IT
ja-JP
kk-KZ
ko-KR
lt-LT
lv-LV
mk-MK
ms-MY
nb-NO
nl-NL
pl-PL
pt-BR
pt-PT
ro-RO
ru-RU
sk-SK
sl-SI
sq-AL
sr-Latn-CS
sv-SE
th-TH
tr-TR
uk-UA
uz-Latn-UZ
vi-VN
zh-CN
zh-TW
How to flash ?
So... The whole update process will proceed in two steps. The first step is flashing the ROM in which certain features are unlocked (required for flashing custo ROM). Performance of the system, its working, etc have not been changed. The second and last step concerns flashing Custom ROM.
! REMEMBER! Everything you do at your own risk.
Step 1 !
a) Download ROM and Flash tool
b) Run "HWDiagnosticApp (##2846579#) ", turn on "Diag settings" and reset phone.
c) Run Flash Tool , select ROM file / Config XML and click "Scan && Download".
d) Now your phone should reset and start in download mode.
If your phone does not want to start the download mode, use QPST​
e) When phone displays 100%, and the inscription OK. The process of flashing rom is complete. Now you need Reset the phone (press power button on 15 sec or remove battery). Flash tool displays information about the bad file FFU, just ignore it .
Step2 !
Before you begin the process of flashing Custom ROM, make sure that you have a ROM with ability to run the device in mass storage mode. If not, flash it. Also remember that after flashing Custom ROM you need perform the first start (until you see the start menu). If you already have ROM with the ability to run in mass storage mode, you can follow the below instructions.
a) Download latest ROM + WP8CRUU, link at the bottom of the page.
b) Run device in mass storage mode
c) Run WP8CRUU.exe and follow the instructions in the program.
!!Attention!!​​​​If you have Custom ROM , you only need start the phone in Mass Storage mode and flash new Custom ROM with WP8CRUU. You do not have flash everything from scratch !!
How to Enable Mass Storage Mode ?
This is very simply, when you start your phone, press "cam" + "vol -" .
Changelog :
v1.32
- Build 14219
- Corrected some regstry entries
- Rebuild firmware packages
- Solved problem with the updates
Now you can update to W10 !
How to do it? Instruction is given below
You need set this values :
[HKEY_LOCAL_MACHINE\SYSTEM\Platform\DeviceTargetingInfo]
"PhoneManufacturer"="NOKIA"
"PhoneManufacturerModelName"="RM-976_1115"
"PhoneFirmwareRevision"="01061.00066.14235.36003"
"PhoneHardwareVariant"="RM-976"
"PhoneMobileOperatorName"="000-GB"
You can use this REG editor (working without CustomWPSystem app)
Important! You need choose "sign in with different account" in Windows Insider otherwise the program will not search for updates !
v1.10
- Fixed a bug with memory card detection
- Fixed bug with incorrect reading of the battery status
Click here to download v1.32
Click here to download v1.10
Click here to download v1.00
Super Big thanks for donations :
€10,00 EUR
$15,00 USD
$16,00 USD
$33,00 USD
$66,00 USD
If you appreciate my work, click it ​
Good work!
May be you should hide langs under a spoiler.
Trying not to get jealous --- Lumia user here
Great work indeed! When you say "mass storage mode" do you literally mean USB mass storage mode (view the phone's storage as a block device)? That would be... very impressive. I'm guessing you need to reboot the phone to enter such a mode though. Alternatively, if you "just" mean Full FS Access via MTP, that's still very cool.
One thought: did you include the Samsung RPC server (so that tools written for interop-unlocked Samsung phones will work)? If not, it may be difficult to port some apps; not all the relevant parts of the registry are writable even with capability unlock (unless you modified the registry ACLs) and I can't find an arbitrary registry write function in the Huawel WINMDs (although there may be one I just didn't see; I did find a read function).
GoodDayToDie said:
Great work indeed! When you say "mess storage mode" do you literally mean USB mass storage mode (view the phone's storage as a block device)? That would be... very impressive. I'm guessing you need to reboot the phone to enter such a mode though. Alternatively, if you "just" mean Full FS Access via MTP, that's still very cool.
One thought: did you include the Samsung RPC server (so that tools written for interop-unlocked Samsung phones will work)? If not, it may be difficult to port some apps; not all the relevant parts of the registry are writable even with capability unlock (unless you modified the registry ACLs) and I can't find an arbitrary registry write function in the Huawel WINMDs (although there may be one I just didn't see; I did find a read function).
Click to expand...
Click to collapse
I saw read/write dword functions somewhere in Huawei apps.
Finally. This literally might be the only way to upgrade the Tracfone version since straight talk has no plans on releasing a update. Been flashing all the foreign GDR2 Huawei W1 ROMS and all work fine but don't allow me to use 3G. Really hope this project takes off and possibly a work around for users with the Tracfone branded version of the phone.
soft of reker work in your rom?
http://forum.xda-developers.com/showthread.php?t=2685826
reksden said:
soft of reker work in your rom?
http://forum.xda-developers.com/showthread.php?t=2685826
Click to expand...
Click to collapse
You can't talk about copyright.
-W_O_L_F- said:
You can't talk about copyright.
Click to expand...
Click to collapse
I'm writting:
reker written this xap and jailbreak. I don't change original files.
GoodDayToDie said:
When you say "mass storage mode" do you literally mean USB mass storage mode (view the phone's storage as a block device)?
Click to expand...
Click to collapse
Yes ... If you can enter to Mass storage mode you need reboot phone and press appropriate buttons
anonymous007 said:
don't allow me to use 3G
Click to expand...
Click to collapse
In my ROM 3G works fine !
WojtasXda said:
Yes ... If you can enter to Mass storage mode you need reboot phone and press appropriate buttons
In my ROM 3G works fine !
Click to expand...
Click to collapse
you should try to сopy reсovery(huawei w1) in htс 8x (rom)/ if you are familiar with the format nbh
reksden said:
you should try to сopy reсovery(huawei w1) in htс 8x (rom)/ if you are familiar with the format nbh
Click to expand...
Click to collapse
Hmmm , you should stop posting **** like that in threads it doesn't belong !!!!!
HARDWARE HARDWARE HARDWARE isn't the same !!!
read this and read it real carefully.
http://forum.xda-developers.com/showpost.php?p=51233276&postcount=5
and ps , nbh is a container , in that container are another few .nb containers , and they are signed !!!
reksden said:
you should try to сopy reсovery(huawei w1) in htс 8x (rom)/ if you are familiar with the format nbh
Click to expand...
Click to collapse
It didn't work without bricking your phone, because HTC has other hardware and other bootloader!
Please stop posting stuff in development thread if you don't know about development!
I'm sure WojtasXda will find a way to do this on all WP8 devices, BUT WAIT!
please can you give us the link off your rom ?
Update... Info in first post !
WojtasXda said:
Update... Info in first post !
Click to expand...
Click to collapse
This is great!!!
Bt is the a possibility to disable 3 collums?
athloni said:
This is great!!!
Bt is the a possibility to disable 3 collums?
Click to expand...
Click to collapse
Yes, you can disable 3 rows with WPH Tweaks by @jessenic: http://forum.xda-developers.com/showthread.php?t=2486387
Sent from my RM-915_nam_usa_228 using Tapatalk
Can I install WP8.1 with the Developer Preview program after using your ROM?
xdevilium said:
Can I install WP8.1 with the Developer Preview program after using your ROM?
Click to expand...
Click to collapse
Developer Preview only check some Registry Keys then apply a key I don't remember
When you have a Interop Unlocked devices you have Developer Unlock too . So there's no problem with using Dev Preview app.
I think next preview will release in 2nd of April , Yes?
ngame said:
Developer Preview only check some Registry Keys then apply a key I don't remember
When you have a Interop Unlocked devices you have Developer Unlock too . So there's no problem with using Dev Preview app.
I think next preview will release in 2nd of April , Yes?
Click to expand...
Click to collapse
yes
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Where can I find "HWDiagnosticApp"?
Also will this work on Windows 8?

[Guide] How to root SM-J730F without TWRP [Android 7.0.0] [Firmware Included]

Note to users: I am NOT RESPONSIBLE for any damage done to your device. I did this on my phone and it worked just fine. Any damages done to the device is your fault. Please make sure to follow the steps carefully.
This is a guide on how to root the Samsung Galaxy J7 SM-J730F without TWRP. I've included a backup stock firmware in case you soft-brick your device.
BACKUP STOCK FIRMWARE FOR SOFT-BRICKED DEVICES:
In case you have soft-bricked your device by doing this tutorial incorrectly, download the stock firmware HERE and follow this guide to re-flash your phone, HERE. Do not attempt to root your device again unless you know what you're doing this time.
I also recommend completely backing up your device after successful root - click here to find out how.
WARNINGS:
1. You will have to WIPE ALL YOUR DATA in order to complete this tutorial.
2. You are at a very high risk of screwing up your device if you proceed ahead with this tutorial. Please make sure you know what you are doing, and that you have knowledge of re-flashing your phone. I am not responsible.
Requirements:
1. A Samsung Galaxy J7 SM-J730F device;
2. PC;
3. An USB cable;
4. Odin v3.12.7 - Download Here;
5. SuperSU .tar file - Download Here;
6. ADB - Download Here.
Instructions:
1. Download Odin on your PC from the link above, and extract everything from the archive to C:\ODIN (create a new folder);
2. Download the SuperSU .tar file from the link above and place it in your C:\ODIN folder. DON'T extract this archive;
3. Download ADB from the link above and extract the contents of the archive to C:\ADB (create a new folder);
4. Make sure USB Debugging AND OEM Unlock are ENABLED in Settings --> Developer Options on your phone. If you don't know how to activate Developer Options, check this out. After you've enabled these, connect your USB cable from your phone to your PC.
Note: If the phone tells you an access request is being received from your PC's fingerprint, accept it.
6. Open ADB on your computer by going to a Command Prompt, and typing cd C:\ADB;
7. Type adb devices to make sure your phone has been detected by ADB, like so:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. In the Command Prompt, type adb reboot recovery and press enter to reboot your phone into Recovery Mode;
9. Once your phone has booted into Recovery Mode, select the Wipe data/factory reset, and then select Yes when it asks for confirmation:
(Note: THIS STEP IS MANDATORY. If you don't wipe your data, the encryption on your phone will remain and you will be unable to root your phone.)
10. After you've wiped your data, BOOT DIRECTLY INTO DOWNLOAD MODE FROM RECOVERY MODE. You can do this by holding down Volume Down + Home Key + Power Button WHILE STILL IN THE RECOVERY MENU.
Important Note: Ideally, you should still be in the recovery menu after doing a factory reset. Then do the instructions above to enter Download Mode. If you reboot AND THEN go to Download Mode, this method won't work, because your encryption will be put in place again and your phone will become unrootable. Please do the above steps with caution.
11. Hold the buttons down. If you did everything correctly, you should see a screen like this pop up:
12. Press the Volume Up button to proceed to the flashing section. You should see this screen:
13. Now, make sure that the USB cable is still connected to your phone. Open ODIN on your PC, and click on the AP button, then select the SuperSU archive that you downloaded. Make sure that your phone is detected, Odin has to say "Added!!" in the log to the right. If it doesn't say that, re-connect your USB cable to your phone, or switch the USB port on your PC. Then press Start to begin flashing SuperSU and rooting your phone:
14. After Odin has finished flashing your phone, it should say PASS! at the top left of the window, under it's name. Your phone will reboot automatically.
15. Once your phone has rebooted, you should be greeted by the usual setup screen that happens when you factory reset your device. Set up the settings as normal, and install SuperSU from the Play Store HERE once the phone is set up. (This is VERY important.)
16. After you've installed SuperSU, download Titanium Backup from the Play Store, and uninstall the system app "Knox" and everything with "Knox" in their name, and also uninstall "Device Security". They could mess with your boot and spam you with "Unauthorized Action" notification. You don't need them anyway -- once you're rooted, those two don't work anymore.
And that's it!
Your phone should be rooted now! I recommend installing Root Checker to see if you have done everything correctly. It should return this result if so:
Thanks for reading my tutorial! I hope it has helped you root your phone. If you did everything correctly, you should be rooted now. If you have soft-bricked your device and your phone is stuck on the Samsung boot logo, please download the included backup firmware and re-flash your phone, and do not attempt to root your phone again.
Hit the "Thanks!" button if my guide helped you!
Please leave any problems you might have in the comments, and don't be immature. I will not help people with a bad attitude. As I said, if you **** up, it's your problem and I am not responsible. But I will still try to help.
-----------------------------------------------------------------
Recommendations (Optional):
I recommend the following root-only apps to enhance your rooted experience.
1. Titanium Backup - Must-have app for rooted users. Useful in debloating your phone, freezing apps (hiding them from app drawer and disabling them - even system apps), backing up apps and more.
2. FlashFire - Useful for completely backing up your phone, flashing your phone with ZIPs, restoring backups and more.
3. Link2SD - Useful for moving apps to the SD card or to the Internal Storage, and more.
4. Greenify - Greenify working in root mode is the best battery saving app there is. It hibernates the apps that you don't use so that you can get the most out of your battery.
5. ES File Manager PRO - The perfect file manager. It lets you back up your apps, has a root explorer function, can let you see hidden files, lets you create shortcuts to any file on your home screen, and much more. There is a free version too, but I strongly recommend the PRO version.
Note: You guys can leave root-only apps in the replies as well, I didn't include a full list of them, obviously, so you guys can help people finding the apps they need to enhance their newly unlocked root experience.
If you want me to send you a list of safe to uninstall system apps, PM me.
Quick extra tip: To disable the ugly white frames for icons in the TouchWiz Home launcher, go to Settings -> Display -> Icon Frames and choose Icons Only.
------------------
Revisions:
- Added extra step about Knox resulting from the feedback of a user.
- Removed system app section. Seems to be giving people boot issues.
good work:good:
i did it and all was good till rebooting.my phone got stuck in the product logo so i had ton get a new software and root again but i'm afraid of rebooting it again.what should i d plz ?
i think the proplem within the device maintenance & security...it says restart to undo the unauthorised actions!!
MEMA1191 said:
good work:good:
i did it and all was good till rebooting.my phone got stuck in the product logo so i had ton get a new software and root again but i'm afraid of rebooting it again.what should i d plz ?
i think the proplem within the device maintenance & security...it says restart to undo the unauthorised actions!!
Click to expand...
Click to collapse
Root again and check every step carefully.
After you've checked everything was done properly, ONLY UNINSTALL KNOX AND DEVICE SECURITY. Don't attempt to uninstall other system applications other than the ones listed in the list.
That's why you're getting "Unauthorized Action" warning. Because Knox is still in effect, and it's detected that you're using a rooted phone. Therefore it warns you. So uninstall it completely, and everything else with "Knox" in its name.
I'm going to add this to the guide so that this doesn't happen again.
NOTE: Also don't worry, once you have completely re-flashed your phone with default stock firmware, it's not rooted anymore and rebooting is safe. Rebooting while rooted is also perfectly safe, if you can do tutorial steps correctly and don't skip over any steps.
I think this guide should be on this forum : https://forum.xda-developers.com/galaxy-j7-2017, but it had very help me, thank you!
After my second reboot (first done after remove the knox things), I'm stuck ont boot screen... I'm not sure, but I think onedrive can't be remove... I will try again
arwandar said:
I think this guide should be on this forum : https://forum.xda-developers.com/galaxy-j7-2017, but it had very help me, thank you!
After my second reboot (first done after remove the knox things), I'm stuck ont boot screen... I'm not sure, but I think onedrive can't be remove... I will try again
Click to expand...
Click to collapse
Don't try to uninstall system apps. I will remove that whole section - seems to be giving people a lot of trouble.
ScarXL said:
Don't try to uninstall system apps. I will remove that whole section - seems to be giving people a lot of trouble.
Click to expand...
Click to collapse
For me, it's the only useful part of the tutos, as I root the phone with trwp... I am tring to remove all systems apps exept onedrive, which always leads me to have issues after reboot.
For now, I've successfully remove
Duo
Excel
Google Play Musique
Google Play Films & séries
Powerpoint
S Health and services
Samsung notes
Skype
Smart Switch
Talkback
Upday
Word
*knox* + device security
EDIT:
Removed too without problems:
*ant* + radio
internet browser
samsung members
voice recorder
maps
my files
choco truc
foundation
roseeukor
samsung push
ScarXL, can you pm me the list you've removed?
arwandar said:
For me, it's the only useful part of the tutos, as I root the phone with trwp... I am tring to remove all systems apps exept onedrive, which always leads me to have issues after reboot.
For now, I've successfully remove
Duo
Excel
Google Play Musique
Google Play Films & séries
Powerpoint
S Health and services
Samsung notes
Skype
Smart Switch
Talkback
Upday
Word
*knox* + device security
Click to expand...
Click to collapse
Well, don't remove OneDrive then. I have no idea what's causing this issue. I uninstalled all those apps in the list on my phone and it works just fine?
this did not work for me. After rooting the device I am stuck with SAMSUNG boot logo. I think I have android 9 might be the issue.
AP: J730FXXS6CTD1
CP: J730FXXS6CTD1
CSC: J730FOXX6CSK6
Model: SM-J730F/DS

Categories

Resources