I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.
Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..
As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:
summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!
Gdhhs
Related
Hi to everyone. I have a Samsung Tab S2 SM-T810 with Android 5.1.1 / Kernel 3.10.9 that has retail mode on, it was a demo in a store. Is there anyway to remove this from the device? I already try doing a factory reset with stock firmware and odin and it stills the same. I think it has some kind of software installed on the ROM memory that prevents it to fully restore and wipe the retail mode app. Thanks in advance.
Please do a search this has been covered plenty of times already. There is no need to repeat over.
ashyx said:
Please do a search this has been covered plenty of times already. There is no need to repeat over.
Click to expand...
Click to collapse
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.
huntejes said:
I did it. that's why I specified re installing with odin didnt help. I checked all the forum. even this http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-sale-version-t2890171
and it stills the same.
Click to expand...
Click to collapse
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.
ashyx said:
It's simple, make sure OEM unlock is enabled in developer settings, Install twrp, factory reset with twrp, boot to download then flash stock Firmware.
Done.
Click to expand...
Click to collapse
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?
huntejes said:
I wouldn't be asking for help if it were that easy. I tried doing that too. All the option in the developer settings tab are gray. I can't change them. The retail app is blocking it.
Any other idea ?
Click to expand...
Click to collapse
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.
ashyx said:
Just go ahead and install twrp and continue with the previous instructions. If you get the FRP block, just flash the stock Firmware.
Also if you carry on with the attitude you're on your own.
Click to expand...
Click to collapse
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.
Ok so ive got the Sm-810 and i was experiencing the same issue of it not letting odin flash to stock OR install twrp etc. etc. and i was going to give up and i **** you not i was trying to get into the recovery to see if i could jostle some solution loose and it fixed itself !! It was booted into download mode and i unplugged the cable and pressed and held power+vol down and as soon as the screen went black i did the same thing again and then i mustve messed up cuz it booted into the os but i repeated the process from there and no kidding after 2 or 3 cycles of power+vol down i got a blue screen with an android on it and it flashed and showed a dead android with the caution! sign and the next screen showed the regular android with the word "erasing" underneath and vio'la no more retail mode. After this Odin worked and let me autoroot and so on an so forth. sorry for my long post i just though i should share
I think the major issue is that OEM is disabled and there is no way to turn it on. So most of the solutions are a no go... So any other suggestions on make this work?
huntejes said:
Excuse me, I didn't mean to offend. I'll try to install twrp right now.
As I expected while I was trying to install twrp it always return an error on Odin so I gave up, then after a couple of hours the table ran out of battery and since it was the first time it went off without the retail app monitoring. I decide to boot it into download mode. and that's it.
After that the twrp finally got installed and I erased everything on the tab. after that that it got stuck on the samsung logo. And I could install the stock firmware with no problem.
All thanks to you.
Click to expand...
Click to collapse
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\
My husband and I also ran into the problem of having our Samsung Tablet E nook 2017 model stuck on Retail Mode.. we tried EVERYTHING we could possibly think of after the 5444 password didn't work. We rooted, we downloaded "easy uninstalled" apps, did the hard reset with the 3 button deal.. nothing! Then we finally came across a few passwords we were willing to give a try.. so when you go to the retail mode bar and it prompts you for a password to uninstall try blue. The word BLUE but in lowercase.. and it worked! We were then given tons of options and finally got that crap off our paid for device. I'm 100% sure that any device purchased from Best Buy and stuck in retail mode will use the password blue. A few other passwords we came across that might be worth a shot if blue doesn't work are: galaxy and unlimited. (Each by themselves as one password) Well good luck, we know how frustrating this has been!!
Skapino said:
Hi huntejes,
I've a SM-T650NU unit and have the same issue you faced on the Odin step (of course I'm using the specific TWRP file for my unit) just want to know what error showed up. In my case it returned: FAIL! (Auth).
Will let the battery fully drain and after that repeat the TWRP flash. Do you remember (step by step) what you did after the battery drained? I mean charged to 30% then put on download mode? Any feedback will be appreciated.
BR\
Click to expand...
Click to collapse
Dude, I have a SM-t560nu and I feel your pain. For months I was trying to find a solution and had to deal with obnoxious fools who couldn't get it thru there heads that this was NOT the usual Samsung Retail Mode but a special piece of software that puts the tablet into a rolling cycle of 2-10 minutes, shuts off all developer options, locks frp and basically makes anything you do null and void. I tried every password Imaginable including "BLUE," "5444" and the oft repeated "M729Q16K8546" all to no avail.
Here's the deal: this IS unique software and you'll find it at retailsamsung.com. (I can't post the actual url because of the new user rules, which is kind of funny because I've been a member for about 10 years but I don't think I've ever posted anything.)
Go there, search your device and download 2 items: One will be your installation package (for instance "Samsung_Retailmode_Global_Common _141006.apk") and the other will be called "RetailMedia.main." Download both to na sd card, put the sd card in your device, move the programs from the sd card to the download area ON the device. Now start your device, got to the download area and tap on the first program, the apk. Enter 5444 as your password, follow the instructions. the second password will be "M729Q16K8546." This will remove the Retailmode software and most likely trigger a Samsung lock. Go to Sammobile, download the original firmware and congrats, your new tablet is finally working right.
I was wary of downloading software from such a plain site, especially one I've never heard of but I figured after 6 months of no luck and my new tablet just sitting in a drawer, unusable, what did I have to lose? Well, it works, i'ts awesome and it's like new.
Hope this helps.
Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.
I hope I'm not posting on a dead thread. I saw a good deal on a T813 in retail mode (will provide link if needed, it's on a very popular and legal south american online store). The thing is, as explained by the vendor, someone attempted to remove the retail app and now is stuck on a countdown in the lock screen. After some time it reboots itself. I've been reading a lot about the topic and the main problem seems to be the OEM unlock off. Now apparently I won't be able to access any feature of the device at all. I thought maybe I could reinstall the retail mode and get back the app or just boldly odin flash twrp and a stock rom risking myself to an FRP lock.
However I thought better ask advice first, so what do you think? Any help is greatly appreciated.
Well, I bought it and first day has been no success. I can access guest user, could log in to my ggl account and downloaded some apps. OEM, third party apps and developers are out of reach and cannot access main account. No sign of retail app.
Flashed new stock rom, FRP asks for a password, tryed 5444 Mz$%"#$%& blue galaxy unlimited with no luck. Attempts to flash twrp via odin fail due qst (?) error. I guess because is OEM locked. Flashed some older rom and still a countdown that doesn't let me in in main account.
So far, this is my progress with it. Any advice to flash twrp, remove frp lock and/or remove retail mode? Thanks in advance
_Iffer_ said:
Mfb5159, You Are Awesome! A friend entrusted me to remove the Retail Mode from her Samsung Galaxy Tab A 9.7. I tried Everything. The passwords that can be found everywhere online, circumventing the FVP (of course that was useless), downloaded & installed the firmware with Odin in download mode... nothing. Then I ran across this forum. Tried two versions of retail mode from RetailSamsung.com and the second one worked. I had to open the retail app I installed, enter the generic passwords (5444 & the M729Q16K8546), then it gave me the option to factory reset the device. I chose yes & it worked! No sign of Retail Mode on the tablet. It's like a brand new tablet!! The .apk file that worked for me was SamsungRetailMode_GlobalCommon_141006
Thank you So Much for your help.
Click to expand...
Click to collapse
Did the same, although I had to use the older ap_SamsungRetailMode_Global_Tab_A_L_v1.0.4_15031100_M15031100_P0.apk with my SM-T550 (Galaxy Tab A (2016) 9.7") - I also had to stop the existing RetailMode Service from running by opening applications, swipe across to Running Applications, and tap on the Retail Mode executables to disable the "Sta" service. Annoyingly if you accidentally get the password wrong then it'll reset itself and delete the newer APK and you have to start the whole process over again
Could anyone at least point me in the right direction please? I can't access the main user of the tablet because there's a lock on the screen saying "Try again in 1440 minutes" which is a day. It self reboots every 5 minutes and each time the 1440 minutes thing resets. I booted in safe mode, now it doesn't reset and countdown is set for the next 4 hours.
Please, any light on the matter will be great. I have 4 days to return and I wouldn't like to do it cause it was extremely cheap unless, but I don't want to end with an expensive brick either.
Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.
Hi guys,
I have a galaxy tab and sm-t561, which presents the problem of retail mode that you can not remove in any way even with odin, I wanted to ask, how do I install a version of retail mode via apk? I downloaded the new version of retail mode but how do I install it?
whchapma said:
Huntejes,
I had the same experience as you with my SM T810. The particular version of the Samsung Retail app (com.samsung.sta.retailagent.lite 6.9.20161101) installed on my unit didn't have a 'configuration settings' option; instead an option called 'Store Settings' prompted a password entry - but admin passwords 5444, blue, galaxy, unlimited all failed.
So then I went the Odin/flash stock firmware route. Unfortunately, despite two rounds of that, the Retail Mode application and restrictions remained. However, what did arise from this seemingly pointless process was the ability to enable installation of third party apps under Settings - all other admin access and functions (i.e. factory reset, program uninstallation, etc.) remained under the restricted control of Retail Mode. I went through that process about a year ago, assuming I had failed - the restrictions remained, and I was out of ideas/options.
Two days ago, I decided to revisit the problem, having to reeducate/remember what I had done previously along the way. Eventually, I came up with a novel workaround that hadn't occurred to me before - side-loading an apk file containing a different version of the Retail Mode software. Ironically, this worked. After installing and running the alternative Retail Mode app, using admin password 'blue' I was able to uninstall the original (i.e. problem) Retail Mode app, enable factory restore, and execute a complete wipe, which was successful.
I know this thread has been silent for a while, but it was one of only two threads that I thought took the larger conversation beyond the first basic step and I thought that contributing to it would be a small way to express my thanks.
Cheers.
---------- Post added at 04:56 PM ---------- Previous post was at 04:46 PM ----------
It now seems that others (SeriousEion) have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - it's very interesting to me that this thread only reactivated last month after having gone dark by the time I came across it in 2016.
---------- Post added at 05:08 PM ---------- Previous post was at 04:56 PM ----------
It now seems that others, namely mfb5150's post from 20-07-2017, have used the approach I mentioned above to successfully bypass Retail Mode in several of the most troublesome cases - I can confirm that the approach he outlines also works for the Samsung Galaxy Tab S2 (SM T810) using the apk files available from samsungretail.com
So thank you, mfb5150, for your post - had I seen it earlier you might have saved me an hour or two of trial and error. It's interesting to me that this thread has finally reactivated after having gone dark by the time I came across it back in 2016. I'm not a developer, and have no programming/coding experience, so I hope that this thread continues to be a resource for any others like me out there.
Click to expand...
Click to collapse
i just follow your instructions and awesome mine is unlock now and downloading the update to android 7.0 thanks bro
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse
dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:
Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.
Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.
I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.
I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.
After much messing and a headache I finally got to c432b370
And everything back to normal
tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk
Hi. So I decided it was time to move to EMUI 9 and after looking at various posts on here I believe the easiest way was to you EMUI Flasher to flash the ROM (coming from 8.1 rooted).
The phone restarted and went to EMUI installer but after 10% or so I got an error. It asked if I wanted to go to erecovery or reboot the device (I think). As far as I was concerned it was only checked that the ROM was OK and hadn't installed anything so I selected reboot. Now the phone won't come on. I've tried holding the power button for an inordinate period of time but it's not happening.
Is there anything I can do?
EDIT - I've tried a different USB port on my PC and can see something in the device manager now ---- Kedacom USB Device > Android Bootloader Interface ---- which gives me a sliver of hope this can be fixed.
EDIT2 - I could send img files through fastboot all day (phone was recognised even though it wouldn't turn on) but couldn't fix this. Gave DC Phoenix a try but no luck there either. Think I've killed it.
EDIT3 - Just in case anyone ever comes across this. I tried below but nothing would work so I contacted someone on Telegram who said the only option was to open the phone up and short it out. No way I was attempting that so I eventually contacted Huawei UK and told them it had died during an update, never let on that it was MY fault! Anyway, they sent out a prepaid envelope to send to a their repair partner. I won't name them here but they have terrible reviews on Yelp so I was a bit apprehensive. I know the phone arrived with them last Friday as I checked the post tracking but I never heard anything from them. Today out of the blue my phone has come back to me in full working order, repaired under warranty! Considering there was only one thing I was really using root for and it was only a slight convenience, I think I'll just leave it as is.
Are you able to flash anything in fastboot?
Are you able to boot to recovery via fastboot? Disconnect the cable after you give the reboot recovery command in fastboot.
You may be able to flash each component of emui, system, vendor, oeminfo, kernel etc. Seems that it's missing most or all of it.
Bootloader sounds like it's intact.
Btw. The easiest way to update to emui would be to wait for an OTA from Huawei.
Personally I don't see a point, pie is not as efficient as Oreo nor does it have any features to merit an upgrade, in fact you would lose features (4k zooming, functional TWRP)
Hey,
I purchased a Samsung Note 8 (SM-N950F) a couple of years from Amazon.de. The phone was unlocked, since then new OS releases were really slow so I decided to download the Pie update from Sammobile and updated my phone via Odin. The phone is using official firmware and has never been rooted yet when I try to activate Google Pay I receive the following error; "Couldn't finish setup to pay in shop. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I spoke to Samsung and told me to check a few things and they confirmed the phone is not rooted, I spoke to Google and they told me I should ask Samsung how to unlock the bootloader but Samsung said doing this would void my warranty. I'm a bit confused as to what to do, is there a stock pie rom I can use without voiding my warranty?
Thanks a lot, appreciate any help
Regards
p4rma
The only thig i can think of is that, the phone you've got has a CSC code of a region where Google Pay is not supported, or maybe you are living in a country that do not support Google Pay.
If you think I'm wrong, flash stock pie firmware.
Flashing stock offiicial binaries doesn't need your bootloader to be unlocked.
Thanks for the quick reply I will try this. Would Samsung have their own stock pie rom? Kinda wish I just waited for the pie update rather than flashing. Its annoying I can't use Netflix either as it says my device is not compatible.
I just checked and my bootloader is N950FXXU7DSJ1
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Unix_Dominator said:
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Click to expand...
Click to collapse
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
p4rma said:
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
Click to expand...
Click to collapse
I'm glad it worked out for you too!!!
Unix_Dominator said:
I'm glad it worked out for you too!!!
Click to expand...
Click to collapse
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
p4rma said:
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
Click to expand...
Click to collapse
It has been permanently fixed for me, I never faced any issue with GPay after that method (I don't use Netflix though). Could you also see if you phone is updated to the latest version, if so also check if your phone has a fix for Stagefright.
To check if you are vulnerable to that exploit download this app it will tell you Click Here . If it fails, try OEM unlock as off and see, might fix it.
I really hope this issue doesn't come back for you.
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.