Database Users

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

Need help, urgent

Hi, I have a D806 G2 and I have a big problem.
After an error modifying my build.prop I was left with a broken phone. It wouldn't boot to the os.
I was rooted and with TWRP so I restarded and tried to revert to the old build.prop (that's the only backup I had) and it didn't work.
I followed the tutorials to go back to stock (I had done it once before to update my phone while rooted, but that time the phone was working fine).
Well, to my surprise, given that I only had recovery or download mode, the process started but failed with an error.
Now, I don't have a System, meaning that my system folder is empty so I really don't have an os in the phone, and all procedures to flash a rom, fail.
I have tried flashtools and everyother tool but nothing, can't put a rom in the phone.
Now I'm kinda desperated because It is too expensive for me to loose the phone (things in Argentina are far too expensive) and when I put it in download mode it clearly says ROOTED so I will have a problem with guaranty.
Please, someone give me a hand!!

MasterTB said:
Hi, I have a D806 G2 and I have a big problem.
After an error modifying my build.prop I was left with a broken phone. It wouldn't boot to the os.
I was rooted and with TWRP so I restarded and tried to revert to the old build.prop (that's the only backup I had) and it didn't work.
I followed the tutorials to go back to stock (I had done it once before to update my phone while rooted, but that time the phone was working fine).
Well, to my surprise, given that I only had recovery or download mode, the process started but failed with an error.
Now, I don't have a System, meaning that my system folder is empty so I really don't have an os in the phone, and all procedures to flash a rom, fail.
I have tried flashtools and everyother tool but nothing, can't put a rom in the phone.
Now I'm kinda desperated because It is too expensive for me to loose the phone (things in Argentina are far too expensive) and when I put it in download mode it clearly says ROOTED so I will have a problem with guaranty.
Please, someone give me a hand!!
Click to expand...
Click to collapse
Can you still get to TWRP (recovery)? Which version of TWRP are you using? Do you still have the zip file of the ROM you're on?
Sent from my LG-D800 using Tapatalk

Jank4AU said:
Can you still get to TWRP (recovery)? Which version of TWRP are you using? Do you still have the zip file of the ROM you're on?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Sorry was too crazy to post most data.
No I don't have a backup of my rom, but I got a backup from another phone and it doesn't work
Gladly I could use a USB OTG to copy Carbon and Gapps to the phone and I could install that so the phone is working now.
The problem is going back to stock because I would need a backup of a D806 rom and I don't have one.
I'm on TWRP 2.6.3.4 and it's working fine now. Thank you very much.,

Very simple and very lucky you still can access download mode. Just using flashtools to flash TOT again then its all go back to original stock.

cccho said:
Very simple and very lucky you still can access download mode. Just using flashtools to flash TOT again then its all go back to original stock.
Click to expand...
Click to collapse
what is TOT? i need this to back stock rom

cccho said:
Very simple and very lucky you still can access download mode. Just using flashtools to flash TOT again then its all go back to original stock.
Click to expand...
Click to collapse
I would if I could, but my IMEI reads 0, hence no luck with LG software.
Luckily I could boot the phone to an AOSP rom (copied via USB OTG to my phone -I still have recovery-)
So, I have an AOSP rom, I can get a backup of a similar rom to my stock rom -from a user in another forum- and I can install that backup (foing it ATM)
BUT, my IMEI is 0 so LG software doesn't fully recognize my rom and drivers don't fully install
HELP??

nicogarcia1229 said:
what is TOT? i need this to back stock rom
Click to expand...
Click to collapse
Read this and do more seach.
http://forum.xda-developers.com/showthread.php?t=2541030

No OS. PLEASE HELP!!

I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.

shaggy9585 said:
I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.
Click to expand...
Click to collapse
we need a story, for starters what did you do/happened before you got into fastboot?

XxZombiePikachu said:
we need a story, for starters what did you do/happened before you got into fastboot?
Click to expand...
Click to collapse
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?

shaggy9585 said:
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?
Click to expand...
Click to collapse
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock

XxZombiePikachu said:
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock
Click to expand...
Click to collapse
is there a way to flash a rom using adb while in twrp or fastboot?

shaggy9585 said:
is there a way to flash a rom using adb while in twrp or fastboot?
Click to expand...
Click to collapse
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)

XxZombiePikachu said:
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)
Click to expand...
Click to collapse
now i just need to figure out whats going on with the touch sensor. idk if its the phone or just twrp

Accidentally wiped OS from phone

I accidentally wiped my OS from my phone when I wasn't paying attention. All recoveries wiped as well. It will not boot past startup screen. Odin v3.07 and 3.09 both display FAIL when I try to flash the stock ROM back. I am using a G900P. Help?

How do you accidentally wipe an OS from a phone?
You're putting the phone in download mode for ODIN right?

*Detection* said:
How do you accidentally wipe an OS from a phone?
You're putting the phone in download mode for ODIN right?
Click to expand...
Click to collapse
Yes. It recognizes my phone as plugged in but keeps displaying a FAIL message when flashing, Also I'm running Android 5.0.

Try this
http://forum.xda-developers.com/spr...in-sm-g900p-oa6-official-restore-rom-t3022826

If you're putting your phone into Download Mode you should be able to flash a custom recovery onto it (such as TWRP - the one I personally use.)
Try flashing that onto your device then flash a ROM through TWRP - You can mount your phone and SD card onto a PC through this, allowing for you to access the devices file system here.
Then, if you really wanted to, you can go through Samsung Kies on your PC and restore back to the original TouchWiz ROM from Samsung. It'll ask you to verify your device and ask you to put it into download mode but not sure if you'd want to go back to stock.
If you need any more help, just ask here and I'll give you a hand.

Exvious said:
If you're putting your phone into Download Mode you should be able to flash a custom recovery onto it (such as TWRP - the one I personally use.)
Try flashing that onto your device then flash a ROM through TWRP - You can mount your phone and SD card onto a PC through this, allowing for you to access the devices file system here.
Then, if you really wanted to, you can go through Samsung Kies on your PC and restore back to the original TouchWiz ROM from Samsung. It'll ask you to verify your device and ask you to put it into download mode but not sure if you'd want to go back to stock.
If you need any more help, just ask here and I'll give you a hand.
Click to expand...
Click to collapse
I'm going to try the Mounting method but I don't exactly understand the process.

limitedsound said:
I'm going to try the Mounting method but I don't exactly understand the process.
Click to expand...
Click to collapse
It's quite basic, you simply just go into TWRP and select what you want to be mounted to the computer from the custom recovery. If you need more help here, just let me know.
- Removed False Content -

Exvious said:
It's quite basic, you simply just go into TWRP and select what you want to be mounted to the computer from the custom recovery. If you need more help here, just let me know.
Also, in download mode I'm not sure if you can access the devices file system through Windows / OS X - Never tried, but I'm assuming it works - Don't quote me on that tho haha.
Click to expand...
Click to collapse
No, that's what ADB is for, but the device needs to be booted for ADB, download mode is just for flashing with ODIN

*Detection* said:
No, that's what ADB is for, but the device needs to be booted for ADB, download mode is just for flashing with ODIN
Click to expand...
Click to collapse
Right - Thanks for the correction.

How exactly do I use ADB to mount?

limitedsound said:
How exactly do I use ADB to mount?
Click to expand...
Click to collapse
If you wiped the OS, you have no reason for adb
Use my link to flash a rom, or use ODIN and a stock rom

*Detection* said:
If you wiped the OS, you have no reason for adb
Use my link to flash a rom, or use ODIN and a stock rom
Click to expand...
Click to collapse
Yeah Detection Odin is still displaying FAIL messages for the ROM you linked me to.

limitedsound said:
Yeah Detection Odin is still displaying FAIL messages for the ROM you linked me to.
Click to expand...
Click to collapse
What exactly did you do to 'accidentally' wipe the OS?

*Detection* said:
What exactly did you do to 'accidentally' wipe the OS?
Click to expand...
Click to collapse
I was wiping something in TWRP and I apparently checked the "System" button.

You still have TWRP working?
Flash a custom ROM

PLEASE HELP!!! Phone stuck in bootloop, will not boot. Will not boot into recovery.

I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Edit: I fixed it. had to manually extract and reflash some files from a very useful restore to stock tool.
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
Thank you for all of the help so quickly.

kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.

kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.

thanks
[email protected] said:
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
Click to expand...
Click to collapse
fixed it thank you!

thanks
benjmiester said:
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
Click to expand...
Click to collapse
fixed it thank you!

kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Great news! You're very welcome. I was in that exact same situation with my old Xperia Z2. It's pretty scary.

kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk

DonKilluminati23 said:
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.

kagarii said:
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
Click to expand...
Click to collapse
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.

jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
It's possible, through tools like this. I don't know too much of the topic.

jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.

Sherrillface said:
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Click to expand...
Click to collapse
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?

jDally987 said:
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
Click to expand...
Click to collapse
Nothing it just vibrates as soon as i hit factory reset then bootloops now it wont even go into recovery just fastboot screen but cant get fastboot to work at all and have all drivers android studio etc. Nothing will work need a new solution

It was hash kernel it corrupted all 64 gigs of storage and music etc. Had to return to stock via auto flash firmware.

Mine is XT1572 device. Since the mentioned tool was not available for this model, I took the chance with XT1575 tool. It did all the steps but the issue has become worse. Now, my device is automatically getting On and OFF in seconds and does not boot beyond the bootloader 'unlocked' warning screen. Please please please help !!!!