yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] cmegmhi:
Boot issues

I have successfully flashed the 3.0.07 rom to my blackphone 2 using adb sideload, through fastboot and through stock recovery. But when the phone boots it never ends however, sometimes it gives a message that decryption failed, the data reset required which it does and still no end of the boot process. It is to mentioned that my phone has no OS installed and it is clean. I also used TWRP for blackphone 2 as recovery. I was not able to install any rom having .zip extensions, always give error 7 or 4. however, i was able to install OS as the .img file but the same thing happens as mentioned above. One strange thing I noticed. The data partition cannot be mounted unless I format it to fat file system then to ext4. Even then when I try to reboot I get the same non ending boot process. Please help and thanks in advance
[Miscellaneous Android Development] asaflevif:
Help me please

Hi, I wish you can help me, I Install this rom for Silent OS 3.0.14 but when my phone starts, it appears the "welcome to blackphone" screen, but I can click "next" , I just can choose my lenguage but can't click "next". Does somebody know what it's happening with my phone?
[Miscellaneous Android Development] matvey123:
Following... Did you get it?
[Miscellaneous Android Development] Vuche:
I think androidblue has sold his phone and doesn't follow this thread anymore... As expected, alI other followers have unofficial BP2s and we won't get the latest working updates anymore as they are nowhere to find.
[Miscellaneous Android Development] alvinasnow:
Hello there.

I got a BP-2 from a friend, which runs on Lollipop 5.1 with a baseband .2.0.2.ci-00017-M8935FAAANUZM-1.

The Model Name is unknown and so it the build number. Certain built-in apps in the phone simply does not work and some android features such as accessibility option or date and time option, when clicked just closes down the settings tab. Moreover, the phone also has issues connecting to PC and Wifi.

Before posting my request, i did all available options to upgrade the rom to latest available on forums. I was able to flash original recoveries and TWRP. I could use ADB and Fastflash tools to experiment sideload options. Nothing seemed to have worked for me. In almost all attempts, the progress just stops at "Patching system image unconditionally......" indefinitely.

I have also tried for days to get past the issue but my bad.

I will really really appreciate, if someone can give me an idea here on what possibly could be the problem and how to address it. Once again, I am thankful to the immense help i am getting from respected gurus here.

Thanks
[Miscellaneous Android Development] SkillaVilla:
Re-Lock Blackphone 2 ?????

Hello androidblue...

So, after 'unlocking' the device...I'm trying to 're-lock' it...but I get this:

sh-3.2# ./fastboot flashing lock

FAILED (remote: unknown command)

finished. total time: 0.002s

sh-3.2# ./fastboot oem lock <---:: (got same result using 'lock-go')

FAILED (remote: For privacy reasons, can't lock an unlocked device.)

finished. total time: 0.004s

Is there a way to 're-lock' the Blackphone 2? I've got it up to 3.0.14. ??? Any advice

would be great! Thank You :confused:

PS.

According to 'Silent Circle' my BP2 is not a grey...but original.
[Miscellaneous Android Development] testadura2:
Hi, Sorry but I am unable to create a new Post for Blackphone parts.

On my Bp2 under 3.0.14 original battery can only be used half a day, so I found one in Aliexpress (2 sellers)

I also found a tutorial to open the BP2 but I broke the rear cover, it's a plastic ultra thin material, and I think it's absolutely impossible to open the phone without breaking the rear cover.

So I need to change it but I don't know where to buy it.

Searching for "Blackphone rear cover" Blackphone Back" Blackphone Shell"

My english is not too rich , any idea how to call this part? or where to find it.
[Miscellaneous Android Development] lohanette:
I've just purchased a bp2 from registered UK dealer and silent os is 3.0.3a and android version 6.0.1 security patches 5 September 2016.

When I click to update via security center-phone aettings it says "no update found" for the os and "please try again later" for silent is app updater, but I've seen unboxings on YouTube and they have more up to date software.

contacted silent circle and they won't give me an answer.

All they keep saying is "we don't deal with Blackphone please contact dealer".

Dealer says silent circle stopped pushing updates but others bp2's have newer updates in.

Any idea's?
[Miscellaneous Android Development] johnduggins:
I hadn't powered mine on for many months. Mine is running 3.0.23 (June 2018 security patches). I also get the "no update found" response when attempting to look for updates. I suspect the update servers have been decommissioned. I remember their support site had release notes for updates but no longer do. That and you're comment about their support suggests to me Silent Circle has washed their hands of the device.

I did send them a message asking if they had a download location for the latest firmware made. I doubt I'll hear anything good.
[Miscellaneous Android Development] Vuche:
This is great news johnduggins that you have version 3.0.23. Could you make a TWRP backup and post it on mega or elsewhere? Or post the update.zip file if you still have it? I guess you must have an "official" BP2 phone. Not sure if we will be able to install it on the "grey market" ones but at least we would have the files to work on them.

Mine is still on 3.0.14 I think, last one that we could install from this thread without locking our phones. Thanks in advance if you can do anything to help us.[emoji108]

Edit:

I've tried to update it via the update tab in settings, but it also tells me that there is no new update, although it was telling me 3.0.18 was available before I hit the check button. So I guess the communication with the server is broken.
[Miscellaneous Android Development] VirusF:
Is this ROM can be used on any mobile? Does it work? Thank you very much in advance. Best regards.
[Miscellaneous Android Development] oneplusfive:
Hi all,

I have experience in flashing via ADB etc, however I was wondering if someone could point me in the right direction and tell me how I should go by flashing

"BP2-OTA-3.0.7-RC3-candidate-ROW-1482330514.zip"

Should this be done via ADB sideload or?

I am currently running Silent OS 2.0.2, Android 5.1.1

Only asking as I read somewhere that flashing to 3.0.8 or 3.0.9 could brick the phone.

Any help would be greatly appreciated.

Thanks!
[Miscellaneous Android Development] hick3158:
Hi Android Blue! If you would please provide the 3.0.14 Link for North America

Hi Android Blue! If you would please provide the 3.0.14 Link for North America, it would be greatly appreciated. I'm assuming this is the last update that I could update the blackphone 2 with? What operating system do I have to be on in order to update? 3.0.9?

Thanks so much!
[Miscellaneous Android Development] drtiendiep:
Can you send link? Thank a lot!
[Miscellaneous Android Development] drtiendiep:
Can you send for me 3.0.15? Thank a lot!
[Miscellaneous Android Development] drtiendiep:
3.0.7: https://drive.google.com/uc?id=0BzRdGOqYA-Pudlh1enpqQ1BHLWM&export=download
[Miscellaneous Android Development] drtiendiep:
I appear error: This package is for "BP2" devices; this is a "bp2"; Updater process ended with ERROR: 7 Error installing zip file '/sdcard/Blackphone3014.zip' ... help me!
[Miscellaneous Android Development] drtiendiep:
[MENTION=5188944]androidblue[/MENTION] Can you fix? Thanks
[Miscellaneous Android Development] Feebles:
Hello drtiendiep,

I haven't got the 3.0.15 rom of Silent Circle, and my blackphone is dead ...

You can take the rom 3.0.14 of the first page : https://drive.google.com/open?id=0ByqsGlGfYIRdZmE3OXFadF9mSkU

Download the zip, copy it to the sdcard, boot for wipe partition and cache, and install the rom.

I hope this will working for you like it was working for me ;)
[Miscellaneous Android Development] drtiendiep:
Thank you! Final because the SD :(. I change SD and up rom normal. Thanks all! Have you got 3.0.23 zip send for me? Thank a gain.
[Miscellaneous Android Development] drtiendiep:
Have you got 3.0.23 rom? [MENTION=5188944]androidblue[/MENTION]!
[Miscellaneous Android Development] speed_boy:
I don't know what's happening but root doesn't work!!!

I don't have twrp (black screen) so i'm using command

fastboot.exe boot twrp-3.4.0-0-bp2.img

to just run it.

Then i put Magisk-v21.0.zip on sdcard and use command

twrp install /sdcard/Magisk-v21.0.zip

from adb shell

Everything goes well. I can open Magisk manager and it says that module installed. Also I have security alert that i have active root and it's dangerous blablabla.

But it doesn't work!

Total commander, root uninstaller, lucky patcher, titanium backup they all says me "you don't have root".

How it's possible? It's just for a first time for me. Usually it works like 1..2...3... done!

Tried 3.0.14 version. Flashed reflashed a few times. Tried BP2-OTA-3.0.7-RC3-candidate-ROW-1482330514.zip

the same here.

Appreciate any help!

Thanks in advance!
[Google Pixel XL Questions & Answers] bschatzow:
Here are the steps that got me to where I am.

1.	Stock Pixel XL March 2017

2.	Installed TWRP

3.	Installed SU

4.	All worked correctly for the last month

5.	Saw that there was a new April release

a.	It would not install as I was rooted

b.	I installed the April OTA using TWRP

c.	Rebooted

6.	Saw that I was no longer rooted

7.	Tried to go to Bootloader

8.	Got dead droid with no command error

9.	Went to recovery (Power + up vol) to enter sideload

10.	Sideloaded the April updated

11.	Rebooted

a.	Same no command error

b.	Went to recovery (Power + up vol) to enter factory restore

c.	Rebooted

12.	Tried to go into boot loader

a.	Same no command error

13. Problem is that twrp was not asking for pattern And would not install correctly with image file. Solution was to keep loading the twrp image file until it asks for pattern. Then follow standard twrp /su instructions.

Thanks.
[Google Pixel XL Questions & Answers] wyrdtrtle:
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
[Google Pixel XL Questions & Answers] glensta:
This should be posted under Q&A not development
[Google Pixel XL Questions & Answers] bschatzow:
Bootloader does not load.
[Google Pixel XL Questions & Answers] wyrdtrtle:
When you get the dead Droid just hit vol up, no power button.
[Google Pixel XL Questions & Answers] bschatzow:
Then what?
[Google Pixel XL Questions & Answers] mac796:
I think I know where you went wrong you installed an incremental OTA with TW RP. If I'm not mistaken that new firmware had an updated bootloader and I believe that's dangerous to do. You may be out of luck
[Google Pixel XL Questions & Answers] bschatzow:
Why would the built in factory restore fix it?
[Google Pixel XL Questions & Answers] biggiesmalls657:
Can you get into fastboot?
[Google Pixel XL Questions & Answers] mikaole:
So no bootloader.

Just my thoughts. I don't know if that's even possible.

Isn't it possible to edit the ota script to flash a bootloader?

Or even make a full factory update like this?
[Google Pixel XL Questions & Answers] bschatzow:
To use fastboot you need to be in bootloader mode.
[Google Pixel XL Questions & Answers] bschatzow:
If it is, I don't know how. I would need it to be able to load from Sideload.
[Google Pixel XL Questions & Answers] BDogg718:
Does phone boot at all? To OS?
[Google Pixel XL Questions & Answers] bschatzow:
Yes it does. Only thing not working is bootloader. Without out this I can't root.
[Google Pixel XL Questions & Answers] BDogg718:
Ok..if phone boots ur bootloader is still there. Phone wouldnt boot without it. You on stock rom? Hit me up on hangouts and I will try to help you if you want. For the sake of time. Im sure you wanna get this resolved ASAP.
[Google Pixel XL Questions & Answers] bschatzow:
Sent you a pm requesting contact info.
[Google Pixel XL Questions & Answers] bschatzow:
Moderator Close

Worked for a long time with BDogg718. He generously spent a great deal of his time with me and opened several Chats with Developers and No one had a solution. He is very knowledgeable and really did not want to give up. For now the solutions seems to be send it back to Google and get a replacement. It would be nice if someone could talk to Google, as a phone that has a recovery built in firmware should be able to restore itself. The dual slots seems to be a problem for them as well.
[Google Pixel XL Questions & Answers] mattkelly:
I think I had the same thing happen with me! I installed the update via TWRP. The update installation seemed to crash at the end, resulting in a reboot. The phone did install 7.1.2 successfully, but I lost root and the ability to successfully boot into any recovery. I tried flashing TWRP again, but it failed "FAILED (remote: partition recovery doesn't exist). It appeared to attempt to flash it into slot "_b", if that means anything.
[Google Pixel XL Questions & Answers] wyrdtrtle:
TWRP will not boot on 7.1.2. At least that's the conclusion formed last night in #twrp while the devs were working with someone else with this issue. I don't think they know why yet, but I doubt it will be overly long til they figure it out.
[Google Pixel XL Questions & Answers] mattkelly:
Glad to hear someone is on the case. I will be sure to send a few shekels their way for my clumsiness.
[Google Pixel XL Questions & Answers] mikaole:
Damn i was lucky than.

Flashed 7.1.2 factory and installed twrp after. Now I am on custom 7.1.2. Am a tester so flashed about 10 testbuilds the last days and twrp is still working fine here.
[Google Pixel XL Questions & Answers] mattkelly:
Did you flash the incremental update or the full ROM? Did you wipe beforehand?

Edit: whoops, didn't read your comment in full! Question - did you have TWRP installed previous to the factory build?
[Google Pixel XL Questions & Answers] mac796:
Your ok doing that. His issue was he flashed ota with TWRP.
[Google Pixel XL Questions & Answers] wyrdtrtle:
Ok, was beginning to see a pattern of OTA flashing thru TWRP. Good to know.
[Google Pixel XL Questions & Answers] avenator14:
I am also having this issue. Updated my Pixel to the latest April release with ADB sideload and now my bootloader will not load. It enter a ramdump mode when I try to boot to recovery with Volume Down + Power... Definitely has something to do with me flashing the OTA through TWRP sideload. Any way to fix this issue? ADB is also not working while booted.
[Google Pixel XL Questions & Answers] bschatzow:
More to my story. It appears what was broke was the recovery (for me) not the bootloader. If I boot to recovery (first screen on power down Vol)I can load anything via ADB or fastboot. I have tried several restores (system, format, complete) but nothing restores the recovery. My phone works fine and I was able to re-root. I think for me my slot A is corrupt, but still don't know how to fix it. Not sure why the reformat, and reinstall all on each slot did not fix the problem, but it did not.
[Google Pixel XL Questions & Answers] mattkelly:
How did you get root back?

At least the TWRP group is aware of this issue. I feel a little helpless without a working recovery, but at least my phone still works.
[Google Pixel XL Questions & Answers] 5.1:
Hello...

Try flashing factory image to both slots and start fresh... Reboot into bootloader and flash to the current slot, a or b. You can see which slot is active in bootloader under the RAM info:

Boot-slot= a or b

Once finished and it reboots into system, power down your device and boot into bootloader.

Change active slot. See Boot-slot= a or b

If the first flash was on slot "a" use:

fastboot --set-active=b

Or if the first flash was on slot "b" use:

fastboot --set-active=a

And flash the same stock firmware again...

Reboot. Done!

Hopefully this will clear all issues..!

Good luck... :)
[Google Pixel XL Questions & Answers] bschatzow:
Hello...

Try flashing factory image to both slots and start fresh... Reboot into bootloader and flash to the current slot, a or b. You can see which slot is active in bootloader under the RAM info:

Boot-slot= a or b

Once finished and it reboots into system, power down your device and boot into bootloader.

Change active slot. See Boot-slot= a or b

If the first flash was on slot "a" use:

fastboot --set-active=b

Or if the first flash was on slot "b" use:

fastboot --set-active=a

And flash the same stock firmware again...

Reboot. Done!

Hopefully this will clear all issues..!

Good luck... :)[/QUOTE]

My boot slot is b. This is the command and error

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --set-active=a

error: Could not get suffixes.

This is all the steps I have done since I had the problem after loading the OTA in TWRP. After the last step I can now load TWRP (temporary) and install SU,

1. Sideload of OTA of N2G47E

2. fastboot -w (will format userdata)

3. fastboot format system_a

4. fastboot format system_b

5. fastboot reboot bootloader

6. fastboot format vendor_a

7. fastboot format vendor_b

8. fastboot reboot bootloader

9. fastboot erase boot

10.fastboot reboot bootloader

11.Ran flash-all.bat on marlin-n2g47e lines below

[MENTION=8011874]Echo off[/MENTION]

:: Copyright 2012 The Android Open Source Project

::

:: Licensed under the Apache License, Version 2.0 (the "License");

:: you may not use this file except in compliance with the License.

:: You may obtain a copy of the License at

::

:: http://www.apache.org/licenses/LICENSE-2.0

::

:: Unless required by applicable law or agreed to in writing, software

:: distributed under the License is distributed on an "AS IS" BASIS,

:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

:: See the License for the specific language governing permissions and

:: limitations under the License.

PATH=%PATH%;"%SYSTEMROOT%\System32"

fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-marlin-8996-012901-1702171013.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot -w update image-marlin-n2g47e.zip

echo Press any key to exit...

pause >nul

exit
[Google Pixel XL Questions & Answers] 5.1:
Hello...

So you tried switching slot and had this error before you attempt flashing on your current slot right? When i advised flashing on your current slot first :)

Since it flashed without switching slot, it flashed n2g47e fine on slot b right?

And it rebooted in system properly? i assume yes. Then reboot now in bootloader and retry switching slot with:

fastboot --set-active=a

I think it should switch properly now (hopefully). And let the factory image do its job and reboot afterward.

Let me know how it goes! Good luck...
[Google Pixel XL Questions & Answers] bschatzow:
Did the flash all batch file on b. I rebooted than went to bootloader tried to switch slots here and got error. Again I have the latest on B and can't switch to A.
[Google Pixel XL Questions & Answers] 5.1:
Hey... Are you using latest platform-tools ADB/fastboot. If you're unsure, download them here and retry: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

If it fails yet, you could try to fastboot boot twrp.img

Once in TWRP, select reboot. At the bottom, you have an option to set slots. Try switching from here and select reboot bootloader...

What does the bootloader info says? Did it switch properly now to slot a?

Good luck...
[Google Pixel XL Questions & Answers] bschatzow:
The latest platform tools let me switch to A. When it rebooted Memory dump twice than back to B. I'm sure A is bad. Can I do the fastboot --set-active=a, then install the rom without rebooting?
[Google Pixel XL Questions & Answers] mac796:
If you think a is bad I would switch to a

Then reboot bootloader make sure it's in a

Then flash all. Should flash to your active slot
[Google Pixel XL Questions & Answers] 5.1:
Hey,

Yes you can... As long as the output from --set-active=a reports slot a is active, you can go ahead and use flash-all

But after reading others posts with similar issue, I'm not sure it will flash though... Crossing fingers for you..!

Hello,

It seems one of his slot has a problem. We already managed to flash on slot b. Just trying to "repair" slot a to avoid further issues... :)
[Google Pixel XL Questions & Answers] bschatzow:
is the report that a is active on the pc or on the phone?
[Google Pixel XL Questions & Answers] 5.1:
Hey...

When you issue the fastboot command and get the output from the command prompt saying a is active. :good:

Don't reboot in-between and flash-all directly.

Good luck...
[Google Pixel XL Questions & Answers] bschatzow:
Phone is working great off of b slot. When I flash all on a do I lose my data?
[Google Pixel XL Questions & Answers] 5.1:
It may wipe your data, unless you edit the flash-all.bat and remove the -w in the script.

Also it's up to you if you want to have a full working device or maybe face another issue in the future. I'm not saying you are not ok using your device as is, i honestly don't know how it will behave. Also, I'm not even sure it will flash properly on a as I previously said

I'm just trying to help you as if it was my phone, i would like to have both slot working. Because this is how it is supposed to be... :good:

If you decide to flash anyway and it doesn't work, I suggest you to RMA your device. In my opinion, if the slot remain corrupted, the device is not 100% reliable... And if you don't flash, you won't know...

Good luck... :)
[Google Pixel XL Questions & Answers] 5.1:
Hello... You can press edit in the OP and at the bottom, click "advanced"

I don't know if there is a tag you can select, otherwise just add this in front of your title:

[SOLVED] Bootloader - No Command Error

Cheers...
[Google Pixel XL Questions & Answers] avenator14:
If anyone is having this issue that I had, I was able to solve it. I did a factory reset and then I was able to boot into bootloader without the ramdump mode error. After that, I just reflashed stock images and restored my data and I was fine. Flashing an OTA through TWRP is a bad idea.
[Google Pixel XL Questions & Answers] bschatzow:
It seems a lot of people have had problems updating on a rooted pixel. I had problems caused by updating the ota in twrp. Others sideloading. Does anyone have a clear procedure for installing the OTA on a rooted phone?
[Google Pixel XL Questions & Answers] 5.1:
Hello...

You may wait for someone else to confirm​ as I'm not really used to this, but I think flashing stock boot.img from the same factory image you used to flash on both slots (both, just to be sure) and since SuperSU is systemless, also considering you didn't make "any" change to system partition, it might be enough to take an OTA either pushed by Google or with ADB sideload.

You'll have to boot TWRP.img again, install TWRP zip and maybe SuperSU (not sure).

Again, wait for someone to confirm, read through the forum as this question might have already been answered 100 times or open another thread.

Good luck...
[Google Pixel XL Questions & Answers] bschatzow:
That is the problem. I have read many answers in different discussions and two that many have suggested caused problems. Installing from twrp caused my problem and installing via side load has caused others. I believe but have not confirmed that you need to install the OTA via fastboot, then install the image file for twrp via fastboot, then the zip of twrp via twrp and lastly su via twrp.