Related
* WARNING: WE DO NOT HAVE A FASTBOOT TO FIX YOUR PHONE SHOULD YOU BOOTLOOP AND BE UNABLE TO ENTER RECOVERY **
** YOU INSTALL AND USE THIS SOFTWARE AT YOUR OWN RISK **
Want to freeze some bloatware or make changes to your System but are nervous because we don't have a fastboot restore?
Interested in a stock ROM to safely deodex and test?
Safestrap *MAY* be the answer you're looking for. Read more about it here:
http://hash-of-codes.blogspot.com/p/how-to-safestrap_24.html
Here is a link to a *SAFESTRAP ONLY* Stock ROM for the Droid 4: 6.13.215:
http://bit.ly/y6FEjv
md5sum: c19d09fe0db646a8916985c1e672eee5
Install this in Safestrap after ENABLING Safe Mode, and as long as you keep it enabled while running your phone, if you make a mistake by freezing too much or if you're deodexing and hit a bootloop, you won't be screwed.
Because Safe Mode is enabled, you should be able to get back into recovery to restore a backup or reflash this ROM so that you can boot back up.
What it contains:
- MotoBlur for Droid 4 (6.13.215)
- A few of the obvious bloatware have been removed: Netflix, NFL TV, Slacker Radio, etc.
- Pre-rooted with Superuser
To Install:
1. Be rooted
2. Install the APK for Droid 4 Safestrap found here (BE SURE YOU'RE GETTING THE DROID 4 VERSION):
http://hash-of-codes.blogspot.com/p/android-downloads_24.html
3. Once installed open up the application and use "Install Recovery"
4. Make sure you have this .zip on your SD card
5. Reboot the phone and enter Safestrap Recovery by pressing the [menu] button while the Safestrap boot screen is displayed
6. - MAKE A FULL BACKUP OF YOUR NON-SAFE SYSTEM FOR DISASTER RECOVERY BY CHOOSING (FUNCTIONS SIMILAR TO CWRecovery)
- Controls in recovery are: scroll up = volume up button, scroll down = volume down button, select = power button
- Scroll down and select "backup and restore"
- in the "Nandroid" menu choose "Backup"
- Optionally include webtop in the backup (probably want a 1 for the full backup)
- Confirm
This will take a while ... so be patient.
- Once that's done you can use the [back] soft key on the front of the phone or scroll down to "+++++Go Back+++++" and use that to go back to the main menu
7. Now that we made a full backup, we can turn on Safe System, scroll down to "safe boot menu" and select
8. Select "Toggle Safe System"
This will also take a few moments while your main /data was stashed away.
9. Now that we have Safe System "Currently: ENABLED" (should see this at the top of the screen), we can flash a ROM
10. Make sure you're on the main menu, and scroll to "install zip from sdcard" and select
11. select "choose zip from sdcard"
12. choose whether you have the file on your internal or external SD card
13. now using the scroll and select buttons, navigate to your .zip file and select it
13. confirm that you want to install the ROM.
This will take another little bit.
Now exit Safestrap by going back to the main menu and select "reboot system now".
The phone should reboot right back into your 2nd version of the Stock MotoBlur system.
Enjoy.
Reserved for future use
Thank you thank you thank you!!! I almost gave up on the D4!! wooooOOOOOoooo
Hash,
I can flash this with no problem, but just like everything else i try to flash when safe mode is enabled, it hangs on the off black screen after booting. Any other ways I can try this?
**Edit** Got it working. I was actually trying to deodex a few files and add afew touches to your base, so I guess I did not recompile it correctly. Gonna try again.
reigndropz said:
Hash,
I can flash this with no problem, but just like everything else i try to flash when safe mode is enabled, it hangs on the off black screen after booting. Any other ways I can try this?
**Edit** Got it working. I was actually trying to deodex a few files and add afew touches to your base, so I guess I did not recompile it correctly. Gonna try again.
Click to expand...
Click to collapse
Keep at it, we'll need deodexed files.
Also, I updated the ROM tonight. I had left some cheesecake files in which were pointing users to a motoblur-dev OTA server.
Please re-download when you can, so we don't distribute a deodexed ROM with that info in it.
Does anybody have a .219 safestrap ROM?
[edit]
Never mind. I just tar'd over the .219 files from /system onto /preinstall, to overwrite my "safe" install.
I've attached the list of files the 219 update replaced. To use it:
Install the 215 ROM into your safe system, then toggle back to Unsafe mode.
Then in a root shell:
Code:
cd /system; tar cf - `cat 219.txt` | (cd /preinstall; tar xf - )
Then when you toggle back to your Safe system it will be running the identical 219 software as your original system.
One for ICS
Im looking for a stock ICS rom that I can flash to safestrap. I did a search, but I'm leary of flashing anything that im not 100% sure is the right one.
zeroktal said:
Im looking for a stock ICS rom that I can flash to safestrap. I did a search, but I'm leary of flashing anything that im not 100% sure is the right one.
Click to expand...
Click to collapse
if you need it for GSM network, try flashing my rom (olegfusion cleaned rom thread)
Hoping to get google now to run
hello well first off i just finished troubleshooting the **** out of my phone and i see lots of others are having issues as well and its all scattered. so i am going to post my method which should get you updated with MT's AIO which also includes a fix for those who are having permission problems with the AIO.
(this is optional and for those who were having problems with permission errors using AIO on GV 2.0) (skip below for first step of getting to zv7)
first off the main thing that I figured out is that if you are on GV2.0 the kernel by default (at least for me) disables logcat which gives many problems with MT's AIO solution with the error cannot open dev/log/main with all the permission problems with rooting / unrooting on GV2.0. So for those who are having that issue here is the fix:
open root explorer
go into /system/etc/init.d/12gvtw
long click then open up text editor
go to where it says rm /dev/log/main and change it to
#rm /dev/log/main
then save and then reboot which should fix the permissions errors.
now doing that enabled me to be able to have success with the AIO to prepare for the update to zv8 while on GV 2.0 ...
but then I ran into another problem after that was that the OTA update would fail. most likely because the boot.img was not stock (this is just a guess, probably other reasons as well)
----------------------
but what worked for me was going completely stock gingerbread.
so for this fix I simply went to this thread to get completely to stock zv7
http://forum.xda-developers.com/showthread.php?t=1348637
I then downloaded the nandroid and followed MT's instructions steps 1-6
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
3.) I recommend to wipe data to prevent any problems
I want to emphasize that you SHOULD WIPE DATA NOW AT THIS STEP IN CWM BEFORE IT GETS TO STOCK RECOVERY.
4.) Go to install zip from sdcard
5.) Select RevoZV7GBStock.zip
6.) Reboot
then after that my phone booted up completely stock (with stock boot.img) and wiped data with root still enabled.
then I went to this thread to get MT's AIO zv8 and followed the steps 1-5 (steps 6 and 7 will be completed later)
http://forum.xda-developers.com/showthread.php?t=1566729
1) Download zip and extract
2) Install drivers if not already installed
3) Make sure you are on stock ZV7
4) Click Root&RecoveryAIO.bat
5) Select "Prepare for Update"
then the phone rebooted and was at stock recovery and unrooted and was completely stock but with the added the data/local.prop edits.
so then I went to this thread to download Broken Out Rom from my computer and followed steps 1-2 (steps 3-9 will be completed later) before i completed the AIO process steps 6-7 stated earlier.
http://forum.xda-developers.com/showthread.php?t=1577423
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
So now you should have your phone completely unrooted with stock recovery with Broken Out Rom downloaded on your phone's sd card (not installed yet).
You are now ready to go to get the OTA update. (step 6)
go to settings > about phone > software update > check new
then you should have the OTA update successfully installed when it reboots.
you now have zv8 installed with no root or cwm.
then i went to MT's AIO for zv8 and clicked option 7 which is too root zv8.
then the phone gave me an error on AIO when trying to root but then CWM still got installed at the end of the AIO process.
so the phone then booted up with no root but CWM was installed but could not get into recovery mode using quickboot to recovery option on the phone due to no root access..
for this fix I then opened up MT's AIO for zv7 found here under step 2 of "How do I completely Return to Stock"
http://forum.xda-developers.com/showthread.php?t=1348637
and then clicked option 7 which is reboot recovery. this booted my phone into recovery.
then I went to continue the process of installing Broken Out Rom (steps 3 and 4 are skipped because we already wiped data initially above)
5.) Go to install zip from sdcard
6.) Select BrokenOutRevo1.1.zip
7.) Do not wipe data after flashing!!!
8.) Reboot!
9.) To Block CIQ Logs Requires Reboot After Initial Boot
You should now have a fully rooted zv8 phone with CWM and can give yourself a pat on the back.
if i forgot to mention things please let me know. this was just my process which worked after much troubleshooting so i thought i'd share it with you all.
My method
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
LeadPharmer said:
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
Click to expand...
Click to collapse
Looks good.. although if you did step 1 using LGNPST you don't need step 3. The .tot contains the stock recovery.
I had every problem you could think of (all problems liste here) and this is my method that finally worked:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Factory reset, just in case
3 - Using the OLD AIO (Root&RecoveryAIO), root it (option 1 only!).
4 - Use Check Root app to make sure you have root
5 - Use fileslick app to Change folder permissions and move local.prop file app to
- Open fileslick, click actions, and click show root
- Swipe all the way left until you are at root and see /data folder
- Tap the data folder so it has a green check and then hit actions and select "permisions"
- Check everything in that menu (This will make it so you don't has any permission denied menus when moving the local.prop)
- Put the local.prop file from the "data" folder in the ZV7toZV8Root.zip by tapping it in fileslick, navigating back to the "/data" folder you just set permissions for, clicking "actions" and clicking "copy file to this location"
6 - Go to about this phone in the settings app and check for updates to update ZV8
7 - After reboot use ZV8CWMRecovery.bat (option 1) to install clockwork
8 - After reboot go back and use OLD AIO (Root&RecoveryAIO) to reboot to recovery (option 7)
9 - Reboot recovery and wipe data
10 - After wiping data and without exiting CWM, flash BrokenOut.
11 - DON'T WIPE DATA AFTER FLASH
This guide is for fellow at&t customers who will be stuck with JB 4.1.2 forever because there won't be an official 4.3 release (and any new Sony phones until at least the next year).
WARNING: You may lose some of your contacts if you don't follow this guide!
DISCLAIMER: I'm not responsible for bricked devices and data loss from power surges, hardware damage, or changes to the linked software. Always check the native manuals for all the tools listed here!
What You Will Lose:
All at&t branding
at&t address book (see below how to save contacts)
at&t emergency numbers dialer
Stable LTE connection (you'll see the H+ icon often in places with weak signal)
NFC icon
What You Will Gain:
Clean ROM with all stock Sony apps
All the new JB 4.3 features
Sony's new camera app with plugins
Significant improvement in battery life if your phone barely survives a day
What You Will Keep:
All of your contacts and data
James Bond themes
Root access
Recovery
Required Downloads:
1. Flashtool (got questions about it? - ask them here) - requires installation
2. @[NUT]'s dual XZDualRecovery. I'm linking to v2.7.94 BETA installer. If you wish to check for a more recent version, go to his download page and do a page search (CTRL+F) for XT-lockeddualrecovery[version-goes-here].installer.zip. (got questions about it? - ask them here) - unzip to a location you'll remember (say, C:\xperia-upgrade\recovery\)
3. @amarullz's AROMA File Manager - current version can be found at the bottom of the 2nd post - don't do anything to the zip
4. @DaRk-L0rD's Ultimate PureXT ROM and all patches and/or add-ons from the 2nd post you'd like (got questions about it? - ask them here) - don't do anything to the zip, save it to a location you'll remember (say, C:\xperia-upgrade\ROM\)
4.1 There might be additional files needed for the ROM, such as SuperSU update. They will be mentioned in the post. Download them to the same location as the ROM (e.g., C:\xperia-upgrade\ROM\).
5. at&t baseband FTF (attached) - unzip it to the default Flashtool firmware directory (C:\flashtool\firmwares\)
The Guide (assuming your phone is running at&t's 4.1.2 (9.1.F.1.120):
1. Backup any contacts saved in at&t address book or make sure there are none.
1.1 Open the stock Contacts app.
1.2 Tap the filter icon on the left.
{
"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"
}
1.3 Make sure that the two checkboxes are blank.
1.4 Go through every single connected account EXCEPT for AT&T Address Book and uncheck them (there might be a few), then tap OK.
1.5 Tap the menu button, then Back up contacts.
1.6 Select SD card.
1.7 You don't need to remember the location of the vcf file - the system will recognize it on its own.
2. If USB debugging isn't enabled yet, you need to do it.
2.1 Go to (System) Settings -> Developer options and flip the switch in the top-right corner of the screen.
2.2 Look a bit down (toward the middle of the screen) and check USB debugging.
3. Connect your phone to the computer and let the computer recognize it.
4. Copy AROMA Filemanager to the SD card
4.1 Go to the location on your computer where you saved aromafm.zip and copy the file (select, then CTRL+C).
4.2 Navigate to your SD card (not internal storage) and create a folder called clockworkmod.
4.3 Open the new folder and create another folder inside it called aromafm.
4.4 Open that folder and paste the zip (CTRL+V).
5. Copy the ROM and all of the files required for it to the SD card.
5.1 Go to the location on your computer where you saved the ROM zip with all other required files and copy the files (select, then CTRL+C).
5.2 Navigate to your SD card (not internal storage) and create a folder called 00-install (such a name keeps it on the top of the content list in Linux).
5.4 Open that folder and paste the zips (CTRL+V).6. Install the dual recovery.
6.1 Go to the location on your computer where you extracted dual recovery (e.g., C:\xperia-upgrade\recovery\).
6.2 Double-click install.bat.
6.3 Press 3 on your keyboard for the option 3. Installation on unrooted ROM.
6.4 Follow the instructions on your computer's screen.
6.5 When you will try to reboot the phone back into Android, the recovery will prompt you to root the OS. Do that.
7. Backup old system and install the new ROM (YOU MUST DO THIS!!!) - if you skip this and have issues, later, I'm not responsible
7.1 Initiate the reboot sequence by holding POWER + VOLUME UP for a few seconds.
7.2 Once you see SONY logo, start pressing VOLUME UP to enter clockworkmod recovery.
7.3 Connect the phone to a power outlet.
7.4 Tap Backup and Restore
7.5 Tap Backup to /storage/sdcard1 and confirm. The process can take up to 10-15 minutes depending on the amount of data in your internal storage.
7.6 When backup is complete, tap the Back button (2nd from the right) to go to the main menu.
7.7 Tap Wipe Cache Partition (4th from the top) and confirm the operation.
7.8 Tap Back button (2nd from the right) to go to the main menu.
7.9 Tap Advanced (3rd from the bottom), then Wipe Dalvik Cache (1st from the top) and confirm the operation.
7.10 Tap Back button to go to the main menu.
7.11 Tap Install Zip (2nd from the top), then Choose zip from /storage/sdcard1, then select the folder 00-install, then the ROM file, and confirm the operation. If you receive Status 7 error message, leave the phone as is, scroll down to the troubleshooting section to restore the backup and fix it.
7.12 Repeat step 7.11 for all the files that need to be installed.
7.13 When you are done, select Reboot System Now in the main menu. It may take good 20 minutes for the system to perform all operations needed for the first start.
8. If the phone doesn't pick up LTE signal, you need to re-flash the at&t baseband.
8.1 Turn off the phone.
8.2 Start Flashtool from your Start menu.
8.3 Click the flash icon, select Flashmode (default), and click OK.
8.4 In the list of firmware select the one you've downloaded (if this is your first time flashing, it'll be the only one for LT30) and make sure that No final verification is checked. Then click Flash.
8.5 When prompted, hold the VOLUME DOWN button, and connect the phone to the computer. The operation will take about 10-15 seconds. DISREGARD THE INSTRUCTIONS IN THE ANIMATION. Xperia T/TL doesn't have a hardware Back button.
8.6 Boot the phone.
8.7 Sometimes the phone will still lose LTE signal and show H+. You can reconnect to LTE by putting the phone into Airplane mode for a couple of seconds and then turning the Airplane mode off. If that doesn't help, open dialer, type *#*#4636#*#* to get into Testing service menu. There, you need to tap Phone information and scroll all the way to the bottom where you'll see a selector with the label Set preferred network type. Pick the flavor of LTE and downgrade that you'd like and watch the connection be re-established. Unfortunately, through experimentation, I've discovered that every ROM keeps its regional baseband regardless of flashing method (even overwriting with NAM bands will only enable LTE reception but the baseband property stays the same).
9. Battery fix if your battery dies within 9-10 hours of use.
Apparently, in some areas at&t doesn't support a network feature called fast dormancy (it allows for somewhat faster reconnection to the data network after idling). Some apps aren't written properly and keep on pinging Sony's FD service to connect, which results in thousands of wakeup alarms and the phone never entering deep sleep. You can notice this if Android OS is your top battery hog in standard battery usage stats (com.sonyericsson.android.wakeup is the service name). Before applying this fix, check your battery drain using BetterBatteryStats or Wakelock Detector. If you see what I've described, this will help you increase your battery life by at least a couple of hours (for me, it almost doubled).
There's one downside though: the last 10-15% of battery charging take much longer (my battery now charges over 3+ hours).
Huge thanks to @mirhl for writing the original guide.
1. Install some root-capable file browser (I prefer ES File Explorer for being free).
2. Grant it root access (in ESFE, tap the top-left corner to open the navigation sidebar, scroll down to Tools, tap it to expand, scroll down to Root Explorer, and tap the switch).
3. Mount /system as R/W (in ESFE, get to Root Explorer as above, but instead of the switch tap the tile itself, then tap Mount R/W, and move the radio button next to /system into R/W column).
4. Navigate and open /etc/fast-dormancy/fd_custm_conf.txt (ESFE has a built-in text editor but editing needs to be enabled through the top-right menu.
5. In the file, you'll see two lines ending with MCC and MNC and a zero next to each. Change the zeros to 310 (MCC) and 410 (MNC), save the file, and reboot the phone. That should take care of it.
IF SOMETHING WENT WRONG
1. There shouldn't be any issues until you complete 7.6 (phone backup).
2. You better have followed this guide and created a complete backup of the working setup.
Bricked phones (something went wrong and you turned off your phone and now it doesn't boot)
1. Download a 4.1.2 FTF file from this master list to C:\flashtool\firmwares\.
2. Remove the SD card from the phone just in case.
3. Follow the instructions in the master list on how to flash the firmware.
4. Insert the SD card back into the phone.
5. Repeat steps 2, 3, and 6 of the guide above to install recovery.
6. Boot into clockworkmod (7.3 above), navigate to Backup and Restore, then Restore from /storage/sdcard1 and select the appropriate backup. This will get you up to step 7.6 and you can try the guide again.
Status 7 error message when flashing a ROM
After some experimentation, I noticed that some rooting methods are the culprit. You need to unroot your phone (don't worry recovery installer will work either way and will reroot it safely). Just download this Xperia rooting script, connect your phone with Debugging access enabled, run the script, and select the appropriate option (unroot). When it's done and the phone reboots, reinstall recovery (it will prompt you at one point to root the device), and continue to 7.7.
Huge thanks to all the devs who have built the tools!
Changelog
Code:
v2 - Apr 1, 2014 - Added extensive troubleshooting & battery fix; formatting changes
v1 - Mar 26, 2014 - Original publish
I've linked your guide to my list: http://forum.xda-developers.com/showthread.php?p=50323041#post50323041
I think it will make many AT&T users happy
Nice one
I didn't do that at all due using Ubuntu, I download flash tool, I used the bell firmware didn't exclude baseband (they use the same bands plus h+42 for T-Mobile in case this phone has it). Rooted it and added a recovery, flashed a 4.3 ROM by our doomlord and flashed superuser update thus 4.3 no bloat and got LTE working on T-Mobile
Sent from Sauwny the TL
Durteedee said:
I didn't do that at all due using Ubuntu, I download flash tool, I used the bell firmware didn't exclude baseband (they use the same bands plus h+42 for T-Mobile in case this phone has it). Rooted it and added a recovery, flashed a 4.3 ROM by our doomlord and flashed superuser update thus 4.3 no bloat and got LTE working on T-Mobile
Sent from Sauwny the TL
Click to expand...
Click to collapse
Which rooting script did you use? I couldn't find a working one so I had to wait for a good flashable release. How's the battery life on Bell firmware?
bsined said:
Which rooting script did you use? I couldn't find a working one so I had to wait for a good flashable release. How's the battery life on Bell firmware?
Click to expand...
Click to collapse
I used the one that came with the flash tool 4.1.2 only, battery life wouldn't know it was only on the bell firmware for about 30 mins at most before flashing doomlords 4.3 ROM
Sent from Sauwny the TL
Durteedee said:
I used the one that came with the flash tool 4.1.2 only, battery life wouldn't know it was only on the bell firmware for about 30 mins at most before flashing doomlords 4.3 ROM
Sent from Sauwny the TL
Click to expand...
Click to collapse
That's strange. I've tried every single root method in Flashtool and none of them worked on 4.3.
Link to doomlord's ROM (I found only his 9.2.A.0.278 release)?
bsined said:
That's strange. I've tried every single root method in Flashtool and none of them worked on 4.3.
Link to doomlord's ROM (I found only his 9.2.A.0.278 release)?
Click to expand...
Click to collapse
Because I rooted bell 4.1.2, 4.3 can't be rooted yet without an unlocked bootloader
Sent from Sauwny the TL
Thanks for this. Its been a long time since I've upgraded, came from XperimenT 3.5, and I wasn't sure where to start reading first. I'm curious though. Do you know if the cpu control is working for us locked bootloaders?
Also, do you know how to get rid of this "close all x" button at the bottom of the recent apps list? It covers the bottom ago in the list. Plus I like the one in the top corner thats enabled by gravity box. I'm not sure how it even turned on. I don't remember it being there at first. Even disabling all the xposed modules doesn't remove it.
- Xperia TL, Ultimate PureXT v2 ~ via XDA App
redincali said:
Thanks for this. Its been a long time since I've upgraded, came from XperimenT 3.5, and I wasn't sure where to start reading first. I'm curious though. Do you know if the cpu control is working for us locked bootloaders?
Also, do you know how to get rid of this "close all x" button at the bottom of the recent apps list? It covers the bottom ago in the list. Plus I like the one in the top corner thats enabled by gravity box. I'm not sure how it even turned on. I don't remember it being there at first. Even disabling all the xposed modules doesn't remove it.
- Xperia TL, Ultimate PureXT v2 ~ via XDA App
Click to expand...
Click to collapse
- Judging by the CPU states reported in BBS, governor changes are working. Though I'm also using CPU Tuner for automatic downthrottling.
- "Close all X" is a part of the ported Z2 UI. There's a request to remove it in the ROM thread.
How did you root? is it the dual recovery that does that? or another method. Just asking as I understand that rooting the AT&T TL is extremely hard.
Happy-J said:
How did you root? is it the dual recovery that does that? or another method. Just asking as I understand that rooting the AT&T TL is extremely hard.
Click to expand...
Click to collapse
Dual recovery will prompt you to root the phone on reboot during installation and the new ROM retains root access. However, rooting 4.1.2 on its own was very easy, too - the scripts provided on the forums work flawlessly.
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Happy-J said:
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Click to expand...
Click to collapse
Yes its what I used for my att TL
Sent from Sauwny the TL
Thank you for your help, I think I'll be installing this very soon!
Happy-J said:
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Click to expand...
Click to collapse
FYI: the install might fail if the phone is rooted by a method other than the one included with recovery. If that's the case, see the bottom of the guide for troubleshooting - just don't forget to backup your existing setup before trying to flash.
bsined said:
FYI: the install might fail if the phone is rooted by a method other than the one included with recovery. If that's the case, see the bottom of the guide for troubleshooting - just don't forget to backup your existing setup before trying to flash.
Click to expand...
Click to collapse
Ok, I will keep that in mind when I start the installation, and just use the recovery's root. Thanks for the tip.
I can't seem to get into recovery. I have tried pressing volume up at said time, and long pressing, but no dice. Can anyone offer assistance?
Happy-J said:
I can't seem to get into recovery. I have tried pressing volume up at said time, and long pressing, but no dice. Can anyone offer assistance?
Click to expand...
Click to collapse
Did the phone boot into recovery during installation? If not, you need to reinstall it. If yes, there's now a new app called NDR Utilities - use it to boot into PhillZ Recovery. Otherwise, please ask the recovery script author.
No, the phone did not boot recovery any of the times I reinstalled it, which was about 5. I am going to try flashing back to stock and try it again. Thanks for the helping hand again, very much appreciated.
---------- Post added at 01:07 PM ---------- Previous post was at 12:59 PM ----------
OK, a clean flash of the stock firmware did the trick. Thanks again for the help.
Twrp Backup Process Steps:
1. Download TWRP.7z
2. Unzip Twrp with 7zip program then make sure the pathway looks like this D:\TWRP\BACKUPS\LGMP26016c6f013\2016-12-31--20-18-59_NRD90U basically put it on the root of the sdcard or if you don't have one just connect phone in twrp mode by putting it on mtp and put it on the root of your internal storage and then go to restore in twrp
TWRP BACKUP Contains:
1. UI, Ringtones, Notification Sound Changes (Apple Sounds & Emojis iOS 10.2)
2. Boot Animation Is Google
3. Google Assistant Added As Well As The Pixel Launcher And Other Features
4. Removed Most Bloatware And Some Other Apps
6. For Those That Have That Message When You Download Supersu App And Says Root Not Detected or Something Like That Download These Two Files To Properly Install Root On It https://mega.nz/#!tYlyGQKS!F2UEnS-Sy1_Z16tbY20RZvIhU12r3tT2flc0HX6HZnY https://mega.nz/#!hY1hXKBa!DBDSmqNTE3FJBp1yiIqEAm9yv37f0B1vuzZEq4mYEhY
7. Install UPDATE-unSU-signed.zip first then reboot system to check if it boots normally after that just take the battery out put it back in and hold the power button and volume down and wait for the lg logo and release power button and hold it again and install SR5-SuperSU-v2.78-SR5-20161130091551.zip and then you have root!
5. Let Me Know What You Think I Wish I Could Have Made A ROM But I Need System.img
Details: When You Are Done Going Through The Setup Hold The Screen or Go To Settings To Change Launcher To Pixel & To See All The Emojis With The Color Support Download Gboard From The Play Store
Twrp Link: https://mega.nz/#!IEEHiTQJ!T__o91ZFLIY4X46ZBQMIDf41yPMxSwk4_wzJqwR0YxE
Will this work for the T-Mobile variant of the LG K20 Plus?
iiphanaticx said:
Will this work for the T-Mobile variant of the LG K20 Plus?
Click to expand...
Click to collapse
I Mean It Definitely Would Restore On Your Device However Your Data Connection Wouldn't Work Because It's A Metro Modem Flashed Instead Of T-Mobile
What kind of apps were removed? and can I go back to normal if I dont want this backup anymore? will it erase all my data?
my worthless T-mobile one refuses to enter recovery
wont work too vague
the 2nd step is too vague. Iam trying to follow step to but it isn't very specific. can you explain it with a little more detail. please
System image
TheAmbition215 said:
Twrp Backup Process Steps:
1. Download TWRP.7z
2. Unzip Twrp with 7zip program then make sure the pathway looks like this D:\TWRP\BACKUPS\LGMP26016c6f013\2016-12-31--20-18-59_NRD90U basically put it on the root of the sdcard or if you don't have one just connect phone in twrp mode by putting it on mtp and put it on the root of your internal storage and then go to restore in twrp
TWRP BACKUP Contains:
1. UI, Ringtones, Notification Sound Changes (Apple Sounds & Emojis iOS 10.2)
2. Boot Animation Is Google
3. Google Assistant Added As Well As The Pixel Launcher And Other Features
4. Removed Most Bloatware And Some Other Apps
6. For Those That Have That Message When You Download Supersu App And Says Root Not Detected or Something Like That Download These Two Files To Properly Install Root On It https://mega.nz/#!tYlyGQKS!F2UEnS-Sy1_Z16tbY20RZvIhU12r3tT2flc0HX6HZnY https://mega.nz/#!hY1hXKBa!DBDSmqNTE3FJBp1yiIqEAm9yv37f0B1vuzZEq4mYEhY
7. Install UPDATE-unSU-signed.zip first then reboot system to check if it boots normally after that just take the battery out put it back in and hold the power button and volume down and wait for the lg logo and release power button and hold it again and install SR5-SuperSU-v2.78-SR5-20161130091551.zip and then you have root!
5. Let Me Know What You Think I Wish I Could Have Made A ROM But I Need System.img
Details: When You Are Done Going Through The Setup Hold The Screen or Go To Settings To Change Launcher To Pixel & To See All The Emojis With The Color Support Download Gboard From The Play Store
Twrp Link: https://mega.nz/#!IEEHiTQJ!T__o91ZFLIY4X46ZBQMIDf41yPMxSwk4_wzJqwR0YxE
Click to expand...
Click to collapse
I did a full system backup with twrp would it help if I gave that to you for rom building
I can try
Thomas080808 said:
I did a full system backup with twrp would it help if I gave that to you for rom building
Click to expand...
Click to collapse
I have built a stock rooted rom, but it will not complete the initial setup. Its as if there is no data when it shows 4g lte of wifi, strange.
And what about sim lock? Is this ROM unlocked?
arcos said:
And what about sim lock? Is this ROM unlocked?
Click to expand...
Click to collapse
Your asking 2 questions thinking they are related. The rom is unlocked meaning you can change it if there was a rom for it bootloader is unlocked so tou can modify the recovery bit sim lock is another thing they are not related in any way shape or form. If tour asking id it can be sim unlocked then yes it can be but that proceas is not like flashing a new rom to make that part work sim unlocking would work on the ohone on stock or not that just depends on who you got the phone feom like tmobile or metro tjey have presequets on how to sim unlock or you pay someone to do it for you
So in other words just because you have custom recoveey or rom or not sim unlocking is another process that has nothing to do with the phone being stock or not if that makes any sense
Thanks for the answer. Do you know how or who can remove sim lock from a K20 Plus? The original network is MetroPCS.
arcos said:
Thanks for the answer. Do you know how or who can remove sim lock from a K20 Plus? The original network is MetroPCS.
Click to expand...
Click to collapse
Yes you can either pay for it now or wait the 3 months or so and metro unlocking app will do it free the option is yours
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
Esin8785 said:
Yes you can either pay for it now or wait the 3 months or so and metro unlocking app will do it free the option is yours
Click to expand...
Click to collapse
Herea metropcs sim unlock policy 90 days of active aervice amd they will unlock free if not then you need to find someone on the net or here on xda and pay for someone to unlock to for you
https://www.metropcs.com/terms-conditions/phone-unlock-policy.html
Has this worked for anyone? I tried it, I extracted the TWRP folder and all its contents on the sdcard went into restore (in twrp) but nothing was found.
New Optimus said:
Has this worked for anyone? I tried it, I extracted the TWRP folder and all its contents on the sdcard went into restore (in twrp) but nothing was found.
Click to expand...
Click to collapse
Backups need to be i in twrp/Backups/LGxxxxxxxxxx (model/serial of phone) folder for twrp to see them, not on root of sd card.
If you haven't made a twrp backup, just do a backup of boot to create the proper folder and copy the 2016-12-31--20-18-59_NRD90U folder from the downloaded zip into it.
Thanks, now I am having another issue, I think I can resolve it I can't get twrp to mount /system rw so restoring backups is failing.
Is anyone else having this problem? What I did to fix it was open terminal in twrp, and type "mount -o rw,remount,rw /system" which seems to have worked, this was after installing the no-verify and a SU
New Optimus said:
Thanks, now I am having another issue, I think I can resolve it I can't get twrp to mount /system rw so restoring backups is failing.
Is anyone else having this problem? What I did to fix it was open terminal in twrp, and type "mount -o rw,remount,rw /system" which seems to have worked, this was after installing the no-verify and a SU
Click to expand...
Click to collapse
You have to create a new backup folder , containing only one item. And then take the file that you have of all your real backups , and put it in that spot , if ur backup location is SD card , then this can easily be done useing Sun 3.0 micro SD card reader , or other method. The TWRP will see the file then. If ur backup is in internal memory , u just do the same thing. Useing minimal adb and fastboot (fromXDA). Otherwise TWRP will not see the backup file. There r a couple of videos on Utube as well , that cover this process.
williamacker77 said:
You have to create a new backup folder , containing only one item. And then take the file that you have of all your real backups , and put it in that spot , if ur backup location is SD card , then this can easily be done useing Sun 3.0 micro SD card reader , or other method. The TWRP will see the file then. If ur backup is in internal memory , u just do the same thing. Useing minimal adb and fastboot (fromXDA). Otherwise TWRP will not see the backup file. There r a couple of videos on Utube as well , that cover this process.
Click to expand...
Click to collapse
Yes did that, got that sorted, thank you, I was asking specifically about if anyone else had system that was Read Only, would not allow Read write.
Is this based on a stock Google rom? I'm about to be getting this phone tomorrow through Metro, but I hate the LG UX UI and would rather it be vanilla Android 7.
Worked for mine but xposed makes it boot loop...
Was not comfortable exposing TWRP, Rooted phone without encryption. Averge Joe who knows TWRP can easily get into my phone. I also needed Verizon VoLTE which requires TWRP/Root. hence the research and results of the guide below.
Should applicable equally to S7/S8/N8
All instructions were taken from following threads.
N935F TWRP
S7 Encryption
Verizon CSC VoLTE
S7 CSC Selection
Start with a stock N935F/DS XME CSC and Verizon Sim Card already activated and provisioned for VoLTE
Although N935F/DS does not support CDMA, it does have all verizon LTE, can be used fully with VoLTE enabled
Basic Setup -- enable optional encryption
0. Copy files extracted from TWRP_Root.zip (attached) into SD card. insert SD card with Verizon Sim Card. Download TWRP image from N935F TWRP
1. Ensure RMM is not enabled
-- boot to download mode (vol down+home+power), if "RMM State: Prenormal", then you need keep phone on, connect to internet, wait for 168 hrs
2. If already on Stock ROM then skip to 3 below, otherise
-- Flash via ODIN Stock Rom, in ODIN, turn off auto-reboot, use CSC not HOME_CSC.
-- when finished, push vol. down+home+power until screen turns black
-- right when screen turns black, immediately re-push and hold vol. down+home+power again to get into download mode again
-- this is to avoid reboot the phone and potentially trigger RMM again
3. Flash via ODIN TWRP 3.2.1-0 (turn off auto-reboot) via AP
4. Disconnect USB, hold home+vol. down+power to exist download mode, when screen becomes blank, immediately hold vol.up+home+power to boot to TWRP
5. Install RMM-State_Bypass_Mesa.zip -- to fix RMM first
6. Format data partition
7. Install tweakpro-tima.zip -- to allow encryption
8. Install no-verity-opt-encyrpt-5.1.zip -- to diable verty and disabling enforce encryption. allow to choose encryption or not during initial setup
9. Format data partition !!
11. Reboot and run through setup wizard
-- when asked to "activating device protection features" it is asking if you want to encrypt the phone i.e. the data partition
-- set a PIN/password to enable. TWRP won't be able to read or backup data partition anymore (not possible on samsung devices)
you might still be able to use "adb pull /dev/block/dm-0 /tmp/dm0backup.img" to back up to PC, and use "push" to restore
12. Reboot once, and then reboot to TWRP. verify encryption was enabled a). ask for boot PIN/password b). can not mount data partition in TWRP
13. Install Magisk-v16.0.zip through TWRP.
-- Magisk must be installed AFTER encryption has been enabled via initial setup process.
-- with Magisk installed, data won't be encrypted even if you activate the device protection features during setup
[OEMXME-RMM-ENCRYPT-ROOT-SYS02]
14. reboot to system. Open Magisk Manager, and verify SafteyNet pass
15. download estrong file manager, turn on root access
16. open /system/built.prop to make sure/set
ro.security.vaultkeeper.feature=0
ro.config.tima=0
17. download "CSC feature expert for samsung"
DisableAntiMalware = TRUE
=== Profit, now you have a RMM removed, verity disabled, rooted, encrypted NoteFE===
=== NOTE: if ecryption was enabled, and you need to reset phone or format data partition:
-- once Magisk is installed, data partition will not be encrypted anymore during intial setup
-- if you want to encrypt, need to uninstall Magisk (zip included), setup phone, and install Magisk again
=== Optional - 1 ====
Enable Verizon VoLTE only, without installing US CSC
1. rename /system/csc/customer.xml to customer.xml.bak
2. copy vzw_customer.xml (attached, was extracted from S8 VZW CSC) to /system/csc/customer.xml and set chmod 755 (rw-r-r-)
3. download "CSC Features Expert for Samsung" (these are not neccessary, just good to have)
Message_DisableSmsToMmsConversionByTextInput = TRUE (disable auto convert long sms to mms)
Setting_CustNetworkSelMenu4 = LTEONLY (enable LTE only network mode)
SystemUI_SupportDataUsageViewOnQuickPanel = TRUE (data usage shown in quick panel)
Wifi_SupportAdvancedMenu = TRUE (advanced wifi options)
Wifi_SupportMobileApOnTrigger = TRUE
====== Optional -2 ====
Install US CSC and enable Verizon VoLTE. (it is safe to apply this after applying Option - 1 above "Enable Verizon VoLTE only without installing US CSC"
-- not needed to enable VoLTE, but might be needed to enable WifiCalling. I have not tested
-- this does mess with system files, and deletes all original CSC files under /system/csc and replace with /system/omc structure
-- might lose some dual sim functions, I only found one so far: native phone/contact app does not support dual sim
a). download CSC_selection v1.3.0 from S7 CSC Selection
b). replace updater-script and csc_script.sh with ones attached
c). copy to sd card and flash via TWRP
-- select XAA and XAA, DO NOT select VZW (in VZW CSC many dual sim functions gets messed up)
-- during flash, stay away from CSC tweaks that are related to phones. "Enable LTE only" is safe
d). after finish, DO NOT Reboot yet
e). rename /system/omc/XAA/customer.xml to customer.xml.bak and copy /system/omc/VZW/customer.xml to /system/omc/XAA/customer.xml
f). reboot
==== To upgrade ROM in future if you selected encryption ===
- Flash the latest full stock firmware package but this time use HOME_CSC
- Let it reboot into stock recovery and do the upgrade process.
- It should end up on the secure Startup page asking for your password. No password will work at this point because your data was encrypted in TIMA state "0".
- Reboot to download mode and flash TWRP.
- Reboot to TWRP
- Flash the TIMA prop and verity zips.
- Reboot into to Android (password should work now)
- Let it finish the upgrade.
Tmobile works too
Thanks a lot for the guide. I was able to get TWRP, encryption, Magisk, Xposed (non-systemless), and VoLTE on T-mobile USA working. I used the customer.xml located in "XAA/TMB" folder (located in zip file) from CSC selection 2.50 thread you have linked. I am on Android 7.0. Just wanted to post for those who were interested.
Only thing I changed was to keep the customer.xml file rw- r-- r-- 644 instead of the suggested 755. Don't think it makes a difference.
I did try multiple times to get Systemless Xposed working, but it would always freeze up on the screen with the unlocking icon when booting up. If anyone gets stuck there, just hold Vol Down + Home + Power until phone restarts. Power the device off when you can (will be able to access the power menu on the secure boot password screen). Go back to recovery -> format data -> go through setup process again. After setup is complete, the phone will not have an encrypted /data partition. You have to go back into recovery -> run Magisk uninstaller -> format data -> install tweakpro-tima.zip / no-verity-opt-encyrpt-5.1.zip -> go through setup again. You might be able to run Magisk uninstaller on the first boot to recovery, but I am just posting the process I went through.
If anyone is able to get Systemless Xposed working, please do share. I hate running phones without XPrivacyLua.
So I've hit a snag with this whole process, i waited for 7 days got TWRP installed, rooted and everything,(encryption was not important to me), but attempted option 1 for getting Verizon Volte working with no luck. (things never seem to work the easy way), so i did option 2 with installing the US CSC per the instructions and that went all fine and dandy.. but when I boot up the phone into the system and it ask me to choose the network for my sim it shows 2 options VZW and VZW. When selecting first option it says device needs to reboot to apply features so I click OK and it attempts to reboot but then goes straight into recovery blocking whatever process it was doing. If i select the second VZW it just does nothing. Was curious if any insight or advice can be given on this. I'm in no way at a pro at all this just want to enjoy a Samsung phone with a psychical home button and a none weird screen ratio haha. Thanks and much appreciated ahead of time!
Volte for india
Is it work for india to get the volte option...(where I can get the indian CSC)