Database Users

Wrong SPL zip file. Now what? [SOLVED]

[SOLVED. READ BELOW FOR DETAILS]
HI all.
I've managed to brick my Hero (T-Mobile G2) by flashing the wrong SPL file.
To make things more difficult I've lost the USB cable.
I can still:
Power+Menu (three vibrations + blinking green)
Power+Back (Fastboot)
Power+Search (Storageclean)
Power+VolumeDown (HBOOT, SD checking ...)
Is there a way to reflash the right SPL with one of these menus?
I've not found any similar case here and in MoDaCo.
Thanks in advance.
[SOLUTION]
This case is particular as there is no system available to use the "adb shell" commands. Nonetheless it's recoverable.
At least in one case
Almost everything comes from MoDaCo.
Despite I would say I'm not a real newbie, this time was a little bit harder than with other embedded devices for some reasons I'll explain later.
What do you need?
1. A miniUSB cable. Now I know that any miniUSB can work.
2. A Windows XP PC. A Linux or Mac OS X should also work. Read below.
3. The right USB software driver (I used this one) otherwise it won't work.
4. A modified recovery image (I used this one) that has flashing capabilities from the SD.
5. A working SPL (Second Program Loader) image (I used this one, thanks to the enlightner.
6. A system ROM image (again, I used this one).
What was the problem?
I used to play also with a Magic and still had an SPL zip of its on my SD.
I already had rooted and modded my Hero with MoDaCo's mod.
By mistake I flashed that SPL zipped image into my Hero and since then nothing was working any more.
The boot process was simply stopping at the "G2 Touch T-Mobile" screen up to the complete battery drain.
The directions found here were ineffective due to the fact that there was no running system to execute the "adb shell" commands.
I am using 99.99% of the time a Linux laptop but decided to get a Windows XP PC in order to simplify the troubleshooting while asking people for help and hints.
Maybe in the future I'll dare to reproduce the problem and solution with Linux. Maybe,
But let's see a stepwise procedure.
How I solved it (impossible to me without MoDaCo's and englightner's help, kudos to them)!
0. Unpack the USB driver and the recovery image ZIP files somewhere into your PC. Put the SPL and the system ROM image zip files into the SD card. Use the root directory of the FAT partition in case you have already partitioned it.
1. Switch off the Hero (by pulling the battery out).
2. Turn it on again without the USB cable in by pressing the back and the power keys. I've noticed some different behaviour if you keep the cable plugged in.
3. A white screen (the Initial Program Loader aka IPL aka Fastboot) will pop up.
4. Plug the USB cable in both the Hero and the PC. The screen will now show in red "FASTBOOT USB".
5. Windows should warn you about some unknown hardware having been plugged (Android 1.0). Ask for a manual installation by browsing to the directory where you unpacked the USD driver. Install it. No reboot is required (unbelievable!).
6. Open a command line session on your PC (Start-->Execute-->CMD on Windows), change the current directory (cd) to where modified recovery image has been unpacked and where both the fastboot.exe and cm-hero-recovery.img files are located.
7. From the command line run this command (without the quotes): "fastboot boot cm-hero-recovery.img". You'll see a green progression bar rising on the right side of the Hero screen and after 1 second you'll see the modified recovery image running.
8. At this point I tried to recover a previously saved nandroid backup. But for some reason this time the recovery was complaining about a chown/chmod not being able to change the permissions on a system file! So it's useless to try it.
9. Instead I asked to flash the SPL zip file. It worked fine and I asked for a reboot.
10. the final step was to pop the recovery tool again (Home+power, keep the home pressed until you'll see the friendly black and green screen) and to slash the system ROM zip file.
I also reset all user data before doing it. I'm not sure whether this reset is required.
11. At the reboot the flashed system ROM was happily waiting for me to customise the settings.
12. As a last check, I rebooted once again the Hero to see whether the solution was permanent. And it was.
Few suggestions for seniors.
Please, please be patient with newbies. This could be the first time they hit the wall and panic and frustration can play an important and irritating role.
Please, please be as precise as possible. What a senior thinks is an implicit piece of information, can lead to hours of frustration for the newbie. For example, the SUB driver installation is not mentioned very often in any thread. It looks trivial. It's not.
Please, please be positive to newbies. By encouraging them they'll become less newbies than they are now.
And a few suggestions for juniors (like me).
Please, please don't panic! If there's a solution, you don't need to panic. If there's none, you don't need to panic as well.
Please, please be precise in describing the problem (I've not been myself). Small unseen details can matter a lot.
Please, please don't blame people for late answers. Very probably they are busy with their own job, life or hobbies.
Please, please remember that if you are in trouble is very probably due to your own mistakes. Not someone else's. You are playing with low level stuff, not just application settings.
If you decide to follow someone's directions, please do it carefully. If you take some decisions on your own, please document them in the thread.

If you can get to fastboot with power and back, then all is not lost. And most importantly it's not a 'brick'. A 'brick' is a device that won't turn on.
You can flash the recovery via fastboot (using this guide) then a new ROM (I suggest my custom ROM) but, er, you're obviously gonna need a USB cable!
P

I was already using your marvelous mod, though.
I only took the SPL file from the wrong directory (I have been playing also with Magic, aka G1).
The cable is a huge problem, now.
At the moment I'm using a mini-USB cable which is good for charging the battery, but has no effect on the communication side.
Can I put some file in the SD card from my PC in order to have it booted into?
I still have a couple of nandroid backups in the SD but have no idea whether this makes any difference.
Anyway, thanks not just for the hints. Your 1.5 (1.5.1 when I'll fix my problem) rocks!

A real miniUSB cable should work fine. Yours must be only wired for charging. Go and buy one.
There's no other way to do it unless power+home gets you into recovery (which it sounds like it should?)
P

The mini-USB comes from my USB 2.5" HD.
It works with cameras and other mini-USB devices for full dvice access.
But it does not work with the Hero.
The original cable looked different from this one because of the asymmetric shape (and possibly an extra pin or two).
The Hero cable looks like it's proprietary design and buying one seems quite difficult. Would any HTC USB cable work?
Now I'm not in the Netherlands anymore and here the HTC stuff looks quite uncommon to have a cable lent.

I never use my HTC cable, I use a standard mini USB cable.
P

OK.
I've bought a brand new mini-USB cable. It works with my Nokia phone, my digital camera dnd also my USB disk.
1. I've donwloaded the file from the guide MoDaCo referred previously.
2. I've unpacked the ZIP file, opened the CMD session, CDed to the directory containing the adb.exe file
3. I've booted the phone to the FASTBOOT (VOLUMEDOWN+POWER)
4. I've connected the phone to the cable.
5. The HERO screen says now "FASTBOOT USB"
6. I've run the command "adb shell reboot bootloader"
7. I get "error: device not found".
What's next?
P.S.
Steps 3 and 4 are not mentioned in the guide, though.

You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
I might be able to help you out.

Try following the guide linked above.
You can't do ADB until you've done the 'fastboot boot cm-hero-recovery.img'.
Seriously... how hard can it be to read thru a handful of steps!
P

You are right! It's hard unless you already know how to.
I quote:
- download this file and extract it to your PC or mac
- open a command prompt to the directory containing the extracted files
- type the following commands (prefix each command with ./ if you're on a mac)
So far it's trivial ...
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
That could also be trivial if:
1. I knew about the driver installation (quite later in the thread)
2. I knew in which initial status the phone is to be
Of course, a bit at a time I find everything.
Maybe re-editing the original post to include all the bits in one single place would both boost the success rate of n00bs like me (really) and lower the amount of stupid questions (really) like mine.
Anyway, I need to thank you very much!!!

Hmm, bad news, ust spoken to an extremely knowledgeable friend of mine, and he says your device is knackered.
P

I'm impressed the SPL actually booted on a Hero.
It's is a "real" Hero you have right? aka T-Mobile G2 Touch?
Fastboot can be used when you are in HBOOT, with FASTBOOT USB being displayed.

So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P

packetlss said:
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Click to expand...
Click to collapse
Good to know. I have no idea about this specific device!
And the help is quite fragmented among a large number of threads.
packetlss said:
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
Click to expand...
Click to collapse
HERO CVT
HBOOT-1.33.2005 (HERO10000)
MICROP-010e
RADIO-6.35.05.15
Apr 20 2009,15:30:43
packetlss said:
I might be able to help you out.
Click to expand...
Click to collapse
I hope so.

Try doing what modaco suggested and see where that ends up.

modaco said:
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
Click to expand...
Click to collapse
I hope to fix mine.
Anyway, is there any comprehensive guide about the booting (not rooting) process with the software stack and the "cheat codes"?
I don't think I'm really a n00b, but the fragmentation of information is quite large for these marveloous Android phones.

The HEROIMG.zip has been flashed, I presume, as a vertical blue bar appeared on top right screen.
After fre minuted the process ended ... with no news.
At the reboot everything is again as before.
Home+Power won't make the CyanogenMode+JF menu pop up.
The simple boot itself won't make my Hero botting in any system.
Only a big "G2 Touch T-Mobile" on the black background.
Now what?

That HEROIMG.zip contained a hboot. When you boot to bootloader is still the same?
You say 'fastboot boot recovery.img' (as per my instructions) didn't work?
P

'fastboot boot recovery.img' works.
It's the subsequent step that doesn't. I cannot mount /sdcard (error: device not found)!
And even recovering a previous nandroid backup won't help.
What I understand there's something in between the fastboot and the actual image (the SPL?) that is missing doe to my original error.

Does the bootloader still show the old version?
P

Any advise?

I recently upgraded my G1 to the cyanogenmod 2.1 ROM and everything went fine untill i went to the market and installed a program called ROM manager. while i was using ROM manager it had an option, i cant remember what its name was, that said it fixes FC's if needed. Well i was getting those in ROM manager so i clicked it. It did a bunch of stuff and then suddenly tossed an error at me. Next thing i know im getting LOTS of FC's and when i rebooted my phone im suddenly stuck staring at the G1 boot screen and thats where it stays......indefinetly.
I cant get into recovery mode, already tried that. And so far the only thing(that i know of) that i can do is get into fastboot. Does anyone know how i can fix this? Its gotta be software related from whatever that ROM Manager program did to my permissions. But now im basically bricked and cant do anything.
My storage card still has all of the ROM's and files from when i flashed last but i dont know if or how i can use that to re-flash my phone again and start over.
Any suggestions?

I had a similar issue just yesterday. Dowloaded rom manager from the marketplace - attempted to flash recovery - pulled an error and ended up on the G1 screen. Could not get into recovery, but fastboot was available.
I followed these instructions
( reboot holding camera button, connect usb and press back button )
on pc
HTML Code:
fastboot erase system -w
fastboot flash recovery <recovery.img>where <recovery.img> is the full path to the recovery you want to flash
I had to do a full erase in fastboot - that is the first line of text above, I then flashed my recovery.img again - that is the second line of text above (I placed my recovery.img file directly in the adb folder - so it easy to find )
Once I was able to get back into recovery - I restored my last back-up, and the phone booted once again.
If you do not have any backups - I am not aware of the next step. Hopefully someone with more experience can direct you accordingly
Good luck

How is it that you send the commands? I plug in my USB, then hit back and it says FASTBOOT USB but how do i input the HTML codes to get it to do anything?
Do i make an HTML file on the pc and upload it, if so, how? I understand all of it except how to get the commands into it.
Well that and what the full path will be for the recovery.img.

well i feel like a total moron !!! lol
I had been being a script kiddie for the last few years and forgot my roots. I got it figured out and got the commands sent to fastboot in a CMD prompt.
Ugh, i gotta stop using google so much and finding all the easy ways out of things that others have already written.
Thanks for the help, much appreciated and worked a treat. I flashed everything and its working great again

install mods and updates without fastboot?

since i somehow managed to lose the ability to connect via fastboot..
is there another way for me to install zips?
phone rooted with 1 click..
also open to ideas as to why fast boot only says < waiting for device > now?
no conflicts in dev mgr, have uninstalled and reinstalled the sync and driver..
removed from dev mgr..
updated while in fastboot mode etc..
no dice..
318-us
official 2.2 rom
att unlocked.
Black

can i convert a zip to a pkg and rename it update.pkg?
right now all i have is the pkg option when i hold the vol buttons and power.
i recently flashed to the new update which had fixes and newer baseband etc..
that went fine but the the steve 1.5 came out and i want to switch back.
as stated above thats not possible now since fastboot refuses to see my device.
Can someone put it in a pkg format for me maybe?
I dont like this official release...
its slow..it has lame apps, etc..
lil help?
dont really want to formate my laptop to fix a usb driver issue..
especially when the mass storage and sync work just fine..

+1
cant use fastboot after update to 318
rooted by super one click
black
unlock 00

there is a way of flashing custom recovery via terminal emulator. DEVICE NEEDS TO BE ROOT'D
save .img on to SDcard and rename to recovery.img
then open terminal emulator and type
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot (press enter)

I had the waiting for device problem. I read a few tips saying to try...
Type "adb devices" to see if its recognised there.
Make sure streak is the only device plugged in usb.
If using a hub try a different slot or direct into pc.
Turn streak off and into fastboot while still connected to pc (after pc loads drivers)
Reboot pc.
I swapped usb soccets and that fixed it for me
Hope one of these tips works for you too.

Thank you. I actually tried all of those things...before i posted.
wondering if maybe the 318 isn't compatible..
it says its in fastboot mode..
everything else works..sync, sd card shows in explorer etc etc..
just no fastboot.
luckily the recovery still allows me to do .pkg but i need zips too
very annoying..
I ordered a M11XR2 and will try with that when it arrives..
tina333 said:
I had the waiting for device problem. I read a few tips saying to try...
Type "adb devices" to see if its recognised there.
Make sure streak is the only device plugged in usb.
If using a hub try a different slot or direct into pc.
Turn streak off and into fastboot while still connected to pc (after pc loads drivers)
Reboot pc.
I swapped usb soccets and that fixed it for me
Hope one of these tips works for you too.
Click to expand...
Click to collapse

I have 318 and fastboot works for me.

I only had to reconnect the adb bootloader interface driver again (just like I had to the very first time).
It is just fine now...
http://forum.pocketables.net/showthread.php?t=8285

I've not had any issues with fastbooting, after installing 318, I've managed to flash clockworkmod aswell as the new Streakmod recoveries with my Windows 7 64bit.

reconnect the adb bootloader???
what do you mean?
you mean you plugged the usb cable in and ran fastboot?
lol
yeah..thats helpful
Radimus said:
I only had to reconnect the adb bootloader interface driver again (just like I had to the very first time).
It is just fine now...
http://forum.pocketables.net/showthread.php?t=8285
Click to expand...
Click to collapse

bigfoots1 said:
reconnect the adb bootloader???
what do you mean?
you mean you plugged the usb cable in and ran fastboot?
lol
yeah..thats helpful
Click to expand...
Click to collapse
NO....
The streak wasn't recognized on the PC in fastboot mode, so I went back to device manager and found the unrecognized android device and set it to use the bootloader driver... The same proceedure as was done the first time the streak was connected to a PC to setup fastboot.
Took almost 30 seconds to fix

as i said though.. i have no conflicts...
I can even remove it from the device mgr...put eh phone in fastboot mode where it is waiting for usb coinnection..plug the phone in.. iot installs the drivers then the phone sees this and shows fast boot...
so you would expect it to work right? wrong... it says waiting for device...
I have tried everything I can think of..
i got a good deal on a new m11xr2 with win 7 so i will have a fresh slate and will see what results i can get.
in the mean time.. how can i convert this steve 1.5.zip to a .pkg?
or even install it with some other sokution or method?
i have it rooted via one click...
i have root explorer...
what now? lol
there has to be a better way..
Radimus said:
NO....
The streak wasn't recognized on the PC in fastboot mode, so I went back to device manager and found the unrecognized android device and set it to use the bootloader driver... The same proceedure as was done the first time the streak was connected to a PC to setup fastboot.
Took almost 30 seconds to fix
Click to expand...
Click to collapse

Its easy to miss bits when its all going wrong so do check the sticky look here first for streak, I had to refer to it a few times. You definitely need clockworkmod or streakmod to flash updates. I believe you can do it via a terminal app with su privileges. There's a thread from a few hrs ago saying. I will find for you if you can't

Can zip be extracted and converted to .pkg?
Hell I would be content with just a way to install the performance tweaks...thats the main issue really...
Sent from my Dell Streak using Tapatalk

bigfoots1 said:
Can zip be extracted and converted to .pkg?
Hell I would be content with just a way to install the performance tweaks...thats the main issue really...
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
I know Steve mentions "if you haven't flashed official dell update" blah blah... so im guessing you don't loose performance unless you manually downgrade? Have you seen the thread I mentioned? The OP claims he changed the dell .pkg to .zip and successfully flashed via clockwork..
http://forum.xda-developers.com/showthread.php?t=869076

how does that help me?
when i power up holding the vol up and down buttons i only get the install Update.pkg option and when i choose it it takes me to the blue text screen when i choose to either update via pkg or reboot. its the Android system recovery utility GAUSB1A131800
there is no option or way to get an option to install zip.
I would like to be able to install the performance fix for 2.2 zip or steves 1.5zip
so do you understand now?
I cant get fastboot to work to install clockwork.
I only have the recovery utility...
tina333 said:
I know Steve mentions "if you haven't flashed official dell update" blah blah... so im guessing you don't loose performance unless you manually downgrade? Have you seen the thread I mentioned? The OP claims he changed the dell .pkg to .zip and successfully flashed via clockwork..
http://forum.xda-developers.com/showthread.php?t=869076
Click to expand...
Click to collapse

it seems like i remember a thread about converting zip to pkg..
I cant seem to find it though..
if you just rename it in root explorer you get a signing validation error when you try to install it..
so I'm still stuck on stock 2.2

The initial thread is irrelevant, Have you not flashed a clockworkmod or streakmod previously? I would guess its possible to store a recovery.img on sd then flash via terminal app, i cant see why not? You could also probably use adb (if you cant connect to that the theres apps to do it wirelessly)

yes, i have flashed many times...
I flashed to 309 recovery in order to install the latest dell Update.pkg which went just fine. then when i went back to flash clockwork i could no longer connect via fastboot.
and thats where im at now..
cannot get fastboot to flash clockwork so i can install zips..
hence im asking for a way to do it without clockwork/fastboot until i get that sorted..
tina333 said:
The initial thread is irrelevant, Have you not flashed a clockworkmod or streakmod previously? I would guess its possible to store a recovery.img on sd then flash via terminal app, i cant see why not? You could also probably use adb (if you cant connect to that the theres apps to do it wirelessly)
Click to expand...
Click to collapse

an I still believe the issue is that you do not have the correct bootloader driver installed on your PC as described here:
http://forum.xda-developers.com/attachment.php?attachmentid=397078&d=1283901727
The issue is your PC, not the Streak (most likely)

Strange Bootloop problems!!!

Ok, i have a mytouch 4g that has never been rooted. The problem with the phone is that all of the sudden when i try to turn it on it wont get pass the splash screen. It will just turn off and reboot to the splash screen over and over. Thing is that i can get into Hboot quite easily. I tried to reflash the stock IMAGE file and it does it well without problems. But once its done and i hit power to reboot, the phone just starts to bootloop again doing the exact same thing. I know its kinda odd but i read somewhere that if i can get into Hboot the eMMc is not fried. But then what should be the problem?

enelyam said:
Ok, i have a mytouch 4g that has never been rooted. The problem with the phone is that all of the sudden when i try to turn it on it wont get pass the splash screen. It will just turn off and reboot to the splash screen over and over. Thing is that i can get into Hboot quite easily. I tried to reflash the stock IMAGE file and it does it well without problems. But once its done and i hit power to reboot, the phone just starts to bootloop again doing the exact same thing. I know its kinda odd but i read somewhere that if i can get into Hboot the eMMc is not fried. But then what should be the problem?
Click to expand...
Click to collapse
Sounds like hardware problem = warranty replacment
RcMix 3D Darkside Glacier HD
Tdj's Demonspeed v7 Kernel
Virtuous OC Damean
ClockWorkMod Recovery 5.0.2.0

Thanks, thats what i thought. Just wanted to ask so if someone have seen this before maybe there was a solution for that. But yeah, something is not right and i also think its a hardware issue.

Same prob here...anything like odin for htc? Engineering mode? I used two diff zip files tha were supposed to be the same recovery/ stock image/zip... think it i15img.zip or something... one does not do anything cept try and parse and restart other goes thru ok ok ok ok ok ok then skips the tp tp writes and says deferred or something but looks to get the job done but nah... what are the tp writes I skips...think they are right before the radio write...arg too tired
Sent from my SPH-D700 using XDA App

vizionforever said:
Same prob here...anything like odin for htc? Engineering mode? I used two diff zip files tha were supposed to be the same recovery/ stock image/zip... think it i15img.zip or something... one does not do anything cept try and parse and restart other goes thru ok ok ok ok ok ok then skips the tp tp writes and says deferred or something but looks to get the job done but nah... what are the tp writes I skips...think they are right before the radio write...arg too tired
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
HTC's too pro to have odin
the stock image file is named "PD15IMG.zip" and should be flashed in the bootloader.

Same here, this one skip the tp tp saying Bypassed on the second tp but everything seems to run ok. Only thing is that when i hit power after the update it will just start with the bootloop again. Since this is a friend, I dont really know what version it was running. But i do know its never been rooted or anything like that. Its on .86.000 and S-on and everything. Im going to try the gingerbread just for fun and see what happens.

thinking tese are Gingerbread update fails?
Let us know how the gingerbread turns out...Someone must have a recovery zip? Its obvious the two files I am trying to flash named the same thing are not the same thing or one is corrupted....211mb takes an hour on my connection now ANYONE HAVE A RECOVERY ZIP? Is there a program like odin(OK NOW I KNOW TO USE CMD AND ADB) Now I need a mytouch button press sequence to get to ENGINEERING MODE? to write to the frickin thing...I thought HTC was gonna be better than Samsung in this respect...I have one good mytouch4g that I can get the serial using the command 'adb devices' that is once mytouch is booted up...so question is how do i get to engineering mode in my bad my touch(which wont boot) so I can PUSH the file in command line interface.

vizionforever said:
Let us know how the gingerbread turns out...Someone must have a recovery zip? Its obvious the two files I am trying to flash named the same thing are not the same thing or one is corrupted....211mb takes an hour on my connection now ANYONE HAVE A RECOVERY ZIP? Is there a program like odin(OK NOW I KNOW TO USE CMD AND ADB) Now I need a mytouch button press sequence to get to ENGINEERING MODE? to write to the frickin thing...I thought HTC was gonna be better than Samsung in this respect...I have one good mytouch4g that I can get the serial using the command 'adb devices' that is once mytouch is booted up...so question is how do i get to engineering mode in my bad my touch(which wont boot) so I can PUSH the file in command line interface.
Click to expand...
Click to collapse
Turn the phone completely off, and turn it on again using volume down+power buttons. This enters hboot, or bootloader, where you flash the stock PD15IMG.zip file.
Sent from my HTC Glacier Sense 3.5 using xda premium

Unstick my heart
I should be able to communicate with device using adb push in command line interface hboot then? I dont see any device serial with adb devices
...Was hoping there was an engineering mode like samsung has...Well some different output here getting me excited...Img zip (211mb) that used to just stall with the other stock image zip I used (that does not parse) has at least allowed the img crc to work... below are my output pictures
http://www.flickr.com/photos/[email protected]/6447958131/
and this is the .zip (output picture of it anyway) (312mb)that I first used, seemed to work better than the one I had to rename in a recent post in Q&A forum, that said the zip that seems not to work unstuck img crc so now it reads hmmm....any ideas?
http://www.flickr.com/photos/[email protected]/6447957849/

vizionforever said:
I should be able to communicate with device using adb push in command line interface hboot then? I dont see any device serial with adb devices
...Was hoping there was an engineering mode like samsung has...Well some different output here getting me excited...Img zip (211mb) that used to just stall with the other stock image zip I used (that does not parse) has at least allowed the img crc to work... below are my output pictures
http://www.flickr.com/photos/[email protected]/6447958131/
and this is the .zip (output picture of it anyway) (312mb)that I first used, seemed to work better than the one I had to rename in a recent post in Q&A forum, that said the zip that seems not to work unstuck img crc so now it reads hmmm....any ideas?
http://www.flickr.com/photos/[email protected]/6447957849/
Click to expand...
Click to collapse
Once the phone is in bootloader, connect it to the computer, and you should see "fastboot USB" on the phone. Then open up adb, and type
Code:
fastboot devices
Sent from my HTC Glacier Sense 3.5 using xda premium
EDIT: here, download THIS FILE, rename it to PD15IMG.
then place it in the ROOT of your SDcard (not in any folders)
turn off and reboot the device into bootloader
bootloader should find the file and ask if you want to update
not sure if this is the method you used... tell us how it goes

Hmm Command did not say i had any devices (blank line) but my command line interface is in fastboot / adb(whats the differnce?) seems like it sees it? tell me if Im wrong... The command 'Fastboot devices' brought up long dir of commands, then I tried the following commands faastboot push and update PD15IMG (See pic below) Thanks for your help! I will try your zip! (but I would like to push from command line fastboot)
http://www.flickr.com/photos/[email protected]/6448265267/
Currently downloading ur zip thx...23 mins left :\
THANKS!

vizionforever said:
Hmm Command did not say i had any devices (blank line) but my command line interface is in fastboot / adb(whats the differnce?) seems like it sees it? tell me if Im wrong... Fastboot devices brought up long dir of commands for adb? then I tried following commands (See pic below) Thanks for your help! I will try your zip! (but I would like to push from command line fastboot)
http://www.flickr.com/photos/[email protected]/6448265267/
Click to expand...
Click to collapse
does your device say that it's "fastboot USB" somewhere on it? if it says "HBOOT USB", manually scroll to fastboot and select it.

no it does not seem to see it is connected
http://www.flickr.com/photos/[email protected]/6448372103/
I know USB works because it attempts to orange led flashes/charges before it turns on but it does not say usb after fastboot
still waiting for download...29 mins remaining at 72kb per sec groan

vizionforever said:
no it does not seem to see it is connected
http://www.flickr.com/photos/[email protected]/6448372103/
Click to expand...
Click to collapse
hmm.. might be because you don't have the engineering bootloader.
my mom's is S-on as well, and computer can't see it through fastboot.
anyway, just use the method i told you, move it onto the SDcard manually

Computer cant see it, but can it write to it?(i want to try) What is proper command to push pd15IMG in adb/fastboot? should I do it in adb or fastboot on computer? and what mode on phone: hboot or fastboot? thx G

vizionforever said:
Computer cant see it, but can it write to it?(i want to try) What is proper command to push pd15IMG in adb/fastboot? should I do it in adb or fastboot on computer? and what mode on phone: hboot or fastboot? thx G
Click to expand...
Click to collapse
i meant taking out the SDcard and connecting the SDcard to the computer, and transfer files that way.

Understood what u meant, just wanted to try usb push ind adb while file is downloading...

vizionforever said:
Understood what u meant, just wanted to try usb push ind adb while file is downloading...
Click to expand...
Click to collapse
don't think that's gonna work :/
sorry

ehh crap same thing skips tp writes....Still stuck, any other .zip to try? HTC Device(without seperate engineering mode does not seem to more "pro" (but the htc windows drivers, they seem more robust
What to do now :| ???
thx G
---------- Post added at 09:36 PM ---------- Previous post was at 09:12 PM ----------
same thing bootloop
computer now sees a unknown usb device anyone have the .inf? Google search for "mytouch .inf" showed only 6 results none I can use... Would rather use a .inf and install from disk than use .exe
EDIT: flashed http://forum.xda-developers.com/show....php?t=1174344
not it writes to #7 TP but not #8 still in bootloop... Now cant flash cause that is most recent... Can I try to flash any custom roms? or... My s is on

Its a waste of time people, sorry to say but this is definetly a hardware issue and its been spreading all over the world with people having issues on that same subject.

[Q] Installing Custom ROM on Wrong OS Version, Looking for Solutions

I apologize if this question has been answered already, but I just spent 15 minutes using the search button and could not find a response.
I just installed Matr1x v10.5 (http://forum.xda-developers.com/showthread.php?t=2007231) onto my Nexus 4 but it had JB 4.2. Based on the version notes of the thread, I assumed that it was backwards compatible with my phone and therefore installed the new version on my Nexus 4. Now every time I turn on my Nexus 4 the screen is blank. What can I do to fix this issue? Will it require a reset so that all my data is lost? Thanks.

What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app

failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.

pooq said:
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
Click to expand...
Click to collapse
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.

failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Chromium_ said:
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
Click to expand...
Click to collapse
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?

pooq said:
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
Click to expand...
Click to collapse
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app

failly said:
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?

pooq said:
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
Click to expand...
Click to collapse
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app

failly said:
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.

pooq said:
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
Click to expand...
Click to collapse
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app

failly said:
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with. I am presently trying to find a way to copy the downloaded Nexus image files provided online into my internal storage so I can install them.

pooq said:
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with.
Click to expand...
Click to collapse
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app

You just have to do the following :
A) flash a recovery via fastboot (fastboot flash recovery recovery.zip)
B) now go ahead and boot from your recovery, and push the rom of your choice, in case you don't have one already inside your sdcard (adb push ROM.zip /sdcard/ROM.zip)
C) flash your recently copied rom of choice to your phone. (if necessary, wipe data, cache and dalvik cache)

failly said:
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I just spent a couple of hours reading through the guides (and trying them out) which led me to several other guides. To be incredibly honest, I am completely confused as there is a plethora of new information thrown at me. I have to pose several questions before I continue:
1) When you say bootloader, are you referring to the fastboot bootloader screen that pops up after holding the volume down button and the power button? I just wanted to confirm this as I am starting to feel you are referring to something different after reading several guides.
2) Is the scenario 2 guide you posted basically a method to "sideload" the JB 4.3 into the storage of my Nexus 4 so I can install it via Recovery Mode?
I tried installing the drivers but I cannot seem to do it successfully as I do not even have a starting OS for my phone in the first place. I can not access a theoretical "Developer Mode" either from when I first rooted my phone.
So basically, I do not understand how I can get the direct downloads from Google (the JB 4.3 files) and get them into the internal storage of my Nexus 4 to install the OS.
Is there a simpler way to do this? If not, here is my current progress. At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.the OS[/B]. Is there a simpler way to do this? At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.

Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.

wammie said:
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
Click to expand...
Click to collapse
The first thing I'd like to do before reporting my progress report is to thank you and failly for taking the time to help me out. You both have contributed tremendously in trying to help me out with this, so I would like to thank you both for that.
1) I had installed the sdk program and changed the adb path (following this guide http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/)
Following wammie's guide:
2) Booted into bootloader
3) Downloaded and installed NEXUS 4 TOOLKIT V2.0.0 (had used it before but it didn't work for me so I relied on a different program to root my phone). Renamed fastboot-toolkit to fastboot
4) Typed fastboot devices in in cmd, does not recognize phone
5) Uninstalled current usb drivers and installed usb drivers provided. The driver I chose to install for was titled "Android". The other ! mark was "Base System Device" which was something I had never seen before until today when I had reinstalled usb drivers
6) Typed fastboot devices in cmd again and still nothing has changed
I am unable to continue any further as fastboot does not recognize my phone when I have it under bootloader. I had downloaded all the files that were recommended in your post. I think the reason why I cannot access fastboot devices is because there is literally no OS running in my phone. I could be wrong though.
I guess I'll take a break and call it a night since I've been trying to fix this problem the past 13 hours or so. Any additional feedback and support is appreciated!
Additional Notes: I have tried this both on my laptops (Windows 8) and on my desktop PC (Windows 7)

Luckly, if windows doesn't recognize your device while in fastboot it isn't because you don't have a OS installes but because not correctly set up drivers.
I posted a link some posta ago about a toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
When opening the program at the top there is a button called full driver installation, press it and follow the instructions.
Sent from my Nexus 4 using xda app-developers app

http://i.imgur.com/sOT7FGh.png
http://i.imgur.com/WNEKb0z.png
http://i.imgur.com/vUmTDcZ.png
http://imgur.com/da7NGwB
http://i.imgur.com/bjmhXZv.png
This is what you should do when you are updating the drivers, its imperative you get those drivers working. Otherwise, you won't get access to fastboot.

Oh I would recommend using a Windows 7 PC.
Windows 8 can also do the trick but you maybe need to disable driver signature enforcement, so you better go with windows 7 for now.
Sent from my Nexus 4 using xda app-developers app

Status Update:
I had spent a whole day reformatting my Windows 7 machine and am back at it. I have made a bit more progress than before.
1) After typing in fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img in command prompt, under the "List of devices attached" it is blank (i.e. there is no device attached). http://i.imgur.com/TnyBCKS.png
2) I have successfully installed the usb driver on my PC the first time when the only explanation mark was titled "Android", however the only Android option at the moment now is labelled "Android Bootloader Interface". No such thing as ADB (or any variations including Android ADB Interface) exists.
3) In TWRP Recovery mode, I see an exclamation mark titled mako but I believe that is irrelevant. I have tried installing the drivers to this just in case but failed. I then tried it again in Bootloader mode and mako is gone and Android Device pops up again with "Android Bootloader Interface"
4) I have tried restarting my PC and repeating the above steps.
Edit:
5) The only time I see an Android Composite ADB Interfaces is when I boot normally to the "Google" screen. However, I cannot move any of my ROMS over into my phone. When I typed "adb devices" it shows a bunch of characters with offline beside it. I do not have any options to reinstall any drivers for this.
From my understanding,I should be able to access the Android Composite ADB Interface while in recovery mode, which should let me transfer my ROMs over... but the issue is I cannot access Android Composite ADB Interface while in recovery mode.
Also, is there any reason why I shouldn't use the official JB 4.3 img as the ROM I want to install on my phone?