Database Develop

Easy Root Toolkit Not Working

Im trying to root my phone, its an Xperia Z from tele2 in sweden, C6603, android version 4.1.2, version 1.0.11.a.1.253, when im on this part of the tutorial it won't work, it doesn't do anything when im entering display on service test, just flashes some colors, so can you try to help me? im on part 9 but nothing happens when i press the power button to power down the screen many times, i used droidviews.com as the guide, for the toolkit, please help me, i have tried everything possible, changing to msc mode didn't work either
7. You will see the Service Menu of your phone, select “Service tests” from the available options.
8. Now select “Display” (screen will turn white), the toolkit will now start executing some commands.
9. Now press the Power button to turn off the screen, wait for few seconds and press the Power button again in continuation till you hear a beep sound. Keep observing the command prompt for outputs.
10. Then you will see “transfer files to your phone part2“, “installing busybox,su,Superuser,etc…“.
11. Finally, you will see “Cleaning up“ on the screen and then the phone will reboot automatically and when it boots, it should be rooted.
im a complete newbie with rooting, fine, i rooted my old galaxy 5, gt-i5500 using some app named one click root, and another app named z4 root also worked, please help me out here, bootloader is unlocked, according to the service test thing, but it still won't root my phone

That isn't for 253, ready the stickys for the latest methods.

XperienceD said:
That isn't for 253, ready the stickys for the latest methods.
Click to expand...
Click to collapse
which ones? as i said, im completely new to rooting

Serathas said:
which ones? as i said, im completely new to rooting
Click to expand...
Click to collapse
You're not new to reading though are you. General section, start at top, READ thread titles, find appropriate thread, READ it, watch a video even, done.

watch?v=sXbsgYVuRZU im using this video guide on the binary root toolkit (doomlord v4 root) its saying it can't complete cause the file system is set to read only

img35.imageshack.us/img35/2018/rootzd.jpg

Serathas said:
img35.imageshack.us/img35/2018/rootzd.jpg
Click to expand...
Click to collapse
Since you can read and did follow the instructions but it still isn't working, your phone is probably broken.

im trying my best here to fix it, buy its still saying the phone is set to read only or something and i have looked everywhere for how to remove a read only partition from a phone and repartition it to still work, but also become writeable
Oh, and i bought my phone less than a month ago, so i don't think its broken

Spy on Wife - Bypass Pin with Demo code?

http://forum.xda-developers.com/showthread.php?p=40782218
In the above thread, does this method work with the stock sony Xperia T firmwares
please can you post your firmware version (stock only, no cm, no aokp or custom roms) and let me know
if it worked.
Basically I want to access my wifes phone and check her messages as she has been acting weird
I tried the service menu trick on her phone but it didn't work which means her phone has more up to date firmware i believe
EDIT found this
http://forum.xda-developers.com/showthread.php?t=2244741
Can someone confirm it works on xperia T?

owen1978 said:
http://forum.xda-developers.com/showthread.php?p=40782218
In the above thread, does this method work with the stock sony Xperia T firmwares
please can you post your firmware version (stock only, no cm, no aokp or custom roms) and let me know
if it worked.
Basically I want to access my wifes phone and check her messages as she has been acting weird
I tried the service menu trick on her phone but it didn't work which means her phone has more up to date firmware i believe
Can someone confirm it works on xperia T?
Click to expand...
Click to collapse
Just tried that for you, it didn't work; the Emergency dial screen wouldn't accept the *#*#73556673#*#* code.
The lock screen WAS disabled whilst the Demo was active but as pressing the power button to wake the screen was immediately rerunning the Demo I'm sure that would get noticed. (Xperia T firmware 9.1.A.1.141).
Might have time to test out the 2nd link you posted later.

BarneyJ said:
Just tried that for you, it didn't work; the Emergency dial screen wouldn't accept the *#*#73556673#*#* code.
The lock screen WAS disabled whilst the Demo was active but as pressing the power button to wake the screen was immediately rerunning the Demo I'm sure that would get noticed. (Xperia T firmware 9.1.A.1.141).
Might have time to test out the 2nd link you posted later.
Click to expand...
Click to collapse
1) Did the demo run?
2) Did you then press home button to go to the home screen?
3) Did you then bring up dialer and type in the demo code again to disable the demo?
http://www.youtube.com/watch?v=gRelLSb0vgw&feature=youtu.be
In the video when the demo is running he taps it to bring up the home button, did this work on yours?
Thanks v much

owen1978 said:
1) Did the demo run?
2) Did you then press home button to go to the home screen?
3) Did you then bring up dialer and type in the demo code again to disable the demo?
http://www.youtube.com/watch?v=gRelLSb0vgw&feature=youtu.be
In the video when the demo is running he taps it to bring up the home button, did this work on yours?
Thanks v much
Click to expand...
Click to collapse
1) The Demo ran when the phone was already unlocked and I typed in the code from the dialer - on first run it even prompts you that it will change the screen unlock password.
2) Yes pressing the home button went to the Home screen (at this point if you switch the screen off then back on the Demo reruns).
3) Yes I did.
The code doesn't seem to work at the Emergency Call screen on my Xperia T, or perhaps the phone he's using in the Video doesn't have the most current firmware.

BarneyJ said:
1) The Demo ran when the phone was already unlocked and I typed in the code from the dialer - on first run it even prompts you that it will change the screen unlock password.
2) Yes pressing the home button went to the Home screen (at this point if you switch the screen off then back on the Demo reruns).
3) Yes I did.
The code doesn't seem to work at the Emergency Call screen on my Xperia T, or perhaps the phone he's using in the Video doesn't have the most current firmware.
Click to expand...
Click to collapse
It is possible you can test the zip file method?

I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.

BarneyJ said:
I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.
Click to expand...
Click to collapse
ahh ok, neither does her phone so that wont work.... never mind thanks for your help

Had a thought what if I flash an older version of firmware which has the service menu security hole?
Would just have simply plug her phone in, flash it, and then let it restart (wiping only cache and dalvik, if they are available in stock recovery)
So she won't lose any of her data and won't be any wiser?
hmmm....

BarneyJ said:
I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.
Click to expand...
Click to collapse
Ahh was reading too quickly method b doesnt require CWM... ok, if you can give this a try and get back to me it would be much appreciated

owen1978 said:
EDIT found this
http://forum.xda-developers.com/showthread.php?t=2244741
Can someone confirm it works on xperia T?
Click to expand...
Click to collapse
I've tested a similar method on windows that worked on my T on JB.
all it needed was a
adb shell
su
rm /data/system/gesture.key
Click to expand...
Click to collapse
This of course has limitations, the device needs to be rooted and usb debugging must be enabled

owen1978 said:
Ahh was reading too quickly method b doesnt require CWM... ok, if you can give this a try and get back to me it would be much appreciated
Click to expand...
Click to collapse
matt4321 said:
I've tested a similar method on windows that worked on my T on JB.
all it needed was a
adb shell
su
rm /data/system/gesture.key
Click to expand...
Click to collapse
This of course has limitations, the device needs to be rooted and usb debugging must be enabled
Click to expand...
Click to collapse
Well I suspected that USB debugging would need to be enabled to use the B Method in that thread you linked and what Matt has said Tally's with this; I've now had time to try and can confirm this.
Matt's commands worked when I substituted 'password.key' instead of 'gesture.key' in the 3rd line (I had a PIN lock set) - 'gesture.key' seems to be for when a pattern lock is set, and 'password.key' for PIN lock.
Method B in that thread is missing the 'su' line that Matt has above, so failed with 'Permission Denied' when trying to delete the .key files - works once you add the su command.

MIUI Global 7.2.4.0.0 uses A LOT of RAM. (?)

Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.

proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0

Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!

androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.

i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..

7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working

Can't update my ROG Phone II

Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!

HyphenZzX said:
Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293

reg66 said:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293
Click to expand...
Click to collapse
but i don't understand i am already on ww fingerprint???

HyphenZzX said:
but i don't understand i am already on ww fingerprint???
Click to expand...
Click to collapse
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck

reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
hi thank you for the response when i open flash thing it just opens the cmd and closes again? what do i do?
edit never mind its doing it now thanks!

reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
thank you so much it works now quick question can i do manual updates now and get the latest firmware?

HyphenZzX said:
thank you so much it works now quick question can i do manual updates now and get the latest firmware?
Click to expand...
Click to collapse
Well, up until 1910.44, we were able to just download the updates from asus and put them in the root of internal storage... But this changed for many users with the .44 update, so I'm not sure... We'll have to see how the next update goes, but yeah, it'll either be through download of ota or by flashing raw rom... Either way it'll be posted here by someone. Won't be long to wait as China versions already have update .52 update, WW comes shortly after

Hi there I am in a similar situation with a tencent rog 2 purchased on ebay that is on android 9 WW version. Is it possible to flash WW_ZS660KL_17.0240.2107.100_M3.23.44.20-ASUS_1.1.232_Phone-user.raw to get to android 10 immediately? I have attempted it just now but it appears the flashall_AFT.cmd is stuck and i have waited around 20 minutes.
edit: I waited an hour and nothing seemed to happen. so I restarted the phone and it seems like nothing happened at all. Any ideas?

edit: accidental double post

Flicking Lock Screen after update to latest Android 11 OTA update

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.