Related
Before you Begin:
This guide is a basic how-to for installing a custom ROM & its update for the Galaxy Tab 10.1v… For all those who struggled (like me)
Also, this is for Windows… If requested, I’ll dig up the Linux method.
REMEMBER: This is all done at your own risk.None of the people mentioned, or myself, can be held responsible for any damages caused! Following these steps will void your warranty.
If you are not comfortable, don’t do it!
Always keep a backup of your data; it will get lost at some point during this!
(Titanium Backup, Rom Manager etc can create backups… use ‘em!)
This guide assumes you’ve already unlocked & rooted your Tab. If you haven’t, check these threads:
(Much thanks to these gents!)
Bcmobile’s unlock thread
Chainfire’s unlock thread
Bcmobile’s rooting thread
I recommend Chainfire’s method to unlock – you get a stock ROM (unlocked) + ODIN3 in case something goes pear-shaped…
PM me if there is something I’ve missed, need to take down or redo.
I do not provide support for the ROM(s)/ programs mentioned; go to the appropriate thread (list at the end).
Above all: have fun and thank the devs who put in so much time!
Required Packages:
Java SDK – found here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Android SDK – Found here:
http://developer.android.com/sdk/index.html
USB Drivers – install via Android SDK Manager. See here:
http://developer.android.com/sdk/installing.html
(USB Package r4)
USB Note:
After installing the drivers via the Android SDK Manager, navigate the folder where you installed the Android SDK, and look for a folder called ‘extras’. Open that, then open the folder ‘google’, then ‘usb_driver’. Edit the android_winusb.inf file and insert the following text under the section [Google.NTx86] (32bit Windows) or [Google.NTamd64] (64bit Windows):
========
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
========
All other files needed are mentioned under their specific section.
Ok, now onto the good stuff…
===============================================================================
Installing a custom ROM:
(I’m using Seo’s ROM purely as an example, as it includes a wipe file and updates. You can use whichever rom you like/ want/ need. Just check the rom’s thread/ site for any special instructions)
This example uses the TB Galaxy ROM, it can be found here - http://forum.xda-developers.com/showthread.php?t=1155023
You’ll need to download V1.0 FULL ROM, whichever update you need/ want (this guide uses 1.0.9), and wipe.zip.
Place the downloaded .zip files in your Android SDK \tools or \platform-tools directory (whichever one has adb.exe in it)
[FONT="]1) [/FONT]Download and install Rom Manager from the Android Market (The free one is fine).
[FONT="]2) [/FONT]Open Rom Manager, and select ‘Flash Clockwork Mod Recovery’ (CWM). If you used bcmobile’s unlock method, you can use Rom Manager to back up your stuff, just remember to copy it off the Tab before moving on!
[FONT="]3) [/FONT]Once it has completed, connect the Tab (powered on) via USB (debugging enabled) and open a command prompt. Navigate to your Android SDK’s \tools folder and type:
adb devices
[FONT="]4) [/FONT]Now, push TB-Galaxy-1.0.zip to /sdcard/:
adb push tb-galaxy-1.0.zip /sdcard/
Copy the 1.0.9 OTA update zip as well as the wipe.zip using push.
Check the attached file for the pic...
(Mine has nothing listed after devices, as I didn't connect my Tab...)
NOTE: Seo’s instructions call for copying the file(s) to /sdcard/media/, but for some reason CWM does not let myself see that folder…
[FONT="]5) [/FONT]After it has copied, type:
adb reboot recovery
[FONT="]6) [/FONT]Once in Recovery, navigate with the volume keys, and select ‘Install Zip from sdcard’ with power button (TAP to select). Browse for the wipe.zip and select it. Select ‘Yes’.
[FONT="]7) [/FONT]After the has been completed, install TB-Galaxy-1.0.zip.
[FONT="]8) [/FONT]After it completes, navigate back to the first CWM menu and restart/reboot the tab. Be aware that the first boot may take a while.
[FONT="]9) [/FONT]If all is well, you should be seeing your new home screen… Check it out!
========
If you’re stuck in an endless bootloop or it gets stuck at the Samsung logo screen, go to chainfire’s unlock thread (link at top of page) and follow the steps there. You’ll have the stock ROM loaded back on, with the bonus of the bootloader being unlocked.
========
[FONT="]10) [/FONT]Update time… Connect the Tab via USB, enable debugging, open a command prompt and navigate to the Android SDK tools folder and reboot into recovery: adb boot recovery. Follow step 6, but select the OTA zip instead of wipe.zip.
[FONT="]11) [/FONT]Once that completes, reboot & enjoy. Done!
List of links/ threads:
Rom Manager:
https://market.android.com/details?id=com.koushikdutta.rommanager&feature=top-free
Packages/ Drivers:
Java SDK – found here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Android SDK – Found here:
http://developer.android.com/sdk/index.html
USB Drivers – install via Android SDK Manager. See here:
http://developer.android.com/sdk/installing.html
(USB Package r4)
ROMs: (some to play with )
TB Galaxy thread by Seo:
http://forum.xda-developers.com/showthread.php?t=1155023
ISI-Galaxy thread by isimobile
http://forum.xda-developers.com/showthread.php?t=1223131
Rs HDBlog Galaxy thread by Rs125
http://forum.xda-developers.com/showthread.php?t=1200985
Thanks for this.
However to Windows users who just can't get the proper drivers to work (like my case, I tried every method for a week), just install Ubuntu. Way easier...
DannyBiker said:
Thanks for this.
However to Windows users who just can't get the proper drivers to work (like my case, I tried every method for a week), just install Ubuntu. Way easier...
Click to expand...
Click to collapse
You're welcome.
The fix by modifying the android_winusb.inf and pointing Windows to it cleared the problem for me, as did installing Samsung Kies and letting it auto-install the driver.
Otherwise, Ubuntu could work...
Yeah I know it works for most of people but check the latest posts in all the guids topics, I tried almost everything, doing things right but Xp or 7 could never connect to the tab.
I'm just saying, as an info, that if someone encounters the same issue, Ubuntu (or Linux) is the answer...
Works like a charm. Can I remove the .zip files afterwards?
Fadawah said:
Works like a charm. Can I remove the .zip files afterwards?
Click to expand...
Click to collapse
As long as you've checked that everything is working 100%... if it is, go ahead and remove them
Hi guys, time to cry for a little help here...
today I've managed to get 3.2 loaded on my p7100. everything went well and I was really enjoying it, until I got a crappy app that started to freeze the tab before I could remove it (AVG 2.9). I tried everything I could and after a "fastboot -w" the tablet entered in an endless loop mode, restarting all the time. I've fixed that flashing the stock rom using ODIN, but now I cannot get into clockworkmode to reload the 3.2 rom. every time I enter "fastboot boot recovery.img" (clockworkmode recovery image), it displays on the tab "Booting downloaded image" but doesnt go any further... dont know what to do now... it is working fine with 3.0.1, but I cant get 3.2 back.
thanks a lot for your help, it is much appreciated !!!!
Cheers
S.
Forgot to mention: trying to boot into recovery mode leads to a screen with the android dude and a big yellow exclamation mark (adb reboot recovery) and nothing else happens.
sitani said:
Hi guys, time to cry for a little help here...
today I've managed to get 3.2 loaded on my p7100. everything went well and I was really enjoying it, until I got a crappy app that started to freeze the tab before I could remove it (AVG 2.9). I tried everything I could and after a "fastboot -w" the tablet entered in an endless loop mode, restarting all the time. I've fixed that flashing the stock rom using ODIN, but now I cannot get into clockworkmode to reload the 3.2 rom. every time I enter "fastboot boot recovery.img" (clockworkmode recovery image), it displays on the tab "Booting downloaded image" but doesnt go any further... dont know what to do now... it is working fine with 3.0.1, but I cant get 3.2 back.
thanks a lot for your help, it is much appreciated !!!!
Cheers
S.
Forgot to mention: trying to boot into recovery mode leads to a screen with the android dude and a big yellow exclamation mark (adb reboot recovery) and nothing else happens.
Click to expand...
Click to collapse
Is your bootloader unlocked?
Sent from my GT-P7100 using Tapatalk
yep, I think so
Hi Isimobile, thanks for your help.
I believe it is unlocked (can see the open padlock when I turn it on, fastboot mode says unlocked and I even tried "fastboot oem unlock" once again to make sure). dont know what else to do. It seems there's something wrong with the restore partition (hope Im not saying anything nonsense here).
Cheers
S.
Thanks for the tip.
will someone please tell me why clockwork recovery is messing up my Tab? I rooted and unlocked, then went to install it through ROM manager. it says installed correctly I click the option to reboot into recovery and my Tab is suddenly bricked please help I have no backups and my Tab says the update failed and I need to select recovery in Kies. however Kies won't recognize my device
automaddux said:
will someone please tell me why clockwork recovery is messing up my Tab? I rooted and unlocked, then went to install it through ROM manager. it says installed correctly I click the option to reboot into recovery and my Tab is suddenly bricked please help I have no backups and my Tab says the update failed and I need to select recovery in Kies. however Kies won't recognize my device
Click to expand...
Click to collapse
Did you flash or boot recovery. Img
I had the same problem using rom manager when trying to get in cwm, exept i got the exclamation mark with the android.
I Let it rest for a while and it booted fine.
Don't know wich rom your on but you should first flash recovery then reboot in recovery..
Sent from GT-P7100 running android 4.0.3
Great ! Thank you ! It will help me to level up my 10.1v !
My tab after flasing doesnt wake up. Its mean that ot start and stock on boot samsung animation
I try flash it again but i still have the same sitiation
There is any option to upload all factory soft agaon. I eant to mantion that i wad try to recovery from backup but i get error for data files
Thanks in advance
Sent from my GT-I5800 using XDA App
Tab 2 10.1
Hi, does this same method work for the Samsung Galaxy Tab 2 10.1? I am trying to install the infected ROM on it. I would appreciate the help, as you can tell, I am new here!
prejudice to any forum.
I state that I'm an Italian who speaks no English, he writes, so forgive me for possible misunderstandings, but I'm posting the translation running google.
So are the owner of the Nexus 9023's version and then I wanted to try ICS via the Tools Cescomn I first unlocked the bootloader then root permissions and then I put a rom ics moddata atrraverso the recovery that I have changed as the guide told me. Then again, I want to change rom and then I decide to put the rom 4.0.3 Stock. So attraverlo the usb cable connected to the device I transfer the file ZD3PyN0t.zip from about 160MB. Reboot the device into fastboot recvovery I access the run and wipe and then install the rom. I was faced with the device locked with the recovery (after logging in and selecting the recovery fastboot I get black screen and then after a while you start the device) so everything is ok nothing anormale.Il problem is that there is to recognize the device in windows (both x32 and win7 win7 x64 win xp) I did the test with a nexus s aggiornatosi via ota to ics and then he immediately recognized the driver I've tried are good. Windows tells me unknown device unknown device or manually by selecting the driver. If you check the details of the device exactly match that of my friend who received ICS by ota.
What can I do?
try install google driver first
download it from here android sdk
this is the instruction
http://developer.android.com/sdk/win-usb.html
Done and redone.
facts of the problem occurs with my device, with that of a friend of mine (who has received ics via ota) no problem installing everything perfectly.
Putting it in download mode I recognized the same.
someone give me a tip?
Go to windows, manage devices, search for your phone, driver, update driver, select manually, choose android device and point it to the driver files. If it still does not work, i say you reflash your rom..
Sent from my Nexus S using XDA
Lazer Bear said:
Go to windows, manage devices, search for your phone, driver, update driver, select manually, choose android device and point it to the driver files. If it still does not work, i say you reflash your rom..
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I tried many times to install the driver manually and do not go.
Now maybe I understand the problem .. a few days ago I got the ota update to 4.0.4 ics, the nexus has downloaded and installed.
The recovery tells me it's always locked, but after you press recovery from fastboot you press vol + + power and the recovery appears.
Turning the menu will not find anywhere the written MPT.
How can I fix?
The CWM does not make me install.
give me help.
thanks
Hello, I believe my kid had rebooted my tablet during an OTA update. I've been diligently reading page after page of posts trying everything possible to reflash this.
What I know:
- a500 16GB / win8 server / debian VBox
- a500 was rooted prior to OTA update
- can enter apx ( blk screen, wht power) and recovery mode (loads update.zip)
- I can get most recovery update.zip's to start, but so far, all have failed.
- A500 manager detects a500 in APX mode but states i need to install drivers. (repeated this many times)
- nvflash does not communicate (i'm thinking due to the incompatible drivers)
- "fastboot.exe devices" returns nothing- SBK and CPUID
What I don't know:
- the last version of OS on the a500. Maybe HC?
- if the device retained USB debugging before it bricked
- whether or not I installed CWM or other needed programs (was almost 3 years with no issues)
I have tried any images i can locate; mostly in the forums here. I'm not positive if I can just load them from SD, in recovery boot ( if the files are correct format) or if I need prior steps. I have tried every zip making sure it's "update.zip" although the contents of each are not always the same.
Any ideas or perhaps "guide for idiots" would be greatly appreciated.
Thanks!
edit: so I have located the CPUID and managed to find a working SBK calculator. Now I'm having issues related to .NET 2.0 when running the nvflash utility? I'll attempt an XP vbox to see if it's now due to win8.
new edit: the drivers don't seem to work on Win 8 or 7. I tried installing an XP vbox but I am not able to activate, therefor install proper utilities for the nvflash program.
It seems I'm stuck, unable to work around the .NET 2.0 conflict and the driver installation.
Perhaps I'll start looking at linux alternatives and hope someone could provide some more of an updated approach.
Check this: http://forum.xda-developers.com/showthread.php?t=1585907 and/or this: http://forum.xda-developers.com/showthread.php?t=2755126 to unbrick your tablet and begin your unlocking process again.
Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!
This can be done without a toolkit, Flashing factory image with fastboot instead.
Toolkits cause many of the issues on here, learning to do it manually with fastboot can both avoid issues, and fix issues. And teach people valuable skills.... As adb/fastboot are essential tools, especially with a Nexus. ?
But thanks for the info. Contributions like this are always good. ?
Problems with "Boot Failed"
visnkmr said:
Requirement :
Should haveWugfresh Nexus Root Toolkit installed on your computer [with all updates installed ( not necessary),Should wait for it to download necessary updates for your device ( If no net connection then also no prob just wait) ]
( To download nrt visit wugfresh site(can't post link soory) )
You should how to connect your device using nrt, else, follow these steps,
Navigate to about phone section, while you are in the About Phone section, click on the Build Number option seven times to enable Developer mode. Then,go back to settings menu scroll down to developer options, in the Developer mode options, enable USB debugging. A screen will pop up on your phone when the program attempts to make a connection. Make sure to allow it.
Installing drivers :If the program and computer aren't recognizing your device, you will have to install software drivers. In the Nexus Root Toolkit, click on the "Full Driver Installation Guide" button and follow steps one to four. This is the most difficult part of the process. Be sure to follow the steps exactly.
Should know how to boot into bootloader.( can't post a link on where to find out sorry)
How to find if your nexus is bricked:
You see a message "Boot failed...." on your device.
The device is not booting but is staying on boot animation screen for long time (>30 minnutes).
The device is bootlooping means the device is rebooting again and again upto boot animation.
And any other problem that might result in your device, not being able to boot.
What you should do:
Don't panic this error is 100% rectifiable.
if you happened to end up in "boot failed" message on your device after the computer you were using switched off halfway through the flashing process.Then you have to restart your computer and then boot your nexus into bootloader mode and connect it to your computer.
Open Nrt ( Nexus root toolkit)
You should select change in your model type and set "select the android build you are currently running to the version of android you were trying to flash if you were trying to flash some other ROM, then just leave this step.
Then select "soft-bricked or bootloop" or "device is on or normal" depending on your device's current state and press on "Flash stock + Unroot".
you will have to either download a factory image and browse to it when asked so by the software, or let the software download it for you.
( For obtaining factory image for your nexus and search for your device based on build number of your device... )
All the screen on your computer read and do as necessary (Most of the times it is "OK" button that you have to press)
The device should be back to normal after it reboots.
Else just let me know......!
Click to expand...
Click to collapse
Well I had a different kind of problem.
My Nexus was running fine in 4.4.4 when I rooted it since it was out of warranty. It upgraded to Lollipop 5.0 without a problem and continued to function in rooted state.
It made several attempts at updating to 5.0.2 but always ended with "Failed" message. I figured unrooting the device might help with the OS upgrade. It did not and screwed up everything. I then Set it to Factory default and it went to wiped 5.0 state. Then disaster struck. I tried rooting it , unfortunately with older Chainfire which bricked the device and would not let me install 5.0. So I tried to force install 4.4.4 and then the device got bricked. I simply get the message "Boot Failed" I boot into fastboot mode and I get the basic display with green start in the upper right corner, large Android icon in the center of the screen and the standard fine text on the lower let side. Unfortunately Windows ( x64 - Ultimate) insists on recognising the device as "Unknown Device" and when I go into properties this is is what is states ...
"Windows has stopped this device because it has reported problems. (Code 43)"
Do you think I might have better luck if I tried this on a Win XP machine ? I have both, x86 and x64.
Now, can you please tell me how I can get around this problem ?
BTW I do remember olden days of Cassiopeia PDAs before the flash memory came on the stage. The original OS would be on a plugged in masked rom daughter board in the event of losing all battery power. You could always force it to load it and get to factory mode. I think it is high time Android device manufacturers reverted to this process. I believe it can live side by side with the current system at a very marginal higher cost but have a whole lot of satisfied and LOYAL customers. It would give the user ability to go to factory mode albeit without any OS updates/upgrades but a fully functional device.
Would very much appreciate your feedback.
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Uhm... no replies till now?
i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help
When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere
I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.
Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.
These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.