Related
THIS GUIDE IS SPECIFICALLY FOR THE MESMERIZE
Steps To Customize Your Mesmerize (For upgrading from any version to FROYO 2.2 EC10)
1.) Upgrade from any setup to 2.2 EC10 (Official Froyo) - If you have not already done so, you will need to upgrade your phone to EC10 2.2. If you have already, skip to the next step. (You can check this in "settings->about phone" under "firmware version" (should be 2.2.1 if you've already done this) NOTE: There is a custom rom listed in this post, I will detail that down below.
NOTE: The roms for this version come pre-rooted, so no need to root. However, if you have issues with superuser permissions (or are staying stock with root), you can use the SuperOneClick Root tool located here
If in the previous step you installed the leak that had the CWM upgrade pre-loaded or you have already manually updated CWM, skip step 2.- You know you have the updated recovery if when you boot to recovery it takes you to the red recovery with voodoo, backup and other options.
2.) Upgrade CWM manually (if needed) downloading this., (this next step by step will upgrade your recovery so that you are able to flash custom rom's/theme's/kernels.)
1.Shut phone off, pull battery out and leave it out.
2.Run odin (assuming you have it installed)
3.Load the cwm-recovery-all.tar file into the PDA spot
4.Plug usb into computer, then into your phone.
5.Hold the volume down key until phone goes into download mode, there will be a yellow android picture.
6.In odin, one of your com: spots should light up yellow - this means your phone is seen by odin (if not you may need drivers)
7.If above step is true, press start and odin will flash the recovery file to your phone. If all goes well the yellow box will turn green and your phone will power off.
8.Now you're able to boot into CWM recovery using the three button method (see glossary here)
3.)Upgrade Kernel With EC10 brought a new turn of events which thanks to jt has allowed fasicnate users to develop kernels which are compatible on the entire line of this model, so be sure to read phidelt's post on kernel's located here and choose one that is compatible with your rom. AOSP and MIUI require a different kernel, so keep this in mind as if you're restoring you may need to flash the appropriate kernel as the restore does not do this for you.
4.) Flash a custom ROM Choose from one of the Custom Rom's that we have out right now;
EC10 Pick and Pack DOWNLOAD HERE -- This is our stock deodexed rom with bloatware moved to a seperate .zip containing flashable packages with those removed apps. - < created by: phidelt82 >
EC10 Custom RomDOWNLOAD HERE - This is a custom rom built by phidelt82 which incorporates some aspects of AOSP into the EC10 rom - launcher and calendar are to name a few.
AOSP -DOWNLOAD HERE - This is a custom ROM/Kernel built with the android open source project code (by lmartin), one of the most "vanilla" rom's meaning no manufacturer's additions such as touchwiz. It's very lean and runs well, but is in BETA stage so beware it may not be for your daily use. NOTE: If you use this rom/kernel and are wanting to return to EC10 you will need to reflash the appropriate kernel for the ROM you are restoring to (for example touchwiz)
MIUI -DOWNLOAD HERE - This is a custom ROM running on the AOSP kernel, you can learn more about it in the thread linked here.NOTE: If you use this rom/kernel and are wanting to return to EC10 you will need to reflash the appropriate kernel for the ROM you are restoring to (for example touchwiz)
GAS EC10 PNP based rom -DOWNLOAD HERE - This is a custom ROM that runs with the touchwiz kernel. Learn more about it in the linked thread.
HEINZ 57 EC10 (PNP/ED01/EC10 based rom) -DOWNLOAD HERE - This is a custom ROM that runs with the touchwiz kernel. Thanks to Sbrissen, it has a lot of extra settings in the TM parts settings menu, allowing you even more customizing. Learn more about it in the linked thread.
5.)Flash a custom THEME Pick one that's compatible with the ROM you are running, from this list.
HELP MY PHONE IS SCREWED (GO TO STOCK 2.2)!!!: If you weren't attentive and made a mistake or haphazardly missed a step and now you're stuck at a boot screen or one of many other failure points, stop what you're doing. Take a deep breath, wu-sa, grus-fraba, whatever you need to do to calm yourself and simply go to this thread and get your phone back to stock. You may not need to go all the way stock, but it seems to be the easiest, and requires the least amount of help from the developers (who have better things to do than answer questions of careless/unlucky people!! - no offense intended) This is also how you would handle getting your phone back to stock before trying to turn it in for repair.NOTE: Being as going to stock means it's expecting your phone to be formatted to RFS instead of EXT4 (lagfix enabled) you should disable lagfix before doing so or you will have errors and md5 mismatches which will disallow you from flashing from recovery. If for some reason you can't access recovery you will just have to disable lagfix manually which is detailed in this thread here.
---------------------------------------------------------------------------------------------------------
==================================================
---------------------------------------------------------------------------------------------------------
THIS IS THE OLD GUIDE FOR CUSTOMIZING 2.1
When I began this process, I had zero experience flashing any sort of software to any sort of devices, and a very minor understanding of "rooting". After much research and crawling I was able to work my way through these steps with little headache, and learned a lot along the way.
Keep in mind there are many variations to each step, this is what worked for me the easiest as a newb.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
So make sure you're in a comfortable environment (not a good idea to be trying to accomplish this while slamming beers at the bar), take your time, read each step that these people have taken the time to carefully write up (then follow it), and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. Always give it at least 5 minutes before you determine it's looping or crashing or whatevering, there is alot going on behind the scenes, trust me!
Steps To Customize Your Stock Mesmerize (For eclair 2.1)
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal, trust me .
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Mesmerize on 2.1. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone. (Recovery is basically a bios like interface - but it's different than the stock version)
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I had downloaded, along with following with the instructions.
(In your file manager, MAKE SURE YOU ARE Read/Write not Read/Only, for RootExplorer there is a toggle at the top, other ones you may have to enable this through settings, others may just be R/W by default, you will just have to determine this or google the app)
Download the two zip files located in the first post here
Place both files on your SD card root if you were using a computer to download them or you could always download them through your phone's browser
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
Now open TerminalEmulator (Come with me if you want to live )
NOTE:The spaces below are actual spaces and in bml8 there is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the mesmerize. By now - you better damn well trust me , this is just what works with our model
At this point you're all stock and ready for new kernel/rom. (but now you are able to do so very easily)
3) KERNEL: Install Voodoo lagfix kernel and new 5.0 sound
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
You could always install the old Voodoo kernel located here, if for some reason you do not want to take advantage of the new, sound improved one.
Note: Just an FYI, after installing custom kernel's you will always have an issue on start up of seeing a flashing black box in the middle of the samsung logo. This can be corrected by installing a custom boot screen (only requires root access) and you can find out how here.
Note: There are a few ways of getting into this recovery mode, the best way if all else fails is to hold phone from the back with left hand (thumb on volume button, in the middle holding both down and pointer on power button) hold these down until the mesmerize logo pops up then slide your thumb down a bit to volume down only (if you slip don't worry it might blink but it'll still go to recovery) Sometimes this is easier with the back case off. However the best way, is to download and use the QuickBoot app, it allows boot to recovery/reboot/poweroff options from the app.
4) Custom ROM : Download and install the ROM of your choice.
Just pick one from this list Here-They are all there along with other very useful links, read through the first post of each before you decide, some are plug and play some take a few steps first. These are currently only 2.1 eclair builds however right now they have an (somewhat unstable) 2.2 froyo rom/kernel that being worked on but is not quite yet ready for day to day use (some features are not working quite yet). But be patient because these guys will have something long before Samsung let's us have theirs, but who cares - "ours" will be so much better
HELP MY PHONE IS SCREWED!!! (GO TO STOCK 2.1): If you weren't attentive and made a mistake or haphazardly missed a step and now you're stuck at a boot screen or one of many other failure points, stop what you're doing. Take a deep breath, wu-sa, grus-fraba, whatever you need to do to calm yourself and simply go to this thread and get your phone back to stock. You may not need to go all the way stock, but it seems to be the easiest, and requires the least amount of help from the developers (who have better things to do than answer questions of careless/unlucky people!! - no offense intended) This is also how you would handle getting your phone back to stock before trying to turn it in for repair.
MASSIVE AMOUNTS OF Credit go to all of the OP's and many others (some included in my sig), these people are awesome, show them some love! Without them we would be stuck in stock US cell/Samsung HELL!
Final NoteIf you have any suggestions, additions, corrections, subtractions, or multiplications; PLEASE LET ME KNOW! I'm very open to all of the above and since this is now more of a community article let's stick to the android motto and keep it...open source
I gotta say, you did a really good job explaining yourself there. Now I'll just have to send people to one post and not a bunch when I get messages at all hours of the night.
Good work!
phidelt82 said:
I gotta say, you did a really good job explaining yourself there. Now I'll just have to send people to one post and not a bunch when I get messages at all hours of the night.
Good work!
Click to expand...
Click to collapse
Hey thanks, and believe it or not this is the exact reason I decided to put this together with this much detail (aside from answering someone's question). I figure, I'm no android developer but I can follow instruction and explain myself pretty well so I put this together to take some of that off of you guys. (A small token of my appreciation)
Nice work! Stickied for others to follow
Oh and love that comment:
Now open TerminalEmulator (Come with me if you want to live )
Click to expand...
Click to collapse
Gave me a good laugh!
the_scotsman said:
Nice work! Stickied for others to follow
Oh and love that comment:
Gave me a good laugh!
Click to expand...
Click to collapse
Haha well good and thanks, I almost put /badjoke at the end of that comment
EDIT: Edit to main post.
Good Job! This pretty much covers everything. Hopefully soon we can add to it :S
Is there a rough idea of the amount of time it will take to complete? I have pulled the battery a couple of times, and it just sits at the "running exploit in order to obtain root access" spinning the icon for several minutes. I have re-started it for a third time, now just letting it spin to see if it will come around.
LaTuFu said:
Is there a rough idea of the amount of time it will take to complete? I have pulled the battery a couple of times, and it just sits at the "running exploit in order to obtain root access" spinning the icon for several minutes. I have re-started it for a third time, now just letting it spin to see if it will come around.
Click to expand...
Click to collapse
Usually it only takes about a minute or so to complete. If it gives you problems, give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Mesmerize on 2.1. It is located here.
Just wanted to say thanks for all the hard work and for the write ups for those of us new around here. You guys make the scene available for the rest of us.
Sent from my SCH-I500 using Tapatalk
Thanks for the easy walkthrough.
I am getting stuck at the end of step 2. The "redbend_ua restore" part was completed successfully, and after the phone rebooted I launched Rom Manager and clicked "flash ClockworkMod Recovery", selected the Fascinate, and keep getting an error message stating "An error occured while downloading your recovery."
Am I doing something wrong? Is there another way to get clockwork recovery onto my phone? I am on WiFi with a strong signal (I'm about 3 feet from the router) and the connection is working fine in other apps (browser and whatnot) so I don't think it's my internet connection.
Any help for this total newb to the android community would be greatly appreciated.
Mesmerizeuser said:
Thanks for the easy walkthrough.
I am getting stuck at the end of step 2. The "redbend_ua restore" part was completed successfully, and after the phone rebooted I launched Rom Manager and clicked "flash ClockworkMod Recovery", selected the Fascinate, and keep getting an error message stating "An error occured while downloading your recovery."
Am I doing something wrong? Is there another way to get clockwork recovery onto my phone? I am on WiFi with a strong signal (I'm about 3 feet from the router) and the connection is working fine in other apps (browser and whatnot) so I don't think it's my internet connection.
Any help for this total newb to the android community would be greatly appreciated.
Click to expand...
Click to collapse
It's not you. I believe Koush's repo is down right now. Hopefully it will be back up soon and you will be able to finish up.
Thanks for the heads up. Is there any way to get the recovery on the phone without using rom manager, or will I have to wait for the repo's to come back up?
never mind
It's back up. Just flashed to a voodoo kernel. Thanks again for the great instructions.
Very good write up.. You actually made it kind of fun to read if that makes sense.. lol
I seem to be running into problems. Whenever I go into recovery mode my phone doesn't verify the update.zip file. I was wondering how do I fix it or get another one? Also what part does this file play in changing roms?
Error:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Install aborted
Also very good write up A++ would hack again
Edit: got it working. I had to rerun redbend_ua and make sure it went through a full reboot and didn't stall. I think I wasn't giving it super user permissions. Great writeup thanks again!
thanks this is worked great for me on the Froyo step by step
jmtenny said:
thanks this is worked great for me on the Froyo step by step
Click to expand...
Click to collapse
Great, glad to hear it! This is a new addition and I've just made some more changes and also reformatted the OP so i'ts more obvious that there are two processes.
Thanks so much for taking the time to do this!
I'd like to think that now I have a better understanding of what I'm doing.
I'm having some problems and was wondering if someone could help me please.....
I successfully installed the EA11 leak and updated from 2.1 to 2.2. However, when I boot into the blue recovery and try to hit update.zip from there it just shows me an exlamation icon and never goes into the red recovery instantly like it should according to everyone's directions.
At thiis screen it will stay showing this icon, and the only way off of it is to hit the menu key which takes you back to the blue recovery screen. It then has a description below the blue text that says:
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:Failed to verify whole file signature
E:signature verification failed
Installation aborted.
Am I doing something wrong? Any feedback would be so appreciated.
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)
Ota - lmy47v1218_2217
For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.
I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.
Uninstall Xposed (moar hacks)
/system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
/system/etc/permissions/platform.xml (sd card "fix")
If trying to address the issues manually does not work, follow the procedure below.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update
General Notes - Lolipop
Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
SD cards bigger than 32Gb still do not work correctly on stock firmware
Known Working Customizations
To be determined
KitKat Notes
All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)
Sources / Mirror(s)
The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/
Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45
Do you trust Kingo?
I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
kemonine96 said:
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.
Click to expand...
Click to collapse
tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Components to clean up?
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
kemonine96 said:
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse
tomzweifel said:
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.
New OTA Update
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
tomzweifel said:
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.
kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.
Will post back with more info after I've had some time to poke at the OTA some.
Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.
Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.
In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.
Happy hacking and OTAing everyone.
kemonine96 said:
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device
Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?
Dear Friends,
About to pull a trigger on an AT&T LG G4, can someone give me a short answer, ASAP?
Is it possible to have permanent Root and Xposed on the AT&T variant WITHOUT ridiculous bugs like a "green dot" in the camera of the phone? (what does the green dot even mean? It's on every picture? Is it a watermark? Just on the GUI?)
If possible, how? And should I buy the phone?
Appreciate any QUICK responses, about to buy now! Thanks so much in advance!
I just bought the G4 a couple of days ago. I was able to root, but there is no twrp or xposed as far as I know. I also don't have the green dot and everything is working fine!
Thanks for the quick response, my friend. Can you share the method/thread/image you used to Root?
I think you can install Xposed without TWRP via FireFlash? Can someone please confirm?
Thanks guys!
Just got my G4 two days ago. You can root and you can install Xposed with FireFlash. Root requires pushing a rooted version of whatever software version you are currently running. If you can't find one you can inject root into your own system.img using Ubuntu. After root get FireFlash and the right xposed zip and be patient, it can sit black screen, appearing dead for 20-30 minutes. Over all not too hard. Took me a couple hours from The un-boxing to Xposed. Definitely do it. The green dot on camera comes from the PR system.img. I'd stay clear of that. Everything is working great on mine!
@Nowak4G - Thanks bud, that's what I read too. Can you point me to the guide and img file you used that worked for you? I doubt I'd prefer the Ubuntu way...
One other question... Is there a way/app/Xposed module that's kind of like G3TweaksBox for us? Letting us change the Status bar icon colors and toggle colors?
I highly doubt themes work for us since we can't Flash them without custom recovery?
Thanks again!
GravityBox works for status bar stuff and yeah here are the threads I used. Good luck bud!
http://forum.xda-developers.com/showthread.php?p=62028519
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
http://forum.xda-developers.com/showthread.php?p=62664473
I'm not totally sure what stuff can and can't be flashed using FireFlash. But for applying icon themes with Xposed I use this module, Unicon:
https://drive.google.com/file/d/0B1nrydqmmOBUdFoyV0FBLUM1OVE/view?usp=docslist_api
I've had my LG G4 rooted and running Xposed with a lot of modules enabled.
If the phone you buy is on the 10G software version (and want to stay on that version), you should be able to root it following the method in the LG G4 Low Effort Root thread. Follow it to the dot and enjoy partial freedom.
If the phone you buy is on 10I, there is a rooted image floating around. So you could take the 10I update (or make sure your phone's on the 10I version), and root it using the Low Effort Root method.
I would also recommend the following:
1. keeping a copy of your untouched fresh system image in your internal memory (as early as possible after buying the phone). In case of a bad flash you have something to possibly go back to - otherwise you'll end up with the PR ROM and the green dot. The method and commands to extracting the system image is very similar to rooting, except instead of dd'ing into the system partition from SD, you do the opposite (from system partition to SD)
2. disabling system apps and system updates using the debloater tool and a tutorial here on the forums
Regarding flashing files via recovery, I usually extract the files and place them in the correct directory with the right permissions. Usually most files use 0644 permissions, but I would first check the existing permissions with ES File Explorer.
Hello @Nowak4G and @mu3g,
Guys thank you for your response. I can confirm that the seller I bought the phone from took the 10l upgrade. I have little to no experience rooting locked bootloader phones, and I have to be honest, I am more confused than I have the answers. Now that I have confirmed that I will end up with 10l update, can you guys give me a noob boost and give me step by step on how to root, Xposed, and possibly back up my stock image, since I do NOT want to end up with the PR build, with the green dot, in case things go wrong?
Am I correct that the right answer to my problem is, Low Effort Root with the floating 10l rooted img file, located here: https://drive.google.com/file/d/0B54ceS-n3ZAiaVAxMkJFLXNMYmM/view?pli=1
Please help me out guys, would even appreciate more if we can maybe connect on Google Hangouts for some dynamic help? Please let me know and thank you again for your wonderful so far !
Yes, exactly. Use the floating around 10I rootedsystem.img with the Low Effort Root instructions. But definitely keep a unrooted system.img on the internal storage as a backup. Instructions are in the LER thread. Just read carefully and follow the steps and you should be fine. All copy and pasting.
You have the correct 10I rooted system img file. I would recommend following the LER steps and backing up the system image for 10I (see post 2 of the LER thread). This would give you the stock image for later use. Then follow the LER steps to the dot using the rooted system image file you have from the google drive link. The LER thread has pretty clear instructions on backup and flashing system image files for the G4. Just make sure to rename your downloaded file as "system.rooted.h81010i.img" and use it in the command...the file name here is the most important!
Thank you guys, couple of follow up questions:
1. Do I run the backup command to copy my Non Rooted image, right after the step that gives us the DIAG Port Number? Or do I do it after the "id" step?
2. The generated back up, I assume will be done as an .img file in the root of my phone, correct? I assume I just back this up on my computer and/or External HD?
3. This is the scariest step. When I am running the step for flashing the rooted img, I need to rename the downloaded file to, "system.rooted.h81010i.img" as @mu3g recommended? Why not, "system.rooted.h81010m.img" for example?
4. I just use the exact file name we determined above for my downloaded rooted 10l image file, in the flash command when following the LER guide? Exactly that file name, correct?
Thank you again for all your help and excuse me for my continuous noobness!
Answers:
1. Run the backup command in Step 7 of the LER root ("Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.") <<---replace the commands to run with the command to backup your unrooted clean system image to your internal memory ---- if you compare the commands, it will become obvious on how the data is being moved (pushed or pulled from the phone).
2. The generated backup will be on the root of the internal memory of the phone. Yes, you can then move it to your computer or any other location for safekeeping AFTER you've booted your phone up properly - don't do any of this while you're still in the LER state.
3. I just gave you a recommendation on the name..you can name the rooted system image file whatever you want - you can even leave it as the way it is....just make sure to use the EXACT file name for the image in the commands to run (also 10I, 10M etc. are software version numbers..I'm not aware of a 10M version being released for AT&T. In any case, just use the EXACT file name for the rooted image.
Thank you @mu3g! I think I am now ready to go through the process myself with confidence.
I am, however, still a bit confused about the file name of the rooted image that I will be flashing. If the phone already has 10l installed, and I leave the name of the rooted image intact, that is, "system.rooted.h81010l" would the phone still accept/get tricked into, thinking that it's getting an "update"? Or did you mean that the file name could literally be anything like, "filename.img" and if the commands match it, all will be installed correctly? As in, when the system boots, it will have all the correct build and software information with it being a 10l update and etc?
Please forgive the annoying, detailed questions, but I want to not mess this up, since every guide triple emphasizes the importance of the command being absolutely right! Thank you!
You can literally name it blahblahblah.img as long as you use blahblahblah.img in the commands to run for the rooted system image. The file naming scheme has nothing to do with the acceptance or rejection of a system image. When you're in the bootloader mode ready to download files (which is the mode for LER), you can inject any file into any partition, anywhere on the phone...it's just whether the phone can use it or not properly and whether or not it ends up being a brick
Your file name for the system has nothing to do with the build number showing on the phone after booting up.
EDIT: The only reason I gave you that file naming scheme is because you don't seem to be too comfortable with the command line, thats all..that way you could copy paste the command from the LER guide and just replace "g" with "i" - that's all..if you're good with the command line and careful, you'll be fine..just make sure the file name is correct..you can't get much else wrong.
Understood brother, just needed that clarity. I am not an absolute noob with cmd line, but you know how it goes when you're rooting your phone, the perpetual fear of an expensive paperweight!
I cannot find the thanks button here, wish I could, so I could thank you over and over and @Nowak4G, but either way, thank you so so much @mu3g!!
good luck!
How did it go? Were you able to go through with it?
While the green dot does usually appear on 810 phones running the PR KDZ, I have heard reports of it on some 815 ...its pretty random. I just did a warranty exchange for my 810 so I will likely be staying on the ATT software.
Hi Guys, wanted to update this thread with my results...:
I successfully rooted on H810l (AT&T) with 0 issues, following the Low Effort Root. Per the recommendations of the process, I also backed up my Stock, Unrooted, .img file for restoration to Stock, if it were needed. Well, I might be moving on from this phone and need to return to stock. Can someone advise the exact steps/commands to return to stock using the unrooted .img file I backed up before pushing the rooted .img? And can you confirm that you did this successfully as well?
I would really appreciate it! Thank you!
I have not done it myself, but if you uninstall all your root apps completely, make sure to enable any and every disabled app you may have (like for example AT&T apps etc.) using the debloater software and then follow LER to install the stock image on it, it should come back to bone stock. Remember, the key here to to ensure that no root apps exist on the phone - I guess SU will get wiped out, but its better to do it clean. And secondly, any disabled apps need to be re-enabled for a smooth process. These are just my $0.02...so proceed with caution.
So, I think that it's a good time to start another thread about the One X2. I own an X2 Mini & am really liking it.
The first thing I can say is to BACKUP your install several times until you get root. MAKE SURE to include your boot.img as part of the backup.
1. Going thru unlocking the bootloader (easy), Installing TWRP (moderate) & Rooting (very frustrating) was an interesting experience. Unlocking the bootloader was by far the easiest I have ever done on any phone. Just enable developer options & tic the switch....That being said---the rest of the process was a PITA.
2. Installing TWRP was easy/moderate--having to do it twice & finding that the tool I used installed an early version that put everything upside-down was "interesting" but not really too difficult (I'm a linux guy, so a trip to the terminal & ADB fixed that without too much trouble).
3. Then came the Magisk install--that took a couple of days & quite a bit of help from forum members to get "sort-of" ironed out. There is protection on the boot/kernel that takes a bit of work to get in the right order to get root. With the Stock ROM you need to either run the AutoRoot script from BLOX2.com ( http://blox2.com/how-to-root-the-blu-life-one-x2/ ) or if you are terminal-savvy there are manual instructions also. I'm NOT a Windows guy, but tried the auto route first......That in retrospect was not the best way for the X2 Mini---the version of TWRP that it installs is early & upside-down so controls do not work. I got past that & found thru trial & error I needed to install Magisk 12.0 (via TWRP zip install) & MagiskManager 4.33 (with a APK Manager after reboot) FIRST. (as Ieatgravity pointed out...)
4. After you get to root this way you can just stay there (depends if you need SafetyNet or not) or get the more modern version of Magisk. As AlienTeck points out, you MUST install zips inside of TWRP due to the way the boot/kernel protection works. Installing inside of TWRP works outside of the booted system & gets the install done. You can't at present install inside of a running system without a reboot as soon as the kernel detects a system-wide change. This would prevent several "on-the-fly" root modifiers from working. I would hope someone will see the need to create a new boot.img & Kernel to side-step these issues.
5. There is only one custom ROM available right now---DRAX, & with my current experience, it seems to work MUCH better than the Stock ROM. It changes the spacing on-screen (for the better) & is debloated....definitely is faster/smoother than Stock.
Well---I'm not the FINAL authority on the X2/X2/Mini...there are several great people on the forum...I did this just to give a brief info list for people to look at without TOO much searching. You will find all the answers in the main thread----it just takes a bit of digging to get to them.
My hope is that this thread starts a "how-to" thread for people to refer to...And if I've miss-stated any info I've posted above, please feel free to correct me.
I downloaded the very latest Magisk from git ( https://github.com/kantjer/MagiskFiles ) version 13.3-170812-zip & then removed the Magisk App-booted into recovery-flashed the Remove-Magisk zip-cleared cache-rebooted into recovery-flashed the new version & NOW I have Magisk working properly.
I thought I'd offer a newbie perspective on the big brother BLOX2 (Life One X2 4 gigs /64 gigs).
I was planning to use BLOX2 AutoRoot, but I couldn't make it work. It got as far as unlocking the bootloader, then just sat there doing nothing. Same thing for BLOX2 ToolKit. (I think both problems were caused by my computer, not the software.) So then I decided to do the unlock via ADB, then Flash TWRP f=and BLOX2 Core from an SD Card.
My laptop (Lenovo ideapad FLEX4 running Win 10 Home 64 bit) does not like to recognize my phone. When I open a command prompt window and type in 'ADB devices' (ENTER) the computer pops up a notice telling me "the last USB device you connected to this computer malfunctioned and Windows does not recognize it." ADB returns an ambiguous statement that "a list of devices is attached" (to what, I have no idea). NONETHELESS, when I got frustrated and ran "fastboot oem unlock" it unlocked my boot loader in less than 2 seconds. Go figure.
I had to install TWRP a couple-three times as well before it "took" and stayed even after a reboot to system. I remember reading in a guide to rooting the Blu R1HD (if memory serves) that one ought to reboot into recovery after each step in order to make sure that the original image does not overwrite the new one. Don't know if this is related, but I followed that dicta from that point on. Lucky for me, TWRP installed right-side-up.
As for installing BLOX2 Core, the hardest part of this was putting the file onto an SD card in such a way that TWRP would recognize it. After that I popped it into the phone, booted up, opened TWRP. I found the BLOX2 Core file, flashed it and sat back to watch the magic happen. Line upon line upon line of pretty little code bits rolling by -- and all of it in black! No angry red lines to be found anywhere! As someone who is so far much better at bricking phones than modding them, this was truly a lovely site.
After this, there was really nothing left for me to do but BACKUP EVERYTHING! First I did a TWRP backup. (I have not been able to convince Nandroid itself to function on demand. It works fine on a scheduled basis, but when I try to run it directly it runs for three seconds, announces it is finished, and presents me with a non-file.) Then I installed one of my favorite apps: Titanium Backup. I setup TB to backup all system data and user apps on a schedule, and then ran the first one directly.
In all the excitement, I had forgotten all about Magisk, but a few hours later I noticed an icon labeled "Magisk." I clicked on it just to see if it was actually installed or just sitting there to install if I wanted to. When I saw that it was indeed the installer I just shut it down and left it alone. I strongly suspect that it was SU-Magisk failing to play nice that led to my bricking my first BLOX2, so I wanted to research how to get rid of it safely. Well, before I could get anywhere on that, the system on my BLOX2 started acting weird in familiar ways. Apps that I had not opened started 'closing' suddenly -- each one flashing a popup at the bottom of the screen that immobilized the touch screen until it was dismissed. When my first BLOX2 started doing this I thought I must have gone overboard with one of the longer-battery-life (Xposed) modules. So I frantically started zeroing them out to stock. This didn't help and the slippery slope had been crossed.
With my second BLOX2 I was a bit better prepared. I immediately uninstalled MAGISK and frantically ran every utility I could think of to be sure that there were no bits and pieces left to irritate SU into killing my phone. Just to be on the safe side I reflashed the entire BLOX2 Core zip, then backed up the result with both Nandroid and TB. This was a couple days ago, and my phone seems content.
I know that the BLOX2 Core I am running is not technically a "custom" ROM, but it still runs noticeably more smoothly than the original. Right now Settings shows 3.6GB total Ram, with 2.1GB free, which means that it is using about 1.5GB with screen on but only background stuff running.
As to my laptop's refusal to see my phone, I think the problem is in my PC. I have had nothing but problems with SP Flash, ADB, and all the various Qualcom-related tools. I have tried QFIL, SN-Write, WRTool, and the like. Even MTK DroidTools gives a message that there is nothing connected to the computer, then freezes. Go figure.
One thing I've learned is that an OTG cable is a real nice thing to have & TWRP will recognize it with a simple click in storage. Put your downloads on a Stick--connect it to an OTG cable, plug it into the phone & you are set.
debianmain1 said:
One thing I've learned is that an OTG cable is a real nice thing to have & TWRP will recognize it with a simple click in storage. Put your downloads on a Stick--connect it to an OTG cable, plug it into the phone & you are set.
Click to expand...
Click to collapse
DOH!!!!!!
This little thing is so cool. Right now I am doing a Nandroid backup (via TWRP) and storing the backup on my USB drive.
I wondered what that funny little cable was.... It came with my BLU VIVO 5R, which I probably could have saved from the brick-yard if I had known what that little cable could let me do.
Thanks!
Augieboo said:
DOH!!!!!!
This little thing is so cool. Right now I am doing a Nandroid backup (via TWRP) and storing the backup on my USB drive.
I wondered what that funny little cable was.... It came with my BLU VIVO 5R, which I probably could have saved from the brick-yard if I had known what that little cable could let me do.
Thanks!
Click to expand...
Click to collapse
No prob...glad the info helps.
Does the mini use the same twrp as full phone?
I ordered a BLU Life ONE X2 Mini - 5.0" Unlocked Smartphone -4G LTE - 64GB + 4GB RAM -Grey.
So just googling for root and so far, won't have phone til next week, so no rush.
Thanks for any information.
debianmain1 said:
So, I think that it's a good time to start another thread about the One X2. I own an X2 Mini & am really liking it.
The first thing I can say is to BACKUP your install several times until you get root. MAKE SURE to include your boot.img as part of the backup.
1. Going thru unlocking the bootloader (easy), Installing TWRP (moderate) & Rooting (very frustrating) was an interesting experience. Unlocking the bootloader was by far the easiest I have ever done on any phone. Just enable developer options & tic the switch....That being said---the rest of the process was a PITA.
2. Installing TWRP was easy/moderate--having to do it twice & finding that the tool I used installed an early version that put everything upside-down was "interesting" but not really too difficult (I'm a linux guy, so a trip to the terminal & ADB fixed that without too much trouble).
3. Then came the Magisk install--that took a couple of days & quite a bit of help from forum members to get "sort-of" ironed out. There is protection on the boot/kernel that takes a bit of work to get in the right order to get root. With the Stock ROM you need to either run the AutoRoot script from BLOX2.com ( http://blox2.com/how-to-root-the-blu-life-one-x2/ ) or if you are terminal-savvy there are manual instructions also. I'm NOT a Windows guy, but tried the auto route first......That in retrospect was not the best way for the X2 Mini---the version of TWRP that it installs is early & upside-down so controls do not work. I got past that & found thru trial & error I needed to install Magisk 12.0 (via TWRP zip install) & MagiskManager 4.33 (with a APK Manager after reboot) FIRST. (as Ieatgravity pointed out...)
4. After you get to root this way you can just stay there (depends if you need SafetyNet or not) or get the more modern version of Magisk. As AlienTeck points out, you MUST install zips inside of TWRP due to the way the boot/kernel protection works. Installing inside of TWRP works outside of the booted system & gets the install done. You can't at present install inside of a running system without a reboot as soon as the kernel detects a system-wide change. This would prevent several "on-the-fly" root modifiers from working. I would hope someone will see the need to create a new boot.img & Kernel to side-step these issues.
5. There is only one custom ROM available right now---DRAX, & with my current experience, it seems to work MUCH better than the Stock ROM. It changes the spacing on-screen (for the better) & is debloated....definitely is faster/smoother than Stock.
Well---I'm not the FINAL authority on the X2/X2/Mini...there are several great people on the forum...I did this just to give a brief info list for people to look at without TOO much searching. You will find all the answers in the main thread----it just takes a bit of digging to get to them.
My hope is that this thread starts a "how-to" thread for people to refer to...And if I've miss-stated any info I've posted above, please feel free to correct me.
Click to expand...
Click to collapse
vampirefo said:
Does the mini use the same twrp as full phone?
I ordered a BLU Life ONE X2 Mini - 5.0" Unlocked Smartphone -4G LTE - 64GB + 4GB RAM -Grey.
So just googling for root and so far, won't have phone til next week, so no rush.
Thanks for any information.
Click to expand...
Click to collapse
Update
I see they use different twrps,.
vampirefo said:
Update
I see they use different twrps,.
Click to expand...
Click to collapse
You can get the Mini one on BLOX2.com
Just for anyone that can't find the TWRP for the Mini: https://drive.google.com/open?id=0B6h1RP64aWh0a1UyaUc2ZlNzQ1E
You guys are using very old roms join Yureka Black and tinno p7210 common group for new roms and discussions - http://t.me/yuyurekablack
Hello, This is a work in progress guide to help you with rooting your phone for whatever reason (i root it to use the Automate app as i am lazy)
I hope this is not a total mess, i will edit this if you have too much trouble reading
DISCLAIMER /!\
• Please consider that you follow this guide at your own risks, i am a random person in the internet, if you do not trust any part of this guide, dont follow it!
• I am adressing this guide to experimented users, i have probably missed a lot of steps and i will try to correct myself, (or not, it takes time sry)
• i am from Europe; not a native english speaker + a noob in the field. feel free to criticize, but be elaborate to help others
I did this on the GALAXY A53 5G phone with :
• Build ver. SP1A.210812.016.A536BXXU1AVCC
• One UI 4.1
• Android Version 12
The following is needed in order to speedrun this :
+MAGISK25.1
+LZ4
+ODIN3.14
+YOUR BOOT.IMG (FROM THE AP_ FILE OF THE FIRMWARE)
1) On your phone go to Settings -> About phone
2) Then -> Software info
3) Check at (the 6th line) ; BUILD Versionfor me it was:
SP1A.210812.016.A536BXXU1AVCC
4) You will have to download yours at sammobile or any other website you trust more : (needs an account but then is free to download)
Download Samsung Galaxy A53 5G SM-A536B firmware
Download the latest Samsung firmware for Galaxy A53 5G with model code SM-A536B. Check out our free download or super fast premium options.
www.sammobile.com
Then when you have you files , the one that matters is the one starting with AP_
5) extract the boot.img.lz4
6) download one of the versions of LZ4 from : https://github.com/lz4/lz4/releases
7) extract all files into a folder
8) drag and drop the extracted file from part 5) INTO the .exe file from part 7)
YOU HAVE YOUR BOOT.IMG
9) Now drag and drop this Boot.img INTO your phone
The version 25.1 of Magisk (or above is needed ? as i used that version of magisk to root my phone i guess)
10) Install it on your A53 you can download it from :
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
11) inside the app, click on INSTALL (written in blue on top right)
12) select the only option
13) go to the boot.img (that you dropped into your phone at part 9)
14) wait
15) when it is done, plug your phone again if you unplugged it and drop the new file generated by MAGISK into your computer and rename it boot.img.tar
Unlock the bootloader of your phone by either ;
• Watch a tutorial it helped me understand why i kept having an error while doing the next steps (i "unlocked" OEM only within dev options, that wasn't enough)
and skip to 22)
• Or follow these steps
on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
turn on the switch for OEM unlocking (wifi must be connected if the button doesnt appear)
and i am not sure if we need to but , turn on the switch for USB DEBUGGING as well (for adb)
16) stay pressed on both VOL UP + VOL DOWN
17) plug your phone to computer
18) wait
19) long press VOL UP
20) wait
21) press VOL UP
ez
So now get ODIN 3.14 on ur computer
I got the official website but cant remember where from, i will look into it, maybe you can find it on google but be carefull of malicious ones i swear !
(if you are kind enough you will share it below ♥)
22)after launching ODIN
23)The on the AP button put your boot.img.tar file that you got from part 15)
24) on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
25) check that you wave wifi connected
26) go to dev options and check if OEM unlock is grey'd out
30) turn OFF your A53 phone
wait for it to BZZZZZZZZ (viber)
31)STAY PRESSED onto the 2 buttons VOL UP + POWER
on recovery choose the 2nd option with your volume keys, "reboot to bootloader"
then if odin recognise the phone press start
This looks like a great guide. Too bad OEM Unlocking doesn't appear on US carrier phones, or else I'd totally do this :/
sorry if i sound stupid but how do i get the boot.img.lz4 file?
This does NOT work on VD7 or most likely later with Magisk 25.1/25.2 (the BL is unlocked on this SM-A536B as I get the warning on reboot and the OEM unlocked is on and greyed out in developer options).
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
I am now rooted with TWRP, thanks to this site, https://www.droidwin.com/install-twrp-recovery-and-root-samsung-galaxy-a53-5g/
Still cannot delete system/app, system/priv-app (not even in twrp) but am able to access data/app (and remove .digest and .dm files)
crazyut said:
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
Click to expand...
Click to collapse
Confirmed, works with VG1 and latest VGA. I used patched AP along with BL, CP and (Home) CSC. Please note that you have to do a factory reset after this, so remember to backup your data properly.
Hlo I rooted my a53 5g thanks to you but cannot remount system partition as read write
I get this output after running
Code:
mount -o remount,rw / <
'/dev/block/dm-0' is read-only
Please help me with it
And also cannot disable dm-verity flashed disable-dm-verity.zip but after formatting data device stuck in bootloop...
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
JoseAndDiezel104 said:
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
Click to expand...
Click to collapse
While I don't have a Galaxy A53, I can speak from experience that almost all Samsung phones suffer from the same pros and cons to rooting
Let's start with the pros:
Using a system-wide adblocker like Adaway is much more battery friendly and more effective using it on root mode than any non-root alternative. This one is the main reason a lot of people root and I think it merits it, it's a really amazing ad blocker.
You'd be able to activate some features that Samsung likes to disable on A-series, like full edge lighting and the camera privacy toggle (I don't know if it's disabled on A53 by default but I'm leaning towards yes)
You get to experiment with GSI and maybe some custom ROMs in the future
You can install some neat Magisk modules like the Pixelify module for example, that tricks Google Photos and lets you have unlimited space like the Pixels have.
With root, you have almost unlimited possibilities of modding your phone, it's just a matter of knowing what you want to modify and finding the right mods to it.
Now, the cons:
Samsung phones have an e-fuse. Flashing custom firmware automatically trips this fuse and it is impossible to recover from unless you change the motherboard. When this fuse is blown, you will never be able to use Samsung's security features like Samsung Pass, Pay, Secure Folder, Secure Wifi, etc...
Even if you flash your stock firmware and even if you re-lock your bootloader, the fuse will still be blown.
There are some regions which even deny any warranty claims if they find out that this fuse is blown, but some places in Europe still accept the phone in this condition.
Another con is that sometimes some apps refuse to work if they detect you are rooted like Google Pay and I believe Netflix and others too (like banking apps). Some are easy to fool/bypass root detection and some are more complicated. It all depends on the app.
And to answer your final question. Fortunately for you, you still should be able to flash the latest stock firmware and if you re-lock your bootloader, you should still be able to receive updates via OTA, just keep in mind of the services that will never work again I mentioned above
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
JoseAndDiezel104 said:
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
Click to expand...
Click to collapse
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
aryanrh said:
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
Click to expand...
Click to collapse
Would this work for US phones?
nsfxpython said:
Would this work for US phones?
Click to expand...
Click to collapse
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
crazyut said:
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
Click to expand...
Click to collapse
Is there any way to recover deleted pictures in the Samsung A53 5G (USA version) if it is impossible to root this version of the phone?
I accidentially manually deleted some photos in my phone today with my computer (so it doesn't appear in the photo's trash bin), and every single recovery program I encountered says I need to root my phone in order to use a deep scan to look for the deleted files.
I have litte hope that there is anything to recover. Despite the fact that us versions can't be unlocked what would be necessary for rooting, flash storage management (also garbage collection, trim etc.) tends to shift data all the time to other/new cells making it unlikely for you to recover lost data on an active device. Better backup from time to time, always your best bet.
Hello! Im having an issue, maybe im doing somthing wrong. I'm at 13) After giving the img.boot.lz4 i wait and wait and the memory of the phone fills completly (Around 120+Gb) and the patched img do not comes out, any thougths?
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Andoreid said:
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Click to expand...
Click to collapse
That's right, but for folks with no experience rooting new Samsung devices, please:
- DO read OP's "Unlock bootloader" section. Visitors to this page who skip to the end and have never rooted non-Samsung or older devices might think "adb reboot fastboot" followed by "fastboot flashing unlock" or "fastboot oem unlock" will do the trick. It won't. To clarify: fastboot will NOT recognize this phone, which is normal because it doesn't have a standard fastboot mode, and simply enabling "Allow OEM unlock" in developer settings is necessary but not enough.
Do follow OP's steps for unlocking.
- For rooting, I followed the instructions here https://samsungusbdriver.me/root-samsung-galaxy-a53-5g/ (second method).
But the instructions on that page for getting the actual model number and CSC for Frija are unclear. Finding that information was not straightforward. Depending on the method I used, the model number would be SEPF_SM-A536B_12_0001, SM-A536B/DS, A536B... and you need to know CSC stands for "country-specific code" and it's a 3-character code. I eventually figured out my model was SM-A536B and CSC was EUX. But it took quite a bit of research.
-If you're not familiar with Magisk's DenyList, google it. You might have to use it some apps, particularly banking apps. I think you need it for Netflix, too. Speaking of Netflix, the version that comes preinstalled won't work after rooting. The way I got it to work was uninstalling that version and sideloading the Netflix APK from Apkpure. And adding it to Magisk's DenyList.
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.