Hello, I own a Cube i10-R. The tablet comes with RemixOS 1.0 installed by factory. Recently Jide released an official RemixOS 2.0 image on their site, but I'm not able to flash it. Tried several times, but the procedure always stuck on "droidboot boot". Usb drivers are working, since I'm able to reflash the 1.0 image without issue. I also tried to swap both droidboot.img files (from 1.0 to 2.0 images), but clearly after flashing procedure, the tablet doesn't start. Both the droidboot images are different in sizes, so that swap was an hopeless try basically.
I'm not an android developver, but it seems that the main problem is the droidboot.img file in the last Jide release. Can anyone give a look at it? It would be nice to have a working 2.0 remixos on this good tablet
@Bad-Pixel - Sorry to hear of your experience. When it's our office hours tomorrow, I'll ask the person in charge of this ROM. She'll probably ask me for some specific info from you and then we'll go from there. So, wait until I PM you. Thanks!
RemixOS_Jason said:
Sorry to hear of your experience. When it's our office hours tomorrow, I'll ask the person in charge of this ROM. She'll probably ask me for some specific info from you and then we'll go from there. So, wait until I PM you. Thanks!
Click to expand...
Click to collapse
Thanks for your quick reply! In order to try to speed up both works, the flashing procedure stuck on the follow fastboot command (from flash5.1_user.xml file):
Code:
<command>
<string>fastboot boot $droidboot_file</string>
<timeout>120000</timeout>
<retry>2</retry>
<description>Uploading fastboot image.</description>
<mandatory>1</mandatory>
</command>
When receiving the "fastboot boot droidboot.img" command, the tablet SHOULD switch from DnX mode to Bootloader mode (also called Droidboot if I'm not wrong). After booted in droidboot, the procedure will continue with other commands (this is what happens when I flash back the original RemixOS 1.0 image).
The problem is that the tablet NEVER switch to bootloader mode, but it remains in DnX mode (despites of what the Intel Manufacturing Flashing Tool shows). After 180 seconds, the procedure fails due to ADB Enum Timeout.
I searched on net for some solution, but nothing was found.
Programs used: Intel MFT (ver 6.0.43) with latest Intel Android driver setup (vers 1.10.0). Also i've tried the Intel Phone Flash Tool (both ver 5.3.2.0 and 5.5.2.0)with DnX usb driver.
I can provide to you some screenshots if you need them, just ask whatever you need for!
Anyway, now I just wait for any your comunication. Thanks for your patiente and sorry for multiple messages
You might as well send me screenshots, because in my experience, they'll be helpful.
Thanks!
Bad-Pixel said:
Thanks for your quick reply! In order to try to speed up both works, the flashing procedure stuck on the follow fastboot command (from flash5.1_user.xml file):
Code:
<command>
<string>fastboot boot $droidboot_file</string>
<timeout>120000</timeout>
<retry>2</retry>
<description>Uploading fastboot image.</description>
<mandatory>1</mandatory>
</command>
When receiving the "fastboot boot droidboot.img" command, the tablet SHOULD switch from DnX mode to Bootloader mode (also called Droidboot if I'm not wrong). After booted in droidboot, the procedure will continue with other commands (this is what happens when I flash back the original RemixOS 1.0 image).
The problem is that the tablet NEVER switch to bootloader mode, but it remains in DnX mode (despites of what the Intel Manufacturing Flashing Tool shows). After 180 seconds, the procedure fails due to ADB Enum Timeout.
I searched on net for some solution, but nothing was found.
Programs used: Intel MFT (ver 6.0.43) with latest Intel Android driver setup (vers 1.10.0). Also i've tried the Intel Phone Flash Tool (both ver 5.3.2.0 and 5.5.2.0)with DnX usb driver.
I can provide to you some screenshots if you need them, just ask whatever you need for!
Anyway, now I just wait for any your comunication. Thanks for your patiente and sorry for multiple messages
Click to expand...
Click to collapse
@RemixOS_Jason
here screenshot and log attached!
ps: Also tried to flash it using win7 x64, same error
Hey @bad pixel - I just received an answer from our migration team that I'd like to share with you:
"The reason is that Intel uses different BIOS for Android 4.4 and Android 5.1. The droidboot for Android 5.1 cannot be run on the old 4.4 BIOS. So the flash tool reports an error.
To solve this problem, the user must flash the BIOS first. We do not have CUBE I10's 5.1 bios,
so the user must ask Cube for the new BIOS."
I hope this reply helps. Thanks again!
@RemixOS_Jason Ok i will try to contact them (but I guess it's a waste of time) and explain the situation. I have to ask you one last thing, so please check your pvt.
Many Thanks for your support, I really appreciated your efforts and patiente for this thread
RemixOS_Jason said:
Hey @bad pixel - I just received an answer from our migration team that I'd like to share with you:
"The reason is that Intel uses different BIOS for Android 4.4 and Android 5.1. The droidboot for Android 5.1 cannot be run on the old 4.4 BIOS. So the flash tool reports an error.
To solve this problem, the user must flash the BIOS first. We do not have CUBE I10's 5.1 bios,
so the user must ask Cube for the new BIOS."
I hope this reply helps. Thanks again!
Click to expand...
Click to collapse
Hi, I already provided bad pixel with the droidboot to boot Android 5.1 and the updated bios and its booting with remix 2.0. Could you please send us a link to the latest bios.
Hey tekcomm,
Have I read your comment incorrectly as you seem to state that you're already booting with Remix OS 2.0. The latest bios needs to be supplied by Cube as we do not have them. Please let me know where I've misunderstood and I'll assist you as possible.
Thanks,
Jason
tekcomm said:
Hi, I already provided bad pixel with the droidboot to boot Android 5.1 and the updated bios and its booting with remix 2.0. Could you please send us a link to the latest bios.
Click to expand...
Click to collapse
RemixOS_Jason said:
Hey tekcomm,
Have I read your comment incorrectly as you seem to state that you're already booting with Remix OS 2.0. The latest bios needs to be supplied by Cube as we do not have them. Please let me know where I've misunderstood and I'll assist you as possible.
Thanks,
Jason
Click to expand...
Click to collapse
I already obtained through other means the bios and droidboot that is required. I was wondering if there was a newer version. How can you boot and test remix 2.x without the correct bios?
---------- Post added at 07:20 AM ---------- Previous post was at 07:15 AM ----------
tekcomm said:
I already obtained through other means the bios and droidboot that is required. I was wondering if there was a newer version. How can you boot and test remix 2.x without the correct bios?
Click to expand...
Click to collapse
It does not matter I was just wondering if there was a newer version. Right now I am busy rebuilding the chinese version of the win 10 reference image for the 10-wb and adding remix os 2.0 to it. So it will work on the 10-wb 10-w and 10-r models. Could you do me a favor and double check with one of your devs there is not a bios on mercury.corp.jide.com
We don't actually have any of the BIOS because they're all proprietary to Cube. Please let me know if there's anything else I can assist with. Thanks!
tekcomm said:
I already obtained through other means the bios and droidboot that is required. I was wondering if there was a newer version. How can you boot and test remix 2.x without the correct bios?
---------- Post added at 07:20 AM ---------- Previous post was at 07:15 AM ----------
It does not matter I was just wondering if there was a newer version. Right now I am busy rebuilding the chinese version of the win 10 reference image for the 10-wb and adding remix os 2.0 to it. So it will work on the 10-wb 10-w and 10-r models. Could you do me a favor and double check with one of your devs there is not a bios on mercury.corp.jide.com
Click to expand...
Click to collapse
tekcomm said:
Hi, I already provided bad pixel with the droidboot to boot Android 5.1 and the updated bios and its booting with remix 2.0. Could you please send us a link to the latest bios.
Click to expand...
Click to collapse
Hi, tekcomm. Did you get remixOS 2.0 works on cube i10?
No, I have android 6 installed it came out on the 14 the stable version. To install it install windows 10 first then shrink the partition and install it in the free space. The selection menu even works on boot wwwDOTandroid-x86DOTorg/releases/releasenote-6-0-r2 . The only thing that is not working which is the audio. That is being fixed in the next mainline kernel release. I don't care because I blew up my speakers and use bluetooth anyways.
Btw thats my other account for mediatek devices. If you need any help message my and ill send you my skype.
Related
Hi folks. I'll start off with some disclaimers.
I'm not part of the Jide team or in any way affiliated with RemixOS other than that I was given permission to post an "easy install" package here.
I cannot fix bugs. If you want to tell me about bugs you are welcome to, but there's nothing I can do about them. This thread *may* be monitored by Jide team members, but I cannot guarantee timeliness nor thoroughness.
I am only here to support this thread in regard to "How To Install It". That said, I will try to assist anyone with any issues that I can. I can't fix bugs, but I can answer question and may be able to resolve some issues.
This process WILL WIPE your device, so be sure to back up any important files beforehand.
Now that all that's out of the way, let's get to it.
If you haven't heard about RemixOS, here's a little intro: http://www.jide.com/remixos
Remix is a different kind of Android experience.
The only way to install RemixOS at this moment is through fastboot. I took their firmware files and simplified "flash-all" batch script and packaged it alongside ADB and fastboot. If you already have ADB and fastboot, you can download the firmware directly from Jide and install just like always: http://www.jide.com/remixos/devices/nexus9
If you don't have ADB or fastboot, or just want to speed up your install process, keep reading.
You will need an UNLOCKED BOOTLOADER to do this. Unlocking your bootloader will wipe your device, but so will installing this ROM normally, so again be sure to back up important files. Click the spoiler button in the instructions below to see the additional steps for unlocking your bootloader.
Pre-install: Enable "OEM Unlocking" in Developer Settings. To do this: go to "About Tablet" in Settings. Tap "Build Number" seven times. You'll see a notification that you are now a developer, and now you'll have a "Developer Options section in Settings. Go into Developer Options and enable "OEM Unlocking" by flipping the toggle.
1. DOWNLOAD EASY INSTALL PACKAGE:
https://www.androidfilehost.com/?w=files&flid=92087
2. Unzip the package. Just the .zip file you downloaded, no need to unzip anything within the original .zip file.
3. Boot your Nexus 9 into bootloader mode. (power off tablet, hold "Volume Down" and "Power" buttons simultaneously for 4-5 seconds. You'll see a white screen with multicolor text if successful)
4. Connect tablet to PC via microUSB cable.
To unlock bootloader, if necessary:
A. Hold Shift and right-click within the unzipped folder containing ADB and fastboot tools, then click "Open a command window here". A command prompt will pop up.
B. Type
Code:
fastboot oem unlock
C. This will wipe your device and takes a few minutes. If it reboots afterwards, get back into bootloader mode to continue.
5. Double-click "flash-all.bat", the batch file within the folder you unzipped from the package.
6. Wait for a while. It takes a few minutes. Do not unplug the tablet or turn off your computer during this process. It will reboot automatically when complete.
Congratulations, you are now running RemixOS 3.0!
A few notes for modders:
I was able to root using CF Auto Root.
TWRP works fine for flashing some .zips, but remember this is a heavily modified AOSP so not all mods will work.
I have not tested Xposed.
Layers do NOT work.
If you install a custom recovery or modify /system you will not be able to install OTA updates, you will have to flash the entire package manually.
Awesome! Can't wait to try it. I just left remix because I couldn't stand to run a 5.1 base. But it was always fast and smooth!
Sent from my HTC 10 using XDA-Developers mobile app
Rather than this, a TWRP flashable version would be awesome.
dictionary said:
Rather than this, a TWRP flashable version would be awesome.
Click to expand...
Click to collapse
Make me one and I'll post it up.
Or use the method provided.
Your choice.
Sent from my XT1575 using Tapatalk
Runs beautifully and was a breeze to install! Thanks
Sent from my SM-N930T using XDA-Developers mobile app
how to get lte working?i really need this
mangomonkey00 said:
how to get lte working?i really need this
Click to expand...
Click to collapse
I am not sure it supports LTE. I only have a WiFi Nexus 9, and have no way to test it.
I'll ask @RemixOS_Jason to check on it for you.
I have been using it from when I got N9 from swappa. Tried other custom and stock ROMs. I keep coming back. Been the best so far. The last stock was dp5 haven't tried 7.0
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
borxnx said:
I am not sure it supports LTE. I only have a WiFi Nexus 9, and have no way to test it.
I'll ask @RemixOS_Jason to check on it for you.
Click to expand...
Click to collapse
RemixOS_Jason said:
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
Click to expand...
Click to collapse
its nice but i was able to get lte working on this after the whole installation had to manually flash vendor.img from latest google image
mangomonkey00 said:
its nice but i was able to get lte working on this after the whole installation had to manually flash vendor.img from latest google image
Click to expand...
Click to collapse
From latest Google image, as in from Nougat? Wouldn't any 6.0.1 vendor image work, so long as it was more recent than the ROM build?
RemixOS_Jason said:
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
Click to expand...
Click to collapse
Would love another update for WiFi version as well, but I have two questions.
1. Is there any way we can be given the choice of using our own launcher? It's really frustrating.
2. If we can't, can the option be added back to not have all apps on the home screen? It was present I believe in the previous build, but it's gone again. I could have two apps on the screen, and everything else in the app drawer. Prefer that.
Hey dictionary,
I talked to migration team and, as of my writing, there is no schedule for another update for the the Wi-Fi version.
1) Currently, Remix OS doesn't support other launchers.
2) Putting this feature back into Remix OS for N9's can be done if we gather enough feedback from the community for it. Personally, I totally get the reason you'd rather have clean desktop option, but we have limited resources here and I need for the feature to be asked by many users first.
Thanks and I do hope you understand. Btw, have you tried any of our other products (ie. Remix OS for PC or Remix OS Player?) They both have the clean desktop feature.
Thanks!
dictionary said:
Would love another update for WiFi version as well, but I have two questions.
1. Is there any way we can be given the choice of using our own launcher? It's really frustrating.
2. If we can't, can the option be added back to not have all apps on the home screen? It was present I believe in the previous build, but it's gone again. I could have two apps on the screen, and everything else in the app drawer. Prefer that.
Click to expand...
Click to collapse
RemixOS_Jason said:
Hey dictionary,
I talked to migration team and, as of my writing, there is no schedule for another update for the the Wi-Fi version.
1) Currently, Remix OS doesn't support other launchers.
2) Putting this feature back into Remix OS for N9's can be done if we gather enough feedback from the community for it. Personally, I totally get the reason you'd rather have clean desktop option, but we have limited resources here and I need for the feature to be asked by many users first.
Thanks and I do hope you understand. Btw, have you tried any of our other products (ie. Remix OS for PC or Remix OS Player?) They both have the clean desktop feature.
Thanks!
Click to expand...
Click to collapse
1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great
You may want to try Remix OS Player again if you're still interested as we made some optimizations and now allow you to use all your CPU cores rather than leave at least one core for your host OS and PC.
http://www.jide.com/remixos-player#download
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
QUOTE=dictionary;68895033]1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great[/QUOTE]
RemixOS_Jason said:
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
Click to expand...
Click to collapse
I would also like to have the option of using a clean desktop on my N9
Thank you for the great work, btw!
I used latest 6.0.1 vendor IMG as nougat factory image is not available for lte
RemixOS_Jason said:
You may want to try Remix OS Player again if you're still interested as we made some optimizations and now allow you to use all your CPU cores rather than leave at least one core for your host OS and PC.
http://www.jide.com/remixos-player#download
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
QUOTE=dictionary;68895033]1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great
Click to expand...
Click to collapse
[/QUOTE]
I'll give player another shot later today.
No disrespect to the PM's, but I vehemently disagree. There is no easy way to sort them, and putting all things in folders isn't very aesthetically pleasing. I have well over 60 apps installed, and it's just a jumbled mess. I always run a clean desktop on my devices. I find it much more intuitive having all apps right by my thumb.
If they refuse to, that's fine. I'll try to find a way to just move the launcher and file manager from my Remix OS for PC over to the n9
@dictionary Your opinion is duly noted. I've definitely passed on your opinion to them as well as @KSS2016 's comment.
Let me know how Remix OS Player works out for you. Thanks.
Any word on the LTE easy install package?
Sent from my Nexus 9 using Tapatalk
If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?
famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.
Hi,
When I connect my ZF2 to the PC, I get an error saying USB device not recognized.
Here are some of the troubleshooting steps I've done:
Tried another cable
Tried another pc
Made sure USB debugging is enabled
Select USB configuration is set to MTP
Made sure ASUS drivers are installed an up to date
Uninstalled drivers from device manager
Updated drivers from device manager
Charging port works (even fast charges when I use the right cable)
SD card slot works
Had a technician replace the entire charging board (pcb board)
Specs:
ZOOA 2gb/16gb
Running 6.0.1
CM13 20161219 Nightly
Also, i'm thinking of restoring my phone back to original stock (that's why I would like to be able to connect it to pc) but if there is a way to put it back to stock without the need of a pc, i'm all ears for it. I'd like to give the stock ASUS updates and software a chance now cause ever since I got the phone, I have been on custom ROMs.
I'm running out of ideas.
Message me here or on facebook or maybe even on battlenet. Just please help me.
KyleGerard said:
Hi,
When I connect my ZF2 to the PC, I get an error saying USB device not recognized.
Here are some of the troubleshooting steps I've done:
Tried another cable
Tried another pc
Made sure USB debugging is enabled
Select USB configuration is set to MTP
Made sure ASUS drivers are installed an up to date
Uninstalled drivers from device manager
Updated drivers from device manager
Charging port works (even fast charges when I use the right cable)
SD card slot works
Had a technician replace the entire charging board (pcb board)
Specs:
ZOOA 2gb/16gb
Running 6.0.1
CM13 20161219 Nightly
Also, i'm thinking of restoring my phone back to original stock (that's why I would like to be able to connect it to pc) but if there is a way to put it back to stock without the need of a pc, i'm all ears for it. I'd like to give the stock ASUS updates and software a chance now cause ever since I got the phone, I have been on custom ROMs.
I'm running out of ideas.
Message me here or on facebook or maybe even on battlenet. Just please help me.
Click to expand...
Click to collapse
hello , can you install a fresh copy of cm13 from around October ?
Obviously do a back up of your current set up first , then test.
Adb , USB enabled etc ?
Nothing in fastboot showing either ?
******WARNING !!! Only flash this below if you have 0094.0183 ifwi version in boot loader. !!!!*******
http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
also , just to test this , even though developer options is showing ... do the tap on build number numerous times again
I had that bug a few times after a restart let me know
KyleGerard said:
Hi,
When I connect my ZF2 to the PC, I get an error saying USB device not recognized.
Here are some of the troubleshooting steps I've done:
Tried another cable
Tried another pc
Made sure USB debugging is enabled
Select USB configuration is set to MTP
Made sure ASUS drivers are installed an up to date
Uninstalled drivers from device manager
Updated drivers from device manager
Charging port works (even fast charges when I use the right cable)
SD card slot works
Had a technician replace the entire charging board (pcb board)
Specs:
ZOOA 2gb/16gb
Running 6.0.1
CM13 20161219 Nightly
Also, i'm thinking of restoring my phone back to original stock (that's why I would like to be able to connect it to pc) but if there is a way to put it back to stock without the need of a pc, i'm all ears for it. I'd like to give the stock ASUS updates and software a chance now cause ever since I got the phone, I have been on custom ROMs.
I'm running out of ideas.
Message me here or on facebook or maybe even on battlenet. Just please help me.
Click to expand...
Click to collapse
You may have to update the driver from device manager. I was alsofacing the same issue..
1. Go to device manager.
2.Right click on MTP DEVICE and Select UPDATE DRIVER SOFTWARE
3.Then select BROWSE MY COMPUTER FOR DRIVER SOFTWARE
4.Then select LET ME PICK FROM A LIST..................
5.Uncheck SHOW COMPATIBLE HARDWARE
6.SELECT (STANDARD MTP DEVICE)
7. In the 2nd panel Select MTP DEVICEAND THEN CLICK NEXT.
hope this will solve the problem.
If not send me a screenshot at this email id: [email protected]
Devc100 said:
You may have to update the driver from device manager. I was alsofacing the same issue..
1. Go to device manager.
2.Right click on MTP DEVICE and Select UPDATE DRIVER SOFTWARE
3.Then select BROWSE MY COMPUTER FOR DRIVER SOFTWARE
4.Then select LET ME PICK FROM A LIST..................
5.Uncheck SHOW COMPATIBLE HARDWARE
6.SELECT (STANDARD MTP DEVICE)
7. In the 2nd panel Select MTP DEVICEAND THEN CLICK NEXT.
hope this will solve the problem.
If not send me a screenshot at this email id: [email protected]
Click to expand...
Click to collapse
I'll do this when i get home later.. I'll keep you posted bro.
timbernot said:
hello , can you install a fresh copy of cm13 from around October ?
Obviously do a back up of your current set up first , then test.
Adb , USB enabled etc ?
Nothing in fastboot showing either ?
---------- Post added at 01:12 AM ---------- Previous post was at 01:06 AM ----------
http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
also , just to test this , even though developer options is showing ... do the tap on build number numerous times again
I had that bug a few times after a restart let me know
Click to expand...
Click to collapse
Hi, Yes.. adb and usb enabled.. I did the tap on build number thing and it just said developer options already enabled.. Will try the cm13 install later andI'll also check if fastboot detects it. keep you posted bro.
timbernot said:
hello , can you install a fresh copy of cm13 from around October ?
Obviously do a back up of your current set up first , then test.
Adb , USB enabled etc ?
Nothing in fastboot showing either ?
---------- Post added at 01:12 AM ---------- Previous post was at 01:06 AM ----------
http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
also , just to test this , even though developer options is showing ... do the tap on build number numerous times again
I had that bug a few times after a restart let me know
Click to expand...
Click to collapse
Hi,
Can you point me to an instructional video on how to install a fresh copy of cm13? I just wanna make sure that I do the right steps.
Also, am just curious. Are you also using a zf2 right now? Are you on stock or custom ROM? Since CM13 has been discontinued, i was thinking of switching ROMs. Any particular ROM that you would recommend?
Devc100 said:
You may have to update the driver from device manager. I was alsofacing the same issue..
1. Go to device manager.
2.Right click on MTP DEVICE and Select UPDATE DRIVER SOFTWARE
3.Then select BROWSE MY COMPUTER FOR DRIVER SOFTWARE
4.Then select LET ME PICK FROM A LIST..................
5.Uncheck SHOW COMPATIBLE HARDWARE
6.SELECT (STANDARD MTP DEVICE)
7. In the 2nd panel Select MTP DEVICEAND THEN CLICK NEXT.
hope this will solve the problem.
If not send me a screenshot at this email id: [email protected]
Click to expand...
Click to collapse
Hi,
I tried the instructions but when I get to step # 6, i do not have standard MTP device on the choices.
KyleGerard said:
Hi,
Can you point me to an instructional video on how to install a fresh copy of cm13? I just wanna make sure that I do the right steps.
Also, am just curious. Are you also using a zf2 right now? Are you on stock or custom ROM? Since CM13 has been discontinued, i was thinking of switching ROMs. Any particular ROM that you would recommend?
Click to expand...
Click to collapse
You install like normal , like you did with your current cm13.
What is your ifwi version in Boot loader ?
KyleGerard said:
Hi,
I tried the instructions but when I get to step # 6, i do not have standard MTP device on the choices.
Click to expand...
Click to collapse
what choices do you have?
send me a screenshot.
timbernot said:
You install like normal , like you did with your current cm13.
What is your ifwi version in Boot loader ?
Click to expand...
Click to collapse
How do I check what IFWI version I have?
Its been a year since i unlocked bootloader and switched to CM13, i just do the OTA updates so i forgot how to flash.
Apologies.
Devc100 said:
what choices do you have?
send me a screenshot.
Click to expand...
Click to collapse
Attached the screenshot.
Interesting thing here is under developer options, when i try to change the select usb configuration, it does not let me choose anything aside from charging.
KyleGerard said:
How do I check what IFWI version I have?
Its been a year since i unlocked bootloader and switched to CM13, i just do the OTA updates so i forgot how to flash.
Apologies.
Click to expand...
Click to collapse
reboot to bootloader and what ifwi version is it ?
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi.
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
..
timbernot said:
reboot to bootloader and what ifwi version is it ?
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi.
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
..
Click to expand...
Click to collapse
LP? Lollipop? I'm at Marsh 6.0.1
KyleGerard said:
Attached the screenshot.
Interesting thing here is under developer options, when i try to change the select usb configuration, it does not let me choose anything aside from charging.
Click to expand...
Click to collapse
ZF2 Driver
Download, and install it..
Then in in the driver list search for asus...hope you will find mtp device
KyleGerard said:
LP? Lollipop? I'm at Marsh 6.0.1
Click to expand...
Click to collapse
KyleGerard said:
How do I check what IFWI version I have?
Its been a year since i unlocked bootloader and switched to CM13, i just do the OTA updates so i forgot how to flash.
Apologies.
Click to expand...
Click to collapse
This is the 3rd time i ask for your IFWI version ?
You said its been a year since you installed CM13 , and the chances of you having M BL is virtually none existant
You probably have the LP version of M :good:
Unless someone magically sneaked in your home whilst asleep about July and upgraded your bootloader and installed 3.0.2M twrp.
The reason i asked for your IFWI version.
reboot to bootloader and what ifwi version does it say it is there ??????????
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi version
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
This IS the last time i ask you
timbernot said:
This is the 3rd time i ask for your IFWI version ?
You said its been a year since you installed CM13 , and the chances of you having M BL is virtually none existant
You probably have the LP version of M :good:
Unless someone magically sneaked in your home whilst asleep about July and upgraded your bootloader and installed 3.0.2M twrp.
The reason i asked for your IFWI version.
reboot to bootloader and what ifwi version does it say it is there ??????????
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi version
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
This IS the last time i ask you
Click to expand...
Click to collapse
Apologies. I do not know how to what IFWI version I have. How do I check?
You probably have the LP version of M -- I probably have the lollipop version of Marshmallow?
I am not really well versed with the terminologies now but if you could show me how to check the IFWI version, that'd be great.
......
timbernot said:
......
Click to expand...
Click to collapse
IFWI version is 0094.0173
KyleGerard said:
IFWI version is 0094.0173
Click to expand...
Click to collapse
Thank you - that is LP unlocked bootloader -- if your device is recognised in fastboot ? (was a question i asked you a few days ago but never got a reply to), please follow this :-
There are a few methods to get you back to stock and updated -- i choose the most simplest for you:good:
https://forum.xda-developers.com/showpost.php?p=70096075&postcount=19
timbernot said:
Thank you - that is LP unlocked bootloader -- if your device is recognised in fastboot ? (was a question i asked you a few days ago but never got a reply to), please follow this :-
There are a few methods to get you back to stock and updated -- i choose the most simplest for you:good:
https://forum.xda-developers.com/showpost.php?p=70096075&postcount=19
Click to expand...
Click to collapse
Thank you.
To check if my device is recognized in fastboot, I should connect phone to PC via cable and then reboot to bootloader, correct? I'll do that when I get home.
Would you recommend STOCK or a CUSTOM ROM yourself?
My phone arrived last night. I immediately, following the instructions I found here, magisk'd it. As soon as I flashed the patched image and rebooted... I found that the touch screen had stopped working.
So I booted into recovery (which was hard, because I can't figure out any way to shut my phone down), and wiped data / factory reset. The bootloader is still showing as unlocked. And the touch screen is still not working.
Does anybody know why this might be or what I should do about it? Note that I didn't buy from Google, I bought new from a well-reputed ebay seller...
Send it back. It sounds like a hardware issue.
sic0048 said:
Send it back. It sounds like a hardware issue.
Click to expand...
Click to collapse
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
DanHakimi said:
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
Click to expand...
Click to collapse
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Reflash the factory image and relock the bootloader... It is an official process from Google, if that fails contact the seller and RMA the unit.
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
As it's new and you've got nothing to worry about saving I'd just flash the latest factory image via fastboot and once it's up extract the boot from that image and patch it. The fellow above is probably correct but there is one other thing, use an A to C cord, not the C to C cord for all your flashing.
Bob nesta said:
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Click to expand...
Click to collapse
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
DanHakimi said:
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
Click to expand...
Click to collapse
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
As far as Q - maybe? That's why I said "supposedly" it comes out the 3rd (https://www.theverge.com/platform/a...ndroid-10-pixel-september-3-release-leak-date) , but there are no guarantees in life (except death & taxes).
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
DarkShadowMX said:
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
Click to expand...
Click to collapse
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
krabman said:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
Click to expand...
Click to collapse
Yes, A to C.
Bob nesta said:
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
Click to expand...
Click to collapse
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
DanHakimi said:
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
Click to expand...
Click to collapse
Please do. I'm no dev & can probably offer little to no help, but if you post your errors someone else may be able to help you out.
It could just be a cable/driver/fastboot issue & not the phone, so please provide error info.
Ok, do the full smash. This assumes a basic familiarity with flashing mechanics.
1. Download and install the latest fastboot package.
2. Download the latest image from google again.
3 Use a known good A to C usb cord
4 Before flashing the image type all the following commands one by one in fastboot...
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
5 Flash the image using the flash all script.
6 Once you're up extract the boot from the image you flashed and patch it in magisk.
7 Flash the patched boot image.
DanHakimi said:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
Click to expand...
Click to collapse
I don't either. I used a USB OTG cable
Had a **** ton load of issues trying to go from rooted and TWRP with custom rom to Android 10.. Every time I ran the flash-all.bat it would fail at one stage or another.. Finally grabbed the Pie Ota from the site, sideloaded it through TWRP then wiped everything through stock recovery and then took the Android 10 update. My point is, use the OTA and sideload it
I was rooted on Android 10 beta 6 and trying to download the OTA through the phone update failed every time. I uninstalled magisk and restored images..but still failed. I finally had to sideload the OTA image and it finally updated. That was the only way to get mine to work. Then I took the boot image from beta 6 that was already patched through magisk and re-flashed it because the boot image from Android 10 official patched through magisk would not give root...kept failing. Then when I re-flashed last months beta 6 image, upon reboot the screen would freeze and no apps would load. I then booted into recovery and did a factory reset and upon reboot magisk was identified and root was acquired....phone worked perfectly after that and no issues....weird. I then just reloaded all of my apps from backup and was on Android 10 official, rooted through magisk.
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
DanHakimi said:
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
Click to expand...
Click to collapse
I suspect you are running out of hard disk space on the computer that you are using to try to flash all this with. I ran into a similar issue once when the C drive of my computer was nearly full. The system file ends up needing a lot of disk space in order for it to be unpacked. The error you are getting is that you are running out of space and it cannot unpack it. Again, this isn't phone memory space, this is actual computer hard drive space.
I'm trying to install Lineage OS on my phone and I have followed all the steps (plus many more they just assume you'll know) from this site, up to configuration because adb no longer discovers my phone.
.\adb devices
.\adb fastboot bootload
literally anything to do with adb doesn't work but it did an hour ago. Now I'm worse off because my phone will only upload to bootload and not to the actual homescreen so there's no going in and double checking if my USB debugging is on (it was before the reset) and I can't access my phone at all, nor can I get things configured. I've updated the drivers via web, deleted and retried the drivers, and restarted the computer. I don't know what I'm supposed to have on my computer that would better upload the drivers. I don't have a clue what any of this is supposed to mean, I was forced to do all of this **** because of the recent Adroid 12 update that I couldn't get rid of without just getting a different OS. Please please please make it dumb for me and tell me how I can get my phone back and download this OS.
Try fastboot commands in bootloader
yesca213 said:
Try fastboot commands in bootloader
Click to expand...
Click to collapse
Yes fastboot commands work but I need to copy this in the command prompt
.\adb sideload copy-partitions-20210323_1922.zip
The tutorial says it isn't an optional step. When I try doing this with fastboot, it tells me:
fastboot: usage: unknown command sideload
Try "fastboot reboot" or "fastboot reboot bootloader"
yesca213 said:
Try "fastboot reboot" or "fastboot reboot bootloader"
Click to expand...
Click to collapse
Thanks! I tried it with no change. adb can still not discover my phone and it doesn't start back up, only brings me to FastBoot mode screen.
If it's Windows your using it may be a driver issue.
yesca213 said:
If it's Windows your using it may be a driver issue.
Click to expand...
Click to collapse
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
johnmtrowbridge said:
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
Click to expand...
Click to collapse
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
heyhowyoudoin said:
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
Click to expand...
Click to collapse
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
johnmtrowbridge said:
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
Click to expand...
Click to collapse
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
heyhowyoudoin said:
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
Click to expand...
Click to collapse
Yeah I'm gonna just have to try in a few hours because the only way Signal works on my desktop is if I verify it on my phone lol. Again, the phone is completely stuck on FastBoot mode and anytime I restart it it takes me right back, which I think is probably because of the recovery mode I just installed.
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
heyhowyoudoin said:
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
Click to expand...
Click to collapse
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
heyhowyoudoin said:
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
Click to expand...
Click to collapse
There wasn't a recovery version of 11 at the time that I could find, not for the 9 Pro. So what do I do now, do you know how I at least get my phone off of FastBoot mode to try this **** all over again?
johnmtrowbridge said:
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
Click to expand...
Click to collapse
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Index of /list/Unbrick_Tools/OnePlus_9_Pro
or download version for your phone from link above
heyhowyoudoin said:
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
Click to expand...
Click to collapse
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
heyhowyoudoin said:
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Click to expand...
Click to collapse
NA I'm in America
johnmtrowbridge said:
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
NA I'm in America
Click to expand...
Click to collapse
yes, that's what I mean. is your phone linked to t mobile?
at the moment it is not possible to install any custom OS from version 12 of android, not only lineageos