I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome
YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..
boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here
Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.
Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...
Found a fix, check the forum page
Related
i am in desperate need of help i tried giving my pops a hand with his vibrant since he sees all the stuff i do to my nexus..i flashed the stock firmware from jac and the phone will not boot...well actually i get the tmobile splash...the vibrant splash..and the s animtion..problem is after that i guess the phone just hangs...the screen nvr turns on..i press the capacitive buttons and they light up but nothing on th screen and i cant get it to turn on...now i dont believe its bricked cause i can get into recovery and into download mode..i tried flashing through odin about three times...everything goes through..the phone resets..goes through the boot screens but after that nothing comes up...backtracking for a min...the whole reason i tried to flash the stock jac firmware was because i went into rom manager and tried to partition the sdcard..when i hit partition the phone rebooted and nothing would come up..i am assuming that it reformatted the internal card..needless to say thats when i tried flashing the stock and this is where im stuck at...i would really appreciate some help..and hopefully this will stop anyone else from running into this issue...do not try to partition the sdcard from rom manager..i hope i have described this in enough detail...thanks
looks like someone might owe his daddy a new phone.
Get ready for a spanking.
If my dad were still alive he would probably murder me if I ever bricked his new 200 dollar phone.
Just kidding. I hope you get it working bro. If not, try to exchange it. Say you don't know what happened to it, you turned it off and let it charge overnight and when you woke up to turn it on, this happened. Have tears in your eyes. They'll exchange it for you
MMcCraryNJ said:
Just kidding. I hope you get it working bro. If not, try to exchange it. Say you don't know what happened to it, you turned it off and let it charge overnight and when you woke up to turn it on, this happened. Have tears in your eyes. They'll exchange it for you
Click to expand...
Click to collapse
I agree with this. If you dad goes in, T-mo won't think "This old dude must have hacked it!" They'll exchange it right away and even apologize to him.
Sent from my SGH-T959 using XDA App
have you tried to manually remove the partition and see if it boots? or try to boot without the sdcard?
what I did was flash Eugenes Froyo rom which worked well, then I re-flashed the stock rom. Now it works just like before.
junkdruggler said:
have you tried to manually remove the partition and see if it boots? or try to boot without the sdcard?
Click to expand...
Click to collapse
could u explain to me how to do that..i would appreciate it..cuz i kind of think it has to be a problem with partitions..also another thing i noticed is when the phone reboots and goes into recovery in red letters data wipe says fail..i have also tried both pit files 512 and 513..evrything thing works gets past boot screens but the screen doesnt come on
my nexus 7 is stuck in bootloader with no recovery ive tried the flash back to stock and unroot option on the wugfresh nexus toolkit 1.5.3 and it works all the way til sending system the little - mark still flashes but i left it for like 20m and it still didnt work ive tried multiple times and i clicked cant boot up option, please help
Hold the power button for over 10 seconds and it will reboot its self
Jordanooo said:
Hold the power button for over 10 seconds and it will reboot its self
Click to expand...
Click to collapse
it stops at the google screen and just freezes
How are you certain your recovery is gone? You might just be stuck in bootloop. Your best bet is to use toolkit to get you into recovery. Whether Twrp or CWM. From there youcan flash a new kernel and see if it fixes it or use it to restore a backup.
I had similar issue where it was stuck on boot screen. I ccouldn't enter recovery normally. Only way was hooking it up to a pc. Then using a toolkit to make the tablet go into recovery. Then from there, I could use recovery on tablet itself and restore a backup. From there I was good again. Problem solved for me.
Try one of the other toolkits, like Sambra one. Make sure drivers properly installed though.
demandarin said:
How are you certain your recovery is gone? You might just be stuck in bootloop. Your best bet is to use toolkit to get you into recovery. Whether Twrp or CWM. From there youcan flash a new kernel and see if it fixes it or use it to restore a backup.
I had similar issue where it was stuck on boot screen. I ccouldn't enter recovery normally. Only way was hooking it up to a pc. Then using a toolkit to make the tablet go into recovery. Then from there, I could use recovery on tablet itself and restore a backup. From there I was good again. Problem solved for me.
Try one of the other toolkits, like Sambra one. Make sure drivers properly installed though.
Click to expand...
Click to collapse
i tried to flash cwm back to the tablet and it said couldnt not mount sd card when i went on to it
can you post a link for that samba toolkit please?
wait i just remembered i dont have a backup, any other ways to get it up and working? please help
xfrancis14 said:
wait i just remembered i dont have a backup, any other ways to get it up and working? please help
Click to expand...
Click to collapse
It's an easy fix, just use wug's toolkit and flash the stock Nexus 7 image. It will be like brand new. I don't think you had a very major problem at all to begin with just a minor bootloop, but this far along I'd restore it to stock and start fresh.
CharliesTheMan said:
It's an easy fix, just use wug's toolkit and flash the stock Nexus 7 image. It will be like brand new. I don't think you had a very major problem at all to begin with just a minor bootloop, but this far along I'd restore it to stock and start fresh.
Click to expand...
Click to collapse
ive tried that and it gets to sending system and i leave it for like 10 15 minutes and it just still says that when i come back
xfrancis14 said:
ive tried that and it gets to sending system and i leave it for like 10 15 minutes and it just still says that when i come back
Click to expand...
Click to collapse
I had the same thing happen, but I ran it again and let it have its time and it went on and completed.
CharliesTheMan said:
I had the same thing happen, but I ran it again and let it have its time and it went on and completed.
Click to expand...
Click to collapse
ive tried a few times ill try again tho
UPDATE its still going its been bout since i posted this last post im gonna leave it still but do you think maybe its my computer?
still not working please help
Try using a different cable or re downloading the image file
Sent from Galaxy SIII
i didnt do anythiing and now when i try to flash back to stock it gets to the bootloader thing and finishes that and then it says missing system file 420 000 something kb and then cancels the operation i tried downloading a new system image from google and it still says the same thing help :/ im really worried, i dont wanna broken nexus 7 :/
Please copy paste the terminal (i.e. What you typed in, what outputs it gave you back)
Sent from my Nexus 7 "the most cost-effective iPad yet"
Try locking the boot loader and unlocking it again, then rooting flashing and so on..
Sent from my Nexus 7 using xda app-developers app
now i got it to the point where it goes back to sending system but it still stops, if i do relock the bootloader how would i unlock it? and if i did root it it wouldnt make a difference cause i cant get back to an os
Hey guys, I was running slim bean build 5. Went to update to build 6, followed the directions and now when I try to power on my phone, it vibrates about once every few seconds and the screen remains black. I cannot boot to my recovery, I tried to flash the stock ROM with Odin, it says its successful but the problem persists. Please help me! Did I hard brick it??
SGH-i337
f.rod123 said:
Hey guys, I was running slim bean build 5. Went to update to build 6, followed the directions and now when I try to power on my phone, it vibrates about once every few seconds and the screen remains black. I cannot boot to my recovery, I tried to flash the stock ROM with Odin, it says its successful but the problem persists. Please help me! Did I hard brick it??
SGH-i337
Click to expand...
Click to collapse
If you can boot, you can get to recovery. Hold down Power and Volume up until it reboots. release power and hold volume up until it gets past the blue "booting recovery" and then some more until recovery comes up. Then restore your nandroid that you made before this started.
alacrify said:
If you can boot, you can get to recovery. Hold down Power and Volume up until it reboots. release power and hold volume up until it gets past the blue "booting recovery" and then some more until recovery comes up. Then restore your nandroid that you made before this started.
Click to expand...
Click to collapse
When I do that there is nothing on my screen. It just keeps vibrating every few seconds. The only thing I have been able to get to show up on the screen is the "Downloading" green android bot.
f.rod123 said:
When I do that there is nothing on my screen. It just keeps vibrating every few seconds. The only thing I have been able to get to show up on the screen is the "Downloading" green android bot.
Click to expand...
Click to collapse
If you can get into download mode you are golden, get odin and stock firmware and odin back to stock. Google will point your way to the millions of how to odin back to stock threads
Sent from my SGH-M919 using xda premium
Manufactured consent said:
If you can get into download mode you are golden, get odin and stock firmware and odin back to stock. Google will point your way to the millions of how to odin back to stock threads
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
As my OP states, I have flashed the stock firmware with Odin (3x now). The progress bar finishes and it reboots but the screen just remains black and it vibrates. I did do a manual format in TWRP as the Slim Bean changelog states I should have done. I am freaking out If I bring it back to the store (its less than 30 days old) will they deny me a replacement? I can't see how they could tell I did anything to it if I just say "IDK what happened it just stopped working."
EDIT: I flashed both Slim Bean Build 6 and their Addon pack at the same time.
f.rod123 said:
As my OP states, I have flashed the stock firmware with Odin (3x now). The progress bar finishes and it reboots but the screen just remains black and it vibrates. I did do a manual format in TWRP as the Slim Bean changelog states I should have done. I am freaking out If I bring it back to the store (its less than 30 days old) will they deny me a replacement? I can't see how they could tell I did anything to it if I just say "IDK what happened it just stopped working."
EDIT: I flashed both Slim Bean Build 6 and their Addon pack at the same time.
Click to expand...
Click to collapse
You have to do a factory reset from your recovery, but getting into the recovery is all about timing. Pull the battery, put battery back in, hold power, home and volume up until it vibrates, as soon as you feel vibration, let go of power only... Then if you get into recovery, do a factory reset and reboot
Sent from my Nexus 7 using xda premium
Go figure :/
Manufactured consent said:
You have to do a factory reset from your recovery, but getting into the recovery is all about timing. Pull the battery, put battery back in, hold power, home and volume up until it vibrates, as soon as you feel vibration, let go of power only... Then if you get into recovery, do a factory reset and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
My phone is in the same boat. im about to go try and exchange it i got it like 5 days ago. tyed kies and odin.
kies dosint see my phone. odin wrights the stock back but still vibrates with blank screen. RECOVERY DOES NOT WORK!!!
not how matter you try its gone. I dont understand how odin isint fixing it. i went to instal kernal and after that phone went ape s**t
IT wont even show the SAMSUNG first logo just black screen with vibrating evey 4 secs.
if phone won't boot and it wont show anything on the screen just vibrating. do you think att is going to run me around. im within my 14day return policy. are they going to be able to tell what i did with nothing to see let alone Odinsaid it did right so that means even tho it wont boot the root is gone becasue its back to factoy but no boot.
thank you for you time and help. hopefully someone out there has an awnser.
4purple2haz0 said:
My phone is in the same boat. im about to go try and exchange it i got it like 5 days ago. tyed kies and odin.
kies dosint see my phone. odin wrights the stock back but still vibrates with blank screen. RECOVERY DOES NOT WORK!!!
not how matter you try its gone. I dont understand how odin isint fixing it. i went to instal kernal and after that phone went ape s**t
IT wont even show the SAMSUNG first logo just black screen with vibrating evey 4 secs.
if phone won't boot and it wont show anything on the screen just vibrating. do you think att is going to run me around. im within my 14day return policy. are they going to be able to tell what i did with nothing to see let alone Odinsaid it did right so that means even tho it wont boot the root is gone becasue its back to factoy but no boot.
thank you for you time and help. hopefully someone out there has an awnser.
Click to expand...
Click to collapse
Yeah, I'm going to go to AT&T later. No matter what I try, I cannot boot into recovery. Kies won't see it, Odin doesn't work. I'm within 30 days of my purchase so hopefully they'll replace it.
f.rod123 said:
Yeah, I'm going to go to AT&T later. No matter what I try, I cannot boot into recovery. Kies won't see it, Odin doesn't work. I'm within 30 days of my purchase so hopefully they'll replace it.
Click to expand...
Click to collapse
If its AT&T i think its 14 days now as to what i was told when i got it.
so there is no one that has figured this out. im seeing more about it but no one can figure it out.
PLZ let me know what happens at AT&T. im going after work at 7. untill then im looking every where for anwsers.
NOT GETTING SAMSUNG POST SCREEN
Can ATT tell with the phone just vibrating with nothing showing. you can get in to odin but thats it.
can AT&T tell with out seeing anything saying custom or SU.
DO they have a device that can detect the sytem in its state.
4purple2haz0 said:
If its AT&T i think its 14 days now as to what i was told when i got it.
so there is no one that has figured this out. im seeing more about it but no one can figure it out.
PLZ let me know what happens at AT&T. im going after work at 7. untill then im looking every where for anwsers.
NOT GETTING SAMSUNG POST SCREEN
Can ATT tell with the phone just vibrating with nothing showing. you can get in to odin but thats it.
can AT&T tell with out seeing anything saying custom or SU.
DO they have a device that can detect the sytem in its state.
Click to expand...
Click to collapse
REALLY!?! KNOW ONE ELSE have this problem and fixed it if not at least an awnser about the att thing.
do they have a for sure way of telling modification if the phone wont even boot to recovery or show the first SAMSUNG post spash.
want to find out befor going in there and looking like an idiot.
thank you
sorry for sounding demanding just frustrated :/
The employees at your local store won't have a clue or would even try to figure out the issue. Where the phone gets sent to for repair is a different story. I'm pretty sure those guys can tell the difference between a rooted phone and one that's not.
Thanks took it back and got another. The guys there were clueless trying to get into recovery and it wouldent work. Any one have this happen to them you have 14 days from purchased date. If your over the 14 day then im sorry to tell you that your phone could be stuck that way unless you send it out to get it fixed. Samsung will not help you with warrenty on this.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4purple2haz0 said:
REALLY!?! KNOW ONE ELSE have this problem and fixed it if not at least an awnser about the att thing.
do they have a for sure way of telling modification if the phone wont even boot to recovery or show the first SAMSUNG post spash.
want to find out befor going in there and looking like an idiot.
thank you
sorry for sounding demanding just frustrated :/
Click to expand...
Click to collapse
Well, I went back to best buy, tried to play it off like IDK what happend. Guy saw right through me and said "it looks like the phone was damaged while rooting" I admitted to it. Luckily he said Geek Squad Protection covers rooting errors. Because I was within 30 days of purchase, he let me sign up for it. So now I have to wait a week and make a claim for a new phone.
Cuz
4purple2haz0 said:
REALLY!?! KNOW ONE ELSE have this problem and fixed it if not at least an awnser about the att thing.
do they have a for sure way of telling modification if the phone wont even boot to recovery or show the first SAMSUNG post spash.
want to find out befor going in there and looking like an idiot.
thank you
sorry for sounding demanding just frustrated :/
Click to expand...
Click to collapse
They will prob replace it...
they only check certain things...
is not like the phone police will come running out the stockroom door when you enter the store.... but maybe they should, heh heh
Woop
Hhaha! "Golden" This guy knows :good:
Has anyone figured this out? Also, will AT&T replace it free of charge? I am stressed out now. I flashed the same Slim Bean, how the hell does it brick our devices beyond where even Odin cant restore? Does anyone have a boot loader for download maybe? I really need some help here, and would be nice for those in the future to figure out how to fix this
Tylor
You are in a month old thread. Would probably help giving some specifics aboyt you're issue
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
I did something really really stupid - i wiped evereything on my Find 5 with TWRP. I was trying to fix my not working Wifi in CM (in Color Rom and before installing it worked) and didn't really think trough what I was doing.
Now I'm stuck at the "Touchscreen firmware Update in progress"-Screen, so I can't enter Fastboot. Even a hard reset doesn't work (nothing happens). Can someone please help me? I am really desperate right now
Can you still get into recovery?
Sent from my Find 5 using XDA Premium 4 mobile app
Wait 15 Minutes
This is a known problem, wait about 5-10 minutes. I know it is scary for it hang for that long.
If it doesn't go into recovery on it's own after 10 minutes turn the phone off. Sometimes it gets stuck on the Touchscreen update screen Charge it if necessary.
Start it by holding the volume down and power to boot into recovery. It may take a long time.
Flash a 4.1 based version of Color Rom to get the correct modem back. This is why the WIFI wasn't working.
Reboot into recovery and flash Cyanogenmod WIFI should be working.
Thank you for your help! It worked, but I had to flash Color Rom 3305G, 3333L didn't work.
Glad to help
Xerionius said:
Thank you for your help! It worked, but I had to flash Color Rom 3305G, 3333L didn't work.
Click to expand...
Click to collapse
The phone is really finicky about recovery. I can't explain it. Happy to hear it is working and everything is back to normal.
technologyunit said:
The phone is really finicky about recovery. I can't explain it. Happy to hear it is working and everything is back to normal.
Click to expand...
Click to collapse
I had an Optimus Speed before I got my Oppo, the Optimus was very finicky about Baseband and RIL, the Oppo is nothing compared to this. And what I did was just stupid
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
scythefwd said:
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
Click to expand...
Click to collapse
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
lj50036 said:
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
Click to expand...
Click to collapse
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
scythefwd said:
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
Click to expand...
Click to collapse
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
charesa39 said:
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
Click to expand...
Click to collapse
Like hit them and let go, or till it reboots again?
scythefwd said:
Like hit them and let go, or till it reboots again?
Click to expand...
Click to collapse
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
charesa39 said:
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
Click to expand...
Click to collapse
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
scythefwd said:
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
Click to expand...
Click to collapse
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
charesa39 said:
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
Click to expand...
Click to collapse
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
scythefwd said:
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
Click to expand...
Click to collapse
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
charesa39 said:
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
scythefwd said:
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
Click to expand...
Click to collapse
Thx for taking the time to learn mate, Let us know when you get it back
Thx Josh