I searched thread titles for "dual" and found minor discussions but no explanations.
So I'm running with the assumption we can dual boot and I'm just now interested in this.
So what are the steps to dual boot?
I have TWRP RC1 and I flashed a ROM on A.
Then I rebooted to TWRP and still on slot A, I flashed another ROM and it should have installed on B.
I ended up trying it a few different ways.
But one ROM install always seemed to kill the other ROM install?
It takes so long to test that I said fuggit and decided to ask the forum for help. :good:
Any progress with this? I'm looking to dual boot also. I have heard that both ROMs must be of the same Android version, but looking for more details.
Please reply or post a link, Thanks.
davidbanks said:
Any progress with this? I'm looking to dual boot also. I have heard that both ROMs must be of the same Android version, but looking for more details.
Please reply or post a link, Thanks.
Click to expand...
Click to collapse
I have done this. Just about the only way to use it without problems is to run stock on both slots. One for root and exposed whatever.. The other for no root for android pay and other apps that require safety net and stock build prop. This is the only practical dual boot setup seeing as how both slots share data.
DR3W5K1 said:
I have done this. Just about the only way to use it without problems is to run stock on both slots. One for root and exposed whatever.. The other for no root for android pay and other apps that require safety net and stock build prop. This is the only practical dual boot setup seeing as how both slots share data.
Click to expand...
Click to collapse
IDK what you are talking about. Magisk works with everything. Netflix, Android pay and safetynet. I got it running. As far as dual boot. It will never happen. A/B partitions use the same system. They have the separation for updating and that's it. No way to dual boot two different roms. People confuse A/B partition scheme with dual boot. Yes there is two slots. But only for updating. Research it. If we had a cache partition scheme, yes you can. You allocate part of each partition into another partition that allows for the second rom. And depending on how big and what you use, you could even triple boot. Say the s8 I had could be dual boot. Pixel XL runs a A/B partition with no cache partition.
What?
S8rooted&tooted said:
IDK what you are talking about. Magisk works with everything. Netflix, Android pay and safetynet. I got it running. As far as dual boot. It will never happen. A/B partitions use the same system. They have the separation for updating and that's it. No way to dual boot two different roms. People confuse A/B partition scheme with dual boot. Yes there is two slots. But only for updating. Research it. If we had a cache partition scheme, yes you can. You allocate part of each partition into another partition that allows for the second rom. And depending on how big and what you use, you could even triple boot. Say the s8 I had could be dual boot. Pixel XL runs a A/B partition with no cache partition.
Click to expand...
Click to collapse
The topic is dual booting the Pixel, strange tangent to Magisk by yourself, but you got it running! Oh, wait up, you're still on that diverted tangent. So no way to boot 2 different ROMS. I did research it. You go on to say "If we had a cache pardition ...", which we do, or am I misunderstanding the "Wipe Cache Partition" command on the Pixel? So we can dual boot! Or triple boot even! Oh, hold on again, now we don't have a cache partition? Pixels do have A/B partition as you call it, but within those partitions, are all the partitions we are used to (tho I think a couple are shared between A & B). So, I'll just get Magisk, that works with everything!
No cache partition.
---------- Post added at 12:50 PM ---------- Previous post was at 12:47 PM ----------
Go develop it. Dualbooting cannot happen for reasons I explained above. There is no cache partition and or image. Please show me. Dav cache isn't a cache partition. But hey new developments are discovered everyday. Maybe next you could reinvent the wheel. It has gone on long enough without you reinventing it. Lol.
Supernoobsammyson said:
No cache partition.
---------- Post added at 12:50 PM ---------- Previous post was at 12:47 PM ----------
Go develop it. Dualbooting cannot happen for reasons I explained above. There is no cache partition and or image. Please show me. Dav cache isn't a cache partition. But hey new developments are discovered everyday. Maybe next you could reinvent the wheel. It has gone on long enough without you reinventing it. Lol.
Click to expand...
Click to collapse
Hey air needs to be reinvented too. Not enough going to your brain.
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
Also tampons. Reinvent those too while you are using them.
---------- Post added at 01:08 PM ---------- Previous post was at 12:59 PM ----------
https://source.android.com/devices/tech/ota/ab
Go read yourself from Android. What an AB partition is. No cache partition by itself.
I think we can safely say this question has been answered. Let's move on, the gentleman was right. Dual booting isn't possible , at least not right now.
I am able to duel boot on my pixel xl (was accidental but messed up something during installing lineage 16 and now have 2 versions 1 new install and 1 upgrade install)
S8rooted&tooted said:
If we had a cache partition scheme, yes you can. You allocate part of each partition into another partition that allows for the second rom. And depending on how big and what you use, you could even triple boot. Say the s8 I had could be dual boot. Pixel XL runs a A/B partition with no cache partition.
Click to expand...
Click to collapse
Is there a way to do it?
(And if it is no possible maybe it is possible to simulate a partition like the modules of magisk?)
Mordechay said:
Is there a way to do it?
(And if it is no possible maybe it is possible to simulate a partition like the modules of magisk?)
Click to expand...
Click to collapse
ya sorry i reformatted my pixel xl gen 1 and installed it once. So not sure how I did it.
Related
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.bat WITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.bat WITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Anutter226 said:
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.batWITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.batWITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
I imagine it's overkill but you could just switch the active slot and run flash-all again. As a precaution I would recommend booting into the OS after the first flash-all to make sure it flashed ok. If there happens to be some problem like a bad flash or wrong download you want to be sure that the "other" slot is bootable. Otherwise you might end up with a pair of unbootable slots which could get sticky.
Anutter226 said:
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
then you saw that flash-all.bat flashed both slots
V40 said:
then you saw that flash-all.bat flashed both slots
Click to expand...
Click to collapse
Doesn't flash to both slots on mine
canemaxx said:
Doesn't flash to both slots on mine
Click to expand...
Click to collapse
I believe it flashes to one slot and deletes the data on the other as standard
If you guys would read your terminal output after flashing you would know what gets flashed where. People are making this way to complicated. It is a big change from previous devices but once you know the partitions its pretty easy.
One data slot shared by A + B
Slot A & B have separate partitions for
-Vendor
-Bootloader
-Radio
-Modem
-Boot
-System
Flashall.bat flashes your active slot and installs system_other.img to the inactive system partition and wipes data, unless you edit the flashall.bat and erase -w.
Thats it. Now, how people are handling the two slots is another story. I keep both slots identical. Having two different bootloaders is a recipe for bricks in my opinion.
FWIW, I endorse the post above this one. I would only add if you get in trouble flash all without the -w and then change the active slot and flash all without the-w again.
Golf c said:
Having two different bootloaders is a recipe for bricks in my opinion.
Click to expand...
Click to collapse
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
5.1 said:
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
Click to expand...
Click to collapse
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Golf c said:
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Click to expand...
Click to collapse
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
5.1 said:
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
Click to expand...
Click to collapse
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Golf c said:
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Click to expand...
Click to collapse
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
5.1 said:
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
Click to expand...
Click to collapse
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Golf c said:
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Click to expand...
Click to collapse
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
5.1 said:
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Click to expand...
Click to collapse
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Golf c said:
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Click to expand...
Click to collapse
Hey,
I did it just to show something to someone earlier. I don't need dual boot either...
One ROM is enough in my opinion.
Ok, time to hit the bed. See you later...
Cheers...
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
TonikJDK said:
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
Click to expand...
Click to collapse
And I don't even use it because I have never taken an OTA. lol!
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
canemaxx said:
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
Click to expand...
Click to collapse
No need since it ia working but you get into Fastboot mode then
Fastboot set_active a
Flash L, flash April bootloadee.
deleted
You have to wipe data from stock before using a 3rd party rom.
This is why you get the error. Why lineage works, I don't have any idea.
No concerns here, something must have gone wrong or a bad download. I ran lineage 15 and many other roms without any security red flags
joshk89 said:
No concerns here, something must have gone wrong or a bad download. I ran lineage 15 and many other roms without any security red flags
Click to expand...
Click to collapse
I downloaded it twice. But if it was a bad download, why did it make an encrypted partition? And why would you assume a ROM built with malware would tell you it has malware?
NODE06 said:
I downloaded it twice. But if it was a bad download, why did it make an encrypted partition? And why would you assume a ROM built with malware would tell you it has malware?
Click to expand...
Click to collapse
I'm not saying you shouldn't be skeptical and weary installing software from an unknown source, there's always that possibility I guess. But I also don't see many others with issues. So I'm not sure what you did wrong if anything but I doubt there's a security issues. Also the devs are normally frequent contributors to multiple devices and this forum has been here a long time. I doubt you're dealing with malware
NODE06 said:
I think the flippant attitude towards the security of your phone is disheartening.
People have worked for companies for years as the perfect employee until someone offered them enough money to steal documents. I do not care how long a dev was here, if they cannot explain why they have an encrypted partition on their ROM that is troubling. And if there are not diffs I can look at who the hell know which nightly update they slipped malware in.
Malware being hidden in ROMs are nothing new:
https://arstechnica.com/information...lware-targets-android-users-of-two-companies/
Click to expand...
Click to collapse
Maybe someone else can help you further, but I don't think you have much to worry about if you downloaded from vaches link.
I'm not super technically advanced and I don't know how to code. But I've been around the rooting and custom rom scene for a long time. Just giving you my 2 cents since you asked for it.
Have you posted your issue on the main thread for LOS15?
I believe it has something to do with older versions of twrp for our phone. I didn't have this problem at all. So if we downloaded the same file...how can mine not do it, and yours do it? Would be logical to think its something else...like twrp. Older versions of twrp for this phone had quite a few issues. One I believe was dealing with encryption.
In fact, this has to be a twrp issue. I just clean flashed to PA 7.1.2 with no issue and then clean flashed back to LOS 15 with no issue. No asking for passwords, nothing. 100% normal. There is absolutely no virus or spyware in this ROM, and it is absurd to think otherwise.
I have an answer for you. I formatted my system partition and cache to f2fs just wanted to see if it would boot all f2fs but as the ROM booted I got stopped at that exact same dilemma i then reverted my system and cache partitions back to ext4 reinstalled the ROM and gapps and magisk manager and it booted into los15 so I can only say that whilst u was repairing and resizing your partitions u maybe without realising formatted system/cache into f2fs. Hope this helps bud?.
NODE06 said:
Are you saying you has a screen that asked you to enter a password to decrypt your drive?
Also, I only changed the partition type AFTER I had the error in an attempt to fix my phone. Exevry parition was formatted as default EXT4.
REPEATING MYSELF AGAIN: Why are you not concerned that there is an encrypted partition on your drive with a simple known password?
Click to expand...
Click to collapse
Well you must made that encrypted partition yourself. Lineage doesn't do that. And why formatting data to ext4? Moto devices are always f2fs on data partitions. And if you don't trust us devs, then go back to stock and trust Motorola.
NODE06 said:
Are you saying you has a screen that asked you to enter a password to decrypt your drive?
Also, I only changed the partition type AFTER I had the error in an attempt to fix my phone. Exevry parition was formatted as default EXT4.
REPEATING MYSELF AGAIN: Why are you not concerned that there is an encrypted partition on your drive with a simple known password?
Click to expand...
Click to collapse
Yes I had a screen asking for a password because u formatted to f2fs
skooter32 said:
Yes I had a screen asking for a password because u formatted to f2fs
Click to expand...
Click to collapse
This makes no sense. Please use complete sentences.
NODE06 said:
I think I would have REMEMBERED making an encrypted partition myself with a passowrd "lineage". But someone else had the same issue so that is impossible.
And AGAIN, I had this issue BEFORE I changed the format. I changed the format to repair my phone. And either EXT4 or F2FS will work on a moto G5 plus. They are drive formats and have nothing to do with encryption.
Click to expand...
Click to collapse
Again, lineage does not encrypt your /data partition. Only the user or stock does. If you use ext4 and change to stock say bye to your whole data partition.
NODE06 said:
I did not say it encrypts the DATA partition, I think it is encrypting the system partition or making a whole new encrypted partition.
I am not the only one who saw this happen.
AND AGAIN I did not make ANY CHANGES to my file partitions before this happened.
AND AGAIN why did it only accept the password "lineage". I never made, nor know how to make, an encrypted partition so linage MUST HAVE MADE IT.
At this point I do not know whether you are misunderstanding me or obfuscating to cover up for someone. Maybe I need to recreate and take photos.
Click to expand...
Click to collapse
Lol, encrypted system partition. Like that exists on android. You didnt't format your data partition in twrp, thats why it happened. And I understand you clearly, but it's not possible
NODE06 said:
Format the data partition? To what? It does not say that anywhere in the install instructions. I WIPED THE DATA FOR THE EFFING SIXTEENTH TIME.
And I said it might be the system partition. And I said that only because the password is asked for so early and is a TEXT PASSWORD.
Click to expand...
Click to collapse
"AND AGAIN I did not make ANY CHANGES to my file partitions before this happened." you say something different here.
Anyway you need to format the whole data partition as stated in twrp thread otherwise you get encryption problems. But I doubt you will listen now.
dfhdfhdfhdfh
Unfortunate that it happened to you, but If you were actually right I am sure it would affect us all which is clearly not the case. Oreo is a treat and everything that matters actually works great(thanks to Vache). If you're so suspicious then maybe stay a mile away from custom ROMS and rooting. They aren't for you but stop being so rude and ungrateful for what you're getting for free. Vache is an outstanding dev and has been working on Lineage for potter since long. So do us a favor and yourself and just get off xda if you are so paranoid about your own mistake.
EDIT:The password could be anything btw and it would still fail to decrypt. I had faced the same problem and everything I entered was "correct" password. So no **** Sherlock its definitely no one's fault.
NODE06 said:
I told you I DID FORMAT (WIPE) THE DATA PARTITION. I did not change it to F2FS as some other mentioned.
Click to expand...
Click to collapse
Please answer just these two questions:
1 - What version of TWRP are you using?
2 - In TWRP did you choose Wipe, then in the next screen Format Data (looks like a gray button at bottom right) and NOT Advanced Wipe, then in the next screen you typed 'yes' to continue after the warning in red letters?
* * * Thread Closed * * *
Must. Save. Bandwidth. For. Development.
Please guys; in the future, just report the trolls, don't feed, argue, scold, engage, or throat punch them (I know the urge is incredible, but resist it)
hi there!
I previously had colors 2.1.5.i version installed in my Oppo find7a. I was quite happy for quite a long time but lately I had many issues .SIM card stop working and keep on having continuous crashes when running apps so I uninstalled and reinstalled colors again and again. Finally I went back to the factory setting version and rooted the phone but now I am having issues with more crashes, continuous app logout and login and lack storage (it does not allow me installing many apps even if i keep on uninstalling apps and moving them to the SD).
Could you recommend me the best solution and best Colors version or even a different ROM for oppo find7a so I do not have any of these issues anymore?
Thanks in advance!
J
joselin2017 said:
hi there!
I previously had colors 2.1.5.i version installed in my Oppo find7a. I was quite happy for quite a long time but lately I had many issues .SIM card stop working and keep on having continuous crashes when running apps so I uninstalled and reinstalled colors again and again. Finally I went back to the factory setting version and rooted the phone but now I am having issues with more crashes, continuous app logout and login and lack storage (it does not allow me installing many apps even if i keep on uninstalling apps and moving them to the SD).
Could you recommend me the best solution and best Colors version or even a different ROM for oppo find7a so I do not have any of these issues anymore?
Thanks in advance!
J
Click to expand...
Click to collapse
Do you have TWRP installed?
oppo issue
Jan.Pul said:
Do you have TWRP installed?
Click to expand...
Click to collapse
yes i do!
joselin2017 said:
yes i do!
Click to expand...
Click to collapse
Install nameless rom, first flash the lvm zip then flash nameless then flash gapps, if you need the setup lvm zip tell me
oppo issue
Jan.Pul said:
Install nameless rom, first flash the lvm zip then flash nameless then flash gapps, if you need the setup lvm zip tell me
Click to expand...
Click to collapse
Thanks a lot for your help. Yes I would appreciate a reliable source for the lvm zip file. I guess the same procedure would work for lineage ROM? I tried to instal lineage before but it failed so maybe that was the reason. Cheers!
J
joselin2017 said:
Thanks a lot for your help. Yes I would appreciate a reliable source for the lvm zip file. I guess the same procedure would work for lineage ROM? I tried to instal lineage before but it failed so maybe that was the reason. Cheers!
J
Click to expand...
Click to collapse
What did it say when you installed lineage?
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
joselin2017 said:
Thanks a lot for your help. Yes I would appreciate a reliable source for the lvm zip file. I guess the same procedure would work for lineage ROM? I tried to instal lineage before but it failed so maybe that was the reason. Cheers!
J
Click to expand...
Click to collapse
Lvm zip:
https://androidfilehost.com/?fid=24052804347800902
Nameless rom:
https://sourceforge.net/projects/namelessrom/files/n-4.1/find7/
Gapps just Google opengapps
Please make sure you have the latest TWRP
https://dl.twrp.me/find7/
oppo issue
Jan.Pul said:
What did it say when you installed lineage?
I think: Lineage failed to install ["error 7"]
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
Lvm zip:
https://androidfilehost.com/?fid=24052804347800902
Nameless rom:
https://sourceforge.net/projects/namelessrom/files/n-4.1/find7/
Gapps just Google opengapps
Please make sure you have the latest TWRP
https://dl.twrp.me/find7/
Click to expand...
Click to collapse
would it work for find7a also?
full wipe means .. first, factory reset (data, cache and Dalvik), then system and Dalvik cache or all at once? Just wanna make sure all works fine this time cos takes quite a lot of time the whole process that I've done already a few times
Thanks a lot!
joselin2017 said:
would it work for find7a also?
full wipe means .. first, factory reset (data, cache and Dalvik), then system and Dalvik cache or all at once? Just wanna make sure all works fine this time cos takes quite a lot of time the whole process that I've done already a few times
Thanks a lot!
Click to expand...
Click to collapse
First make a full backup to your sdcard of your current OS so your never left out, I just always wipe everything but raw SD and one other raw partition(data or something) and also not the sdcard I wipe everything apart from those 3, make sure before you make a backup the location is your sdcard, this is a step by step guide.
FIRST INSTALL ALL FHE THE ZIPPS I MENTIONED BEFORE AND PLACE THEM ON YOUR SDCARD
1. Boot into recovery
2. Make full backup to sdcard (this takes about half an hour) after you finished the backup just check if it worked, photos video's and music are not included only the apps your system and all the data
3. wipe everything apart from the aforementioned partitions
4. Flash the setup lvm zip
5. Reboot recovery
6. Flash nameless rom zip
7. Flash opengapps 7.1 arm micro/Pico
8. Reboot phone
---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------
Jan.Pul said:
First make a full backup to your sdcard of your current OS so your never left out, I just always wipe everything but raw SD and one other raw partition(data or something) and also not the sdcard I wipe everything apart from those 3, make sure before you make a backup the location is your sdcard, this is a step by step guide.
FIRST INSTALL ALL FHE THE ZIPPS I MENTIONED BEFORE AND PLACE THEM ON YOUR SDCARD
1. Boot into recovery
2. Make full backup to sdcard (this takes about half an hour) after you finished the backup just check if it worked, photos video's and music are not included only the apps your system and all the data
3. wipe everything apart from the aforementioned partitions
4. Flash the setup lvm zip
5. Reboot recovery
6. Flash nameless rom zip
7. Flash opengapps 7.1 arm micro/Pico
8. Reboot phone
Click to expand...
Click to collapse
If this doesn't work you have to contact me and I'll send you a link for project spectrum 1.3 try it again from that rom
Jan.Pul said:
First make a full backup to your sdcard of your current OS so your never left out, I just always wipe everything but raw SD and one other raw partition(data or something) and also not the sdcard I wipe everything apart from those 3, make sure before you make a backup the location is your sdcard, this is a step by step guide.
FIRST INSTALL ALL FHE THE ZIPPS I MENTIONED BEFORE AND PLACE THEM ON YOUR SDCARD
1. Boot into recovery
2. Make full backup to sdcard (this takes about half an hour) after you finished the backup just check if it worked, photos video's and music are not included only the apps your system and all the data
3. wipe everything apart from the aforementioned partitions
4. Flash the setup lvm zip
5. Reboot recovery
6. Flash nameless rom zip
7. Flash opengapps 7.1 arm micro/Pico
8. Reboot phone
---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------
If this doesn't work you have to contact me and I'll send you a link for project spectrum 1.3 try it again from that rom
Click to expand...
Click to collapse
sure ! I'll come back to you in a few days because I have to make time to do this again.
Thanks a lot and good weekend!
joselin2017 said:
sure ! I'll come back to you in a few days because I have to make time to do this again.
Thanks a lot and good weekend!
Click to expand...
Click to collapse
Okay. Tell me how it went, if this doesn't work you should contact Oppo support
oppo issue
Jan.Pul said:
Okay. Tell me how it went, if this doesn't work you should contact Oppo support
Click to expand...
Click to collapse
unfortunately all went bad! nothing worked this time!
everything failed this time so I had to go back to colors version 2.1.5i and switch partitions again to avoid storage issues.
Failing message was something like this: "storage: can't find table partition". I could not even root this time. They only thing I did not do was "wipe data, internal and sd card", the rest I wiped first, then it did not allow me to go any further.
Let's see for how long this solution works. I am starting to think that this issue has to do with programmed obsolescence rather than ROMS issues.
Oppo support have ignored me so far. I sent a couples of messages a couple of weeks ago and no answer yet. Maybe they do not speak english cos I could not find any english community. They are mostly asian http://community.oppo.com/id/forum.php?mod=viewthread&tid=5645&extra=&page=1
Do you have any other suggestion? I am tempted to buy another phone if turns to be headache again
Cheers and thanks a lot!
joselin2017 said:
unfortunately all went bad! nothing worked this time!
everything failed this time so I had to go back to colors version 2.1.5i and switch partitions again to avoid storage issues.
Failing message was something like this: "storage: can't find table partition". I could not even root this time. They only thing I did not do was "wipe data, internal and sd card", the rest I wiped first, then it did not allow me to go any further.
Let's see for how long this solution works. I am starting to think that this issue has to do with programmed obsolescence rather than ROMS issues.
Oppo support have ignored me so far. I sent a couples of messages a couple of weeks ago and no answer yet. Maybe they do not speak english cos I could not find any english community. They are mostly asian http://community.oppo.com/id/forum.php?mod=viewthread&tid=5645&extra=&page=1
Do you have any other suggestion? I am tempted to buy another phone if turns to be headache again
Cheers and thanks a lot!
Click to expand...
Click to collapse
I've got a folder on gdrive https://drive.google.com/folderview?id=0BxOXFnbm6PEGLXNxU1A0dzktTFU
It has a both a spectrum 1.3 zip (download this to your sdcard) and a recovery tool in it, you need to install it on your PC and connect your phone in fastboot then follow the on screen instructions and install the stock color OS recovery when your there try to install the spectrum zip, this has worked for me in the past, the problem with Oppo support is that they probably won't help you because your bootloader is unlocked.
Jan.Pul said:
I've got a folder on gdrive https://drive.google.com/folderview?id=0BxOXFnbm6PEGLXNxU1A0dzktTFU
It has a both a spectrum 1.3 zip (download this to your sdcard) and a recovery tool in it, you need to install it on your PC and connect your phone in fastboot then follow the on screen instructions and install the stock color OS recovery when your there try to install the spectrum zip, this has worked for me in the past, the problem with Oppo support is that they probably won't help you because your bootloader is unlocked.
Click to expand...
Click to collapse
wow! this was a great suggestion, i did it and it's going great so far. I'll give you a full summary report after I have a taste of it, I think in one week or so
Thanks a lot!
joselin2017 said:
wow! this was a great suggestion, i did it and it's going great so far. I'll give you a full summary report after I have a taste of it, I think in one week or so
Thanks a lot!
Click to expand...
Click to collapse
Amazing, this is Android 5.1 btw from there you can reflash everything to newer Android versions the stock recovery repairs all the partitions and stuff
Jan.Pul said:
Amazing, this is Android 5.1 btw from there you can reflash everything to newer Android versions the stock recovery repairs all the partitions and stuff
Click to expand...
Click to collapse
hi there! I was giving more time to give you a summary.
Well! it was good while it lasted. Only 24 hours I enjoyed Spectrum. After that first warning message was "google services stopped", then slowly phone started going slower and slower till finally cant start anymore. Now if i restart, it remains at "oppo logo screen". I had the feeling that this was going to happen at some moment but caught me unattended. Furthermore, while I was trying to go back to recovery mode, though I left all files in internal and a copy at external memory, just in case, now at recovery mode cant find any of these files. Meaning I am really stuck at this point and I can't go any further since internal and external memory cant be accessed in recovery mode to reinstall. Moreover, computer cant transfer files to internal or external cos cant initiate well and does not allow me transfering.
I need to find how to make internal or external memory recognised by my computer so that i can transfer files and recover again or a way to read those hidden directories.. any suggestions? any option from the recovery installer? I tried option 3 to install openrecovery twrp but cant find .zip files and computer still cant transfer. This is really killing me :S
joselin2017 said:
hi there! I was giving more time to give you a summary.
Well! it was good while it lasted. Only 24 hours I enjoyed Spectrum. After that first warning message was "google services stopped", then slowly phone started going slower and slower till finally cant start anymore. Now if i restart, it remains at "oppo logo screen". I had the feeling that this was going to happen at some moment but caught me unattended. Furthermore, while I was trying to go back to recovery mode, though I left all files in internal and a copy at external memory, just in case, now at recovery mode cant find any of these files. Meaning I am really stuck at this point and I can't go any further since internal and external memory cant be accessed in recovery mode to reinstall. Moreover, computer cant transfer files to internal or external cos cant initiate well and does not allow me transfering.
I need to find how to make internal or external memory recognised by my computer so that i can transfer files and recover again or a way to read those hidden directories.. any suggestions? any option from the recovery installer? I tried option 3 to install openrecovery twrp but cant find .zip files and computer still cant transfer. This is really killing me :S
Click to expand...
Click to collapse
Okay I have one last suggestion, use an adapter from USB to micro SD of from SD to micro SD (if your PC supports that) if that also doesn't work lock your bootloader and send it to Oppo I just don't know any other options ?
Jan.Pul said:
Okay I have one last suggestion, use an adapter from USB to micro SD of from SD to micro SD (if your PC supports that) if that also doesn't work lock your bootloader and send it to Oppo I just don't know any other options
Click to expand...
Click to collapse
I just wipe data and cache and got lucky to enter some sort of Spectrum version with no access to storage at all but some miracle internal memory inside (2-3G) that I can not access or see at all. It's working for a few apps only cos complaint when i tried the ones I had before. I think Ill keep it as a back up phone and tomorrow i decided to buy some not very expensive phone (150-200 euros) to have my life back and maybe i buy a better phone (maybe Oppo) in my next trip to Asia. I really appreciate your super help. Hope one day I can treat you for a beer
joselin2017 said:
I just wipe data and cache and got lucky to enter some sort of Spectrum version with no access to storage at all but some miracle internal memory inside (2-3G) that I can not access or see at all. It's working for a few apps only cos complaint when i tried the ones I had before. I think Ill keep it as a back up phone and tomorrow i decided to buy some not very expensive phone (150-200 euros) to have my life back and maybe i buy a better phone (maybe Oppo) in my next trip to Asia. I really appreciate your super help. Hope one day I can treat you for a beer
Click to expand...
Click to collapse
Haha you'll have to wait 3 years for the beer,I just turned 15?, im going to be buying the honor 7x it's a great phone on paper
Jan.Pul said:
Haha you'll have to wait 3 years for the beer,I just turned 15, im going to be buying the honor 7x it's a great phone on paper
Click to expand...
Click to collapse
really? wow ! i thought i was talking to a senior what country you live in? I was checking the honor 7x here but its out of stock so I bought another phone for the moment.. "wiko ufell prime" it was 100 euros discount !! lets see how long it works fine hehe
good weekend!
joselin2017 said:
really? wow ! i thought i was talking to a senior what country you live in? I was checking the honor 7x here but its out of stock so I bought another phone for the moment.. "wiko ufell prime" it was 100 euros discount !! lets see how long it works fine hehe
good weekend!
Click to expand...
Click to collapse
Haha a lot of people make that mistake , I live in Holland. I'm not sure about the wiko even for €150 it's not the best deal I've ever seen you could have better gone for the redmi note 4X
So Im selling my Pixel 2 XL and want to completely wipe clean my device before sending it off. I want my personal files completely unrecoverable, whats the best way/program to do this?
ami23 said:
So Im selling my Pixel 2 XL and want to completely wipe clean my device before sending it off. I want my personal files completely unrecoverable, whats the best way/program to do this?
Click to expand...
Click to collapse
Factory reset the device, then. Fastboot the factory image. That'll double wipe your device :good:
Badger50 said:
Factory reset the device, then. Fastboot the factory image. That'll double wipe your device :good:
Click to expand...
Click to collapse
Exactly my routine when I bone my phone and wanna start over! Lol
Encrypt the device then factory reset it. Any not overwritten sections of the phone will be encrypted parts useless without the whole partition. Total gibberish. Perfect as it will wipe out with missing encryption even the "blank" areas of the device.
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
Flashing over the OS does nothing to erase the pure data sections of the phone only the OS. I can undelete those sections easily unless they are overwritten.
https://www.getdroidtips.com/twrp-recovery-motorola-moto-e6/
None of my recoveries have worked for the E6, but I'm being linked as a developer for a working TWRP recovery. if you came from this link, DO NOT use my builds. I've deleted the links to my builds anyway. Someone else got OrangeFox working on the forums. Go check it out and use that one instead.
I tried it but sadly it didn't work - I tried to use it as a temporary boot but it simply booted into the the normal E6 OS
TristianX said:
I tried it but sadly it didn't work - I tried to use it as a temporary boot but it simply booted into the the normal E6 OS
Click to expand...
Click to collapse
Crap, I gotta see if there's a way I can get logs then. But you usually can't get logs unless you can boot into a custom recovery...
Gimme a bit to think about this
I tried this image;
https://unofficialtwrp.com/twrp-3-3-1-root-moto-e6/
This process too
https://forum.xda-developers.com/moto-e6/how-to/rooting-e6-surfna-t3965659
and then of course your image from this post.
They all indicate they flash ok from the fastboot status but when it should boot/temp boot/or replace recovery it simply puts me back into normal boot up. I'm using the t-mobile variant with firmware PCB29.73-65-3
Ohhhh I'm excited to see where this can go!
My buddy just sent me a PM and brought up a good point. When dirty porting, I didn't even think to check if the recoveries were both 64 bit. This could be the reason why it's not booting. I'm gonna have another go at this later today and post up another test image for you all if I can figure something out.
Also, just as a heads up, this is for the QUALCOMM MODEL E6. Not sure if there's a MediaTek international model, but this isn't for that.
Well when you post back I'll deff give it a try.
I'm gonna try porting from a different phone, some kind of Aquarius model. It has the same chipset and is 64 bit too.
Also, to those that werent able to flash/boot from it, you unlocked your bootloader right? Forgot to mention that it needs to be unlocked for this to work
I haven't had a chance to give this a go. I'm making sure I understand everything and the risks. More than willing to give it a shot tho
In the process of dirty porting TWRP again to the E6. The only issue is I now have Windows on my PC (for very important personal reasons) and Carliv Image Kitchen is only available on Linux. Here's the steps I need to take to get you guys the 2nd "alpha" of TWRP:
1) Beat Broken Arrow in Payday 2 so I can go back to Linux
2) Download the recoveries/image kitchens for everything again to do the port
3) Do the dirty port and upload it
Currently I'm working on step 1, but it should be done by the end of this night.
NEW RECOVERY IS UP!!! Go download Attempt 2 and see if it gets you any further. If that breaks, try Attempt 3.
Got a moto e6 recently just as an Android device to experiment/mess around with (Mostly been into iOS and Jailbreaking) and stumbled across this thread. Whats the current situation with this? Is the TWRP port working?
Tim0xff7 said:
Got a moto e6 recently just as an Android device to experiment/mess around with (Mostly been into iOS and Jailbreaking) and stumbled across this thread. Whats the current situation with this? Is the TWRP port working?
Click to expand...
Click to collapse
Attempt 1 didn't work, waiting on someone to try Attempt 2, and if that doesn't work then 3. If you want to help (I'd really appreciate it) unlock your bootloader and try to boot/flash into one of the images I gave
I'd love to help! Bootloader is already unlocked so I'll try flashing and then get back to you with results
Some observations so far:
-Using fastboot to boot an image flat-out doesn't work. I'd hazard a guess and say it's due to Pie requiring system-as-root and the boot image not utilizing a ramdisk, but honestly I don't really know.
-The init executable from the stock recovery is 32-bit, and everything I've seen so far indicates an entirely 32-bit build for the E6. Using 64-bit TWRP bases probably won't work; the second and third attempts linked in the first post do not boot, and attempts to boot to recovery with them flashed will fail, with the phone continuing on to boot the system regularly, which in turn restores the stock recovery image.
-On the other hand, with what I believe is your first build, and my own test using the standard E5 TWRP as a base, I can get as far as the TWRP splash screen, where it locks up indefinitely.
-I've also tried creating my own device tree based on the E5 tree and building from scratch without any further success, although in fairness I've only been at it for a couple of hours.
FEGuy said:
Some observations so far:
-Using fastboot to boot an image flat-out doesn't work. I'd hazard a guess and say it's due to Pie requiring system-as-root and the boot image not utilizing a ramdisk, but honestly I don't really know.
-The init executable from the stock recovery is 32-bit, and everything I've seen so far indicates an entirely 32-bit build for the E6. Using 64-bit TWRP bases probably won't work; the second and third attempts linked in the first post do not boot, and attempts to boot to recovery with them flashed will fail, with the phone continuing on to boot the system regularly, which in turn restores the stock recovery image.
-On the other hand, with what I believe is your first build, and my own test using the standard E5 TWRP as a base, I can get as far as the TWRP splash screen, where it locks up indefinitely.
-I've also tried creating my own device tree based on the E5 tree and building from scratch without any further success, although in fairness I've only been at it for a couple of hours.
Click to expand...
Click to collapse
PM me. I've got a buddy who's more into kernels and things like that that can probably help us. I'd like to help too, but I can't promise much as I've never done kernel development before
Any headway on this front?
Hey OP, I got it to boot to the TWRP logo, but it won't fully boot into recovery. is there something I'm missing? sorry, I sorely want to install liveboot again on my device, and I feel like I'm being an idiot with some huge oversight on my part haha. is it functional?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
I'm only asking because I've sat at the TWRP logo for more than half an hour sorry to bug you
Daltonyx said:
Hey OP, I got it to boot to the TWRP logo, but it won't fully boot into recovery. is there something I'm missing? sorry, I sorely want to install liveboot again on my device, and I feel like I'm being an idiot with some huge oversight on my part haha. is it functional?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
I'm only asking because I've sat at the TWRP logo for more than half an hour sorry to bug you
Click to expand...
Click to collapse
The TWRP is not working. None of them are. The original poster has said in some recent comments that they plan on buying the E6, so maybe in the future we may get a fully working TWRP. I sure hope so, because my E6 has been collecting dust in my drawer for about a month now. I've been content with my G6 and G7 Power but I can't stand such a nice but unused phone.
Since Visible is pretty much giving away the e6 with any old trade in maybe the op will finally get one.