[SLOT A/B devices] Universal A/B-cloner - Android Software Development

I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING
THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER
IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK
Ok, thats over with
INFO:
This is just a simple script, in a simple ZIP, designed to clone all the devices ACTIVE slots in /dev/block/bootdevice/by-name to the INACTIVE ones
it does nothing more, nothing less.
For me, this solved some issues with lineage and custom roms on my device and keeps my mild ocd... well.. mild.
This will not touch any partition with the word logo in it (lowercase only for now, oops)
BASIC HOW-TO:
0) have basic knowledge of how android works, dont be stupid
1) flash rom
2) run AB-Cloner-test
3) If the test runs normal rename it to AB-Cloner.zip ( remove the word "test" from the zip name)
4) run AB-Cloner
5) ???
6) profit!
Tested devices:
Successful tests:
Motorola Z² Force
(report your success below)
Unsuccessful tests:
PLEASE report below, so no one else endangers their phones
Known Bugs/Issues:
currently the word test must be lowercase in the filename, if any letter is not lowercase in the word test IT WILL RUN THE ACTUAL COMMANDS. this will be fixed in RC2/Normal releases
You tell me ?
TODO:
add VOL key detection to cancel zip/ make choices
update detection: figure out which slot is newer, flash that one to older
aroma? probably not tho
You tell me?
C+ slots? if theres a device that needs it
Pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
RC1: here (GDrive)

Ae3NerdGod said:
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING
THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER
IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK
Ok, thats over with
This is just a simple script, in a simple ZIP, designed to clone all the devices ACTIVE slots in /dev/block/bootdevice/by-name to the INACTIVE ones
it does nothing more, nothing less
for me, this solved some issues with lineage and custom roms on my device
BASIC HOW-TO
0) have basic knowledge of how android works, dont be stupid
1) flash rom
2) run AB-Cloner-test
3) If the test runs normal Rname it to AB-Cloner ( remove the word test from the zip name)
4) run AB-Cloner
5) ???
6) profit!
Known Bugs/Issues:
- currently the word test must be lowercase in the filename, if any letter is not lowercase in the word test IT WILL RUN THE ACTUAL COMMANDS. this will be fixed in RC2/Normal releases
- You tell me ?
TODO:
- add VOL key detection to cancel zip/ make choices
- update detection: figure out which slot is newer, flash that one to older
- aroma? probably not tho
- You tell me?
- C+ slots? if theres a device that needs it
Download:
RC1: here (GDrive)
Click to expand...
Click to collapse
This is good work
([emoji3590]09-09-18[emoji3590])

PoochyX said:
This is good work
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
thank you!

FYI I just ran this on my G7 Power (Ocean) and it seemed to work just fine. I had a good Resurrection Remix install on Slot A (active) and some weird borked stuff on Slot B.
I loaded and ran the .zip via adb sideload, it copied everything over, and it all seems to work just fine now, and identical on both slots.
FYI when running it this way (adb sideload) the name included "-test" but there was no test. It just ran--luckily it seemed to work OK.

Oneplus 8 5G UW (IN2019) did not work

Related

How to root, step-by-step.

ok guys, so first, i want to apologize for my bad english. im not very good when it comes to writing and talking.
let's go; what we are going to do is flash the ROM with aan included ROOT, with the posibility of wiping our device.
I remind you that: **I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE OR YOUR COMPUTER.**
**I RECOMMEND CHARGING YOUR BATTERY TO 100%**
**I ALSO RECOMMEND YOU TO MAKE A COPY OF ALL YOUR DATA**
YOU WILL MISS YOUR GARANTY IF YOU ROOT YOUR DEVICE**
​
First step: DOWNLOAD THE ROM Through this link and place it in your desktop.
2. you will also have to download ODIN 3​
3.in Developer options, activate the USB Debugging option (Settings --> Developer options --> USB Debugging
Ok, you have to start ODIN and you have to get your device in Downloading Mode. (you will do this by shuting it off. and then pressing *VOLUME DOWN KEY*+*HOME KEY*+*POWER KEY*. when you do that you should press the volume up key) When you are in Downloading mode you should connect your device to your PC.
4. Once synchronized, with Odin, you have to select "OPEN" where it says PDA. select the archive you downloaded before. (the one with the name *I8190XXALK6_I8190XEFALK1_HOME_ROOTED.tar.md5*) (you have to uncompress that item before using it)
5. then you press start in Odin, and wait 'til the instalation finishes. the your device should reboot and odin should show a message saying PASS!
6. then you should be able to boot your device like you do normally.
EXTRA STEPS JUST IF YOU HAVE ANY ERROR​
1. if you cant boot, you will need to WIPE your device instaling this archive and use it like in step 4 through the PDA button.
2. if you still have any problem, you should install this following step 4.
how your device should look like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any problem or suggestion, please comment and thank.
This will install an older December rom! I'm afraid it's a step back, and bad advice.
Most countries have moved on from the LL2 rom in that file.
The instructions also mention the LK6 rom, which is even older, and not attached above.
this is avicoh first rooted rom and it was posted here on the forum long ago. I dont know why u reposted, to be honest i wayted for u to post but thought u come up with another solution that doesnt include Odin.
Best regards,
Yeah this isn't anything new, I and everyone here thought there was some kind of new ROOTING method. The Rom is already Rooted.
Sent from my GT-I8190 using xda premium
This has been covered before in the correct forum. Read before posting.
Posted in the wrong topic, my apologies to mod's.

How to reload the OS on your BlackBerry Priv

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With the autoloaders for the BlackBerry Priv now available for download, there's sure to be folks needing to know how the whole process works, and we're glad to help with that. Take a look at our full run down of how to reinstall the OS on your BlackBerry Priv. It's all fairly easy, but do keep in mind you will need to have a Windows or Mac computer to complete the process plus, reinstalling the OS will indeed erase all local data.
Overview
* Install the USB drivers for the Priv. To install the Priv drivers, click here.
* Download the autoloader file for your Priv version from the following URL: AT&T, T-Mobile USA, Verizon, Non US Carrier - STV100-1, STV100-3, STV100-4
* Press and hold both the Power and Volume Down buttons for 30 seconds to boot the Priv into fastboot mode. Alternatively, press and hold the Volume Down while turning on Priv and selecting Reboot into fastboot (when in fastboot mode, the Priv will display the BlackBerry Bootloader Menu and a purple LED)
Windows
* Open and extract the downloaded autoloader file (including all files and folders)
* Open the extracted folder
* Execute the flashall.bat
* Follow on screen instructions as prompted
Mac OS X
* Open and extract the autoloader file (note the location of the downloaded autoloader file (example: Documents, Downloads, Desktop)
* Rename extracted folder to Priv
* Open Terminal (Finder > Applications > Utilities > Terminal)
* Type cd /Priv
* Type ./flashall.sh and press Enter
Follow on screen instructions as prompted
Note: Completing the reload of the OS will erase all local data from the Priv.
Once completed, you should have a fully wiped device and be able to start entirely fresh with the setup process of your Priv. If you run into any issues, be sure to head on into the CrackBerry BlackBerry Priv forums to get some further help. And as always, you use these files at your own risk, don't blame us if you break things.
(Please note the above article is taken from Crackberry.com website:
How to reload the OS on your BlackBerry Priv | CrackBerry.com
http://crackberry.com/how-to-reload-the-os-on-your-blackberry-priv)
Can I flash "Non US Carrier" ROM on a AT&T Priv?
lacordaire01 said:
Can I flash "Non US Carrier" ROM on a AT&T Priv?
Click to expand...
Click to collapse
Did you try? I have the T-Mobile variant and it has way too much bloatware on it.
Crimson Ghoul said:
Did you try? I have the T-Mobile variant and it has way too much bloatware on it.
Click to expand...
Click to collapse
I tried, but the phone does not start after flashing it with Unbranded ROM... stuck in boot loader menu. I tried some combinations of files too but nothing worked.
Now I'd flashed the AT&T ROM again and the phone is working as before.
I tried but my priv got stuck in bootloader menu. any idea why?

Gapps is bugged / TWRP does not recognize its own backup (x722)

hello, I require your help to operate my cell phone, I'll tell you step by step what I've done... [it is obvious that my native language is not English]
first, i installed TWRP following this tutorial https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
second, backup the complete system with twrp 3.1.1-0 (O.S. 5.8.0.20S Stable, android 6.0.1, Banggood international version). This left me a folder full of files which twrp does not recognize when I want to install that backup again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
third, Install the ROM by following this tutorial https://forum.xda-developers.com/le...ent--and-mods/stock-eui-5-8-20s-x722-t3680624 Something seems strange to me that when I run the .bat, the phone reboots in a couple of seconds and the only change I see is that it installs the original recovery, since everything else stays the same, even the system version (EUI version: 5.8.001D (Dev))
Finally install S.U. official (all correct), and OpenGApps, use the Stock and Nano (ARM64, Android 6.0) versions, and both show error when starting the system,
does not allow me to do anything (attached image).
So here I am, with a new cellphone, without being able to restore the copy made with twrp, using a EUI developer version, and without being able to install the Gapps.
---I would greatly appreciate your help---
I have just solved my problem, since after installing my TWRP backup (which I was taught a little recently), It could not start because asked for a false password, then, without deleting anything, i installed from fastboot the ROM X722-5.8.020S-by-Batyan, that is here in xda, and arranged.
https://forum.xda-developers.com/showpost.php?p=74129299&postcount=41
How can I end the post?
Kaidodal said:
I have just solved my problem, since after installing my TWRP backup (which I was taught a little recently), I could not start because I asked for a password and it did not accept it, then, without deleting anything, install from fastboot the ROM X722-5.8.020S-by-Batyan, that is here in xda, and arranged.
How can I end the post?
Click to expand...
Click to collapse
Great news. You don't need to do anything. You've done your part. :good: Just leave it up for people in the future to look at and learn from.

I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck

I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
/https://imgur.com/a/NBfrIcZ
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does so it disappears from the ADB Diver Installer / APK Installer
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything. I don't understand what I am doing wrong and am very stuck sadly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Would really appreciate some help!
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
George425 said:
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
Click to expand...
Click to collapse
Ask your question here in moto g4 forum you will gets answers correctly ,because that's where you should have asked, buts it OK here is the link https://forum.xda-developers.com/mo...hread-question-noob-friendly-t3526598/page175
And upload the photos in Google drive and turn on the link sharing feature and post the link there there are many people there to help you out. Don't worry, everything will be fine.
Thank you Dhanush-raj I will do that now.

Samsung Galaxy J7 Refine - Root with Magisk - J737p - J737PVPS2ASA1 - Android 8.0

Credit goes to:
 @☆KØŁØЯΛĐØ☆ providing some of the device files + the original guide for another j737p variant this was modified from + testing/porting aforementioned root method
 @topjohnwu for Magisk as always !!!
The link below is to the thread for the guide to root the j737p J737PVPU1ARG3 variant in which I modified this guide from.
https://forum.xda-developers.com/galaxy-j7/development/twrp-root-galaxy-j7-refine-8-0-boost-t3916575
------------------------------------------
Download all files needed as well as this guide saved to a .txt document here:
https://www.mediafire.com/download/uckb1mji1r01f9m
------------------------------------------
Read all before just winging it and follow directions with precision !!!
( Run all progams by right click - Run as administrator )
Step 1
Unzip - Odin3_v3.13.1 ( non-patched ).zip + Install the samsung USB drivers via SAMSUNG_USB_Driver_for_Mobile_Phones.exe
YOU MUST PAY ATTENTION TO THE FOLLOWING
- In the Step_1.zip you extracted, load up Odin_v13.1 (non-patched)
- Load only the BL/AP/CP files from your stock firmware into Odin
- As soon as the flashing process ends, you must reboot quickly back into Download Mode. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.
Step 2
Assuming you followed directions...
- Close Odin_v13.1 & unplug your device while still remaining in Download Mode
- Launch Odin_v13.1 [Patched] & load up the patched_boot.tar in the AP slot
- Reconnect device & proceed to flash
- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)
( It may get stuck at a soft bootloop on the samsung logo, if it does just hold the power button and volume down until it reboots again then let go. ) ( should not have to repeat this more than once or twice )
- When device reboots to Setup Wizard, skip through it. Do not add any accounts (Google or Samsung). Do not consent to giving any device data for whatever purposes (they will ask twice; look carefully)
- On the home screen, Go to settings - unlock Dev Options & allow USB Debugging. OEM should already have been unlocked.
Step 3
- Connect device to your pc & in the platform-tools+Magisk folder you, run CMD.exe
- Input adb devices to ensure proper connection
- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device
- Open MagiskManager & make sure everything is good to go (see attached screenshot)
- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access
ĐØΠΞ
Again many thanks to:
@☆KØŁØЯΛĐØ☆ - for the Original tutorial and testing via another j737p variant.
@topjohnwu - for Magisk
and credit to Vyp3r ( Myself ) @fsceo - for the files pertaining to this variant and modification of the original tutorial.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Would this work to root my SM-J737P with firmware J737PVPS9BUD2 on Android 9.0? What other files do I need to accomplish this? Thanks!

Categories

Resources