Related
Nandroid Restore
UPDATE: XDA member Cyanogen has put together a new recovery image that has a Nandroid restore mode built right in. This allows Nandroid to be totally selfcontained on the device. My (and Markazah) program still is good for easy restores if you keep multiple backups because Cyanogen's only restores the latest backup (within the Recovery image GUI anyway.)
Here is a link to his "Pimped out recovery image with new features"
http://forum.xda-developers.com/showthread.php?t=523558
Awsome Cyanogen!
{
"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"
}
Nandroid, created through the efforts of Infernix and Brainaid, is a great tool for backing up your phone. The NANDROID backup process itself is easy to use; however, some folks are not so sure about how to restore these backups back to their phone.
Solution: Nandroid Restore and Nandroid Restore GUI
What it does:
Automates the FASTBOOT portion of the restore.
Nandroid Restore will use FASTBOOT to wipe and then restore the boot, system, userdata and recovery partitions from your phone.
When these tasks are completed, the script then reboots your phone.
What you should expect:
You should end up with a clean restore and all of your data just as you had it when you made your NANDROID backup. EASY!
Directions:
Get your phone into the Secondary Boot Loader (SPL):
Plug your phone into your computer with the USB cable
Take your NANDROID backup off of your SD card and place it in a directory on your PC with a copy of both fastboot.exe and AdbWinApi.dll.
Enter the Secondary Boot Loader (SPL) of your phone by powering down your phone and then powering it back up while holding both the <END> button and the <CAMERA> button.
Restore using NANDrest.bat from the command line:
On your PC, drop to a command prompt and navigate to the directory that you placed your NANDROID backup and fastboot.exe files.
Execute the program "nandrest.bat".
(It is also possible to simpily run this script from the folder without using the command prompt. We all have our preferences after all.)
Restore using Nandroid Restore GUI: (GUI written courtesy of XDA user Markazeh)
Make sure that the 4 Nandroid Restore GUI files are in the same folder as your NANDROID backups.
The GUI will make sure that all required files (the *.img files and Nandrest scripts.)
(See the included pictures)
Reference knowledge:
NANDROID is included with JesusFreke's testkeys modded recovery image. If you have a JF ROM then you probably already have this recovery image and NANDROID.
You must have the Engineering SPL or HardSPL to use FASTBOOT.
Fastboot.exe and AdbWinApi.dll are found in the "tools" folder of the SDK files.
FASTBOOT requires drivers to be loaded into your Windows Operating System. These drivers are in "usb_driver" folder of the SDK files.
Conclusion:
Sure, it's pretty simple and I use it to save time and automate the repair of my latest screw-up and now you can too!
Thank you to Infernix, Brainaid, JesusFreke, Haykuro, TheDudeOfLife, Google and all others that have given their skills and time to the Android community (and subsequently introduced the necessity for NANDROID. )
And thank you to XDA member Markazeh for providing the GUI for Nandrest.bat.
NANDROID post:
http://forum.xda-developers.com/showthread.php?t=459830
Secondary Boot Loader (SPL) post:
http://forum.xda-developers.com/showthread.php?t=455860
will try this, thanks.
Thank you for this.
where is nandrest.bat?
@Sandshrimp: The nandrest.bat file is inside of the nandrest.zip file. You must first unzip nandrest.zip before you will be able to access nandrest.bat.
How is this script working for the rest of you?
Hey nicksen,
i was bored this evening, so i decided to write a little GUI for your Script...
How it works:
- First off, i deleted the ":AREYOUSURE" part in your script, cause a security check is
in the GUI.
- When you start the GUI, it checks if no file is missing and shows missing files
graphically.
- You can only press the "Flash" Button, when every file is in the folder...
I renamed the "nandrest.bat" to "nandrest", that no one can accindently flash the phone by clicking the nandrest.bat. When you click "Flash" the Programm renames the script to "nandrest.bat", that Windows can open it and after your Script has finished it renames it back to "nandrest".
Hope you like it!
Greetings
Markazeh
Markazeh said:
Hey nicksen,
i was bored this evening, so i decided to write a little GUI for your Script...
How it works:
- First off, i deleted the ":AREYOUSURE" part, cause this security check is
handled in the GUI.
- When you start the GUI, it checks if no file is missing and shows missing files
graphically.
- You can only press the "Flash" Button, when every file is in the folder...
I renamed the "nandrest.bat" to "nandrest", that no one can accindently flash the phone by clicking the nandrest.bat, cause i deleted the security check in it... When you click "Flash" the Programm rename the script to "nandrest.bat", that Windows can open it. After your Script is finished it renames it to "nandrest".
Hope you like it!
Greetings
Markazeh
Click to expand...
Click to collapse
nicksen782: Thanks a bunch for the script!
Markazeh: Thanks even more for making a user friendly GUI for it!
This is amazing work, I love this community for this sort of collaborations.
I'll send people this way for easy restore.
@Markazeh -
Thanks! I like the GUI! This is technically my first contribution so I'm pretty tickled that it has been useful so soon. May I suggest that your GUI also check for the presence of AdbWinApi.dll and Fastboot.exe? Oh, and maybe throw my name on your GUI for the script portion? I can rewrite the first post of this thread to include the new GUI.
THANKS!
Yeh, I'm gonna put your name also on the GUI.
I CAN check for the other files, but some people have these files in the win dir....
I have to think about that....
I'll upload the GUI with your name in it in a few hours
May you can give a suggestion on how to handle the problem with the files....
Greets
This works great, thanks guys! Nice job!
Wow! What a great idea. We have all been needing this, IMHO.
How difficult would it be to make it possible to restore only one or more portions of the backup? For example, I did a wipe on the last flash of 1.5, and I want to restore my /data, but not the rest. If you could add that capability, this app would be perfect.
Thanks for your work.
agreed
stellarman said:
Wow! What a great idea. We have all been needing this, IMHO.
How difficult would it be to make it possible to restore only one or more portions of the backup? For example, I did a wipe on the last flash of 1.5, and I want to restore my /data, but not the rest. If you could add that capability, this app would be perfect.
Thanks for your work.
Click to expand...
Click to collapse
I'd prefer not to restore the recovery partition every time for example (it doesn't change too much in my experience outside of flashing to an "official" build). That would be a great tweak!
Ok, ill discuss with nicksen...
Markazeh said:
Ok, ill discuss with nicksen...
Click to expand...
Click to collapse
Thanks. I will keep an eye open for your answer.
Another idea: Could this script, or one like it, possibly be added to 'recovery' so that it shows in recovery mode along with the backup command? It would be really sweet if we could do an 'alt + r' (or whatever) and restore the most recent nandroid backup. I know it is asking alot. But, "to g-e-t, you have to a-s-k." Right?
stellarman said:
Thanks. I will keep an eye open for your answer.
Another idea: Could this script, or one like it, possibly be added to 'recovery' so that it shows in recovery mode along with the backup command? It would be really sweet if we could do an 'alt + r' (or whatever) and restore the most recent nandroid backup. I know it is asking alot. But, "to g-e-t, you have to a-s-k." Right?
Click to expand...
Click to collapse
Well, it should be possible in a way, but we cant do it, cause this script is for windows and android/recovery is linux based...
GUI looks good, another suggestion would be to allow user selection of what is flashed. E.g. Data.img only or just Boot.img and System.img
@ markazeh: There have been some good suggestions. Perhaps checkboxes next to the "found/not found" labels? These checkboxes could default to all checked or all checked except recovery. You could also give the user the option of flashing or not flashing individual images via these checkboxes. Maybe 3 radio buttons at the top labeled: Restore EVERYTHING, Restore ONLY data, Restore EVERYTHING except recovery. Something to that effect. How can I help further?
I personally would really like a NANDROID restore to be available via something like alt+r in the recovery mode such as stellarman has suggested. My assumption is that the recovery mode loads in some of these partitions that we would be trying to restore and that would cause a problem. However, if it were possible to safely unmount these partitions and then restore using flash_image then it might work. The flash_image program however is on the system partition so a ramdrive or other temporary solution would need to be created first. I figure that this is why this hasn't already been done.
Can anybody confirm any of this?
Well the problem is, that i have to split your script in these parts: data flashing, recovery flashing, system flashing and boot flashing, cause i cant go to a part in the script, i can only run a bat.... So im going to split your script in these parts.
Then we have 4 small scripts....
Im going to put 4 Buttons to Flash System, Boot, Data and Recovery.
Should be done Tomorrow.
Version 1.1 here...
All you need is in first post!
Note: I give no guarantee if your phone will brick... But if you use our program properly it wont brick!
awesome
Markazeh said:
Version 1.1 here...
All you need is in first post!
Note: I give no guarantee if your phone will brick... But if you use our program properly it wont brick!
Click to expand...
Click to collapse
You guys rock, thanks!
SGSIII EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows:
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
{
"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"
}
For Linux
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
On the basis of the findings made on the basis of the loss of IMEI and serial numbers, decided to update the backup tool for those who have not lost ...
He will be in addition to backing up and restoring an image backup and recover efs is also a copy of the current modema.
I'm tried only backup, restore me unnecessarily!
Only I9300!!!
DOWNLOAD
SAMSUNG_I9300_EFS_BACKUP_RESTORE_AUTOMATIC
Instructions:
! Need for backup Root access and debugging USB
1. Extract from the zip and run. Bat file
2. Is okay to your PC and follow the menu
Automatically create a text file of all the parameters of the device at the time of the copy
Automatic backup of efs:
* Odin flash file. Tar.md5,
* raw.img
* Tar.gz archive
Automatic naming of files and backup archive version of the firmware
Restore to choose from archives and backup images
Automatic start of Odin and the transition to the flashing mode when selecting Odin Restore
DOWNLOAD
Thanks to:
shoma_81, tester99,
For help and assist in the creation of tool
as i9000 said:
SGSIII EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
* Extract from the archive, connect the device to the USB debugging mode and run your. Bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
For Windows:
http://forum.xda-developers.com/attachment.php?attachmentid=1347629&stc=1&d=1348399433
Click to expand...
Click to collapse
What mode do you need to be in? I guess ADB debugging is also required.
Kangburra said:
What mode do you need to be in? I guess ADB debugging is also required.
Click to expand...
Click to collapse
System settings/Developer options/USB debugging, is all it takes...
Hi, I have tried this but it does not seem to be working for me:
For Windows:
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
Click to expand...
Click to collapse
I have I9300, it is rooted with USB debugging enabled
When I click on Backup_EFS,bat file I get the following message:
Backup EFS
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .
The script closes when I press to continue - no efs.img file
Please tell me what I am doing wrong
Thanks
mmrc01 said:
Hi, I have tried this but it does not seem to be working for me:
I have I9300, it is rooted with USB debugging enabled
When I click on Backup_EFS,bat file I get the following message:
Backup EFS
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .
The script closes when I press to continue - no efs.img file
Please tell me what I am doing wrong
Thanks
Click to expand...
Click to collapse
1 didn't install samsung driver
2 haven't root
3 putn't debug usb...
as i9000 said:
SGSIII EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows:
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
http://forum.xda-developers.com/attachment.php?attachmentid=1347629&stc=1&d=1348399433
For Linux
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
http://forum.xda-developers.com/attachment.php?attachmentid=1347726&stc=1&d=1348403575
Click to expand...
Click to collapse
Thanks.
But a lot of apps which use adb to run "dd if=/of=" and pull the backup image in a folder are already release and work fine. What is new in this batch script ? Thank you anyway. It works correctly.
lelinuxien52 said:
Thanks.
But a lot of apps which use adb to run "dd if=/of=" and pull the backup image in a folder are already release and work fine. What is new in this batch script ? Thank you anyway. It works correctly.
Click to expand...
Click to collapse
Nothing, except that, it's pull image to pc and back, and there is no excess, only backup and restore efs partition
as i9000 said:
1 didn't install samsung driver
2 haven't root
3 putn't debug usb...
Click to expand...
Click to collapse
4 Script is wrong, last 2 adb commands not prefixed by files\
also adb pull will fail on later adb versions since no destination specified, so you need to add . on end, e.g.
files\adb pull /sdcard/efs.img .
Odia said:
4 Script is wrong, last 2 adb commands not prefixed by files\
also adb pull will fail on later adb versions since no destination specified, so you need to add . on end, e.g.
files\adb pull /sdcard/efs.img .
Click to expand...
Click to collapse
fixed, but before it was worked...
as i9000 said:
fixed, but before it was worked...
Click to expand...
Click to collapse
Maybe before when you tested abd was in your PATH and was older revision, anyway nice work, more EFS backup solutions the better.
Odia said:
Maybe before when you tested abd was in your PATH and was older revision, anyway nice work, more EFS backup solutions the better.
Click to expand...
Click to collapse
perhaps...
thanx...
as i9000 said:
perhaps...
thanx...
Click to expand...
Click to collapse
Hi. I located efs.img in my sd card(internal) Nothing on the laptop . Is that were its supposed to be? One more question.....For restoring you are sating to retain the img it must be in the same folder as restore.back...must i copy the efs.img and paste to the same folder were restore.back is on the computer?
Odia said:
Maybe before when you tested abd was in your PATH and was older revision, anyway nice work, more EFS backup solutions the better.
Click to expand...
Click to collapse
None yet, the first time was right - the first version back
art_arev said:
Hi. I located efs.img in my sd card(internal) Nothing on the laptop . Is that were its supposed to be? One more question.....For restoring you are sating to retain the img it must be in the same folder as restore.back...must i copy the efs.img and paste to the same folder were restore.back is on the computer?
Click to expand...
Click to collapse
Download new...
as i9000 said:
Download new...
Click to expand...
Click to collapse
Hi Downloaded new...The old version at least was backing in sdcard. The new download says adb not recognised external or internal command.
I have root,debuging on, and all the samsung drivers ....but.........its failing
art_arev said:
Hi Downloaded new...The old version at least was backing in sdcard. The new download says adb not recognised external or internal command.
I have root,debuging on, and all the samsung drivers ....but.........its failing
Click to expand...
Click to collapse
Connect device and run command console and paste
Code:
adb shell
What happend?
as i9000 said:
Connect device and run command console and paste
Code:
adb shell
What happend?
Click to expand...
Click to collapse
exactly the same in command prompt: adb not recognised..blabla....( I hope we are talking about Windows version the rar download)
art_arev said:
exactly the same in command prompt: adb not recognised..blabla....( I hope we are talking about Windows version the rar download)
Click to expand...
Click to collapse
I make tool with new ADB
Dowload...
Mast work
as i9000 said:
I make tool with new ADB
Dowload...
Mast work
Click to expand...
Click to collapse
Works like a charm:good::good::good::good::laugh: Tks your a Star. Spasibo bolshoye
art_arev said:
Works like a charm:good::good::good::good::laugh: Tks your a Star
Click to expand...
Click to collapse
My pleasure!
{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:
GUIDE how to backup Verizon Developer Device aboot Partition
All Samsung Developer Devices are identical to retail devices with exception of one partition "aboot". What is all this fuss aboot? This partition holds the magic that unlocked your bootloader. It has a signed SHA256 key that a thousand Monkeys could not crack. If this partition is overwritten or corrupt the DE phone could brick, and bootloader will lock. Welcome to retail. This partition is device ID specific and coded to the device with super encryption. If this partition is backed up prior to corruption, it could be possible to restore a locked developer device. Some discussion of DE's aboot here and here
As of this writing several DE owners were smart enough to backup aboot, several were able to restore their unlocked bootloader. They were able to restore with the help of several XDA devleopers that were able to take the pre-saved aboot, and make it into an Odin flashable tar. It was reported that EFS Professional could create an Odin flashable aboot.tar.gz, that doesn't need any prior modifications. This info was incorrect, all backups of aboot will require modification prior to flashing. If you accidentally "Retail" your DE, post to this thread, and myself or one of the other devs will fix your backup. There is risk involved with restore, so please don't perposly flash your device to retail.
(No you can't flash aboot on your retail phone)
There are several ways to backup this unique partition, these procedures are not real difficult, but care should be taken. One method is by using ADB. Big learning curve, but rewarding. install Google SDK and use ABD [ADB Guides] Setup and run ADB, and backup the partition using dd command. This is a computer to Android terminal interface via USB. If you have used Linux scripts, this should easy peasy once ADB is functional. Copy and paste a script to copy aboot to SD, and the rest of the partitions using the ADB Method below.
You could even copy aboot to your phone's SD using your recovery file editor, or use ADB pull (permissions, mount, could make this tough though).
There is a cool program built by XDA contributor @lyriquidperfection, it's called EFS Professional It is a very powerful tool, it runs on windows computers, and uses a GUI, no scripts, just point and, click, click, click Easy Method.
Both interfaces require ROOT, and use Busybox. SuperSU, and busybox must be installed on your device prior, as well as Samsung drivers (Direct link to VZW Note 4 DE )
I like BusyBox Tools by Stephen (Stericson), or try Busybox On Rails
Disclaimer: If you are careful, study a bit, and follow direction closely there isn't much risk. Please be careful, these tools are capable of bricking your phone if you blindly explore other commands. If you run into problems, Post to this thread, someone will help you. If you go poking around the advanced user commands and mess it up, good luck. Don't hate on me if you do something stupid.
1. ADB Method Here is a quick guide that I made while backing up my note-4 DE. I point out the path to the partitions on Note-4. The VZW note-4 aboot partition is mmcblk0p7 This location and partition number are different in other DE models. This backup will need to be made flash-able if it's ever needed.
2. EFS Professional Easy Method (This guide will work for the other developer devices too. Tested on Note-3 & Galaxy S5 Developer Editions)
Download EFS Professional on windows computer, install EFSProfessional. This program has an imbedded version of ADB built in (don't run any other ADB programs at the same time)
Make sure USB debug is checked under phone's setting "Developer options", tick "USB debugging" (might already be ticked) If "developer options" tab is missing from "Settings", go to "Settings", "About phone", then tap, tap, tap, on "Build number" do it spasticly until it unlocks, aboot 7 times. ha ha Canada
(Click on the attached thumbnails to enlarge them to huge)
View attachment 3075958 View attachment 3075959
Hook the phone to USB & computer prior to running EFSPro. Keep an eye on the phones screen when the program starts, a few popups will probably pop up on the phone, allow your computer's RSA key, tic the always remember, and allow access to your computer. SU will pop up on the screen too, grant access. (If it doesn't connect, check phone's drop down for connection options. Worst case, toggle usb debug off/on while attempting connection in efspro).
{
"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"
}
Click on EFS Professional, The only folder you need to use is under the backup tab. Don't mess around under the other tabs, just click on backup.
View attachment 3048807 View attachment 3125707
Under the Backup Tab select "manage" Then select "Create New". Now you will create a PIT file, the map of your DE's system.
View attachment 3075885 View attachment 3075886
Type in the File name, display name, and description. I typed "note-4" in all three boxes.
View attachment 3181033
Click "Read Pit" a popup will nag, just click "OK" and continue, device written, click "OK", Then hit "Save".
View attachment 3075888
You now have your DE's PIT, the road map to your system partition. Ready to backup aboot? Lets go, press "Manage" then "refresh". Now your new pit should be visible under the "manage" drop down.
View attachment 3075899
From the drop down find your device (Note-4), and "select" it.
View attachment 3075900 View attachment 3075901
"Deselect all", then tic aboot only (You don't want to save all in one zip, it's +3GB, and will take forever, and most likely choke on it's self. Later after backing up aboot you can go back, and save the other partitions that aren't backed up by TWRP).
View attachment 3075902 View attachment 3075911
Click "backup". When it's finished you should now have two copies of aboot zipped up in a nice file (Note-4_xxxxxxxx.tar.gz) in EFSProBackup folder on your internal SD (or External SD), and on your computer both locations should contain a TAR of aboot. You can rename it "MyNote4_aboot.tar.gz". Later you should also manually move this to external SD using Root Explorer or ES File explorer
View attachment 3075912
Now is the time to donate to @lyriquidperfection , or a least go back to his OP and hit the thanks button.
View attachment 3075913
If a stock Tar is accidentally flashed, locking the boot loader, the phone won't be able to run EFS Pro because it requires root, and busybox, and may not boot anyway. If you do somehow lock your boot loader. Post your request for help to this thread, someone will PM you asking for your aboot backup, one of the devs here will make your aboot odin flashable, and send it back ready to go.
*Odin can't flash all the partitions, only the ones that are mapped in your PIT file. Please do a second backup, make a combined zip, select the following: aboot.mbn, NON-HLOS.bin, rpm.mbn, sbl1.mbn, sdi.mbn, tz.mbn. This will up your insurance policy to premium
Now that your are "out of the woods", go back into EFSPro and backup all partition blocks, minus a few huge ones that are already backed up by your recovery. I back up all blocks on a fresh DE image, before installing a bunch of apps (recovery, SuperSU, and Busybox). If you have a bunch of stuffs already installed you might want to skip blocks: 25 Cache, and 27 User Data. They are huge, and redundant if you already backed up everything in TWRP. You do have everything backed up in TWRP, right???
Eye glazing stuffs: The backups can be un-zipped to a tar, aboot.mbn.tar. Then unzipped again to reveal the unzipped partitions. These can be selectively modified into an Odin flash-able tar.md5. This part should be done by a developer because some hex editing and special software adds an md5 checksum .
Don't be the one that flashes a stock image tar, or allows a repair kiosk to touch your precious. Hopefully the insurance policy you just made won't ever have to be claimed.
Check back for correction, and updates. Please post your results good, or bad to this thread.
THANKS!
Nice guide I will have to do this
radionerd said:
Samsung Developer Devices are identical to retail devices with exception of one partition "aboot". If this partition is overwritten or corrupt the phone will brick, and bootloader will lock. This partition is device ID specific and coded to the boot partition, and device. If both of these partitions are backed up prior to corruption, it would be possible to restore a locked developer device.
There are several ways to backup these unique partitions, these procedures are not real difficult, but care should be taken. One method is by using ADB. install Google SDK and use ABD [ADB Guides] Setup and run ADB, and backup the partitions using dd command. This is a computer to phone terminal interface via USB. If you have used Linux scripts, this should easy peasy once ADB is functional.
There is a cool program built by XDA contributor lyriquidperfection, it's called EFS Professional It is a very powerful tool that runs on windows computers, and uses a GUI, no scripts, just point and click
Both interfaces use Busybox, so it must be installed on your device prior.
I like BusyBox Tools by Stephen (Stericson), or Busybox On Rails
Disclaimer: If you are careful, study a bit, and follow direction closely there isn't much risk. Please be careful these tools are capable of bricking your phone if you explore other commands. If you run into problems, I will try to help.
1. ADB Method Here is a quick guide that I made while backing up my note-4 DE. The VZW note-4 aboot partition is mmcblk0p7 This location and name are different in other models.
2. EFS Professional Method
Download EFS Professional on windows computer, install it. This program has a imbedded version of ADB built in (don't run any other ADB programs at the same time)
Make sure USB debug is checked under phone's setting, Developer options tick USB debugging (should already be ticked) If developer options is missing, go to settings, About phone, tap tap tap "Build number" spasticly until it unlocks.
Hook the phone to USB prior to running EFSPro. Keep an eye on the phones screen when the program starts, a few popups will probably pop up on the phone, Tic the always remember, and allow access to the computer. SU will pop up on the screen too, grant access.
View attachment 3048807
(Click on the attached photos to enlarge them)
The only folder you need to use is under the backup tab. Don't mess around under the other tabs, just backup.
Under the Backup Tab select "manage" Then select "Create New". Now you will create a PIT file, and grab a map the DE system.
View attachment 3048818
Type in the File name, display name, and description. I typed "note-4".
Then Click "read device", it should look like the picture below. Then hit "Save".
View attachment 3048835
You now have a Note-4 PIT, and map. Ready to backup aboot and boot, just press "Manage" then "refresh". Now your new pit should be visible under "manage drop down".
From the drop down find your device, and "select" it.
View attachment 3048845
"Deselect all", then tic aboot and boot only (You don't want to save all in one zip, it's Gigs, and will take forever, and most likely choke on it's self later you can go back and save the other partitions that aren't backed up by TWRP).
Then click "backup", when it's done you should now have an efsprofessional folder on your internal SD, and on your computer that contains a TAR of aboot and boot.
View attachment 3048866
Now is the time to donate to Liquid Perfection, or a least go back to his OP and hit the thanks button.
This is a ruff work in progress, but it's getting late, so check back for typos, correction, and updates. Please post your results good, or bad to this thread.
THANKS!
Click to expand...
Click to collapse
This is great work. Thanks so much. We've already seen a couple of our fellow Note 4 DE owners need a aboot backup to restore their unlocked bootloader. This is a must for any DE owner. It's like an insurance policy.
How do you restore?
Once you use the dd command in terminal emulator or in adb, or once you have an efs-professional backup of your aboot, so you have an aboot.mbn or aboot.bak, how do you restore it if you have inadvertently, let's say, flashed a retail edition aboot by flashing a retail full tar file from Odin for instance? I bought a Note 3 DE last year, and I made a copy of my aboot as soon as I got it, using the dd command, the file is about 2mb, but so far I don't know how to restore it if it does get the retail aboot installed on it by accident. Could you please shed some light on the restoration procedure as well?
Also, I know if you backup your /efs partition on twrp, it can't be restored if you mess it up, supposedly that's what makes the phone tick and gives it its identity, I have read about a few people on this forum that accidentally deleted their /efs partition and their phone never worked right after that, like their unlock screen wouldn't work and a lot of other stuff was messed up, as they described. If you make a /efs backup with efs-professional, could it be restored correctly if the /efs partition gets corrupted by accident? I don't really know why anyone would need to delete that partition, but I think some rom or modem update procedure did it, but just in case it happens.
Thank you for the great work and tutorial
newuser134 said:
Once you use the dd command in terminal emulator or in adb, or once you have an efs-professional backup of your aboot, so you have an aboot.mbn or aboot.bak, how do you restore it if you have inadvertently, let's say, flashed a retail edition aboot by flashing a retail full tar file from Odin for instance? I bought a Note 3 DE last year, and I made a copy of my aboot as soon as I got it, using the dd command, the file is about 2mb, but so far I don't know how to restore it if it does get the retail aboot installed on it by accident. Could you please shed some light on the restoration procedure as well?
Click to expand...
Click to collapse
Hopefully no one will have to be the Guinea Pig, and restore a corrupted aboot from accidentally flashing a retail TAR on their DE. As far as I know only one guy has tried aboot restore successfully, with big help from a dev who made his prior saved aboot flashable.
As far as I know aboot restore is untested with efsprofessional, I have successfully restored other partitions using efspro on my note-3 DE.
Unfortunately every DE version that has been released has had several folks overwrite aboot; accidentally, or in desperation flash retail Tars, by themselves, by Samsung service center, or at a retail store kiosk, like bestbuy.
Your DE warranty, and insurance is your backups. Samsung won't fix your corrupted system, if they do (only if no knox trip 0x0), you will receive your phone with a retail image put on it. Having an aboot backup could possibly bring it back to DE.
newuser134 said:
Also, I know if you backup your /efs partition on twrp, it can't be restored if you mess it up, supposedly that's what makes the phone tick and gives it its identity, I have read about a few people on this forum that accidentally deleted their /efs partition and their phone never worked right after that, like their unlock screen wouldn't work and a lot of other stuff was messed up, as they described. If you make a /efs backup with efs-professional, could it be restored correctly if the /efs partition gets corrupted by accident? I don't really know why anyone would need to delete that partition, but I think some rom or modem update procedure did it, but just in case it happens.
Click to expand...
Click to collapse
Been there done that, Most of the guys that had efs messed up on Note-3 DE, including myself, we used the first T-mobile TWRP version that didn't backup the right efs partition, upon TWRP restore we had major problems, some of us compounded the problems, me too TWRP was quickly updated, and a few of us figured out ways to rebuilt /efs.
"What I learned was backup your backup, then back that up too" I do complete TWRP backup as soon as rooted, DD of all partitions, then backup all partitions, except a few huge partitions using efspro.
newuser134 said:
Thank you for the great work and tutorial
Click to expand...
Click to collapse
Thanks WIP, hope to add soon "copy and paste" scripts for all the partitions.
Thanks for the instructions. I hope to never need it, but I will follow this procedure just to be on the safe side.
Doesn't TWRP handle this by ticking on the EFS checkbox when making a backup?
solidunit said:
Doesn't TWRP handle this by ticking on the EFS checkbox when making a backup?
Click to expand...
Click to collapse
TWRP does backup EFS, but not aboot, or a handful of other partitions. EFS pro can backup all partitions.
radionerd said:
Type in the File name, display name, and description. I typed "note-4".
Then Click "read device", it should look like the picture below. Then hit "Save".
View attachment 3048835
Click to expand...
Click to collapse
When I get to the "read device" step I get an error saying it cannot find the pit file in the EFS folder. What am I missing? Thanks
tfly212 said:
When I get to the "read device" step I get an error saying it cannot find the pit file in the EFS folder. What am I missing? Thanks
Click to expand...
Click to collapse
Did you click on the Manage box and select "create new"
Then read device
Then name note-4 on device name, display name, and description, then click save
go back to manage, click refresh
Then go to device filters, find your note 4
de-select all, then select aboot
Then click backup.
Now you should have a "double zipped" file of aboot in your computer efsprofessional folder, and on your sdcard.
Attached a few pictures from my note 3
radionerd said:
Did you click on the device filter box "v" and select "create new"
Then read
Click to expand...
Click to collapse
I did not the first time...but once I did it worked perfectly, thank you. I didn't think to click the dropdown as I knew Note 4 wasn't going to be on there. Might want to add that line to the instructions in case anyone else runs into the same issue.
All good now...going to donate to the dev tonight.
tfly212 said:
I did not the first time...but once I did it worked perfectly, thank you. I didn't think to click the dropdown as I knew Note 4 wasn't going to be on there. Might want to add that line to the instructions in case anyone else runs into the same issue.
All good now...going to donate to the dev tonight.
Click to expand...
Click to collapse
Great!
I will go look at the wording of the OP
tfly212 said:
I did not the first time...but once I did it worked perfectly, thank you. I didn't think to click the dropdown as I knew Note 4 wasn't going to be on there. Might want to add that line to the instructions in case anyone else runs into the same issue.
All good now...going to donate to the dev tonight.
Click to expand...
Click to collapse
Buy him some nappies for his kid
Thanks man,
I updated my OP with 27 8"x10" color glossy photos with circles and arrows
radionerd said:
Buy him some nappies for his kid
Thanks man,
I updated my OP with 27 8"x10" color glossy photos with circles and arrows
Click to expand...
Click to collapse
Will do...I have a little one also, and while a beer sounds better, the way they go through diapers is staggering.
How do I find my computers RSA key? I am on windows 8.1?
texasez said:
How do I find my computers RSA key? I am on windows 8.1?
Click to expand...
Click to collapse
You don't need to know the computer's RSA key, The RSA pop-up comes up on your phone when entering ADB mode. The key is in the pop-up, Just grant access.
Is the "sbl1bak" a backup of the "sbl1" ????????
larrycjr said:
Is the "sbl1bak" a backup of the "sbl1" ????????
Click to expand...
Click to collapse
Yup,
However sb1bak is empty on my note 4
Easy look at Note 4 partition Mounts by-name (trltevzw)
aboot -> /dev/block/mmcblk0p7 (2048KB)
apnhlos -> /dev/block/mmcblk0p1
boot -> /dev/block/mmcblk0p17
cache -> /dev/block/mmcblk0p25
carrier -> /dev/block/mmcblk0p26
dbi -> /dev/block/mmcblk0p5
ddr -> /dev/block/mmcblk0p6
efs -> /dev/block/mmcblk0p13
fota -> /dev/block/mmcblk0p19
mdm1m9kefs1 -> /dev/block/mmcblk0p14
mdm1m9kefs2 -> /dev/block/mmcblk0p15
mdm1m9kefs3 -> /dev/block/mmcblk0p10
mdm1m9kefsc -> /dev/block/mmcblk0p16
misc -> /dev/block/mmcblk0p20
modem -> /dev/block/mmcblk0p2
pad -> /dev/block/mmcblk0p11
param -> /dev/block/mmcblk0p12
persdata -> /dev/block/mmcblk0p23
persist -> /dev/block/mmcblk0p22
recovery -> /dev/block/mmcblk0p18
rpm -> /dev/block/mmcblk0p8
sbl1 -> /dev/block/mmcblk0p3
sbl1bak -> /dev/block/mmcblk0p4
ssd -> /dev/block/mmcblk0p21
system -> /dev/block/mmcblk0p24
tz -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p27
I finally get past the RSA problem by using installer mode on phone but the phone auto changes back to media device and then efs pro does not recognize the phone. I tried camera (ptp) mode but it will not go past pressing the device info button on efs pro. How do I make the phone stay in installer mode. I keep getting popups wanting me to install the verizon software but I did not install.
How do I keep the installer mode active?
Your obviously on the dev edition?? Correct? If so if it's not to much to ask will you send me a copy of your sbl1. Please.
Sent from my SM-N910V
SPECIAL THANKS TO
@Lunarixus on XDA
I wouldn't have figured out how to maneuver the pixel 2 XL partition table without him.
WARNING!
This tutorial only applies to Taimen (2XL). There's already another tutorial for Walleye, click here for link. I need Walleye testers so please join the telegram group if you can! Google Pixel Development Group.REQUIREMENTS:
Taimen with unlocked bootloader
Updated adb & fastboot binaries
GNU parted for ARM64. Get it here: https://guidedflame.dev/parted
Custom recovery for Taimen with adb support. Get it here: Recovery .img Download
vbmeta image for your device: Download vbmeta.img
STEPS:
1. Enable USB Debugging
2. Reboot into fastboot modeadb reboot bootloader
3. Boot into the recoveryfastboot boot path/to/recovery.img(optional) you can flash TWRP permanently if you wish. fastboot flash boot_a path/to/recovery.img and fastboot flash boot_b path/to/recovery.img DO NOT FLASH TWRP. JUST BOOT TO IT.
4. In TWRP...
If it asks you to decrypt your data, do it.
If it asks you to swipe for RW permissions on system partition, do it.
Unmount all partitions. Click on Mount, then un-tick everything.
5. Back to your PC. Copy parted to /sbin.adb push path/to/parted /sbin
6. Enter shell mode.adb shell
7. Change permissions of parted.chmod 777 /sbin/parted
8. It's time to use parted!We mainly use 3 commands. Here's how they work.
rm x - Removes partition number x. For example: rm 13
Click to expand...
Click to collapse
mkpart name fstype startUNIT finishUNIT - Makes a partition where fstype is the type of filesystem (like ext4), start is the beginning of the partition, and finish is the end of the partition. UNIT is the unit for the start and finish arguments (like KB, MB, B, or s) For example: mkpart system_a ext4 32KB 1000KB
Click to expand...
Click to collapse
name x part_name - Names partition number x and gives it part_name as a label. For example: name 14 userdata
Click to expand...
Click to collapse
In your terminal (still in shell mode), type parted /dev/block/sda
It should greet you with a welcome screen. Type p free, and save what you get in a screenshot or text file (on windows you can copy and paste in notepad, or use Snipping Tool, since it's installed by default). THIS IS VERY IMPORTANT IF YOU GET STUCK!!!!
{
"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"
}
We have to delete all partitions starting from the bottom until system_a. Make sure to keep the screenshot or text file you saved earlier from p free, because we are gonna need it to recreate the deleted partitions later. YOUR PARTITION SCHEME MIGHT BE DIFFERENT THAN THIS. Make sure to STOP after system_a is removed.
rm 13
rm 12
rm 11
rm 10
rm 9
rm 8
rm 7
Once you are done, it's time to recreate those partitions. We do it in the proper order now, starting from system_a. Refer to the screenshot or text file you saved earlier. We will increase the partition size to 3GB to be able to boot most GSIs, including Android 12. If it says that the partition isn't aligned, type Ignore.
mkpart system_a ext4 169MB 4269MB
mkpart system_b ext4 4269MB 8369MB
mkpart pstore 8369MB 8379MB
mkpart aes_a 8379MB 8380MB
mkpart aes_b 8380MB 8381MB
mkpart align_parti 8381MB 8391MB
mkpart userdata ext4 8391MB 62400MB (if you have 128GB Taimen, do mkpart userdata ext4 8391MB 126300MB)
Check your partitioning with p free and compare with your screenshot/text file. It should be similar, with some extra free spaces.
Time to name the partitions.
name 7 system_a
name 8 system_b
name 9 pstore
name 10 aes_a
name 11 aes_b
name 12 align_parti
name 13 userdata
Check your partitioning again with p free. It should show the named partitions. If everything looks good to you, leave parted.
quit
9. Exit shell mode.
exit
10. Reboot into fastboot mode
adb reboot bootloader
11. Format all the partitions we made
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (that you downloaded earlier)fastboot erase system_afastboot erase system_bfastboot erase pstorefastboot erase aes_afastboot erase aes_bfastboot erase align_partifastboot erase userdatafastboot format:ext4 system_afastboot format:ext4 system_bfastboot format:ext4 userdataAnd that's all!
NOTICE: At this point, the partitions should repopulate themselves on the next boot. If they don't, flash latest Android 11 stock ROM (And flash it using flash-all.bat for windows/flash-all.sh for linux) OR flash dotOS (it has a better vendor, so FP works).
Flashing the stock ROM won't undo your partitioning. You will keep your 3GB system partition!
Click to expand...
Click to collapse
You can start immediately flashing GSIs/Android 12. If you're stuck on splash screen, that means the partitions didn't repopulate correctly. Follow the advice above!
If you need Android 12 GSI, here.
If you have any questions, or accidentally brick your device, join the telegram group for direct support.
Had issues with:
Almost all partition steps complaiend about not beign able to inform the kernel and i had to ignore the warnings all the way through....so just be aware, not for the faint of heart
fastboot erase aes_a
fastboot erase aes_b
fastboot erase align_parti
fastboot erase userdata
fastboot format:ext4 system_a
fastboot format:ext4 system_b
fastboot format:ext4 userdata
Aka:
$ fastboot erase pstore
Erasing 'pstore?' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Booted TWRP and at least fixed the data and system parts - Ext4 to Ext2 to Ext4 again....properly mounted
Tried flashing A12...nope
Flashed A11 Stock (to hopefully fix partitions)..booted
Now back in fastboot erasing system (a/b) and userdate and trying to flash to A12 again
Nope, that didnt work...boot warning - your device is corrupt...
Flashing back to A11 again (hopefully)
Update, back in A11....
73sydney said:
Had issues with:
Almost all partition steps complaiend about not beign able to inform the kernel and i had to ignore the warnings all the way through....so just be aware, not for the faint of heart
fastboot erase aes_a
fastboot erase aes_b
fastboot erase align_parti
fastboot erase userdata
fastboot format:ext4 system_a
fastboot format:ext4 system_b
fastboot format:ext4 userdata
Aka:
$ fastboot erase pstore
Erasing 'pstore?' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Booted TWRP and at least fixed the data and system parts - Ext4 to Ext2 to Ext4 again....properly mounted
Tried flashing A12...nope
Flashed A11 Stock (to hopefully fix partitions)..booted
Now back in fastboot erasing system (a/b) and userdate and trying to flash to A12 again
Nope, that didnt work...boot warning - your device is corrupt...
Flashing back to A11 again (hopefully)
Update, back in A11....
Click to expand...
Click to collapse
Are you sure you unlocked properly?
fastboot flashing unlock_critical
Also what's your device and storage config?
Dollscythe said:
Are you sure you unlocked properly?
fastboot flashing unlock_critical
Also what's your device and storage config?
Click to expand...
Click to collapse
I have flashed a few ROMs in my time (since early Android days)
Im usually on a custom ROM, only flashed back to stock 11 to fix the issues with the aprtitions and then not being able to boot A12 when i got those fixed....and after i got the boot message my device was corrupt
So unlocked properly: hells yes
device: Pixel 2XL
storage config : (now) 3Gb system partitions
but A12 will not flash on it and boto successfully, it doesnt detect /data, and reports corruption.
now back on ABC ROM, from where i started the night, and all is well....just restoring my apps via Migrate
73sydney said:
I have flashed a few ROMs in my time (since early Android days)
Im usually on a custom ROM, only flashed back to stock 11 to fix the issues with the aprtitions and then not being able to boot A12 when i got those fixed....and after i got the boot message my device was corrupt
So unlocked properly: hells yes
device: Pixel 2XL
storage config : (now) 3Gb system partitions
but A12 will not flash on it and boto successfully, it doesnt detect /data, and reports corruption.
now back on ABC ROM, from where i started the night, and all is well....just restoring my apps via Migrate
Click to expand...
Click to collapse
sometimes it's fastboot version issue.
try using the fastboot i linked.
also, did you flash the vbmeta as instructed in the GSI flash guide?
aside from that, now that your system is 3GB, you can definitely flash android 12. although i advice against it, until beta 4, it's buggy right now.
Dollscythe said:
sometimes it's fastboot version issue.
try using the fastboot i linked.
also, did you flash the vbmeta as instructed in the GSI flash guide?
aside from that, now that your system is 3GB, you can definitely flash android 12. although i advice against it, until beta 4, it's buggy right now.
Click to expand...
Click to collapse
I was using what i thought were the latest platform tools, but i just checked and it was 30.0.4 (July last year)
Next time i try it, ill try with the newer platform tools
I did try vbmeta...no change, device corrupt
ill take the 3Gb system part as a win for now
It took a lot of searching to find what i was doing wrong. once parted was up the rest was really straightforward. I do not understand why i could not push using the command listed here however for some reason a post on a different site showed how to create a temp folder in the sdcard, it went first try. thank you for an educational (for me) adventure. i really dug learning some shell commands and putting them to good use.
jonpjingleheimler said:
C:\Users\timot\Desktop\Minimal ADB and Fastboot>adb push "C:\Users\timot\Desktop\Minimal ADB and Fastboot\parted"\sbin
adb: usage: push requires an argument
tried the command with the latest platform tools and get the same crap. googling how to use adb push was absolutely pointless. im past being embarrassed now im just getting, frustrated
Click to expand...
Click to collapse
If you have parted in the same path youre running adb from (and you seem to be) then:
adb push parted /sbin
theres no need to quote the entire file path when in same directory, and watch those slashes...
A lot of us managed to flash android 12 by the way. At this point 90% of bugs are fixed.
you can try it already, if you can live with a non-working sound in calls.
73sydney said:
If you have parted in the same path youre running adb from (and you seem to be) then:
adb push parted /sbin
theres no need to quote the entire file path when in same directory, and watch those sla
Click to expand...
Click to collapse
Dollscythe said:
A lot of us managed to flash android 12 by the way. At this point 90% of bugs are fixed.
you can try it already, if you can live with a non-working sound in calls.
Click to expand...
Click to collapse
I really need phone for this device. The Dot OS listed in op is a really nice ROM. I tried installing the GSI with gapps but I got the not enough space message. I'm rather certain I followed the repartition steps listed but even after flashing a vanilla ROM then flashing gapps I still get not enough space message. Pico is 106mb my free space shows 64mb. I tried resize and repair but got error message. I'm sure if I mess around enough I can get what I'm after. I'm grateful for all your work.
jonpjingleheimler said:
I really need phone for this device. The Dot OS listed in op is a really nice ROM. I tried installing the GSI with gapps but I got the not enough space message. I'm rather certain I followed the repartition steps listed but even after flashing a vanilla ROM then flashing gapps I still get not enough space message. Pico is 106mb my free space shows 64mb. I tried resize and repair but got error message. I'm sure if I mess around enough I can get what I'm after. I'm grateful for all your work.
Click to expand...
Click to collapse
show me your current partition scheme.
do the steps until step 8, then type in 'p free' in the shell.
then show me.
Dollscythe said:
show me your current partition scheme.
do the steps until step 8, then type in 'p free' in the shell.
then show me.
Click to expand...
Click to collapse
Thank you for reply. I will definitely do that after work
Dollscythe said:
show me your current partition scheme.
do the steps until step 8, then type in 'p free' in the shell.
then show me.
Click to expand...
Click to collapse
jonpjingleheimler said:
View attachment 5376515
Click to expand...
Click to collapse
Thank you, that looks fine to me.
you have exactly 3.1 GB sized partition. Is there an issue with TWRP not detecting all that size?
Also, dotOS contains gapps already and as such it takes a lot of space. So maybe that's why you arent able to fit in more GAPPS.
What you could try is flashing a GSI and installing gapps. Try lineageOS as well.
By the way, if you still suspect it's a size limitation...you can redo the tutorial, but when recreating system_a and system_b, just make the size bigger.
3.5GB or 4GB should be plenty. There's nothingg stopping you from picking any size for any of these partitions as long as they are bigger than what they were originally.
If you require guidance when creatingg the partition do let me know. I am also available in private messaging or through my telegram group for assistance. I wish you luck!
Dollscythe said:
Thank you, that looks fine to me.
you have exactly 3.1 GB sized partition. Is there an issue with TWRP not detecting all that size?
Also, dotOS contains gapps already and as such it takes a lot of space. So maybe that's why you arent able to fit in more GAPPS.
What you could try is flashing a GSI and installing gapps. Try lineageOS as well.
By the way, if you still suspect it's a size limitation...you can redo the tutorial, but when recreating system_a and system_b, just make the size bigger.
3.5GB or 4GB should be plenty. There's nothingg stopping you from picking any size for any of these partitions as long as they are bigger than what they were originally.
If you require guidance when creatingg the partition do let me know. I am also available in private messaging or through my telegram group for assistance. I wish you luck!
Click to expand...
Click to collapse
Im relieved the partitions look as they should. thank you for all of your knowledge and advice. I can go forward with a lot of useful info
Unable to Download vbmeta.img . Getting 522 error.
zeroerror said:
Unable to Download vbmeta.img . Getting 522 error.
Click to expand...
Click to collapse
zeroerror said:
Unable to Download vbmeta.img . Getting 522 error.
Click to expand...
Click to collapse
You can extact vbmeta from factory image for pixel 2xl. https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004.a1-factory-2f5c4987.zip
Or find one from the last taimen (Pixel 2XL) factory image attached to this post...saves downloading 1.6gb
73sydney said:
Or find one from the last taimen (Pixel 2XL) factory image attached to this post...saves downloading 1.6gb
Click to expand...
Click to collapse
It's always better to have the full stock image in hand especially when dealing with repartitioning. You never know