Related
I was trying to root my nexus 7 but didnt switch on usb debugging. It is now in a bootloop i suppose (stuck with the google logo and unlocked lock). I have searched on alot of forums and tried them but i think i failed because the usb debugging function is not switched on. I still can access bootloader as well. Please advise. Thank you.
Also, i tried to go to recovery mode but it will go straight to the bootloop
Don't you think it's the normal problem? Try fastboot -w in bootloader.
Sent from my Nexus 7 using Tapatalk 4
Try this tool(If you are using the Wifi version, stay clear if you are using a LTE version) :[TOOL] 08/23/13 One Click Factory Restore (dead or alive) updated w/ JSS15Q images, a lot users reported that it works very well for restoring bricked/bootlooped N7s, I once used it to wipe my unlocked & rooted N7 and go back to stock and it worked like a charm.
NovaSense said:
Try this tool(If you are using the Wifi version, stay clear if you are using a LTE version) :[TOOL] 08/23/13 One Click Factory Restore (dead or alive) updated w/ JSS15Q images, a lot users reported that it works very well for restoring bricked/bootlooped N7s, I once used it to wipe my unlocked & rooted N7 and go back to stock and it worked like a charm.
Click to expand...
Click to collapse
Thing is, my usb debugging is disabled
Sahmadi said:
I was trying to root my nexus 7 but didnt switch on usb debugging. It is now in a bootloop i suppose (stuck with the google logo and unlocked lock). I have searched on alot of forums and tried them but i think i failed because the usb debugging function is not switched on. I still can access bootloader as well. Please advise. Thank you.
Also, i tried to go to recovery mode but it will go straight to the bootloop
Click to expand...
Click to collapse
When you access bootloader, do you see the "START" option on the right of the screen with the arrows going up and down?
Sahmadi said:
Thing is, my usb debugging is disabled
Click to expand...
Click to collapse
You don't need USB debugging for fastboot operations. As a matter of fact USB debugging is only used to conveniently boot the Nexus into the bootloader, so you don't have to press any buttons on the device.
Guhrasoh said:
You don't need USB debugging for fastboot operations. As a matter of fact USB debugging is only used to conveniently boot the Nexus into the bootloader, so you don't have to press any buttons on the device.
Click to expand...
Click to collapse
Indeed. That's not the problem.
Sent from my MB860 using xda app-developers app
Hi guys!
So, my sister got a Galaxy Ace II yesterday with some ode stuff, then I decided to install Cyanomod 11, BUT more problems appered:
1 - My Windows 7 (64bits) doesn't recognize the drivers.. so it no even list the phone as conected. I tried using Kies to detect and a bunch of packages of drivers of this smartphone model, but till now haven't made any progress... what can I do?
2 - I reseted the phone to original especifications by his own menu and tried to acess its Download and Recovery mode by pressing the 3 buttons at the same time(Vol UP + Home + Power), but for my surprise it didn't boot like it should, jus initializing normaly...what can I do?
3 - I realized, when it booted, that the boot animation has been changed, samsung logo doesn't apper ever and including I found some stuff installed that doesn't seem to be something that generic stock roms have instaled; this made me think that the room installed is not its stock. If that's so, maybe the problems listed above are resolved, but still so I don't know what to do...
I want to install Cyanomod 11, but need the phone recognized for Windows, it rooted and in download mode, but haven't find a way to begin if my computer doesn't reconize it...
Any Help?
Sant Mark said:
Hi guys!
So, my sister got a Galaxy Ace II yesterday with some ode stuff, then I decided to install Cyanomod 11, BUT more problems appered:
1 - My Windows 7 (64bits) doesn't recognize the drivers.. so it no even list the phone as conected. I tried using Kies to detect and a bunch of packages of drivers of this smartphone model, but till now haven't made any progress... what can I do?
2 - I reseted the phone to original especifications by his own menu and tried to acess its Download and Recovery mode by pressing the 3 buttons at the same time(Vol UP + Home + Power), but for my surprise it didn't boot like it should, jus initializing normaly...what can I do?
3 - I realized, when it booted, that the boot animation has been changed, samsung logo doesn't apper ever and including I found some stuff installed that doesn't seem to be something that generic stock roms have instaled; this made me think that the room installed is not its stock. If that's so, maybe the problems listed above are resolved, but still so I don't know what to do...
I want to install Cyanomod 11, but need the phone recognized for Windows, it rooted and in download mode, but haven't find a way to begin if my computer doesn't reconize it...
Any Help?
Click to expand...
Click to collapse
2. did you hold the buttons? another way is to use quick reboot from play store
3. cyanogenmod has its own bootanimation -.-
teddytsen said:
2. did you hold the buttons? another way is to use quick reboot from play store
3. cyanogenmod has its own bootanimation -.-
Click to expand...
Click to collapse
Yes, I hold the 3 buttons at once and waited to it boot, but it jus performed the normal boot, it didn't get into download or recovery mode... I tried many times, but it's always the same...
And I know that CM has it's own boot animation, I know it, but it's not it this time... it's another one... and for what I know, it's not the samsung original one...
Having Kies installed is counterproductive to installing flashing drivers (and if you sync contacts and calendars with Google I can't even think of why you need it :angel
Try unplugging the cable while entering recovery, the LPM mode (charging while "off") screws it up (but download mode should work!)
And by "no Samsung logo", you mean not even the firmware's "Samsung GALAXY ACE 2 GT-i8160"? Sounds like you got a fake then...
But if it boots, you should check the Settings/About menu and tell us the "build version", often that's enough to know what ROM is on it now
Sant Mark said:
Yes, I hold the 3 buttons at once and waited to it boot, but it jus performed the normal boot, it didn't get into download or recovery mode... I tried many times, but it's always the same...
And I know that CM has it's own boot animation, I know it, but it's not it this time... it's another one... and for what I know, it's not the samsung original one...
Click to expand...
Click to collapse
oh, this is logo from my "the blue job" v1 xD
Ryccardo said:
Having Kies installed is counterproductive to installing flashing drivers (and if you sync contacts and calendars with Google I can't even think of why you need it :angel
Try unplugging the cable while entering recovery, the LPM mode (charging while "off") screws it up (but download mode should work!)
And by "no Samsung logo", you mean not even the firmware's "Samsung GALAXY ACE 2 GT-i8160"? Sounds like you got a fake then...
But if it boots, you should check the Settings/About menu and tell us the "build version", often that's enough to know what ROM is on it now
Click to expand...
Click to collapse
Ryccardo, I installed Kies in the hope of having the drivers easylier recognized... But that was not my luck...
About that trick could you be more especific? Do I put the phone off with the cable plugged to PC and when I press both 3 buttons I unplug it?
About the version it is :
DM_BASE_12A_W12.43|sc6820_modem|11-02-2012
And this means that??? It's not the original one, right?
Thanks for the help in advance!
Enviado de meu XT925 usando Tapatalk
Sant Mark said:
Ryccardo, I installed Kies in the hope of having the drivers easylier recognized... But that was not my luck...
About that trick could you be more especific? Do I put the phone off with the cable plugged to PC and when I press both 3 buttons I unplug it?
About the version it is :
DM_BASE_12A_W12.43|sc6820_modem|11-02-2012
And this means that??? It's not the original one, right?
Click to expand...
Click to collapse
Recovery mode is: with power off, hold up+home+power (if it's on, it will reset since you're holding down power... keep holding it) and download mode is the same with down+home+power...
But that version is VERY dubious, the standard Ace never had "SC6820" (maybe it's the L model?) and I don't even think it was out at the start of 2012...
Rox said:
oh, this is logo from my "the blue job" v1 xD
Click to expand...
Click to collapse
Rox, is it the DM_BASE_12A_w12.43| sc6820_modem| 11-02-2012
Really your Blue job Ron?
Enviado de meu XT925 usando Tapatalk
I am saying that bootanimation is from my blue job, i dont know what rom are you using. can you screenshoot "about phone " ?
And a photo of the back without cover and battery... I suspect something...
Rox said:
I am saying that bootanimation is from my blue job, i dont know what rom are you using. can you screenshoot "about phone " ?
Click to expand...
Click to collapse
Enviado de meu XT925 usando Tapatalk
Strange, afaik galaxy ace 2 is shipped with 2.3.6 android.
Did you succed booting in downlaod mode ( Vol down + home + power )
you have to flash Stock JB and we will see what is going on
Rox said:
Strange, afaik galaxy ace 2 is shipped with 2.3.6 android.
Did you succed booting in downlaod mode ( Vol down + home + power )
you have to flash Stock JB and we will see what is going on
Click to expand...
Click to collapse
When I Google it I noticed it too..
No, I still couldn't reboot it nor in download nor in recovery mode...
Even doing what Ryccardo said, it still boots normally..
Enviado de meu XT925 usando Tapatalk
So could you please post a photo of the sticker under the battery (preferably with the entire inside back of the phone showing)?
Ryccardo said:
So could you please post a photo of the sticker under the battery (preferably with the entire inside back of the phone showing)?
Click to expand...
Click to collapse
Sorry but I'm new here ant they made me wait 5 minutes to be able to post...
Enviado de meu XT925 usando Tapatalk
Ah, sorry, I remember how much the <10 post restrictions sucked
But back to your problem, this is not an Ace 2... I suspected it since you posted that version number:
Googling "sc6820_modem" has http://www.pandawillforum.com/archive/index.php?t-18643.html at the end of the 1st page
2nd post there mentions "Star I8160"
Googling "Star i8160" on images shows http://www.gldron.com/media/tmp/catalog/product/6/4/64cfade20f06e0e31ffd853fb1f8009a.jpg as 5th result... while searching the version number on images shows a lot of Samsung clones...
Unfortunately you have fake galaxy ace 2 (
You cant intall any rom on that device
Sent from my GT-I8160 using Tapatalk
By this you both mean I don't have much to do to change the rom?
Enviado de meu XT925 usando Tapatalk
Sant Mark said:
By this you both mean I don't have much to do to change the rom?
Click to expand...
Click to collapse
You surely can't use roms from these forums... There may be other roms for your device but you'll have to find out what it actually is first, which can be somewhat difficult...
Poor sister of mine.. She won't be happy in knowing this...
Anyway I wanna thank you Ryccardo and Rox!
You both Saved me a bunch of tie searching a solution that doesn't existed...
Thanks guys!
Enviado de meu XT925 usando Tapatalk
Hi All,
If you have some experiences with some situation like this, pls give some advices.
I have my Zl, upgraded to 5.1.1 (10.7.A.0.222) , it work fine for some week, then usually shutdown suddenly, 5.1.1 upgraded from 5.0.2 with rooted, installed xposed and some modules (but not unlocked bootloader) .
After some random hanging and rebooting, i try to flash brand-new from ftf file .
and BTW, i unlocked bootloader, after flash new ftf, system cannot boot up, only show up the Sony logo, then down, after that fastboot and flash older ftf ones normally , event i try to relock bootloader.
while unlocked bootloader, i try to install CM ROM, flash boot.img one but still not up.
While connect the charger, logo sony blink for every 10s (estimation) .
I consider the TA partition affected to booting processs. (i have backuped TA but still don't know how to restore via fastboot/flashtool)
Thank and appricated for reading till this point.
Hope you can give me and someone who encounter this situation some wise advices , i will report each try
This is more clear explanation (just read this ):
My case:
1./ first version is 4.4.2, then i try to flash to 5.02 via flashtool (as i remembered i flash ftf version for Generic US)
2./ Then root/install xpose .... and update to OTA (failed), success with updating via Sony Companion, after that, backup TA.
3./ using normally for some weeks, then occur suddenly hang, reboot, lose signal, i commit to flash a brandnew one
4./ After that i unlockbootloader via sony site, Flash 5.1.1 (10.7.A.222 but customized os)
5./ Try some solutions:
5.1/ (unlocked bootloader)Try to flash some other custom kernel (ex: CM12 kernel, one in this dev subforum) but the symptom as case 5.2 below
5.2 try to relockbootloader install the 5.1.1 Generic US/Customized US still doesn't boot up,
- Unplug charger, press and hold power butter, red light blink for 3 times (although connected to charger all night)
- Connect to charger, not show up the charging progress bar, just blink Sony - Xperia around every 10 s
Still consider to battery issue , hope to hear any experienced/wise advises
Click to expand...
Click to collapse
Any ideal about between Customized US/ Generic US ?
Sony tool "Emma" will bring your xperia back with the latest original Sony Rom.
Gesendet von meinem C6503 mit Tapatalk
web.a said:
Sony tool "Emma" will bring your xperia back with the latest original Sony Rom.
Gesendet von meinem C6503 mit Tapatalk
Click to expand...
Click to collapse
Thank @web.a
Will try and report later, do i need relockbootloader /restore TA partition or not.
Brs.
My Bootloader is unlocked and it works. I think it works with both...
TA Partition, what's that?
Emma bring you back the original Sony stock Rom without root. Bootloader will be untouched. Have fun...
Gesendet von meinem C6503 mit Tapatalk
@ web.a : sad to say, Emma Sony Flash tool doesn't support Xperia ZL C6506 (just C6503)
http://developer.sonymobile.com/services/flash-tool/supported_phones/
more info:
https://talk.sonymobile.com/t5/Andr...ony-Flash-tool-for-Xperia-devices/td-p/307318
Now my ZL still bootloop like this (when connected to charger)
Did you try it. Emma will tell you if your Phone was not supported .Well If not, I was not able to help you. Sorry ?
Gesendet von meinem C6503 mit Tapatalk
I really need your help guys. My ZL got updated yesterday, and then a random reboot. After trying to repair it, it keeps getting into Flashmode direcly.
It does not boot into system, but flashmode. Tried to repair again with PCC, no luck. I don´t know booting process to figure out and get out of bootloop. I can access fastboot, flashmode, TWRP, with UB. I flashed ROM a couple times via TWRP, but no luck again.
I think something is messed up with partitions or something.
HELP.
Did you try to flash stock rom with flashtool?
sturmtruppler said:
Did you try to flash stock rom with flashtool?
Click to expand...
Click to collapse
Yes. Phone boots into system now, but only when plugged in charger. If I unplug it, it will shut down.
Sent from my E2363 using XDA Free mobile app
maybe hw problem battery or battery connector
same story here. Worked well for week after upgrading to 5.1.1. tried everything. Nothing has helped: updated recovery, flashed the ROM, did repair through PC companion. it turns down after Sony logo display.
amin44 said:
maybe hw problem battery or battery connector
Click to expand...
Click to collapse
i consider this situation also
rfg13 said:
same story here. Worked well for week after upgrading to 5.1.1. tried everything. Nothing has helped: updated recovery, flashed the ROM, did repair through PC companion. it turns down after Sony logo display.
Click to expand...
Click to collapse
You mean you cannot boot up, stil flash the logo while connected to charger right?
My case:
1./ first version is 4.4.2, then i try to flash to 5.02 via flashtool (as i remembered i flash ftf version for Generic US)
2./ Then root/install xpose .... and update to OTA (failed), success with updating via Sony Companion, after that, backup TA.
3./ using normally for some weeks, then occur suddenly hang, reboot, lose signal, i commit to flash a brandnew one
4./ After that i unlockbootloader via sony site, Flash 5.1.1 (10.7.A.222 but customized os)
5./ Try some solution
5.1/ (unlocked bootloader)Try to flash some other custom kernel (ex: CM12 kernel, one in this dev subforum) but the symptom as case 5.2 below
5.2 try to relockbootloader install the 5.1.1 Generic US/Customized US still doesn't boot up,
- Unplug charger, press and hold power butter, red light blink for 3 times (although connected to charger all night)
- Connect to charger, not show up the charging progress bar, just blink Sony - Xperia around every 10 s
Still consider to battery issue , hope to hear any experienced/wise advises
Just openned my N5X.
First boot to enable OEM unlock and ADB debugging.
Used sudo ./fastboot flashing unlock
Then I wanted to upgrade from 6.0.0 to 6.0.1, so I downloaded the factory image
I flashed twrp-2.8.7.2-bullhead.img
Booted to TWRP to ADB push some files and did not flash anyting from TWRP
After first boot it showed Google with the unlock symbol for several minutes, so I powered it down.
Now, if I boot to bootloader it shows a blank black backlight (I know it is in bootloader because sudo ./fastboot devices produces a s/n)
If booted normally, a mess of rainbow pixels is usually displayed (see pics).
Since it does get to the bootloader, I have tried revert to 6.0.0 with a couple different builds but the same screen issues persist.
I tried a bit more force with the following:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
I also have tried flashing using the update script, but still have the same results.
I find it strange on the first stock boot that the display was fine, but after flashing 6.0.1 and then TWRP this started happening. Is it possible the LCD is actually just defective?
edit: can't post link to pics of screen because I'm under 10 posts
I don't know why you used fastboot flashing unlock. This device requires fastboot OEM unlock. I don't know of that is your problem though.
Sent from my Nexus 5X using Tapatalk
Did you try flashing using the flash-all.bat?
Maybe that wil completely revert the phone to stock.
If not start from scratch using fastboot OEM unlock (see the root guide on this forum) and reflash the entire phone using flash-all script.
peltus said:
Did you try flashing using the flash-all.bat?
Maybe that wil completely revert the phone to stock.
If not start from scratch using fastboot OEM unlock (see the root guide on this forum) and reflash the entire phone using flash-all script.
Click to expand...
Click to collapse
Yes, I have tried using flash-all.sh on every build of 6.0.0 as well as the 6.0.1. Still rainbow pixels and when booted to bootloader shows blank, black, backlit screen
PiousInquisitor said:
I don't know why you used fastboot flashing unlock. This device requires fastboot OEM unlock. I don't know of that is your problem though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Agreed. Not sure what that command is for. Haven't seen that in any of the rooting guides. Flash all the files from the stock image to return to stock and try again would be my suggestion as pious stated as well
hopesrequiem said:
Agreed. Not sure what that command is for. Haven't seen that in any of the rooting guides. Flash all the files from the stock image to return to stock and try again would be my suggestion as pious stated as well
Click to expand...
Click to collapse
Apparently that's how you OEM unlock the 6P.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Apparently that's how you OEM unlock the 6P.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
****ing huawei lol glad I got the 5x
PiousInquisitor said:
Apparently that's how you OEM unlock the 6P.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I stupidly relocked the bootloader to see if it would do anything. Now OEM unlock and USB debugging is disabled and the screen is too unrecognizable to navigate through the initial setup and enable it.
tehNYAZ said:
I stupidly relocked the bootloader to see if it would do anything. Now OEM unlock and USB debugging is disabled and the screen is too unrecognizable to navigate through the initial setup and enable it.
Click to expand...
Click to collapse
PM me the link. I'm curious to see what your phone looks like when booted
Edit: Does anything happen when you issue this command in fastboot: reboot recovery
Sent from my Nexus 5X using Tapatalk
tehNYAZ said:
I stupidly relocked the bootloader to see if it would do anything. Now OEM unlock and USB debugging is disabled and the screen is too unrecognizable to navigate through the initial setup and enable it.
Click to expand...
Click to collapse
You relocked the bootloader in fastboot mode right? You can just fastboot oem unlock again from fastboot. Once unlocked, flash twrp, push and flash a rom. See what you get.
Sent from my Nexus 5X using Tapatalk
Here's the link for anyone with ideas if @PiousInquisitor suggestion does not work.
PiousInquisitor said:
You relocked the bootloader in fastboot mode right? You can just fastboot oem unlock again from fastboot. Once unlocked, flash twrp, push and flash a rom. See what you get.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have successfully flashed twrp (at according to cmd). When I boot to recovery using volume up + power, I get a blank screen. Tring to slide where the twrp screen lock should be does nothing. ADB does not see any devices. I have also tried booting to recovery from the bootloader with two volume down presses and one power button press-- same result.
I have also succesfully unlocked the bootloader again. I have updated my SDK/fastboot/adb/drivers/etc and have run every flash-all script from every build downloaded from the Google Dev site. I have tried all the flash-all.bat/sh on booth Linux and Windows. I have tried using different USB ports on my machine. I have tried using the USB-C to A cable ordered from the Google store and also the USB-C to A cable that came with the Nexus 6P. I used the same procedure to unlock, root, etc my 6P and did not have any issues.
Every time I get the same result that @SlimSnoopOS linked the screenshot to. I get the rainbow screen when booting to Android, a blank backlight when booting to bootloader, and a blank unlight screen when booting into recovery (although adb can't see the device from cmd or terminal).
Based on the amount of time I have spent on this, it may just be time to lock the bootloader and hope the Google Store accepts a return.
tehNYAZ said:
I have successfully flashed twrp (at according to cmd). When I boot to recovery using volume up + power, I get a blank screen. Tring to slide where the twrp screen lock should be does nothing. ADB does not see any devices. I have also tried booting to recovery from the bootloader with two volume down presses and one power button press-- same result.
I have also succesfully unlocked the bootloader again. I have updated my SDK/fastboot/adb/drivers/etc and have run every flash-all script from every build downloaded from the Google Dev site. I have tried all the flash-all.bat/sh on booth Linux and Windows. I have tried using different USB ports on my machine. I have tried using the USB-C to A cable ordered from the Google store and also the USB-C to A cable that came with the Nexus 6P. I used the same procedure to unlock, root, etc my 6P and did not have any issues.
Every time I get the same result that @SlimSnoopOS linked the screenshot to. I get the rainbow screen when booting to Android, a blank backlight when booting to bootloader, and a blank unlight screen when booting into recovery (although adb can't see the device from cmd or terminal).
Based on the amount of time I have spent on this, it may just be time to lock the bootloader and hope the Google Store accepts a return.
Click to expand...
Click to collapse
Seems like a display issue to me.
Sent from my Nexus 5X using Tapatalk
I had the same issue once with my lg g2. Turned out that I the issue was with the display. Sent in to the service center where they said the problem was damaged display connectors due to moisture.
Skickat från min Nexus 5X via Tapatalk
I had a similar issue with my first 5x. I was trying to flash the update, I think, but may have been doing other things at the same time. My display all of a sudden showed a pixelated vertical line running down the left hand side of the screen. The line was about 1/2 inch wide. It was visible in the boot loader, recovery and when normally running system. All attempts to fix the issue by re-flashing were useless. I finally sent it back and got a new one. No issues, rooted and running perfectly. To this day I don't know if was something I did, or if the display was just defective.
Hello there. I updated my Zenfone 2 ZE551ML to Android 6 as soon as it came out (download it manually from the official website) and now i am trying to do downgrade without sucess. I tried a bunch of things alredy but none of them works. All that need the ADB/Fastboot i get stuck in "waiting device". I installed the drivers, i rebooted my PC, my phone and soo on. The only thing i didnt tried yet is sideloading the Android 5 room.
I have a Win 10 and i am from Brazil (yes, the one place that the Android 6 updated made almost all the sensors stop working), idk if that changes anything.
rafaelloest said:
Hello there. I updated my Zenfone 2 ZE551ML to Android 6 as soon as it came out (download it manually from the official website) and now i am trying to do downgrade without sucess. I tried a bunch of things alredy but none of them works. All that need the ADB/Fastboot i get stuck in "waiting device". I installed the drivers, i rebooted my PC, my phone and soo on. The only thing i didnt tried yet is sideloading the Android 5 room.
I have a Win 10 and i am from Brazil (yes, the one place that the Android 6 updated made almost all the sensors stop working), idk if that changes anything.
Click to expand...
Click to collapse
Are you using the downgrade rom from asus?
Sent from my ASUS_Z00AD using Tapatalk
No. Is there one? Do you have a link? And what i should do with it?
kenbo111 said:
Are you using the downgrade rom from asus?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Searched for it without luck
You tried to
download it manually from the official website.
Have you checked to see if it's there ?
timbernot said:
You tried to
download it manually from the official website.
Have you checked to see if it's there ?
Click to expand...
Click to collapse
Yes. No luck there. Only the usual ones, none to downgrade
Ok I will keep an eye out for you .
You can boot into system or are you bricked ?
rafaelloest said:
Hello there. I updated my Zenfone 2 ZE551ML to Android 6 as soon as it came out (download it manually from the official website) and now i am trying to do downgrade without sucess. I tried a bunch of things alredy but none of them works. All that need the ADB/Fastboot i get stuck in "waiting device". I installed the drivers, i rebooted my PC, my phone and soo on. The only thing i didnt tried yet is sideloading the Android 5 room.
I have a Win 10 and i am from Brazil (yes, the one place that the Android 6 updated made almost all the sensors stop working), idk if that changes anything.
Click to expand...
Click to collapse
I has the same problem as you, try connect your zenfone to the usb ports on the rear panel. Switch different usb ports and check for fastboot devices if it recognize your phone. Zenfones seems to not like all the usb ports, Zen max has this problem, too
timbernot said:
Ok I will keep an eye out for you .
You can boot into system or are you bricked ?
Click to expand...
Click to collapse
I can boot into the system, its just that most of the sensors dont worke and i have no idea when asus will patch it
Found this but you have to fully understand ..all your own risk too read the whole thread from beginning
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=101490&extra=page=1&page=3&mobile=2