I figured I'd illustrate the basic boot process flow for the Transformer. This should help conceptualize what the Transformer does when running stock Android, custom ROM with CWM Recovery, or something even more custom, like dual-booting Ubuntu. I'll add onto this as I have time and learn more.
{
"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"
}
Boot Modes
Normal Boot - By default the Transformer will boot up and load the Android boot configuration from the boot partition, which ultimately loads the OS from the System partition. Once Android loads, you'll see these partitions mounted to /boot and /system.
Recovery - When you boot the Transformer by holding Power+VolDown and then press VolUp when prompted, the Recovery partition is loaded. I don't actually know what the stock recovery looks like, since I rooted almost immediately, but this is where the ClockWorkMod (CWM) Recovery is installed. While I left this out of the diagram, this partition should have write access to most of the internal flash.
APX Mode - When you boot the Transformer by holding Power+VolUp, APX mode is started. This is a bit different from the other two boot modes, as the internal flash isn't used. Instead the APX Mode is booted from another read-only chip, which has direct write-access to the entire internal flash. This is the mode that nvflash communicates with to backup from or write to the flash. If your Transformer is nvflash-able, you should also be un-brickable because of this mode.
Partitions
Boot - This partition stored the boot configuration for Android. As with any Linux-based operating system, this partition is necessary to start the OS. Eventually the remaining OS files are loaded from the System partition.
System - This is where most of the Android OS files are located. Generally this partition is mounted as read-only, as removing or editing the wrong file could bork your Android installation.
Recovery - This partition stores the recovery software, such as the stock recovery or ClockWorkMod (CWM) Recovery.
Data - This partition is used for application and user data storage. This is generally the largest partition, so some custom configurations (such as dual-boot Ubuntu) will shrink this partition to steal some extra space for their own use.
Cache - This partition is used for Android cache. As I don't know much about how Android uses this partition, I don't have a better explanation.
Notes:
Please reply with any requests or fixes. This is a Work-In-Progress.
Reserved for future use.
Any boot involving a kernel, so all operating systems, and recovery mode the boot flow is Bootrom reads BCT, BCT tells of the device config, then the PT is read, and EBT is located from that and booted, bootmode selection is done via the bootloader.
APX boot is bootrom -> USB recovery mode, bootrom is listening to the GPIO on boot, if found it drops back into the internal nv3pserver for nvflash connectivity, nothing is accessed that is not on the Tegra2 SoC
Awesome. Thanks, lilstevie. I'll update the diagram tonight.
Related
Ok, I really screwed up my phone badly and I am hoping someone can help me out. Basically, my original goal was to change the Radio because it keeps making static noise when someone calls me or I call someone. Anyways, I tried changing it but when I went into the BootLoader (Tri color) screen and USBed it. The CustomRUU.exe still didn't recognize it. So I just gave up and was like I'll deal with the noise...
Now, I saw that tyween released a new patch. I plan on installing it like my normal plan was which was, Boot AD NAND, which launches into CWM and then I do back up, install zip , restore old stuff. Pretty simple.
ANYWAYS, the issue is, when I did it this time, some error about NAND file failed or something along those lines so what I did when I googled the solution was to install WMC 6.5 onto my computer which now recognized the MAGDLR device (phone) when I did the option USB Flasher. Once opening USB Flasher, I installed this (http://www.multiupload.com/LVJEZV8MZV) and it seemed everything works.
Problem is, when I boot with the Boot AD NAND, it boots with the new tyween but all my data that I had before was lost. I tried to see what the issue was, but when I go into Boot AD NAND, it loads the ROM; NOT CWM like it used to, instead CWM is booted under the option Boot AD SD card option. If I look at my micro SD card:
{
"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"
}
You can see that all my previous files are still there.
Basically, my issues are:
1) How do I get CWM to load when I select the Boot AD NAND?
2) How do I reverse everything and hopefully get my data back, I was hoping to have a backup from the clockwork recovery folder but my hopes aren't high, just hoping that my partition of the new ROM didn't over-write the old one which means I can delete it and hopefully still have my old stuff.
For those who read everything, thanks for doing so and I hope you can all help me =/
Willing to donate to anyone that can help. =/
Dorianking said:
Basically, my issues are:
1) How do I get CWM to load when I select the Boot AD NAND?
2) How do I reverse everything and hopefully get my data back, I was hoping to have a backup from the clockwork recovery folder but my hopes aren't high, just hoping that my partition of the new ROM didn't over-write the old one which means I can delete it and hopefully still have my old stuff.
For those who read everything, thanks for doing so and I hope you can all help me =/
Click to expand...
Click to collapse
1.)CWM will not load under Boot AD NAND EVER!!
MAGLDR 1.3 had CWM built in under option 8. AD RECOVERY, you do not need it under BOOT AD SD.
2.)Unless you did a backup in CWM of your old ROM, there is no way to restore your data. If you did a backup, go into CWM, choose backup/restore, advanced restore, then choose and reboot after.
Hi I finally decided to send my z3c D5803 in for repair.
I want to remove any sensitive data from the device.
It runs on rooted Android 5.1.1 and has TWRP 2.8.7.0 installed. Over the time I installed a lot of xposed modules and tweaked a lot of settings. So I really want to keep my exact system image.
I have several Questions for every step:
1. Which partitions should I backup
{
"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"
}
According to What should I back up in TWRP?
`The default backup options in TWRP are system, data, and boot`
1.1 Is `Kernel Image` the same as boot ?
1.2. I just go with the defualt settings ?
2. My first simple idea was to remove the external SDcard after the backup from step 1 and perform a "factory reset" using TWRP:
2.1 root and TWRP is preserved ?
3. When the phone is back from repair I just boot in recovery and recover only the /data partition from the inserted SDcard ?
3.1
Is wiping /data enough to remove all sensitive data ( password manager app) [ SdCard removed of course ] ?
What about XPOSED Modules that maybe contain sensitive data ?
4. I guess the TWRP factory reset does not secure erase data ?
4.1 Does anyone know the method that TWRP uses to remove the data from the /data partition?
-> I read about encrypt the phone but a lot of discussions say that you have to unroot before and I guess this would destroy my whole plan of just erasing the /data partition ?
4.1 Does anybody know and tested method to add a additional layer of security.
I found this:
Normal erasing via TWRP should be enough. But if you want to erase all of your data on the phone then you need to execute the TRIM command on your flash storage.
You can do this on TWRP by following the steps:
– Mount the /system partition
– Go to Advanced and then Terminal Command
– Execute the command to TRIM /system partition:
fstrim -v /system
– Execute the command to TRIM /data partition:
fstrim -v /data
– Execute the command to TRIM /cache partition:
fstrim -v /cache
When you delete data from your storage, the actual data is not cleaned but the link to the internal blocks (where the actual data is stored) is made as invalid or the block is made as dirty.
TRIM command is designed specifically for flash storage. When you execute TRIM command on flash storage, it cleans all the data of all the blocks.
NOTE:
But you need to be careful, as the TRIM actually erases block by block and flash storage has limited erase and write cycles.
Click to expand...
Click to collapse
Well personally it doesn't really matter but backup Data,System and Boot(kernel image) and if you really want to remove everything transfer pictures to your computer and wipe internal storage
And when you backup everything will be kept and when you wipe everything will be wiped including password managers and etc,and when you restore it back everything will be as you left it with everything on your device as before.
When you click the title above and start to read this article, I guess you may have run into a trouble: Your smart device cannot be powered on? You have to recover the software system after a failed ROM flashing? You want to switch from a third-party system back to Huawei system after a successful ROM flashing?
Don't worry. Huawei provides you with eRecovery that excels at recovering the software system easily and successfully. If you fail to start your device because of a software fault, try eRecovery.
If your device system works, you are not advised to use eRecovery to update the system. At present, eRecovery is only available for some regions and models, and will be available for other regions and device models after some time. Please wait for your surprise.
{
"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"
}
*Note: It’s not supported for USA users and Docoma users in Japan.
Pay attention to the following points before system recovery:
1. If you can enter the main system, please back up your data. All your personal data will be erased after your system recovered if you didn’t meet the following conditions when entered eRecovery system.
(1) The data partition is mounted read-write mode. If the mounting fails and data clearing is required, a prompt will be displayed for you to know.
(2) Your device is locked.
(3) Your device has sufficient space in an internal or external card. If the space is insufficient, your device displays a message indicating that you need to empty the internal card or insert an external card.
2. Ensure that a Wi-Fi hotspot is available (eRecovery supports some authentication modes, such as WPA-PSK, WPA2-PSK, WEP, and open system now).
3. Keep connecting your device to power (A powered-on computer can also provide power).
Now, let's get back to the fixing:
1. There are three ways to start eRecovery:
Method 1: The software system detects a startup failure, and your device automatically enters the eRecovery system;
Method 2: The software system automatically detects a fault (for example, your device uses a third-party system after ROM flashing), but the device can be started and displays a message on the UI. You can press and hold the volume up key for more than 3 seconds to enter the eRecovery system;
Method 3: You can initiate the process of entering the eRecovery system (by pressing and holding the volume up key for more than 5 seconds while your device is connected to power).
2. Tap Download latest version and recovery on the UI to enter the download confirmation UI.
3. Tap Download and recovery and waits for the software system to restart the Wi-Fi system and scan available hotspots.
4. Select an available Wi-Fi hotspot and enter the password for connection.
5. After your device is connected to the Wi-Fi hotspot successfully, the software system automatically obtains and downloads the upgrade package. You don't need to do anything at this stage. The package has a large size and may take some time.
6. After the download is completed, your device automatically installs the upgrade package.
7. After the upgrade is successful, your device automatically counts down and enters the software system. Voila! Your device works now.
After reading this article, you can recover your device no matter what happened to it before. If you think eRecovery is powerful, don't hesitate to share it with your friends.
Background Information
NOTE: I am not responsible in any way for whatever may go wrong with you or your device by following this guide. What works for me may not work for you. Read the commands and understand what they mean before using them. If something doesn't look right, then stop. If you don't understand something, then stop. You use this guide at your own risk
The honor 5x has another separate recovery partition called eRecovery. It can be accessed by powering on the phone by holding the Power + Volume Up button at the same time, while the phone is connected to a computer via usb. Using those same keycodes while the phone isn't connected via usb will boot into normal recovery. (This was pretty confusing behavior for me at first until I figured it out). eRecovery looks like this screen:
{
"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"
}
Flashing this eRecovery partition with a recovery of your choice (such as TWRP) will give you a second choice in the event that the first recovery is corrupted or damaged. The core premise of this guide is saving the recovery image to the sd card, locating the erecovery partition using ADB shell, and then using dd to write the recovery image to the partition. For this guide, it is assumed you already have twrp installed into the main recovery, and intend to download another twrp image to write to the erecovery as well.
The Guide
Download the recovery image from here: https://dl.twrp.me/kiwi/
Open a terminal in the folder of the downloaded recovery image
Reboot to the main recovery using adb
Code:
adb reboot recovery
Push the recovery image to the external sd card
Code:
adb push ./twrp-3.3.1-0-kiwi.img /external_sd
Open up an adb shell
Code:
adb shell
Within this shell, locate the erecovery partition and save it to a variable for use later. (if the below command doesn't print out anything, try browsing through /dev/block/platform until you find the folders /by-name/erecovery, and then using that path in the below command)
Code:
DEV=$(ls /dev/block/platform/soc.0/7824900.sdhci/by-name/erecovery); echo $DEV
Write the recovery image from the external sd card to the erecovery partition
Code:
dd of=$DEV if=/external_sd/twrp-3.3.1-0-kiwi.img
The installation is now complete! Try it by connecting your phone to a computer, and holding the power + volume up button while turning the phone on.
you start from fastboot mode or eRecovery?
Gentlemen. And Ladies.
First of all I'd like to all thank you for all your work and input as community of xda-developers.
I came here seeking for your help. I am trying to recover the pictures and videos I lost after accidentally performing factory reset. Since the factory reset I havent been using the phone so as least data as possible is overwritten. My phone is rooted and have Busybox installed.
So far I was able to copy a user data disk (I hope I chose correct one: '/dev/block/bootdevice/by-name/userdata' ) via adb from the device to my computer as a file 'userdata.raw' which has around 111gb. I've tried to mount the 'userdata.raw' as a virtual disk using OSFMount - this resulted in appearance of D: disk partition but it's not accessible via Windows Explorer (as it was corrupted). Afterwards I tried to recover data from that mounted D: drive using ActiveUNDELETE but the program doesnt see that D: Disk in the volumes list. Now I am trying to recover using qphotorec which is able to see D: drive as f2fs system. I'm also trying to restore the data directly from that 'userdata.raw' file using qphotorec. But both of these methods result only in outputting the one file: 'f60340268.swf' of around 3gb in size. Overall overview of the whole process is attached on the overwiew screenshot.
{
"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"
}
Now I think there are three scenarios but may be more:
I chose the wrong userdata disk while copying it via adb to on my PC. I picked '/dev/block/bootdevice/by-name/userdata'.
On the screenshot above you can see all the other locations which 'adb shell' -> 'su' -> 'df' outputs (number 1. window in left top corner)
I am doing something wrong while mounting the 'userdata.raw' as a virtual disk thus ActiveUNDELETE can't see it. Or doing something wrong while recovering the data directly from 'userdata.raw'
Contents of '/dev/block/bootdevice/by-name/userdata' is encrypted which results in receiving odd 'f60340268.swf'
file weighing around 3gb. You can see both the contents of 'f60340268.swf' and'userdata.raw' after running strings command on them. See attached Strings screenshots.
It feels like I am almost there but I got stuck and dont know how to approach this any further.
For copying user data disk from mi9t to my pc I followed guides I found here: https://stackoverflow.com/a/41397418
Windows won't explore raw files, you have to use linux or some software to recover your data, like minitool mobile recovery
yaro666 said:
Windows won't explore raw files, you have to use linux or some software to recover your data, like minitool mobile recovery
Click to expand...
Click to collapse
I tried minitool mobile recovery but no luck. I also tried minitool and diskdrill but same results - both of these apps dont see the monuted userdata.raw as D: drive. As it was not there. Windows Disk Management doesnt see it neither.
The only app that's able to see it is qphotorec but it determines file system type as f2fs
anyone?