[Q] Boot loop after upgrading Nexus 4 to 5.1 - Nexus 4 Q&A, Help & Troubleshooting

I recently got 5.1 update on my nexus 4. But after the update I am experiencing boot loop issue on my phone. This is a stock image and un-rooted phone which is out of warranty.
The phone was stuck in a 'Starting apps' message after the 'optimizing apps' for close to 3 hours. I rebooted the phone and was able to boot into 5.1 once.
I could not get a network and I restarted my phone. Since then, I have never been able to complete the full boot even once.
It either gets stuck in the animation of the 4 balls moving, or the 'optimizing apps' stage or the 'starting apps stage'.
I searched the internet and tried some solutions given by people who were facing a similar issue. But nothing seems to be working for me.
Solutions tried:
1) I rebooted into recovery mode and wiped the cache multiple times.
2) I rebooted into recovery mode and did a factory reset hoping that some apps which was causing issue optimizing/starting would be deleted.
3) I flashed a 5.1 as well as 5.0.1, 4.4.4 image using the NRT in the 'Soft-brick' mode. I faced the same issue with the loop. I can't get a adb connection to work since the developer options is not enabled I believe.
I cannot even find out which app is causing the issue as well since I don't get any logs during the boot. But I thought a factory reset should handle this problem.
I have already lost data since I didnt have a full backup. At this point, I just want to get my nexus back.
Please Help!!!

Ican understand how you must feel It looks like you have done everything. The only suggestion I can make that might help is seek out the SkipSoft Android Tool Kit. It will allow you to restore your nexus so check it out
https://www.google.com/url?sa=t&rct...=z2XaCTV2HIaBSAHTninuig&bvm=bv.91665533,d.b2w
I hope that helps you... I have used it successfully many time.

Thanks for your reply.
Is there any particular option on the toolkit I should be using to restore my Nexus? Or I should just try re-flashing stock firmware using the mentioned tool kit?

rajath575 said:
Thanks for your reply.
Is there any particular option on the toolkit I should be using to restore my Nexus? Or I should just try re-flashing stock firmware using the mentioned tool kit?
Click to expand...
Click to collapse
I would plug your Nexus 4 in via USB port
Select your device type Nexus 4 option 02
Then go to the next step and select the build number that you want to start
---------- Post added at 01:25 PM ---------- Previous post was at 01:23 PM ----------
Blacksmith5 said:
I would plug your Nexus 4 in via USB port
Select your device type Nexus 4 option 02
Then go to the next step and select the build number that you want to start
Click to expand...
Click to collapse
The SkipSoft tool kit will guide you through the whole process
skipsoft.net

Related

[Q] Rooted Nexus 4 refuses to encrypt. Resets itself.

I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Bubblewhip said:
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Click to expand...
Click to collapse
Are you using a custom recovery - TWRP or CWM? You need to be using the stock recovery image to encrypt your phone. The nexus toolkit will allow you to re-flash the stock recovery.
One the stock recovery has been re-flashed, you should be able to encrypt your phone. I had to re-flash stock recovery, reboot the phone, then reflash the stock recovery again.
Once the device has been successfully encrypted using the stock recovery, you can re-flash either the TWRP or CWM as your recovery. TWRP supports reading data from encrypted devices, so it is probably the way to go (not sure if CWM dows now, but it didn't last time I looked).
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
randomvector said:
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
Click to expand...
Click to collapse
I haven't noticed a difference in speed, however technically there will be a little bit of a slowdown.
I'm running stock Android, so I don't know how well it plays with custom ROMs, but you can re-flash a TWRP recovery after encrypting your phone with stock Android on it.
If the custom ROM installation wipes the data partition, it would remove the encryption.
I've tried flashing stock recovery using Nexus 4 Toolkit and recovery is back to stock. However the phone is still just rebooting when I press encrypt device. What am I doing wrong?
For some reason I had to reflash the stock recovery, reboot, then reflash the stock recovery again. No idea why, but it worked for me!
Sent from my Nexus 4 using Tapatalk 2
Booted back into stock recovery device is still rebooting itself after hitting the encrypt button, Encryption did not happen.
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Bubblewhip said:
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Click to expand...
Click to collapse
The android with a warning symbol is the normal symbol of stock recovery.
However, I wonder, if you could solve the problem? My nexus doesn't want to encrypt itself too. Flashed stock recovery already twice and it just keeps rebooting when I start the encryption process.
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
c_m_l said:
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
Click to expand...
Click to collapse
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
JohnnyBBB said:
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
Click to expand...
Click to collapse
Old thread, same issue, HTC One w/ OmniROM (m7att). My Nexus 10 did it as well.
The person saying to reflash stock? DOn't listen to that. Doesn't need to be done. Encrypted all my devices w/ TWRP installed.
Airplane mode DID work, though.
I just had this issue with my N4, too. I read on the Google Product Forum that this was because a process prevents from unmounting the /data partition. ("Nexus 5 is not going through encryption process" - can't post link due to being new)
With that in mind, I rebooted into safe mode and then tried again and it worked on the first try (At least it started the encryption process, it's at 10% now)
I had this problem for a looooong time. Thankfully, I seem to have discovered a solution for those still encountering this issue.
Turn off SuperSU (Settings -> More -> Application manager -> All -> SuperSU -> Turn Off)
Reboot into Safe Mode (How to)
Run encryption (Settings -> More -> Security -> Encrypt Device)
Turn on SuperSU after complete (Settings -> More - > Application manager -> Turned Off -> SuperSU -> Turn On)

[Q] Stuck on Google start screen after installing CM 10.2

Hi All,
I've searched across forum to find also similar cases, but no results so far.
I have a N4 with TWRP and CM (previously running 10.1.2)
Today I decided to install the new 10.2.
Installation went fine but after the restart I've noticed some strange behaviour with some applications (missing from phone, but installed for my play store account)
I've decided to reboot again the phone, and since that time I'm stuck with the black start up Google screen (the one with the lock at the bottom).
Entered recovery mode, I've wiped Dalvik, Cache and System, but no results, rebooting is always stuck on Google screen (I've also left it there for 15+ minutes, no changes)
I've tried to install a previous ROM (zip available on phone storage) but no result even in this case.
Any help or suggestion would be much appreciated, even a link pointing to similar case happened in the past.
Let me know if any further detail may be needed to better understand the situation
Thanks!
mh a wipe/factory reset should be working...
Try pushing a different rom with ADB to your device, then flash it.
Sent from my Nexus 4 with Tapatalk 4
This is usually happening when you don't flash something right. I'd go back, flash it all again with wiping everything and flashing it by the right order and stuff. If it doesn't work, as written above, flash other ROM through ADB or something similar.
Besides, you could always restore your nandroid backup, and if you don't have one, learn from your mistake
Good luck
Sent from my Nexus 4 using xda app-developers app
To be honest, I've already tried to revert back to previous CM and even to the factory image from Google, but it always hang on the google screen.
I've not yet Format/completely wiped the phone, and that's my last option.
Once I'm done with the manual backup I'm doing via adb shell, I will try again to flash a new ROM, and see what happen.
Definitely I'm learning from my mistakes

[Q] Nexus 4 updated to Kit Kat via OTA and got looped on boot

Hi, this is my first post here. I'm new into Android and I've always updated my Nexus 4 when the system prompts me to do it. Today, I got the notification to update from 4.3 to 4.4... I did it and restarted my phone. Then I got (and have been) stuck on the boot sequence after the Google logo. The thing is that I've tried to wipe and restart the phone by Bootloader (I don't know if I lost all of my files) and didn't work out. So now I'm trying with Nexus Root Toolkit but I don't know if that will work. I'm really needing some help, here in Venezuela not so many people have this cellphone and I really don't know how to proceed. I'm upset with Google for these kind of fails, my phone was working 100% good. Please help me! Sorry if my english is not so perfect.
I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!
Same case, nothing works.
I had the same problem, go stuck on a boot loop and then it just said 'no command' or 'error' with an android lying down. Im a noob so i used ncry toolkit to reset it to factory 4.3 and then i upgraded to 4.4 again and all worked fine. Did lose data though, but i had it all backed up.
Do a clean flash of KitKat via fastboot.
Similar Situation
Chidvilas said:
I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!
Click to expand...
Click to collapse
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
NissanskylineN1 said:
Do a clean flash of KitKat via fastboot.
Click to expand...
Click to collapse
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?
http://forum.xda-developers.com/showthread.php?t=2302780
Its actually way easier to set it up on Linux than on windows.
Edit: java jdk6 was giving me issues on install so I used openjdk instead and it works perfect.
Edit: (last one, I promise), I don't know how new you are to Linux but if you are super new, anytime that guide mentions "code" in a box, copy and paste one line at a time into the terminal. Leave out the dollar signs when copying.
AMarted said:
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?
Click to expand...
Click to collapse

[Q] Nexus 4 Bricked / going in bootloop

Hey Guys,
I am facing a very strange issue with my N4. On Friday Night, I kept my phone for charging overnight and it was working as usual. on Saturday morning, I noticed that the phone was unresponsive and was showing a blinking red light. Tried to charge via various means but it was of no use. Finally went to a LG service centre were they could revive the phone but it was stuck in a bootloop. He suggested me that he will downgrade from KK 4.4.2 to JB 4.3 but still the phone was stuck in bootloop.
LG guy said that he doesn't have answer why this is happening. He said change the motherboard that will fix it. That is a very costly option which I cannot take. and he mentioned that there are tools online which will help it work but as an authorized service centre place he can't do it.
So here's what I did after reading several blogs, videos and but got stuck in the same place.
1. Booted in Bootloader mode, flashed stock JB 4.3 using Wugfresh Nexus Toolkit selecting the option Softbrick / Phone in bootloop.- Result : Stuck at Bootloop.
2. Flashed CWM Touch via fastboot, Went to the CWM recovery, Cleared the dalvik cache, Data, User data, Cache, Reflashed a Stock JB 4.3 - Result : Stuck at Bootloop.
3. Flashed KK 4.4.2 , again using the Wugfresh Nexus Toolkit - Result : Stuck at Bootloop.
I tried searching google for bootloops due to motherboard issues just to be clear from my side. The solution what LG guy gave sounded like I have no idea, lets replace the entire thing. Which i am pretty sure is not the correct method.
What my phone can do at this moment is:
1. boot into bootloader.
2. Communicate with the PC using Fastboot.
I know Nexus 4 is a developer phone and easy to recover from brick status due to its intended purpose. Please advise what else can I do to revive my Nexus 4 and let me know in case I haven't done any thing which can restore this thing back to normal.
Thanks and Cheers,
Sid
siddhu2411 said:
Hey Guys,
I am facing a very strange issue with my N4. On Friday Night, I kept my phone for charging overnight and it was working as usual. on Saturday morning, I noticed that the phone was unresponsive and was showing a blinking red light. Tried to charge via various means but it was of no use. Finally went to a LG service centre were they could revive the phone but it was stuck in a bootloop. He suggested me that he will downgrade from KK 4.4.2 to JB 4.3 but still the phone was stuck in bootloop.
LG guy said that he doesn't have answer why this is happening. He said change the motherboard that will fix it. That is a very costly option which I cannot take. and he mentioned that there are tools online which will help it work but as an authorized service centre place he can't do it.
So here's what I did after reading several blogs, videos and but got stuck in the same place.
1. Booted in Bootloader mode, flashed stock JB 4.3 using Wugfresh Nexus Toolkit selecting the option Softbrick / Phone in bootloop.- Result : Stuck at Bootloop.
2. Flashed CWM Touch via fastboot, Went to the CWM recovery, Cleared the dalvik cache, Data, User data, Cache, Reflashed a Stock JB 4.3 - Result : Stuck at Bootloop.
3. Flashed KK 4.4.2 , again using the Wugfresh Nexus Toolkit - Result : Stuck at Bootloop.
I tried searching google for bootloops due to motherboard issues just to be clear from my side. The solution what LG guy gave sounded like I have no idea, lets replace the entire thing. Which i am pretty sure is not the correct method.
What my phone can do at this moment is:
1. boot into bootloader.
2. Communicate with the PC using Fastboot.
I know Nexus 4 is a developer phone and easy to recover from brick status due to its intended purpose. Please advise what else can I do to revive my Nexus 4 and let me know in case I haven't done any thing which can restore this thing back to normal.
Thanks and Cheers,
Sid
Click to expand...
Click to collapse
Try not using a toolkit, and doing it manually instead:
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
abaaaabbbb63 said:
Try not using a toolkit, and doing it manually instead:
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
siddhu2411 said:
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
Click to expand...
Click to collapse
Flash the KitKat factory image. That might solve the mobile signal issue.
The battery one, if not solved my the kitkat image, might be a hardware fault.
abaaaabbbb63 said:
Flash the KitKat factory image. That might solve the mobile signal issue.
The battery one, if not solved my the kitkat image, might be a hardware fault.
Click to expand...
Click to collapse
So chances that the Motherboard is screwed?
siddhu2411 said:
So chances that the Motherboard is screwed?
Click to expand...
Click to collapse
Or the battery itself. If the motherboard was busted, then the phone wouldn't have booted.
siddhu2411 said:
Thank you abaaaabbbb63, I did find that post and performed the steps and now i can boot into android JB 4.2.2
But here's the thing the battery icon is showing an exclamation mark and mentioning that it is not charging. and second it seems that i am not receiving any mobile signal.
Could this mean my battery is faulty and replacing it may allow me to use the mobile signal.
Click to expand...
Click to collapse
Did you get this fixed? Were you able to upgrade beyond 4.2.2?
My Nexus is currently bootlooping if I try and upgrade beyond 4.2.2 - though my battery seems fine. I'm wondering if there's some similar problem though.

Please help! Stuck on boot screen

I left my phone charging overnight as I have done many times with no issue. When I woke up I pressed the home button and the only thing that shows was my wallpaper. Wouldn't show anything else. I then did a battery pull. It now gets stuck at the note 4 powered by android screen. A little history in case it helps. This is an unlocked at&t model that I am using on t-mobile. It's not rooted or anything. A few weeks ago I downloaded the recent 5.0.1 small update. In the past week a notification keeps appearing and disappearing from the menu. It was dm software download or something which would disappear if I clicked it.
So it's stuck on the boot screen today. I booted in to the recovery screen. It starts by saying "installing system update" with the little android. Then it goes to recovery menu. At the bottom it says "dm-verity verification failed". I tried to wipe cache and reboot but it still gets stuck at the boot screen. Another small detail is after turning phone off if I plug it in the charger it stays at the grey lighting screen and does not show any battery percentage.
I don't know what to do. I really need my phone today as I am traveling. I hope someone can please help me. Thank you.
In the case u tried recovery now u should flash ur stock rom.
How do I flash the stock rom? Should I do that before trying a factory wipe/reset? I haven't tried that because I really dont want to erase everything unless I have to.
When u do the flashing everything in your device will be lost. So if u do the flashing then u just need to backup all your data.
---------- Post added at 01:05 PM ---------- Previous post was at 01:02 PM ----------
First u have to download your stock rom
Anyone else have any ideas? I really have no clue how to flash the stock rom. Is there a guide I can follow? Thanks
Just google your device name flashing
morjam401 said:
How do I flash the stock rom? Should I do that before trying a factory wipe/reset? I haven't tried that because I really dont want to erase everything unless I have to.
Click to expand...
Click to collapse
I would suggest you start download stock as already mentioned by previous mentor
Than try to make a factory reset from recovery while stock is downloading. In case factory reset all your apps and settings will be gone but your data stay untouched.
If positive with factory reset no need to flash stock anymore
I just tried doing factory reset/date wipe and it's still getting stuck at the boot screen. I guess I need help now to flash the stock rom. Again I have never done this so I appreciate it if someone has or could find a simple guide for me. I just don't want to download the wrong file and mess phone up even more. It's an at&t model SM-N910A. Thanks again
How long did you wait after wiping? For lollipop its normal after wiping to see nothing but Samsung boot up logo up to 20 minutes
In response to above. It did the date wipe/reset which did it in like 5 seconds. I rebooted and left it on the boot screen for about 3 minutes. I should wait longer then? Another thing I was going through kies to see if anything could help. I ended starting a firmware upgrade. I entered my model # and S/N#. It then asked me to go to recovery and made it to a screen with an android, "downloading do not turn off target". That's loading now and i'll see what happens. I also checked on google and it looks like there is a program called odin that will flash the stock rom. I need to find that program and also find the stock rom file to download?
Yep. Google for Odin, download and extract it on your PC. You'll need to download a stock firmware from Sammobile for your device. It will be as Archiv so extract it. In Odin click on AP and choose extracted file.
Another update. The firmware upgrade through kies went through fine. It booted up like normal afterwards. I didn't know it would happen but I am back to kit kat 4.4.4 as well. I wasn't too thrilled with lollipop so maybe that isn't a bad thing.

Categories

Resources