Develop Bugs

Play Store - full howto

Here is an instruction how to install Play Store (and Play Services) on Chinese version of Nokia N1
DISCLAIMER: you're doing it on your own risk, it can probably even eat your kitten
Credits should go to rumambo who has described everything in this thread.
Original credits from rumambo:
Thanks a lot sadfrog_lin for right link
Great Thanks social-design-concepts for Tools and working solution !!!
This was successfully done by me on A5CN507 build. IMO it should work the same good on other versions of Lollipop, but I cannot promise anything.
Prerequisites
I assume that you have Intel Drivers up and running http://opensource.dell.com/releases...ition/FlashTool/IntelAndroidDrvSetup1.5.0.exe
I assume that you have adb/fastboot up and running http://forum.xda-developers.com/showthread.php?t=2317790
I assume that you have usb debugging enabled
I assume that yu have a basic knowledge how to use these tools
Installing GApps
Download GApps from this thread. I have used Nano version for Android 5.x, direct link here.
Copy it to your sdcard (any method is fine, but adb will do: adb push <filename> /sdcard/).
Download and extract IntelAndroid-FBRL-05-16-2015.7z.
Connect N1 via USB and run launcher.bat
Type ACCEPT (all capital) and select T4 method.
N1 should reboot and do a lot of things, then you should end up in temporary CWM Recovery session.
Choose install zip (volume up/down + power to select) and find and select the previously uploaded file.
After it finish reboot the tablet
Final fixes
After reboot you should have initial selection of Google Apps (including Play Store) installed. However Play Music will crash on start and GMail won't work (Play Services crashes). The reason for that is that GApps package is probably not fully prepared for x86 - but now you can simply fix it.
Go to ApkMirror and install Google Play services with -470 suffix, it is Lollipop x86 version (on the time of writing this the newest version was here ). Now both Play Music and GMail should work correctly.
An another issue is that Play Store reporting some apps (like Chrome, Google Maps, Google Earth, Chromecast, etc) as incompatible with the device. It probably could be fixed by hacking build.prop, however I haven't had time for it yet. The easiest method is to download them from ApkMirror and side install. Drawback is that you won't get autoupdates for them.
Enjoy!

reserved
reserved for a future use

For information the next update fails with this log...
I:verify_file returned 0
Installing update...
Verifying current system...failed to stat "/system/app/QuickSearchBox/QuickSearchBox.apk": No such file or directory
file "/system/app/QuickSearchBox/QuickSearchBox.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
"/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
E:Error in /cache/A5CN51C_update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse

This really works! Thanks a lot.
After the installation, a few days later I found out that there was an update for N1. I could not make the update successfully. Probably the GAPP issue. So in the end, we still need the Taiwan ROM so far. So that the system update can also be made.

I installed GAPPS, but disabled root(in SuperSU's settings). I can run the OTA update (A5CN51C) successfully.
After the update, "google service is stopped" appears again. I think re-flush GAPPS and SuperSU is needed.

bricked
Hi Guys,
after the issue with the update I started replacing new files with the originals from the previous update. I've checked md5 of every file I used and compared it with update script from the new update - so I'm sure every file was correct. Actually everything was working fine with these original files.
However after the update I got a boot-loop. If I remember correctly it was something abt OpenGL in logcat. I was not able to run recovery by pressing volume up and power, but since adb was working I did it via adb. I came with an idea to clear user data. That was mistake!
Now I still have the boot-loop but developer mode was disabled by cleaning the data. My plan is to reflash with A5CN507 which contains a full system partition image. To do so I need to boot into recovery or download mode.
Do you guys have any ideas how to boot into recovery or download mode if volume up (and down) doesn't work?
Thanks in advance.

Can confirm the boot loop. I was able to get into the CMW session again and tried to restore the backup I made before installing the gapps but CMW got stuck while restoring the system partition.
The device is now stuck in the "Powerd by Android" screen, any help is warmly welcome

Can't root by the method after update to latest 5.1.1 firmware. Pls update the method

After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?

Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
Your tablet bootloader is locked by the update. I've not found any ways to unlock it and install google play.

same here 5.1.1 messed everything up
Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
same here - so I thought I redo the whole thing with Gapps for 5.1.1, but now Fastboot Tethered Recovery Launcher doesn't recongnize my N1 anymore. Can anybody help? Thanks in advance

Any chance that the following common command work ?
Code:
fastboot oem unlock

jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
It's used to make your device unlocked, but only limited to some devices.
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225

jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you,
I tried that, it didn't work - it says "waiting for device", but it waits forever. As to the Fastboot Tethered recovery launcher, this time I used the one from Jul, 27, before I had an earlier version. Could it be that the older version would work, but not the latest one? It does recognize my device, but it says unauthorized, although it OEM-unlocked and USB debugging is authorized. Thanks for any help.

and that's the end of it, good night N1
Since my N1 is still bricked, hung halfway through bootloading, I talked to an Android-Repair-shop. They said it cannot be unbricked, I would need a new motherboard... but motherboards for the N1 are not available.
Does anyone hv better news?

Hi,
so I came back to the problem today - and I managed to unbrick my device. Somehow (vol-up + power) I managed to enter fastboot. Then I rebooted into recovery and sideloaded a full update.zip with 701.
Now I'm trying to change Chinese version to Taiwanese one.

my nokia n1 stuck
my Nokia n1 stuck at boot screen i lost my recovery too my tablet only open at fastboot mode.Pls HELP
i need boot.img and recovery.img for NOKIA N1(A5CNS1C)

Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19

sasha2910 said:
Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19
Click to expand...
Click to collapse
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...

LineArc said:
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...
Click to expand...
Click to collapse
Can't wait for that! :good::good::good::good::good::good:

October Security OTA won't install on rooted Nexus 5x with stock Android 7.0

Hello. When I bought my Nexus 5X, it had Android Marshmallow on it. I immediately rooted it and flashed TWRP using the Nexus Root Toolkit (NRT) and it went well.
Along came the Android 7.0 OTA and I only had to remove the saved fingerprints and PIN (to make TWRP see the phone as decrypted) I was able to go through the update successfully with that current setup. Of course I had to re-root my phone after that.
But the 46.7MB October Security Update won't install via OTA. I've tried:
re-rooting it with the latest TWRP (via NRT)
re-flashing the stock recovery (via NRT)
but the OTA still wouldn't get installed. I checked the recovery log and it showed this line:
Code:
installing lge.bullhead updater extensions
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
script aborted: E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
E:unknown command [log]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '@/cache/recovery/block.map'
Done processing script file
But I checked the build.prop file and found this:
Code:
ro.build.desciption
google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Where could that google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys have come from? How do I proceed with the OTA? I've yet to try FlashFire because it won't detect the downloaded OTA file and I've yet to download that 1.2GB factory OTA file.
Also why only now am I having problems with OTA? It should have happened during the Android 7.0 update, right? I would like it very much if I could do this without wiping my data. Please help. Thank you.

d4ryl3 said:
Hello. When I bought my Nexus 5X, it had Android Marshmallow on it. I immediately rooted it and flashed TWRP using the Nexus Root Toolkit (NRT) and it went well.
Along came the Android 7.0 OTA and I only had to remove the saved fingerprints and PIN (to make TWRP see the phone as decrypted) I was able to go through the update successfully with that current setup. Of course I had to re-root my phone after that.
But the 46.7MB October Security Update won't install via OTA. I've tried:
re-rooting it with the latest TWRP (via NRT)
re-flashing the stock recovery (via NRT)
but the OTA still wouldn't get installed. I checked the recovery log and it showed this line:
Code:
installing lge.bullhead updater extensions
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
script aborted: E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
E:unknown command [log]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '@/cache/recovery/block.map'
Done processing script file
But I checked the build.prop file and found this:
Code:
ro.build.desciption
google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Where could that google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys have come from? How do I proceed with the OTA? I've yet to try FlashFire because it won't detect the downloaded OTA file and I've yet to download that 1.2GB factory OTA file.
Also why only now am I having problems with OTA? It should have happened during the Android 7.0 update, right? I would like it very much if I could do this without wiping my data. Please help. Thank you.
Click to expand...
Click to collapse
The update will fail because you have modified /system. Update using NRT then apply root. I don't use that tool so that's up to you to figure out.
Alternatively, update using fastboot and reflash root afterwards. Follow the guide below:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk

d4ryl3 said:
Along came the Android 7.0 OTA and I only had to remove the saved fingerprints and PIN (to make TWRP see the phone as decrypted)
Click to expand...
Click to collapse
BTW you didn't "decrypt" the phone. It was still encrypted. You just changed the password used to encrypt the storage of the unique encryption "keys", that were used to encrypt your phone, to "default_password", which TWRP knows about and can try automatically to retrieve your encryption keys.

SlimSnoopOS said:
The update will fail because you have modified /system. Update using NRT then apply root. I don't use that tool so that's up to you to figure out.
Alternatively, update using fastboot and reflash root afterwards. Follow the guide below:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I went away and
Downloaded the OTA zip file
Installed the Android SDK tools, connected my device and rebooted it into TWRP
Then went to Advanced -> ADB Sideload
Then from the command prompt, typed "adb sideload /path/to/OTA/zip/file" and hit enter
It took a few minutes to 100%, then I rebooted my phone and all is well and updated now.
Thank you so much for redirecting me to the proper solution.

sfhub said:
BTW you didn't "decrypt" the phone. It was still encrypted. You just changed the password used to encrypt the storage of the unique encryption "keys", that were used to encrypt your phone, to "default_password", which TWRP knows about and can try automatically to retrieve your encryption keys.
Click to expand...
Click to collapse
Oh, all right. Thanks for the clarification and duly noted. :good:

d4ryl3 said:
I went away and
[*]Downloaded the OTA zip file
Click to expand...
Click to collapse
Can you share the link for NRD90R>NBD90W, I'm still stuck on NRD90R and don't want to flash the full OTA (I don't want to flash full image every month and run down the flash rewrites).

MarvinOl said:
Can you share the link for NRD90R>NBD90W, I'm still stuck on NRD90R and don't want to flash the full OTA (I don't want to flash full image every month and run down the flash rewrites).
Click to expand...
Click to collapse
Sorry for not being clear, but I used thr whole 1.2GB OTA zip file for this.
Was also wondering if there's a simpler way of doing this considering the October update was just ~46MB.

NOUGAT 7.0 for G928A ADB update step by step...Enjoy !!!

As i promise to one of member here then i will post it and i have it.
I can't help you with any of problems related do to i don't have S6E+ .
For all with March 4CQB2 baseband update for Nougat. SS-G928AUCS4CQB2-to-U4EQC6-UP - link is UP
MD5 :7a55165ce2b9d3ffe6170491813c44ac
Nougat update if you are on 4CQA1 baseband SS-G928AUCS4CQA1-to-U4EQC6-UP.zip - link is up
MD5 checksum : c74d9106d59dcb0411f9a1e4e23ca797
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
0. Make sure you are on G928AUCS4CQA1 or March update G928AUCS4CQB2 Baseband. Check this 3 times
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-G928AUCS4CQA1-to-U4EQC6-UP.zip or after March 20 update SS-G928AUCS4CQB2-to-U4EQC6-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update SS-G928AUCS4CQA1-to-U4EQC6-UP.zip or after March 20 update SS-G928AUCS4CQB2-to-U4EQC6-UP.zip
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-G928AUCS4CQA1-to-U4EQC6-UP.zip or after March 20 update SS-G928AUCS4CQB2-to-U4EQC6-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks

Thanks again. Will try it as soon as available.
Please be reminded to upload the qa1 update. I don't think it's available anywhere

vista1984 said:
Thanks again. Will try it as soon as available.
Please be reminded to upload the qa1 update. I don't think it's available anywhere
Click to expand...
Click to collapse
nougat is uploaded i just downloading to check if file is OK after upload.

vista1984 said:
Thanks again. Will try it as soon as available.
Please be reminded to upload the qa1 update. I don't think it's available anywhere
Click to expand...
Click to collapse
Link is UP.. Enjoy !!

norbarb said:
Link is UP.. Enjoy !!
Click to expand...
Click to collapse
Downloading...
could you upload the adb sideload from PJ1 to QA1 please.

vista1984 said:
Downloading...
could you upload the adb sideload from PJ1 to QA1 please.
Click to expand...
Click to collapse
10 min away

updating. will report back later. it's getting late here. so i will probably report back early tomorrow.
Thank you again norbarb for all the hard works to our devices.

norbarb said:
As i promise to one of member here then i will post it and i have it.
I can't help you with any of problems related do to i don't have S6E+ .
Nougat Update Here - link is up
MD5 checksum : 9970ef8f7ba21ea499cd977775f68d88
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-G928AUCS4CQB2-to-U4EQC5-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-G928AUCS4CQA1-to-U4EQC5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-G928AUCS4CQA1-to-U4EQC5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
After 3 updates, I am confirming that the updates work like a charm. 7.0 has lots of new tweaks after first 15 mins use. And stable so far.
Thanks again!!

thanks for share

I am having lots of issue installing this update.
first status 7 error.
Sorted with editing binary file and than signature not verified error and failed on 50% tried again failed on 92% .
Any help?

fysaldar said:
I am having lots of issue installing this update.
first status 7 error.
Sorted with editing binary file and than signature not verified error and failed on 50% tried again failed on 92% .
Any help?
Click to expand...
Click to collapse
Odin back to older avalable version and update gradually. Looks like your recovery is corrupted
Clicking from Edge of Galaxy

norbarb said:
Odin back to older avalable version and update gradually. Looks like your recovery is corrupted
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
Just realised that update is AUCS4CQA1-to-U4EQC. And my build is UCU2BPE6 have you got firmware for this build by chance?

Here is donwload links to all the Odin file. Credit to the member who uploaded it. Which should bring you to pj1 directly
https://forum.xda-developers.com/at...neral/g928a-odin-restore-files-t3214359/page9

fysaldar said:
Just realised that update is AUCS4CQA1-to-U4EQC. And my build is UCU2BPE6 have you got firmware for this build by chance?
Click to expand...
Click to collapse
I can look for it tomorrow. I'm not familiar with S6E+ at all, i just find update because one of the member ask me if i can. I have no idea what is ladest available firmware for your devices. But like i said i can look for it.
Clicking from Edge of Galaxy

Seems edge+ (and probably note 5) got huge upgrade in Android 7 update. Including performance mode which is not available to gs6.
So far I noticed and worth to mention.
Camera UI renewal
Performance mode
New function from nougat, notification panel and night mode
All the Samsung app seems all redesigned
Display render resolution can be changed between 720p, fhd and wqhd
Battery is better especially for standby time
Great job from Samsung this time

norbarb said:
As i promise to one of member here then i will post it and i have it.
I can't help you with any of problems related do to i don't have S6E+ .
Nougat Update Here - link is up
MD5 checksum : 9970ef8f7ba21ea499cd977775f68d88
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-G928AUCS4CQB2-to-U4EQC5-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-G928AUCS4CQA1-to-U4EQC5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-G928AUCS4CQA1-to-U4EQC5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
first of all thanks alot.
so my current version is G928AUCS3CPJ1.
will there be any issue if i tried to sideload from this version or should i do the other updates?
if i need to do the other updates,by any chance do you have odin files for this G928AUCS4CQA1 version?
i was on bpe6 and odin to cpj1

rahulje9 said:
first of all thanks alot.
so my current version is G928AUCS3CPJ1.
will there be any issue if i tried to sideload from this version or should i do the other updates?
if i need to do the other updates,by any chance do you have odin files for this G928AUCS4CQA1 version?
i was on bpe6 and odin to cpj1
Click to expand...
Click to collapse
They are here : https://forum.xda-developers.com/att-galaxy-s6-edge-plus/general/g928a-adb-updates-t3575021

norbarb said:
They are here : https://forum.xda-developers.com/att-galaxy-s6-edge-plus/general/g928a-adb-updates-t3575021
Click to expand...
Click to collapse
thanks alot.
all should be sideloaded right?

rahulje9 said:
thanks alot.
all should be sideloaded right?
Click to expand...
Click to collapse
Yes

Hi can please find update to nougat from UCU3CPHA?
Edit: nvm thanks so much norbarb on 7.0 now. 1 odin and 4 sideloads lol
Sent from my SAMSUNG-SM-G928A using Tapatalk

How To Guide Installing OneUI 4 Beta / Android 12 on US Galaxy Z Fold 3 F926U/1

Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"

Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?

shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again

Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.

Haven't logged in to XDA in years. Just wanted to say THANK YOU.

mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.

Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!

AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.

Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.

Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload

erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?

I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop

zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1

Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.

ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com

Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...

I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?

I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?

Development [ROM][13][UNOFFICIAL][alioth] PixelExperience for Redmi K40/Poco F3/Mi 11X [AOSP]

Hello,
After a lot of work done by lzgmc, jayanthk and after some tests, I have built an unofficial continuation of PE for alioth.
Motivation:
- I have the device and wanted to have last security patches
- I want to have Netflix, Google Wallet, McDonald app working
- because of lzgmc's and JayanthKandula's hard work, needed changes were reduced to minimum
Changes:
- Updated binaries from the most recent global alioth image
- All updates from PixelExperience, including security updates
- Share the same kernel as munch
Changelog:
05.2023
- small kernel updates
- small performance and ui tweaks
04.2023
- use updated drivers from the most recent version of MIUI Global 14.0.4.0
- use current 4.19 kernel instead of old one
- performance and ui tweaks
Images:
PE - Alioth - Google Drive
drive.google.com
Sources:
https://gitlab.com/lukasz1992-pe/
Instruction:
- you have to flash 05.2023 full image first, if you were on different image
For every next incremental update:
- allow system to boot after flashing
- then reboot to recovery
- flash incremental update
FAQ:
Q: Do you have the device?
A: Yes, I use my ROM on my device
Q: How to report bugs?
A: Write about them here
Q: I do not trust your builds
A: No problem, build image yourself from source or just do not use this rom
Q: What about official support?
A: My ROM is not official (depsite OFFICIAL in name of images). There is already an official maintaner, but has not released images yet.
Q: Why automatic updates are not working?
A: Because alioth is not officially supported, I support it unoficially. Maybe I add updates to my repo.
Q: Why do you publish incremental updates
A: They take less space on my Google Drive and are easier to flash
Q: I want to install 05.2023 (and newer) images directly
A: Flash 04.2023 version first, then install incremental updates one by one (as described in description above)
Q: Incremental update does not work
A: Make sure you are on the correct image, follow the order and allow to boot system after each flash (do not try to flash >1 image without reboot)
Q: Is this a vendor-boot ROM?
A: No
Q: Is there any guarantee?
A: xD

You accidentally used the Question-tag for this thread

Hi, I'm on the 20230420-1753 build but when I try to adb sideload the from-20230420-1753-to-20230516-2127 update I'm getting this error, I'm using the provided recovery image:
Code:
Supported API: 3
Finding update package...
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1.
Installation aborted.
I also tried with OrangeFox Recovery, I didn't get this error there but upon reboot I noticed that my version number didn't change.
Also, thanks a lot for keeping PE on the Poco F3 alive, I briefly tried MIU14 but I found it too bloated for my taste.

Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?

lukasz_m said:
Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?
Click to expand...
Click to collapse
Sure, here they are: https://pastebin.com/M5kvav40 https://pastebin.com/VRkbgbvh
I also don't have magisk or anything like that installed.

[DELETED]

Okay, released a new, fixed update - I tested it, it should work

I flashed the new update and its been working fine, thanks for you work!

I flashed the full image on GDrive linked above - thanks very much, works really well. But I think I'm being a blind and can't see the May update? Where do I find that...

Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.

lukasz_m said:
Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.
Click to expand...
Click to collapse
Ah great, thought I was asking a stupid question
Thanks for all your work - had semi-retired my F3 and just bumped it from 12 to 13, its really fast and smooth.

Update - 2023.05 image was reuploaded

Sorry if this is a noob question. Is it possible to dirty flash to this 2023.05 from the latest official build?
And thx for keeping this device updated, really appreciate what you're doing here.

hi, yes - you can do it

Hey Lukasz,
thanks for this work you are doing for all of us.
I I'm on last OFFICIAL PE build from lzgmc and I'm tying to dirty flash with ADB your ROM.
I receive this error whenever I run the ADB sideload comand but Maybe I did something wrong...can you help me ?
Thanks in advance
My version is:
PixelExperience_alioth-13.0-20230119-0644-OFFICIAL
Enabled ADB.
Now send the package you want to apply to the device with "adb sideload <filename Supported API: 3
Finding update package...
Installing update... Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1. Installation aborted.
@lukasz_m

It happens when update was interrupted. I do not remember exact names, but please do from ADB:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
reboot to recovery and try again

lukasz_m said:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
Click to expand...
Click to collapse
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.

ciottaciotta said:
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.
Click to expand...
Click to collapse
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above

blonderulez said:
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above
Click to expand...
Click to collapse
OK thnaks for the explanation...
After giving "mount /dev/block/by-name/metadata /metadata" command i get:
"mount: bad /etc/fstab: No such file or directory"
When I try to browse it with "cd" and "ls" commands i can browse till /dev/block/by-name/ and I see metadata folder with "ls" than when i go for "cd metadata" i get this "/dev/block/by-name/metadata: Not a directory"

Does this work?
Code:
mkdir /tmp/metadata
mount /dev/block/by-name/metadata /tmp/metadata
rm -rf /tmp/metadata/ota*