Database Info

Bricked :(

All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?

spooky71 said:
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
Click to expand...
Click to collapse
What happened?
This is a common result if you flash a non-4.2 twrp on a 4.2 bootloader, which will cause a fastboot flash brick.
You will need adb drivers installed on pc, then while in recovery connect your tab to pc, open a command prompt and cd to you android-sdk/platform-tools folder and type
Code:
adb devices
if adb is setup correctly you will get a response with your devices s/n. If this is ok then type
Code:
adb reboot-bootloader
which will reboot your tab to the bootloader screen.

The problem is that whenever I boot up, all i get is the TWRP menu, not letting the pc see the pad. On device manager I get Transformer under other devices. Ive downloaded the drivers, but its not installing them. When I run adb reboot-bootloader, I get device not found.

Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later

pjc21 said:
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
Click to expand...
Click to collapse
Still nothing. Whats killing me is that it cant detect different sd cards.

Device stuck in Bootloop | Can Access Fastboot | Commands don't work

My Oneplus One - 64GB was running LiquidSmooth's Alpha ROM.
I hadn't used the phone in like a month. A couple of days ago i thought there'd be an updated version so i just downloaded a later version. I think I flashed the 01-22 Build.
I did not do a full wipe however. (I realize now that It would have been a good idea to do a full wipe before the flash. :s )
I assumed that since the base of the ROM was the same lollipop, all I had to do was wipe cache/dalvik and flash the update.
Installation proceeded as usual and I wiped cache/dalvik(I'm never sure when to do this so i do it before and after install) once more and then Reboot System.
But the phone went on a bootloop for like 10minutes or so.
I tried to get into Recovery but it just wouldn't. It would just show the 1+ Logo and Powered by android screen and then turn off..
I did however manage to get into the fastboot mode by pressing power +vol up.
Now the problem is, the device doesn't show up in the command prompt when i type
Code:
fastboot devices
I uninstalled all the usb drivers from my pc.
Installed the Universal ADB drivers from kouch's site but still no progress..
Device manager still shows the phone as an unknown device.
What am I doing wrong? What can i do to get the phone to be recognized so I can flash the recovery and flash a new ROM?

It's related of firmware change. After 01.17.2015 you must flash the latest CM12 rom and then flash the rom you want.
That's a known "issue". Hope it helps.

Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.

thetearer said:
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
Click to expand...
Click to collapse
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.

timmaaa said:
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
Click to expand...
Click to collapse
That's the order I did stuff in last time I believe. I'll try it again and report back

[Q] Device not found after wiping data (trying to flash CM)

Hi,
I am not sure if I can ask about upgrading to CM here? Today I tried to follow their guide from their wiki and now my I can't access anything but recovery, and adb won't work.
I installed the recovery using fastboot and unlocked the device. That worked.
After that, I wiped data/factory reset and the next stage is to push CM to my device, but the device isn't recognized by the PC (when I type adb devices no devices appear).
Now I don't have an os and cannot do anything outside of recovery. I tried clicking on mount USB storage but it doesn't open my storage on my computer. When I connect the device my computer makes sound that a USB is connected.
I tried to /mount data and pretty much everything.
Any ideas?
Sorry for bad English.

I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.

schmos said:
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
Click to expand...
Click to collapse
No, I have CW recovery (I thought I wrote that, sorry).

You need to get adb drivers sorted out, I believe there's a guide for it on General forum.

beekay201 said:
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
Click to expand...
Click to collapse
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.

Mr Light said:
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Click to expand...
Click to collapse
You previously wrote, and I quote, "I installed the recovery using fastboot and unlocked the device. That worked."
^ This means to me that the connection between your bootloader (fastboot client) and your computer (fastboot host/server) is working, from which we can assume drivers FOR FASTBOOT are correctly setup.
You previously wrote, and I quote, "but the device isn't recognized by the PC (when I type adb devices no devices appear)"
^ This means to me that the connection between adb (on the phone) and adb (on the pc) is not working.
Now, if you are in a custom recovery, hook up the usb to the pc, start adb server on the pc, and you still don't see your device sn appear on the output of 'adb devices', then it means that the drivers FOR ADB aren't setup correctly.
Running a tool and then coming back saying it didn't work... That's not helpful at all. How did it not work? What version of the tool did you use? 1.4.2? 1.3? Keep in mind that you need (more likely than not, since you're probably running latest recovery versions) updated adb and fastboot binaries to API 21 version (Android 5.0). v1.3 of that tool doesn't seem to support API 21 yet.
Learn how to ask for help, please. Also, read the entire first post of this thread please: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If you still can't get it to work, there's a thread to help out troubleshooting drivers stuff, check it out at http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396

Ok... Sorry for making you confused, it's not easy for me to communicate in English.
Anyway I managed to flash twrp which is much friendlier than CWM, and then I had access to my storage again. Thanks (solved).

bricked shield?

hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks

@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !

i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system

ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd

Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?

fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:

Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...

fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works

Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.

fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself

Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?

I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?

How to root zenfone 7 ZS670KS

hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.

Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip

Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"

so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?

Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?

Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?

is it possible to root using adb sideload or install twrp using adb sideload?

articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.

Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.

articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.

articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer

decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more

articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence