Related
I download the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
was the INIT.D HACK installed correctly?
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
I don't know what to do now.
thanks
you need to either toggle safe system off, or flash a ROM to use for safe system, and then flash the init.d hack
and my suggestion is to flash CM7 or Monster, Mav, SD3, Liberty, Etc. Im on CM7, works very nice http://hash-of-codes.blogspot.com
thanks MrJudylicious,
but sorry don't know how to do it...
this is my first android phone i just follow the steps that Chaoticweaponry told on the other topic:
"1: Root your Droid 3 using the 1 click root method (search around XDA/Google)
2: Download Safestrap from Hashcode's website. - USE BOOTSTRAP IF YOU'RE ON STOCK/NON-SAFESTRAP ROMS
3: Install the .apk file using AppInstaller from the Android Market.
4: Start Safestrap (or similar) and allow superuser permissions - then install recovery.
5: Get Download All Files from Android Market.
6: Download the init.d hack.
7: Turn your phone off.
8: Press m + power, scroll down to BP Tools (volume down key) and select it (volume up key)
9: Scroll down to install zip from SD card (select using power button)
10: Go to internal sd card - downloads folder.
11: Find the init.d file, and install it.
12: Reboot the device (go to main menu on safestrap (or similar) recovery)
13: Done."
I don't know what is flash a ROM...
so the init.d hack is not working?
as I said, I put system safe on and installed complete.. then it won't boot I don't know why..
so I put system safe off and it booted.
can you tell me what to do step by step please?
i'm thankful
Pedro
ps: I got one app called "droid3bootstrap" but idk if it will serve.
if you can, tell me what I need to download and what I should do...
sorry for the inconvenience
thanks
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
MrJudylicious said:
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
Click to expand...
Click to collapse
Thanks a lot MrJudylicious,
but what is this 'CM7 11-16 build'? what will it do on the phone?
I just wanted to install INIT.D HACK because I read that saves battery.
cm7 is a stripped down very functional, very fast operating system. if you want stock, you can visit his hash-of-codes.blogspot.com and under android downloads you can download the stock 5.6.890 /root + superuser ( http://goo.gl/3bTpJ ). you cannot flash to teh main system with safestrap, but you can with bootstrap. you could have issues installing more than one *strap, which is why i suggested you keep safestrap.
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
pedroramos said:
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
Click to expand...
Click to collapse
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
ChaoticWeaponry said:
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
Click to expand...
Click to collapse
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
pedroramos said:
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
Click to expand...
Click to collapse
This is why this didn't work
You install safestrap, it allows you to install roms to your /preinstall directory (directory for windows users ^^). You don't install a rom but install the init.d files to /preinstall and then try to boot off /preinstall (because safestrap is enabled). Obviously that wont work because when your phone boots it looks for system files in /preinstall but all that's there is the init.d hack.
You uninstalled safestrap, installed koush' and then installed the init.d files to /system which your phone actually runs off. At that point the init.d is correctly installed.
Another option(the one that people are telling you here) is to install safestrap, enable safestrap, install your rom to the safestrapped system and then install your init.d hack on top of the rom you just installed which is also correct.
it's 2 different ways to do the same thing slightly differently(although with the second method you basically have 2 /systems). I hope this helps clear up your confusion.
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
pedroramos said:
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
Click to expand...
Click to collapse
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
You can test that this works on your roms by flashing and then checking for a ".ItWorks" file in /data partition. If you are using ES File Explorer or similar you will need to be sure to allow it to show hidden files, otherwise you won't see this file.
Click to expand...
Click to collapse
In his development thread. This might work for you.
Willis111 said:
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
In his development thread. This might work for you.
Click to expand...
Click to collapse
I opened root explorer and there was a ".itworks"(with a medal of sheriff) on /data partition
you said that safestrap won't change my system because it install the ROM in a different partition and the boot is made by there.
doesn't bootstrap happen the same? bootstrap overwrite the original system?
a case:
I used bootstrap and suppose that I want to unflash the init.d.. how can I do it?
thanks a lot
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
pedroramos said:
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
Click to expand...
Click to collapse
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
calash said:
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
Click to expand...
Click to collapse
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
It works 4 me
pedroramos said:
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
Click to expand...
Click to collapse
Ok, so right now it sounds like you are using the basic Clockwork Mod recovery, identified by the installed Droid 3 Bootstrap from the market/downloaded. In this case you do not have a backup from before the change you applied (Side note: Backups are also called nandroid backups. They are the same, just a different term).
If you wanted to remove the init.d hack it would be a bit more difficult at this point. Not impossible but you may end up losing all your data. It depends on if the changes the init.d hack made are well documented or not. It is a fairly safe hack so I would not worry too much about it at this point.
For your reference the bootstrap you installed, also called Clockwork Mod, and SafeStrap do nearly the same thing, providing you with the menu at the very beginning when you power on the device and allows you to flash (what you did to install the init.d have), backup, and some other neat features.
The big difference is that SafeStrap allows you to have two operating systems, also called Roms, on the phone. These are identified as Safe and non-Safe. non-safe is whatever OS (or Rom, the terms mean the same on our phones) you start with while the Safe is a new install that you do in the same way as you flashed the init.d have.
As you work with it more you will get the hang of the various terms and software packages. For now you should be in good shape, even without a stock backup. We have ways to get back to a pure stock image if that needs comes up, just check the threads in the development forum for more information.
Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread
Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!
Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....
This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post
This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Nice ! Trying soon... :fingers-crossed:
SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.
i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?
what about ics and gingerbread on dual boot!?
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Nice man" I ll try it soon!
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.
I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!
Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:
And what about dual boot with linux?
tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...
How about flashing the second rom that have aroma installer??
My phone (3T) has an unlocked bootloader, is encrypted, not rooted, and running stock OOS 5.0.
I flashed TWRP and discovered that stock OOS restores the stock recovery in boot.
I saw the Oreo dm-verity thread by xenet, had a look at the zip file, noticed that it just modified fstab to prevent force encrypt, so I flashed it to see what happens.
And nothing happens. After the system had booted, fstab is unchanged from the original stock copy.
So I'm wondering whether this file is also restored when booting up on stock.
I get aggressive and go back to TWRP and delete /system/etc and /system/bin and modify build.prop.
Surely now the phone won't boot!
Wrong! It boots up and everything is back to normal in /system.
I go back to TWRP and have a look at /system and it shows me one without the etc and bin folders and has the modified build.prop.
What's going on? How can I see one version of /system in TWRP but a different version (ie, stock) when the phone has booted?
By the way I've been an Android user for many years and have rooted and flashed custom ROMs on a variety of phones and I've never seen anything like what's happening on my 3T. I'm sure that dm-verity is somehow involved in this.
Happened to me on my earlier OOS 5.0 attempts...
But i suspected Magisk is involved in my case.
I downloaded Magisk Module "System Terminal Debloater,"
remove some apps like Duo, Chrome, and Google Play Movies.
Some restarts, they magically re-appear again on Apps Drawer...
Haven't touch them yet again after....
nicknacknuke said:
Happened to me on my earlier OOS 5.0 attempts...
But i suspected Magisk is involved in my case.
I downloaded Magisk Module "System Terminal Debloater,"
remove some apps like Duo, Chrome, and Google Play Movies.
Some restarts, they magically re-appear again on Apps Drawer...
Haven't touch them yet again after....
Click to expand...
Click to collapse
Thanks.
I should have mentioned that I'm also not rooted. So stock OOS 5.0.
Sent from my OnePlus 3T using XDA Labs
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Jackhass said:
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Click to expand...
Click to collapse
No, I don't get that message because my phone is encrypted with a password. So the first thing I see in TWRP is the request for the password and then I'm presented with the menus.
However, in the Mounted menu, system isn't mounted and I have the option of mounting it in read-only mode.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
No, I don't get that message because my phone is encrypted with a password. So the first thing I see in TWRP is the request for the password and then I'm presented with the menus.
However, in the Mounted menu, system isn't mounted and I have the option of mounting it in read-only mode.
Click to expand...
Click to collapse
After first time flashing TWRP a folder gets created on your internal storage, with a hidden file called .twrps, go delete it and reboot recovery to trigger the message "allowing system modifications" on TWRP's first boot...
It's not about encryption, it's just that TWRP remember the decision you made due to the file I pointed out...
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
After first time flashing TWRP a folder gets created on your internal storage, with a hidden file called .twrps, go delete it and reboot recovery to trigger the message "allowing system modifications" on TWRP's first boot...
It's not about encryption, it's just that TWRP remember the decision you made due to the file I pointed out...
Click to expand...
Click to collapse
Somehow the attachment strikes on previous post
Edit: still not working, check your TWRP Folder on storage to find the file
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Somehow the attachment strikes on previous post
Edit: still not working, check your TWRP Folder on storage to find the file
Click to expand...
Click to collapse
Thanks, you are correct. I'd forgotten that that TWRP remembers. Deleting .twrps does bring up the RO prompt after decrypting storage.
Jackhass said:
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Click to expand...
Click to collapse
I had allowed changes to the system otherwise I couldn't have made changes to it, which includes the ability to restore the system partition.
But I'm still unclear why if I make changes to the system partition and boot with the stock kernel, then after the boot none of the changes are present in the system partition, but if I boot back into TWRP then the changes are all there.
I recall someone in another OOS 5 thread saying that the stock kernal replaces TWRP with stock recovery if you don't flash root (magisk/superSU). Is it possible that the kernel re-flashes system on boot? Another possibility is that TWRP thinks it's making changes to system but it's not actually? Not quite sure, I've never heard of anything like this before either, just throwing other ideas out there.
I've never read anything about the OP3T or any oneplus phones for that matter having A/B system partitions like the pixels. *shrug*
@nhshah7, something's like what you suggest must be going on to account for what I'm seeing. I'm hoping that someone can confirm my observations and provide a definite answer.
@BillGoss
My thread has been updated relating to all your queries...
Thank you...
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Xennet said:
@BillGoss
My thread has been updated relating to all your queries...
Thank you...
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Click to expand...
Click to collapse
Actually it doesn't explain how TWRP can make changes to system yet the phone boots up on an unmodified system if using the stock kernel. And then, when you boot back into TWRP and look at system, the changes are still there.
Where does the unmodified system come from?
Where does the modified system live?
Why doesn't modifying system result in a failed boot due to dm-verity, while restoring a backup of system does result in a failed boot?
So many questions with no answers.
BillGoss said:
....So many questions with no answers.
Click to expand...
Click to collapse
Not sure if this is applicable in your case but the following possibilities may be worth considering for you:
1. Are you sure that the system image is actually getting modified? If the system partition is not mounted before flashing the zip and the zip being flashed does not mount the system partition in read / write, then no changes to system partitions will actually be written.
2. If dm-verity is enabled, then restoring system could result in an error as this is different from restoring a system-image (nandroid copy of the whole partition and not just the files in the system partition). DM-verity can be triggered if the files are all the same but the dm-verity signature computed by hashing the system partition has changed.
3. For boot partitions, strange behaviour can occur if remnants of the previous boot.img are still in the partition (...e.g. if the previous boot.img was of larger size and a new boot.img of a smaller is flashed, then there will be some bytes after the new boot.img that are from the previous boot.img). To verify this, format the boot partition from fastboot and see if you notice anything different with the new boot.img.
4. In Oreo / 8.0, dm-verity flags are stored in dtb (device tree blobs) inside the kernel and not in the fstab file. Only data encryption can be changed from the fstab file and dm-verity needs to be changed from changing the dtb (...Magisk beta v1456 and SuperSu 2.82 SR4 do this, I think).
rk2612 said:
Not sure if this is applicable in your case but the following possibilities may be worth considering for you:
1. Are you sure that the system image is actually getting modified? If the system partition is not mounted before flashing the zip and the zip being flashed does not mount the system partition in read / write, then no changes to system partitions will actually be written.
2. If dm-verity is enabled, then restoring system could result in an error as this is different from restoring a system-image (nandroid copy of the whole partition and not just the files in the system partition). DM-verity can be triggered if the files are all the same but the dm-verity signature computed by hashing the system partition has changed.
3. For boot partitions, strange behaviour can occur if remnants of the previous boot.img are still in the partition (...e.g. if the previous boot.img was of larger size and a new boot.img of a smaller is flashed, then there will be some bytes after the new boot.img that are from the previous boot.img). To verify this, format the boot partition from fastboot and see if you notice anything different with the new boot.img.
4. In Oreo / 8.0, dm-verity flags are stored in dtb (device tree blobs) inside the kernel and not in the fstab file. Only data encryption can be changed from the fstab file and dm-verity needs to be changed from changing the dtb (...Magisk beta v1456 and SuperSu 2.82 SR4 do this, I think).
Click to expand...
Click to collapse
I'll come back to 1.
2. That makes sense and accounts for why a restore of the system partition with the stock boot image causes me to get dumped back in fastboot mode. If I flash the stock system zip file then the system boots properly.
3. I've not had any issues with strange boot behaviour. I'm always starting with stock or flashing kernels that modify the stock boot image, like Blu Spark.
4. I gathered this from my reading of various threads. If I want to make changes to the system partition and get them to stick and not fail dm-verity then I have to flash a custom kernel. I've proven this in my testing. (A rooting solution would also work, but I've not done this).
Back to 1:
Here's what I've done:
Starting with pure stock image (flash OOS 5.0).
Boot into fastboot and flash TWRP.
Boot into recovery.
Mount system as rw. (In ro mode the next step fails)
Delete the bin, etc, and lib folders in system using the TWRP file manager. (Screenshot a)
Reboot system.
... First interesting fact ...
System boots ok, deleted folders are present in file manager. (Screenshot b)
Boot into fastboot and flash TWRP. (Booting with stock restores stock recovery)
Mount system.
... Second interesting fact ...
TWRP file manager shows that deleted folders are missing. (Screenshot c)
Flash custom kernel or patched boot image
Reboot system
... Third interesting fact ...
System fails to boot. Hangs on splash screen.
So TWRP made the changes (otherwise how could they be visible between reboots, including a replacement of recovery) and I only did them once.
Yet they don't actually take effect until I replace the stock boot image.
So, where are the changes hiding? What did TWRP actually change?
Screenshots (note that TWRP has the wrong timezone set so the time shown is wrong):
BillGoss said:
....
Back to 1:
Here's what I've done:
Starting with pure stock image (flash OOS 5.0).
Boot into fastboot and flash TWRP.
Boot into recovery.
Mount system as rw. (In ro mode the next step fails)
Delete the bin, etc, and lib folders in system using the TWRP file manager. (Screenshot a)
Reboot system.
... First interesting fact ...
System boots ok, deleted folders are present in file manager. (Screenshot b)
Boot into fastboot and flash TWRP. (Booting with stock restores stock recovery)
Mount system.
... Second interesting fact ...
TWRP file manager shows that deleted folders are missing. (Screenshot c)
Flash custom kernel or patched boot image
Reboot system
... Third interesting fact ...
System fails to boot. Hangs on splash screen.
So TWRP made the changes (otherwise how could they be visible between reboots, including a replacement of recovery) and I only did them once.
Yet they don't actually take effect until I replace the stock boot image.
So, where are the changes hiding? What did TWRP actually change?
Screenshots (note that TWRP has the wrong timezone set so the time shown is wrong):
Click to expand...
Click to collapse
Some more thoughts for you to consider:
1. Have you tried this with the official TWRP recovery version 3.2.0-0?
2. Is there anything inside the folders that you see using the file manager after a regular boot? Folders of same name may exist in the boot ramdisk and these are merged with system folders after boot.
3. Try wiping cache between reboots and see if that changes any of your observations.
rk2612 said:
Some more thoughts for you to consider:
1. Have you tried this with the official TWRP recovery version 3.2.0-0?
2. Is there anything inside the folders that you see using the file manager after a regular boot? Folders of same name may exist in the boot ramdisk and these are merged with system folders after boot.
3. Try wiping cache between reboots and see if that changes any of your observations.
Click to expand...
Click to collapse
Good questions. They got me thinking more about how this could possibly work.
I had a look at the cache and there's definitely no copy of the system hiding there.
I also unpacked the ramdisk in the boot image and it had nothing in system. Furthermore, the boot position is only 64 MB, no where near enough to hold the system.
Then I installed Magisk so that I could browse around the phone's partitions and take copies.
I learnt two things from this:
1. If there's a second copy of the system there are only three partitions large enough to hold it (/proc/partitions shows the sizes in 1 kB blocks). The system is about 1 GB. There is space in the system partition (sde20) for 3 GB. There's also space in the data partition (sca15). And there's space in the major partition holding the modems (sdf).
I could eliminate the data partition by formatting it but restoring the internal storage (sdcard) is such a a pain.
So I'll just accept that there is space for a copy, but I'm unlikely to find out exactly where.
2. When I had Magisk installed installed and the system boot, I added a folder and file to /system/priv-app using a file manager (so not using TWRP). I then booted into recovery, flashed the stock boot image, and rebooted. I was expecting it to fail dm-verity (modified system) but it didn't. After booting up there's no evidence of the folder I added to priv-app.
And if I restore the Magisk boot image then the additions show up again.
I'm actually very impressed with how the stock system (kernel, recovery, system) protects itself from modification. Very cool!
RETIRED! No longer supported or being developed. @Giovix92 is now the lead dev, please use his TWRP for full compatibility with modern kernels/ROM's - https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-3-1-0-tissot-manager-t3976117
Old thread below:
-----------------------------------
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing, Dual boot repartitioning and other power-user tools with integrated Aroma Installer-powered GUI screens that I call Tissot Manager.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know!. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready with dual-boot ROM patcher;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Option to install a payload ROM in the current slot, rather than the inactive one;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Adds a "Tissot Manager" Aroma GUI to TWRP Advanced Menu (bottom-right button), which is the tool used to repartition the device for Treble and Dual boot, as well as some other nifty stuff:
Has the option to shrink System OR Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink System, you will keep max size Userdata - however it will be incompatible with non-Treble ROM's (they will crash on installing with Error 28 due to System being too small). It will Erase system, requiring you to reinstall a ROM or restore a ROM backup.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Dual boot requires Userdata shrink and works by splitting into userdata_a and userdata_b. The partition split size is customizable during the repartition process.
Adds a "Patches" section with the following current options:
Patch the current Vendor for dual-boot capability (only required if automatic patching wasn't possible). See the 'About Dual-boot' section below for more information.
Enable an insecure ADBD on boot for the current slot (i.e. enable debugging and remove authentication requirement). Useful for ROM hackers/porters.
Patch the current slot to enable/disable forced userdata encryption
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-boot.img-3.2.1-with-Tissot-Manager-x.x.zip:
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches (Aroma Installer powered GUI - a fully guided and interactive process).
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack. Reminder - check out my full guide for learning and instructions on all things Treble.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
About Dual-boot
Dual-boot on this device is relatively simple. As you know we have Slots - boot_a and _b, system_a and _b and vendor_a and _b (for Treble). This repartition splits userdata into userdata_a and _b too. You can simply change your Slot in TWRP reboot menu to change which ROM to boot.
This is designed for developers and testers - NOT for daily use. There are some significant issues with dual boot systems:
Any kind of security lock (PIN, fingerprint, etc.) set on one ROM will cause the other ROM to believe it has security too, but constantly fail with unlocking. This is reportedly because security info is stored on persist, which is shared between each slot (and not compatible with differing ROM's).
Because Userdata is split, so is Internal Storage. In TWRP, when changing slots, the MTP will remain mounted to the old slot - it must be manually disabled and renabled (Mounts menu) to update to the new slot.
I will not fix these issues - dual-boot is not designed to be for general/daily use and there may be more minor issues that I don't know about. It's intended for developers only.
In order for a ROM to be dual-boot compatible, the fstab file (information given to Android about partitions to mount) needs a small modification. This TWRP can try to do this patching automatically when you install a ROM, or it can be done manually in Tissot Manager's Patches menu (as well as single-boot patch to e.g. revert a ROM backup from a dual-boot state).
You will see in the install log if a dual-boot patch attempt is successful in the flash text output.
Automatic dual-boot patch occurs only if necessary when:
Flashing an AIO Treble ROM ZIP with TWRP
Flashing a vendor.img in TWRP "Install Image" mode
Automatic dual-boot patch does NOT work when:
Flashing a vendor.img via fastboot
Restoring vendor in a TWRP backup
Any other way of flashing a vendor
In any of these cases, you can manually patch Vendor for Dual Boot in Tissot Manager's Patches menu. You can also remove dualboot support the same way. It will detect the dualboot state of the current Vendor slot and present the available option. If you find that it doesn't actually change after patching, the Vendor is incompatible (please report it to me). RR AIO Vendor is tested OK.
Download
All downloads (and source code) always at:
https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases
...or via DevBB Downloads section.
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/CosmicDan-Android/android_system_update_engine_tissotmanager-mod
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk. The void kernel included in RR AIO does not have this problem and can therefore be safely used without Magisk (for e.g. GSI compatibility).
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work. It will definitely not work if you have shrunk system.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ROM ZIPs with a shrunk System (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Credits and Thanks
- @mohancm for the original TWRP port, I used some flags from his DT
- @ghpranav and @mountaserhalak for the RR device tree that this is built with (and random help)
XDA:DevDB Information
TWRP with Tissot Manager (Treble & Dual boot support), Tool/Utility for the Xiaomi Mi A1
Contributors
CosmicDan
Source Code: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot
Version Information
Status: Stable
Created 2018-05-29
Last Updated 2019-11-24
Reserved
Screenshots (click for slightly larger non-cropped version)
Screenshot of new TWRP button:
_______________
Main menu (stock partition map detected):
_______________
Repartition choice type when coming from stock:
_______________
Repartition wipe warning/disclaimer if chosing to shrink Userdata for Treble:
_______________
Main menu (Shrunk Userdata type Treble partition map detected):
_______________
Repartition wipe warning/disclaimer if chosing to restore Stock from Shrunk Userdata Treble mode:
_______________
Example of Repartition processing screen:
Good job! :good:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Omg, you are the best man. @mohancm also huge thanks to u man, great devs in our XDA.
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Chikoow1 said:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Click to expand...
Click to collapse
This is just the repartition part, one step of Treble. You still need a Vendor pack. But yes, this enables Treble ROMs and the ROMs require repartition.
ddaggebi said:
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Click to expand...
Click to collapse
1. If you do, it will wipe partition map back to stock. So you will need to repartition with Treble Manager TWRP again. But you can make a backup of stock ROM in TWRP and just restore it after the repartition. It should work.
2. Don't know. Needs testing.
3. Yes! I forgot to add this to the FAQ.
Has this tpwr f2fs support and working?
Since Los support It i would like ti have
@CosmicDan
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Filip013;76586434 [user=1844875 said:
@CosmicDan[/user]
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Click to expand...
Click to collapse
It's indeed not intended to be compatible with stock ROM, but your mileage may vary, and as @CosmicDan said, it might work good enough or it won't. You can only try to see the results yourself.
This whole Treble thing is meant mainly for custom ROMS, since stock will never be Treble compatible (still, anything could happen)
I've just updated the TWRP with Treble Manager to 1.1 which fixed a semi-important bug.
Also, I've released a guide for those who find the Treble conversion/install process confusing - check it out. If you can, keep TWRP and Treble Manager specific questions in this thread, but ask your general questions and help over there - I will update the guide as I get feedback
CosmicDan said:
FAQ
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) Untested. Please report your results. But Treble is really not about Stock, you will likely encounter more problems down the line or it may turn out to be completely incompatible.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest/only way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (untested - if you get bootloop when using stock, it means you do) or Magisk (also untested, may still get bootloop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ZIP's on ROM's with a shrunk Userdata (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Unable to mount '/vendor' (Invalid argument)" red error in this TWRP
A) You can safely ignore it. It just means you have not repartitioned your device for Treble yet, so it can't mount the /vendor image.
Click to expand...
Click to collapse
Ay!
Have just finished testing about OTA on stock after Treblizing!
Result?!?
OTA works perfectly on stock after shrinking data to Treblize! Hurrah! ???
Process I followed:
1) Treblize by shrinking data
2) This is important: flash stock ROM in fastboot using MiFlash! When flashing for the first time, select "clean all and lock"! No other standard options working! I couldn't even boot stock using other options!
I've tested by fastboot flashing April build and then updating it to May OTA!
*** On a note: clean all will erase everything on your phone including your personal data!
If you use "save user data" then stock can't even boot! This may caused by the encryption!
BTW, after everything I just restored my non-Treble RR backup and everything works perfect! Just Treble Check app can't check that it's Treblized!
But don't worry! Treble partition table still remains! Fastboot flash can't touch that and can't recognize that it actually exists! Which to me is a good thing!
@CosmicDan, give me a thanks buddy! I deserve this!
SomratMJX said:
-snip-
Click to expand...
Click to collapse
Don't quote the whole OP and please use a smaller font size.
Change slot doesn't work... Others are okay as far as i have seen
dback31 said:
Don't quote the whole OP and please use a smaller font size.
Click to expand...
Click to collapse
Just thought it's too important to highlight! Nothing else!
Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Reboot to fastboot and change the slots with
fastboot set_active b
Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Use the latest TWRP 1.1! Works fine for me!
SomratMJX said:
Just thought it's too important to highlight! Nothing else!
Click to expand...
Click to collapse
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
dback31 said:
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
Click to expand...
Click to collapse
Ha ha ha! It's related to OP buddy!
Anyways, I am too lazy to quote a certain part of the OP!
Hello all,
First of all, I'm not very familiar with recovery/rooting on phones. Although my daytime job is customizing embedded linux, so I have some knowledge
I got my hand on a few Alcatel 5033d devices, on which I want to run a software I created. However, this software needs access the notifications. And Android GO doesn't allow that. So I need to change the low-ram flag in build.prop. If possible I also want to remove the google apps from it and make my app a system app. But for the rest I'm happy, so don't need linageos or anything.
Is there a way to make a custom system.img, based on the original one, with only build.prop changed and load this complete firmware via the original recovery mode? I already saw you could load things via sdcard (adb doesn't work in stock recovery -> authentication required).
I already tried mtk-su (worked on a tablet before), but I guess that flaw is already patched
Something to try
This is from my head so if this doesnt work im sorry
1. install a custom rom.
2. install magisk onto the custom rom.
3. make a copy of the boot image
4. use "Mobile upgrade S" from alcatel to restore your phone
5. flash the backed up boot image from before.
6. if your lucky you may have root on the original system partition.
P.S i would use https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713 rom because it doesnt touch the boot partition.