This is just a quick poll to find out how many G3 owners can access their bootloaders.
Terminal:
Code:
su
reboot-bootloader
ADB (windows):
Code:
adb reboot-bootloader
ADB (Linux):
Code:
./adb reboot-bootloader
I cannot it seems.
Cheers, glad to know it's not just me. Anyone else?
[email protected] :/ reboot-bootloader
tmp-mksh: reboot-bootloader : not found
127|[email protected] :/
D855 32gb
sabret00the said:
This is just a quick poll to find out how many G3 owners can access their bootloaders.
Terminal:
Code:
su
reboot-bootloader
ADB (windows):
Code:
adb reboot-bootloader
ADB (Linux):
Code:
./adb reboot-bootloader
Click to expand...
Click to collapse
Should be:
From device
Code:
su; reboot bootloader
PC
Code:
adb reboot-bootloader
There is no reboot-bootloader binary so your probably getting an error "reboot-bootloader does not exist" or something similar. reboot is the binary and bootloader is one of its commands.
wedgess said:
Should be:
From device
Code:
su; reboot bootloader
PC
Code:
adb reboot bootloader
There is no reboot-bootloader binary so your probably getting an error "reboot-bootloader does not exist" or something similar. reboot is the binary and bootloader is one of its commands.
Click to expand...
Click to collapse
still doesn't work. Though though typing just ADB does suggest the hyphenated version.
sabret00the said:
still doesn't work. Though though typing just ADB does suggest the hyphenated version.
Click to expand...
Click to collapse
I don't actually have the device just though I could lend a helping hand when I saw the command were wrong from adb, adb reboot-bootloader.works but on a device it doesn't. it uses the reboot binary.
wedgess said:
Is your bootloader unlocked? If you don't have the reboot binary inside /system/bin or /system/xbin then it ain't going to work. What is the shell throwing at you when you do reboot bootloader?
I don't actually have the device just though I could lend a helping hand when I saw the command were wrong from adb, adb reboot-bootloader.works but on a device it doesn't. it uses the reboot binary.
Click to expand...
Click to collapse
I just tried it from terminal and the phone just reboots, sadly not into bootloader.
wedgess said:
Hmm, is your bootloader unlocked? And can you attach the last_kmsg please.
Click to expand...
Click to collapse
Pass, tell me how to find out and I will tell you. Also where do I find the last_kmsg, my ageing brain can't remember where to find it
Bootloader is locked. Its accessible by flashing a bad boot.img. it will then take you into fastboot mode which oem unlock does nothing.
p70shooter said:
Pass, tell me how to find out and I will tell you. Also where do I find the last_kmsg, my ageing brain can't remember where to find it
Click to expand...
Click to collapse
it is in >proc>last_ksmg
also here is mine the phone reboots but not into booloader,but this is because i installed drivers from here
for the people reading my last_kmsg I tried the adb reboot-bootloader command a couple of times and just for fun I tried adb reboot oem-unlock once
last_kmsg
papi92 said:
Bootloader is locked. Its accessible by flashing a bad boot.img. it will then take you into fastboot mode which oem unlock does nothing.
Click to expand...
Click to collapse
kernel sources are up so now wwe play the waiting game I guess
Install rom toolbox or similar and choose reboot bootloader from it and see what happens
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Install rom toolbox or similar and choose reboot bootloader from it and see what happens
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
nop it just reboots the phone:crying:
Related
Hello,
I wanted to update one SE Arc Experia already running cm7, but with a few months old Rom.
fastboot is not detecting my device, and I have no ideas why. After a few hours of search, I am still unable to fastboot it.
Arc is running fine with cm7.2.0 with FXP Kernel, debug is ON.
I am on Ubuntu 11.10, and everything is correctly set up. I already flashed Rom & Kernel in the past. The file 51-android.rules is in /etc/udev/rules.d.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="gabx", GROUP:="plugdev", MODE=”0666″
the usb is working :
Code:
[email protected]:~/Xperia/xperia$ lsusb
Bus 001 Device 005: ID 0fce:0dde Sony Ericsson Mobile Communications AB
fastboot executable is in my box, with correct permission. The fastboot command works.
The phone is correctly in download mode, with the blue led (turn off, press menu, plug USB).
When I fastboot devices, I have no entry :
Code:
[email protected]:~/Xperia/xperia$ fastboot devices
[email protected]:~/Xperia/xperia$
Weird, the -i 0x0fce option doesn't seems correct:
Code:
[email protected]:~/Xperia/xperia$ fastboot -i 0x0fce devices
usage: fastboot [ <option> ] <command>
.../.... list here of all otions and command
Sudoing doesn't change anything.
Code:
[email protected]:~/Xperia/xperia$ fastboot reboot
< waiting for device >
The device is not detected. Why ??
TY for any help
EDIT
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!
gabx said:
The device is not detected. Why ??
TY for any help
Click to expand...
Click to collapse
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
gabx said:
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!
Click to expand...
Click to collapse
Don't use flash_image, it doesn't work with Xperias
Cheers,
z
zdzihu said:
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
Don't use flash_image, it doesn't work with Xperias
Cheers,
z
Click to expand...
Click to collapse
TY so much. Yes, a lot of wasting time, checking everything on my Linux box!! Your answer is nice to me, as I was doubting about my Linux set up, and now I feel safe.
I managed to settle everything today on a Winodows box, in just 15 mn! Fastbooted boot.img, flashed update from sdcard, et hop!
TY for the binary. I will use it next time on my Linux box.
fastboot -i 0x0fce devices
Click to expand...
Click to collapse
shouldnt it be
Code:
fastboot -i 0xfce devices
instead?
try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G
g el said:
try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G
Click to expand...
Click to collapse
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z
zdzihu said:
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z
Click to expand...
Click to collapse
Agree totally, no need sudoing, neither use option. As previoulsy mentioned, a wrong binary was the only culprit. Usually, fastboot is trivial in Linux, with the only condition being the correct android rules in /etc/udev.
Pardon me if this has been covered in the past, but I'm having a difficult time finding the info that I'm looking for.
I have a Kindle Fire that I had put CWM on. Yesterday, I installed TWRP and the Reloaded ICS rom.
Everything went fine and I'm very happy with the ICS installation.
However, if I boot back into recovery, then CWM loads up. I was expecting TWRP to overwrite CWM, but apparently that's not how it works.
I'm on a Mac and these are the steps I took to flash TWRP:
Connect your KF to you computer and open a terminal.
Navigate to your platform-tools folder
cd Path to platform-tools
Once here check to see your KF is recognized by ADB
sudo ADB devices
Click to expand...
Click to collapse
*Note you may have to use the command Sudo ./adb devices, it really depends on how you have your SDK setup.
If you see a series of numbers it verifies your KF is being seen by ADB. Next you'll type
sudo ADB shell or sudo ./adb shell
Click to expand...
Click to collapse
Then ask for root permission
SU
Click to expand...
Click to collapse
Next you'll need to set your bootmode to fastboot
idme bootmode 4002
Click to expand...
Click to collapse
It will tell you that <idme> write 4002 to offset 0x1000. Now you'll need to exit the shell
Exit
Click to expand...
Click to collapse
Exit
Click to expand...
Click to collapse
Once you're back in your platform-tools folder restart adb
Sudo adb reboot or sudo ./adb reboot
Click to expand...
Click to collapse
ADB will restart then you can issue the fastboot command
sudo fastboot -i 0x1949 boot twrp-blaze-2.0.RC0.img or sudo ./fastboot -i 0x1949 boot twrp-blaze-2.0.RC0.img
Click to expand...
Click to collapse
If memory serves me correctly, the device will reboot to TWRP and saying its installed. It will reboot itself. Once rebooted you'll be shown a yellow triangle with a fire on it. Don't panic as its a modified bootloader that allows you to access your recovery. It boots here because your device is still set to boot into the bootloader. To fix this type
sudo fastboot oem idme bootmode 4000 or sudo ./fastboot oem idme bootmode 4000
Click to expand...
Click to collapse
Then simply give fastboot the command to reboot
sudo fastboot reboot or sudo ./fastboot reboot
Click to expand...
Click to collapse
Your device will reboot to the bootloader again, except this time it only stays like that for a short period in order for you to access your recovery if need be. To access TWRP simply hold your power button down for around 2 seconds. Your power button will change to an orange color, release the button and TWRP will show up. If you do nothing at the bootloader your rom of choice will continue to boot.
Click to expand...
Click to collapse
Does anyone have any advice? Thoughts?
I'm very new to Android. . .
Best,
Chris
czucker said:
Pardon me if this has been covered in the past, but I'm having a difficult time finding the info that I'm looking for.
I have a Kindle Fire that I had put CWM on. Yesterday, I installed TWRP and the Reloaded ICS rom.
Everything went fine and I'm very happy with the ICS installation.
However, if I boot back into recovery, then CWM loads up. I was expecting TWRP to overwrite CWM, but apparently that's not how it works.
I'm on a Mac and these are the steps I took to flash TWRP:
Does anyone have any advice? Thoughts?
I'm very new to Android. . .
Best,
Chris
Click to expand...
Click to collapse
If you are trying to install TWRP version 2.1.x then those steps will not get TWRP installed onto your recovery partition. "fastboot boot" just loads the image into memory and boots from there. You'll need to "fastboot flash" the image to actually get it on to the recovery partition.
Just to clarify a possible source of confusion... version 2.0.0 was distributed as a boot image wrapped around the recovery image. So, the instructions were to "fastboot boot" the boot image and then it would run an internal script that would flash the recovery image contained within the boot image. Now, version 2.1.x is just a recovery image, so you'll need to flash it manually.
Code:
fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img
Thank you.
That worked perfectly.
Hi folks.
I'm trying to root my phone (ZE551ML - 2.83Ghz and 4Gb Ram) with method 3 in this thread (Using Ubuntu 14.04.1 with installed ADB 1.0.32 and android-tools-fastboot) but the script Root.sh gives me this error:
./adb.mac: 1: ./adb.mac: Syntax error: ")" unexpected
And the script is not rooting the phone.
Then i tryed to do things manually and observed that after i hit the 'adb reboot bootloader' (so i can flash the files like the script would do) the phone reboots into fastboot mode but the 'adb devices' or 'fastboot devices' didnt show my phone anymore - or anything.
Tried to do the same with phone in recovery mode and got the same result.
Can anyone help me?
Did I miss anything?
Ps. My Bootloader is locked and i have no intention of unlocking it yet.
C-Ph87 said:
Hi folks.
I'm trying to root my phone (ZE551ML - 2.83Ghz and 4Gb Ram) with method 3 in this thread (Using Ubuntu 14.04.1 with installed ADB 1.0.32 and android-tools-fastboot) but the script Root.sh gives me this error:
./adb.mac: 1: ./adb.mac: Syntax error: ")" unexpected
And the script is not rooting the phone.
Then i tryed to do things manually and observed that after i hit the 'adb reboot bootloader' (so i can flash the files like the script would do) the phone reboots into fastboot mode but the 'adb devices' or 'fastboot devices' didnt show my phone anymore - or anything.
Tried to do the same with phone in recovery mode and got the same result.
Can anyone help me?
Did I miss anything?
Ps. My Bootloader is locked and i have no intention of unlocking it yet.
Click to expand...
Click to collapse
Are you using root command prompt on your pc? You need admin privileges on pc.
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Are you using root command prompt on your pc? You need admin privileges on pc.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Yes. Using 'sudo fastboot devices' nothing happens.
C-Ph87 said:
Yes. Using 'sudo fastboot devices' nothing happens.
Click to expand...
Click to collapse
http://www.asus.com/zentalk/thread-76656-1-1.html
geopit said:
http://www.asus.com/zentalk/thread-76656-1-1.html
Click to expand...
Click to collapse
The comands in the Python Script are:
adb reboot bootloader
fastboot flash /system/bin/resize2fs magic
fastboot flash /system/bin/tune2fs busybox
fastboot flash /system/bin/partlink supersu.tgz
fastboot oem start_partitioning
fastboot flash /system/bin/logcat installer
fastboot oem stop_partitioning
The thing is that fastboot doesnt recognize my device after the 'adb reboot bootloader' and the message 'waiting for the device' gets stuck.
If you look into the thread you'll see that the 7th answer (user orlapalm) has the same unsolved issue.
Guess the solution is used somebody elses PC with Windows since there's no way to use Ubuntu on This phone.
Try this:
Code:
#!/bin/bash
adb reboot bootloader
fastboot flash /system/bin/resize2fs magic
fastboot flash /system/bin/tune2fs busybox
fastboot flash /system/bin/partlink supersu.tgz
fastboot oem start_partitioning
fastboot flash /system/bin/logcat installer
fastboot oem stop_partitioning
Save as root.sh and try again.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Try this:
Code:
#!/bin/bash
adb reboot bootloader
fastboot flash /system/bin/resize2fs magic
fastboot flash /system/bin/tune2fs busybox
fastboot flash /system/bin/partlink supersu.tgz
fastboot oem start_partitioning
fastboot flash /system/bin/logcat installer
fastboot oem stop_partitioning
Save as root.sh and try again.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Thanks but will not work.
I know how a script works but seems that Zf2 needs the Fasboot v1.0.32 - Witch i dont find anywhere.
Fastboot v1.0.31 (installed with apt-get install android-tools-fastboot) doesnt recognize the Zenfone 2 on Ubuntu.
Maybe because the USB device is not recognized, what does lsusb say before and after the reboot in bootloader?
Magister54 said:
Maybe because the USB device is not recognized, what does lsusb say before and after the reboot in bootloader?
Click to expand...
Click to collapse
lsusb (before reboot)
Bus 001 Device 004: ID 0b05:5601 ASUSTek Computer, Inc.
lsusb (after reboot)
Bus 001 Device 006: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
Fastboot cmds:
~$ fastboot continue
< waiting for device >
~$ fastboot reboot
< waiting for device >
Ps. After this I saw that device code is different after (0b05:4daf) and before (0b05:5601) reboot so i added the permission for this 'new dvice' in /etc/udev/rules.d/51-android.rules and now fastboot seems to recognize my phone.
Magister54 said:
Maybe because the USB device is not recognized, what does lsusb say before and after the reboot in bootloader?
Click to expand...
Click to collapse
Thank you very much for the tip, man!
Without it i would never solved this situation!
C-Ph87 said:
Thank you very much for the tip, man!
Without it i would never solved this situation!
Click to expand...
Click to collapse
No problem :highfive:
I cant flash everything on fastboot mode
i have usb enabled and bootloader unlocked latest
status: Bootloop, no recovery
only fastboot mode
help for a fix ... I bricked the tab
TRIED TO RETURN TO STOCK WITH FLASH ALL.BAT BUT ALL PARTITIONS END WITH UNKNOWN COMMAND
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Alessandro999 said:
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Click to expand...
Click to collapse
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
parakleet said:
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
Click to expand...
Click to collapse
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Alessandro999 said:
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Click to expand...
Click to collapse
Good job
I searched through threads on here, and the only similar one, there was no solution because OP could not unlock his bootloader.
I unlocked my device, and decided to revert back to stock. I want to retain Android Pay functionality and use Netflix, but do not want to be rooted. I flashed the latest factory images from Google, then locked the bootloader. When i went to boot the device, I was met with an error message saying that it could not find an OS, and I could not proceed from there. If i unlock the bootloader, the device will boot just fine.
Any advice? It's been a long time since i messed around with root etc. Any help would be greatly appreciated.
Flash the factory images to both slots and then lock the bootloader. Use lock_critical as well and see if that helps.
rickysidhu_ said:
Flash the factory images to both slots and then lock the bootloader. Use lock_critical as well and see if that helps.
Click to expand...
Click to collapse
Does using flash all flash to both slots? Pretty sure it says sending to slot a and b in the terminal output. I’ll try doing it manually, but thanks!
Sent from my iPhone using Tapatalk
beats4x said:
Does using flash all flash to both slots? Pretty sure it says sending to slot a and b in the terminal output. I’ll try doing it manually, but thanks!
Click to expand...
Click to collapse
No it doesn't, you have to use the set active command to manually switch slots. I forget the exact command but I'm sure you'll be able to find it with a quick search on XDA/Google.
So the steps would be:
Flash all
Let it boot at least once
Use the set active command to go to the other slot
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
I haven't tried this myself but from researching on my own, these steps seem like the correct way to do things!
rickysidhu_ said:
No it doesn't, you have to use the set active command to manually switch slots. I forget the exact command but I'm sure you'll be able to find it with a quick search on XDA/Google.
So the steps would be:
Flash all
Let it boot at least once
Use the set active command to go to the other slot
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
I haven't tried this myself but from researching on my own, these steps seem like the correct way to do things!
Click to expand...
Click to collapse
This was absolutely it. After doing this, I'm back to normal. Thank you!
As a side note, I also had to update adb/fastboot drivers.
beats4x said:
This was absolutely it. After doing this, I'm back to normal. Thank you!
As a side note, I also had to update adb/fastboot drivers.
Click to expand...
Click to collapse
could you tell me the commands you used to relock the bootloader or thread you used
xringo said:
could you tell me the commands you used to relock the bootloader or thread you used
Click to expand...
Click to collapse
fastboot flashing lock
fastboot flashing lock_critical
TheSt33v said:
fastboot flashing lock
fastboot flashing lock_critical
Click to expand...
Click to collapse
what about switching from a to b
xringo said:
what about switching from a to b
Click to expand...
Click to collapse
fastboot --set-active [a or b depending on which you want]
So if you want b to be active, fastboot --set-active b
rickysidhu_ said:
No it doesn't, you have to use the set active command to manually switch slots. I forget the exact command but I'm sure you'll be able to find it with a quick search on XDA/Google.
So the steps would be:
Flash all
Let it boot at least once
Use the set active command to go to the other slot
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
I haven't tried this myself but from researching on my own, these steps seem like the correct way to do things!
Click to expand...
Click to collapse
I want to create auto process batch with this.
So is it possible to use this steps in this way ?
set active a
Flash all
Let it boot at least once
set active b
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
thanks for your help
XiorgON said:
I want to create auto process batch with this.
So is it possible to use this steps in this way ?
set active a
Flash all
Let it boot at least once
set active b
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
thanks for your help
Click to expand...
Click to collapse
Just modify the flash all bat. To skip reboot. And and you can save yourself some time by not having to boot both of them. Just remember after you fastboot set active slot, to A or B, reboot to Bootloader for it to make the change. Then run your flash all. I don't know if it's really necessary but I do it just in case.
thanks for your help !
is good now what do you think ?
please note that. i want to make batch that will factory restore for returning the phone to google for warranty and relock bootloader
i dont know if i need to set active partition for factory restore or just for the bootloader locking process.
adb reboot bootloader
fastboot --set-active a
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip
fastboot reboot-bootloader
fastboot --set-active b
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip
XiorgON said:
thanks for your help !
is good now what do you think ?
please note that. i want to make batch ta will factory restore and relock bootloader
i dont know if i need to set active partition for factory restore or just for the bootloader locking process.
adb reboot bootloader
fastboot --set-active a
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip
fastboot reboot-bootloader
fastboot --set-active b
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip
Click to expand...
Click to collapse
If you clean flash the factory image, that will wipe your phone and return it to stock. Then you can just run the bootloader locking commands. Not sure why you want to make a script to do that, but best of luck to ya :good:
Badger50 said:
If you clean flash the factory image, that will wipe your phone and return it to stock. Then you can just run the bootloader locking commands. Not sure why you want to make a script to do that, but best of luck to ya :good:
Click to expand...
Click to collapse
ok so why is telling that is needed to set active a or b ?
i need to set it or not ?
XiorgON said:
ok so why is telling that is needed to set active a or b ?
i need to set it or not ?
Click to expand...
Click to collapse
If your clean flashing the factory image via fastboot, then it doesn't matter. It'll wipe the phone and install the OS to both slots.
XiorgON said:
ok so why is telling that is needed to set active a or b ?
i need to set it or not ?
Click to expand...
Click to collapse
I flashed the developer preview using the flashall.sh file and did not have to flash to a then b. The script takes care of that.