[Q] Help! Spontaneously Bricked My Stock Nexus 4 - Nexus 4 Q&A, Help & Troubleshooting

Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.

Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.

I don't think the button is stuck.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
Click to expand...
Click to collapse

Rusty! said:
Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.
Click to expand...
Click to collapse
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.

Alex_Dreyk said:
I don't think the button is stuck.
Click to expand...
Click to collapse
are u able to get to the bootloader and recovery

One3OneKing said:
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.
Click to expand...
Click to collapse
I picked an instrucktion form the link below.
As you have already wiped it do as in instruction

faddyie said:
are u able to get to the bootloader and recovery
Click to expand...
Click to collapse
yes, I can get to recovery. can i get to the bootloader?how would i get there, no clue. lol

Bootloader = fastboot
Try the factory image flash.

Rusty! said:
Bootloader = fastboot
Try the factory image flash.
Click to expand...
Click to collapse
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.

One3OneKing said:
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.
Click to expand...
Click to collapse
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed

faddyie said:
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed
Click to expand...
Click to collapse
No luck. This is crazy, I literally don't know what happened...:crying:

Have u downloaded the sender image file as described in previous posts
Sent from my Nexus 4

One3OneKing said:
Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.
Click to expand...
Click to collapse
Being that you haven't unlocked or rooted the phone its most likely a hardware problem. If you bought it from Google RMA
From my BLACKED OUT N4

Before RMA'ing try the factory image. You don't need instructions, you just run a .bat file while in fastboot. What have you git to lose?

if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.

simms22 said:
if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.
Click to expand...
Click to collapse
You can't wipe /system from stock recovery, so he didn't do that.

EvoXOhio said:
You can't wipe /system from stock recovery, so he didn't do that.
Click to expand...
Click to collapse
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode
Click to expand...
Click to collapse

simms22 said:
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
Click to expand...
Click to collapse
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.

EvoXOhio said:
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.
Click to expand...
Click to collapse
yea, if had my data partition get corrupted too, wouldnt finish booting. flashing the stock img fixed it quick. but it was my own fault.. bennchmarking at 1890mhz with fsync turned off

I ended up just taking advantage of my warranty and I'll get a new one. Thanks to everyone for the suggestions and tips. I'm still trying to figure out why simply turning off the phone to restart it caused this to happen. It makes no sense.

Related

[Q] Semi-Brick?

Okay, today I was about to flash a new rom so I attempted to wipe, but I got an error that the phone could not mount the cache (and later couldn't mount data). It says "E:Can't mount CACHE:recovery/command" on the next line "E:Can't mount CACHE:recovery/log" and the next "E:Can't open CACHE:recovery/log". So I have tried reflashing recovery to fix it and it did not work. I cannot flash any rom without an error or restore my nandroid backups. I am in the process of trying to restore the nandroid backups throught fastboot. Can anyone give me any help on this?
SOLUTION: blancoisgod recommends formatting the cache partition to fix this problem
Did you pull the battery and retry?
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
toby4059 said:
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
Click to expand...
Click to collapse
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
No man dont turn it into tmobile. Now everyone is gonna ride you because you broke it and your going to return it because of what you have done,not the manufacturer.
Go ahead and turn it in, but please read around a bit before you do this again.
CBConsultation said:
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
Click to expand...
Click to collapse
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
toby4059 said:
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
Click to expand...
Click to collapse
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
CBConsultation said:
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
Click to expand...
Click to collapse
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
toby4059 said:
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
Click to expand...
Click to collapse
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
CBConsultation said:
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
Click to expand...
Click to collapse
Okay I will give that a try thanks.
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
blancoisgod said:
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
Click to expand...
Click to collapse
Did you do that and did it fix? I did that through adb and thats when it stopped booting, although I think the boot issue is unrelated to my current problem.
i did it via clockwork
Alright, I will try this if I can ever get my phone started again.

[Q] Help! Nexus 4 stuck in bootloop after 4.4 update.

Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically

[Q] lollipop upgrade - stuck on boot screen

I have an encrypted n4 that I upgraded to lollipop.
Eveything went well but i cant get past the boot screen.
The dots just keep spinning.
I dont want to do factory reset. Have too much data that I dont want to lose.
Has anyone had any luck with resolving this issue other than doing a factory reset?
The first boot could take up to 6-8 minutes... else try to clear the cache
I've let it run for 8 hours and still stuck on boot screen.
Even rebooted and still the same.
How do I clear cache?
On boot press and hold the volume rocker to get into the bootloader. Then use the volume rocker and power button to select recovery, and wipe the cache with the stock recovery using the volume rocker and power button also. There should be video tutorials on YouTube also
NotBillable said:
I have an encrypted n4 that I upgraded to lollipop.
Eveything went well but i cant get past the boot screen.
The dots just keep spinning.
I dont want to do factory reset. Have too much data that I dont want to lose.
Has anyone had any luck with resolving this issue other than doing a factory reset?
Click to expand...
Click to collapse
NotBillable, were you able to solve this issue? I'm having the exact same problem, stuck on the spinning dots after upgrading to lollipop. I cleared the cache, it's been a few hours Anyone else have any other ideas (besides a factory reset)?
gouhst said:
NotBillable, were you able to solve this issue? I'm having the exact same problem, stuck on the spinning dots after upgrading to lollipop. I cleared the cache, it's been a few hours Anyone else have any other ideas (besides a factory reset)?
Click to expand...
Click to collapse
It should only take 10 minutes or so. You wiped /cache and it still did not work? A Factory Reset will probably fix your issue. Hope you made a Nandroid
I'm having the same problem but when I fastboot and try for recovery, I get a downed Android. Thoughts?
cnatalie said:
I'm having the same problem but when I fastboot and try for recovery, I get a downed Android. Thoughts?
Click to expand...
Click to collapse
I tried everything and nothing works except Android 4.4.4... I relocked bootloader, formatted everything, even erased all partitions, flashed via Factory Image, via OTA zip, via flashable zip... It used to work the first time I flashed Lollipop but the second time I ended up with the spinning dots for hours...
Maybe we should make a sticky thread for everyone having the same problem.
Flying f...... dosts
Hello guys,
I have the same problem. After I updated my Nexus 4 my system cannot load. It stucks only on boot screen with flying dots. I dont want to do wipe/erase data. What is wrong please? I tried wipe cashe, but nothing happend with this bug. I have so a lot of dirty words on this s....
ariesgodofwar said:
It should only take 10 minutes or so. You wiped /cache and it still did not work? A Factory Reset will probably fix your issue. Hope you made a Nandroid
Click to expand...
Click to collapse
yep, did wipe cache and it did not work. Had to factory reset. Didn't lose anything too important (e.g. photos and contacts backed up in the cloud), lesson learned though: back stuff up, esp. before before touching and upgrading the OS. Also used this as a chance to flash cyanogenmod
Solved it without a format! I had the same issue with my Nexus 5. I manually sideloaded the OTA zip via adb in Recovery mode and it rebooted ok. Hopefully that helps you guys too.
francobanman said:
Solved it without a format! I had the same issue with my Nexus 5. I manually sideloaded the OTA zip via adb in Recovery mode and it rebooted ok. Hopefully that helps you guys too.
Click to expand...
Click to collapse
Nice! Did you already have debug mode enabled to be able to use adb? Or am I missing something here (I'm a noob )
gouhst said:
Nice! Did you already have debug mode enabled to be able to use adb? Or am I missing something here (I'm a noob )
Click to expand...
Click to collapse
No, all you need to do is connect the phone to the computer, get into Recovery at startup, select to install a zip file. At this pount you need to run adb sideload from command and it should take care of itself. You have to rename the file to update.zip. For this to work you do need the right drivers. Let me know if you need further help.
Stucked on boot screen
If anyone helps.
I tried to install directly the 5.01 update from 4.4.2 on my Nexus 7 and was stucked on boot screen.
After several attempts I installed lollypop 5.0 and worked fine.
I'll try to install now the update from 5.0 and will tell you later if that works.
Cheers

No Root after factory reset

Root just disappeared.
This is not a huge problem but when I go to TWRP to reinstall SuperSU, I can't get to the files so I can't install SuperSU.
I have now a MegaPixel ROM with EX kernel and I want to go back to stock. With no root, kernel and recovery... Just don't know how to.
Step by step here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page567
HeroPlane said:
Root just disappeared.
This is not a huge problem but when I go to TWRP to reinstall SuperSU, I can't get to the files so I can't install SuperSU.
I have now a MegaPixel ROM with EX kernel and I want to go back to stock. With no root, kernel and recovery... Just don't know how to.
Click to expand...
Click to collapse
Follow the guidelines on this page and download the factory image from Google server to return 100% stock.
https://developers.google.com/android/images
RoyJ said:
Step by step here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page567
Click to expand...
Click to collapse
therock3181 said:
Follow the guidelines on this page and download the factory image from Google server to return 100% stock.
https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried to reinstall SuperSU but now its stuck on boot animation. How can I fix this?
I don't think you can do a factory reset if you are on a custom Rom. Power down your phone by holding down the power button until the phone shuts down. Go into bootloader mode by pressing power and volume down buttons at the same time. Flash complete factory image from Google site using flash-all.bat command. If you don't know how to do that follow the XDA/Heisenberg guide only to the point where it shows you how to flash. Do not flash all the pieces individually like in the guide. Just use flash-all.bat command like Google suggests.
HeroPlane said:
I tried to reinstall SuperSU but now its stuck on boot animation. How can I fix this?
Click to expand...
Click to collapse
Use the link I posted above. Read it and follow the return to stock section. Like I mentioned earlier, that's a step by step guide to all things 6P. How to root, how to return to stock and everything in between. It has (or at least links you to) all the tools you need. It's a lot more thorough than I am, quite frankly. Just do your best to follow the return to stock section of the guide and if you run into any issues quote me again and let me know where you're stuck and I'll see if I can help. But you're asking for a step by step on how to recover and I've already provided you with a link with those exact steps. Good luck. Specifically steps 10 or 11 depending on if you want to keep your data intact.
RoyJ said:
Use the link I posted above. Read it and follow the return to stock section. Like I mentioned earlier, that's a step by step guide to all things 6P. How to root, how to return to stock and everything in between. It has (or at least links you to) all the tools you need. It's a lot more thorough than I am, quite frankly. Just do your best to follow the return to stock section of the guide and if you run into any issues quote me again and let me know where you're stuck and I'll see if I can help. But you're asking for a step by step on how to recover and I've already provided you with a link with those exact steps. Good luck. Specifically steps 10 or 11 depending on if you want to keep your data intact.
Click to expand...
Click to collapse
I flashed back to stock like the guide told me. Now its bootlooping with the normal Nexus animation. It means that now I have stock ROM but still bootloop...
HeroPlane said:
I flashed back to stock like the guide told me. Now its bootlooping with the normal Nexus animation. It means that now I have stock ROM but still bootloop...
Click to expand...
Click to collapse
What were the exact steps you took? Also, how long has it been boot looping? First boot on a factory image flash can take a while. I've waited like 10 full minutes before boot.
RoyJ said:
What were the exact steps you took? Also, how long has it been boot looping? First boot on a factory image flash can take a while. I've waited like 10 full minutes before boot.
Click to expand...
Click to collapse
I did all the steps in part 10 with angler 7.1.2
It was bootlooping for 5 minute or so. I turned the phone off (While it was bootlooping) and now when I try to boot I get a "No Command" with a opened Android screen. What should I do now?
Maybe I can still flash TWRP and do stuff there?
HeroPlane said:
I did all the steps in part 10 with angler 7.1.2
It was bootlooping for 5 minute or so. I turned the phone off (While it was bootlooping) and now when I try to boot I get a "No Command" with a opened Android screen. What should I do now?
Maybe I can still flash TWRP and do stuff there?
Click to expand...
Click to collapse
The no command screen with an Android on its back is stock recovery. When you see that, hold volume up and while holding volume up, press the power button. That'll get you inside stock recovery. From there you can factory reset. This will likely wipe your internal storage. I'm not exactly sure on that, but assume it does. If that's not an issue, do it and try booting again, but wait longer this time. Leave in on the charger and wait 10 minutes or so. If it still won't boot, try again with 7.1.1 factory images. Also if you're using the flash all .bat file try manually flashing each partition using fastboot.
Edit: If you didn't already, don't lock the bootloader. You won't be able to use fastboot or flash TWRP (if that's what you want to do) with it locked.
RoyJ said:
The no command screen with an Android on its back is stock recovery. When you see that, hold volume up and while holding volume up, press the power button. That'll get you inside stock recovery. From there you can factory reset. This will likely wipe your internal storage. I'm not exactly sure on that, but assume it does. If that's not an issue, do it and try booting again, but wait longer this time. Leave in on the charger and wait 10 minutes or so. If it still won't boot, try again with 7.1.1 factory images. Also if you're using the flash all .bat file try manually flashing each partition using fastboot.
Edit: If you didn't already, don't lock the bootloader. You won't be able to use fastboot or flash TWRP (if that's what you want to do) with it locked.
Click to expand...
Click to collapse
Can't get to the recovery. Forgot to mention that the "No command" screen is flashing. Like, I can see it for less that a second, it turns black, and comes back again for less than a second. Is it looping too?
double
HeroPlane said:
Can't get to the recovery. Forgot to mention that the "No command" screen is flashing. Like, I can see it for less that a second, it turns black, and comes back again for less than a second. Is it looping too?
Click to expand...
Click to collapse
Sounds like it. That's not good, it sounds​ like a real issue here. How did this end up happening in the first place? You factory reset from TWRP and all this happened? That should have not made you boot loop. You should have been fine and booted and had to sign in again, etc.
Did you lock the bootloader?
RoyJ said:
Sounds like it. That's not good, it sounds​ like a real issue here. How did this end up happening in the first place? You factory reset from TWRP and all this happened? That should have not made you boot loop. You should have been fine and booted and had to sign in again, etc.
Did you lock the bootloader?
Click to expand...
Click to collapse
Didn't lock bootloader
I did the factory reset from system.
I hope it's not a big issue cause I just paid 150$ to fix the screen. I just wanted to give it to my mom fresh (with no root, custom ROM etc...)
HeroPlane said:
Didn't lock bootloader
I did the factory reset from system.
I hope it's not a big issue cause I just paid 150$ to fix the screen. I just wanted to give it to my mom fresh (with no root, custom ROM etc...)
Click to expand...
Click to collapse
Yeah if you're not on stock, don't factory reset from the system. Use TWRP. Try to fastboot flash TWRP back on the phone and see if you can boot to that.
RoyJ said:
Yeah if you're not on stock, don't factory reset from the system. Use TWRP. Try to fastboot flash TWRP back on the phone and see if you can boot to that.
Click to expand...
Click to collapse
TWRP works! OK that's a good sign (I think so...)
I wiped EVERYTHING (Dalvik/ART cache, cache, system, Data and internal storage)
I will probably try to flash stock now.
HeroPlane said:
TWRP works! OK that's a good sign (I think so...)
I wiped EVERYTHING (Dalvik/ART cache, cache, system, Data and internal storage)
I will probably try to flash stock now.
Click to expand...
Click to collapse
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
RoyJ said:
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
Click to expand...
Click to collapse
I think I know why 7.1.2 didn't boot
I have a EX kernel updated to march security. I should download a stock with march security or lower.
RoyJ said:
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
Click to expand...
Click to collapse
Wow man, thank you so much!
The phone is working after I flashed 7.1.1 march
You are the best!!! :victory:
HeroPlane said:
Wow man, thank you so much!
The phone is working after I flashed 7.1.1 march
You are the best!!! :victory:
Click to expand...
Click to collapse
Glad you got it sorted out!

[! HELP NEEDED !] encrypted J510FN only boots to recovery after flashing / wiping

!!! I apologize if this is the wrong thread to ask for help and kindly request that a moderator move it, because I don't know where it's supposed to go and my brain is in panic mode right now, thank you. !!!
So, here goes:
DEVICE INFO: SM-J510FN, TWRP, stock ROM, encrypted data partition
ISSUE: Phone does not boot. Powering it on makes it boot to recovery. Selecting "Reboot to system" from inside the recovery, also boots back to recovery. Cannot mount data partition as it is encrypted (but it doesn't at least ask for PIN or anything, just cannot select /data in mount).
HOW IT HAPPENED:
1. I encrypted the phone while it still wasn't rooted.
2. I flashed TWRP (via Odin) and SuperSU (via TWRP)
3. Phone booted to system normally, everything OK. Root access, all good.
4. Reboot to TWRP, flashed some blacked out Google Apps (Team Blackout .zip files). I got no error message, just "cannot mount data" at some points.
5. I selected "wipe cache and dalvik cache"
6. Reboot to system
Reboot to system doesn't work. It boots back into TWRP!
Now I don't know if the flashing of the .zip apps or if the wiping bricked the phone as I don't have that deep of an understanding of how it works. If you can enlighten me , I'd really appreciate it.
FEAR: That the phone is bricked forever and that I won't be able to format the data partition as I cannot even mount it and TWRP needs it mounted in order to wipe it (as far as I know). In short, phone ruined forever because of my stupidity.
HOPE: That someone will tell me a way to re-flash the stock firmware or any ROM so that I get the phone to boot up normally.
I really really need help ASAP because this phone does not even belong to me. My employer gave it to me as a gift, provided I use it for work. That's the reason it's encrypted, he wanted it encrypted in case it gets stolen. Now you're probably thinking "why would you root a company phone??" Well it's not a company phone, it is my main phone, my daily driver. It was given to me by my employer, who said I can do whatever I want with it, as long as it remains functional (at work I use it simply for phone calls, WhatsApp, Skype, mail etc)
I assume that I won't sleep much tonight, will try everything to get the phone to boot. But first I'm going to wait for any piece of advice!
Thank you in advance for any feedback...
Can you get into download mode?
If so, you should flash your stock firmware.
Yes if you boot into download mode you can flash stock rom and all will be good
capsLock1337 said:
Can you get into download mode?
If so, you should flash your stock firmware.
Click to expand...
Click to collapse
pando504 said:
Yes if you boot into download mode you can flash stock rom and all will be good
Click to expand...
Click to collapse
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
bi11ie said:
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
Click to expand...
Click to collapse
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
capsLock1337 said:
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
Click to expand...
Click to collapse
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
bi11ie said:
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
Click to expand...
Click to collapse
How did it go?
capsLock1337 said:
How did it go?
Click to expand...
Click to collapse
I'm flashing right now Let's see if it boots...
*fingers crossed*
Case solved
bi11ie said:
I'm flashing right now Let's see if it boots...
*fingers crossed*
Click to expand...
Click to collapse
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
bi11ie said:
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
Click to expand...
Click to collapse
No need to apoligize, we all do stupid mistakes sometimes
Glad that it worked!

Categories

Resources