A guy wants to change his Nexus 4 for my actual phone, but here is the problem:
Seems like in the middle of an update to 4.4 the phone turned off suddenly
*The phone don´t charge but the battery icon shows up
*If you connect it to the charger you can enter to the recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*If you connects it to the PC you can see that it connects to "google nexus 4 bootloader image"
So, is the problem reversible? I dont want to change my phone for another with no possible repair, the guy thinks the battery is the problem
What do you think guy? Do I accept the change or is too risky?
Thanks and sorry for my english.
If the phone gets recognized on your computer while in the boot loader (the menu you see on your picture posted) you can just flash the official Google factory image. This should make the phone running again.
It seems during the 4.4 update something went wrong seeing the phones still on the .27 baseband and old version of the boot loader.
Please search the forums to on how to flash factory images using fastboot mode. There are plenty of easy manuals here.
PS: do not post the phones serial number (like on your picture). Bad people can do bad stuff
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
If the phone gets recognized on your computer while in the boot loader (the menu you see on your picture posted) you can just flash the official Google factory image. This should make the phone running again.
It seems during the 4.4 update something went wrong seeing the phones still on the .27 baseband and old version of the boot loader.
Please search the forums to on how to flash factory images using fastboot mode. There are plenty of easy manuals here.
PS: do not post the phones serial number (like on your picture). Bad people can do bad stuff
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I didnt know about the serial number, I will delete the pic, but I dont know what people can do with it (if you explain to me)
So, if is safe to restore the phone I should make the change righ? what do you think? Thanks for your help!
Well, if the phone doesn't work at the moment why don't you try to make it work before you decide to trade?
I'm not entirely sure but I think the serial number is important for warranty claims and such. But generally you shouldn't let anyone know your phones serial or imei number, there's no legal/harmless reason anyone needs to know.
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
Well, if the phone doesn't work at the moment why don't you try to make it work before you decide to trade?
I'm not entirely sure but I think the serial number is important for warranty claims and such. But generally you shouldn't let anyone know your phones serial or imei number, there's no legal/harmless reason anyone needs to know.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
The problem is that he just want to change, he is not going to give it to me for try, for that reason I was thinking if I should do the change or not, seems like if you plug the phone to the power you can enter to the recovery like you see in the pic, but im not still sure, if Im sure about fix the phone I will do the change, but I have no way to know it :/
Can I do something just from the recovery for know if the phone have a solution? (without a pc)
Well, why wouldn't he let you try to fix it first. No way to tell if it can definetly be fixed if you can't even try.
Sent from my Nexus 4 using XDA Free mobile app
Well, I'll try to do something, hope I can fix it, I have a few hours to decide if I do the change.
Thanks buddy, I'll tell you later about my decision!.
Finally I saw the phone in person; if you plug it to the power it just blink the red led, you can access to the boot loader, and if you try to start the system the phone just show the google splash and then just turn off, I wasn't really sure about the change so I finally said no at least for now.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Motorola Defy XT: So what does it mean when this is the only screen your rooted Defy XT can make??? Once i turn it on this the first and only thing that appears on the screen but after a few min. my phone starts being a phone and everything, well at least making all the sounds it used to and receiving messages still, but the screen is kaput. Is my phone Bricked for good? or is there anything I can do? Please someone help!!! :crying:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks for the response!
I've actually only just rooted my phone. I haven't put any rom on it. It is still running the factory gb on it. Only rooted it so that I could run a screen shot app on it, and was probably eventually going to rom it once I became a little more knowledgeable about doing so. But everything was working fine with the phone after rooting it, for about 2 weeks even, but yesterday I just pulled out my pocket after coming out of the grocery store, clicked it to unlock it and there was that screen. Tried everything to get rid of it, took the battery out, plugged it in the wall, my computer. Nothing. Weird thing is though, after 5 min of being on, it will continue being the phone that it is, making all its regular sounds and receiving messages and notifications, just with that pixelated screen, which leads me to believe that it might be a hardware/bios problem, or if phones even have bios. This is my first smart phone so I'm just really starting to get to know it. Again, appreciate all help given! Just bummed this phone I've had for a month has already crashed on me.
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Also forgot to mention I tried a factory reset by memory but with no visual it's hard to see if I'm even doing anything.
Search for your stock from and flash it
You can also use the custom from like miui v5 for defy/defy+ http://forum.xda-developers.com/showthread.php?t=2232947
Do you have a cwm recovery? Or you have to use the fastboot method
Sent from my A11 using xda app-developers app
Well, I got my N4 3 days ago, but I recalled its a 16GB version, but now when I look back I only had 8gb?
Is there any way to identify which version am I in?
Or is there any chances that flashing stock recovery bootloader and system etc once using fastboot messed those up?
Because I'm using 4.3 this morning and I reverted earlier today.
Well, help please and thank you.
KiD3991 said:
Well, I got my N4 3 days ago, but I recalled its a 16GB version, but now when I look back I only had 8gb?
Is there any way to identify which version am I in?
Or is there any chances that flashing stock recovery bootloader and system etc once using fastboot messed those up?
Because I'm using 4.3 this morning and I reverted earlier today.
Well, help please and thank you.
Click to expand...
Click to collapse
The best way is check whats written on the box.
check in system>storage.
Box never really wrote anything.
There's only 5.6GB user available space.
Check the boot loader info I think it tells you which one you have. Also there's a bug when flashing stock images the 16gb shows as 8gb. A guide in Q&A has the fix
Sent from my Nexus 4 using xda app-developers app
KiD3991 said:
Box never really wrote anything.
There's only 5.6GB user available space.
Click to expand...
Click to collapse
You've got a 8gb nexus.
Sent from my Nexus 4 using xda premium
KiD3991 said:
Well, I got my N4 3 days ago, but I recalled its a 16GB version, but now when I look back I only had 8gb?
Is there any way to identify which version am I in?
Or is there any chances that flashing stock recovery bootloader and system etc once using fastboot messed those up?
Because I'm using 4.3 this morning and I reverted earlier today.
Well, help please and thank you.
Click to expand...
Click to collapse
If you are sure you bought a 16gb model this might be helpful:
http://forum.xda-developers.com/showthread.php?t=2033692
And my N4 box show which kind of storage i bought.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you boot to the bootloader it will say what version you have. If the bootloader say 16GB yet you only have 5.xGB free you probably need to do a full factory reset to get it to see all the storage. If the bootloader says 8GB then you're good as you are
The bootloader said I'm a mako 16gb alright.
Now on to , how to fix it. Will try what mini androidian said
That how-to he linked worked for me so it should work for you too.
Sent from my Nexus 4 using xda app-developers app
KiD3991 said:
The bootloader said I'm a mako 16gb alright.
Now on to , how to fix it. Will try what mini androidian said
Click to expand...
Click to collapse
WARNING: BACKUP DATA ALWAY the STEP 1
If you have custom recovery like CWM or TWRP just boot into it and wipe data and factory reset and reboot your phone.
If you have stock recovery just boot to recovery mode you will see an android buddy with a red mark on it just press the volume up + power button same time after while it will show up a list of option. Wipe Cache and factory reset then reboot your phone it should show up 12.9GB total free space on your phone now.
Thanks for the advice, I fixed it already.
Using the long method of clean wipes and reflashing everything, all I found is because I was once in 4.3 the radio is wrong and that might be it . ( although I do not see how it will affect)
In fact I'm always flashing rom to the fact that I don't have anything to lose.
I've been digging around online and can't find anything that helps me in my case.
Here's my stupidity: I flashed a kernel that was not intended for my phone (meant for Note 2). Reboot and dead screen. Can't get into download mode, recovery, nothing. Removed battery. Didn't help. Plugged into computer. Doesn't pick up anything connected. Odin doesn't see it. Tried RIFF. Can't get it to install the drivers it's supposed to. I saw something about jig dongles that can force it into download mode but I don't know about that.
What really stinks is I had just compiled SheepShaver for android and it took a few hours of work and I really don't want to do that all over again. Also pictures of my father who's just passed away are on there.
Am I screwed? Is there any way at all to get the proper kernel flashed back on this thing without a wipe? If not is there any way I can fix this phone? I have a semi-recent backup (about a month old) on my SD card. I have both Titanium Backup and a full nandroid backup on the SD.
Someone please come to my rescue. I've logged countless hours on this phone and I love it. All this because I couldn't get SELinux to go permissive...
You already know the answer. If you flashed a kernel not for your device and with the symptoms you have, your hard bricked. Jtag is the answer.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You already know the answer. If you flashed a kernel not for your device and with the symptoms you have, your hard bricked. Jtag is the answer.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Do you know if these guys are the real deal? http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair
I don't have the equipment to jtag it myself. Also just to be perfectly clear; An incorrect kernel cannot be fixed with a download mode jig correct?
mascondante said:
Do you know if these guys are the real deal? http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair
I don't have the equipment to jtag it myself. Also just to be perfectly clear; An incorrect kernel cannot be fixed with a download mode jig correct?
Click to expand...
Click to collapse
mobiletechvideos.com have gotten high reviews on xda. They're the only ones I'd use.
Edit, I'm not sure they're the same as your link
Edit, edit it looks like they're the same guys
Edit, edit edit I don't know about the jig. It could get you into download mode.
Sent from my Nexus 5 using XDA Free mobile app
mascondante said:
I've been digging around online and can't find anything that helps me in my case.
Here's my stupidity: I flashed a kernel that was not intended for my phone (meant for Note 2). Reboot and dead screen. Can't get into download mode, recovery, nothing. Removed battery. Didn't help. Plugged into computer. Doesn't pick up anything connected. Odin doesn't see it. Tried RIFF. Can't get it to install the drivers it's supposed to. I saw something about jig dongles that can force it into download mode but I don't know about that.
What really stinks is I had just compiled SheepShaver for android and it took a few hours of work and I really don't want to do that all over again. Also pictures of my father who's just passed away are on there.
Am I screwed? Is there any way at all to get the proper kernel flashed back on this thing without a wipe? If not is there any way I can fix this phone? I have a semi-recent backup (about a month old) on my SD card. I have both Titanium Backup and a full nandroid backup on the SD.
Someone please come to my rescue. I've logged countless hours on this phone and I love it. All this because I couldn't get SELinux to go permissive...
Click to expand...
Click to collapse
Install drivers riffbox and use this program, revive your galaxy
https://mega.co.nz/#!LVZSHbSb!jX5wqKImIiT3C_rKXcQvZDlCzH0jJbLe0V8h5JpZmcE
djdedonrg said:
Install drivers riffbox and use this program, revive your galaxy
https://mega.co.nz/#!LVZSHbSb!jX5wqKImIiT3C_rKXcQvZDlCzH0jJbLe0V8h5JpZmcE
Click to expand...
Click to collapse
Thank you. I'm trying. I installed those drivers. Trying to find the forum that explains how to use that tool. I saw that thread but it didn't have the download link anymore for the tool.
Update:
Huston I believe we have a problem:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried installing manually and I get an error about the file's hash doesn't match the cert.
dead s4
mascondante said:
Thank you. I'm trying. I installed those drivers. Trying to find the forum that explains how to use that tool. I saw that thread but it didn't have the download link anymore for the tool.
Update:
Huston I believe we have a problem:
View attachment 2917703View attachment 2917704
I tried installing manually and I get an error about the file's hash doesn't match the cert.
Click to expand...
Click to collapse
which program is that? link is dead.does someone has it?
emplokeas said:
which program is that? link is dead.does someone has it?
Click to expand...
Click to collapse
I think you will need the actual riffbox device. I've long since given up on trying to interface over USB. Riffbox talks directly to the memory chip. Need to be comfortable with soldering. But I do happen to have a link to the latest release of their software. http://www.unlockforum.com/showthread.php/riff-jtag-manager-v1-72-more-new-models-32724.html?
Thats the forum they use. The official site is riffbox.org
Sorry I don't know much else to tell you. If it won't boot it won't listen for a connection on USB. Some devices have a failsafe that activates a sort of programming mode over USB but the Galaxy S4 isn't one of those devices afaik.
Whenever I try to update 4.2.2 to a newer version via about -> phone, I get bootloop at Google logo. I've already tried to follow "official" guide for rooting but flashing any ROM in CWM newer than 4.2.2 resulted in the same error. I've been desperately looking for solutions for a while and finally came across this blog http://fixandoridproblems.blogspot.co.il/ . I actually managed to get working 4.3 with those steps, but again, as soon as I update it, I get bootloop.
In addition I got weird error while flashing ParanoidAdroid + GAppps, so that obviously didn't help as well. Of course I always wipe data, cache and dalvik cache before flashing anything whatsoever:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I really don't know what else to do, so some help would be greatly appreciated. Thanks in advance.
this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
hp420 said:
this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Flash the factory image from developers.google.com for Nexus4 4.4 then reflash the latest versions of custom recovery and SuperSU
I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.
krneki10 said:
I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.
Click to expand...
Click to collapse
Dude, we've told you repeatedly....FLASH A FACTORY IMAGE WITH FASTBOOT! STOP USING RECOVERY, BECAUSE THAT IS YOUR PROBLEM!!
Read the guide on how to flash with fastboot.
Jd is right, there are devices out there that after a certain amount of time will refuse to boot any OS above 4.2.2, regardless of how the OS is flashed to the device. No idea why this happens, and the only solution is to get another device.
Sent from my Nexus 4 using XDA Free mobile app
I have the exact same problem on my nexus 4, have you found a fix?
I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
Take a look: http://forum.xda-developers.com/nexus-4/help/help-please-bootloop-4-4-4-imei-t2882868
I'm tired of trying different solutions whit the same result, its exhausting
conquesoextra said:
I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
I'm tired of trying different solutions whit the same result, its exhausting
Click to expand...
Click to collapse
I think this has happened to a few people recently. It happened to me too. For now I have ogt 4.2.2 running, I managed to fix the baseband and IMEI but if i update to a new version it gets broken again.
This is what I did to fix IMEI, hope it works for you
http://forum.xda-developers.com/nexus-4/help/fix-nexus-4-bad-imei-t2882694
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a Nexus 4 in front of me with a diagonal crack from top left to bottom right corners of the screen.
The touch screen only responds on the upper half of the phone.
I have been tasked with getting the images, videos, music etc. from this phone, however as I am unable to unlock the phone I am finding it pretty difficult!
Is there any way to get the data from the phone using either software or hardware hacks?
I know there are a lot of very knowledgeable people on this forum, any information is appreciated, even if I have to open up the phone and start cutting wires!
Thank you,
- Pano
Yes there is quite a single way to do it using ADB on your computer. Do you have that set up?
Sent from my Nexus 4 using XDA Free mobile app
fredcorp6 said:
using ADB
Click to expand...
Click to collapse
I've not got that set up no, are you talking about This?
OK I installed ADB and Fastboot.
I downloaded the custom Nexus 4 recovery from Clockwork Mod.
Booted the phone into Fastboot mode
Found the phone with ADB, tried to run the recover image... the phones LOCK STATE is LOCKED
How do I get past this!?
- Pano
EDIT:
It seems your bootloader is locked. NRT will unlock it but it will wipe your data. And a locked bootloader won't allow ADB (correct me if i'm wrong)
Try doing a factory reset through Recovery, it should get rid of the lock screen and allow you to transfer stuff through USB. I never tried to so i'm not sure will it work
Mashed_Potatoes said:
Try doing a factory reset through Recovery
Click to expand...
Click to collapse
Sure this won't wipe any data :fingers-crossed:
I'll have a look into it, thanks
- Pano
Panomosh said:
Sure this won't wipe any data :fingers-crossed:
I'll have a look into it, thanks
- Pano
Click to expand...
Click to collapse
##
Hi.
Is the device still under guarantee?
If not, you maybe can open the device and get the storage out of it, if there's no other way. First try it with this program, if you give up and there's no other way, (sorry to say this) you must do that.
Or try this:
Connect your phone to the charger
Reboot it
And start in safe mode (somehow, if you're able to do.)
...or replace the screen!
I'm so sorry for you, that something like that happened.
I hope you to manage to rescue your data somehow.
I also know the bitter feeling of data loss ;(
I hope this helped.
OK just to keep all updated and in case anyone ever uses this post in the future to help them...
I have tried everything, nothing worked as it either involved use of the touch screen at some point, or required me to have previously turned USB DEBUGGING on... I have come up with a new solution :
Using the ADB I will unlock the phone using the command
Code:
fastboot oem unlock
This will WIPE all the data from the phone, however it will allow me to finally install a custom recovery mod.
I am then going to find a way to connect the phone to the computer, clone the internal memory to a virtual hard drive and then use some recovery software to get back all the data that was "erased" when I unlocked the oem
Hopefully :fingers-crossed:....
I'll keep the thread updated
- Pano
▲Important Information before Continueing!
Panomosh said:
OK just to keep all updated and in case anyone ever uses this post in the future to help them...
I have tried everything, nothing worked as it either involved use of the touch screen at some point, or required me to have previously turned USB DEBUGGING on... I have come up with a new solution :
Using the ADB I will unlock the phone using the command
Code:
fastboot oem unlock
This will WIPE all the data from the phone, however it will allow me to finally install a custom recovery mod.
I am then going to find a way to connect the phone to the computer, clone the internal memory to a virtual hard drive and then use some recovery software to get back all the data that was "erased" when I unlocked the oem
Hopefully :fingers-crossed:....
I'll keep the thread updated
- Pano
Click to expand...
Click to collapse
This will only work, if the Computer has FULL ACCESS to the file system.
The best Data-Recovery Program is IsoBuster by Peter van Hoove.
...and also, it's not just normal deleting but WIPING, so recovery chance is very low.
...Nexus 4 ALWAYS makes god-damn' problems: RedLight of Death, No MicroSD, Data Loss because of Google's Locked Bootloader.
My Advice The Next time you buy a Device with Android - Unlock the bootloader to avoid further problems.
I hope you to fix all problems. All the best / Have a nice day