Root Nexus 4 stuck in bootloader with usb debugging not enabled

[robygraz]

Hello, i did something very wrong...
I've tried to flash Kitkat 4.4 with the custom recovery instead than with adb sideload!
Now i'm stuck with my phone, i can go to bootloader, i can acess twrp custom recovery but i am not able to do anything because i cannot connect it properly to the laptop! My horrible mistake to have usb debugging not enabled!
Is there any way to recover from here?
All my files are still in the internal memory: i can see them but i cant access them as well.
I can connect from fastboot i can see my device id but that's all i can do
I only need to have the adb sideload working?
IF NOT IS THERE ANY WAY TO FLASH A FACTORY IMAGE FROM FASTBOOT WITHOUT ADB?
please please please help...


THANKS A LOT!!!

 

[El Presidente]

Your best bet would probably be to manually flash the factory images from here: https://developers.google.com/android/nexus/images#occamkrt16s

If you can still access the bootloader and fastboot, that should still work.

 

[robygraz]

thanks for your concern and help: i have flashed factory image before but with adb; i don't have any idea how to do from bootloader?
I also wish to know if my files and folder in the internal memory will be still there after i restore the factory image (the bootloader is unlocked).
If not is there any procedure to save them before flashing?
Thanks again for your help!
Cheers
Roberto

 

[bjacks12]

It's super easy to do it from the bootloader with fastboot. The commands are somewhat similar.

Your bootloader being unlocked is good, that means that this can be done without wiping your data.


Download the KRT16S factory image. Extract it from the .tgz into the same folder as FASTBOOT.exe

Boot your phone into fastboot, plug it into your computer.

Now, before you flash, right click on the file 'flash-all.bat'. It's not formatted well, but find the last line that says 'nulfastboot -w update image-occam-krt16s.zip'
Erase the '-w'. The '-w' tells fastboot to wipe the data. Removing it will stop that.

Save the file and run it.

 

[hstroph]

... right click on the file 'flash-all.bat'. It's not formatted well, but find the last line that says 'nulfastboot -w update image-occam-krt16s.zip' ...

It's actually formatted perfectly for the Android OS, which is embedded Linux. Linux and Unix have always used a simple newline character "\n", while Microsoft chose to defy established computer conventions at the time (early '80s) and add an additional carriage return "\n\r" that causes the formatting issue you're observing on an MS desktop.

Attached is an image of how the file appears in its native language in a simple gui text editor.

 

[bjacks12]

It's actually formatted perfectly for the Android OS, which is embedded Linux. Linux and Unix have always used a simple newline character "\n", while Microsoft chose to defy established computer conventions at the time (early '80s) and add an additional carriage return "\n\r" that causes the formatting issue you're observing on an MS desktop.

Attached is an image of how the file appears in its native language in a simple gui text editor.

What I meant is that it's not formatted for ease of viewing/editing.