The phone goes crazy - OnePlus 7 Pro Questions & Answers

Hello, while playing with the installation of Windows 11 on OnePlus 7 Pro, unfortunately, I screwed something up and the system simply does not want to get up. Even after uploading various roms, including stock roms, and botching a given .img image via TWRP, the system still does not want to get up, it assumes that the fingers could have dipped the commands that I used when preparing the smartphone for installing Windows 11 via fastboot.
Commands were sent to the +/- command "rm 17" after which it crashed and did not go further, probably because these commands were prepared for OnePlus 6T / Windows 11.
Is there a way to repair the system?

Related

[Q] Bricked - Formatted Partitions with no OS to install

Hello guys, so before I go any further I'll say that I have spent two days attempting to figure out ways to get my self out of this trouble and I've come close, but no cigar. The limiting factor here is the inability to connect to a PC.
Ill begin with the intent: format all partitions to F2FS. I finished backing up all important data to cloud storage and what little I could to my PC (photos only). While I was able to connect my phone to the pc, all I could get it to recognize was as a camera device, not an MTP device, so I was limited as to what files I could back up (hence the cloud storage used for the rest). I tried many different drivers (LG mobile device drivers, Google USB driver, Installing google SDK tools, etc).
I admit that I messed up not realizing I would've needed to restore the f2fs roms previously downloaded in order to re-flash in TWRP. I went ahead and formatted the phone to F2FS and all I have is TWRP 2.7.1.1. I have tried mounting through TWRP in windows XP sp3 and also in windows 8, I can not get the phone to mount the internal SD card in order to drop an f2fs compatible rom to flash.
So I basically have a useless phone at the moment (TWRP and no OS). I was hoping there would be an option to flash a rom image using ODIN, but I can't seem to find any helpful instructions online. Any help at this moment would be greatly appreciated. I'll answer any questions I can.
murph187 said:
Hello guys, so before I go any further I'll say that I have spent two days attempting to figure out ways to get my self out of this trouble and I've come close, but no cigar. The limiting factor here is the inability to connect to a PC.
Ill begin with the intent: format all partitions to F2FS. I finished backing up all important data to cloud storage and what little I could to my PC (photos only). While I was able to connect my phone to the pc, all I could get it to recognize was as a camera device, not an MTP device, so I was limited as to what files I could back up (hence the cloud storage used for the rest). I tried many different drivers (LG mobile device drivers, Google USB driver, Installing google SDK tools, etc).
I admit that I messed up not realizing I would've needed to restore the f2fs roms previously downloaded in order to re-flash in TWRP. I went ahead and formatted the phone to F2FS and all I have is TWRP 2.7.1.1. I have tried mounting through TWRP in windows XP sp3 and also in windows 8, I can not get the phone to mount the internal SD card in order to drop an f2fs compatible rom to flash.
So I basically have a useless phone at the moment (TWRP and no OS). I was hoping there would be an option to flash a rom image using ODIN, but I can't seem to find any helpful instructions online. Any help at this moment would be greatly appreciated. I'll answer any questions I can.
Click to expand...
Click to collapse
ODIN? This isn't a crappy Samsung device. Flash factory images with fastboot in bootloader, or adb push a flashable ROM zip to your internal storage and flash it in recovery. If you don't know how to do that, I don't know why you're messing with your device at all. If that's the case, first link of my signature for threads on how.
Lethargy said:
ODIN? This isn't a crappy Samsung device. Flash factory images with fastboot in bootloader, or adb push a flashable ROM zip to your internal storage and flash it in recovery.
Click to expand...
Click to collapse
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7). I would need to reformat the partitions to ext4 in order to fastboot flash stock images no?
murph187 said:
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7).
Click to expand...
Click to collapse
Theres a thread for diagnosing driver issues. You might have to disable signature enforcement on Win8.
Flashing factory images will reformat it to ext4, I'm pretty sure.
Also, there is hardly any UI difference in 8 compared to 7. Even the "start menu" is theoretically the same, just with a different layout. Pinned shortcuts and a list of shortcuts.. You can install a 3rd party start menu if you're someone that can't adapt to something new. Any complaints that "Windows 8 is terrible" are just stupid.
murph187 said:
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7). I would need to reformat the partitions to ext4 in order to fastboot flash stock images no?
Click to expand...
Click to collapse
Make your suffer short. Try lg flashtool. Link in my signature.
bitdomo said:
Make your suffer short. Try lg flashtool. Link in my signature.
Click to expand...
Click to collapse
Your method worked thank you very much! Mod can close thread.

ASUS ZenPad C 7.0 (Z170C - P01Z) - Working Root Method

Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All credit lies where it is due.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all you guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you. This guide has been reported to also work with the Z170CG and Z370C tablets, in which case owners of these tablets can attempt this method but with caution. Beware, this method has not been tested by myself and prepare yourself for the event of a brick.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
Unbrick process not working for you? Download the stock firmware .zip here, and be sure to boot into recovery mode (power + volume down at boot) and flash the .zip. - I haven't tested this yet so I cannot confirm 100% that this method works, but it should. It could be either an update package or the full stock firmware, but one user has confirmed this method to be working.
UPDATE: A quick update for all you guys on what is currently happening.
v1.0.2 - Minor update, grammar corrections.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.
Success!
With latest updates on my device tried and it works thx for great job
great job AwesomeLewis24.
I complete all steps and the device Z170CG ( p01y) boot into normal mode without any root rights.
After repeating the method, device is hanging on asus boot screen and even factory reset not helped.
Fortunately i was able to flash stock rom and device turned on and now working normally again.
wish me luck, i'm going to try rooting again.
Asus p01z z170c tablet rooting access /custom recovery anyone?
AwesomeLewis24 said:
Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All rightful credit can be paid to those.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all y'all guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this by accident and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.
Click to expand...
Click to collapse
Thanks for all your work and research. I must wait till I'm home and try this method out! Has anyone been working on a custom recovery for this!? Thanks again!
hayabusa_gsxr said:
great job AwesomeLewis24.
I complete all steps and the device Z170CG ( p01y) boot into normal mode without any root rights.
After repeating the method, device is hanging on asus boot screen and even factory reset not helped.
Fortunately i was able to flash stock rom and device turned on and now working normally again.
wish me luck, i'm going to try rooting again.
Click to expand...
Click to collapse
Good luck buddy! If you could, do you mind sharing where you got the stock ROM from? This could come in handy sometime...
Also, @totalppl so far there's nothing in terms of custom recoveries or the such for this device. Maybe I'll see if there's any chance of an available TWRP port I can port over from a fellow x86 asus device. Until then, this is as far as we have gotten in terms of dev support.
Sent from my Moto G 2014 LTE using Tapatalk
AwesomeLewis24 said:
Good luck buddy! If you could, do you mind sharing where you got the stock ROM from? This could come in handy sometime...
Also, @totalppl so far there's nothing in terms of custom recoveries or the such for this device. Maybe I'll see if there's any chance of an available TWRP port I can port over from a fellow x86 asus device. Until then, this is as far as we have gotten in terms of dev support.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
This (as it stands) is much appreciated.....
No need to hurry on the recovery front...
Root (for me at least) is the important bit....being able to use TiBu to get rid of the bloat.....that's my priority.....
http://i.imgur.com/rVnFwJM.jpg
@keithross39
Can confirm for me that the majority of the bloatware has been successfully removed and the tablet runs much cleaner now.
Thanks for the messages guys, but like I said credit is where it stands to the guys who found the root.
Sent from my Moto G 2014 LTE using Tapatalk
http://4pda.ru/forum/lofiversion/index.php?t679135-1600.html
Here is the stock rom.
rom flashed using the official rom(there are 2 roms 1GB and 2GB, i'm using 1GB version,don't know the difference) and boot from sdcard.
@hayabusa_gsxr
Thanks for the link, I've been searching on ends for stock ROMs for this tablet. It's been stressing me out! 4pda has been a good forum to us Zenpad users.
Other than that, maybe I'll link that in the top forum post, just in case worse comes to worse.
Sent from my Moto G 2014 LTE using Tapatalk
hayabusa_gsxr said:
http://4pda.ru/forum/lofiversion/index.php?t679135-1600.html
Here is the stock rom.
rom flashed using the official rom(there are 2 roms 1GB and 2GB, i'm using 1GB version,don't know the difference) and boot from sdcard.
Click to expand...
Click to collapse
Just to confirm.....what is the exact process for flashing these firmwares?
tia.....Keith
http://i.imgur.com/rVnFwJM.jpg
Thank you very much, working 100% in my P01Y.
Please share if you know about custom roms for this tablet.
Having root is amazing, I created a bootloader already:
https://youtu.be/H5eXCwYpRvs
chrisupi007 said:
Having root is amazing, I created a bootloader already:
https://youtu.be/H5eXCwYpRvs
Click to expand...
Click to collapse
Nice work! Awesome to see how we are slowly but steadily finding out and developing more and more for this nimble tablet.
Sent from my Moto G 2014 LTE using Tapatalk
Need a little help
AwesomeLewis24 said:
Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All rightful credit can be paid to those.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all y'all guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this by accident and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
Unbrick process not working for you? Download the stock firmware .zip here, and be sure to boot into recovery mode (power + volume down at boot) and flash the .zip. - I haven't tested this yet so I cannot confirm 100% that this method works, but it should. It could be either an update package or the full stock firmware, but one user has confirmed this method to be working.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.
Click to expand...
Click to collapse
Okay, I am not sure what I am doing wrong, i can run the adb devices command and it shows that it is connected. After i run the adb reboot fastboot my p01z is at a green screen with the little android guy on it. Then I try to run the next command and it says waiting for device. What am I doing wrong? What info do I need to provide for some help? Any and all help is appreciated. Thanks
@corvusfan23
When you're in the green screen where it says "waiting for device", check your Device Manager (windows key + R, search for devmgmt.msc"). If you see your device with the yellow warning symbol next to it, it isn't correctly installed. Simply double click on it, and click browse to manually install the driver and click on either the Google / ASUS / Intel or any other compatible ADB driver and let it install. It should then be usable to and from your computer.
This happened with me and is quite frequent. For me however, the device kept connecting and disconnecting every 20 seconds so I had to be very quick at reinstalling the correct driver. After the driver was reinstalled for my tablet again in fastboot, I could continue on with the process.
Sent from my Moto G 2014 LTE using Tapatalk
AwesomeLewis24 said:
@corvusfan23
When you're in the green screen where it says "waiting for device", check your Device Manager (windows key + R, search for devmgmt.msc"). If you see your device with the yellow warning symbol next to it, it isn't correctly installed. Simply double click on it, and click browse to manually install the driver and click on either the Google / ASUS / Intel or any other compatible ADB driver and let it install. It should then be usable to and from your computer.
This happened with me and is quite frequent. For me however, the device kept connecting and disconnecting every 20 seconds so I had to be very quick at reinstalling the correct driver. After the driver was reinstalled for my tablet again in fastboot, I could continue on with the process.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
Okay I did end up getting my device rooted, how would I go about making a backup of my device? I saw something about titanium backup, and the next thing I want to do is remove the bloatware. Any help is appreciated!
@corvusfan23
That's great to hear! To make a backup of your device, yes definitely I'd recommend Titanium Backup. It's a pretty powerful tool for root users to make full backups of the system, media, specific apps, etc. I haven't actually used it much myself as usually I don't keep much important stuff on my device (photos and music I usually keep in the cloud now) but on the odd occasion that I have used it, its been very good. I have it installed on my Moto G for "emergency situations".
Also, to uninstall the bloatware you can indeed use Titanium Backup but I'm quite a fan of Link2SD. I prefer the material design interface and the easy visuals, but that's just me. In terms of uninstalling bloatware, they work pretty much the same so its your choice. I've been loyal to Link2SD for a while now.
As far as bloatware comes, uninstall (or even better, freeze) as much crap as you want. I haven't experienced any problems with it so far - (on my old Acer tablet that I got at Christmas, the first thing after root I did was uninstall the Amazon app store. It bricked my tablet and there was nothing like stock firmwares around, or any dev support, so I returned it and got this asus). However, stay cautious and of course don't mess around with any apps that seem to be tied in with the system in some way.
Sent from my Moto G 2014 LTE using Tapatalk
AwesomeLewis24 said:
@corvusfan23
That's great to hear! To make a backup of your device, yes definitely I'd recommend Titanium Backup. It's a pretty powerful tool for root users to make full backups of the system, media, specific apps, etc. I haven't actually used it much myself as usually I don't keep much important stuff on my device (photos and music I usually keep in the cloud now) but on the odd occasion that I have used it, its been very good. I have it installed on my Moto G for "emergency situations".
Also, to uninstall the bloatware you can indeed use Titanium Backup but I'm quite a fan of Link2SD. I prefer the material design interface and the easy visuals, but that's just me. In terms of uninstalling bloatware, they work pretty much the same so its your choice. I've been loyal to Link2SD for a while now.
As far as bloatware comes, uninstall (or even better, freeze) as much crap as you want. I haven't experienced any problems with it so far - (on my old Acer tablet that I got at Christmas, the first thing after root I did was uninstall the Amazon app store. It bricked my tablet and there was nothing like stock firmwares around, or any dev support, so I returned it and got this asus). However, stay cautious and of course don't mess around with any apps that seem to be tied in with the system in some way.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
Last question I have for now. What apps would you recommend uninstalling/freezing? I don't use a lot of the asus apps that came with it. Could I get rid of the "Asus Demo" app and "Asus Support" apps?
@corvusfan23
I've uninstalled most of the preinstalled apps (non asus) but also I've uninstalled some of the asus cloud and "do it later sort of apps. I've frozen the asus keyboard, the ZenUI launcher, and the built in browser as well because I use alternative Google apps.
Sent from my Moto G 2014 LTE using Tapatalk

BlissOS X86 stuck at boot logo animation

Hello. I have installed BlissOS 10.1 nightly build on a Dell Venue 11 Pro 7139. The iso used was Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso. The installer completed succeffuly and I installed to my C: partition as an image partition, not as a separate partition. When I try to boot the OS, it starts as usual saying android found at sda sth, then after a very quick dump of echoes I don't know how to capture, the boot logo animation appears and stays there forever. After a number of attempts, I realized that the console is active and I can type commands like logcat. Unfortunately they only appear as they scroll because apparently the boot animation refreshes the screen, so I can't see the output and don't know if there is any command to stop the animation or redirect the output of the command to a log file that I can read through Windows. I had successfully installed BlissOS in the past in the same notebook, but had to resort to PhoenixOS, because touchscreen input didn't work. In PhoenixOS everything worked, but now I need Widevine DRM support and read that BlissOS currently supports it.
Any help would be appreciated.
slazaris said:
Hello. I have installed BlissOS 10.1 nightly build on a Dell Venue 11 Pro 7139. The iso used was Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso. …… Any help would be appreciated.
Click to expand...
Click to collapse
I have never installed BLISS; but, I had the same thing happened with Android X 86 install. I did a quick reinstall And when prompted to run Android or reboot I chose the reboot option. The operating system booted up just fine after that.
I met the similar probem on Qemu
It's very strange. It does work at the begining, and i used it for some days, but suddendly can not boot into the desktop, just stuck at the boot logo.
And i met this problem on three different PCs with Qemu.
BTW: I am using Bliss-v11.10--OFFICIAL-20191214-2253_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-undefined_gms.iso
i have same (lingeageos) on virtualbox

I broke the ENTIRE OS

As a joke, I ran "rm -rf /" in Terminal Emulator with superuser rights, after a few seconds the app crashed and the phone froze and I had to press the power button for 15s to cut the power. The biggest suprise was that partitions like /system and even /sdcard were not completely erased, as I booted right back into Lineage OS, however the phone was really sluggish and I experienced a lot of ARNs and micro stutters. Everytime I would try to use my phone I'll only get a maximum 10 seconds of SoT followed by an instant shutdown.
Now trying to install a new rom works 1/2 times. When it fails I get an error such as "couldn't mount /firmware" in the TWRP log, and when it succeeds and boots into the first time setup, the same story as above happens again (ARNs and shutdowns).
Somehow I must've deleted more than just the user writeable partitions, as the file system is all over the place and it's not functioning correctly anymore. The phone isn't recognized by ADB even in Fastboot and Recovery mode, and I reinstalled the Universal ADB Drivers from ClockworkMod for Windows.
Idk if this phone will ever see the light of day again although I daily drove it 4 years and it served me like a champ.
Right now I'm questioning if there is any possible solution or if I have to resort to manually pumping electrons into the NAND Flash =)
To mention:
-My phone is the Xiaomi Redmi 4 Prime (codename markw);
-I had an unofficial build of Lineage OS 18.1;
-I can still boot into Fastboot mode and TWRP Recovery;
-I can still transfer files between my phone and my pc using a micro sd card;
-You can get as technical as you want.
Everyone's opinion will be well perceived and every little bit of help will be much appreciated!!
Side remark:
You've to use Xiaomi Android USB Driver.
jwoegerbauer said:
Side remark:
You've to use Xiaomi Android USB Driver.
Click to expand...
Click to collapse
I have also tried using the MiFlashTool which came bundled with Xiaomi Adb drivers, but no success.

Question Trouble rooting my Pixel 7 Pro

I am trying to root my new Pixel 7 Pro, build number TD1A.220804.031, but have run into an issue. Let me explain what I have done and where the issue arose:
I am following the instructions here: https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-7-pro/. I found the factory image for my phone, downloaded it, then downloaded/installed the Payload Dumper Tool, extracted init_boot.img, copied it to my phone, patched it using Magisk, and copied it back to my computer. Took a bit longer than expected, but no problems.
Via the phone’s setting, I enabled OEM Developer options and then allowed OEM Unlocking. Again, no issues. I then turned the phone off, attached the phone to my computer using a USB cable, and then booted it so that the bootloader menu was visible. In a command window on my PC, I then ran ‘fastboot flashing unlock’. I think this worked (because, when I restarted the phone, I had to go through the whole initialization process again).
The next step is where I ran into the problem. The first time, I put the modified init_boot.img in a new folder on the C: drive, but when I ran ‘fastboot flash init_boot path/to/magisk_patched.img’, I got the error “fastboot: error: cannot load <patched file>: permission denied”. So, then I copied the file to a folder on D:, ran the same command, and got the same error.
I suspect that I missed a step or something equally silly. Any suggestions as to what I should try or any pointers to other rooting guides that might be helpful? Don’t know if this means anything, but when the phone was powered off and plugged into the computer, I tried ‘adb reboot bootloader’ but nothing happened.
When you reboot, do you get the orange triangle with exclamation in it?
it might just be easier to move the magisk_patched.img to the platform-tools folder (the same folder that has adb.exe and fastboot.exe); if you are having "permission" issues from Windows, but you aren't from adb or fastboot, then supposedly having it in the same folder should run it under the same permissions.
Also, make sure that you run CMD as an elevated prompt; search for CMD, right-click, and "Run as administrator" -- this might help with the permission issues as well.
Final suggestion is to be sure to run platform-tools version r33.0.3...
Good luck and hope this helps...
P.S. Also, you might've had better luck and/or it's better organized if you posted in the Pixel 7 Pro (cheetah) forum instead of the Pixel 7 (panther)....
Use Pixel Flasher. Less hassle, more convenience.

Categories

Resources