Database Users

Bricked....Need help

Well, I have finally done it......bricked my Transformer
Any assistance to fix my problem would be greatly appreciated.
Here is my situation:
I have a tf101 - model b90
I was running ICS rom with rogues recovery
I have been trying to fix the GPS problem for a while now and went back to stock rom unrooted to see if that would work.....it did not
In my effort to re-root my device i STUPIDLY flashed recovery with ROM Manager (and then read AFTERWARDS that was BAD, BAD, BAD)
I am now stuck in a recovery bootloop......HERE IS THE GOOD PART
I tried to flash an older ROM - Revolution 3.2
So now i have a combination of the recovery loop and when i try a cold boot it gets stuck on the Linux cold boot / android screen
i have tried to get ADB running with no success.....my computer (WIndows XP) makes the chime when i connect my transformer......i even get the message in the taskbar showing the device is trying to install drivers but it never shows up in my computer
My device does not show up when i run adb
Can get into ADX mode but my model is too new at B90 to run NFLASH
I have downloaded drivers but cant get the transformer to install them
I have tried PERI to unloop to no success - i get an adb error
What can i do to unbrick my transformer?!?!?!
Thanks in advance

salukis93 said:
Well, I have finally done it......bricked my Transformer
Any assistance to fix my problem would be greatly appreciated.
Here is my situation:
I have a tf101 - model b90
I was running ICS rom with rogues recovery
I have been trying to fix the GPS problem for a while now and went back to stock rom unrooted to see if that would work.....it did not
In my effort to re-root my device i STUPIDLY flashed recovery with ROM Manager (and then read AFTERWARDS that was BAD, BAD, BAD)
I am now stuck in a recovery bootloop......HERE IS THE GOOD PART
I tried to flash an older ROM - Revolution 3.2
So now i have a combination of the recovery loop and when i try a cold boot it gets stuck on the Linux cold boot / android screen
i have tried to get ADB running with no success.....my computer (WIndows XP) makes the chime when i connect my transformer......i even get the message in the taskbar showing the device is trying to install drivers but it never shows up in my computer
My device does not show up when i run adb
Can get into ADX mode but my model is too new at B90 to run NFLASH
I have downloaded drivers but cant get the transformer to install them
I have tried PERI to unloop to no success - i get an adb error
What can i do to unbrick my transformer?!?!?!
Thanks in advance
Click to expand...
Click to collapse
good news is you didn't really brick the device.
edit:
try this first
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
try using easy flasher
and restore the partitions.
if you have a problem installing the drivers try using [Win32/64][Dual Boot] Tubuntu - Dual boot 1 click installer SBK2 Only! my drivers or try using [ADB/FB/APX Driver] Universal Naked Driver 0.7
hope this helps. let me know how your turn out

x3maniac said:
good news is you didn't really brick the device.
edit:
try this first
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
try using easy flasher
and restore the partitions.
if you have a problem installing the drivers try using [Win32/64][Dual Boot] Tubuntu - Dual boot 1 click installer SBK2 Only! my drivers or try using [ADB/FB/APX Driver] Universal Naked Driver 0.7
hope this helps. let me know how your turn out
Click to expand...
Click to collapse
clockwork recovery is not reading my sd card - i took it out to download the twrp recovery - clockwork is not showing the file on the sd card....even when i reboot recovery
ezflasher does nothing for me - i go in to apx mode and try to flash twrp and nothing
the ubuntu does not detect my tablet in apx mode
i dont know what else to try - looks like i am running out of options

salukis93 said:
clockwork recovery is not reading my sd card - i took it out to download the twrp recovery - clockwork is not showing the file on the sd card....even when i reboot recovery
ezflasher does nothing for me - i go in to apx mode and try to flash twrp and nothing
the ubuntu does not detect my tablet in apx mode
i dont know what else to try - looks like i am running out of options
Click to expand...
Click to collapse
Try pushing the new recovery zip to internal storage with ADB.

baseballfanz said:
Try pushing the new recovery zip to internal storage with ADB.
Click to expand...
Click to collapse
the recovery i am in does not give the option to flash zip from internal sd card

salukis93 said:
clockwork recovery is not reading my sd card - i took it out to download the twrp recovery - clockwork is not showing the file on the sd card....even when i reboot recovery
ezflasher does nothing for me - i go in to apx mode and try to flash twrp and nothing
the ubuntu does not detect my tablet in apx mode
i dont know what else to try - looks like i am running out of options
Click to expand...
Click to collapse
When using Easy Flasher are you choosing SBK2?

baseballfanz said:
When using Easy Flasher are you choosing SBK2?
Click to expand...
Click to collapse
yes

Instead of just trying to flash recovery with Easy Flasher, try restoring to stock ROM with EF per instructions and start over with rooting.

baseballfanz said:
Instead of just trying to flash recovery with Easy Flasher, try restoring to stock ROM with EF per instructions and start over with rooting.
Click to expand...
Click to collapse
no luck
a command prompt comes up and tells me that file ..\temp\META-INF\MANIFEST.MF already exists. Overwrite with same file name.
options:
yes
no
always
skip all
auto rename all
quit
Same message with several other files
no matter what i choose it looks like ef is going through the process but the tablet does nothing

salukis93 said:
no luck
a command prompt comes up and tells me that file ..\temp\META-INF\MANIFEST.MF already exists. Overwrite with same file name.
options:
yes
no
always
skip all
auto rename all
quit
Same message with several other files
no matter what i choose it looks like ef is going through the process but the tablet does nothing
Click to expand...
Click to collapse
Silly but start with Skip all, then no, then auto rename all, then yes, see what those do. Ensure that you have the correct zip rom from ASUS from their site, instead of trying to install a DEV ROM.
LET IT SETTLE. Often times these errors are caused by impatience. set the tab down for a while, an hour, maybe 2 when you start this whole reflash.
CWM has an issue with the TF101, if at all possible install TWRP, and work from within there.

I agree with MasterDecker, use TWRP. I had some issues with CWM. TWRP is a nicer interface anyway.
I find wheelie (from linux PC) to get me back from any situation. The steps are not easy at first. I had to download the stock blob, unpack the blob and then use reflash_sbkv1.sh to flash it through USB cable in APX mode.
Even if you don't linux, you could download a free Ubuntu livecd from ubuntu.com, boot off the cd and use wheelie without installing ubuntu linux. Or just about any other linux distro fro that matter.

ethoms said:
I agree with MasterDecker, use TWRP. I had some issues with CWM. TWRP is a nicer interface anyway.
I find wheelie (from linux PC) to get me back from any situation. The steps are not easy at first. I had to download the stock blob, unpack the blob and then use reflash_sbkv1.sh to flash it through USB cable in APX mode.
Even if you don't linux, you could download a free Ubuntu livecd from ubuntu.com, boot off the cd and use wheelie without installing ubuntu linux. Or just about any other linux distro fro that matter.
Click to expand...
Click to collapse
Using my app tubuntu you can flash either twrp or cwm(by roach) via one click. I also have the windows version of wheelie in the bin folder
Sent from my SGH-T999 using xda app-developers app

Asus eee pad 101t dont reponse
I don't think my TF has ADB enabled, and i have a non working power button. No access to internal or external storage, and pc doesn't want to detect my TF. Is there a way around this?
Asus eee pad transformer TF101; CaynogenMode 10; I click reflash_sbkv1 on wheelie folder in APX mode. Going lines in cmd and TF restart, apear EEE logo and stop. I click Power button and nothing. Black screen, i cant induce APX mode, Buttons not working, APX mode Off, controled on 2 computers on windows 8, windows 7, Ubuntu. No responding.
Cable work
Buttons not broken

this worked for me when i bricked mine
google and download "asus_ics_tf101_winnix_nvflash"
connect to computer put it in APX mode then run "download" untill it boots itself

kudiska said:
this worked for me when i bricked mine
google and download "asus_ics_tf101_winnix_nvflash"
connect to computer put it in APX mode then run "download" untill it boots itself
Click to expand...
Click to collapse
no luck for me on any front
adb still wont recognize
apx mode recognizes but when i run any fixes the tablet does nothing
might have to sell it as bricked if i cannot find a solution

[Q] ADB + ClockworkMOD - Unauthorized

While rooting my i9505 i ran into a little issue with adb.
Code:
List of devices attached
8e0fe3ad unauthorized
It didn't effect what i needed to do, but it did raise the question, how do i authorise and get adb access when booted into a ClockworkMOD based recovery?
Anyone know?

It's probably because it needs RSA authentication. You can do it by making sure USB debugging is enabled in developer options and running adb then tick the "always allow from this computer" check box. It then should work in ClockworkMod Recovery.

-=nezero=- said:
While rooting my i9505 i ran into a little issue with adb.
Code:
List of devices attached
8e0fe3ad unauthorized
It didn't effect what i needed to do, but it did raise the question, how do i authorise and get adb access when booted into a ClockworkMOD based recovery?
Anyone know?
Click to expand...
Click to collapse
first be sure that you have latest adb file version installed http://forum.xda-developers.com/showpost.php?p=45698254&postcount=9
when you are booted in os, enable usb debuging, connect your phone, open command prompt in adb folder(look at your phone screen, to allow adb) and type "adb devices"
now you can turn off usb debugging. boot into custom recovery and try the "adb device" command, it should recognize your phone in recovery mode.

Can't Load OS
samersh72 said:
first be sure that you have latest adb file version installed http://forum.xda-developers.com/showpost.php?p=45698254&postcount=9
when you are booted in os, enable usb debuging, connect your phone, open command prompt in adb folder(look at your phone screen, to allow adb) and type "adb devices"
now you can turn off usb debugging. boot into custom recovery and try the "adb device" command, it should recognize your phone in recovery mode.
Click to expand...
Click to collapse
What if you can't boot into your OS? I'm in CWM recovery, and I need to push a zip of my operating system to my phone, so I can have a bootable operating system. I'm bricked right now. Is there any way to authorize it in CWM?

mikechase3 said:
What if you can't boot into your OS? I'm in CWM recovery, and I need to push a zip of my operating system to my phone, so I can have a bootable operating system. I'm bricked right now. Is there any way to authorize it in CWM?
Click to expand...
Click to collapse
Just reflash the rom you are on. You don't need adb.

Lennyz1988 said:
Just reflash the rom you are on. You don't need adb.
Click to expand...
Click to collapse
I don't think I can do that, because I don't have any zips. I have a factory zip on my PC, and I simply need to get it on the phone. I can't find a image of CWM or TWRP for my Asus ZenPad S 8.0, but I found a script that temporarily flashes some version of CWM recovery to my phone. I have a custom recovery available for use, but now need some way to get my zip to my tablet so I can extract it. That's where I'm stuck. If ADB was authorized, I would just push the file and install it. Here's the options as I see them
1: Authorize RSA via CWM Recovery (Which is why I'm here..)
2: Find a version of CWM or TWRP or some other recovery compatible with my tablet, and try again. Hope it's more updated, and cross my fingers.
3: Use an external microSD card to move the zips. (Doesn't work. E:Can't mount /external_sd/. I tried FAT32 and tried formatting with a different android device which used exFAT. No luck)
4: Somehow fix operating system to approve RSA. (Safe mode failed)
I hate to say it, but I think the tablet may have won this war unless I'm missing something. Thanks for your help though! And Merry Christmas! I'll be over at XDA Assist...

@mikechase3: Some clarification needed here. What device are you trying to restore, and what brand? Your initial post doesn't mention, and your latest mentions an Asus device. If it is Asus, then the help we can provide is going to be limited, since this is a Samsung device forum.

Strephon Alkhalikoi said:
@mikechase3: Some clarification needed here. What device are you trying to restore, and what brand? Your initial post doesn't mention, and your latest mentions an Asus device. If it is Asus, then the help we can provide is going to be limited, since this is a Samsung device forum.
Click to expand...
Click to collapse
Hey! I didn't realize this was a Samsung Galaxy Forum. Sorry about that. Specifically, I'm referring to my Asus ZenPad S 8.0 CA, and I made a more detailed post over at XDA Assist here if you have time to take a look. Thanks a bunch!

@mikechase3: I can't reply to that thread as XDA frowns on doing so while it is located in XDA Assist, but regarding the MicroSD card, format it as FAT32 in your PC, using SDFormatter from sdcard.org, and then try using the card to load the file. This will be easiest to do if you have a laptop, but can be done on a desktop if you have a card reader.

Strephon Alkhalikoi said:
@mikechase3: I can't reply to that thread as XDA frowns on doing so while it is located in XDA Assist, but regarding the MicroSD card, format it as FAT32 in your PC, using SDFormatter from sdcard.org, and then try using the card to load the file. This will be easiest to do if you have a laptop, but can be done on a desktop if you have a card reader.
Click to expand...
Click to collapse
I figured it out. So I went through the forumn again on this forum. Somewhere, deep down, I saw a little tid-bit that said the sd card had to be less than 32gb. I was using a 64gb card, and that's probably why it didn't work. I also used the tool you recommended, so it could have been that too. I'm extracting the files now, but now I'm getting somewhere. I'll let you know how everything goes once I'm finished.
---------- Post added at 11:13 PM ---------- Previous post was at 10:36 PM ----------
@Strephon Alkhalikoi I fixed my problem, but it looks like I'm going to be returning it anyways. I was able to install the zips, but now I can't even boot up the device. It's a paperweight. Nothing is showing up on the display. No low-battery or even a boot logo, and I can't even access the bootloader anymore. I'll be returning it as a defective unit (even though I was so close!!!) I'll charge it overnight and see if anything happens, but that's a bummer. Thanks for all of your help and ideas! And Merry Christmas if you celebrate it. :good:

Lg g2 Boot loops

I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app

lingarajug said:
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have more or less the same issue. Was with StockMod for D802 and received an official OTA and accepted and installed it. Now I'm stuck in bootloop. Unlike you, I can go into recovery (CWM not TWRP) BUT I can't seem to go into fastboot mode. When I hold the Volume Up and connect the phone through cable to my laptop, the phone boots but goes automatically into recovery mode. Did system wipe as well (which I shouldn't have) and at that point my phone has no OS to boot into so I used ADB to transfer CM 10.2 and GAPPS to my phone hoping that if I do it like I'm flashing a custom rom will help but unfortunately it didn't. I'm still stuck in bootloop and can't go into fastboot. help please...:crying:

Try a stock Rom and see if it helps.
Sent from my LG-D800 using xda app-developers app

cant enter recovery cant bootloader error usb isnt recognised

hi,
i had this issue for a while, the thing now is that my a500 is rooted with the a500 root tool, i have acer recovery installer
image number (Acer_AV041_A500_RV03RC01_WW_GEN1)
Build number (Acer_AV041_A500_1.031.00_WW_GEN1)
Recovery image set is CWM rev1.3.4 by thor2002ro (gives bootloader verification error) set by acer recovery installer
Bootloader version 0.03.12-ICS
usb isnt recognizing the device, cant use blackthnd3r APX flashtool or a500 manager or any other tool using usb. i tried to check for the usb using usbdeview the only way i can get to the device is with adb using tcp (connect thru wifi)
i think i can get in APX mode thru the a500 root tools cuz i get the black screen and the power light is on. i have my cpuid and SBK and a terminal emu on my a500 too i hope i gave sufficient info on this to help me.
any help? i need to unroot it or fix the bootloader issue or download another rom that could be better than what i got now
I dont know how i got into this, i been into some threads around here but im not that pro with this and i hope i get some help :crying::crying:

Does it boot normally?
Sent from my SAMSUNG-SGH-I337 using Tapatalk

dkephart said:
Does it boot normally?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Yes it does boot normally

If hou can enter custom recovery download stock rom via tablet and rename it to update.zip and flash it.
sent from sgs3 -stock 4.3 open europe rom

uglyjohny said:
If hou can enter custom recovery download stock rom via tablet and rename it to update.zip and flash it.
sent from sgs3 -stock 4.3 open europe rom
Click to expand...
Click to collapse
how to get to custom recovery mode?
cuz i mentioned that cant flash anything to it, or is there a way i can flash without recovery mode or thru APX using usb?

This is a way via tablet. No pc adb etc. I rushed a bit... any recovery is ok (custom or stock) you enter it via power +vol up (i think) and than flash stock rom
sent from sgs3 -stock 4.3 open europe rom
---------- Post added at 11:14 AM ---------- Previous post was at 11:10 AM ----------
So basicly first download stock rom on your tablet. Rename it to update.Zip enter recovery and wipe all and flash. Aint that hard
sent from sgs3 -stock 4.3 open europe rom

uglyjohny said:
This is a way via tablet. No pc adb etc. I rushed a bit... any recovery is ok (custom or stock) you enter it via power +vol up (i think) and than flash stock rom
sent from sgs3 -stock 4.3 open europe rom
---------- Post added at 11:14 AM ---------- Previous post was at 11:10 AM ----------
So basicly first download stock rom on your tablet. Rename it to update.Zip enter recovery and wipe all and flash. Aint that hard
sent from sgs3 -stock 4.3 open europe rom
Click to expand...
Click to collapse
its not working it gives varifacation failed.

Try power vol down
sent from sgs3 -stock 4.3 open europe rom
---------- Post added at 02:31 PM ---------- Previous post was at 01:58 PM ----------
Ok i remmebered now, what you shoud is download stock rom first rename it and try power + vol up/down. It shoud starg update proces. Rom shoud be on your sd card
sent from sgs3 -stock 4.3 open europe rom

Nouas said:
hi,
i had this issue for a while, the thing now is that my a500 is rooted with the a500 root tool, i have acer recovery installer
image number (Acer_AV041_A500_RV03RC01_WW_GEN1)
Build number (Acer_AV041_A500_1.031.00_WW_GEN1)
Recovery image set is CWM rev1.3.4 by thor2002ro (gives bootloader verification error) set by acer recovery installer
Bootloader version 0.03.12-ICS
Click to expand...
Click to collapse
First, you cannot install a custom recovery using acer recovery installer with 3.12 bootloader, this is why you are getting boot verification error.
To get a custom recovery on your tab you must flash the unlocked bootloader
To get the unlocked bootloader you must have
a) Your CPUID
b) Drivers - The acer drivers and the usb drivers
c) micro usb cable to connect to your PC
d) a PC running XP, Vista, win7 32bit system or ubuntu
e) Use icsRoot tool to delete the boot.p file (otherwise your custom recovery will be overwritten with the stock recovery (dead android) on reboot.
f) If you are already rooted check this file /system/boot.p - if its not there carry on
Once you have all this you can use the apxFlash tool to flash the bootloader.
You will need a custom rom on your ext sd card. After you've flashed the bootloader, enter recovery immediately, do the wipes and flash your rom. Done.
All download links can be found in the root guide in my sig or civato's guide which is stickied in the Dev forum

dibb_nz said:
First, you cannot install a custom recovery using acer recovery installer with 3.12 bootloader, this is why you are getting boot verification error.
To get a custom recovery on your tab you must flash the unlocked bootloader
To get the unlocked bootloader you must have
a) Your CPUID
b) Drivers - The acer drivers and the usb drivers
c) micro usb cable to connect to your PC
d) a PC running XP, Vista, win7 32bit system or ubuntu
e) Use icsRoot tool to delete the boot.p file (otherwise your custom recovery will be overwritten with the stock recovery (dead android) on reboot.
f) If you are already rooted check this file /system/boot.p - if its not there carry on
Once you have all this you can use the apxFlash tool to flash the bootloader.
You will need a custom rom on your ext sd card. After you've flashed the bootloader, enter recovery immediately, do the wipes and flash your rom. Done.
All download links can be found in the root guide in my sig or civato's guide which is stickied in the Dev forum
Click to expand...
Click to collapse
the whole issues is i cant use the usb to fix anything, something wrong with the ROM im using i guess makes the usb useless

Nouas said:
the whole issues is i cant use the usb to fix anything, something wrong with the ROM im using i guess makes the usb useless
Click to expand...
Click to collapse
I'm not sure you're understanding the process.
The method I posted does not have anything to do with a rom. Its based on using apx mode.
A) Put yr tab in apx mode.
B) connect yr micro usb cable
C) check " safely remove hardware" icon for an "apx device"
If its listed there then follow the directions I posted.
If its not showing then you must install the drivers, as I posted above!! Nothing will work as it should, until you have both sets
of drivers are installed correctly.
If you don't know what apx mode is or how to access it. Pls read the root guide in my sig. The first 2 posts.
Sent from my GT-I9300 using Tapatalk
Yr pc should be running xp, vista or win7. Win 8 and 64bit have issues

dibb_nz said:
I'm not sure you're understanding the process.
The method I posted does not have anything to do with a rom. Its based on using apx mode.
A) Put yr tab in apx mode.
B) connect yr micro usb cable
C) check " safely remove hardware" icon for an "apx device"
If its listed there then follow the directions I posted.
If its not showing then you must install the drivers, as I posted above!! Nothing will work as it should, until you have both sets
of drivers are installed correctly.
If you don't know what apx mode is or how to access it. Pls read the root guide in my sig. The first 2 posts.
Sent from my GT-I9300 using Tapatalk
Yr pc should be running xp, vista or win7. Win 8 and 64bit have issues
Click to expand...
Click to collapse
i tried to connect my a500 on few devices and its not being connected to any....
the ROM im using now got issues with the usb i bet, thats why i cant connect my tab to any PC, im stuck!

ZTE Blace V220 / Avea Intouch 4 [root success]

[edit]: Succesful root thanks to @mseskir advice [edit]
Hello everyone.
I just replaced my old Samsung Galaxy S3 Mini (i8190) by a new ZTE Blade V220 (nifty hardware at nifty price, EURO 140, WOOT).
I chose it because I didn't want to make a great spent, only to find out that there is no development on this model and that it doesn't even appear on ZTE webpage, so I can't "root" it or change the recovery.
As per Mseskir, this phone is the same than "Avea Intouch 4", a phone sold by a turkish brand.
Below are the hardware details:
- Qualcomm MSM8916 quad core 1'2 Ghz
- 800/900/1800/2100/2600 Mhz CAT 4
- 5" IPS screen (1280 x 720), looks nicer than the super AMOLED S3 mini screen
- 1 Gb RAM + 8 Gb storage (2 gb already spent for OS, even though it brings no bloatware at all)
- Bluetooth 4.0, GPS, WIFI, SD card slot
- 13 Mpx back camera with autofocus, and 5 mpx front camera (not top-notch quality, but good enough for me)
- 2100 mAh battery
- 139 x 71,5 x 9,5 mm (the back is too curvy for most hard covers ).
- Android KITKAT 4.4.4
ROOT steps:
A) I had to use the ZTE ADB drivers bundled with the phone (just mount USB in "driver mode" option
and run the bundled exe in your mobile storage).
The drivers will be installed in "C:\Program Files\ZTE_Handset_USB_Driver". Remember this directory.
B) Download "Root-SuperSU-v2.37.zip" from file from mseskir's yandex drive, within the "root"
folder. You can find the link in his post below. Upload without unzipping to your mobile internal memory.
You will need it later.
C) Download the "IT4_Recovery_Yukleme_Programı.exe" file from mseskir's yandex drive, within the "root"
folder. You can find the link in his post below.
D) Unzip "IT4_Recovery_Yukleme_Programı.exe" and get "recovery.img" (recover with TWRP) or
"recovery_stock.img" (if you prefer stock recovery) from the "tools" folder.
I will use "recovery.img" because I have been using TWRP since my old Xperia Neo V.
Copy the your "recovery.img" of choice to the folder where the USB ADB drivers was installed.
Copy the "fastboot.exe" file there too.
E) Enable "USB ADB debug" in android "Developer Options". Ensure that Windows detects and installs
the drivers properly.
F) Open command prompt and go to "C:\Program Files\ZTE_Handset_USB_Driver"
G) Type "adb devices", if everything goes well you will see your phone serial number listed
there. If you receive some error while starting the daemon, ensure that no other ADB app
is running in the background or try another ADB drivers.
You can check your phone serial number in the mobile itself: Phone Information --> Status
H) Type "adb reboot bootloader" in command prompt. The phone will reboot and will get stuck in boot image
with the notification led in red (scary, but don't worry, it's all fine).
I) Type "fastboot devices" in command prompt. You will see again the phone serial number in the window.
The phone screen will remain unchanged, like if it where frozen, but don't worry, everything is still fine.
J) Ensure that you have copied "recovery.img" in the same folder than adb.exe and fastboot.exe
( "C:\Program Files\ZTE_Handset_USB_Driver", as I mentioned earlier).
Then, type "fastboot flash recovery recovery.img". If you copied the "recovery.img" and the "fastboot.exe"
to the driver folder you will see the flash progress. It will take one or two seconds and give you an "ok" message.
K) Type "fastboot reboot" and the mobile will reboot. Let it boot till the end. Disconect USB cable and
shutdown the mobile completely.
L) Push and maintain "volume up". While you maintain "volume up", push "power" button a few seconds
to start the mobile. Keep maintaining "volume up" until TWRP boot screen appears.
M) Flash "Root-SuperSU-v2.37.zip" with TWRP. You should have already copied it to mobile storage if you followed my advice in point "B". Reboot to system and it's done.
I leave this here so if anyone searches for this phone like me, he will know how to succesfully root it.
Thanks to everyone in advance.

Root
Hi, your phone is same like my phone "avea intouch 4" this is my files link
https://yadi.sk/d/8GHocBtnfTp7A
Go to root folder, download the IT4_recovery_yukleme_programi.exe
Run it, turn usb debugging on in your phones devoloper options then connect your phone select twrp recovery yukleme in the programs menu, a message will pop up on your phone, select "ok" then it will reboot to bootloader and flash twrp recovery to device. After reboot open the twrp recovery and firstly backup your device to sdcard1 and copy it to your pc then install supersu package from my root folder. Thats all.
But first you must install drivers.
If anything goes wrong i will help you as i can.
If you cant use the program (its language is Turkish) i will make an english program tomorrow.
---------- Post added at 04:02 PM ---------- Previous post was at 03:48 PM ----------
Our Turkish forum link is
http://mobile.donanimhaber.com/showTopic.asp?m=100770257&p=1
We are trying to port roms. And i'm using a custom rom right now.

mseskir said:
Hi, your phone is same like my phone "avea intouch 4" this is my files link
Go to root folder, download the IT4_recovery_yukleme_programi.exe
.... /QUOTE]
Thanks @mseskir, I have tried it without luck.
When using option 2, I receive "sonraki asamaya gecmiyorsa suruculeri tekrar yukleyiniz" which means
something like "Your driver does not pass to the next stage reload".
So I uninstalled the ADB drivers that came bundled within the phone storage, and installed the ones on your link,
but still the same even after reboot and complete clean.
Any suggestion?.
Click to expand...
Click to collapse

Ok. Can you try this;
open my exe file with 7zip and extract
open tools folder
click right mouse button with shift (from keyboard) pressed
select open command prompt here
in command prompt;
type adb device
on your phone screen a warning will pop up, select ok
then you will see your phones serial number in cmd window
then type;
adb reboot bootloader
your phone will reboot to bootloader,
type;
fastboot devices
if you cant see serial number; go to my yandex folder, in tools folder; AdbDriverInstaller.exe download it and run it. it will install the fastboot drivers
then type "fastboot devices" again, if you can see your serial number type;
fastboot flash recovery recovery.img
then type "fastboot reboot"
if you dont want twrp recovery you can use cwm recovery, it is inside my root folder IT4_Root_Anlatımı.zip (extract it, there is cwm recovery)
if something goes wrong tell me..

mseskir said:
Ok. Can you try this;
open my exe file with 7zip and extract...
Click to expand...
Click to collapse
I got TWRP (i'm used to it) working and root by working following your instructions, thank you very much.
But I have had to use my own adb files taken from zte drivers installer (bundled with the mobile)
as replacement from the ones bundled in your zip file, which always errored out for me when trying
to start the service.
The only scary moment was when I issued "adb reboot bootloader" and the mobile got stuck on ZTE boot image. I was waiting for a while for bootloader to appear, but it didn't happen, so I proceed with next step.
When I have some time tomorrow or weekend, I will update the first post for the proper steps to attain root.

helpful thanks

lollipop update
avea intouch4 original 5.0 update files
http://www.avea.com.tr/web/android5update/update.zip
How to update zte blade v220 Download update zip that link. And move sdcard then settings-Phone information-System updates and press OK
It shows recovery wait here.
Later Phone will start and 'll boot 5.0.2

I would advice to avoid updating the phone to V5.0.2 with the update file because of the following:
A) You will lose your existing root. You will have to root again Use http://www.kingroot.net/ for easy and clean root.
B) You will have trouble connecting to previously working WLAN networks (I'm suffering it right now, lots of people complaining about this, just click here "https://www.google.es/webhp?sourcei...8#q=android 5.0.2 wifi authentication problem" to see what I mean). Using "Wifi Fixer" app it sometimes works well, sometimes it disconnects itself, I need to check further.
C) Only English, German, French and Turkish languages are available in the update. Although I miss the Spanish language, I could live with english. Partly fixed with "Set Locale and Language" app from Google Play
D) I'm still trying to figure out how to flash TWRP to restore my 4.4.4 backup.
E) Fastboot support with 5.0.2 is crimpled so I can't use it to reflash TWRP. I can't seem to find a valid TWRP version to flash with "TWRP manager" either.
F) Don't know if it's a bug or not, but screen switches on and off when idle and locked without any reason that I can find. It bothers me a lot!.
G) Just discovered that this update also locks bootloader. That's the reason I can't flash recovery.img back.
Be warned.

I give up with this!
Well, after a few days trying different solutions to install a TWRP recovery to recover my stock backup, I have messed it up to the point that I'm now stuck in the following status:
The phone gets stuck in bootloop with Avea logo. It heats up a lot but doesn't boot no matter how long you wait.
Before messing it up, I managed to install Phil6 recovery version 6.57.9 (I still can access it with VOL+ and power button).
This Phil6 version I got seems to be compiled for "sprout" hardware, so it will always error up when trying to flash roms for msm8916 hardware.
Any other roms I try to flash that don't error up with sprout message will always fail with "error: 0". I have tested a few roms with two different SD cards, so it's not a badly downloaded rom.
Restoring my TWRP backup with Phil6 doesn't error out, but the phone still doesn't pass the avea logo.
I first went for a 6" Sony Xperia C5 Ultra, but the main camera quality was terrible and it heated up a lot, enough to unglue the screen protector.
So I returned it to the shop and picked a Huawei Ascend P8.
Much better hardware than V220, much better still camera, slightly worse video recording quality (IMHO), and twice as expensive as the V220, but it really flies compared to the V220, gentlemen.
Thanks everyone.

Thanks to @ozgurharan's rom, I have been able to bring back to life my ZTE Blade V220.
This is his rom's link, I got his permission to post it here: https://yadi.sk/d/uv3bhb0knX8nn
Too bad that I still can't restore my TWRP backup or the original KitKat rom with spanish language, but something is better than nothing.
Be warned that this rom has only English, French, Turkish and Deutsch languages.
Thanks a lot @ozgurharan

Hello. I have already upgraded my Avea In Touch 4 to 5.0.2 before reading this post. Now I cannot root my phone. I have followed every step on this post but in bootloader mod when I try fastboot flash recovery the recovery.img I get an error like "writing recovery... failed (remote: unknown command). I tried to install the last rom you have shared but still not working. I just want to root my phone and have the last version of stock rom for my phone if avaliable. Can you please help me?:crying::crying::crying:

TheSuburban said:
Hello. I have already upgraded my Avea In Touch 4 to 5.0.2 before reading this post. Now I cannot root my phone. I have followed every step on this post but in bootloader mod when I try fastboot flash recovery the recovery.img I get an error like "writing recovery... failed (remote: unknown command). I tried to install the last rom you have shared but still not working. I just want to root my phone and have the last version of stock rom for my phone if avaliable. Can you please help me?:crying::crying::crying:
Click to expand...
Click to collapse
Use kingroot. It worked for me.

@mseskir, do you happen to still have the previous TWRP version for Avea Intouch 4 (I think it was 2.7.0.3 or around it)?.
I have flashed your current TWRP 2.8.6.1 to root the phone but this version can't mount SD card, so I can't flash zip files from SD card.
The File Explorer shows SD card as 0 Mb, but if I boot the phone SD card is recogniced and will work well.
Or if you have a newer version than 2.8.6.1 that doesn't fail to mount SD card will be fine too.
NOTE: Long story short with my previous struggles with Blade V220 and horrible Android 5.0.2 update. Doing some tests I did a very bad flash and f##ked the phone completely,
so I had to send it to ZTE tech support. The phone was still on warranty so they replaced the phone PCB with a new one that has Android 4.4.4.
Thanks in advance.