If my upgrade fails, how do I boot from the slot that I installed the crap on the inactive slot from so the phone boots to the old version before the update?
I wanted to know and found the answers. I'll post here in case anyone wants to know cause I found nothing on these forums:
How to Check if Partition Slot A or Slot B is Currently Active?via https://krispitech.com/check-partition-slot-a-b/
Make sure the smartphone is connected to the PC with a USB cable
Now boot the smartphone into Fastboot Mode
This process will vary from device to device but usually involves holding certain button(s) down during the boot cycle.
Open up a Command Prompt, Windows PowerShell, or a Terminal in the same folder as your ADB and Fastboot files
Type out the following command. . .
fastboot getvar all
. . .then press Enter on the keyboard
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device
{
"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"
}
In this instance, my device was currently using partition slot B.
How to Boot from One Active Partition Slot to Anothervia https://krispitech.com/change-active-partition-slot/
Boot the smartphone or tablet into Fastboot Mode
Connect the device to the PC with a USB cable
Open a Command Prompt, PowerShell, or Terminal and type out the following command. . .
fastboot --set-active=a
OR
fastboot --set-active=b and then press Enter on the keyboard
Make sure you get a successful OKAY response before restarting the device
So if my updates go pear-shaped, I should be okay. And if not, well, I'm not buying a OnePlus ever again cause I've had it with all the extra steps, headaches, and disappointments with this model.
Excellent guide, I like it.
Think check out TWRP too, I think ( not 100% ) but I think it can change slots for you too.
Related
Hi Folks,
I am running Mac OS X 10.8.2 and I have ran into the following issues. I am trying to root a friend's Nexus 4 that's on 4.2.2, unlocked bootloader and USB debugging enabled/on.
I can easily root this on my Windows desktop but I thought I'd try out the Mac. Do note that I am not getting the "Allow USB Debugging" message that pops up on the phone when you connect it to a computer normally and you select Allow for the respective RSA key. The one that shows up after 4.2.2 is updated from 4.2.1.
I am not getting the above prompt when hooking up the phone to my Mac. *PS I removed the name of my MBP pro and the user name.
Okay so here are the two issues/scenarios:
1) I downloaded the latest ADB and Fastboot Mac OS X 64 bit files from the ADB dev tools website, etc. The files are "adb" and "fastboot"
When I type "./adb devices" since the "./" command is for Mac on the terminal, I get the following message and it does not show up any device listed.
{
"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"
}
Then when I type "./adb reboot-bootloader", I get the following:
__________________________________________________________________________________________________________
2) When I use an older adb and fastboot files from last year: "./adb_Mac" , "./fastboot_Mac" and "ADB-Install-Mac.sh", I get the following:
When I type in the adb devices command and the adb reboot-bootloader command:
The serial # shows up this time (Again I have crossed out half of it lol)
When typing in the reboot-bootloader command:
Now to my knowledge, I know that I am getting the device offline mode based on using the old ADB and Fastboot files. So the way to fix it, is to download the updated files but it doesn't result in anything at all.
With the updated ADB and fastboot files, and by booting into fastboot mode manually and then typing in ".fastboot devices", I get the Error Could Not Get Pipe Properties error in a loop.
Would appreciate the help folks!
T.I.A
Try this command
adb kill server
adb start server
scream4cheese said:
Try this command
adb kill server
adb start server
Click to expand...
Click to collapse
Beauty! I didn't know that it has to be done for the same in OS X. Query, does this have to be done every time or?
So i was searching around and couldnt find actual answers on how to get rid of that annoying ass sticky bit factory fastboot menu when phone powers up. So i decided to take matter in my own hands and learn a little bit about adb and fastboot commands etc.. Typed in some commands in a certain order and BOOM sticky bit no longer gets in the f-ing way ^^ this should work on any android powered phone seeing how it doesnt go to any specific phone. So far i learned that it works on the xpirea (how ever you spell it) and the droid razr m consumer and dev edition. so here we go.
MAKE SURE YOU HAVE USB DEBUGGING ENABLED
Files to download:
Android.zip: http://www.mediafire...0imf9xv2uicwkbh
Latest usb drivers: http://www.motorola....motodev_lp.html
STEPS
1. Power up your phone completely.
2. extract the folder in the android.zip file to your local disk. just drag the folder to local C: or whatever your main HD is
3. hold left shift and right click on the folder and click on pen command window here"
4. plug in your phone if you havnt done so already
5. in the command window type: adb devices ( this makes sure your phone is connected and it'll show its serial number under List of devices attached.
6. once it shows the serial number type in these commands ( these are in order)
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
and walla phone will reboot like when you first got it ^^
{
"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"
}
Your links are broken.
This seems cool. But I don't know what menu you are talking about, perhaps more clarity, as I'd like to know what causes this menu to be shown and if I am just missing it somehow. Curious to know if this fix may aid me in the future. As probably are some other users.
Also probably helpful for you to note that fastbooylt erase userdata will clear user settings.
Sent from my XT907 using xda app-developers app
Thank you...
Your steps got me out of the sticky mess...
SOLVED UPDATED TO LAST OTA AND DID THE WHOLE TUTORIAL AGAIN.
Tried different USB ports. ( 3.0 / 2.0 )
{
"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"
}
Tried in 2 different PCs and 6 usb ports 2.0 and 3.0
Windows 8 and windows 10.
Have you tried using cmd (administrator) istead of PowerShell?
Lamizure said:
Have you tried using cmd (administrator) istead of PowerShell?
Click to expand...
Click to collapse
Yes
It's really strange... Have you unlocked the bootloader?
Yes " Device State - Unlocked "
It's due to the filename being too long. I found a different fastboot which allowed long filenames. Rename it to one letter like r.img or something and see if it works.
Had exact the same problem under Linux
People mention to change to another USB port but that did not help
What helped... if all stuff is correctly installed (adb, root rights, etc.)
1. Reboot into the bootloader (even if you are in already)
adb reboot bootloader
Click to expand...
Click to collapse
2. Then directly (use the arrow up key to really be fast enough) send the command for flashing (my file was called twrp.img)
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
If this doesn't work you could try (under Linux) to write a little script with just the two above commands or try
adb reboot bootloader && fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It seems to be a timing problem... One might need to play around with the time between this two commands. E.g. wait until the bootloader screen is on the phone and directly issue the flash command. Sorry after it worked for me I did not bother to investigate it in more detail.
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.
Hi everyone,
(Sorry if my english is bad) I recently saw Crosscall device must have a key to unlock their bootloader with fastboot (common way), and most of Crosscall devices are SnapDragon except the S4 Core, because there's an universal way for MTK to unlock the bootloader, without waiting time and key needed.
Requirements :
PC or Laptop (at least running Windows 10)
Crosscall Core S4
USB cable
/!\IMPORTANT/!\ : THIS PROCESS WILL WIPE ALL YOUR DATA, SO IF YOU HAVE IMPORTANT FILES BACKUP THEM BEFORE DOING THIS
Ready ? Go !
First : Install USBDK (depends on your processor arch download x64 for 64 bits and x86 for 32 bits)
Download MTKClient extract it and copy the extracted folder on your C: drive folder
Ok now open a Powershell session (if you're on W11) or a cmd session (if you're on W10)
{
"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"
}
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked