Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
I rooted and installed custom recovery on my HDX7 using the HDX Toolkit according the the given instructions. After a few days I decided to uninstall recovery and moved the TWRP backup to external storage. I hadn't installed any custom roms or created any rom slots. I had no problems for days until these changes I made last night.
I uninstalled towelroot, reading that it was safe to do so. I installed a flashlight app. I installed Greenify and auto-hibernated some some third-party apps - including ES FileManager and Safestrap, which I considered safe since I had already uninstalled recovery. I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well. I also turned WIFI off before shutting down.
The device is now stuck at the second splash screen with the animated white and gold Kindle Fire logo. The screen is also slightly dimming and brightening repeatedly. I can't get into safe-mode/ recovery mode. I looked up what I was disabling but think I goofed using NoBloat and Greenify and screwed myself by uninstalling recovery.
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Segue2 said:
...
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Click to expand...
Click to collapse
Did you try hard reset? Press power button for more than 20 sec. Your kindle should then restart itself hopefully without bootloop. I was once messing with rooted stock fire OS trying to add one app to system apps (live wallpaper support I think), after restart I get neverending bootloop, but I was able to get out of this by doing hard reset, then Safestrap showed again and I was saved.
If you can manage reverse all your changes on system through adb, good for you, but without installed Safestrap ... well, maybe someone with better skills can manage you through this ...
I have tried but hard resets aren't working.
Can you still access it through ADB?
EncryptedCurse said:
Can you still access it through ADB?
Click to expand...
Click to collapse
No, looks like I am having trouble getting adb access. Command adb devices is returning nothing. Windows is recognizing the Kindle, however, but only as a portable device. Definitely had adb access before (established to use the HDX Toolkit). Now, I am wondering whether I disabled adb support on the kindle at some point beforehand.
On a sidenote, I just unplugged and reconnected the usb cable a few times and was able to hit the lockscreen for a few seconds before falling back into the bootloop. I have been able to repeat this.
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Segue2 said:
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Click to expand...
Click to collapse
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
EncryptedCurse said:
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
Click to expand...
Click to collapse
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
jimyv said:
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
Click to expand...
Click to collapse
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Segue2 said:
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Click to expand...
Click to collapse
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
jimyv said:
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread and that you till the thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
Click to expand...
Click to collapse
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
lol
Segue2 said:
I will try fresh installs on Windows again, then. I did read and interested tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Click to expand...
Click to collapse
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
Segue2 said:
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
Click to expand...
Click to collapse
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
jimyv said:
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
Click to expand...
Click to collapse
Ok, good to know about the power.
Yes, I have used the Minimal Adb and Fastboot utility before and couldn't get access.
I can get into stock recovery for a factory reset.
I can not get into SafeMode. It ends up booting to the lockscreen for a second or two before falling back into bootloop - sometimes flashing the lockscreen again.
okay well I do believe you have run out of options..in a nutshell you are looking at a replacement device anyway so you should be on the go for a factory reset
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
by
Segue2 said:
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
Click to expand...
Click to collapse
nope you are out of options before you got to the factory reset.apparently something was done to the system that nobody knew about. Or there is a hardware problem anyway.you can try to hold the power for over 20 seconds or another factory reset but sounds like you need to give Amazon a call anyway you might have had a bad unit. Because nothing you described in above paragraphs should have gotten you to this point.
Segue2 said:
... I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well.
Click to expand...
Click to collapse
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
jeryll said:
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
Click to expand...
Click to collapse
the loop he was in would not allow him ADB either ,something was done here other than what has been stated whether it was known or not.
correction I also use greenify it on all my devices. And to be able to do anything to system you must have had exposed framework installed....in which case I would have never have recommended a factory wipe. as stated several times already. simply hibernating a few apps even hibernating a few apps ( which is about all you can do without framework) would have not gotten him here. he had to have permanently removed something from system or permanently disabled iteither way without knowing exactlywhat service he appy that too it would be a guessing game even with adb.in short like you said lesson learned for another person that bothers to read this thread not to tamper with your stock system without safestrap at bare minimum and a backup
I wonder if he has had any luck with ADB now that he is no longer in a perpetual boot loop. May be able to come up with a reenable command for system apps? Su should still be in systemat least the binaries will be in case the app wasn't. And I think in this case it would be better if the app was not in system but the binaries remained since he cannot get into the OS he will not be able to grant permission..but without. su command should work still
Thanks for the input. Wiithout a doubt, lessons learned here. At the very least, I never should have uninstalled Safestrap even if I wasn't planning on doing anything else to the system. I have the TWRP backup of my rooted stock, but with no way to use it now - useless.
I must have disabled some critical app or combination of apps that lead to the conflict, despite the care I thought I was taking. As far as Xposed framework goes, I never installed it manually. Maybe it is packaged in with one of those apps? The other thing I wondered about was whether disabling wireless could have led to a conflict. Using the Toolkit has been reported to lead to a bug where the system can crash when trying to enable wifi without first enabling bluetooth.
Either way, all I had to do was leave safestrap alone, just in case. F.
All of your help and feedback has been appreciated!
Wow. Well, I have adb access. After mutliple unsuccessful attempts on Windows and Linux, I was able to fire up an old MacBook and established an adb connection in 10 minutes. Unbelievable! The list of installed packages doesn't show any third party packages. Can I push and install Safestrap through adb to get my backups up and running? Whar is the correct syntax for those commands? I have already got a replacement on the way, but I would like to try to bring this one back and unroot. On second thought, maybe I should just leave it?
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
5. The stock rom my phone has is based on Android 8.1 (8.1.0 OPM1.171019.011) to be exact, for rom version refer to reply. I've tried different versions of gcam, but none of 'em has worked for me. Normal camera app works fine, nothing I've encountered yet.
These are the versions I've tried -
* F1v9.5_6.2.030.apk (Couldn't install as 6.2 is only supported by android pie)
* MGC_6.1.021_XCAMBase_F1_v5a.apk (Installed and worked, details below)
* MGC_6.1.021_Potter_v7.1_san1ty.apk (Installed, didn't open)
* MGC_6.1.021_Potter_v7_san1ty.apk (Installed, didn't open)
On photo, the camera lags like I'm playing a game at 2-3 fps, same for other photo related options. Except for panaroma, photo sphere, lens blur, these I didin't had problem with. Except panaroma pic never showed up in camera app or gallery. In video it doesn't lag, so recording normal video was fine. But when I recorded a slo mo video, it lagged after the recording, inside & out the camera app. Inside gcam the audio was fine but outside it was muffled. By outside I mean gallery app & vlc player.
I may try other versions but each app is so big.
Gurkirat_Singh said:
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
Click to expand...
Click to collapse
sir, you never mention which version you are on ? since Boot is locked so definately MIUI but which one? global/beta/Eu/ Stable/chine etc?
anways..
Answer for 1, - No you have to redownload it, the Fastboot Rom consist of few extra files like persist and recovery and if they are update you must use the latest one. however via twrp you can take system/data/ and other partitions backup if you want...
for 2. after 72hours, goto dev option and try enabling oemunlock, it will give you warning but do it, come out of dev option and go in and do it again, repeat until the UNLOCK setting stays on UNLOCK, (don't know why it is, but this is how it is,,,, ) , later verify your miui account and sim, keep signed in. download unlocker and sign- in and try unlocking the device (make sure all qualcom drivers are installed)
for 2 again, This is very strange, ONE OF ITS KIND error I AM hearing , I honestly thought this bug is ONLY custom rom related! , you see Poco f1, Beryllium uses MODIFIED VENDOR IMAGE ( can be found at) https://mirror.akhilnarang.me/MIUI/beryllium/.
now these modified vendor images by MIUI dumps logs on data/data/netstat (specially if you are USB TETHERING on 3g, ... you will start suddent System UI reboots and some com.android.xyz processes crashing errors and if you toggle Airplone mode 3g/4g or usb tethering from quick setting , device either hung or system ui restarts or device reboots.
now this error is always in all custom roms due to vendor image
solution? DELETE all files from data/data/netstat and reboot (rooted device on custom rom)
for locked device (unrooted) you may have to flash updated version of miui to fix this bug!
Once you unlock device take latest vendor image ( i am using 9.6.27.9-0 , it has better battery life) and flash custom rom...
for 2 again,,,, some users are complaing that miui10.3.6 alters fastboot commands! and twrp no longer works! , make sure you don't flash miui10.3.6,
for no3,, i don't use facial unlock feature, i will study more and will get back to u if relevent.
for 4
Open MIUI Security App.
Tap on Data Usage Tool.
Tap on Restrict Data Usage.
Now find out those data hunger apps and restrict them by tapping on the green tick.
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Gurkirat_Singh said:
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Click to expand...
Click to collapse
sir Gurkirat_Singh
1. sir you are on Miui9.6 which is based on oreo.I have personally updated till 10.0.03 and have all the fastboot command working fine.
you may download miui9.6.22 (a bit updated version from what you are currently on) from
http://en.miui.com/thread-3995650-1-1.html ( both Recovery (1.6gb) & Fb rom (2.5gb) as backup.
2. under Developer options , poco f1 has this trick that OEM UNLOCK doesnt stick on UNLOCK and keeps coming to default once after you exit Developer option. on my 5th attempt it finally stick to UNLOCK and i was able to unlock the device from unlocker Tool.
3. I havent removed my poco sticker from back (yet), put 9h class, bought extra skin my self and book cover too so yes I second that. I always protect my devices like part of me , even the retired ones are sleeping in boxes with proper covers and unused accories!,
now, update your rom and try again to toggle 3g/4g usb tethering. 99% chances are its software issue! and i have faced this issue many times and its my 5th month with device so i havent noticed any hardware damage or performance / speed problems yet... so don't worry. YES few kernels affect network connectivity, however I am on Optimus Drunk kernel on Havoc 2.8 and its working like a charm!
-about file manager issue, can you try the same with FX File Explorer? and report back plz
4.if you restrict globally then miui will only allow system apps to use data in background as and when needed. MIUI won't allow facebook/whatsapp and other VOIP callers to work in the background. Once in restricted mode on miui9 on RN5pro, I used to miss call on whatsapp unless i wake the device up and notifications starts appearing that i have many whatsapp miss calls!, this feature went even worse on rn5pro when i was on dual sim, miui use to prefer carier sim over data sim always! so yes miui has strict data usage control.
5. i am unable to find 5th question plz help
few screen shots of my poco f1 on HAVOC2.8 / OD kernel build20190820 / magisk19.3 / gapps nano
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Gurkirat_Singh said:
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Click to expand...
Click to collapse
sir
1. I never read any such method so far where you can reverse engineer the extracted files in partitions and pack them back as fastboot rom. and to think of it thats almost impossible because stockroms usually comes with digitally signed by vendors ensuring no foul play.
2. once your 72hrs over, just unlock the oem unlock switch from Dev option, verify sim of on your mi account, download the unlock tool, login using same mi account, hit unlock, after success, the device will BOOT on POCO logo and "UNLOCKED" will start appearing (always) and all data partition, internal storage will be wiped! so make sure you take backup!
2a. with me on custom rom it wasn't a sure thing but it used to happend randomly when least expected.
5. on oreo , GCAM version came in sep2016 worked for me and later ones are for pie and kept crashing (please check old version on apkmirror)
@YasuHamed Thanks for all the help.
5. I did found a version that is working fine for now. But the features I was interested in was super res zoom, night mode, slo mo etc. Super rez wasn't that impressive(seemed similar to stock zoom), night mode either, slo mo still doesn't work properly and phone heats up, even when I'm not using too old of a version of gcam. Even the stock cam app took some good shots with zooming.
And if those features will work better with pie version then IDK what to say cause that new version would come with better stock cam having slo mo, night mode and all that shiz if not everything. So I'm kinda thinking is this gcam port really relevant? It drastically changed image quality with my RN3 but I don't see that now.
Edit: Also I wanted to say that my phone was working fine now i.e. no reboots after closing mobile data or wifi or switching. But you know what they say don't celebrate too soon. As soon as I used usb tethering the problem arised again, I wasn't able to it for 2 days as my PC wasn't booting. Same reason why I wasn't able to reply to you earlier.
Not only this, this whole bugged situation has started to irritate me a lot. Just today I was trying to run flash on my android. And even on the supported browser, it just wouldn't show up. I really hope after I unlock this device, all of these bugs would go away after the data gets deleted, or I'm gonna be more disappointed.
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Gurkirat_Singh said:
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Click to expand...
Click to collapse
please consider upgrading to MIUI10.3.x , download the complete recovery rom and name it as update.zip and put it in download folder and open updater and call the rom from there , and flash it, I suggest CLEAN FLASHING so all the data will be deleted!
plz take backup!
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Gurkirat_Singh said:
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Click to expand...
Click to collapse
frankly i never used my poco on miui either on 9 nor on 10 ,
the day I got, I placed unlock request and after 3-4 days, I unlocked my device and put it on HAVOC and since then my experience is based on custom roms but i did flash miui 10 in between just to have a taste of it! and came back to havoc in a day or two, hence i never deeply tested these feature.
however I do know that modified vendore have created usb tethering problems throughout devices
https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Gurkirat_Singh said:
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Click to expand...
Click to collapse
-sir, most of your observations are pertaining to V9.6.14.0.OEJMIFD, where I am not on MIUI hence I will wait for other members to step in and share their views about them.
- you can always use "Disable-Force-Encryption-Treble" from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389, when flashing rom (clean flash, FORMAT DATA) to disable encryption on kernel level.
- since Twrp official doesnt support OTA so if you call recovery from updater, it wont work! you may have to use Orange Fox (oct/nov2018) version which had OTA support or better flash full rom after downloading desired version from https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
- what are you looking is from different world of android devices, such as TEMP ROOT, IVORY ROOT (sony xperia on android 5.1) days only! when nothing used to be changed but just to gain access of certain partition temporarily, temp root techniques used to apply to extract DRM KEYS. ITs not the case here hence you will have to root your device properly!
- about gpu, i never tried but you can used app such as FK kernel manage or Kernel Auditor to play with your GPU accordingly
- twrp usually ask keep system readonly whenever flashed new room its standard warning to avoid any bootloops since Twrp doesn't know you will be flashing kernel and/or disabling dm varity soon. so it warns you.
- don't worry POCO is FREE from ARB4 $hit so when page said ROLLED BACK, it means those version were recalled back for some buggs and an update released soon after!
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
please view my replies sir
Gurkirat_Singh said:
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
I flashed "DisableForceEncryption_Treble_v18.0.zip" and it worked/works, but I always flash before magisk., the current version is Magisk19.3 hence I recomend you to use the updated version, 16.7 is obsolete long back. However if 19.3 may give you bootloops then the max you can go back is Magisk18.0 (since after 18.1, Magisk started using different Script language unknown to some recoveries. However if BOTH (your recovery and Magisk are latest, it should work just fine
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
once on RN5p I tried updating OTA via twrp, it never booted to update hence I recomend you to download full recovery rom 1.8gb, of the build you want and flash it via twrp
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
plz try any root checker and see
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
fk kernel manager or kernel Auditor does support editing build prop, apart from many tweaks for GPU and Cores. the video shows a simple edit in order to think your device is some other version of Galaxy to trick samsung app ; however The boy didn't explain why he just didn't install the already downloaded apk file from fortnite website ?
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
if you are flashing MIUI From twrp, and DON"T wana ROOT then yes you should never allow system modification because then device will never boot in to system due to DM-Verity. However if you are rooting yoru device, try reading Magisk Lines, It always patch fstab and disable Dm-verity, once its disabled /system parition permision wont be verified on boot. So when you boot in to twrp and you know you are going to flash Magisk, you can ALLOW SYSTEM MODIFICATION swip
on Custom Roms it doesn't matter, because twrp never ask such question. "allow system modification" is only limited to StockRoms
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
the next version above ROLLED BACK one is the bug fixed. (now i don't know what exactly were they) . Also MIUI forums for devices always announce updates! you can google
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
well probably this is the bug of this version 9.6.14 hence you should upgrade atleast to 9.6.20 in order to compare
Click to expand...
Click to collapse
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
6. Again you didn't tell me how'd you find those roms!?
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
Sorry for the late reply, got a little busy.
sir ..........................
Gurkirat_Singh said:
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
1- Yes I flashed DFET before Magisk19.3 - and why i didn't use the third file, i remember in post one user confirmed this particular one working for him (atleast) so i downloaded that one.
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
2- ideally this is the case with recoveries which doesn't support OTA, OrangeFox based on OLD version of TWRP does support OTA , I NEVER TRIED but worth reading the post. you should find it in the Poco Development section
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
3- I use THIS ONE
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
4- To get general IDEA about altering Build.Prop, The video is Good! however you can not assume Samsung Modded Android over MIUI's one! also It seems the boy in the video has Android7 where Miui Poco is atleast on 8.1, there is huge difference!
The only way to find out whether any type of build.prop (EVEN ON CUSTOM ROMS) will WORK or NOT on POCO; is to Try and find out yourself.
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
5- Once twrp changes the /System as writable, cannot be undone from Twrp itself - since you have magisk16.7 as you mention earlier the dm-varity is turned off and you are booting normally.
-unlocking means, your device can accept fastboot commands to Alter various Partitions developed by Third Party! /recovery /system /vendor /oem etc
-Rooting is Gaining /system access in Android OS to perform Forbiddon and/or Unsafe Commands / Apps etc
- now your question about security , i will simply say! its HIGHLY UNSECURE to unlock your device & Root it!, there is debate about SeLinux Permissions to be Permissive or Enforcing , SELinux in enforcing mode is considered to be little better and secure but Permissive mode means any command can be run even by hacker to gain your /system access ! REFERENCE
- unlocked bootloader is also very unsafe! anyone can just flash any compatable recovery and atleast WIPE your data!
HENCE this is what i say to all my fellow friends and mates in general! if you are CONCERN security privacy , NEVER ROOT your device! or keep two devices, one being as family device! for fotos, emails contacts etc! and play with the other!
- about warranty! every region has different rules! my country's Xiaomi centre doesn't cover any brick devices because here they are alreadly selling many Redmi fones on UNLOCKED mode! directly from china!
6. Again you didn't tell me how'd you find those roms!?
https://c.mi.com/oc/miuidownload/index select poco and see officially available rom
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
EDL ? you mean fastboot rom flashing via miflasher!, thats not edl! to trigger EDL you must have
1. authorized Xiaomi Account
2. back panel of poco to be opened and short test point to put device in EDL
Sorry for the late reply, got a little busy.
Click to expand...
Click to collapse
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
................................................................................................................................................................................
Gurkirat_Singh said:
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
we i am glad , we have a winner here
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
Temporarily , LOS is suspended but even unofficial roms till mid August are very stable ! you should try! , hoever Pixel is very popular too, on deeper level what diferences you may find thats only user can discover over time. there is no direct answer to this question! LOS is driven from CynogenMod which was on AOSP wehre Pixel is CAF based, so the difference comes on Kernel Level this means CAF rom may have different Hardware performance / behaviour when compare to AOSP based roms (and vice versa). I am not sure about multirom as a daily driver, yes I would like to try for fun but wont keep it.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
on Poco i have tried Nitrogen, Omni, MoKee, BootLeggers, CrDroid, LOS and Havoc..
BootLeggers is pretty stable rom! however CrDroid is outstanding because the developer @gwolfu is more active and releases many updates (sometimes 3-4 in a month). Crdroid has serious level of customization (dirtyUnicorn) and you can change the look of your rom in every possible way you imagine!
so the question is WHY am I on Havoc, well the simple answer is both Crdoid and Havoc Offers serious level of DU customization & variations found on deeper level. some items which crdroid doesn't offer i found in Havoc so I stick to it, moreoever I feel the font and resolution by default in havoc is next to pixel where in Crdoid you manualy have to fix (dpi and font)
now I am on havoc2.8 but I am using Optimus Drunk Kernel (which is also used by CRDROID) - the developer of havoc2.8 offers SHADOW kernel which as I said I feel is not very battery effcient (atleast for me, others can disagree)
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
-keeping system Read only OR swipe to allow /system as writable is on Recovery Level ,
- when you keep system on READY ONLY on recovery Level and later flash magisk, the module magisk modify the /system permission which twrp doesn't know!
-if you "allow system modification on twrp level the /system is now set on writable permission by twrp, and magisk is a module which is always set to alter /system partition permission irespective of Global policy on recovery level
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
now this let me think a little bit, the only possible explaination (in theory) I found is
- when you flash all or clean flash all, its not necessary that /recovery partition is first erased by miflasher! and recovery.img file has many folders including setting folder! so miflasher and later by you simply there was swaping of recoveries, the Tree was always there! when you reflashed twrp! try to do this way
Code:
fastboot erase recovery
fastboot flash twrp.img
this should erase any previous left over data and settings
try and let me know!
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
i simply google / web search rom number with device name with code name like Miui9.6.20 fastboot download poco f1 beryllium and google suggest few popular results which usually works for me!
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
I would say 9.6.14 had bug so reflashing didnt help! as I said before, consider upgrading atleast to 9.6.20
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
till MiMax
-holding THREE buttons for 30 seconds used to trigger edl mode
-miflasher simply identify EDL mode and used to flash the beryllium fastboot rom
the question is why they stopped?
well fastboot rom when extracted, hackers can simply alter and repack the img files! YOU CAN EVEN place twrp as "recovery.img" in extracted folder miui will flash twrp thinking its vendor recovery! and the device in EDL mode will accept it..
this was serious security risk! so they capped EDL mode in both ends
- miuiflasher needs AUTHORISED ACCOUNT
- DEVICE won't enter in edl mode unless you remove back cover and under batter wire you short two motherboard points with thin wire or tweaser! (and immediately connect usb calbe to system)
now what can you do?
1. use older version of Miflasher which doesnt verify rom
2. user altered rom of specific build or time to WAKE UP your BRICKED device!
I have never done it so you need to investigate and use your poco as gunie pig to test these methods after REMOVING Back Panel (HIGHLY NOT RECOMENDED
or take device to authorised Mi Dealer and let them EDL for you!
Click to expand...
Click to collapse