Database Info

Root Kitkat/Lollipop KNOX 0X0

​I searched but couldn't find a proper guide to do what the title says..
Whatever is mentioned in pieces here and there aren't detailed enough for a starter..
Thanks to
@geohot for TowelRoot
@Chainfire for Mobile Odin Lite/Pro and SuperSU
@joeykrim for Root Checker
@Wrathlon for the pit file (I registered on XDA just to Thank him - he helped me overcome Boot Loop with that pit file when I installed the 1st Poland Kitkat firmware) :highfive:
Please let me know if I am missing crediting someone else.. :angel:
TowelRoot won't function on recent Kitkat firmwares because geohot has been hired by Google and therefore, the loophole was fixed (t​​his is what I've read on XDA-not very sure about it though it makes sense)..
Mobile Odin Lite/Pro won't function on latest Kitkat firmwares & any of the Lollipop firmwares.
Now, moving on..
I own the 32 GB International variant of Samsung Galaxy Note (from UK), Model : SM-N9005 to be precise, I am not sure if this works on other models of Note 3 or not
I am gonna mention here the steps that I followed, in a manner as precise as I can enlist..
I'll also gonna try to do so in a manner that's as elaborate as I can make it.. Therefore, some steps might seem obvious and/or extra
If you still find yourself in any doubt-do let me know..
Strong Personal Advice -
Please read the steps twice before you actually start following them
Because these are all Official Firmwares that we're gonna be using, you don't need to turn on ADB (Android Debugging) in Developer Options.
Requirements
Install latest Samsung USB Driver for Mobile Phones (current latest can be downloaded from here).
Download and extract N9005XXUEND3_BTU
Download and extract N9005XXUGNG1_BTU
(only if you want to your device to be finally on Lollipop), download and extract N9005XEOGBOA4_XEO (you can find all of these here at Sammobile.com or Samsung-Updates.com
Download the archive from the attachment & extract it. It contains a pit file, Odin v3.09 (newer versions are available too, I provided with this version so that snapshots don't differ), SuperSU v2.46, Root Checker (so you won't need to visit Play Store when your phone would be lagging after downgrading) SuperSU v2.46.zip & TowelRoot (so you won't need to visit their respective websites when your phone would be lagging after downgrading)
I request you guys to visit these websites before & or after this process to donate to their creators.
Guys! Please do so.
You'll also need Mobile ODIN Pro which can be bought from here.
Back up your data & ensure that your phone is charged 80% or more
Downgrade to N9005XXUEND3_BTU
Use Odin v3.09 & flash your phone with the N9005XXUEND3_BTU tar.md5 file & use the pit file that I provided in the attachments
Make sure that before you hit the Start button, it matches this snapshot-
{
"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"
}
The actual name & path of files will differ, just ensure that the same options are Ticked/Unticked
Let the device boot normally, a seeming Boot Loop might be encountered (I encountered it), don't worry, let it Boot Loop several times, finally, it'll Start
It'll lag (mine lagged badly ), will not have any Network signal/IMEI
Don't panic & be patient with your phone, you might need to pull out the battery if it goes totally unresponsive (mine did), but it'll manage to get the work done & be better with the operations after some time.
Connect it to the same PC as before (if you removed it after flashing it)
Copy the extracted tar.md5 from N9005XXUGNG1_BTU archive, SuperSU v2.46.apk & TowelRoot.apk into the phone's internal memory
Install TowelRoot.apk & Root using the app (reboot won't be required-I didn't need to)
Install SuperSU v2.46.apk & let it update SU binaries
Tick on Enable Pro in SuperSU, it'll restart itself
Tick on Survival Mode in SuperSU
Restart your phone now.
Use Root Checker, grant it SuperSU access & you should have Root access now.
Upgrade to N9005XXUGNG1_BTU
Purchase Mobile ODIN Pro & run it (grant it Root access)
In Mobile ODIN Pro, use the Open file option & choose the extracted tar.md5 from N9005XXUGNG1_BTU archive (it should be in the Internal SD-card if you've followed the steps precisely
choose Enable Ever Root
choose Inject Superuser
choose Wipe data and cache
choose Wipe Dalvik cache
Tap on the Flash Firmware option & then tap on Continue to go ahead with the flashing process
You might wanna plug in your phone's AC charger to avoid any power shortage during this critical phase.
Let the phone boot up, use Root Checker.
Phewwwww..... :victory:
Your phone should now have the Stock Firmware which is Rooted & KNOX 0x0
:laugh:
You can remove your phone from charging now.
But, if Lollipop is what you desire to have rooted on your phone, you'll have to follow these steps too..
Upgrade to Lollipop N9005XEOGBOA4_XEO
Put SuperSU zip in a folder in your SD Card (external SD recommended)
Put Lollipop ROM (N9005XEOGBOA4_XEO.TAR.MD5) in your SD Card (external SD recommended)
On Mobile Odin Pro, touch on "Open file ..." load the TAR.MD5 file and confirm
Then touch on "OTA / Update ZIP" and select the SuperSU v2.46.zip
Untick the Enable Ever Root box.
Tick the Wipe data and cache box.
Tick the Wipe Dalvik cache box.
Tap on the Flash Firmware option & then tap on Continue to go ahead with the flashing process
You might wanna plug in your phone's AC charger to avoid any power shortage during this critical phase.
Let the phone boot up, use Root Checker.
:victory:
Your phone should now have the Lollipop Stock Firmware which is Rooted & KNOX 0x0
:laugh:
You can remove your phone from charging now.
Note : The bootloader won't upgrade in this method.
DOWNGRADE POSSIBILITY TO KITKAT AFTER GOING TO LOLLIPOP?
Please read this.. :highfive:
Click on the following line for
LOLLIPOP 5.0 STOCK ROM MODS
Note : I take no responsibility for any damage that you bring to your phone, I just gathered information from XDA & some other websites (I don't remember which all) & used them myself - use them at your own risk.
Skip typing - hit
instead..

Waiting for the first tested users))) And why using PIT file? If I'm already use 4.4.2 with root and KNOX 0x0, that I not need firmware with PIT?

alex3n said:
Waiting for the first tested users))) And why using PIT file? If I'm already use 4.4.2 with root and KNOX 0x0, that I not need firmware with PIT?
Click to expand...
Click to collapse
4/5 current Thanks for the OP are there because it works for them..
1/5 current Thanks is from one of the developers whose app has been mentioned here, Root Checker's developer to be precise..

I would be very very wary of using PIT as many brick the phone .
I flashed using the original posts that this thread expands upon but at the boot loop just flashed Modem NF2 and rebooted .

JJEgan said:
I would be very very wary of using PIT as many brick the phone .
I flashed using the original posts that this thread expands upon but at the boot loop just flashed Modem NF2 and rebooted .
Click to expand...
Click to collapse
I did the "almost same steps" twice because sometimes (with these 2 Kitkat firmwares) the Bootloader won't update..

I used this instruction to root KitKat.
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
Apparently, you don't need to downgrade. Flashing old kernel is enough to use towelroot.

I'm already on N9005XXUEND3, rooted with TowelRoot with Knox 0x0.
Can I directly upgrade to Lollipop or I have to upgrade to N9005XXUGNG1 before?

cinciopillo said:
I'm already on N9005XXUEND3, rooted with TowelRoot with Knox 0x0.
Can I directly upgrade to Lollipop or I have to upgrade to N9005XXUGNG1 before?
Click to expand...
Click to collapse
Great.. :good:
You can directly jump to Lollipop.. :highfive:
Skip typing - hit
instead..

Still on Jelly Bean
I am still on JB - MJ3 (see in my signature). Rooted with Towelroot
Can I use this method but skipping the UEND3 ?
Also does this do the modem etc or is it just kernel?

louiscar said:
I am still on JB - MJ3 (see in my signature). Rooted with Towelroot
Can I use this method but skipping the UEND3 ?
Also does this do the modem etc or is it just kernel?
Click to expand...
Click to collapse
Yes, you can..
It'll upgrade everything.. Though, if you choose to move to Lollipop in the end-the bootloader will not upgrade and it'll stay to that version of Kitkat upon which you'll install it (Lollipop).. :good:

TheTAMAS said:
Yes, you can..
It'll upgrade everything.. Though, if you choose to move to Lollipop in the end-the bootloader will not upgrade and it'll stay to that version of Kitkat upon which you'll install it (Lollipop).. :good:
Click to expand...
Click to collapse
Is that a bad thing or is it ok to have the KK bootloader?
So to be clear, I just go from "Upgrade to N9005XXUGNG1_BTU" with mobile Odin?
My region is UK which is a non-branded phone. I think BTU is the correct version for this (supports 4G)?

im on 4g updated to lollipop polish version using mobile odin i then installed lollipop bootloader seperate using odin knox will stay 0x0 too

louiscar said:
Is that a bad thing or is it ok to have the KK bootloader?
So to be clear, I just go from "Upgrade to N9005XXUGNG1_BTU" with mobile Odin?
My region is UK which is a non-branded phone. I think BTU is the correct version for this (supports 4G)?
Click to expand...
Click to collapse
There might be some bugs..
I was personally facing bad battery performance but others reported that they didn't feel that way..
EDIT:Yes, BTU is correct.. I've the same device..
stesteste said:
im on 4g updated to lollipop polish version using mobile odin i then installed lollipop bootloader seperate using odin knox will stay 0x0 too
Click to expand...
Click to collapse
That's great..
Could you please share with us the link to the bootloader, I'll update the OP with it and give credit to you.. :highfive:

TheTAMAS said:
There might be some bugs..
I was personally facing bad battery performance but others reported that they didn't feel that way..
EDIT:Yes, BTU is correct.. I've the same device..
That's great..
Could you please share with us the link to the bootloader, I'll update the OP with it and give credit to you.. :highfive:
Click to expand...
Click to collapse
Thanks, I'll probably go in stages. KK first.
 @stesteste I also second that request for details of bootloader information and can you tell us the exact steps you took and from what firmware you updated?

yeah ill just find it guys i might have it on phone otherwise its on my pc ...be back soon
---------- Post added at 02:08 PM ---------- Previous post was at 01:42 PM ----------
havent got the bootloar tar at hand but its in this post somewhere if you want to go through them ..sry not at home for now so no pc
followed these instructions
http://forum.xda-developers.com/showthread.php?t=3029557

Does this method of obtaining a Knox 0x0 root on Lollipop extend to other Lollipop ROM's, or only the one listed in the OP?
For example would it work with a newer ROM, or with the UKO2 latest release?
I literally only want root to be able to use Titanium Backup, having just had the pain of losing everything following an unintentional factory reset (don't ask!)

SilverHelmut said:
Does this method of obtaining a Knox 0x0 root on Lollipop extend to other Lollipop ROM's, or only the one listed in the OP?
For example would it work with a newer ROM, or with the UKO2 latest release?
I literally only want root to be able to use Titanium Backup, having just had the pain of losing everything following an unintentional factory reset (don't ask!)
Click to expand...
Click to collapse
It'll work on others too.. :highfive:

TheTAMAS said:
It'll work on others too.. :highfive:
Click to expand...
Click to collapse
That's awesome!
Now... please excuse my ignorance, I'm such a 'casual' user, it's almost pathetic how unadventurous I am and how intimidated by 'warranty status' I am...
But...
Could you possibly explain to me whether there is any inherent disadvantage in me using this method over, say, simply having a stock unrooted Lollipop?
Does it create any inherent instability or issues that I should be aware of?
And do you by any chance know of a better stock unbranded Lollipop ROM which will work better or with greater stability than the current UK O2 offering?

SilverHelmut said:
That's awesome!
Now... please excuse my ignorance, I'm such a 'casual' user, it's almost pathetic how unadventurous I am and how intimidated by 'warranty status' I am...
But...
Could you possibly explain to me whether there is any inherent disadvantage in me using this method over, say, simply having a stock unrooted Lollipop?
Does it create any inherent instability or issues that I should be aware of?
And do you by any chance know of a better stock unbranded Lollipop ROM which will work better or with greater stability than the current UK O2 offering?
Click to expand...
Click to collapse
None that I'm aware of..
EDIT:I mentioned in my previous replies that, the bootloader will not be upgraded to the one that comes with Lollipop if you upgrade to Lollipop with this method..
The difference is that in unbranded roms, bloatware is less than those found in a carrier rom..
On the contrary, a carrier can choose not to include some feature or pre loaded app from the manufacturer.. For eg-in the US, a carrier removed Microsoft Apps from it's version of S6 rom (you can say that the carrier removed some bloatware this time).. :laugh:

Oh, I forgot to add... does it work with other 'KK' firmwares as the 'starting place'? Are there newer KK's that this method will also accommodate as the baseline to root and then install Lollipop and keep root and 0x0?

US Version flashing Internation version and mobile signal.

So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
{
"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"
}

mykenyc said:
So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
Click to expand...
Click to collapse
Did you still keep fingerprint functionality? I flashed the CE1 ROM last night and my signal strength is horrible compared to the US ROM.
Sent from my G8142 using Tapatalk

GiancarloMorr24 said:
Did you still keep fingerprint functionality? I flashed the CE1 ROM last night and my signal strength is horrible compared to the US ROM.
Click to expand...
Click to collapse
Yes flash back US then flash only these from Euro.

mykenyc said:
Yes flash back US then flash only these from Euro.
Click to expand...
Click to collapse
Got it. Thank you.
Sent from my G8142 using Tapatalk

Did you unzip the partition zip file and create a partition folder before you flashed?

Thanks for this my signal has been horrible as well after flashing the CE1 firmware on the US model. Just to summarize.
1. Download the US firmware.
2. Flash everything from it.
3. After this, from the CE1 firmware only flash the files shown from your screen shot.
Doing this will give the working fingerprint scanner as well as intended signal strength/quality from the original US firmware. Is my understand correct?
Edit:
Just tried and worked fine, not measured the signal strength yet but definitely looks to have more bars than I had before. I'll test at office on Monday where signal was not holding well compared to other phones [emoji106]
Any idea if this is going to affect the updates since we have files flashed from 2 different firmwares?

mykenyc said:
So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
Click to expand...
Click to collapse
Did you compare the actual dBm values before and after flashing, or were you just looking at the number of bars shown?
I don't know if Sony does this, but on some of my other phones like my S7 Edge the US Rom will show more bars than international roms on the same phone, however the actual signal strength (in dBm) is exactly the same.

walrusmonarch said:
Did you compare the actual dBm values before and after flashing, or were you just looking at the number of bars shown?
I don't know if Sony does this, but on some of my other phones like my S7 Edge the US Rom will show more bars than international roms on the same phone, however the actual signal strength (in dBm) is exactly the same.
Click to expand...
Click to collapse
No, but for myself when I flashed the Euro ROM in my apartment the signal would die or go to 1 bar I also had horrible call problems outside. Now I have full bars and have yet to have call issues so I'm sure it isn't a placebo.

mykenyc said:
No, but for myself when I flashed the Euro ROM in my apartment the signal would die or go to 1 bar I also had horrible call problems outside. Now I have full bars and have yet to have call issues so I'm sure it isn't a placebo.
Click to expand...
Click to collapse
Interesting, maybe the USA firmware's baseband is tuned to favor certain bands or something than the European firmware.
I haven't noticed any major difference between the Singapore and CE1 firmware on my XZP or my T-Mobile S7E. I haven't tried the USA firmware though.
In any case, I will keep this in mind if I do come across something down the line.
Do you know how this would affect future OTAs?

Interesting discussion. I purchased mine from the UK so I would NOT have to flash anything and still have the fingerprint sensor working. However, is it the consensus here that the US firmware will provide for a better signal? I am on AT&T pre-paid.
If I were to flash the US firmware over my phone from the UK will it kill the fingerprint sensor also???
Thanks in advance for any information!

I tried your method with the files exactly as you have shown but got stuck on the boot screen after flashing. Do you know what I did wrong?

Did you extract the files from the partition.zip and then create a folder called partition with those files in it. According to the developer of newflasher, that's what needs to be done

No I did not, I will do that now. Thanks for the reply.
---------- Post added at 02:01 AM ---------- Previous post was at 01:17 AM ----------
Same result, its stuck on the boot screen.

madmc320 said:
No I did not, I will do that now. Thanks for the reply.
---------- Post added at 02:01 AM ---------- Previous post was at 01:17 AM ----------
Same result, its stuck on the boot screen.
Click to expand...
Click to collapse
I would download and run xperia companion and do a emergency repair on your phone
http://support.sonymobile.com/us/xperia-companion/

Would you mind to create a step by step manual, please
mykenyc said:
So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
Click to expand...
Click to collapse
HI, would you mind to create a step by step manual of what you did, so we all can enjoy the finger print unlock feature and the good signal, please?
Cheers

As no one has done a step by step manual for dummies like me...
hittori said:
HI, would you mind to create a step by step manual of what you did, so we all can enjoy the finger print unlock feature and the good signal, please?
Cheers
Click to expand...
Click to collapse
Hi,
a few days ago i asked if someone can create a step by step manual for dummies like me, and no one has done it. Therefore i put some effort, and risk, and i tried myself. Open hundreds of XDA developers pages, and at the end this is what i found outÑ
1.- Download XperiFir from here version 5 in my case.
2.- Click on Xperia XZ Premium Maple, then in G8142 dual, then in Central Europe, finally on the right side click on the 45.0.a.5.1; this will start the process and download 3 files which it will unzip for a total of 2.75GB
3.- Download New Flashear from here [Updated for Oreo]
4.- Copy to the folder where you unzip Newflashear the following files:
as you can see in the right side i have all the files from the European Version, and i copied to the left side (where the newflasher.exe is) the needed files
5.- in this folder, create a folder call partition and unzip all the partition.zip files in there.
6.- Check that you have the boot, flash_session and Partition folder. in the Boot folder you should see this:
and in the Partition folder this:
7.- Turn off your Sony Xperia XZ Premium, press the volume down button and plug the Usb C cable to the phone and the other part to the Computer
8.- Run newflasher.exe (I did as Admin to be sure it will run with no restriction).
8a.- Newflasher will be asking you two questions, type n and then press enter on both questions [Update for OREO]
9.- Wait and enjoy it will tell you when to unplug it and turn on your device.
Extra, in my case it took me a few tries to turn it on. What i think i found out is that if I press Volume Up and Power ON, it does power on.
Enjoy your previous disabled feature, now finally enabled.

Thanks for the guide, I am getting am disk space error. Error code 112 during the system_X inflation process. The device has nothing on it , why am I getting this error.

I can not find the folder flash_session, What is it? And where do I find it?
Cheers

san.13 said:
I can not find the folder flash_session, What is it? And where do I find it?
Cheers
Click to expand...
Click to collapse
it was empty, so no need to have it. If you please, create it yourself, but i believe it was created first time i run it without the right files
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
madmc320 said:
Thanks for the guide, I am getting am disk space error. Error code 112 during the system_X inflation process. The device has nothing on it , why am I getting this error.
Click to expand...
Click to collapse
Sorry, i have no clue why is that.... Do you have the US version and installing the European version, are you? maybe someone with more experience can help you here.

hittori said:
it was empty, so no need to have it. If you please, create it yourself, but i believe it was created first time i run it without the right files
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
Sorry, i have no clue why is that.... Do you have the US version and installing the European version, are you? maybe someone with more experience can help you here.
Click to expand...
Click to collapse
Fixed the issue by moving the file to another location. Not sure why it the difference was because there was plenty of space.

Bricked MT6577 SoSoon/Senq X8 Elite 3, NO USB Debug/ADB, Stock Recovry No Roms to D/L

I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time

Hello have you tried a hard reset so far ?

-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it

can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations

-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"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"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.

the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope

-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk

-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.

Dead Devices After using DRM fixes!!

As said in the title... my insurance company has given me several different devices after they keep dying during charge.. I have had several different G1841's and they all seem to die during charge a few days after from applying the DRM fixes and do not turn back on again at all... Has anyone else experienced this issue yet??
I applied all the OTA updates through Sony's official software update then I unlocked the bootloader so I do not believe I am doing anything wrong.. It's just that the devices keep dying every time I obtain root access!! Not sure what to do as this is the 4th time it has happened (happened just today after receiving another device only a few days ago, my insurance company will start to think something is up now...)

Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?

saved-j said:
Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?
Click to expand...
Click to collapse
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?

avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?

avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?

YasuHamed said:
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?
Click to expand...
Click to collapse
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Didgesteve said:
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?
Click to expand...
Click to collapse
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
{
"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"
}

avi312singh said:
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
Click to expand...
Click to collapse
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.

sToRm// said:
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.
Click to expand...
Click to collapse
I believe I used the zips from your 2.0 software.. I sent you a donation through PayPal when you released this, do I get the software or some sort of discount? Student life has hit me hard this year
Well I am getting a completely different device tommorow and will hopefully be able to use your 3.0 fix on it... With regards to the charger, I will use a new wall charger - hopefully can order a new official one from amazon when it arrives and not charge it till then
Before unlocking the bootloader and applying the DRM fixes I experienced no problems such as dead devices.. Let's hope the sixth device is ok!

Update: the culprit of this was the battery charge limit application which requires root privileges and is found on the Google Play store.
I'm not going to link in here but there seems to be a conflict with either the device., rom I don't know - but yeah just making people aware of this

General SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)

Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99% sure the methods will work for any mediatek version of this phone just make sure to use your correct firmware
the tools included will allow you to :
Enable OEM Unlock +Unlock the Bootloader
Create Scatter Firmware
Unbrick your device if stuck in Brom/Da mode
Root Your Device / Install TWRP
Enter Brom Mode
and more
All instructions are included inside the main folder of tools, seriously... and i mean seriously...please read the 3 or 4 different guides/methods to see which ones you actually need to do. Some are not needed depending on your end goal. I spent a month making every error possible and testing things so you dont have to so save yourself the trouble and read through
Ill do my best to answer any questions or issues you might have but please...please use your eyeballs and google.. i really dont want to have to answer questions like "how flash magisk" etc. Google is there.. it is your friend , use it. XD
A12 Toolkit.zip | by Privyetcyka for Galaxy A12 Nacho
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com

Thank you, I hope I can figure it out with the translator, I went to try ..

fackstrot said:
Thank you, I hope I can figure it out with the translator, I went to try ..
Click to expand...
Click to collapse
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you

PrivyetCyka said:
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you
Click to expand...
Click to collapse
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware

fackstrot said:
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware
Click to expand...
Click to collapse
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included

PrivyetCyka said:
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included
Click to expand...
Click to collapse
I followed the steps, I was inattentive myself) but still ran into a problem

when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
{
"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"
}

Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error

well, if I put it from SM-A125W, then the rollback error

Will that work for the Samsung Galaxy A13

Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.

Ansemseekerofdarkness said:
Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.
Click to expand...
Click to collapse
I have no idea which directions your directions your talking about the only ones I wrote are the ones in the main folder , probably with a bunch of exclamations. I can't remember and don't have the file with me right now but as far as unlocking the bootloader you just need to get the phone to accept different firmware. Try flashing Sm-a125w Canadian version XAS

fackstrot said:
when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
Click to expand...
Click to collapse
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included

PrivyetCyka said:
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included
Click to expand...
Click to collapse
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center

fackstrot said:
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center
Click to expand...
Click to collapse
Nothing is supposed to happen if nothing happens that is good . Just leave the phone connected how it is and use a mediatek unlocking tool

When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!

ronnieshane1 said:
When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!
Click to expand...
Click to collapse
Change date to 25 may 2022 to get working

Ok... im trying to repair mi phone and failed i follow exactly as i seen in the readme instructions on the unbrick folder and nothing... i got 2 errors in relation of super.img (im trying to flash the last android 11 firmware on the phone A125MUBS3BVF1) if i uncheck the super the phone flash correctly but doesn't boot so what next...?

fackstrot said:
Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error View attachment 5664401
Click to expand...
Click to collapse
And now i had this error i think using the format all + download relocks the bootloader sp flash tool is asking me to download signed images i can't exit from that so i give up and buy another mainboard

My last reply...
I uploaded some images to get BROM working on A125M this zip includes
Preloader and PGPT files from 4 firmwares
Android 10 Binary 1 (AUC1)
Android 11 Binary 1 (BUF9)
Android 11 Binary 3 (BVF1)
Android 12 Binary 3 (CVH3)
Plus i will modify this post because im uploading CVH3 firmware for SP Flash tool flash (Includes the scatter) pls disable the auth using mtkmeta or the python coded program (used 3.7.9 and worked using the shell)
PGPT and Preloader images