I am seriously irritated with 2 partition bs while im screwing up my phone with different ROMs, TWRP's , ROOT est...
So is there any way to merge partitions so i can have one ?
I read somewhere that flashing MIUI is solution but i really dislike MIUI so i want to have possibility to flash different roms and i dont know if they demand 2 partition
no.
yrakun said:
I am seriously irritated with 2 partition bs while im screwing up my phone with different ROMs, TWRP's , ROOT est...
So is there any way to merge partitions so i can have one ?
I read somewhere that flashing MIUI is solution but i really dislike MIUI so i want to have possibility to flash different roms and i dont know if they demand 2 partition
Click to expand...
Click to collapse
I don't understand the problem.
The easiest way to avoid issues with two partitions is once you upgrade a partition only boot from that one.
I normally flash BOTH partitions with the same OS version.
The issue is because although the ROM has a different partition, the settings for the phone are stored in a common partition.
Switching between rims in different slots will cause issues.
Related
http://forum.xda-developers.com/showthread.php?t=1315982
I tried this on my A2 and it works.. Not sure if it helps yall to know that or not. I was able to boot into recovery by holding volume up and down while powering on then selecting bp tools. Idk where to post this either.. Could we use this to install custom roms? The droid 3 has similar hardware to ours, What would happen if I used safestrap and installed a droid 3 rom?
Do not try to install a Droid 3 rom. While this may help us in some way the architectures of the devices are very different and you will more than likely end up with a bricked device.
If your able to dual boot with this then wouldn't that mean that i'd be unable to brick my phone because the os that i'm flashing is installed to a second partition? ...It is able to dual boot android on a droid 3.
Nvm.. It cant mount /emmc
Jimmy273 said:
Do not try to install a Droid 3 rom. While this may help us in some way the architectures of the devices are very different and you will more than likely end up with a bricked device.
Click to expand...
Click to collapse
Please listen to Jimmy, you are talking about installing something that was not meant for our phone. As similar as they may seem they aren't the same. No one wants to see you brick your phone but at the same time YOU'VE BEEN WARNED AND WE HAVE NO WAY OF HELPING YOU RECOVER RIGHT NOW!
I didn't flash it.. It cant mount /emmc which i assume is where the second file system goes so, I don't wanna brick my 4th atrix just yet.. But the backups that the safestrap recovery make are just over 200mb bigger why is that? and there is a boot folder but its empty. Will this be any help in the custom roms area?
Someone already posted something like this from the Bionic which is even cloder to our phone. Like they said PLEASE DONT FLASH THAT ROM...or any ROM not made for the Atrix2. To answer your questions
EMMC is internal media space, or internal storage that is user accessible. We do not have that space, our 8gb of internal space is not user accessible.
The backups are 200mb bigger because of Webtop (assuming you are comparing it to a Droid 3 backup)
I do not know why the boot folder is empty. A reason why it may not be safe to use this bootstrap.
Nope, I'm comparing backups I made from my a2. one with the atrix bootstrap and one with the droid safestrap. the one made with safe strap is actually over 300mb bigger. Is that because of webtop?
Not that i want to see you brick your A2, but were you able to restore a backup? That is the only that scares me about doing any kind of tweaks. I like to do backups anytime I am doing any kind of changes, just in case i blow it up. Once we get an SBF to flash back to stock, I won't be worried.
Are there not any CWM/TWRP Flashable ZIPs for stock or GPE ?
I've just spent frustrating hours trying to get stock or GPE running, on my GSM device that's been happily running CM11 for a while. This in part because I'm running Linux and there's no way to get mfastboot running I guess. Tried under Linux Wine but no luck.
Only after grabbing a windows PC and messing around a bunch have I been able to get CWM re-loaded after a partial install of GPE; The GPE recovery flashed OK but /system failed.
On other popular phones, there have always been flashable ZIPs of stock derived, and GPE derived ROMs. So I could keep custom recovery and easily switch ROMs, in order to test my apps.
If there are no such solutions for MotoG, I'll just have to stick with AOSP ROMs I guess. Is there some technical reason, or just not enough dev interest in ZIP flashable versions of stock and GPE ?
Thanks for any thoughts !
Yeah, I always get nervous with fastboot flashing cause anything can go wrong. Would really love some flashable stock roms. Or atleast a tutorial on how to make one. I have the dual sim version and I am running a GB firmware with cm11 (single working sim). I am guessing that would make things even harder to make a flashable rom to revert to the dualsim firmware (or impossible). Will a simple twrp backup suffice for restoring stock?
Edit: http://forum.xda-developers.com/showthread.php?t=2605824
This might be what you are looking for. Not for dualsim though.
This would be a nice thing to have. Flashing through fastboot is straightforward, but a pain...
divergens said:
This would be a nice thing to have. Flashing through fastboot is straightforward, but a pain...
Click to expand...
Click to collapse
It's not straightforward when it's a proprietary Mfastboot from Motorola.
And Mfastboot is only for Windows and we can't run it from Linux, even with Wine.
Since a lot of Android devs, such as myself, run Linux exclusively, this is a pain. At least the popularity of Samsung has resulted in MobileOdin, to flash firmware on phone, as well as Heimdall to flash from Linux PC.
I gave up on Motorola some time ago. I hoped the new "Google Moto" would be different. With the Moto G and Moto X it looked like the "Google Moto" was finally here. Now the sale to Lenovo... I'm not so happy with "Lenovo Moto".
And since I'm ranting, LOL, what's with the phone date being reset to 1970 (!!!!) ?? I guess they saved a penny or two in hardware with this trick...
hemanthmahesh said:
Will a simple twrp backup suffice for restoring stock?
Click to expand...
Click to collapse
I'm not sure...
hemanthmahesh said:
Edit: http://forum.xda-developers.com/showthread.php?t=2605824
This might be what you are looking for. Not for dualsim though.
Click to expand...
Click to collapse
Thanks. In theory it should work.
In practice it wrote over my custom recovery, then it tried, and failed, to write the system partition. I have no idea why.
This left my MotoG in a state where I had to mess with a Windows PC again, and waste another 30 minutes of my life.
So, AOSP only for me I guess...
(Must. Resist. Temptation to flash non-AOSP. Forever. Or be doomed to waste more time.)
(I have 20 app test phones I've flashed with MANY ROMs each over 3 years. Every stinkin' phone is different, pretty much, and requires different tricks and poses different problems. Each seems to require a minimum of 20 hours of reading and messing about to unlock, root, add recovery, backup, save EFS, avoid corruption bugs, etc. Buying a new test phone is just the START of the "investment" in it. What a pain, LOL.)
Some stock ROM downloads contain motorola fastboot for Linux.
1970 is Unix epoch. Google for it if you want to know more. I'd thought a dev working on Linux would know that already
scott_doyland said:
Some stock ROM downloads contain motorola fastboot for Linux.
Click to expand...
Click to collapse
Really ?? Can you or anyone clue me in to which downloads have a Linux version ? Thanks !
scott_doyland said:
1970 is Unix epoch. Google for it if you want to know more. I'd thought a dev working on Linux would know that already
Click to expand...
Click to collapse
Oh, I've known that since the 80's, along with obscure experience with real ASR33 110 baud TTYs with punch and reader in my basement. Then there were "television TTYs" with 24 lines and 40 columns or less, LOL.
I'm just griping that the clock isn't automatically set. AFAIK some phones went cheap and can't set it automatically, while others do. (?)
Anyway, even decades old PCs have BIOSes that start in the 80's or 90's or 00's, instead of the 70's. Just seems ridiculous to have to scroll through 3+ decades when setting time.
mikereidis said:
Really ?? Can you or anyone clue me in to which downloads have a Linux version ? Thanks !
Oh, I've known that since the 80's, along with obscure experience with real ASR33 110 baud TTYs with punch and reader in my basement. Then there were "television TTYs" with 24 lines and 40 columns or less, LOL.
I'm just griping that the clock isn't automatically set. AFAIK some phones went cheap and can't set it automatically, while others do. (?)
Anyway, even decades old PCs have BIOSes that start in the 80's or 90's or 00's, instead of the 70's. Just seems ridiculous to have to scroll through 3+ decades when setting time.
Click to expand...
Click to collapse
I think it's the 4.3 version (UK retail I used) from sbf-droid that has the moto fastboot. Its just called 'fastboot' though. Worked fine for me flashing stock 4.3 and 4.4.2.
4.4.2 version from.sbf-droid doesn't have it included.
Also one of the official moto x stock downloads from Motorola site has a Linux version.
If you can't find it let me know and I will attach to this thread when I get home.
1970 - fair enough I see your point. I work with IBM pSeries AIX servers and if you remove power AND the internal clock battery dies they revert to 1970 on boot up as well - and they cost tens of thousands of pounds/dollars.
I have Sony Xperia Miro i basically have no idea where to begin i know i have to root but what are the things i should know and how it works ?
From where should i begin and what are the odds of System crash and which version i will be getting after upgrade.
please help
You have rooted your phone, so the first thing you should do, is get yourself a recovery (CWM or TWRP) and make a full system backup. That's important because you will have something to come back to in case you end up messing your phone.
Now, if you plan on installing ROMs based on stock, you can straight away use recovery to install them (the instructions for each ROM are given along with the ROM).
In case you want to install a custom ROM, aka something built from a source different from the stock like the Cyanogenmod or Paranoid or MIUI or something based off on them, you gotta first unlock bootloader. There are pretty nice tutorials for unlocking bootloader using flashtool.
That reminds me, always have a flashtool and ftf file for your phone handy. Flashtool always helps, as long as your hardware isn't damaged that is.
Now talking about risks: There are a lot, but I never faced any that made me lose my buddy.
1) Your motherboard may get fried. Don't worry, it happens 1 in 100 or maybe 1000.
2) Phone sometimes overheats.
3) During installation of a ROM, you may encounter an error and phone may go into bootlop (Go upto logo screen and be there forever). Backups and/or Flashtool comes to the rescue here.
4) Never flash a ROM with the memory swiped (internal -> external exchange). I have seen somewhere that it causes a hardbrick.
A hardbrick is when you gotta go to service centre. Your phone isn't going to start anymore.
A softbrick is when there's some problem with the software. You can fix it using flashtool or backups of recovery. Someone who keeps on switching ROMs (like me ) faces it a lot. Just follow all steps and you will be alright.
In the end, luck has some contribution too
maxzeroedge said:
4) Never flash a ROM with the memory swiped (internal -> external exchange). I have seen somewhere that it causes a hardbrick.
Click to expand...
Click to collapse
Not really, at least on my J - I've been flashing few roms like this and everything is fine. The only thing worth mentioning is that cwm isn't tricked by memory swap, so backups and roms should be on external in it.
Saleen28 said:
Not really, at least on my J - I've been flashing few roms like this and everything is fine. The only thing worth mentioning is that cwm isn't tricked by memory swap, so backups and roms should be on external in it.
Click to expand...
Click to collapse
Oh well, good for you. I have tipo, but I never tried it. I was just mentioning it because the one who said that was pretty confident about it. You know its better to warn than to mourn (I know they don't rhyme),
Can please some good developer manage to provide something like that custom twrp with dual boot or any other alternative way?
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Slim K said:
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Click to expand...
Click to collapse
Your device already rooted right? How long u wait to unlock bootloader?
Kuma_Chaser said:
Your device already rooted right? How long u wait to unlock bootloader?
Click to expand...
Click to collapse
You have to wait 604,800 seconds. Same for everyone
A possible solution could be to create a new dynamic partition and flash your custom OS onto it.
people on xda working on that for other fons already here (TWRP), here (TWRP) and here (orangefox). would be great to have that for poco x3 nfc too
Slim K said:
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Click to expand...
Click to collapse
drahtwurst said:
people on xda working on that for other fons already here (TWRP), here (TWRP) and here (orangefox). would be great to have that for poco x3 nfc too
Click to expand...
Click to collapse
Did you check those posts and above comment? They all do use A/B partitions the x3 does not have. And imo a true non buggy/ deep hack multi boot solution without partition support is yet to find.
i was showing links i found for anyone interested and hopefully//partially//capable in developing a solution. it is clear, the poco does not have a/b patition scheme. are you mad i did not provide a solution?
drahtwurst said:
i was showing links i found for anyone interested and hopefully//partially//capable in developing a solution. it is clear, the poco does not have a/b patition scheme. are you mad i did not provide a solution?
Click to expand...
Click to collapse
Why should I be mad? I am not interested in dual boot. I am just telling you, that it wont be of any help as all 3 links point to OnePlus devices (2 also to already linked OP7) where TWRP/OF does make use of A/B partitioning. It doesnt mather how many twrp dual boot links you post if you can clearly see that they use s.t. which the x3 nfc does not have.
To make that more clear here mi a2 A/B do you think it will help? No. Several old methods of dual booting, one thing more buggy than the other https://www.xda-developers.com/dual-boot-on-android-a-power-users-holy-grail/ and lets not forget https://forum.xda-developers.com/t/app-boot-manager-pro-dual-boot-unlimited-roms-wip.1617055/ ... all useless (never stable or for A10+ anyway). There was this rel good working method for Sony Dev. loading up in early in modified kernel but yeah device specific, limited kernel & Co. .... Had no future. Except A/B partitioning there is simply nothing that works (good and/or modern devices).
you have clearly more oversight. i just guessed A/B partitioning can be done somehow. maybe dual boot is not even the best solution for what i am looking for. it used to be for me some years ago.
still searching for best solution to use banking+navigation but avoid gaugle + tracking as much as possible. keeping data with myself using FOSS apps+nextcloud is what i started with recently. OT.
I'm running OOS 10.3.8 on my OP 7Pro (GM1917). Currently, I boot into that OS via the B partition.
I'd like to duplicate everything in the B partition and install it on the device's A partition, so that I can switch between the A and B partition and boot up identically, no matter which partition I choose.
In the past, I did what is described in the two following posts in order to duplicate B onto A:
https://forum.xda-developers.com/t/...droid-device-partitions.2450045/post-83339451
https://forum.xda-developers.com/showpost.php?p=83389563&postcount=2818
I could do that again, but I'm wondering if perhaps a newer way of accomplishing this might have been developed since back then.
Thanks in advance for any thoughts or suggestions.
HippoMan said:
I'm running OOS 10.3.8 on my OP 7Pro (GM1917). Currently, I boot into that OS via the B partition.
I'd like to duplicate everything in the B partition and install it on the device's A partition, so that I can switch between the A and B partition and boot up identically, no matter which partition I choose.
In the past, I did what is described in the two following posts in order to duplicate B onto A:
https://forum.xda-developers.com/t/...droid-device-partitions.2450045/post-83339451
https://forum.xda-developers.com/showpost.php?p=83389563&postcount=2818
I could do that again, but I'm wondering if perhaps a newer way of accomplishing this might have been developed since back then.
Thanks in advance for any thoughts or suggestions.
Click to expand...
Click to collapse
Well, I got impatient, and I just re-ran what I described above, and it worked.
I'm still wondering if there might be a better way to do this, however.