Related
Bought a new in box N6 that comes with Android 6.0.1. Checking system update via WiFi can't find any updates to 7.1.1. Are system updates tied to having carrier service? I'd like to just use this device as an e-reader and for media consumption. Is there a way to force this update without root? Thanks!
I'm not really sure don't have a Nexus 6 yet although im sure it'd be possible thru recovery possibly
Sent from my LG-M153 using Tapatalk
New in box Nexus 6 devices come with Android 5.0 standard, thus yours isn't new if it comes with Android 6.0.1. Updates are not tied to having carrier service, but if you want stock Android 7.1.1 on the device you'll have to flash a ROM using ADB (Android Debug Bridge). OTA (Over The Air) updates for the Nexus 6 do not go past Android 7.0.0, even though Android 7.1.1 ROMs are available for download from Google. For more information on how to manually update the N6, please check out the sticky posts in the General forum.
P.S. None of this requires root.
Strephon Alkhalikoi said:
New in box Nexus 6 devices come with Android 5.0 standard, thus yours isn't new if it comes with Android 6.0.1. Updates are not tied to having carrier service, but if you want stock Android 7.1.1 on the device you'll have to flash a ROM using ADB (Android Debug Bridge). OTA (Over The Air) updates for the Nexus 6 do not go past Android 7.0.0, even though Android 7.1.1 ROMs are available for download from Google. For more information on how to manually update the N6, please check out the sticky posts in the General forum.
P.S. None of this requires root.
Click to expand...
Click to collapse
Hmm, well mine was sealed when I got it, so how can that be? I would manually update, as I'm not new to rooting (have had rooted Galaxy S3, Sony Xperia Z3C, etc), but unfortunately, I'm one of those unlucky ones that have that dreaded "Unknown USB Device (Device Descriptor Request Failed) when connecting to Windows 10. I see that plenty of other Nexus owners have had this issue as well. I can't for the life of me solve this, and I've tried every suggestion I've googled. Any idea how else I can update without using a computer, or maybe you know a workaround to this Windows 10 BS?
"New" Nexus 6: Was your box shrinkwrapped? If so, it's a rewrap as Nexus 6 boxes do not come shrinkwrapped. On a new Nexus 6 you have a label that must be cut to get into the box. In this case, the version of Android on your device is a dead giveaway that it isn't new. I purchased mine brand new from Amazon 19 months ago, when Android 6.x was readily available for the device, and out of the box it came with Android 5.0.
Unknown USB issue: https://forum.xda-developers.com/android/general/fix-unknown-usb-device-device-t3375320
I can't guarantee the above will be of much help as I don't have this issue on any of my Windows 10 devices.
Do you have a phone with the same size SIM chip? Have you tried just putting it into the Nexus 6 to see if it will update that way?
Strephon Alkhalikoi said:
"New" Nexus 6: Was your box shrinkwrapped? If so, it's a rewrap as Nexus 6 boxes do not come shrinkwrapped. On a new Nexus 6 you have a label that must be cut to get into the box. In this case, the version of Android on your device is a dead giveaway that it isn't new. I purchased mine brand new from Amazon 19 months ago, when Android 6.x was readily available for the device, and out of the box it came with Android 5.0.
Unknown USB issue: https://forum.xda-developers.com/android/general/fix-unknown-usb-device-device-t3375320
I can't guarantee the above will be of much help as I don't have this issue on any of my Windows 10 devices.
Click to expand...
Click to collapse
Not shrinkwrapped. Just the sticker cover on the box sealing it. Anyway, I saw that link, but not sure what key would be appropriate for the Nexus 6, as the key the poster wrote on that might be for the HTC? I think i would need to change that to the device ID for this, but since my computer won't even recognize the N6, no details appear for me. WOuld you happen to know it? Thanks
Paul1201 said:
Do you have a phone with the same size SIM chip? Have you tried just putting it into the Nexus 6 to see if it will update that way?
Click to expand...
Click to collapse
I have one in my iPhone. Not sure if it's the same size, but will try that. I was hoping I wouldn't have to ever put a SIM in this, but I'm at last resort now.
@radiohead14 - There were a lot of problems with the early MM releases and windows drivers.
Can you try booting to a Linux flash drive? Then you could use ADB to sideload 5.1.1. Then go back to windows and I'll bet it finds the phone correctly. You should be good to go upgrading again after doing that. Once windows finds the phone, you should be ok in the future.
ktmom said:
@radiohead14 - There were a lot of problems with the early MM releases and windows drivers.
Can you try booting to a Linux flash drive? Then you could use ADB to sideload 5.1.1. Then go back to windows and I'll bet it finds the phone correctly. You should be good to go upgrading again after doing that. Once windows finds the phone, you should be ok in the future.
Click to expand...
Click to collapse
I was able to upgrade to 7.0 after putting my SIM in (so I guess updates are tied to having carrier service), but in-between the updates from 6.0.1, i kept testing the USB connection. unfortunately it still won't get recognized, so at this point, I don't think it's the Android version. I'm just gonna return it.
radiohead14 said:
I was able to upgrade to 7.0 after putting my SIM in (so I guess updates are tied to having carrier service), but in-between the updates from 6.0.1, i kept testing the USB connection. unfortunately it still won't get recognized, so at this point, I don't think it's the Android version. I'm just gonna return it.
Click to expand...
Click to collapse
I certainly understand not wanting to deal with it. Particularly if your not comfortable with Linux. The thing is, the advice to roll back to 5.1.1 was specific as the last release that had a high probability of working with win10. If you are somewhat comfortable with Linux, it's easier to get it connected and will help prove whether it's the device or win10.
ktmom said:
I certainly understand not wanting to deal with it. Particularly if your not comfortable with Linux. The thing is, the advice to roll back to 5.1.1 was specific as the last release that had a high probability of working with win10. If you are somewhat comfortable with Linux, it's easier to get it connected and will help prove whether it's the device or win10.
Click to expand...
Click to collapse
Ok, I'll give it a shot. Do you have a link where I could follow instructions to how? Thanks!
radiohead14 said:
Ok, I'll give it a shot. Do you have a link where I could follow instructions to how? Thanks!
Click to expand...
Click to collapse
How to create a bootable Linux Mint USB drive using Windows Accurate, though the current release of mint is 18. You could use Ubuntu (Mint is a derivation of Ubuntu) but I link to mint because most users find it easier.
For Nexus 4 but still accurate for N6. Not mentioned is;
in some cases it's also needed to restart adb with:
adb kill-server
adb start-server
Or completely reboot the system
I assume you know this, but as a reminder, If you have just enabled the ADB debug option on your phone and created a new connection, the ADB command might list your device as unauthorized. Just check the screen of your phone then to authorize the new connection.
In case you hadn't seen this thread: nexus 6 one beginners guide.
I would be happy to help you through this. The only thing is I'm traveling the next 2 days so it will be intermittent and late before I can get on a computer
P.S.
the "sudo" command referenced is to gain elevated privileges. you shouldn't be prompted to enter a password when using a bootable flash drive.
the "whoami" command will tell you who you are logged in as.
Hi all.
I have an unbranded multimedia device installed in my car.
I know its cheep and old (OS is 4.1.1)
the only thing that can help identify is that on startup it says 'powered by Uzeb'
my problem is that the device is locked and no apps are allowed to be installed
I would like to root it so ill be able to install a newer version and if not than some apps.
problem is I can not find the option to Factory reset.
I am pretty sure that this option is gone or at list hidden from end users.
the company that installed it at first place demands an extra payment to unlock it back.
so Im trying to do it on my own.
For some reason I can't attach a photo
in About option,
there is a Uboot version - v00.01.13
Appreciate any sugestions.
no apps are allowed to be installed
Click to expand...
Click to collapse
Android Auto doesn't work that way - apps get installed on your phone, not on the head unit.
so what am I missing here ?
Its a touch screen mounted inside my car.
it runs on old version android and blocked to end users
who wants to update the OS by themselves or to install different apps (or even update the existing ones)
So this is not Android auto and perhaps im not at the right forum
any suggestions on what else can I do ?
Damn, it's been a while since I was here. Back then it was mostly about Windows PDAs.
Disclaimer:
Your warranty after this process is void and your phone will tell you it can not be trusted because it's unlocked.
This is what worked for me. I did it on Windows 10. I just went through the process and it was a bit of mixing and matching various guides.
I'm not your tech support, the only one responsible for following this is you.
If any part of this guide doesn't work for you: too bad. Maybe Google or other users can help you with your problem.
Needed:
An internet-enabled PC
Huawei P10 Lite phone
USB to Micro-USB cable
HiSuite https://consumer.huawei.com/en/support/hisuite/
DC-Unlocker (comes with abd & fastboot) https://www.dc-unlocker.com/
Optional: Huawei Driver Tools https://mega.nz/file/qrpBUIKA#zaI8Th0ovgyK48VzFUFAzMNWF2r_R12lNc-uJZsIx4w
Note: I recommend not to buy credits until you've come to the part in my guide which says buy credits.
Install HiSuite
Unzip and install HiSuite on your PC
Start it at the end of the installation (it should show a button with "Start")
Connect the phone to your computer with the USB cable and follow the instructions in HiSuite to install HiSuite on your phone
At the bottom of the (Windows) HiSuite there's an option to do a System Upgrade, mine had the option to install an older version (Android 7 with EMUI 5.1) Install this. (This will take some time)
Note: I've read that some people couldn't downgrade because of modern security fixes. It's possible I didn't run the latest updates, but as far as I'm aware everything was up to date.
The following part might be annoying because HiSuite tries to connect to the phone. I uninstalled it at this point, but I had the Driver Tools installed (and did the Install within said tools).
Phone
Once the phone restarted, go through the set-up as quickly as possible (skip WiFi-setup, decline all optional things and skip account creation)
Go to Settings > System > About Phone > Keep tapping the "Build Number" until you're told you're a developer
Find the developer options (Usually in Settings > System and enable USB/ADB debugging
Open the telephone app and type: *#*#2846579#*#* (it should open a menu automatically after the last *)
Click Background Settings > USB Port Settings and select Manufacture Mode
Once Manufacture Mode is selected, leave the phone untouched
DC-Unlocker, part 1
Unzip the contents of the DC-unlocker zip
Start dc-unlocker2client.exe
In the top left, under "Select manufacturer" change "Huawei modems" to "Huawei phones"
Click the button with the magnifying glass, if you did the previous step hovering should say "Detect phone" on hover
Example out put (this might differ for you, but triple-check a port is detected):
Code:
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM3
Model : Huawei HiSilicon Kirin Android phone
Serial NR. : [redacted]
Firmware : System 5.1.0.78(0VVV)
DC-Unlocker, part 2
Check again if a model and port is shown in both the output and above the big buttons.
In the top right, click About > Buy Credits
DC-Unlocker site
Select your payment processor
By default it creates a new account, unless you've used this service before, you probably want to keep it this way.
Fill in a username and an email address
You need 4 credits (€4 for me) at the time of writing this, but do check the link "How much do I need?"
Hit confirm and go through the payment process, wait until everything is processed (if you use a script blocker, you might want to temporarily disable it).
At the end you should get confirmation page with your username, a password and 4 credits. (Username and password will be mailed too.)
DC-Unlocker, part 3
Go back to DC-Unlocker
In the top right, click "Server" and enter the details you've gotten
Click "Check login" and see if the output window shows your username and the credits you have left (which should be 4 at the time of writing)
In the top right, click "Unlocking" and then click "Read bootloader code"
The output should show you the bootloader code once it's done. Copy this to a textfile and save it (and keep it in the memory).
You can close DC unlocker once you've saved the code.
Don't be lazy and try to copy/paste the commands following in the next section, since you want to keep the code in your memory, as seen in step 6. Besides, I'll show you some shortcuts anyway! Keep in mind that our example code is 1111222233334444 (yours most likely isn't, mine sure wasn't) and that [tab] will mean the tab-key on your keyboard.
PowerShell/Command Prompt
In the folder where you unzipped dc-unlocker2client.exe to, press [shift] on your keyboard and hold it while right-clicking in an empty area underneath the files, then click "Open PowerShell (or command prompt) here".
Whatever command-line you started will open, type ad[tab] and adb.exe should be appear (shows up as .\adb.exe in PowerShell)
Follow this by typing reboot bootloader. So it should show as
Code:
./adb.exe reboot bootloader
(no ./ in command prompt)
Hit [enter] and the phone should reboot to a screen with a white background
Once the bootloader screen shows (white background with the android mascot) type fast[tab] in PowerShell/Command prompt and follow it up by oem unlock[space]
If you still have the bootloader code in memory, right-click in PowerShell/Command prompt to paste it. Your entire line should be
Code:
./fastboot.exe oem unlock 1111222233334444
Hit [enter], the unlocking will start and factory reset your phone. My output was:
Code:
(bootloader) The device will reboot and do factory reset...
OKAY [ 10.330s]
If everything went right you'll see the Huawei/Android bootscreen and then a warning that the phone is "unlocked and can not be trusted" to use or something like that. It'll boot into the OS after that.
I'd like to remind you of the disclaimers at the top, but hopefully this will help some of you going through the process.
Edits
Forgot about USB debugging
Added the warning you get after a successful unlock
Changed the build number tapping sentence
Rewrote a sentence for clarity
Very nice guide, if ppl ask about unlocking we just link this from now on...
This is a very helpful guide, thank you so much! My question is, if I wanted to flash twrp when the bootloader is unlocked, is there a way to upgrade it to Oreo once again without locking the bootloader again? I can't seem to find a twrp tutorial where they use Nougat/Emui 5 to flash twrp, and all the tutorials to upgrade to Oreo/Emui 8 look like they're locking the bootloader once again and I don't really want to waste 4 euros to go back to the start.
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
Thank you for your quick reply! So after the bootloader unlock, did you flash twrp on Android 7? or did you upgrade your phone to Android 8 and flash twrp then? How did you manage to upgrade it to Android 8?
I really appreciate your help with the previous tutorial, I've done everything until the buy credits part (I'm waiting a bit for that part) and I'm planning on getting to the end of the tutorial at least before August. My idea is to upgrade to Android 8 + flash twrp and Magisk, hopefully I'll be able to do all of that!
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Oh, I understand now! One more question (sorry if I'm being annoying, it's my first time playing with a Huawei, I must say that Samsungs are far easier to root/unlock lol): If I follow your method, but after getting the bootloader unlock code and right before unlocking the bootloader, I use HiSuite to upgrade back to Android 8/Emui 8, would the procedure be fine? like, it's totally fine to unlock the bootloader either with android 7 or 8, the only time I need android 7 is to get my code because DC unlocker supports them better, right?
Again, thank you so much!!!
I'm not sure to be honest. But I reverted to 7/EMUI 5 because I read around here on the board that's better for trying to unlock.
Thank you,
Only fastboot.exe oem unlock xxxxx failed with the following error: FAILED (remote: Command not allowed)
finished. total time: 0.022s
This was resolved by going back to settings, developer options and check 'enable oem unlocking'. I didn't read that in your guide.
Syrion said:
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Click to expand...
Click to collapse
Hi, I have the same model. But I can't figure out how to update to EMUI8 again (or which custom recovery works). It doesn't find the update in HiSuite and it doesn't find it via System update. Do you happen to know how? Thank you.
What should I do next?
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
For me, I did get to relock by accident but I confirm that the unlock code is permanent (at least, I did use it 3 times with no problem!)
P10 lite Pinout
I would like to know if they have tried to unlock the bootloader with the Pinout method.
Correcaminos604 said:
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Click to expand...
Click to collapse
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
be-rty said:
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Click to expand...
Click to collapse
Correcaminos604 said:
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
Click to expand...
Click to collapse
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Sam Nakamura said:
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
DC-Unlocker can't find my phone
I followed your instructions, but when I click the magnifying glass on DC-unlocker it says
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM6
===================================================================
But then nothing else is listed .....
My model is WAS-LX1
Correcaminos604 said:
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Click to expand...
Click to collapse
Yeah, it's actually crazy cool that it was patched after all this years, I however read it was primary updated to support the coronavirus warning App framework! That's actually the reason for Huawei to push another last update!
Sounds like a crazy conspiracy theory but was written on their Homepage...
Sent from my Google Pixel 3 XL using XDA Labs
Downgrade option doesn't exist for me in Hisuite. My phone is WAS-LX2 8.0.0.370(C185). The last update I got was on 13 February 2019 with the 2019 Feb security patches. Is there a free way to unlock bootloader?
I just saw an update notification that Android 11 had been released. Since my phone was running Android 10, I proceeded the update without hesitation (and without backup). The phone is running stock rom without root (I guess I did unlock the bootloader but couldn't confirm since this new rom version cannot boot into fastboot mode). After update, the lock screen keeps flicking and I cannot unlock the phone. I tried booting into safe mode but got the same flicking lock screen.
The rollback pack has flagged 'ota-downgrade=yes' so data will always be wiped.
Code:
... "ota-downgrade=yes" will be set in the package metadata file. A data wipe will always be enforced when using this flag...
I guess my last hope is that
Option 1) Wish I really did unlock the boot loader and some gurus found a way to boot into fastboot mode and flash the customer recovery/android 10 so I can pull my photos/videos by adb.
Option 2) Tried booting into recovery but no new OTA update available. Wait for new OTA update
Option 3) Some found a way to
a) boot into EDL/Download mode and
b) flash TWRP/Android 10 using QPST/QFIL (Not possible currently since Qualcomm QPST/QFIL tools did not work and official realme flash (MSMDownloadTool) ALWAYS wipe your data!)
Option 4) Someone got the private key so we can sign our customized-made update_pack and copy photos/videos to OTG USB Drive under Recovery.
Option 5) Someone share a rollback pack with 'override_timestamp=yes' instead of "ota-downgrade=yes" so data will NOT be wiped
Any comments are welcome
Spoiler: Button Combos for Booting into Other Mode
Vol Up + Power (hold for 10s)= Force Shut Down
Vol Down + USB Charging = Recovery
Vol Down when booting = Safe mode
depth testing.apk = Fast Boot (https://c.realme.com/in/post-details/1244859266402091008)
? = EDL/Download Mode
Latest Official Roms
软件升级
软件升级
www.realme.com
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1340_all_2QCxQYdkxpql.ozip
Bootloader Unlock Guide
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
c.realme.com
Spoiler: OTA Update Pack
https://download.c.realme.com/osupdate/RMX1931_11_OTA_0150_all_oDfL8HoMZ5HW.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1220_all_Dx2plLOdGTD4.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1280_all_4zs7Gcdyxm3V.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1250_all_H8peW44p7GS0.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1300_all_QzFVhQQieINQ.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1330_all_sgVacScUYMkf.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1340_all_2QCxQYdkxpql.ozip
Spoiler: OTA Rollback Pack
RMX1931_11_OTA_0170_all_VEio9eM857gn.ozip
RMX1931_11_OTA_1330_all_19781_downgrade.ozip
Did you have any luck getting your phone back to normal?
aiben16 said:
Did you have any luck getting your phone back to normal?
Click to expand...
Click to collapse
No.
I want my data back and waiting for next update seems to be the only hope. Reported to realme but get no response.
If you have similar issue and don't care your data, you can do factory reset.
Am on the same boat here, Bluetooth devices still get automatically connected, USB works (mouse and keyboard) but still haven't found a way past the flicking login screen.
Happened overnight and last backup was quite a few months ago, definitively need to get the data back.
- Edit: Booting to safe-mode doesn't help either.
- Edit2: Can't attempt any update because the device is not accepting my lockscreen password either.
Mywk said:
Am on the same boat here, Bluetooth devices still get automatically connected, USB works (mouse and keyboard) but still haven't found a way past the flicking login screen.
Happened overnight and last backup was quite a few months ago, definitively need to get the data back.
- Edit: Booting to safe-mode doesn't help either.
- Edit2: Can't attempt any update because the device is not accepting my lockscreen password either.
Click to expand...
Click to collapse
If you disabled or uninstalled the coloros calendar package via ADB, enable or reinstall it again via ADB, the new System UI in the Android 11 update relies on it
This really sucks.
Any solution yet? Would be happy if I could just get access to my photos...
BTW for future reference, I'm on a Realme X Lite. I actually was positively surprised with this phone (up and running perfectly for over 2 years), but this policy is quite shocking...
Phil_123 said:
If you disabled or uninstalled the coloros calendar package via ADB, enable or reinstall it again via ADB, the new System UI in the Android 11 update relies on it
Click to expand...
Click to collapse
Just wonder if there is any way to sideload apk via adb since I can't even go to the home screen and accept adb connection.
Almost one year passed but no progress. No firmware update either.
damonxd said:
Just wonder if there is any way to sideload apk via adb since I can't even go to the home screen and accept adb connection.
Click to expand...
Click to collapse
I forgot what I exactly did to get out of the situation. From what I very vaguely remember, it might have involved tapping where the Allow button would be very quickly before the whole UI crashes. Then, depending on whether you disabled or uninstalled the weather package, you either enable or "install-existing" the package name.
How to install / get back uninstalled Apps (APKs) with ADB.
A lot of people searched for a way to uninstall bloat or APKs using ADB because a lot of OEMs don't allow uninstalling many of preinstalled apps. Tested on Pie and Oreo. BUT most of the articles if not all of them ( couldn't find any article...
forum.xda-developers.com
Phil_123 said:
I forgot what I exactly did to get out of the situation. From what I very vaguely remember, it might have involved tapping where the Allow button would be very quickly before the whole UI crashes. Then, depending on whether you disabled or uninstalled the weather package, you either enable or "install-existing" the package name.
How to install / get back uninstalled Apps (APKs) with ADB.
A lot of people searched for a way to uninstall bloat or APKs using ADB because a lot of OEMs don't allow uninstalling many of preinstalled apps. Tested on Pie and Oreo. BUT most of the articles if not all of them ( couldn't find any article...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the tips. It seems my situation is a bit difference. I can't even see the unlock pattern screen to let me unlock the phone before I can tap "allow" for USB connection and entering ADB commands. Maybe yours have the screen lock disabled before updating.
Hi,
for my Google Pixel 5 I want /e/os/.
Two instructions how to accomplish this. To flash /e/os onto a Google Pixel 5, the smartphone need to have Android 12.
My Google Pixel 5 has Android 13 (I received a New Old Stock device in a unopened box with Android 13. So no tinkering
beforehand.)
I found this archive of Android 12 images - all for the Google Pixel 5 and all Android 12:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
How can I determine and choose the correct image to flash?
Cheers!
Etymotics
12.1.0 (SQ3A.220705.003.A1, Jul 2022) is going to be the latest android 12 build which should be compatible.
Hi noidea24,
thank you for your post and the information. That helps me a lot - I was confused by the shear amount of images.
Do you know a thread which may have the things I want to achieve as topic ? I tried to search with keywords
like "Google Pixel 5 /e/os" and similiar, but it looks like the search found all threads containing GOOGLE *and* all threads with PIXEL *and* all....and so forth. I would need a second search engine to skim through the results...\
Cheers!
Etymotics
What are you looking for specifically? There's not really much info on e/os on the pixel 5. It works well, but the development is slow. Why e/os over similar projects with updated android versions like Graphene, Calyx, Copperhead?
e/os is not daily drivable, recommend not to install.
e/os was recommended to me by Marcel Bokhorst, the author of XPrivacy.
But as it seems, I had bad luck with the phone I bought:
The "OEM unlock" is greyed out and I know of no way to unlock the bootloader.
It currently runs on Android13 and last update was Dec. '22.
My intention behind all this was to have a de-googled phone because I [CENSORED] this
tracking and spying and "owning" a device, which I cannot control to 100%.
Anything else I can do to achieve this?
PS: My phone may be is one of these [CENSORED] Verizon devices. It was originally packaged
and as it seems never used before...
Where did you buy your phone? Ebay? A retailer?
Is there a keyword "Locked" or "Unlocked" anywhere on the website?
If the product listing didn't mention anything about it being carrier locked, I suggest requesting a refund or a replacement.
The "OEM Unlock" greyed-out is most definitely due to it being a carrier locked device and you're out of luck.
Also, if you truly want a de-googled OS, I recommend Graphene OS. https://grapheneos.org/
Etymotics said:
e/os was recommended to me by Marcel Bokhorst, the author of XPrivacy.
But as it seems, I had bad luck with the phone I bought:
The "OEM unlock" is greyed out and I know of no way to unlock the bootloader.
It currently runs on Android13 and last update was Dec. '22.
My intention behind all this was to have a de-googled phone because I [CENSORED] this
tracking and spying and "owning" a device, which I cannot control to 100%.
Anything else I can do to achieve this?
PS: My phone may be is one of these [CENSORED] Verizon devices. It was originally packaged
and as it seems never used before...
Click to expand...
Click to collapse
Not to give you false hope but did you connect to wifi on your first time through setup? If you don't, OEM unlock will be greyed out, regardless.
Hi Alex,
(NOT meant as any form of criticism or complaint... )
...I am a little confused here.
Other posts (not necessarily on this forum...can't remember) say: "Pull out the simcard, disable Wifi and DON'T contact anything, only skip through the setup..."
At the moment I only have a simcard of the wrong size...but I enabled Wifi but did not update anything in fear of getting an even stronger patch to disable any form of tinkering.
But as I am still having a locked "OEM unlocking" and a locked bootloader I am open for any kind of tinkering to get
this damn thing freed.
Would these steps ok:
Start the phone,
Setup lockscreen, dark theme, etc..
enable Wifi and download all updates, install updates
Ok? Or what would you suggest?
Cheers!
Etymotics
Etymotics said:
Hi Alex,
(NOT meant as any form of criticism or complaint... )
...I am a little confused here.
Other posts (not necessarily on this forum...can't remember) say: "Pull out the simcard, disable Wifi and DON'T contact anything, only skip through the setup..."
At the moment I only have a simcard of the wrong size...but I enabled Wifi but did not update anything in fear of getting an even stronger patch to disable any form of tinkering.
But as I am still having a locked "OEM unlocking" and a locked bootloader I am open for any kind of tinkering to get
this damn thing freed.
Would these steps ok:
Start the phone,
Setup lockscreen, dark theme, etc..
enable Wifi and download all updates, install updates
Ok? Or what would you suggest?
Cheers!
Etymotics
Click to expand...
Click to collapse
If you're not going to lose data or your not afraid of it, I would:
Factory reset without sim card in
When phone reboots, start setup
Don't put sim in but do connect to wifi
Skip through setup if you want and check if oem unlock is available
I'm not sure of the instructions you have, maybe that's what people believe for Verizon phones but you're not sure if you have one, correct?
Here's my experience:
I have several pixels, all unlocked. If I flash back to stock firmware and skip through setup without connecting to wifi, OEM unlock is greyed out. If I connect wifi on the first time through, it's available.
I've also heard this in tech videos. However, it won't work with Verizon phones. But if yours isn't Verizon, this could be the reason you're not able to unlock.
Hi Alex,
thank you for all your help! By the way: Are there any definite proofs for "my smartphone is a Verizon one" ?
I will try what you wrote and will be back with the result.
Two things came into my mind:
- Shall I install updates/upgrades if offered?
- Would downgrading (if even possible) via Chrome and the "Flash" feature on the Google page with all these images help, if I have a Verizon jail?
Cheers!
Etymotics
Etymotics said:
Hi Alex,
thank you for all your help! By the way: Are there any definite proofs for "my smartphone is a Verizon one" ?
I will try what you wrote and will be back with the result.
Two things came into my mind:
- Shall I install updates/upgrades if offered?
- Would downgrading (if even possible) via Chrome and the "Flash" feature on the Google page with all these images help, if I have a Verizon jail?
Cheers!
Etymotics
Click to expand...
Click to collapse
There may be a way but I'm not entirely sure, perhaps Google well help. I do seem to remember something about the IEMI but that may have been older models.
I wouldn't upgrade anything after setup and it shouldn't offer anything during.
As far as I know, downgrading won't help but I don't think you could from the Google page, as it requires an unlocked bootloader
Hi Alex,
I will try, what you wrote without updating anything ... will be back then...
Hi Alex,
no...unfortunately it does not help to connect to wifi...the "OEM unlock" is still grayed out.
Now....I wanted a de-googled phone to keep my privacy...instead I got a phone which is the
exact opposite. Unfortunately the cost of that thing remains the same...
Anything else, I can try?
Cheers!
Etymotics
Last week-end, i was abble to downgrade a Pixel 5 from A13 to A12 following this page
Navigate this article:
Downgrading your Google Pixel smartphone to stable Android version
Method 1: Leave the beta program
Method 2: Manual downgrade
Using Android Flash Tool
Using Fastboot
choose method 2 : fastboot (at the end of the article)
https://www.xda-developers.com/how-...rom-beta-developer-preview-to-stable-android/
and install e-1.10-s-20230412278810-stable-redfin according to the official instructions https://doc.e.foundation/devices/redfin/install
Hi Piero-e
That sounds very interesting. Did you unlock your bootloader before starting the procedure?
Did you change the bootloader of you device to another one?
Cheers!
Etymotics
Yes, i first unlock the bootloader (using the WiFi connection to another phone)
And flash bootloader and modem,
Then unfortunately my computer don't find the flash-all command, so I used the Gogol online tool to flash the others partitions