Hi everyone,
I have a live demo unit Samsung Fold 4 SM936B/DS (000... imei).
I obtained it for free from a friend who has an internet provider store and received it as a retailer (because this device has no market he says...).
I'm using it as a tablet and I'm loving it.
This phone is amazing, just holding it feels great, the premium feel is intense.
Now, it works perfectly except for the retail mode, which does not allow me to do certain things (screen lock, energy save mode ecc.).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, it's in Italian.
Does anyone knows how to get rid of this mode?
I tried everything, but this mode is always on (wow samsung, well done!).
There is no Retail app on the phone.
What I've done:
- Wipe data and factory reset (this was easy)
- Flash stock firmware with same csc via ODIN (WWA)
- Flash updated firmware and kernel with android 13
- Change CSC (EUX)
- Root with Magisk
- LsPosed with Zygisk (searched for some module in it with no success)
- Successfull USB ADB su
(Really, is this mode written with some kind of magic or with Mjöllnir on the cpu?)
Doesn't seems like Chimera or Z3X have the remove demo functionality for this phone yet.
Regarding this, why? Why chimera has only basic functionalities for the entire Galaxy Fold branch?
Any idea of what else can I try?
Secondary question:
Is it possible through some kind of advanced or fancy tool to repair the IMEI?
Attention: I'm not asking to replace IMEI as it is illegal, but to repair the original device IMEI (as I think it should have a modem).
I am not really an expert in the android's stuff but as a software programmer (or at least I try my best) I can try to perform some usually "hard" procedures.
Thank you
You can repair imei only if knox void 0*0
My Knox void is 0x1.
Do all original imei repair methods require knox 0x0?
For example, i was looking for a method which edit efs files with hex editor (doesn't work as I don't have the indicated files).
What does knox void have to do with imei and demo mode?
Thank you!
giorgiogatti1112 said:
My Knox void is 0x1.
Do all original imei repair methods require knox 0x0?
For example, i was looking for a method which edit efs files with hex editor (doesn't work as I don't have the indicated files).
What does knox void have to do with imei and demo mode?
Thank you!
Click to expand...
Click to collapse
For these devices, the imei is repair on the Samsung cpid server
One of the most important conditions is Void 0
It's a demo unit so you're never going to be able to repair the IMEI issue. Samsung deliberately send out demo units with gimped modems to retailers so when these phones are snatched, they're next to useless.
Get a replacement board, sell for spares or if I was on another website, I'd tell you to give it back.......
mckeowngoo said:
It's a demo unit so you're never going to be able to repair the IMEI issue. Samsung deliberately send out demo units with gimped modems to retailers so when these phones are snatched, they're next to useless.
Get a replacement board, sell for spares or if I was on another website, I'd tell you to give it back.......
Click to expand...
Click to collapse
Thank you for your reply!
In this case, i think I'll use it as a tablet, you know, it's free!
I'll wait for chimera to release Imei repair and patch certificate(if ever); on older models it is possible to apply also on knox 1 status.
Hi, do you maybe have this video on your phone? I saw it on the phone in the store but dont have it on my fold 4
So many misleading information here on this thread;
Let me a correct a few; and link this whenever this discussion starts somewhere. It's an effing pain to see this getting repeated again and agin.
----
Demo units (After S10) are an exact match to commercial units which are sold, the only thing missing is an IMEI.
Prior to this, They used to "not have" SIM Slots, Modems, Antenna and other various hardware differences.
Demo units have X in their model code's end while commercial units have F / B codes. (eg: G980F is commercial and G980X is Demo).
Most common accusation (not here - in general) is that you have stolen a demo unit from a shop - No, They aren't always stolen, sometimes samsung gives them away to their store employees when the product is marked EOL. Some do get stolen as well, but at a time where we are monitored by CCTV 24/7 - what are the odds of that nowadays?
You can remove the demo mode loop / demo apps by flashing a stock firmware from ODIN and use it as a tablet with just WIFI connectivity. You cant make calls from this yet - without the IMEI.
If you need to use it as a phone with cellular connectivity, You need to generate and assign an IMEI for it. For this you need someone with Samsung CPID server access, Let them know your DID code from Download mode - and the phone needs to be stock (Not Rooted / Knox 0x0). This service costs and you can find many sellers with a Google search. They will connect to you over TeamViewer to carry out the process.
If the Phone is rooted, there is a certificate patch method - but that is temporary and gets wiped when the phone is updated or sometimes even when rebooted.
The Demo Error which OP speaks of - cannot be removed. I have a fully converted Fold 4 from a demo (With IMEI - see top of attached screenshot) and later rooted it as well. Still I couldnt figure out how to remove this error. I modified the EFS files (Product Code / Region Code) too, and didnt remove the below error. It may be linked to the same reason why we cannot change the 4th CSC of the phone. It doesnt affect in any daily work, and the phone works fine. Just the error shows up in a few settings screens.
Related
Introduction
This package will totally reset your Galaxy Tab P100 to EA24 . This package is intended for use on the SPRINT Galaxy Tab.
This package includes:
Repartitioning: Repartition to stock EA24
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and
Formatting:Cache and DBdata
This package does not wipe:
MODEM(communications handler, get one from The Modem Thread)
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
Download:
Download Sprint Total Stock EA24
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download VZW Total Stock DJ11
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
Your device will end up as it came from the factory. You will be asked to set your device up again. After connecting to WIFI you may receive a carrier package update.
Will this work for VZW Tabs? I see VZW in the title, but EA24 is totally Sprint. What gives?
ezeuba said:
Will this work for VZW Tabs? I see VZW in the title, but EA24 is totally Sprint. What gives?
Click to expand...
Click to collapse
It is a sprint package. My focus is recovery with UnBrickable mod. This is part of a system of recovery for use with Linux where a device which wont boot needs a firmware flash from temporarily uploaded bootloaders.
I'll get a vzw package up. I totally forgot about carrier branding.
Yeah this will be great for VZW. I was thinking of selling mine and returning it to stock but when I tried it said baseband was EI04 but it was android version 2.2??!??? will your method, when u post it, take us back to stock 2.3.5 EI04?
tombepa said:
Yeah this will be great for VZW. I was thinking of selling mine and returning it to stock but when I tried it said baseband was EI04 but it was android version 2.2??!??? will your method, when u post it, take us back to stock 2.3.5 EI04?
Click to expand...
Click to collapse
I'm uploading DJ11 right now, this is a 2.2 build.
tried this tonight on VZW tab - flash goes fine - when I try activation bypass with volume up/down, it works initially, then lets me proceed with setup, but when setup is done and get prompt that galaxy tab is ready to use, it takes me back to the "welcome to SCH-I800" screen (which I've never seen on any ROM - can't remember if it was there when I first got the tab stock and set it up) - when I touch the android, it takes me back to activation screen, but activation bypass will not work this time - perhaps some remnants of your Sprint files still there? Have reflashed three times, same result - I don't know - so close to working - I'm trying to get back to stock DJ11 so I can update to stock 2.3.5 - anyone else having this problem?
Jacklad said:
tried this tonight on VZW tab - flash goes fine - when I try activation bypass with volume up/down, it works initially, then lets me proceed with setup, but when setup is done and get prompt that galaxy tab is ready to use, it takes me back to the "welcome to SCH-I800" screen (which I've never seen on any ROM - can't remember if it was there when I first got the tab stock and set it up) - when I touch the android, it takes me back to activation screen, but activation bypass will not work this time - perhaps some remnants of your Sprint files still there? Have reflashed three times, same result - I don't know - so close to working - I'm trying to get back to stock DJ11 so I can update to stock 2.3.5 - anyone else having this problem?
Click to expand...
Click to collapse
They're two different packages. Different kernels ROMs and Params and cache. You're experiencing a stock ROM which requires activation.
AdamOutler said:
They're two different packages. Different kernels ROMs and Params and cache. You're experiencing a stock ROM which requires activation.
Click to expand...
Click to collapse
Understood that it's stock - but even on out of the box, totally stock tabs the bypass trick works - something weird about they way it will take you through the setup process perfectly, only to bring you back to the android screen, which you do not see initially - I don't use a data plan, just wi-fi - you've done such a great job here, so close - is there any workaround?
If only this could restore modem... I would've named it the holy grail of Galaxy Tab.
I've released information on creating your own Heimdall one-Click here: [Release] Heimdall One-Click - ROM Packaging and Distribution System
I know this is an old thread but I need some assistance from whoever can provide it. I am trying to return my Sprint tab to stock with the one click but I am having a hard time.
I try to do it, but I am constantly running into walls.
I try to flash but it gets stuck on the last step where it says that it has to reboot the tab. then the one click screen says disconnected. And the computer says that it found new hardware. The tab stays looping at the samsung screen.
What should I do to get out of this?
I feel your pain! I wound up bootlooping my Sprint Tab yesterday.
I didn't see this thread, so I don't have any experience with this particular tool. However, I did manage to recover my Sprint through information I found on the forums.
You should still be able to put it back into download mode. Then using Odin/Heimdall, you can flash it back to stock with the stuff found in this post: Stock Odin/Heimdall Files: Stock EF17 Tar
Also, the [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR) thread was pretty helpful too.
Hope this gets you headed in the right direction, I haven't done much flashing with my tablet and the information above wound up helping me out.
Please Reupload Stock Firmware
Hey wondering if anybody still has the one click file for sprint sph p100
I can't find any good download links for sph p100 seems like they are too old.
Thanks
Hi everyone,
I wouldn't really call myself a developer, but I am part of a team of developers (well was - we have all got so busy in life at the moment so Android developments have slowed down a fair bit) anyway I am not currently employed so I have been doing a fair amount of phone work for a local Phone repair shop here on the Gold Coast. I met the guy when I went in to my friends computer store to get PC parts and this guy's phone store conjoins. Anyway I made mention that I can fix software on Android devices. He said that he didn't do software, my reaction was "So what you just let all that business walk out the door then?" he laughed "I suppose so". Anyway one thing lead to another and i had a phone I needed to try unlock. I wasn't actually successful with that one, but I did manage to revive the corrupt IMEI and he seemed pretty impressed by that. I got a call saying he had a Galaxy Tab for me to try get working again. So here I am
Initially I DID get it running (only for a while) on stock Gingerbread from the Restock Overcome ROM thread here, so a big thanks to @AdamOutler, @priyana, @Alterbridge86 and @ApriliaM3 for their ongoing efforts to date with supporting the P1000 TAB.
So why am I uploading a new Re-Stock? What's all this about?
Tell tell you the truth plain and simply the well known and famous "GB_Stock_Safe_v5.tar" did not work for me. I was not satisfied that this was a hardware fault either, something was telling me there was some underlying issue that had not been dealt with. Most other people, simply flash gt-p1000_mr.pit, GB_Stock_Safe_v5.tar, and JK3 Modem and they are good to go. For me I had the most unstable device I had ever worked with. Random reboots. Constant bootloops, in among every 10 reboots occasionally I reached the homescreen :victory: if I was lucky I could maybe open an app or two and apply some settings but soon as the screen locked or I left the tab for any length of time I came back to a revolving boot screen If you want to know if this is you and if what I went through is what you are experiencing then read more here >>> Tab reboots before BML/MTD can even get started. Then no recovery
There is a solution!
Download
GB_Stock_AUST_Jarmezrocks+P1.pit.zip
Mirror
GB_Stock_AUST_Jarmezrocks+P1.pit.zip
Contains the following:
GB_Stock_AUST_Jarmezrocks.tar
P1_add_hidden.pit
P1_add_hidden.pit came from the stock Australian Optus Firmware P1000XWJU6_P1000OPSJU3_P1000XXJR2_HOME.tar.md5
Oddly enough this firmware DID NOT work on this Tab? The Restock base was as close as I got and it was ridiculous and unusable.
Each time I flashed this firmware ^^^ with Odin the Tab would switch off as it was applying cache or hidden and then was Bricked. Luckly Adam developed Heimdall OneClick Unbrick. I would say in the last week I have easily bricked this Tab maybe 30 or 40 times, I was determined to not let this beat me. There had to be an answer?
I pulled apart the firmwares and pretty much went with my gut instincts. Here is the run down:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The PIT
The difference between P1_add_hidden.pit and gt-p1000_mr.pit have hidden and cache partitions switched as far as I can see? Naturally in the Optus firmware the Hidden partition is just oversized and most likely full of bloat/[email protected] in other words. I included the P1 pit in the firmware build because it was in the original. I am not sure of this does anything extra, but figured it can't hurt anyway (even though people are freaked out about pit files) seeming we re-partition when Re-stocking GB anyway.
dbdata
I knew that dbdata is important especially if we have oblitorated the data partition and made a fair mess of everything. I think this is the most importance file besides the pit when we need to return to stock.
movinand
Movinand was included because when I inspected the P1 pit it had an allocation for it. There was maybe a chance that when not all partitions in the structure are written to I could provide a weekness or void for data to "overflow" so to speak. I think of partitions like dividers in fishtanks as an analogy.I bred fish and I know what happens to the structure of large tanks with partitions if adjacent tanks are filled and one left empty; it creates weakness. Anyway I decided to fill it, at least for the flashing part where data and structure are being formed by bytes of information.
cache
cache I decided to go with the larger stock firmware mainly because I think part of the issue with the Tab its self is a lack of cache (causing the instability first noted).
hidden
Need I say more? Look at the size of the stock Aust firmware
modem.bin, ZImage, boot.bin, factory.rfs
I spose I chose to stick with stock so that if that was where the tablet was staying that it looked as though it had matching firmware when looking in 'About divice' and the modem for connection specific to the carrier and region, nothing more than that really.
param.lfs
Now this part I wasn't sure about? Maybe I should have gone with the smaller one? I don't know.....they were not worlds apart in difference anyway, and really by that stage I just wanted to flash the darn thing and see if it worked! :laugh:
Result. 100% smooth boot. Device rebuilt dalvik in a reasonable time (I weigh it up close to the specs on my Galaxy S1); a few force closes when reaching the home screen but they are kind of expected considering the device age and specs. Within about 15 min and 1 reboot into recovery to "re-fix permissions" (which seemed to stabilise it for some reason?) and then no more force closes, device operated perfectly! Smooth, no glitches no random reboots. Man I was sooooo happy!!!:victory:
As per the instructions I went on to faultlessly perform the upgrade to Overcome Kernel, CM9 (BML/MTD), it rebooted once as expected to change kernel and recovery, then continued all the way through to completion. I then remounted the partitions (wow this seems to be a really big issue with the P1000 doesn't it? Why is it that nearly every boot into recovery leads to half or more partitions left unmounted? - Note it doesn't boot unless you mount the damn things!) anyway I cleared caches(note clearing caches happened far too fast so that is how I noticed the partitions were not mounted), factory reset and reset permissions! (THIS PART IS IMPORTANT ON THE P1000!!!)
I rebooted; it took several reboots and rebuilding of the dalvik caches before it would reach the home screen. I think something like 28 apps got split up into about 3 or 4 reboots (which did it's self) and I was worried again that I had another unstable device, but figured it was a bit uneasy on her feet in GB, and maybe JB was similar....so I rebooted, fixed permissions again and rebooted. Sure enough perfect!! Device is still running faultlessly. I will proceed to theme it, and add a few "nice touches" before it is returned to the owner tomorrow.
To fill in the blanks of the story when I got given the Tab I could see someone had messed with it already. When I told the guy initially the next day that I got it working albeit rather unstable though his reaction was priceless! He goes "You what? You got it going? How the f#*% did you manage that? Man 5 different phone shops have looked at that and probably at least another 5 other tech geeks that all know a fair bit about phones & tablets. None of them got it to work!" he continued "Do you know that thing has not been touched for at least a year and half!"
So it was a big test really. I didn't know this till about an hour ago when he saw that I had it all running:laugh::laugh::laugh: Guess I passed then eh?
XDA:DevDB Information
*NEW* GB Re-Stock Safe for Australian P1000 Tabs where GB_Stock, ROM for the Samsung Galaxy Note 10.1
Contributors
Jarmezrocks
ROM Firmware Required: For Bricked Devices
Based On: GB_Safe_Stock_v5
Version Information
Status: Stable
Current Stable Version: v1.0
Stable Release Date: 2014-05-22
Created 2014-05-22
Last Updated 2014-07-09
cannot download!
can you upload to MF?
If I flash on my Gt-P1000, everything is OK?
Great job!
This rom saved my tab! The other old rom's all had missing parts (dbdata...) but this one is completely usable. Thanks!
Thank you so much!
Best regard!
So, I decided to apply to unlock my bootloader. I started following this guide.
I created a Mi account, but I was not greeted by a form to write the reason I wanted to unlock the bootloader.
A little baffled there, but I decided to proceed (maybe the form was in the app). I proceeded to the unlock page and voila! I had the link to download the Flash Tool. And so I did, I ran the miflash_unlock.exe and filled in my account and password.
Next I plugged in my phone in fastboot mode, as it was needed (I had not enable OEM Unlock in Developer Options nor had I associated my device with my account), and I was greeted with this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What am I doing wrong? The Unlock button is active (meaning I can click it), but I don't want to brick my phone a couple of days after I bought it.
My device (just in case):
Android Version : 8.1.0 OPM1.171019.011
MIUI Version : MIUI Global 9.5 | Stable 9.5.13.0(OEIMIFA)
Baseband Version : 660_GEN_PACK-1.147555.0.150932.1
Kernel Version : 4.4.78-perf+
Android Security Patch Level : 2018-05-01
You're not doing anything wrong. Now you don't need to apply for permission. Instead go ahead and start Unlocking process. You will be promoted with a message saying that you need to wait for some amount of time (72, 360 or even 720 hours) depending on your model.
Bind your Mi account with your device first.
Go to settings > additional settings > developer options > here you'll find the option to bond your Mi account with your device.
Edit: don't update MIUI as you have arb-3
Dhaval.Savalia said:
You're not doing anything wrong. Now you don't need to apply for permission. Instead go ahead and start Unlocking process. You will be promoted with a message saying that you need to wait for some amount of time (72, 360 or even 720 hours) depending on your model.
Bind your Mi account with your device first.
Go to settings > additional settings > developer options > here you'll find the option to bond your Mi account with your device.
Edit: don't update MIUI as you have arb-3
Click to expand...
Click to collapse
Thank you for your reply, it was clarifying! On the guide, it says I have to use a VPN to access the Chinese servers, is it really necessary? (just a question, it is not an issue!)
Hi,
My query is kind of different.
I want to hide unlocked bootloader from a few apps. ( Blackberry Work email app).
Any information on this will be greatly appreciated.
Thanks.
Preetam
TassosKan said:
Thank you for your reply, it was clarifying! On the guide, it says I have to use a VPN to access the Chinese servers, is it really necessary? (just a question, it is not an issue!)
Click to expand...
Click to collapse
I tried connecting to a bunch of Chinese server using VPN (as seen on some youtube videos) but I guess that method is now patched. I guess, it's only applicable on phones with Chinese ROMs within China.
You have to wait. While find some good ROMs and stuff. All the best.
---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------
preetam.id said:
Hi,
My query is kind of different.
I want to hide unlocked bootloader from a few apps. ( Blackberry Work email app).
Any information on this will be greatly appreciated.
Thanks.
Preetam
Click to expand...
Click to collapse
Some apps requires Safetynet to be passed in order to use them, i.e. Banking apps. Unlocked bootloader, rooted phone can trigger this safetynet to fail. You can use magisk to hide the fact that your phone is unlocked.
Dhaval.Savalia said:
I tried connecting to a bunch of Chinese server using VPN (as seen on some youtube videos) but I guess that method is now patched. I guess, it's only applicable on phones with Chinese ROMs within China.
You have to wait. While find some good ROMs and stuff. All the best.
---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------
Some apps requires Safetynet to be passed in order to use them, i.e. Banking apps. Unlocked bootloader, rooted phone can trigger this safetynet to fail. You can use magisk to hide the fact that your phone is unlocked.
Click to expand...
Click to collapse
Thanks for the revert,
however I have already tried Magisk hide and safetynet module but it's not working for me. I am using Redmi note 5 pro with Android 9.0 Pie based Pixel Experience Custom ROM. I am very happy with the ROM except that I am not able to use Blackberry Work app. Other banking apps are working fine.
Yesterday I decided to update to MIUI, I'll see what happens with ARB when I get to it, and I must say I am impressed! @preetam.id I believe it has to do with Blackberry Servers, not Magisk Hide feature, though I haven't used it for a couple of years now and don't what changes RIM has introduced.
TassosKan said:
Yesterday I decided to update to MIUI, I'll see what happens with ARB when I get to it, and I must say I am impressed! @preetam.id I believe it has to do with Blackberry Servers, not Magisk Hide feature, though I haven't used it for a couple of years now and don't what changes RIM has introduced.
Click to expand...
Click to collapse
Since you updated you can no longer go back to the stock ROM your device came with. You do realize this right? What you will have to do from here is stay on ARB4 and unlock your device from here.
Did you proceed with the unlocking for your device? I too just got my device yesterday and do not want to risk bricking. I don't see an option for bonding the account to the device in developer options.
Through googling, there are a few tutorial in going through how to get this rooted. But does anyone has any success?
Do I have to apply to unlock the OEM unlocker first through online before getting started?
How To Root Xiaomi Poco F3 with Magisk (No TWRP Required) - NaldoTech
If you like to customize your Xiaomi Poco F3 and have complete control over its firmware, then the first thing you should do is root it. You can root the
www.naldotech.com
https://www.getdroidtips.com/root-poco-f3/
Mahoro.san said:
Do I have to apply to unlock the OEM unlocker first through online before getting started?
Click to expand...
Click to collapse
Yes, your F3 bootloader has to be unlocked. Keep in mind that doing so will NOT void device warranty, but phone contents will be erased. So take a backup of personal or important files before proceeding.
Thank you Leo,
Just started the unlock process and it requires 168hr (7days) of wait time , guess I can still uses my op5 phone for sometime until the wait.
Pretty annoying way of wait but at least its not unattainable.
fastleo63 said:
Yes, your F3 bootloader has to be unlocked. Keep in mind that doing so will NOT void device warranty, but phone contents will be erased. So take a backup of personal or important files before proceeding.
Click to expand...
Click to collapse
Hey. Are you sure it won't void warranty ? E.g.article
Bootloader Unlocking does not Void Warranty of Xiaomi and Redmi Devices - Gizmochina
Xiaomi smartphones are popular in the developer community, thanks to the company’s policy regarding warranty against unlocking of bootloader. But the brand has now updated its policy. Thankfully, bootloader unlocks still does not void warranty of Xiaomi and Redmi devices but with some caveats...
www.gizmochina.com
It says about unlock policy :
... "This policy is applicable to Xiaomi phones in India under both the Mi and Redmi sub-brand. Other regions could possibly have variations to this policy. And before you ask, POCO is excluded from the scope of this article and this policy entirely as it operates as an independent unit and has its own separate policy."
Do you have the source of the information that unlocking POCO from anywhere in the world is officialy not voiding warranty?
I don't know exactly if the above apply in your country.
Here in Italy Xiaomi/POCO said clearly that bootloader unlock and device rooting DOES NOT void warranty.
If further operations will lead to a phone crash/brick, so warranty will be void, and device will be repaired at a cost.
If in doubt, I suggest to ask directly to your local POCO office.
I've got not local poco office jn my country (Poland) . When asked reseller they said - every software modification results in warranty loss. I don't trust their judgment entirely. Anybody know who I may ask about that?
Eventually we all know we relock bootloade, but if they want to they can see if that was the case.
I'm really struggling about unlock + root. I'm not sure if phone has a any defect.
I'll do it for sure in time (I really need V4A). I would have more morales if it was not loosing warranty
osemoka said:
...I really need V4A...
Click to expand...
Click to collapse
Be aware that installing V4A on Android R devices like our F3 isn't as simple as it was with previous versions.
For example, the driver needs Selinux set to permissive to work correctly (a little risky practice).
For the moment I decided to give up, and installed a similar alternative (Wavelet).
Well. On my poco f1 with android q it was problematic but I found workaround not setting Linux to permissive I think. I just had to restart v4a and Spotify often before to make it work ^^. I am desperate to have it. I can't use in-ear headphones without auditory ear protection. They hurt my ears. Wavelet does not have that. Is it a way to achieve the effect? It's a bit off topic already so I will just ask elsewhere...
Mahoro.san said:
Thank you Leo,
Just started the unlock process and it requires 168hr (7days) of wait time , guess I can still uses my op5 phone for sometime until the wait.
Pretty annoying way of wait but at least its not unattainable.
Click to expand...
Click to collapse
Hey mate I'm new on this kind of thing but can you share to me how do you unlock your bootloader?
jfmark0718 said:
Hey mate I'm new on this kind of thing but can you share to me how do you unlock your bootloader?
Click to expand...
Click to collapse
Apply for unlocking Mi devices
en.miui.com
Mahoro.san said:
Do I have to apply to unlock the OEM unlocker first through online before getting started?
Click to expand...
Click to collapse
Yes. Before flashing the patched boot.img you must unlock the bootloader of your F3.
What is this?There is option in dev opt that unlocks bootloader.I never unlocked my old phones by manufacturer.
djuroue1 said:
What is this?There is option in dev opt that unlocks bootloader.I never unlocked my old phones by manufacturer.
Click to expand...
Click to collapse
It does not unlock bootloader, it only allows you to do it in fadtboot if you toggle it. With Xiaomi you need as well their blessing with a code to be able to unlock bootloader as far as I know (no real life experience with Xiaomi yet, still waiting for my F3)
Today I managed to set up Magisk Root without TWRP!
Installation
The Magic Mask for Android
topjohnwu.github.io
"Patching Images"
The first time the F3 was stuck in bootloop so please save the original Boot.img on the PC to flash it via Fastboot if something goes wrong.
Bootloader unlock is mandatory, is only unlocked after 1 week and deletes all data.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does unlocking the bootloader disable the ota rom update ? If that's the case do you have to manually flash the rom through fast boot everytime for updating?
Mahoro.san said:
Does unlocking the bootloader disable the ota rom update ? If that's the case do you have to manually flash the rom through fast boot everytime for updating?
Click to expand...
Click to collapse
Afaik unlocking bootloader does not, rooting does disable ota.
And yes. Only way to flash/update roms is via fastboot untill twrp release.
I found some instructions on how to preserve Magisk root on A/B devices like our F3:
https://topjohnwu.github.io/Magisk/ota.html
I need some advice because the Magisk uninstall process described up there involves original boot.img restoring.
But how can it be possible? The original boot.img is only on my PC, and not on the phone...
Hello, is it possible and how to have magisk after unlocking and flashing a rom with fastboot ?
lejeanlouisF said:
Hello, is it possible and how to have magisk after unlocking and flashing a rom with fastboot ?
Click to expand...
Click to collapse
Yes, it's absolutely possible.
Link: Installation | Magisk
The above operations must be repeated every time you'll flash a new ROM.
I have flashed it but failed safety check .
And can't get the adaway work
RTHello Everyone This Is My OnePlus 9RT 5G
Actually Before I am In custom rom I just want to switch oos then I use rollback packages its Successfully done and I finish setup then I off phone again and try to lock boot loader when I press lock then it's happened...Someone Can Help Me Please???
Thank You Everyone....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It happened because you locked bootloader with non signed firmware installed.
Press all three buttons for a long time (about 30 sec), then device should reboot to bootloader mode. From bootloader you should be able to unlock bootloader back.
penguinus said:
It happened because you locked bootloader with non signed firmware installed.
Press all three buttons for a long time (about 30 sec), then device should reboot to bootloader mode. From bootloader you should be able to unlock bootloader back.
Click to expand...
Click to collapse
Bro I try lot of time but phone can't switch bootloader....
have any another salutation like edl msm tool..
penguinus said:
It happened because you locked bootloader with non signed firmware installed.
Press all three buttons for a long time (about 30 sec), then device should reboot to bootloader mode. From bootloader you should be able to unlock bootloader back.
Click to expand...
Click to collapse
Your browser is not able to display this video.
Strange. Try to release power and volume up button (continue to press vol down) when phone reboots.
MSM is not available for public for 9RT. You may try to contact OnePlus support, 5hey can do it remotely on your PC. Other option is third party paid service.
penguinus said:
Strange. Try to release power and volume up button (continue to press vol down) when phone reboots.
MSM is not available for public for 9RT. You may try to contact OnePlus support, 5hey can do it remotely on your PC. Other option is third party paid service.
Click to expand...
Click to collapse
Do You Know Bro How Can i Apply for OnePlus Support Via remotely?
penguinus said:
Strange. Try to release power and volume up button (continue to press vol down) when phone reboots.
MSM is not available for public for 9RT. You may try to contact OnePlus support, 5hey can do it remotely on your PC. Other option is third party paid service.
Click to expand...
Click to collapse
And Bro I Try as You Said But Its Not work If Possible Please Tell me how can i apply for OnePlus Support Via Online???
9RT is only for China and India market. So you should communicate with support in country your phone is bought in. I.e. if you bought on Alixpress (as I did), you should communicate with chinese support. Find the link to support chat on this page, it will require valid heytap account as I know. Also I don't recommend to say you tried custom firmwares and other such stuff. Just say your phone stopped to boot after firmware upgrade and you don't know what happened. Also take into account that chinese version is Color OS, they will flash ColorOS - not Oxygen.
Personally I didn't use this way, I used paid service.
penguinus said:
9RT is only for China and India market. So you should communicate with support in country your phone is bought in. I.e. if you bought on Alixpress (as I did), you should communicate with chinese support. Find the link to support chat on this page, it will require valid heytap account as I know. Also I don't recommend to say you tried custom firmwares and other such stuff. Just say your phone stopped to boot after firmware upgrade and you don't know what happened. Also take into account that chinese version is Color OS, they will flash ColorOS - not Oxygen.
Personally I didn't use this way, I used paid service.
Click to expand...
Click to collapse
Thanks a lot Bro I Buy From India bro..and if they install COS later I install OSS Right? if i get there Support??
Mr.brand said:
Thanks a lot Bro I Buy From India bro..and if they install COS later I install OSS Right? if i get there Support??
Click to expand...
Click to collapse
How Much they charge bro?
And can you share contact who can fixed for me with oos not cos..
If you bought from India, you probably should communicate indian support. I expect it will be easier, because china is very separated from external internet, but India is very different case. I.e. for India there is official support in WhatsApp. Check it here . I believe official support may reflash for free. At least chinese support does it for free.
Paid service is third party. They are not related to OnePlus directly, but they also have MSM account.
penguinus said:
If you bought from India, you probably should communicate indian support. I expect it will be easier, because china is very separated from external internet, but India is very different case. I.e. for India there is official support in WhatsApp. Check it here . I believe official support may reflash for free. At least chinese support does it for free.
Paid service is third party. They are not related to OnePlus directly, but they also have MSM account.
Click to expand...
Click to collapse
i talk with China & India also but china said i need to contact with inida support then they give link i talk with them already via wp but they said i need to go service centre but right now i cant because i live in Vietnam that's why last day i used paid services from the same you recommend me bro after beginning he done for me 2k and now device work fine bro...thank you for your all reply and suggestions bro..