Related
How to root and mod a Mytouch 32b without a data plan
This is the exact same phone that I had 32b HBOOT-1.33.0006 (SAPP30000)
I tried to root it and install several different root methods and several different roms. I never bricked the phone, but I did at one point have a phone that would go to the cyanogen bootsplash screen, then continually reboot.
The issue that I had was that I didn't have a data plan, and the mytouch is set up where the phone must register with google before it can be used. To get to the wifi screen, you first had to register with google, so without a data plan, the phone was worthless. To bypass the data plan, I put an old tmobile sim in the phone, went to the corporate store, told my tale of woe, and begged then to let me use a sim with a data plan so I could register with google. I actually had to do this twice because the first tome I rooted and modded the phone, I was stuck in a boot loop and I got scared, and reset the phone to factory. The phone would boot up, but when it got to the modded rom, it would always just reboot and reboot. I googled all over the place about all of these issuse, and decided to compile everything so that someone else could benefit, and if I forgot how I did it, years later I would have a reference. I also never formatted my sd card to fat32 because I did it before. It is a good idea to remove old files from the root of the SD card once you have finished flashing your phone.
This is the first step I did, and it worked perfectly.
[MT3G 32b] Root / Break perfect SPL / Way less steps from http://forum.xda-developers.com/showthread.php?t=570659
I'm creating this thread in hopes no one who owns a MyTouch, in America, on T-Mobile with a perfected SPL doesn't have to go through the brain numbing process I've just adventured through over the past week.
Special thanks to Amon_RA and Radix999 who have compiled an impressive set of information on this topic. I would have been totally lost without their contributions to this forum.
Setup:
You'll need a brand-spanking-new MyTouch 3G, 1.6 updated, un-modded, perfected SPL [Mine was: HBOOT-1.33.0006 (SAPP30000)]. To find out if your SPL is perfected power your phone off: press the vol button down > hit the power button > compare the info listed in fastboot (white screen with three skateboarding Androids) to Amon_RA's list of SPL's. If you have done anything to your phone before attempting this process go consult someone who knows wtf they are doing. I don't, but I rather tell people how this went down for me.
How I Rooted my MT3G:
1. Get your phone back to 1.5 cupcake by whatever means necessary. I used these directions: http://theunlockr.com/2009/08/22/how...ur-mytouch-3g/ (see below they are copied for your convienience)
How To: UnRoot Your MyTouch 3G/MyTouch 1.2 MyTouch and Get Back to Cupcake (Updated 04.19.10)
Written by: David Cogen
Posted on 08.22.09
Android How To's (Advanced), Featured, How To's, HTC MyTouch 1.2/Fender myTouch How To's (Advanced), HTC MyTouch 3G How To's (Advanced), Video
562 Comments
UPDATE: THIS NOW WORKS ON THE MYTOUCH 1.2 (THE MYTOUCH WITH THE 3.5MM HEADPHONE JACK AT THE TOP) AND THE OLD MYTOUCH AS WELL.
1. Download the correct .nbh file for your device and rename it to sappimg.nbh if necessary (make sure it is sappimg.nbh and NOT sappimg.nbh.nbh or anything else)
NBH File (Works for the Old MyTouch)
Zip File (Works for the new MyTouch w/ 3.5mm headphone jack) RENAME IT TO sappimg.zip (not sappimg.zip.zip, just sappimg and its a .zip file!) Thanks Caesar for sending this in!
2. Save the sappimg.nbh/sappimg.zip file to your SD card. As always, do not place it in any folder on the SD card, just on the SD card.
3. Put the SD card into the phone and turn the phone on by holding down Volume Down and Power.
4. Push the trackball down on that screen and wait for it to pick up the Sappimg.nbh.
5. Push the trackball to begin, it should automatically update from there.
6. Once the flashing is fully complete, reboot the phone. DONE!
Reported Issues
Issue: Phone says that the wrong Main Version is Older or Wrong Model ID…
Solution: Use our Goldcard Method instead.
2.Follow these steps to root your device: http://theunlockr.com/2009/08/29/how...-in-one-click/. When you are done with this process you should have Amon_RA's recovery and boot loader all setup. This will allow you to format your SD card to whatever file system you want, flash roms, do nandroid backups, the works.
Once your phone is reflashed with sappimg.nbh if you do not have a data plan, you will have to head to your nearest tmobile corporate store and beg to use a data sim. They are pretty nice, and will usually allow you to do it. Register your phone with google, then quickly go to market and install Astro File Manager, or Linda File Manager. If you do it right away with a tmobile data sim, that is the best. If you want to do it later on wifi, it is difficult. You might be able to do it right away as soon as you register with wifi because I managed to install one program that way. Shortly after you register with wifi, tmobile does something in your phone that prevents market from working. You get a download unsuccessful error over and over. I finally figured out you could take out the tmobile sim and replace it with a different sim, and the market would start working again, but it is a hassle, and you might not have a non tmobile sim handy.
I then proceeeded to the following proceedure
How To: Root the HTC Magic in One Click! http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/
Written by: David Cogen
Posted on 08.29.09
Android How To's (Advanced), Featured, How To's, HTC Magic How To's (Advanced), Video
422 Comments
I. Read Before You Begin
1. You must downgrade back to cupcake first:
Get Back to Cupcake for Magic
After you have done the above procedure and are back on cupcake (Android 1.5), you can come back to this procedure and continue.
II. How to Check Your Motherboard Version
1. Turn off your phone
2. Turn the phone on by either holding down the volume down button and power button at the same time OR by holding down the back button and power button at the same time.
3. When the screen comes up, it should say somewhere on the first line either 32A or 32B. THAT is your motherboard version. Remember it…
4. Turn off and on the phone.
5. Goto Settings > Applications *> and make sure Unknown sources is checked ON.
III. Root the Magic
1.Â*Download this APK and the appropriate recovery image for your motherboard (32A or 32B) and save it to your computer:
FlashRec.apk (Updated: 09/26/09)
Amon Ra’s Recovery Image (32B)(Updated 11.18.09)
Amon Ra’s Recovery Image (32A)(Updated 11.18.09)
2. Once they are saved to your computer, copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
3. Unplug the phone from the computer once they are downloaded to the SD card.
4. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
5. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it.Â*It should automatically install the apk.
6. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
7 (FOR 32A ONLY) Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RAv1.6.2H.img
7 (FOR 32B ONLY) Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RA-sapphire-v1.6.2G.img
8. Then click on the Flash Custom RecoveryImage button and wait for it to finish.
9. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on (keep holding until the recovery screen comes up has a bunch of text on a black background). So long as that screen comes up, you have done it correctly and can now go on to the*How to Load a ROM video for your appropriate device!
10. To get Root access you MUST go to the next video mentioned above and load a custom ROM.
Reported Issues
Issue: I get Invalid Recovery Image when using the FlashRec program.
Solution: Make sure that the spell correction and auto completion are OFF in the Text Settings (Settings > Locale and Text > Touch Input > Text Input then turn off Prediction, spell correction, and word completion) of your phone. If not then it may put in spaces where they do not belong. (I had it put a space after .img and couldn’t see it so couldn’t figure out why it kept saying invalid recovery image, like you guys).
Other than that, just make sure it is on the root of the SD card (not in any folder) and that you are typing in the recovery name and filepath correctly.
Then and it should show Flash Recovery Image.
Issue: When I download the FlashRec.apk it shows up as a .zip not an apk.
Solution: No problem. Do NOT extract it, just simply replace the .zip with .apk and then proceed with the procedure.
Issue: I get backup failed or flash failed when I try to use the FlashRec progam.
Solution: This is most likely because you already have a custom recovery image, please use one of the unrooting procedures to get back to the original recovery image and THEN you can use this procedure.
Also, instead of doing that, if you have root access, you can just put the recovery image on your SD card then go into Terminal (download it from the Market if you don’t already have it) and type:
flash_image recovery /sdcard/recovery-RA-dream-v1.2.3.img
3.
3. Go to Amon_RA's thread about SPL's: http://forum.xda-developers.com/showthread.php?t=529019
and download a Engineering SPL for your phone. (Engineering SPL 1.33.2004 by Crios worked for me)
4. Edit the SPL file name to "update.zip"
5. Load the SPL to the root of your SD card.
6. Load up RA's boot loader. (Power + Home)
7. Wipe / Clear from the boot loader menu.
8. Apply update.zip from the boot loader menu.
9. Wait for the phone to reboot, all kinds of whacky **** will happen, don't mess with the device, etc. Eventually you should reboot into recovery mode. Whatever you do - figure out how to get to recovery mode.
10. Wipe / Clear from the boot loader menu.
11. Format the SD VIA boot loader.
12. Load a new / favorite ROM onto the SD. (I use Blueberry Hero)
13. Install the Rom VIA boot loader.
14. Crack open a beer.
No gold card, fastbook, no crazy 40 step process. There may be some security issues or something involved with this process. Whatever the case, whatever the politics are between XDA/unlockr - this WORKED for me from a STOCK 1.6 device.
With a little bit of reading you should either have turned your phone into a 400$ brick or a happy little Hero pumping Android phone.
Cheers.
I backed up whatever was on my SD card, and then did this proceedure without the SuperWipe.conf step.
[WIPE][COMPLETE][FLASHABLE] SuperWipe v2 (30 Jan 2011) - So Fresh and So Clean Clean! http://forum.xda-developers.com/showthread.php?t=834812
One thing we have run into with BiffMod ROM is that there is no single "COMPLETELY erase the phone" solution.
So this is my attempt at it.... No console/terminal, no adb shell, no USB, no anything required. Just flash the file in recovery and you are done.
But OHSAKA! There are tons of threads about this, there are even existing "wipe-update" files to erase the phone. What makes your flashable update file so special???
Well I'm glad you asked that. This update contains the 'erase_image' executable with all the needed libraries statically linked. (thanks ezterry) 'erase_image' performs a low-level format of the partition which can fix unforeseen problems. Most other wipe-updates just perform "rm -rf *" at the file system level and don't touch the boot partition.
v2
---
Kudos to RichieDaze! He stepped up and added some often requested functionality to this popular wipe script. Now SuperWipe will check the root of the /sdcard/ directory for a file named "SuperWipe.conf". This file will control which partitions get erased and also control if the script triggers an auto-reboot. If the file is not present, then the script will default to wiping all partitions.
SuperWipe.conf
Code:
## SuperWipe Custom Configuration
## So Fresh and So Clean Clean Menu
## Cannot be blank (yes or No)
#
Wipe_Cache=yes
Wipe_Userdata=yes
Wipe_System=yes
Wipe_Boot=yes
Wipe_Sd_Secure=yes
Wipe_Sd_Ext=yes
#
##
## Extras
#
Reboot_when_done=no
Reboot_Delay=5
#
##
SuperWipe v2 (MD5: a3c358c1e027c8ec039ada8e667cab1a)
SuperWipe.conf (MD5: 1e7eb3a97270142aa6bf7c4fca9c2490)
You will need to reboot back into recovery after running this. If you forget and try to boot normally, you will have to pull battery to power off.
v1
---
This update will:
1) Call erase_image on CACHE, SYSTEM, USERDATA, and BOOT partitions
2) Mount /sd-ext (if it exists) and delete all files from it
3) Delete all files in the /sdcard/.android_secure directory which is where all the froyo apps2sd files live
4) Run e2fsck (file system repair) on the your ext partition
5) Log all output to the /tmp/wipe.log file (if you care)
I think this is the most complete way to wipe a phone. It supersedes 'fastboot erase system -w', VOL_DOWN+HOME+BACK, Amon_RA wipes, or various other flashable update-wipe zips.
I have tested this file the best I can on my phone. I verified all partitions are completely empty after running it. Any suggestions or bug reports are welcome!
SuperWipe (MD5: 945218bbbeab63d2c41e20c3243176ce)
You will need to power off and reboot back into recovery after running this. If you forget and try to boot normally, you will have to pull battery to power off.
I then went with this modded rom. It works pretty well.
http://android.modaco.com/content/h...tom-rom-for-gsm-hero-now-with-online-kitchen/
I'm pleased to present my MoDaCo Custom Hero ROM! No 'wipe' is required for anyone coming from MCR 1.2 onwards, or the stock 2.73.x updates.
You can now create a customised ROM containing only the parts you required - click here to read more about the MoDaCo Custom Custom ROM online kitchen!
MCR now includes a MoDaCo Custom Kernel modified by Teknologist, TCK, for additional features.
MCR now optionally includes Wavesecure in ROM, allowing you to lock / locate / wipe your device remotely in the event of loss and be notified if the SIM is changed. The application cannot be uninstalled by a thief and we we have actively worked with Wavesecure to ensure that your settings will survive a hard reset!
This ROM is based on the 2.73.x release series (currently 2.73.771.73 together with my own optimisations) for the best possible performance! The ROM is now available in 2 core versions, with and without Chinese input, with optional add on packs that can be applied to either ROM.
Included in the 'core' version
- Built with my new MCR build process which reduces size and boost speed of the ROM
- Includes Teknologist's Custom Kernel 1.91 featuring additional filesystem support (EXT4, NFS, CramFS, SquashFS 4.0), CompCache modules and config, DroidWall support and much more! See here for details.
- Rooted with 'adb remount' permission and superuser APK
- A2SD included (fully automatic - thanks cyanogen!) - create a EXT2, EXT3 or EXT4 partition as your second partition to use. dalvik-cache remains on device.
- Added Jbed Java
- Added Google Voice Search and required speech library
- Added Dropbear SSH server running by default, check 'About' screen for password (port 2222). You can now remove this by running /system/bin/removedropbear.sh
- Added Notes app from Dragon ROM
- Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
- Added android-wifi-tether 1.60 pre3 (props to the developer, this is a great app!)
- Added WiFi Status indicator, with kind permission of Andrew Schwimmer
- Added busybox 1.15.3 with Droid Explorer support
- Added Titanium Backup
- Added all 4 available HTC widgets
- Added nano 2.09 - text editor for use in shell mode
- Added parted and sqlite tools
- Added terminfo and settings to boot.img to allow nano etc. use
- Added files required for Debian linux including loxley's updated bootdeb script
- Added huge APN list
- Moved Quickoffice to data partition to allow easy uninstall
- Deleted 'Learn More' application
- ROM now includes touch focus in Camera app
- ROM now supports shortcuts using BetterCut (and therefore I assume anycut!) in Rosie
- Silenced boot sound (it's still there and can be reactivated with a file edit)
- You can now check your MoDaCo Custom ROM (MCR) version from the about menu
Included in main 'enhanced' add on pack
- Added Business Card Scanner
- Added 'Plurk' client (currently unavailable)
- Added WAP browser
Other optional add on packs (apply as normal update zips)
- 'WaveSecure' add on pack (puts Wavesecure in ROM - it is no longer in core)
- 'Boot Sounds' add on pack (restores boot sounds)
- 'Hebrew Fonts' add on pack (installs hebrew fonts)
Recommended applications (available from the market)
- More Locale for setting non english Locales
Downloads
This ROM is also available customised to your exact requirements in the MoDaCo Custom Custom ROM online kitchen in the second post of this topic - check it out!
'Core': DOWNLOAD (Mediafire Pro) - MD5: d767e7335a4bb6ef022e7d3082f28bb7
'Enhanced' add on pack: DOWNLOAD (Mediafire Pro)
'Wavesecure' add on pack: http://www.wavesecure.com/installations/update.zip
'Boot Sounds' add on pack: DOWNLOAD (Mediafire Pro)
'Hebrew Fonts' add on pack: DOWNLOAD (Mediafire Pro)
ENSURE YOU DO A NANDROID BACKUP SO YOU CAN 'ROLL BACK' IF REQUIRED!
A 'wipe' is MANDATORY when installing this ROM if you are coming from pre MCR 1.2 or a stock 1.x ROM, and you MUST do this BEFORE applying the update zip (as the update zip puts files on the data partition)! I also recommend you install the latest radio from my 'update zips' topic if you have not done so.
Please note that first boot may take a little while, especially if you have a lot of apps on your A2SD partition. Be patient! If you want a real clean start or you have issues with your existing A2SD installed apps when you boot, you need to wipe your EXT3 partition on SD too by executing 'adb shell rm -r /system/sd/app', 'adb shell rm -r /system/sd/app-private' and 'adb shell reboot'
The ROM is in an update.zip format for installation via the custom recovery image, I also strongly recommend installing the latest radio (63.18.55.06JU_6.35.08.29 at time of writing). As always, do a Nandroid backup before you do anything... just in case!
For the complete newbies, these are the steps you need to take with a 'virgin' Hero:
- Download the patched recovery image linked above and install as detailed in that post
- Download this custom ROM, and copy it to your SD card
- Enter the recovery image (if you're not in it already) by powering on while pressing 'home'
- Select 'nandroid backup' from the menu to do a backup
- If you copied the custom rom as update.zip, select 'apply sdcard:update.zip', else select the option below.
- all done
If you would like to remove parts of the ROM that you do not use, see this post.
Feedback / feature requests welcome!
Finally, if you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
flashrec.apk
here is the flashrec.apk file I used. I had a hard time finding it on the net, the website was down
Honestly, this method is much easier... http://forum.xda-developers.com/showthread.php?t=1121776
That method might be easier, but I was having trouble getting the SDK installed on my machine. I wanted to do everything from the phone, and I needed detailed step by step instructions.
Thanks for the help.
DesignerEvo v0.5, a customized stock rom for the HTC Evo Design 4G!
Visit the original announcement / discussion thread on SDX-Developers here.
Based on the stock HTC build 2.12.651.5 / Android 2.3.4 / HTC Sense 3.0, and baked using the Android Kitchen 0.184 by dsixda (http://forum.xda-developers.com/showthread.php?t=633246).
My goal was to create something that would be more useful for me, but figured other people might be able to benefit from it as well!
Important note: If you want to Factory Reset this ROM, you should reinstall the DesignerEvo-update.zip immediately after performing the reset to restore content to the /data partition. Otherwise there will be a number of preinstalled things missing.
Current Release:
DesignerEvo v0.5 (MD5SUM 71088007ee3da6d2baaf83a113e48f44)
Download here: http://d-h.st/C0I
Old Releases:
DesignerEvo v0.4
Redacted due to Wifi issues
DesignerEvo v0.3 (MD5SUM a0dd61849533fb64d887d6cb1e400cbb)
Download here: http://d-h.st/11i
DesignerEvo v0.2 (MD5SUM 00359825fee03c49007634213ebab901)
Download here: http://d-h.st/b0t
DesignerEvo v0.1 (MD5SUM 44d081019e2fe69dcf416eced88f9448)
Download here: http://d-h.st/gy023lstrxw9
Changelog:
Version 0.5:
Based on HTC RUU 2.12.651.5
Now install boot animation to /data/local/bootanimation.zip so you can easily override it if you want (via symlinks to /system)!
New DesignerEvo boot animation from Dysgenic! http://forum.xda-developers.com/showthread.php?t=905538
Backed out this change in 0.5 since it broke WiFi: Use busybox instead of toolbox for common utilities, gives a bit better functionality on things like ls and friends (colors!)
Version 0.4:
Redacted due to WiFi issues
Version 0.3:
Based on HTC RUU 2.12.651.5
Upgraded version of Android Wifi Tether to 3.1 Beta11 (IMPORTANT: Be sure to enable MSS clamping + Routing Fix in the Wifi Tether settings, otherwise tethering won't work on 3G!).
Added in HTC Radio apps + widget per user request!
Added back in Polaris Office (lets you open MS Office files, and won't run properly when installed to /data, needs to be in /system).
Resoled issue with lockscreen shortcuts and widgets on a Factory Reset.
Updated versions of Amazon Appstore + all other Play-updateable apps.
Added UOT Kitchen battery guage with battery percentage shown.
Modified statusbar to display 1x for 1xRTT data when not in a 3G area.
Using the same boot.img from DesignerEvo-0.2, note that if you don't install the correct boot.img, your WiFi and many other things will NOT WORK CORRECTLY!!! If you have already flashed 0.2, you don't have to re-flash for 0.3 though! People coming from stock and 0.1 should flash the 0.2 boot image (included in this download).
Version 0.2:
Based on HTC RUU 2.12.651.5
Downgraded to Android Wifi Tether v3.0.7 update9 since it is more stable on the Design 4G. You can still upgrade to newer versions, but this is the one that seemed to work the best.
Version 0.1:
Based on HTC RUU 1.19.651.0
Stock kernel 2.6.35.10 with initrd tweak
Debloated (Sprint / HTC stock apps removed, many can be re-downloaded from the Market)
Deodexed
Zip-aligned
/data/app enabled to allow easy removal of stock applications
/etc/init.d scripts enabled (busybox run-parts)
Disabled OTA updates in build.prop (FOTA settings)
Many updated stock applications, moved to /data/app to allow for uninstall / market updates
(Console) Applications added:
Bash shell (default)
BusyBox v1.19.3
Nano text editor
(Android) Applications added:
(Downgraded) EPST from the Evo 4G allowing applying custom PRLs on-demand (##PRL#)
Superuser 3.0.7
Android Wifi Tether v3.1 beta6
Amazon Appstore
EStrong's File Explorer
Ookla Speed Test
How to flash (note that if you have not yet done a HTC Bootloader Unlock, this will perform a factory reset on your phone!!! Be very sure that this is what you want! If you have rooted without unlocking, I highly recommend downloading Titanium Backup to perform a full backup of all your apps and data first!):
Enable USB Debugging on your android phone (http://www.groovypost.com/howto/mobile/how-to-enable-usb-debugging-android-phone/)
Get adb / fastboot working (needed to unlock and flash boot.img)
Windows: http://www.umnet.com/mobile-blogs/321-AndroidADBFastboot_Easy_5_minute_setup_(Great_for_nOObs)
Mac/Linux: Install the Android SDK from Google and then download fastboot from here: http://koushikdutta.blurryfox.com/G1/
Perform a HTC Bootloader Unlock on your HTC Evo Design 4G (makes use of fastboot installed in step 2): http://htcdev.com/bootloader
Reboot into the bootloader (adb reboot bootloader) to access fastboot (or pull your battery, and re-insert it, then immediately hold down Power and VolDown until the white HTC HBOOT screen appears).
Run all following steps in the directory where you've decompressed DesignEvo-0.1.zip:
Run "fastboot flash recovery recovery-unofficial-cwm-5.0.2.7.img" (credit goes to 2fast4u88 on XDA: http://forum.xda-developers.com/showthread.php?p=20444019)
Alternatively, flash any other Evo Design 4G Recovery image (the unofficial TWRP build is also known to work)
Run "fastboot flash boot DesignerEvo-0.1-boot.img"
Now recovery and boot will be flashed. On your phone, select "BOOTLOADER" using VolUp/Down and Power to select.
Press VolDown to select RECOVERY (might take a few seconds to scan your SDCard first) and press Power to select.
You should now be booted into 2FS CWM-based Recovery v5.0.2.7.
Now would be a good time to make a nandroid backup of all your stock partitions! The nandroid backup plus the stock-boot.img I include in my download zip will get you back to a factory flash if necessary. (More info on nandroid: http://forum.xda-developers.com/showthread.php?t=1186090)
Run "adb shell mount sdcard" to mount your SDCARD on the phone. Nothing should be returned (if success).
Run "adb push DesignerEvo-0.X-update.zip /sdcard/DesignerEvo-0.X-update.zip" to copy the update.zip image to your sdcard.
Once the push is successful, choose "install zip from sdcard" (again using VolUp/Down/Power).
It will likely take about five minutes to copy. Be patient
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "DesignerEvo-0.1-update.zip" (probably near the bottom)
Select "Yes - Install DesignerEvo-0.X-update.zip"
After about 5 minutes, you should see "Install from sdcard complete"
You can now select "+++Go Back+++", and should wipe your Cache and Dalvik Cache before proceeding.
Finally, choose "reboot system now"
Your phone should now reboot into DesignerEvo. Verify by navigating to Settings->About phone->Software information->Software number!
Regards-
hofopds
Reserved...
Reserving slot 2...
This is the ROM i use myself, but I post it here in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you. That said, these ZIP files and procedures have been tested by myself and a few others and seem to work quite well.
FLASH THIS AT YOUR OWN RISK.
Requirements:
Sony Xperia Z.
Only tested on LB, but should also work on UB.
Ability to flash ZIP files via recovery.
Features:
Based on Xperia Z_10.1.1.A.1.307_Unbranded BE.ftf (file uploaded by Psicao).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned.
No reboots when mounting system r/w.
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Call recording.
18 Toggles.
36 dpi softkeys.
Changelog:
v8
Added 18 Toggles.
Switched to 36 dpi softkeys.
v7
Added WeatherWidget back due to popular demand.
More robust and less intrusive way to ensure that mounting system r/w doesn't cause a reboot.
v6
Based on 10.1.1.A.1.307
Removed 18 Toggles since it is not compatible with 1.307 yet.
Delete the ric daemon early in the boot process.
v5
Added 18 Toggles.
Applied a few WiFi tweaks to get a (hopefully) more stable WiFi connection.
v4
Removed duplicate notification sound 'vega' (bug in original ROM).
Increased volume a bit.
v3
Created all symlinks found in the original FTF file.
Changed all file and directory permissions to match those in the original FTF file.
Added a more robust script to stop ric.
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.307_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Reboot again once NFC firmware has been upgraded (only needed if upgrading from 1.434 or earlier).
Note regarding unlocked bootloaders: This ROM is designed for LB. If using this on UB flash the following ZIP after installation to remove the CWM recovery for LB: C6603_10.1.1.A.1.307_UBPATCH.zip
Clear data?
If NFC is not working and you're upgrading from a 1.434 ROM, I recommend that you clear your userdata by flashing C6603_10.1.1.A.1.307_ClearData.zip.
You do NOT need to clear user data if you are already running a ROM based on 1.253 or 1.307 and everything is working fine.
MD5 hashes:
2f8fe013da90987447a04c0e5f405998 (C6603_10.1.1.A.1.253_DEBLOAT.zip)
3bba6ffb3cd9bdf7535c5e4b722223d5 (C6603_10.1.1.A.1.253_ClearData.zip)
b889d474290d9b924acbf011277d58e3 (C6603_10.1.1.A.1.307_UBPATCH.zip)
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel and baseband from the original FTF via Flashtool in order to get the full 1.307 experience.
Preventing reboots when mounting /system read-write
This ROM uses my own little utility called RICHunter to prevent reboots when mounting /system read-write. If you want to use it yourself in your own ROM you can download it here:
0c766dc58cc909693f5d669264d78f4a (richunter.zip)
Included in the ZIP file is a README.txt that explains how to use it, but you can also read it here:
RICHunter by Carceri @ XDA
1. What is this?
On the Xperia Z Sony have added a small program called ric which
monitors mount options on filesystems and reboots the system if
they deviate from their default values. This causes the system
to reboot e.g. when the /system partition is mounted read-write.
In short, this programs stops this daemon and replaces it with a
dummy version that doesn't do anything, thereby disabling ric.
2. How do I use it?
Just put the file richunter somewhere on your system, for example
/system/bin/richunter, make it executable (chmod 755) and run it
as the root user. This needs to be done every time the system is
restarted.
This can be achieved by putting the following lines in a file
called /system/etc/install-recovery.sh:
#!/system/bin/sh
exec /system/bin/richunter
Another way is to make a wrapper to /system/bin/ctrlaltdel and
call richunter from there:
#!/system/bin/sh
exec /system/bin/richunter
exec /system/bin/toolbox ctrlaltdel "${1}" "${2}" "${3}" "${4}"
Choose either one, or a 3rd solution to automatically run it.
Remember to make the files executable.
3. How does it work?
On the latest kernel, the ric daemon is restarted whenever it
is killed. Therefore the following steps are taken by this
program to stop it without giving it time to reboot the system:
1) The programs runs as a daemon waiting for up to 60 seconds
for ric to start.
2) It detects which CPU ric was last scheduled on, and forces
ric to always run on that CPU in the future.
3) It forces itself to run on the same CPU as ric and sets its
scheduling priority to real-time. This prevents anything
in that CPU from running, including ric.
4) It mounts the rootfs read-write and replaces ric with a
dummy version that just sleeps forever. Finally it kills
the ric process and remounts rootfs read-only.
5) The daemon now exits. When ric is restarted the dummy
version is started instead.
4. What about unlocked bootloaders and custom kernels?
On custom kernels ric has either been removed or not installed
at all. Therefore this is only needed on locked bootloaders.
5. Can I use it in my own ROM?
Sure. Use it as you want.
6. How do I compile it?
You need to have the Android NDK installed. Then set the
correct paths in the included Makefile and run:
1) make prep
2) make
That's it. When you want to recompile you can skip step 1).
7. What license is this released under?
It is UNLICENSED software. See http://unlicense.org/
Hi, i have not tested this exact zip, but the rom i am using now is based on a previous version you posted in another thread.
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
As i said, this happens on the first zip you uploaded, i don't know if this was already solved on newer versions.
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions. This step could also be added to the main flash script, no user data is lost and i think all NFC related problems would be gone
Thanks for sharing your work.
RoberM said:
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
Click to expand...
Click to collapse
I have added the Notes app back in this zip.
RoberM said:
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions.
Click to expand...
Click to collapse
That was actually the first thing I tried and it didn't work for me. It might work for some and if someone is interested I'll be happy to provide a zip file that just restores this directory and keeps everything else under /data intact.
How do you enable call recording btw? Thanks.
Sent from my C6603
The link is down!! :crying:
mandarjoshiin said:
The link is down!! :crying:
Click to expand...
Click to collapse
Link is back up. I were just in the process if uploading v2
vibranze said:
How do you enable call recording btw? Thanks.
Click to expand...
Click to collapse
Press the menu button during a call.
Carceri said:
This is the ROM i use myself, but I posted this in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you, so FLASH THIS AT YOUR OWN RISK.
Requirements:
- Sony Xperia Z with locked bootloader.
- Ability to flash ZIP files via recovery.
Features:
Based on the first version of the ZIP posted by wawyed on this thread.
...which was based on C6603_Unbranded_10.1.1.A.1.253.ftf (original file uploaded by prakka).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Enabled call recording.
Changelog:
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.253_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Say not to "Disable recovery flash" if asked.
Possibly reboot a second time once NFC firmware has been upgraded.
I had problems with NFC not working if I didn't clear user data the first time I upgraded from a version < 1.253. In order to clear user data follow this step:
Flash C6603_10.1.1.A.1.253_ClearData.zip.
These ZIP files and procedures have been tested by myself and a few others and seem to work. However, some people have also experienced issues, but since I don't know their exact setup it is impossible for me to pinpoint the source of these errors. FLASH THIS AT YOUR OWN RISK.
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel, fotakernel and baseband from the original FTF via Flashtool in order to get the full 1.253 experience.
Click to expand...
Click to collapse
hello I used your guide and everything works to perfection thanks:laugh:, I invite other people to use this guide to those who want to update your phone with the root installed.:good:
ps. sorry if I use a translator.
ciao ho usato la tua guida e funziona tutto alla perfezzione grazie, invito altri utenti ad usare questa guida per chi vuole aggiornare il telefono con il root installato.
Great, this is the first one deodexed and zipaligned, i am sure a lot of people will be interested.
EDIT: Ok, i didn't read well, it says Re-Odexed
Sorry, i'm a little confused, is this rom odexed or deodexed?
Sent from my C6603 using Tapatalk 2
secondkai said:
Sorry, i'm a little confused, is this rom odexed or deodexed?
Click to expand...
Click to collapse
In changes for version 2 reodexed is written. Attentively read an original post.
Carceri said:
Press the menu button during a call.
Click to expand...
Click to collapse
Thanks, but what I meant was how to incorporate call recording into the ROM, is it something that can be done easily, e.g. editing build.prop, etc or any other method?
Cheers.
Update: I got the answer. Thanks.
picasa album sync is missing in google accounts and album view, is this due to bloat removal ?
jimsey said:
picasa album sync is missing in google accounts and album view, is this due to bloat removal ?
Click to expand...
Click to collapse
I don't think so. Is that feature available on a normal Xperia Z stock ROM?
I think that the original Gallery app installs the required sync adapter. Also if you have Google+ installed it is replaced by Photo Sync.
hello Carceri would like to upgrade to v4 there some procedure to be performed?
fabbiotto said:
hello Carceri would like to upgrade to v4 there some procedure to be performed?
Click to expand...
Click to collapse
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.
Carceri said:
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.
Click to expand...
Click to collapse
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?
fabbiotto said:
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?
Click to expand...
Click to collapse
Just flash the new ROM. No need to clear data.
Carceri said:
Just flash the new ROM. No need to clear data.
Click to expand...
Click to collapse
thank you very much:good:
hello v4 does not work well with the DoCoMo Status Bar and the Task Switcher sony disappears, you can take a look please?
by the time I come back to v2
Only valid for Moto G 2014!
Hello, forum mates. I have spent few days with this great device, I gave it meanwhile to my sister as present.
ATM, there are barely any custom ROMs, so I will list here few good things to do right after unlocking its bootloader and obtaining root access :angel:
So here you can read my little checklist and do whatever you prefer:
DISCLAIMER:
Code:
[I]your warranty is now void. All you do
with your phone is on your own risk!
Partitions info is valid for XT1068
international GSM dual-SIM only! Workflow
is tested only on KitKat factory image![/I]
Click to expand...
Click to collapse
Unlocking Bootloader: Motorola's website
Removing startup screen with warning of unlocked bootloader: flash attached zip in custom recovery
(I can confirm that the attached zip works, it will restore the white original Motorola splash screen)
1. Boot custom recovery without flashing it:
Copy and paste custom recovery (file format: img) into your SDK/platform-tools folder, I recommend here TWRP_2.8.0.1_Titan_v2 that I have successfully tested myself. Until this point the latest Motorola USB driver must be installed on your Windows PC, USB debugging (under "developer options") on your phone must be enabled. However, I generally recommend using Linux instead of Windows. You can check in my short guide for Ubuntu users how to install fastboot and ADB in Ubuntu. I have no clue about Mac iOS, sorry.
Here we go:
Navigate in CMD line into the directory where your adb.exe is saved. Example on my PC, it is in the folder "AndroidSDK", and there in the folder "platform-tools". So my commands would be:
Typing on keyboard Win+R
Enter cmd
the command line appears after that
Code:
cd c:\androidsdk\sdk\platform-tools
Now I'm in my desired folder. The next command is checking the USB driver / ADB connection:
Connect the phone to with your PC via USB cable and enter in cmd:
Code:
adb devices
Correct response:
HTML:
xxx(serial No)xxx device
If you don't see serial No of your Moto G, check if USB debugging is enabled. If serial No is there but "offline" instead of "device" appears, you will only have to confirm the promt on your phone's screen to allow USB debugging. If nothing appears, try to update your USB driver (don't go any further without working ADB connection!)
Now we will boot into bootloader mode and check there if fastboot connection is also working:
Code:
fastboot devices
Correct response:
HTML:
xxx(serial No)xxx fastboot
If the response looks like that, we can now boot into the custom recovery without flashing it onto device. The recovery.img will be booted directly from "platform-tools" folder, while stock recovery still remains installed on the phone. My recovery.img file's name is for example "TWRP-Titan", so after I've previously saved it in my "platform-tools" I will now enter in cmd:
Code:
fastboot boot TWRP-Titan.img
The phone will boot into the beautiful touch-recovery TWRP. Blue screen is there? Yesssss!! :good:
Now we can start with backups of our still 100% stock firmware in the next chapture.
Click to expand...
Click to collapse
2. Backup your stock firmware:
While still in the TWRP, simply create backup of all your partitions. It is strongly recommended to save backup on the external SD card, as many modifications or next unlocking of the bootloader (if relocked) will every time blow all your data from the internal memory.
Now still in TWRP, install SuperSU.zip
Reboot into the system
Now we will backup stock recovery, that we can later flash at any point back:
Code:
adb shell (enter)
su (enter)
Look at this point on the screen of your phone, SuperSU will promt you to allow SU access for shell, You should confirm that.
Code:
dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img
It will save the "recovery.img" file in your /sdcard folder on your phone's internal memory. It is strongly recommended to create the new folder on your external SD card where you can move all backup img files. To move the files, use any root file browser like for example Root Browser. When you open Root Browser for the first time, it will prompt oyu to install few utilities (busybox, unrar etc) which you should allow.
At this point, your entire stock firmware has been saved as backup.
Click to expand...
Click to collapse
3. Backup all partitions of your factory image / firmware:
Just the same way as you have previously created backup of your "recovery.img" you can
create "img" backup files of all your partitions. Check the attached screenshots and simply replace in the adb shell command the number of the mmcblk0p block No with the one you desire to backup and change "recovery" to the proper partition names, just like in the screenshots:
Click to expand...
Click to collapse
4. Restore to 100% stock firmware:
To return to 100% stock, you simply need to flash (or only boot) again TWRP 2.8.0.1, to restore your nandroid backup of your stock firmware and -if custom recovery was flashed- to flash in bootloader mode your stock recovery back. Paste your (stock) "recovery.img" file into "platform-tools" folder and execute in bootloader mode:
Code:
fastboot flash recovery recovery.img
After that simply restore your TWRP backup of stock and flash in bootloader mode your stock recovery back. To unroot permanently, open SuperSU app and choose the option "Full unroot" under "settings".
To relock the bootloader again: reboot to bootloader mode and execute in cmd:
Code:
fastboot oem lock
Your Moto G should be now again 100% stock.
Click to expand...
Click to collapse
If you benefit from this guide, show me your love and please hit "THANKS" button.
Credits also to all guys who have created linked guides (please hit there "thanks" also)
EASY MODS (Moto G 2014 stock firmware)
I am myself very big fan of SlimRoms (I was AlphaBeta SlimKat tester on few devices), so I was desperately missing the "Real Dark Slim" mode (and several other mods) on the Moto G 2014 factory image 4.4.4
I had to darken my Moto G 2014, so here I share now quite easy way how to get dark UI on many apps:
Click to expand...
Click to collapse
DARK UI APPS:
On the attached screenshots is an example of the "normal" Play Store (light UI) YouTube app vs the modified, dark UI YouTube app.
Luckily, the Team BlackOut consisting out of some great developers and contributors has darkened out whole bunch of apps. Please visit their website or please visit their thread where you can get more info and download directly the app TBO updater (ver.5.0.0 is up to date ATM, it is a lot better than the v.3 which was suffering of regular FCs on many devices).
With the TBO app you will find also boot animations, wallpapers etc and info how to install, the most important to avoid data loss and crying is: don't forget to create nandroid backup before modifying!
List of modified apps by the TBO available in dark UI (choice, uncomplete list):
Apollo music
Calendar
Chromecast
Drive
DropBox
Ebay
ES File Explorer
Facebook
Google now
Google+
Gmail
Hangouts
Instagram
Keep
MMS (AOSP)
Netflix
PayPal
PlayStore
WhatsApp
Skype
Spotify
Translate
Twitter
YouTube
etc.
Small tipps for the flawless un/installation of the system apps:
Regarding the fact that issues could occur when replacing the system apps (probably caused by smaller scripts which might remain as "corpses" after removing the apps) here is quite reliable way to go:
gain root access (flash SuperSU zip in custom recovery)
backup all apps that should be replaced with the darkened ones (recommended: Titanium Backup to create backup, or SD Maid to create *apk file)
now uninstall the respective apps (also with TB or SD Maid)
Open Play Store, install again and uninstall respective apps (that will remove reliably all rests)
Install the darkened apps (apk files or flashable zips that you have downloaded with TBO Updater)
Enjoy dark apps!
TROUBLESHOOTING: If anything goes wrong (bootloop, dark app FCs etc) delete darkened app and restore your app backup. I have never faced bootloop, but some apps simply might not work and will FC. Even if somebody would face bootloop, restoring the nandroid backup will revert all changes.
For normally installed apps (non-system apps): simply uninstall them through Play Store and install darkened ones instead. If TBO apps don't work, uninstall them and install again from the Play Store normal versions.
Click to expand...
Click to collapse
All credits here go to @djdarkknight96, @B_Boytm, @Gunthermic, @dafoxs, @train, @darkknight and our beloved SlimGapps maintainer, @dankoman :highfive:
Sorry, if I forgot to mention someone- remind me please!
(please if you use their modified apps, don't forget to find some posts of those guys here on forum and hit several times "thanks" button!)
Xposed frameworks
Add hunderds of mods, change functions of your hardware buttons, add double-tap-to-sleep, make your phone to fly etc, endless mods possibilities with Xposed frameworks (main thread)
Little guide for people who never used Xposed frameworks before:
download Xposed installer apk (v. 2.7 experimental is my recommendation for 4.3 and newer firmwares)
download also Xposed-Disabler-Recovery.zip from the main thread (if anything goes wrong)
create nandroid backup!
install Xposed installer app
open the app and Install/Update framework
reboot
if anything goes wrong, you end up with bootloop or so, reboot recovery and flash Xposed-Disabler-Recovery.zip (if even that doesn't help, restore nandroid backup)
if the phone reboots fine (it should) download modules you desire to use and install them
reboot
enjoy your new, customized firmware
If you find this post useful, please hit "THANKS" and honour my time spent to share this with you. Please also hit thanks to all devs and contributors whose work brought you benefits.
Click to expand...
Click to collapse
Hope to see soon more tweaks from you
Gerriitw said:
Hope to see soon more tweaks from you
Click to expand...
Click to collapse
I will post in the second post few more ideas with smaller mods on the stock firmware like using dark UI apps, some useful little frameworks modules, debloating etc.
This thread is actually not so interesting for experienced users, it's all quite common stuff.
tetakpatalked from Nexus 7 flo
Very helpful for newbies....U have done great job...hope to see more...
Second post updated (mods of stock 4.4.4 firmware)
Backup/restore apps and respective data, SSAIDs, runtime permissions, generic system settings, Magisk modules, and more.
Works in recovery mode as well.
Refer to the upstream repository to get started.
I would like to be the first to thank you for this solution, i have one question how to make a full backup all accounts and data i saw in the guide tarb -badsm10 . but im not sure if its full backup or no
yassine2217 said:
I would like to be the first to thank you for this solution, i have one question how to make a full backup all accounts and data i saw in the guide tarb -badsm10 . but im not sure if its full backup or no
Click to expand...
Click to collapse
tarb -badsm10 . would backup the following:
a) All user and updated system APKs;
d) Data of those apps (also includes device-encrypted data (user_de), which can be excluded with D);
s) Generic system settings (quick toggles, sounds, display, etc.);
m) Magisk data (everything from /data/adb/, except magisk/ and magisk.db);
10) This instructs tarb to use 10 as the zstd compression level (default is 1);
This is a complete backup, except if you also want external data. If so, you would add the e flag.
External data includes /sdcard/Android/data/, /sdcard/Android/media/ (can be excluded with M), and /sdcard/Android/obb (can be excluded with O).
Note: backing up Google accounts on recent Android versions is just not a thing. You could try, but there's no guarantee that the restore will work. It may even cause problems. The target data keeps changing with new Android releases, and those changes are fairly unpredictable -- all thanks to Google, yay!
Cool, so this will replace Migrator right
VR25 said:
tarb -badsm10 . would backup the following:
a) All user and updated system APKs;
d) Data of those apps (also includes device-encrypted data (user_de), which can be excluded with D);
s) Generic system settings (quick toggles, sounds, display, etc.);
m) Magisk data (everything from /data/adb/, except magisk/ and magisk.db);
10) This instructs tarb to use 10 as the zstd compression level (default is 1);
This is a complete backup, except if you also want external data. If so, you would add the e flag.
External data includes /sdcard/Android/data/, /sdcard/Android/media/ (can be excluded with M), and /sdcard/Android/obb (can be excluded with O).
Note: backing up Google accounts on recent Android versions is just not a thing. You could try, but there's no guarantee that the restore will work. It may even cause problems. The target data keeps changing with new Android releases, and those changes are fairly unpredictable -- all thanks to Google, yay!
Click to expand...
Click to collapse
Thank you for the clear explaination
v2022.5.12 202205120
- C flag: exclude all *[cC]ache* files/directories globally (alternative to -X '*[cC]ache*');
- Do not backup/restore SSAIDs if /data/system/users/0/settings_ssaid.xml is encrypted;
- Updated info and support texts.
Try upgrading with tarb -u.
v2022.5.15 202205150
- Fixed -rnx ['regex'];
- -r shall have no fallback regex, just like -b;
- Skip GMS data backup/restore.
Try upgrading with tarb -u (interactive) or tarb -uu (no prompts).
v2022.5.16 202205160
- Fixed "backup/restore stops right after gms";
- Remind user to disable/remove Magisk modules that may cause bootloop;
- Updated Telegram group link.
v2022.5.25 202205250
- Architecture-aware self-backup
- Build script gets version from changelog
- Fixed `-rnx ['regex']`
- Fixed settings backup output inconsistencies
v2022.6.4
- cf899cd Remove debugging line, and reword a comment
- f8fdb0f Update help text
- bae6a39 C == "-X [Cc]ache" (non-greedy)
- 9a9138e Always exclude external cache
- 6d29dd6 Only restore SSAIDs and runtime perms after successful data restore
- fb0d1e9 Fix build/VERSION
Hello, I tried using this and I'm not having success. I installed as a Magisk Module with the -m flag and rebooted afterwards. Installed the arm64 as I have the SD855.
When I run the command tarb -badsm10 I get the following:
settings global
settings secure
settings system
/data/adb
Click to expand...
Click to collapse
And on the tarb folder I get a file with 30MB, that's all.
Thanks!
jakito said:
Hello, I tried using this and I'm not having success. I installed as a Magisk Module with the -m flag and rebooted afterwards. Installed the arm64 as I have the SD855.
When I run the command tarb -badsm10 I get the following:
And on the tarb folder I get a file with 30MB, that's all.
Thanks!
Click to expand...
Click to collapse
Perhaps the period is missing at the end of command line. Write command as follows:
tarb -badsm10 .
cave.man1908 said:
Perhaps the period is missing at the end of command line. Write command as follows:
tarb -badsm10 .
Click to expand...
Click to collapse
Yes, that worked. My bad!
Thank you
Edit: fixed
How do you use this in recovery? This works for a12 and a12 recoveries?
parag0n1986 said:
How do you use this in recovery? This works for a12 and a12 recoveries?
Click to expand...
Click to collapse
Only custom recoveries that can decrypt data are supported.
If you've installed tarb as a Magisk module (-m), /data/t is available for use in recovery.
Run /data/t -badems ..
It'll backup (-b):
* All user and updated system apps (a) with respective data (d) and external data (e), excluding cache;
* Magisk modules (m);
* Generic system settings (s).
If you haven't installed it, assuming it's located in /sdcard/Download, run sh /sdcard/Download/tarb-arm64 -badems ...
Use adb shell or recovery's own terminal.
v2022.6.25
ece9f5c Add Zelle donation info
e667f34 Add support for -bnx 'regex'
b1d3484 Remove obsolete lines
2e50b94 Fix: incomplete apk backup
5b268d9 Flag D implies d; M/O imply e
d898768 Make "o" flag work with "-b" as well
9715bbb Update usage examples
ff40224 Exclude internal cache by default
VR25 said:
Only custom recoveries that can decrypt data are supported.
If you've installed tarb as a Magisk module (-m), /data/t is available for use in recovery.
Run /data/t -badems ..
It'll backup (-b):
* All user and updated system apps (a) with respective data (d) and external data (e), excluding cache;
* Magisk modules (m);
* Generic system settings (s).
If you haven't installed it, assuming it's located in /sdcard/Download, run sh /sdcard/Download/tarb-arm64 -badems ...
Use adb shell or recovery's own terminal.
Click to expand...
Click to collapse
So if I'm on an a12 custom ROM, I would have to flash DFE so I am unencrypted and this should work? I've tried DFE on a couple of the 12.1 ROMs and it doesn't work any ideas to get it unencrypted on all these new rooms? I'm assuming I have to use TWRP I didn't know if any of these a12s have a terminal yet
parag0n1986 said:
So if I'm on an a12 custom ROM, I would have to flash DFE so I am unencrypted and this should work? I've tried DFE on a couple of the 12.1 ROMs and it doesn't work any ideas to get it unencrypted on all these new rooms? I'm assuming I have to use TWRP I didn't know if any of these a12s have a terminal yet
Click to expand...
Click to collapse
Android ROMs almost never ship with a terminal emulator. You can always install one or just use adb shell.
Modern custom recoveries (TWRP and derivatives) all have a built-in terminal.
Some recoveries can decrypt data.
When this is not the case, one must disable forced encryption to be able to read /data from recovery (mandatory for tarb to work there).
If Magisk cannot disable encryption, you have to patch /vendor/etc/fstab* file(s). This is usually just a matter of replacing "fileencryption=" with "encryptable=", rebooting, and formatting (not just wiping) the userdata partition.
VR25 said:
Android ROMs almost never ship with a terminal emulator. You can always install one or just use adb shell.
Modern custom recoveries (TWRP and derivatives) all have a built-in terminal.
Some recoveries can decrypt data.
When this is not the case, one must disable forced encryption to be able to read /data from recovery (mandatory for tarb to work there).
If Magisk cannot disable encryption, you have to patch /vendor/etc/fstab* file(s). This is usually just a matter of replacing "fileencryption=" with "encryptable=", rebooting, and formatting (not just wiping) the userdata partition.
Click to expand...
Click to collapse
So basically, using ADB shell while you're in nameless or Evo X recovery, for example, is just like using the built-in TWRP terminal? Just need ADB enabled in recovery mode?
How do I have magisk disable encryption? I've noticed when you flash magisk, It usually shows keep verity and force encryption = true. How do you make magisk disable them when you first flash magisk?
Sorry about all the questions, just really want to learn this stuff more, and you're amazing for explaining this stuff! I miss being able to backup/restore data nandroid style!
One last question. You said manually patch /vendor/etc/fstab.qcom? Do you replace anything that says file encryption with encryptable, or only in the /userdata area in the fstab? Here is what mine says. Would love to know what change in there and put it back and reformat and be unencrypted on a12!
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt latemount,wait,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,metadata_encryption=aes-256-xts:wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,quota,reservedsize=512M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs
That's line #45 in my fstab.qcom file. So from that, my current ROM is FBEv2? And f2fs format for data?