Related
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Installing Xposed works as well using the ADB method mentioned in the thread linked below:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476
I can add any info you find to the device index in the general section for the 500CL.
Djalaal said:
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Click to expand...
Click to collapse
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
cmendonc2 said:
I can add any info you find to the device index in the general section for the 500CL.
Click to expand...
Click to collapse
Sure, that post is much more likely to be noticed than this one. Although I might not find out much. I'm a lot less daring without custom recovery. Hence this thread.
crisbal said:
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
Well, seeing that I do not have a custom recovery (bootloader is still locked), I had to do it the hard way, reflash stock rom. Good news is, apparently your userdata (installed apps+settings and internal memory) is not wiped in the process.
First, you gotta download the rom. Get it from http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. Although I got mine here: http://www.asus-zenfone.com/2015/03/asus-zenfone-2-stock-rom-ze500cl-ze550ml-ze551ml.html, which is the old version.
Second, go into recovery mode (from bootloader mode), and use adb sideload ("apply update from ADB") to flash the .zip downloaded before. This is described under "Flashing Zenfone 2 via ADB" on this thread: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Btw, the bootloop was caused by a mistake I made, not the rooting process.
any news update in our bootloader? hope someone could work for that..
How to get rid off couldn't add widget?
crisbal said:
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
After more than a week of feeling unsure to update mine to WW_12.16.5.118, updating it today after finish uninstalling SuperSU. This is what I have done.
1 - uninstall SuperSU from SuperSU setting - reboot.
2 - update firmware.
3 - re-root using Temporary_CWM method as describe here
Chinaphonearena said:
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
link removed due to post count limitation
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to [post count restriction] and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Click to expand...
Click to collapse
4 - Success!!! now my phone are rooted and all rooted apps installed previously are working.
Note: Previously (before updating FOTA) I also root my ZE500CL using Temporary_CWM since One Click root method aren't working for me.
Recover from bootfreeze while fully stock
Well, after getting a bootfreeze being on a fully (old version) stock ze500cl (Z00D), I figured out something useful. How to recover from a bootfreeze with locked bootloader, non rooted stock rom, without loosing what was saved on your internal storage.
Given that you have not messed with system files (since you aren't rooted), I'm assuming you got either corrupted userdata files or your internal storage is so full, the phone fails to even boot. I had the latter. If system files are the problem, this method might (or probably?) not work. The trick is to use tethered TWRP for backing up your internal storage.
1: Download CWM_Zenfone_2_Intel.zip here: https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2 (gotten from source 1)
2: Download Recovery.zip here: https://drive.google.com/folderview...T0xRMVRkcTg3MHdlc1o0cVFBc3RPeTQ&usp=drive_web (gotten from source 2)
3: Extract the zip from Step 1.
4: Go to the FB_RecoveryLauncher folder you have extracted, and replace the recovery.zip there with the one downloaded in Step 2.
5: Boot into your stock recovery and connect your phone to the computer. Make sure you have adb and the phone's drivers installed (gotten from source 3).
6. Run the cai_dat_CWM.bat script and you should boot into temporary TWRP recovery after a minute or so.
7. Use TWRP to copy your sdcard folder (internal storage) into your ext_sdcard folder (external storage/microsd) for the sake of backing it up.
8a. In the case of having too full internal storage, simply delete some things in there, and you should be able to boot it again.
8b. Not tested, but in case of corrupted userdata, a factory reset is probably necessary, and will solve the bootfreeze issue.
source 1: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 (method 2)
source 2: http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
source 3: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
@cmendonc2 , if you want, you can add this to your index.
Djalaal said:
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
Click to expand...
Click to collapse
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Xanathide said:
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Click to expand...
Click to collapse
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Djalaal said:
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Click to expand...
Click to collapse
That's quite alright, I've had my fun with Z00D, got myself a LG V10 to break now
I dont ask for directions...
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
cuervo233 said:
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
Click to expand...
Click to collapse
?? Is that att ota youre trying to sideload? Att doesn't have fw, ze500cl does. But just unlock your bootloader, flash twrp, then install whatever, cm, aicp, custom stock or straight stock. http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my MotoG3 using Tapatalk
Cool, I didn't read anywhere about unlocking BL first otherwise Ida made that "turn at the first light". We will ULO thru Asus and continue on our journey. These little Asus trinkets are little buggers being Intel based. Only line of Android devices that have ever stumped me. I am much obliged, fellow XDA brethren. Much obliged.
After pondering a little I came to this conclusion:
UL BL is basically the first step one should take when doing any kind of flashing of internal partitions be it a boot.img, recovery.img, FW etc... at least for the higher end devices. I don't recall having to do that for my sm-n900t recently. Does it only apply for flashing back to stock and not custom roms? Although I didn't have to UL BL first when I heim-dall/Odin flashed my note3 back to stock rom after being boot-looped. Cause once I did that I was able to try out a majority of custom roms available for it whether flashed thru HD/fastboot, Odin, via twrp update zip, or adb sideload. Hmmm, I might understand once I think it thru and look at all the different variables.
Good day gentlemen.
Be vewy vewy quiet, I'm hunting androids...
:good:
@cuervo233 Yes most devices you have to unlock the bootloader first. But there are some devices that already come unlocked. And then there are even some that have bootloaders that cannot be unlocked due to carrier restrictions. In order to get custom recovery to boot you must unlock the bootloader or it must come unlocked. With a custom recovery you can Flash the stock zip file from the Asus website or a custom ROM have fun
Sent from my MotoG3 using Tapatalk
Thank you. I was able to ULBL, flash TWRP, flash to ww 118, root, and now its time to explore the neat wonderful world of custom ROMs. This was by far the hardest yet. Next in line is the cricket Stylo which was also giving me hell, but now I dont think I should have any problem getting it done. I'll keep ya'll posted.:good:
Lg stylo should have way more development, have fun brother. Remember tmobile phones( cricket, walmart family mobile, and metro pcs) you can easily unlock the bootloader . att on the other hand usually has locked down bl.
Sent from my MotoG3 using Tapatalk
I’m new to this forum, and I’m new to android, with the minimum knowledge in developing or modifying anything in an android phone. So, I’m asking if someone has solution on my issue, should he please explain it with all the details.
I just bought 3 phones, SAMSUNG GALAXY S4 MINI VERIZON SCH-I435 - ANDROID VERSION IS 4.4.2 [maybe just 1 that I selected on the phone to update the software, and the others (I still didn’t opened it also no line on it) are maybe 4.2]; I need it for 3 employees that I want to use it with a specific program for my business that it not needed to be updated continuously, and its suppose to getting updated daily with a direct USB connection to our server.
My issue is, that for many reasons I want that the internet and any type of data connection should be fully disabled, no browser, no e-mail, no data apps, no in apps purchases, no MMS messaging, and also no video. Just Talk & Text and. So I’m wondering if it’s possible on an android phone to disable all data apps and block all data connections, in a way that it shouldn’t be able to restore it back.
Before I came here, someone told me that I can do it if I first root the phone (he also didn’t know what I need to do after rooting) he gave me to try a few programs to root the phone, Super User, TowelRoot, Kingo ROOT ,Super SU but as I see nothing worked for my phone. The SuperSU gives a message that it cannot find the SU binary, and the others don’t work for other reasons – I tried to search somewhat on the internet about this kind of problems with rooting this model phone, and I found some complicated guidance with a combination of a few downloads, what I even didn’t understand the instructions how to do it, and I’m also definitely afraid of damaging the phone, and maybe after all it will still not work for me to root the phone – and the main thing is that my goal is not rooting the phone, but to totally disable any internet and data connections from this phones.
So I’m asking if someone can please give me a step by step solution for this kind of modification on this model phones, to permanent disable all data connection from the phone, and if 1 of the steps is to root the phone, then I also need detailed information from someone who has the experience with rooting this model phone with this android version.
I will appreciate everyone’s time and effort to help me.
Thanks
P.S. if my issue can only be solved by a paid android developer, maybe… I’m willing to pay some amount to do this. So if u see this for the only solution, then please direct me to a reliable developer. depends on price, experience, and more, to decide if willing to pay
solb said:
I’m new to this forum, and I’m new to android, with the minimum knowledge in developing or modifying anything in an android phone. So, I’m asking if someone has solution on my issue, should he please explain it with all the details.
I just bought 3 phones, SAMSUNG GALAXY S4 MINI VERIZON SCH-I435 - ANDROID VERSION IS 4.4.2 [maybe just 1 that I selected on the phone to update the software, and the others (I still didn’t opened it also no line on it) are maybe 4.2]; I need it for 3 employees that I want to use it with a specific program for my business that it not needed to be updated continuously, and its suppose to getting updated daily with a direct USB connection to our server.
My issue is, that for many reasons I want that the internet and any type of data connection should be fully disabled, no browser, no e-mail, no data apps, no in apps purchases, no MMS messaging, and also no video. Just Talk & Text and. So I’m wondering if it’s possible on an android phone to disable all data apps and block all data connections, in a way that it shouldn’t be able to restore it back.
Before I came here, someone told me that I can do it if I first root the phone (he also didn’t know what I need to do after rooting) he gave me to try a few programs to root the phone, Super User, TowelRoot, Kingo ROOT ,Super SU but as I see nothing worked for my phone. The SuperSU gives a message that it cannot find the SU binary, and the others don’t work for other reasons – I tried to search somewhat on the internet about this kind of problems with rooting this model phone, and I found some complicated guidance with a combination of a few downloads, what I even didn’t understand the instructions how to do it, and I’m also definitely afraid of damaging the phone, and maybe after all it will still not work for me to root the phone – and the main thing is that my goal is not rooting the phone, but to totally disable any internet and data connections from this phones.
So I’m asking if someone can please give me a step by step solution for this kind of modification on this model phones, to permanent disable all data connection from the phone, and if 1 of the steps is to root the phone, then I also need detailed information from someone who has the experience with rooting this model phone with this android version.
I will appreciate everyone’s time and effort to help me.
Thanks
P.S. if my issue can only be solved by a paid android developer, maybe… I’m willing to pay some amount to do this. So if u see this for the only solution, then please direct me to a reliable developer. depends on price, experience, and more, to decide if willing to pay
Click to expand...
Click to collapse
Hello, i think to achive this someone have to create a modified rom(maybe based on samsung's stock or even cyanogenMod). I dont think its pretty difficult, but i dont have the wright knowledge to accomplish this.
But i can help you for rooting the phones. S4 mini s running 4.4.2(lets call it v1). But samsung pushed an update again on 4.4.2 after some months(call it v2).The v1 is easy to update with towelroot.
But the v2's kernel cant be rooted with that way. I follow some instructions from a post here on xda and i rooted mine. If you are on v2 you have to flash v1's kernel with odin, root it and then flash the v2's kernel.That's the way i did to my phone and i successfully root it.
You can download from sammobile all the stuff you need(kernels). I think it will gonna work for you too. To check if you are on the old(v1) or on the new(v2) rom, try towelroot and if it fails you are on v2, else on v1.
Thanks.
First, how do i get such kind modified rom?
second, about rooting. I tried already Towelroot and its not working, so maybe this means that i have already the update that you call V2. how could i know if i have V1 or V2?
also can you please explain me in detail your solution. Sory Im a novice in the android language. what "odin"?, how do i get it, how do i use it?, what means flash? how do i flash v1's kernel? and how do i flash V2's kernel?
Thanks again
solb said:
Thanks.
First, how do i get such kind modified rom?
second, about rooting. I tried already Towelroot and its not working, so maybe this means that i have already the update that you call V2. how could i know if i have V1 or V2?
also can you please explain me in detail your solution. Sory Im a novice in the android language. what "odin"?, how do i get it, how do i use it?, what means flash? how do i flash v1's kernel? and how do i flash V2's kernel?
Thanks again
Click to expand...
Click to collapse
About the 'modified rom' you have to wait for a response from someone with the knowledge to do this. There is no reason talking about root from now.
You can pm some developers and ask for help.
Maybe try something like LBE Security think you can deny access to things like that and maybe have a master app password. Maybe try looking under Android development forum under software or general. You may get a better response to your question, as it's pretty much just a device topic here. But I would think on Android such things should be possible.
Okay, I realize I'm gonna get backlash for this, because I'm clearly missing some critical bits of information, so I'm certainly gonna come across as though I don't know what I'm doing - which I'd argue is only partially true.
But whatever, here are my gripes. I've never had so much difficulty rooting an Android device before, and I'm losing my mind. The lack of resources for this particular model is unheard of, and every article I read has me download DIFFERENT decryption files! It's insane - it's like nobody - but the few of us on XDA - own one of these or care about the flashing and root process!
- I've been reading through the forums and there are comments acknowledging issues that appear to be far and wide, and always inconclusive!
- TWRP (mind you, the ONLY version that actually works and let's me boot into it, gave me a bootloop!) And this version of TWRP can't connect via ADB/won't read anything but SD cards and anything other than this version of TWRP won't let me boot into it.
- Tab S4 won't listen to FASTBOOT cmds on my pc! Yes, drivers are installed correctly. My Tab S first gen. Works fine with it!
- STOCK FIRMWARE. My biggest complaint is the firmware. It's NOWHERE online! Every website excludes the US varient (which should be prefixed with XAR, or so I thought!?!?) and downloads at 100kb/sec AFTER you sign-up with them. Updato claimed to have the US XAR version, but the link to it was empty! A few users provides links to the "US" version, but nothing for Android 9.0 SM-T830 (US).
As troublesome as this device has proven to be, it's insane that noone has compiled all of the CORRECT information into ONE place and called it a day. If you think that's what a few users on XDA have done, I'd strongly disagree. The forums are just as bad! It's like an endless rabbithole of "oh try this file instead" "I found another issue doing it THIS way" "fix it like this" "oh now THIS isn't working" "well here's an updated version of that" "
To be clear, I have a US varient of the Galaxy Tab S4 (SM-T830) running the latest version of Pi, and while I'd love to describe everything I've done to the tablet to get to the point I'm currently at, I'm currently at my wits end, and I'd love to just have a working tablet again.
THE WHOLE POINT OF THIS POST:
Can someone please, please provide me the UPDATED Android 9.0 stock firmware for the SM-T830 UNITED STATES varient including ANY combo files or EXTRA files needed so I can get my tablet back to it's out-of-box STOCK firmware?
Robert_McCoy2 said:
Okay, I realize I'm gonna get backlash for this, because I'm clearly missing some critical bits of information, so I'm certainly gonna come across as though I don't know what I'm doing - which I'd argue is only partially true.
But whatever, here are my gripes. I've never had so much difficulty rooting an Android device before, and I'm losing my mind. The lack of resources for this particular model is unheard of, and every article I read has me download DIFFERENT decryption files! It's insane - it's like nobody - but the few of us on XDA - own one of these or care about the flashing and root process!
- I've been reading through the forums and there are comments acknowledging issues that appear to be far and wide, and always inconclusive!
- TWRP (mind you, the ONLY version that actually works and let's me boot into it, gave me a bootloop!) And this version of TWRP can't connect via ADB/won't read anything but SD cards and anything other than this version of TWRP won't let me boot into it.
- Tab S4 won't listen to FASTBOOT cmds on my pc! Yes, drivers are installed correctly. My Tab S first gen. Works fine with it!
- STOCK FIRMWARE. My biggest complaint is the firmware. It's NOWHERE online! Every website excludes the US varient (which should be prefixed with XAR, or so I thought!?!?) and downloads at 100kb/sec AFTER you sign-up with them. Updato claimed to have the US XAR version, but the link to it was empty! A few users provides links to the "US" version, but nothing for Android 9.0 SM-T830 (US).
As troublesome as this device has proven to be, it's insane that noone has compiled all of the CORRECT information into ONE place and called it a day. If you think that's what a few users on XDA have done, I'd strongly disagree. The forums are just as bad! It's like an endless rabbithole of "oh try this file instead" "I found another issue doing it THIS way" "fix it like this" "oh now THIS isn't working" "well here's an updated version of that" "
To be clear, I have a US varient of the Galaxy Tab S4 (SM-T830) running the latest version of Pi, and while I'd love to describe everything I've done to the tablet to get to the point I'm currently at, I'm currently at my wits end, and I'd love to just have a working tablet again.
THE WHOLE POINT OF THIS POST:
Can someone please, please provide me the UPDATED Android 9.0 stock firmware for the SM-T830 UNITED STATES varient including ANY combo files or EXTRA files needed so I can get my tablet back to it's out-of-box STOCK firmware?
Click to expand...
Click to collapse
Use SAMFIRM.EXE to download firmware it's so easy So true it's a pain to root and getting everything up and running again! Took me 2 days and about 40+ flash stock flash recovery dam flashed wrong decryption zip as there's so many versions, it would boot OEM lock not showing you reboot stuck in a boot loop then it started to work then you reboot it would wipe the whole tablet like stock it did that so many times i really wanted to smash up my Tab S4! At 1 point i even considered to slap it on ebay partially booting it was driving me up the wall i think this will be the last device i ever root its just too much headache!
But anyway use SAMFIRM.EXE Clicky and flash WETA Rom Clicky Please note WETA also has the decryption if you got TWRP installed you can flash Weta via it real simple!
Samfirm or Frija is going to be the answer as far as firmware goes. All of the download sites are just horrible now.
I was easily able to find and download the stock firmware for the normal tab, though it seems none have the 837 model available.
veekay said:
Samfirm or Frija is going to be the answer as far as firmware goes. All of the download sites are just horrible now.
I was easily able to find and download the stock firmware for the normal tab, though it seems none have the 837 model available.
Click to expand...
Click to collapse
What's Frija ?
Never mind found it thanks https://forum.xda-developers.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584
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!
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
RushPL said:
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
Click to expand...
Click to collapse
Sadly, that's the way XDA developed in the most recent years. A lot of developers have become "impatient", they rarely tolerate questions (which they consider unnecessary for reasons of their own) or consider everything that is not in their concise jargon offtopic and either ignore, flame or delete those.
The basics are not explained anymore, they expect everyone to work naturally with the tools at hand, most often or not "small" steps are left out (like clicking on something, or changing a menu), or they refer to "go look at that guide" - only then - that guide tells you (aswell) "for step 3, go look at that guide", because "everyone should know" - that way the rooting community is quite small and elitist; and it's hard for outsiders to come in (and potentially add something to the pool of stuff) simply because it's not a pleasant experience to "dive" into the world of Android customization. It's a sad development and only very few seem to be intend on breaking it.
Then we also have the problem of manufacturers trying to make this communities life harder, just take a look at Google and the constant war to have safetynet NOT trip, to give people the chance to use banking apps or GPay. It's a constant struggle and many "guides" get out of date pretty quickly - and most often or not, those are not kept up to date, or getting demolished by a mod team, so that also adds to the whole confusion, when people try to work with guides / community fixes that won't even work anymore.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...irmware-sd1a-210817-036.4353807/post-85857811
I followed the instruction from this post to restore my P6P to preinstalled October firmware, then updated with November firmware OTA, then unlocked bootloader and root again. My phone works much better now.
I made a mistake of flashing the vbmeta and boot imgs of October firmware for rooting after updating November firmware OTA. I experienced some strange issues with my phone until I restored it with Official Google Android Flash Tool and start the whole rooting process again with the correct version of vbmeta and boot imgs.
Pekempy said:
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
RushPL said:
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
Click to expand...
Click to collapse
No need but thank you for offering.
The vbmeta is also new to me. I want to be clear, I've mostly compiled others' instructions (credited in the post) with my own experience, and tried to make it as easy to follow as I can
I was able to root successfully with working Safety Net! Thank you @Pekempy