[Q] ZTE Blade not starting, maybe bricked... - Blade General

I think my phone is bricked
When I start up my phone it just stops when it says "ZTE"
Tried to reboot but wont work, its fully charged...
Please help

Are you rooted? Do you have ClockworkMod installed? What rom were you running?

NO
matt4321 said:
Are you rooted? Do you have ClockworkMod installed? What rom were you running?
Click to expand...
Click to collapse
No. No. and none.
I weren't running any roms or anything, but i have tried to root it with z4root and gingerbreak (etc..) a million times...

Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2

if he installs stock rom and unroots then it should be fine and he will keep his warranty
Sent from my Blade using xda premium

Ehhh..
matt4321 said:
Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
I dont quiet know how to do that
I was on 2.3.5 have 2gen stock rom
how do i get into fastboot then?

To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2

matt4321 said:
To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
Still looks way to complicated for me :/
Do u know any videos that can show me how to do it?

hi is it bricked or what?
hi all xda members, im new on this forum and i really don know were to post or something like that, sorry, and i have searched on every singel page in google and on a lots of forums, and i dont find anything that can help me with my problem..:crying:
So now to my poroblem, i have a zte blade II 2.3.6 gen3 un-rooted, i tryed but no luck... and now i think its really bricked...because i cant boot it at all, not in FTM, not in bootloader mode, not in recovery, the only thing i can boot it in is DFU but i cant flash from there, it is bricked or can this be fixed easily? Thanx in advanced guys!

ZTE Blade does not respond at all
My ZTE Blade does not respond at all.
I have tried to install the official update from android 2.1 - 2.2 using this official application from ZTE
( ztedevices official site -> downloads -> Greece -> smartphone ->Blade)
It stopped in the middle of the process and after that I cannot use neither Power&volume(+) nor Power+volume(-) nor Power.
It looks completely dead.
Battery is fully charged,
When connected to charger, back button does not get red.
When connected to computer does not show android logo.
I have copied gen1 to gen 2 image folder to sd... nothing
gen2 to gen 1 the same.
I have also tried the AIO-BLADE application no respond to any action.
I have been searching this forum and the internet for 2 days now. No one answers cases whith hardbricked phones.
I think the phone is out of warranty.
PLZ it is my only smartphone and there is no money for a replacement, I am unemployed.
:crying:

Related

[Q][SOLVED] Bricked ZTE Libra

Hi! I have a bricked ZTE Libra (Sapo A5 in Portugal) and no mather how much I search for solutions I only seem to make things worse, so I was hoping someone here could help me.
Things started to go wrong after flashing a CyanogenMod rom. Everything worked except two things: I couldn't use anything that required my SIM card (so no phone or messaging) and I could not access the recovery screen (clockworkmod).
Without the recovery screen, I turned to ROM Manager but since it uses clockworkmod to do its work it didn't help.
Then I started trying other ways to recover my phone, until I tried ADB which allowed me a shell in my android. But then I broke it all by doing "wipe system" which cleaned my system of everything that was still working and left me with an expensive brick.
Now all I can do is boot until I see the green droid. If I don't press the volume buttons it goes into "device" mode and I can see it listed under "adb devices" but have no idea what to do with it.
If I press the volume button down to go into recovery mode it keeps flashing but never really goes anywhere.
If I press it up to go into the bootloader it stays the same and the only thing I can use to tell me something is different than the normal mode is that lsusb reports the vendor as "Google Inc." instead of what it reports in normal mode: "ONDA Communication S.p.A.".
With this I'm not even sure if I can get to the bootloader or not, but even if that is the bootloader, I have no idea what to do with it that might help me recover my phone.
By the way, I'm trying all this on Linux, although I could try solutions in Windows if required.
Can anyone tell me what can I do in this situation?
Ok, maybe my first post wasn't that easy to answer, so I'll make a simpler question to see if someone can help me.
What can be done at my android's bootloader? What is it for and what tools do I need to use to do it?
You could try installing ClockworkMod recovery using wbaw's guide here http://forum.xda-developers.com/showthread.php?t=1319257 Once that's installed you should be able to flash a new rom with it.
In bootloader mode you can flash a new kernel or recovery image using fastboot.
If you follow that guide that I wrote & Amphoras linked to then you should be able to get a working clockworkmod installed and then you can use that to flash a working rom, or restore a backup.
Thank you both, I'll try what you said as soon as I can and then I'll let you know if it worked!
Ladies and gentleman, today a miracle happened, my ZTE came back from the dead!
Apparently the problem was that I installed some GEN2 applications on my GEN1 model.
I found this while reading the tutorial you suggested, after which I upgraded my ZTE to GEN2 which allowed me to slowly recover everything else.
So, I have to say, thank you very much, and I hope I won't need your help again anytime soon! xD

Flashed JB Stock Rom via CWM 5.8.2.0 Touch

Hey folks,
once there was a little boy who was glad to own a new Transformer, but after he made a mistake, the little boy thought his beloved Transformer transformed into a pretty pricey paperweight (Oh, by the way the "little man" was me :crying.
The following lines are telling the whole story.
DISCLAIMER
I am in no way responsible for what you do with your Transformer, even when you are following these (my) instructions.
There is always the risk of making it worse and this risk is completely down to you!!!
(Because it worked for me, I dont guarantee it will work for anybody else.)
Precondition:
- TF300T
- unlocked
- rooted
- CWM Recovery 5.8.2.0 Touch
- Stock ICS
What I did:
Flashing the stock rom from ASUS via CWM.
What happend:
My Transformer was stuck in a recovery loop, which means it started, the asus logo appeared on the screen and instead of starting Android, CWM started.
The Problem:
- The Transformer wasnt able to start...
- Fastboot didnt work. If I tried to get into fastboot mode the message:
"The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "ww_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image"
appeard.
- ADB didnt recognized my device
- Wipe, format, etc in CWM didnt work.
So I managed to get out:
- Installing Transformer Prime drivers. Universal Naked Driver 0.7 http://forum.xda-developers.com/showthread.php?t=1766220 and/ or TransformerPrimeDriver http://downloadandroidrom.com/file/TransformerPrime/drivers Choose one or take both (worked not the first time, but after a few tries Windows recognized my TF300T as ASUS Prime ADB device.)
- ADB still didnt work.
- I found & downloaded "WSG_UnBricker_TF300T_V1.0.2.zip" http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html to my PC(Google will help. You also can choose and try the original one from MasterZen88, but I chose the other one)
- after extracting I started the WSG_Unbricker.bat on my PC and started the ADB Shell.
- There I did the commands from DiamondBacks' Option 1a and rebooted the Transformer.
- After doing so my Transformer stucked on the ASUS Screen.
- I pressed Power till the screen went black.
- Then I hold Power + Volume Down. Then I chose Fastboot Mode. On my PC I started WSG_Unbricker.bat again. Here I started "Install Menu" and tried to install recovery, boot, system, all... Did a few restarts with my Transformer and repeated this step. After a few times I was able to start into CWM Recovery 5.5.0.4 instead of the 5.8.2.0 in the beginning.
- Transformer in CWM Recovery I opened cmd out of the WSG_UnBricker-folder and did the command: adb devices. My Transformer was RECOGNIZED!
- I downloaded cm9.1.0-tf300t.zip http://get.cm/?device=tf300t, renamed it into update.zip (after all maybe not necessary )
- put this update.zip into the same folder you started your cmd out of.
- Then I did the command: adb push update.zip /sdcard/update.zip
- After the transfer was finished I was able to flash the update.zip via CWM Recovery.
- Now I rebooted and watched my Transfromer booting into Android! :highfive:
I m not sure ir this story really helps anybody.
I m not sure if even anyone reads this lines, but maybe I could help another little boy
Ok, I don't test, because I already use TWRP, but it will be good if you could insert the links for all of your different files so that the members can use your method correctly.
Thanks.
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
timmytim said:
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
Click to expand...
Click to collapse
don't think he has since he was able to install CM
timmytim said:
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
Click to expand...
Click to collapse
Hey,
I was on stock ICS (unlocked bootloader + rooted) and flashed the stock JB via CWM.
Now I m on CM 9 and thinking of updateing to CM 10 because the ICS bootloader isnt affected by this update (at least I think so )
Droid_1 said:
Hey,
I was on stock ICS (unlocked bootloader + rooted) and flashed the stock JB via CWM.
Now I m on CM 9 and thinking of updateing to CM 10 because the ICS bootloader isnt affected by this update (at least I think so )
Click to expand...
Click to collapse
hello mate..same problem with tf201...stuck on asus logo i see you solved your problem..my computer do not recognize my tab when connect it via usb..shall i go into apx mode or how you did this ? because fastboot and abd do not work..cannot boot into recovery and vol+ & power button also dont work ..thx
0din said:
hello mate..same problem with tf201...stuck on asus logo i see you solved your problem..my computer do not recognize my tab when connect it via usb..shall i go into apx mode or how you did this ? because fastboot and abd do not work..cannot boot into recovery and vol+ & power button also dont work ..thx
Click to expand...
Click to collapse
Hello,
when my transformer was stuck on asus logo I was able to go to bootloader so... at the moment I dont have an idea.
But this thread may help http://forum.xda-developers.com/showthread.php?t=1514088 if you didnt read already.
Just want to say thank you.
I Bricked the tf300 by flashing a JB rom and still using a ICS bootloader.
Flashing the cm-9.1 version was a good advice, now i can boot again.
Tank You!

asus tf300t bricked

kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.

[Q] Stuck in FTM Mode?

Hi folks,
My wife dropped her 2-week old Nexus 4 which caused part of the front glass to crack and portions of the touchscreen to be dead, so we had to send it into LG for repairs (at quite a price tag). Fine.
So we get it back, I turn it on, and it's in something called "FTM Mode" (file transfer mode, I think)? I can't seem to get it out of it.
Things I've tried:
Rebooting (have to hold the power button down for 5-10 sec).
Factory data reset (the settings are available through the notification menu in FTM Mode).
In recovery mode:
[*]Start (goes right back to FTM Mode)
[*]Power off (duh)
[*]Restart bootloader (gets me right back to the same screen)
[*]Recovery mode (gives me a little android with its stomach open, a red exclamation point, and says "No command.")​
I attempted LG support, but they asked me to do a few of these (after asking me to hit the "home" button...), then told me to mail it back to them because they probably have to flash it.
So, the obvious question: how the hell can I get out of FTM Mode?
Secondary question: if none of the above worked and I do have to flash the OS, can I flash it myself to default Jellybean? Any idiot-friendly step-by-step guides out there?
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Depressio said:
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Click to expand...
Click to collapse
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, I haven't even been able to install the bloody USB driver, so fastboot/adb can't even see the device. I've described by problem here. I think the source issue is what LG did during repairs... the device is named "Full JellyBean on Mako" instead of something like "Nexus 4", so the drivers in that post aren't being recognized by Windows as valid for the device. At least that's my guess.
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
For future reference ADB only works in recovery and when booted into android, never in boot loader. Bit glad you got it working
Sent from my Nexus 4 using Tapatalk 2
drives
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
how did you can install the adb drivers,have same problem
ramonrecio said:
how did you can install the adb drivers,have same problem
Click to expand...
Click to collapse
plug your phone into your computer, then restart it in bootloader mode. the drivers will automatically install
same
hi,thank you,ok i can go to fastboot mode and select restart bootloader but when i hit power ,they turn off for a second and go back to fastboot mode initial page ,the pc do the sound when disconnect and connect back to usb pc,but that's it,no drivers installation ,what can i do!! this make me crazy,please help

Unlocked but can't root/install CWM

I used the toolkit for mac and it unlocked me, but when it came to the next steps it said device not found and then told me to highlight recovery and press start, when I do I get the android with the red ! symbol.
Can someone help me?
That symbol is a security feature within the stock recovery, volume up and power to access the stock recovery.
Sent from my Nexus 4 using Tapatalk 4
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...
I searched and saw hold power and press up when I see the red ! but it just reboots the phone...
help please?
Sent from my GT-N5110 using Tapatalk 4
ADB wont work in stock recovery
roguedroid said:
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...do you know the adb instructions on how to push supersymmetric and cwm?
edit my adb now won't recognize my phone even though it did a few mins ago...
I'm frustrated, been trying to access the stock recovery for the past several mins and simply can't.
help please?
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
badhri said:
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
Click to expand...
Click to collapse
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Sort out the drivers and adb,fastboot
roguedroid said:
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Just as I mentioned, i also had the same problem with stock recovery. So I simply flashed a Custom one(CWM, in my case)
Get the ADB and FASTBOOT working and that'll solve your recovery problem. Try fiddling with your drivers again. Not sure how to do that in MAC. If FASTBOOT is working, the you can boot into a Custom Recovery(you need not even flash it) and perform whatever you need to.
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Again, look at the efrant's guide i referred above; i took this from there only.Remember to replace 'customrecovery.img', with the actual downloaded custom recovery image name.
Or you can try posting your problem with the toolkit, in mac toolkit's thread.
I have been youtubing everything and finally got to
Reboot system
apply update from adb
wipe data/factory reset
wipe cache partition.
I now can get adb working so I tried ./adb sideload cwm from my desktop and it is giving me signature verification failed. installation aborted.
What can I do to resolve this?
I searched xda and no one can solve this issue from the threads I've read.
I fixed it! Whooohoooo! Installed cwm and root ....now to install pa rom.
Thanks for the help!
Sent from my GT-N5110 using Tapatalk 4

Categories

Resources