Related
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
soccerplayer00321 said:
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
Click to expand...
Click to collapse
Do you have an unlocked bootloader (root)? You could try reflashing twrp with odin to get recovery back.
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
soccerplayer00321 said:
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
Click to expand...
Click to collapse
If you don't want to root, you could try flashing the cpd1 firmware with odin and that should overwrite what might be throwing off your battery calibration. Unless it's a hardware problem that is. Are you comfortable using odin? Also if you have no interest in rooting, you could flash the most recent firmware.
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
soccerplayer00321 said:
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
Click to expand...
Click to collapse
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
kevintm78 said:
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
Click to expand...
Click to collapse
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
soccerplayer00321 said:
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
Click to expand...
Click to collapse
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Sent from my SM-N910V using XDA-Developers mobile app
kevintm78 said:
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Click to expand...
Click to collapse
No luck on Kingroot. It usually dies around 25% or so. Sometimes a little before that and sometimes after that. It never even got into the 35% range.
What I think I am going to do is go back to kitkat, original samsung rom. Try Kingoroot and see if that works. If not, I will push lolipop to it and try kingoroot again. If that doesn't work, I will try to push Marshmallow to it and try one more time. Hopefully one of them will be successful.
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
fastjohnson said:
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
Click to expand...
Click to collapse
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
kevintm78 said:
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
Click to expand...
Click to collapse
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
fastjohnson said:
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
Click to expand...
Click to collapse
It may not make a difference, but there is a newer version of Odin here that you could try.
kevintm78 said:
It may not make a difference, but there is a newer version of Odin here that you could try.
Click to expand...
Click to collapse
I'll give it a shot, right now I'm a Lil burned out on trying this because my other phone LG g4 is boot looped for no reason so I'm down to just my N4 and my N3 my gf has it. I forsee a big cup of coffee at 3am and let the flashing begin. Oh FYI I did try I think Odin 3.10 version it failed quicker so I'll try this version in the morning. I appreciate your help very much you'll be the 1st to know if it pushes through. Merry Christmas btw.
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
fz798 said:
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
Click to expand...
Click to collapse
Reflashed and thought the wakelocks were gone, but not so. msm_hsic_host appears to be related to cellular.
flyers00 said:
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Click to expand...
Click to collapse
What I've noticed with this bootloader unlock is, like right now I'm 5.1.1 and my bootloader is unlocked but not rooted. OK if I use the the no A boot 6.0.1 file to flash mm it's stay unlocked and you can be rooted but if you use the normal full firmware 6.0.1 cpd1 file you lose your unlocked BL and back to start. Normally you unlock a BL it's stays unlocked no matter what you do. OK bugs with the no A boot 6.0.1 mm file no WiFi that's it. I really dislike 5.1.1 it sucks so there's not a lot of choices here. Good work on this exploit though.
So I have a rooted BND-L24 that I uninstalled a couple of system apps from, including the Huawei Home app. My question is: if I could track down an apk of the Home app, is there any reason I couldn't just reinstall it as a system app?
I've tried doing this already and the app shows up as installed, but when I try to select it as my launcher it doesn't work. So I'm not sure if I just installed a version that isn't meant specifically for my phone, or if there's no way to really reverse what I did and I'll just have to wait until firmware is released. Any info is appreciated.
Answered..
mjtschmid said:
So I have a rooted BND-L24 that I uninstalled a couple of system apps from, including the Huawei Home app. My question is: if I could track down an apk of the Home app, is there any reason I couldn't just reinstall it as a system app?
I've tried doing this already and the app shows up as installed, but when I try to select it as my launcher it doesn't work. So I'm not sure if I just installed a version that isn't meant specifically for my phone, or if there's no way to really reverse what I did and I'll just have to wait until firmware is released. Any info is appreciated.
Click to expand...
Click to collapse
IMO.. you've just answered your own question.
I'm at a loss as to why so many have rooted.. and there is no firmware yet available.. And, with all the updates that are coming.. backdoor bootloaders have to be sealed shut to open the front door.. and the Signed updates walk into a device to be installed.. (at least on the 1st days of the EMUI 8.0 / Oreo 8.0 rollout.)
I'm sure someone will make them available for a sideload in time..
RaiderWill said:
IMO.. you've just answered your own question.
I'm at a loss as to why so many have rooted.. and there is no firmware yet available.. And, with all the updates that are coming.. backdoor bootloaders have to be sealed shut to open the front door.. and the Signed updates walk into a device to be installed.. (at least on the 1st days of the EMUI 8.0 / Oreo 8.0 rollout.)
I'm sure someone will make them available for a sideload in time..
Click to expand...
Click to collapse
I'm pretty new to rooting, and it didn't even occur to me when I did it that I wouldn't have a stock image to reflash in case anything went wrong. In retrospect it was obviously a dumb idea. But oh well, I think of it all as a learning experience. I'll do my homework next time.
Anyways, my phone is still 98% functional at this point, just has one or two weird quirks from what I did, so I'm fine waiting it out. Thanks for the response!
No Problem Sir..
mjtschmid said:
I'm pretty new to rooting, and it didn't even occur to me when I did it that I wouldn't have a stock image to reflash in case anything went wrong. In retrospect it was obviously a dumb idea. But oh well, I think of it all as a learning experience. I'll do my homework next time.
Anyways, my phone is still 98% functional at this point, just has one or two weird quirks from what I did, so I'm fine waiting it out. Thanks for the response!
Click to expand...
Click to collapse
You're Quite Welcome Sir.
Don't feel bad... many rooted.. and all it means is... those of you that did, can only hope Huawei releases a Stock N Image that can be flashed prior to the rest of us receiving the Facial Unlock, EMUI 8.0 / Oreo 8.0 updates.. ( Not to mention Project Treble ) so they can receive them along with us.. or, someone or some app may allow them to sucessfully install the updates through a sideload.
There is nothing wrong with N running on the 7X... I Love my phone..
But I know that updates are going to be really, really cool as well !
The last time I rooted a phone was with a GS3 to install CyanogenMod. I've recently picked up a Pixel 2 XL, and I had some fairly noob-esque questions:
1. Do I have to wipe my phone to root it? That is, there is no "in-place" rooting?
1a. Are there any good methods to make a full backup *without* root before rooting it, and then restore it after I root?
2. Does rooting my phone make future OS updates more difficult/impossible? Ie: Will I still get OS updates, or will I have unroot my phone to get updates, then reroot it, possibly wiping everything?
3. What's the best method to go about doing this now? Googling around, and looking around here, I see a few different, but similar methods. I also see references to a "critical unlock," but no matter how many guides I read, I don't understand it. I'm starting to feel like I don't understand enough anymore to root my phone :-/
I really want to just be able to get back hosts-file based ad blocking again, and maybe a few other tweaks.
1, 1a: Go here and start reading, if you haven't already done so. To root requires unlocking the bootloader, which will cause the device to be wiped. It's best not to put anything important on the device until afterward.
2: OTAs must be applied manually. See the link I provided for instructions.
3: The P2XL is apparently unique in having two unlock commands. The non-critical unlock unlocks the bootloader while still providing some protection. The critical unlock strips all protections from the bootloader. To be on the safe side, execute both commands as mentioned in the link I provided.
Strephon Alkhalikoi said:
2: OTAs must be applied manually. See the link I provided for instructions.
Click to expand...
Click to collapse
Does that require re-wiping the device? Will I still get notified of updates, or will I have to keep track of new releases on my own?
The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.
Strephon Alkhalikoi said:
The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.
Click to expand...
Click to collapse
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.
LucentPhoenix said:
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.
Click to expand...
Click to collapse
Seems daunting. But read and ask till your comfortable. Lots of really helpful and Patient people on this lovely site. Stock + Root is the ish.
G
Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?
LucentPhoenix said:
Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?
Click to expand...
Click to collapse
Some have "dirty flashed" P over oreo with removing the -w flag from flash-all.bat script in the P factory image with mixed results. Your best bet is to clean flash the P build with fastboot to avoid any potential problems. However, yes, it will wipe your phone
Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?
LucentPhoenix said:
Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?
Click to expand...
Click to collapse
Yes you would be able to upgrade to the beta releases. However, you'd likely have to go back to Oreo, which would require a full wipe and clean flash, then upgrade to the betas. The first beta release is due out this month according to all the scuttlebutt I've read, so I think your best bet is just to wait a little longer. Here's a thread on the PDP1 that several folks are using :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/android-9-0-developer-preview-1-t3757268
Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee
Lee KZN said:
Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee
Click to expand...
Click to collapse
You will need to get hold of the stock firmware from somewhere like Sammobile and flash back to stock using ODIN. There's tons of guides knocking about on here for the step by step. The damage is done though as far as any Knox related features go, it's like a fuse that blows when you root and you can never fix that.
Having said that, biometrics should have never been affected by rooting so that's a bit unusual. Flash stock and set up from scratch then go from there, could be faulty also
Thanks for the guidance Dave. I'll search the forums for the steps.
For clarity, when I say biometrics didn't work, it works allow me to record etc, but when I tried to enable it, like on my banking app, it wouldn't allow me. This is how I eventually figured out my phone was rooted. While I know the benefits of being rooted, a normal everyday user like myself, certainly won't benefit from it.
I've had a Samsung my entire life, and always saw the secured by knox logo... When you say damage has been done, does this mean that all my security in the device, such as my banking details etc, may be compromised?
Jees. I hope not. As this would really freak me out...
Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**
Lee KZN said:
Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**
Click to expand...
Click to collapse
The last letters are the region/operator of the Rom. Not necessarily has to be the exact description, the really important are the first that indicate model number.
Ok. So have downloaded Odin and am busy downloading the flash firmware.
May I please be so bold as to ask someone on here to please share a link tot he step by step guide that I will need to follow in order to flash my phone back to the original boot thingie :silly::silly::silly:
I have tried to search but seem to only come up with a nexus thread with no mention of Odin.
~Sorry to ask, but little overwhelmed LOL and want to make sure I do this properly and not screw up my phone.
REAL noob here, so apologies if I come across lazy and getting others to do the work, but am really grateful for the help.
Maybe I'm searching incorrectly???
I found this somehow....
Is this it?
https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
**fingers crossed**
Can you unlock your phone with biometrics? Im guessing only the banking apps don't work because it's rooted. If i remember correctly most banking apps and maybe Google pay(not sure about that) stop working after rooting because the phone is "compromised" and it's not safe. You have to hide your root status from these apps and they will work properly then. Maybe someone else can help you with that because i do not remember how to do it.
Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????
Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????
if the phone was bought as new, go back to the dealer and demand a new one that is not rooted.
could also be that your husband rooted the phone and installed software that keep tabs on what you do.
Hello,
I have recently entered the world of Xiaomi after a history with Sony Devices (Xperia, Xperia SP, Xperia Z3). I'm so far delighted with the Mi 10T Lite, it's feature rich and blazingly fast. However, I miss one feature I had installed on my SP and Z3 that made their batteries live extra long. It's this:
Battery Charge Limit [ROOT] - Apps on Google Play
Stop charging at desired level to preserve battery health for most devices!
play.google.com
With this tool, you can essentially leave your device permanently on the charger and it will stay within the limits you have set. I used to have it set to 71-80%. So when the charge dropped to 70% it started charging, until reaching 80%. I therefore balanced keeping the battery charged for short intervals and at a sweet spot for its health, with having enough charge in case I wanted to grab my phone and leave the house. I really love this app.
The problem is, it requires root privileges.
I understand that rooting my Xiaomi is not particularly hard, but since it is a new device I would not want to void its warranty. It's possible that some defect shows up and I am left without a warranty. It would be a particularly big bummer if I discovered I rooted the device only to see that the app does not work properly with it.
So, could someone with a rooted device try out this fantastic app and let me know if it works? You might end up with a battery life extender you never knew existed!
Many thanks,
Yanni
Athens/Greece
Friendly bump! Could somebody try this nifty app for battery life optimization on their rooted 10T Lite? Let me know if it works so I can go ahead with arcane rooting magick, hehe.
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
egor27 said:
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
Click to expand...
Click to collapse
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
funkyjester said:
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
Click to expand...
Click to collapse
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
_mysiak_ said:
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
Click to expand...
Click to collapse
Thanks for the link. Besides the EU statutory warranty, a quick search reveals that the company itself allows rooting without voiding your warranty. So I'm a happy camper I guess.
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Hemerson Silva said:
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Click to expand...
Click to collapse
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
_mysiak_ said:
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
Click to expand...
Click to collapse
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Hemerson Silva said:
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Click to expand...
Click to collapse
Maybe if you provide step by step guide how to extract xqcn file and remove sensitive information from it before uploading to the internet, someone will be willing to do it.
In each case, we are heavily offtopic here.
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
funkyjester said:
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
Click to expand...
Click to collapse
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
_mysiak_ said:
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
Click to expand...
Click to collapse
I should have figured out what VF means. I think I will take the straightforward way and use QJSEUXM which I have found readily available. Thanks!