Database Info

[SOLVED] gt-i9023 help please - no usb,adb,fastboot access

I am a beginner at this so please excuse me.
I successfully rooted my phone, installed clockwork, super user was working, could connect like a dream with usb to the phone. Flashed stuff using fastboot in command line - all was good.
When I say successfully it did take a long time, the phone didnt work for a while but I flashed clockwork on then flashed the rom for my phone from here http://forum.xda-developers.com/archive/index.php/t-1063664.html
I used this one:
Android 2.3.3/GRI40/KB1 Radio/KA3 Bootloader (http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip)
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Which was great - sorted the phone a treat - I had the super user working - I installed the clockwork rom app - worked a treat - even did a backup (I think)
Then the phone tried to update to 2.3.4 which failed - right now I should of check the forums but thought I know I'll just flash the update from the above page - which failed - not to be defeated I tried harder using different roms through clockwork recovery or clockwork rom mod until sucess 2.3.4 GRJ22 build.
Then I find the super user app doesnt work or the clockwork rom - no problem boot into clockwork recovery - uh oh thats gone as well though i can get to android recovery.
I'll just flash clockwork recovery on but I cant as I've no access with adb or fastboot the phone is not connecting to the pc in fastboot mode with the android logo and phone details.
When I'm trying to use USB connection on the phone normally the USB man goes orange then back to green - and the phone prepares the USB storage again.
I can use a app to get files on to the sd card for use with android recovery so i try to reflash the 2.3.3 rom above that worked but I get the status 7 error with a long number 1297306095
I try the update again and this is where i realise that the update ROM i put on was the wrong one.
I flashed this: Android 2.3.3 (Build GRI54/KB3 Radio/KA3 Bootloader) (whole rom)
I should of flashed this Android 2.3.3 (Build GRI40/KB1 Radio/KA3 Bootloader) (smaller update)
I can flash the correct update above but it doesnt change anything.
I have spent a few days now trawling the forum with little success and having got all the correct drivers on the pc and had it connecting fine I am assuming it is a phone issue now
the base band details have changed from XXKB1 to XXKD1 and the build from GRI40 to GRJ22
I am at my wits end here and before I put a hammer to my phone and send it back as an insurance job I'd like to mend my stupid mistakes.
Thanks
Acne

it doesnt matter if you flashed the whole rom. (provided you didnt use odin)
first thing, try to format sd card through the phone,
then enable usb debugging and try using adb n fastboot.
also, try to flash a newer recovery.img ( be careful no to use one not meant for ur phone e.g ns4g...)
post ur results.
good luck

can't find an option from within the phone to format the SD card - found an app on the store that is called "format sd" which did something and allowed me to connect to the USB once but it was very flaky and took a few attempts at the "turn on usb" screen to get it to connect. I'm not sure that it wasnt just deleting the data from the sd rather than formatting as it took maybe 10 seconds first time and now its done straight away if I try again.
Edit - i've used the stock erase usb command within the phone and the USB connection within the phone seems to becoming more stable - I can read and write data to it from the pc but it still struggles to connect first time.
No change with command line commands abd or fastboot neither are connecting.
I've come to the conclusion that maybe I need to flash a newer recovery image (ROM?) myself but where do I find one? And how do i check that it really is the correct one for my phone - which of the details are important - should i use the original stock details? I'm confused, remembering all I can use is the "Android system recovery <3e>" that only gives me the option of reboot, apply update from sd card, wipe data/factory reset, & wipe cache partition.
I flashed the wrong ROM with the clockwork rom app from within the phone I dont know what odin is.
Thanks for the pointer anymore ideas or direction appreciated.
Acne

Try to wipe from the stock recovery and then install this
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
It is the full 2.3.3. It will return your phone to complete stock 2.3.3
P.s sorry i am not being able to help more. I am myself in a far bigger trouble

I tried that rom but got the status7 error. That one worked before under clockwork but won't reflash now. I can do a factory reset under stock but will that make a difference? I thought all that did was reset user data not the system data. I think l need to wait for a new stock Tom to be issued.
Acne

Tried the reset phone from within the phone and reset using stock recovery, still cant flash the old 2.3.3 rom above getting the status 7 error:
assert failed ! less_than _int(1297306095. getprop(ro.build.date.utc"))
so the usb works fine from within the phone when the phone is running normally, when I connect the phone in fastboot mode it shows as an Android ADB interface on the "safely remove hardware" window but i cant use any command prompt instructions on the phone - using fastboot devices to show connected devices I get no reponse.
Any ideas?
Any pointers to a later rom that will correct my problems?
Thanks
Acne

After a bit of experimenting I find that when the phone is switched on normally I can use the ADB devices command to return the ID of the phone. The fastboot devices command still returns a blank.
Is this normal?
Does this mean I could flash the clockwork recovery image onto the phone? or can all that malarkey only be done in fastboot mode?
thanks
Acne

You need the fastboot devices command to return your phone info then you can fastboot flash recovery in order to try flashing a recovery that will allow you to flash the rom you are getting a failed message from. The stock recovery can only flash official updates put out by Google iirc.
I am thinking you are having driver issues on the PC you are using. Try another PC with fresh drivers or uninstall and reinstall the drivers on the one you have been using.
sent from the nexus of the 4g universe

I've read up on the driver problems, I tried the phone on two different pcs using two different methods on each to install the correct drivers. none work. The phone used to connect fine which is how i rooted the phone. I'm using the same pc, same supplied cable and can see the ADB mounted in the "safely remove hardware" window
The adb command works when the phone is switched on normally, but not fastboot command.
When in fastboot mode neither works. Looking in device manager the android adb interface is listed fine under android phone.
I'm pretty sure its not the drivers.
Doesn't the above prove that the pc connects fine but the phone is broken in fastboot mode?

You could still flash the latest 2.3.4 full ROM with ODIN. The Phone will be restored completely and then you can root it again.

Thats great Odin looks like it will be the way forward, just so I dont make another noob error could someone point me in the right direction for the correct version of odin and a guide on how to use it. I have looked around the forum but am struggling to find the relevant thread
I have tried the usb/2 button and it enters download, the version od odin that i found (1.81) does see the phone but I think that version is for the 9020 only I have the GT-i9023 so dont want to use the wrong programme/rom
Thanks
Acne

Ok took a chance and flashed the phone with odin - great it worked reset all the fastboot mode values back to their original ones when i got the phone. (seems I chose the correct rom) the only difference is that the Carrier info is now EUR not VDF as it was when I first got the phone.
Applied the auto update to 2.3.4
Tried at every step but I still have no fastboot or ADB access the phone just doesnt connect. Tried different leads, tried different usb ports - nothing.
I'm stumped now unless there are any advanced settings in odin I should try.
Acne
The

Discovered after the auto update to 2.3.4 that the USB connection from within the phone was "broken" again, To sort this i did a format cache and reset phone from the stock recovery which sorted the usb connection. so thats that one solved then.
tried again to connect via command prompt, unistalled drivers - reinstalled drivers - no change still no devices detetcted.
Any good ideas?

Solved
using the usbdeview mentioned here I uninstalled all the usb drivers on my pc that looked like they could be anything remotely connected to the nexus and samsung.
I ran and updated/download pretty much everything i could through SDK
Then I did everything I read in this thread
Up till then I had been using the fastboot command found and downloaded through this thread
That continued not to work but when i tried the fastboot in the android-sdk/tools folder I finally got fastboot access.
Solved Solved Solved
to get my phone unlocked and updated I did an odin restore to 2.3.3 let it auto update to 2.3.4 copied the su(superuser zip) to the sd card. flashed clockwork recovery and then installed the su.zip with clockwork. after that I installed the rom manager from the android shop and Inow have the phone just how i want it.
To all those that have helped with their ideas here many many thanks.
Acne

[Q] asus transformer sort semi brick need help asap please...

ok so ive had my tf101 rooted since i got the thing over a year and a half ago, i was running the megatron rom which was cm9 based and everything was good. today i tried to flash Eos4 and i got F%$ked out the a$$. so i did my standard procedure which was put the rom and gapps package on my device and then i wiped everything (after making a nandroid) and flash the rom along with its gapps. then i went to reboot it then i got shot back into recovery...so i was like wtf. i then found a way where if i hold the power and volume down for about 10 seconds i could cold boot android and once booted fix this problem with my recovery. unfortunately when i go to boot into android my device just bootloops on the boot animation ( ive left for about ten mins just to make sure) then i was like oh well ill just restore my nandroid, but for some reason clockwork mod touch wont let me use my microsd card, and its also not letting me restore from the backup i made earlier, it says files not found. i tried to connect it to my pc so i could just factory reflash it but unfortunately it will not be picked up by my pc through adb or apx.
so here is my main issue,
i just need to boot into android one time successfully so i can change the location of some ROM files and fix this stupid recovery bull****.
or if i could some how factory reset the tablet completely then that would be fine too
or or i could flash a different recovery that actually worked (currently on CWM 5.8.3.4 installed from rom manager which i realize now to be a huge mistake)
and i've tried ever tool on this forum as well and nothing works because it cannot pick up my device.
*** one other side note i am running windows 8 pro 32bit through Vmware (if this can be problematic)
thanks for any help in advance

To fix this, you will need to get your tablet recognized by your computer via ADB (in recovery) or APX mode.
You could have a bad cable, or it could be the VM causing the detection issues.
Is there a way you can connect it to a computer running Windows natively?
Does your computer make the new hardware sound when connecting?
Once you get it detected via one method or the other, here are my suggestions:
APX - Use the Naked Driver 0.72 and replace whatever driver is being used. Then use EasyFlasher to install TWRP 2.2.1.4 (it blows CWM away, and can read internal AND external memory)
ADB - use the Naked Driver 0.72 and replace whatever driver is being used. Then download the TWRP 2.3.2.3 blob from the TWRP project: http://techerrata.com/browse/twrp2/tf101
Call the downloaded file TWRP.blob.
Then run the following from your computer via ADB:
Code:
adb push TWRP.blob /sdcard/
adb shell
su
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Make sure it is a normal reboot to complete the recovery. Then reboot to recovery and you should be able to see the external card (so long as it is formatted for FAT32).

Thanks for the quick response and it probably is because I am using vmware... Unfortunately I don't have access to a windows machine right now. But I will definitely try to find one
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so now it looks like this... All i did was flash some random ass jb rom I found in my cwm folder... It has been like this for about 15 mins
Sent from my SAMSUNG-SGH-I747 using xda premium
** edit I'm assuming it got stuck boot the apps because now a my directories seem F&#cked up too... It now goes sdcard/0/0/0/(everthing else)

That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.

Lethe6 said:
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Click to expand...
Click to collapse
But my problem is I can't flash another recovery... I can't access the memory on my micro sd card... So like idk what to do
Sent from my SAMSUNG-SGH-I747 using xda premium

What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.

frederuco said:
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
Click to expand...
Click to collapse
I can't get into the os that's the problem... I just clean installed Windows via boot camp on my mac... Gunna try a few tools now... Hopefully I can get it back to stock... I'll update in a little bit
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so my computer can sort of detect it... I installed the drivers via brks root kit but when I plug it in in apx mode it says unknown device... Tried all my programs and they all failed...
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so I've tried to to reinstall the drivers... Tried to flash everything in apx and adb but it's not being properly detected By the PC... So I have no idea what to do at this point... If I could somehow either boot into android or flash TWRP
Sent from my SAMSUNG-SGH-I747 using xda premium

Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.

frederuco said:
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
Click to expand...
Click to collapse
Not to sound like a complete noob at this point but idk how to install these naked drivers
Sent from my SAMSUNG-SGH-I747 using xda premium

I think I installed the drivers right but idk can someone please like teamviwer or Google + hangout with me
Sent from my SAMSUNG-SGH-I747 using xda premium

Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.

Lethe6 said:
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Click to expand...
Click to collapse
Not working... :/ I swear it's not me
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] tablet not working properly

when i factory reset the tab and installed a rom. it started normally. i did everything normally and it showed google account manager has stopped.
so i tried going into CWM recovery mode but got me into stock recovery so factory reset the tablet and then tried wipe cache participation but shows error. I think that the problem is the cache and the dalvich. but i cant use usb debugging so i cant delete the cache and the dalvich.
:crying::crying::crying::crying::crying:
so does any body know how to fix this
thanks in advance :laugh:

Help cache partication error
yolo squad dodo said:
when i factory reset the tab and installed a rom. it started normally. i did everything normally and it showed google account manager has stopped.
so i tried going into CWM recovery mode but got me into stock recovery so factory reset the tablet and then tried wipe cache participation but shows error. I think that the problem is the cache and the dalvich. but i cant use usb debugging so i cant delete the cache and the dalvich.
:crying::crying::crying::crying::crying:
so does any body know how to fix this
thanks in advance :laugh:
Click to expand...
Click to collapse
Can anyone help me please!!!!!!!

yolo squad dodo said:
so i tried going into CWM recovery mode but got me into stock recovery
Click to expand...
Click to collapse
You are not reading what you are typing.
Obvious answer: If you end up in the STOCK RECOVERY you simply do not have a custom recovery installed (Clockworkmod as you wrote). Get yourself a copy of a recent recovery from AndroidAndi's download repository (TWRP, Clockworkmod Swipe, PhilZ Touch), and flash the .tar.md5 of the recovery with ODIN in download mode.
Obvious question: How did you flash a ROM, other than some OTA Stock Samsung update on the device itself, in the first place when you don't have a custom recovery installed in order to do so?
EDIT: What exactly do you mean by "factory reset"? Did you re-flash your tablet with a Stock ROM? If that's the case, then any custom recovery you had installed was wiped and replaced with the stock recovery. Hence why you now don't have a custom recovery anymore.

BoneWithABeagle said:
You are not reading what you are typing.
Obvious answer: If you end up in the STOCK RECOVERY you simply do not have a custom recovery installed (Clockworkmod as you wrote). Get yourself a copy of a recent recovery from AndroidAndi's download repository (TWRP, Clockworkmod Swipe, PhilZ Touch), and flash the .tar.md5 of the recovery with ODIN in download mode.
Obvious question: How did you flash a ROM, other than some OTA Stock Samsung update on the device itself, in the first place when you don't have a custom recovery installed in order to do so?
EDIT: What exactly do you mean by "factory reset"? Did you re-flash your tablet with a Stock ROM? If that's the case, then any custom recovery you had installed was wiped and replaced with the stock recovery. Hence why you now don't have a custom recovery anymore.
Click to expand...
Click to collapse
Odin won't recognise my tablet in Odin mode neither does my computer is there another to install a CWM recovery. By the the I do have back up on the phone if that helps.
By the way I am a noob

yolo squad dodo said:
Odin won't recognise my tablet in Odin mode neither does my computer is there another to install a CWM recovery. By the the I do have back up on the phone if that helps.
By the way I am a noob
Click to expand...
Click to collapse
Just to recap on the steps you should have done...
1. You downloaded the .tar.md5 of the recovery you want to install, from Android Andi's filehost, on your PC
2. You installed the Samsung USB drivers on your computer
3. You installed ODIN on your computer
4. You unplugged the tablet from the charger and powered it off
5. You took your tablet and HELD VOL-UP while you powered it back on (to get into bootloader mode)
6. You plugged the tablet in to the computer and waited for a moment while Windows was installing the driver
--- Here the story ends, according to what you wrote as you say ODIN does not find the tablet.
Well, are you sure you did the steps so far in that order? Can't be that ODIN doesn't detect the tablet when it's operational (read: no a total dead brick) and it's in download mode.
The ONLY problem possible: You installed Samsung KIES, and not just the USB drivers, on your computer. KIES interferes with ODIN. You need to exit ODIN, bring up the Task Manager (press CTRL+ALT+DELETE and select "Task Manager"), find "kies" and end the running process(es) - ignore any warning message.
If that's too complicated: Uninstall KIES and then find the "Samsung Mobile USB drivers" installation package ... with a bit of searching (just to assign some homework to you) you will the links right here in this forum section more than just once.
Once KIES is terminated, or uninstalled and just the USB drivers installed, start ODIN again ... now it should detect the tablet.
Once ODIN confirms that the tablet is detected...
7. Select the .tar.md5 of the recovery as the "PDA"
8. Flash the recovery. Once complete the tablet rebooted into the newly installed recovery.
As for on-device flashing. That's possible...
- Your installed ROM must be ROOTED (no root, no fun)
- You need Chainfire's "MobileODIN" (the free version from the Play Store would suffice), and you need to let MobileODIN install the "p311x flashkernel package" (I think with the free version you need to download it manually from Chainfire's thread and install it manually) - jump into Chainfire's thread and read on
Once you have Mobile ODIN installed it is just a matter of:
- Download the .tar.md5 of the recovery on your tablet once more (or transfer it over from your PC)
- Start Mobile ODIN
- Select the .tar.md5 of the recovery (should automatically be set as a "PDA")
- Flash and reboot into the recovery
However, as a fair warning ... as with every flashing of your device ... keep in mind something could go wrong (just to straighten it out that there's always room for user mistakes or murphy's law getting into the way ("Everything that can go wrong will go wrong"))

BoneWithABeagle said:
Just to recap on the steps you should have done...
1. You downloaded the .tar.md5 of the recovery you want to install, from Android Andi's filehost, on your PC
2. You installed the Samsung USB drivers on your computer
3. You installed ODIN on your computer
4. You unplugged the tablet from the charger and powered it off
5. You took your tablet and HELD VOL-UP while you powered it back on (to get into bootloader mode)
6. You plugged the tablet in to the computer and waited for a moment while Windows was installing the driver
--- Here the story ends, according to what you wrote as you say ODIN does not find the tablet.
Well, are you sure you did the steps so far in that order? Can't be that ODIN doesn't detect the tablet when it's operational (read: no a total dead brick) and it's in download mode.
The ONLY problem possible: You installed Samsung KIES, and not just the USB drivers, on your computer. KIES interferes with ODIN. You need to exit ODIN, bring up the Task Manager (press CTRL+ALT+DELETE and select "Task Manager"), find "kies" and end the running process(es) - ignore any warning message.
If that's too complicated: Uninstall KIES and then find the "Samsung Mobile USB drivers" installation package ... with a bit of searching (just to assign some homework to you) you will the links right here in this forum section more than just once.
Once KIES is terminated, or uninstalled and just the USB drivers installed, start ODIN again ... now it should detect the tablet.
Once ODIN confirms that the tablet is detected...
7. Select the .tar.md5 of the recovery as the "PDA"
8. Flash the recovery. Once complete the tablet rebooted into the newly installed recovery.
As for on-device flashing. That's possible...
- Your installed ROM must be ROOTED (no root, no fun)
- You need Chainfire's "MobileODIN" (the free version from the Play Store would suffice), and you need to let MobileODIN install the "p311x flashkernel package" (I think with the free version you need to download it manually from Chainfire's thread and install it manually) - jump into Chainfire's thread and read on
Once you have Mobile ODIN installed it is just a matter of:
- Download the .tar.md5 of the recovery on your tablet once more (or transfer it over from your PC)
- Start Mobile ODIN
- Select the .tar.md5 of the recovery (should automatically be set as a "PDA")
- Flash and reboot into the recovery
However, as a fair warning ... as with every flashing of your device ... keep in mind something could go wrong (just to straighten it out that there's always room for user mistakes or murphy's law getting into the way ("Everything that can go wrong will go wrong"))
Click to expand...
Click to collapse
odin recognize tablet and it got flash or what ever its called. it restarted but it didn't go into recovery but just restart as normal

I got it working by installing custom rom.
Thanks a lot by the way for the tips

yolo squad dodo said:
odin recognize tablet and it got flash or what ever its called. it restarted but it didn't go into recovery but just restart as normal
Click to expand...
Click to collapse
For future reference: keeping VOL DOWN UP held while powering on/rebooting the tablet takes you into the recovery in case you borked the system and selecting "Reboot" -> "Recovery" from within the _custom_ ROM's power menu is not an option (the Stock Samsung ROM does not have that option by default). Though keep in mind that this only works when the tablet is _NOT_ connected to the charger/computer ... when the USB cable is plugged in it seems to ignore the hardware keys.
yolo squad dodo said:
I got it working by installing custom rom.
Thanks a lot by the way for the tips
Click to expand...
Click to collapse
Great you got your recovery and custom ROM installed. Have fun.

BoneWithABeagle said:
For future reference: keeping VOL DOWN held while powering on/rebooting the tablet takes you into the recovery in case you borked the system and selecting "Reboot" -> "Recovery" from within the _custom_ ROM's power menu is not an option (the Stock Samsung ROM does not have that option by default). Though keep in mind that this only works when the tablet is _NOT_ connected to the charger/computer ... when the USB cable is plugged in it seems to ignore the hardware keys.
Great you got your recovery and custom ROM installed. Have fun.
Click to expand...
Click to collapse
Umm isn't recovery power and volume UP? At least that's how it is on my 7'' tablet and the 10'' I rooted and installed a ROM on.
jrc2
Sent from my T-Mobile S2 using Tapatalk

jrc2 said:
Umm isn't recovery power and volume UP? At least that's how it is on my 7'' tablet and the 10'' I rooted and installed a ROM on.
Click to expand...
Click to collapse
Now that you mention it... yes, you're right jrc... "VOL DOWN" == Download Mode / "VOL UP" == Recovery (I failed to recall the "UP as in update.zip" association).

How to turn on Pantech Discover USB debugging? (via CMD, Recovery, ADB)

I have problems with my pantech discover magnus P9090, the problem is that the phone is completely bricked and dead. When i turned on the phone, it simply just shows BLACK SCREEN ( No Logo and nothing else). My assumption is that there is no OS inside or something causes it to be bricked. I have done almost everything by using Android Recovery (Not custom recovery) to do factory reset and wipe cache. I rebooted it and it doesn't work either. So i found a solution which is by using apply update from ADB. I understand the process but the only problem is
The device is not detected by ADB when i type "adb devices" it could be two problems:
a. No drivers for this phone installed (While i try to update driver, it fails)
b. USB Debugging off (Since phone can't get into OS, so im confused how to turn it on via other ways)
I got the Custom rom and CWM recovery image but how can i install the recovery and ROM if ADB isn't detecting the phone. I can't even use sideload command.
My plan to fix this is by installing CWM with the command "fastboot flash recovery [filename]" and then using CWM to push the file ROM into phone and install zip in SD card. However, it links back that i need the phone to be detected first. Anyone can help me? Thank you so much. Im so badly want to revive this phone. :good:

There's no other way until pantech usa release pdl file for restore discover..
Sent from my ZTE N986 using XDA-Developers mobile app

Install Stock Recovery on Unrooted Phone That Cannot Connect to a PC

Hey,
I own a WileyFox Storm that runs Cyanogen OS (kipper) as stock. A while back, I tried to root it, but failed so gave up. As it turns out, I forgot to get rid of the TWRP CR (which was an edition specifically designed for the Storm). There is now an update which I would like to install, but obviously it does not work because I do not have stock recovery.
MY PHONE IS NOT ROOTED!!!
I was going to flash the stock recovery using ADB fastboot, however my phone is now refusing to be recognised by my PC. Yes;
- I have the correct drivers installed.
- I have enabled USB debugging (I have also tried disabling it).
- I have tried rebooting both my phone and PC.
- I have tried rebooting my phone and wiping Cache and Dalvik Cache.
- I have tried with a different USB cable, and tried using a different USB port.
- I have tried removing my SD card.
My phone says that it is charging (which is is) when it connects to my PC, but nothing comes up, anywhere. No notifications (on both devices), ADB nor fastboot recognises it, no *chime* sound on my PC.
I cannot try using a different PC (I only have one). So, how can I replace the TWRP recovery with stock recovery???
Thanks )