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
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
So i flashed something that my phone doesnt agree with and now it gets stuck in boot. it gets to samsung screen then goes black and back to samsung over and over..
through clockwork i've wiped everything, tried to recover, tried to flash fresh roms, new kernels everything but i'm still stuck.. is this a situation to try odin? I don't have access to a pc so i just wanted to know if that is the next step cause its kinda of a pain in the ass to get a hold of one
illtema said:
So i flashed something that my phone doesnt agree with and now it gets stuck in boot. it gets to samsung screen then goes black and back to samsung over and over..
through clockwork i've wiped everything, tried to recover, tried to flash fresh roms, new kernels everything but i'm still stuck.. is this a situation to try odin? I don't have access to a pc so i just wanted to know if that is the next step cause its kinda of a pain in the ass to get a hold of one
Click to expand...
Click to collapse
what exactly did you flash to your phone that it didnt agree with
i flashed geek's uv superfast test and then followed his links to enable the BLN.. i think i might have flashed a bln mod for another device by accident but i'm having trouble finding the links i clicked so i'm not positive.. all i know is after i flashed it my boot animation changed to i 9000 and then it got stuck and then it got stuck in boot lock
to be frank, i can't find what the **** i did so i'm starting to think i was in a diff device forum or something... i musta flashed something for another device
illtema said:
i flashed geek's uv superfast test and then followed his links to enable the BLN.. i think i might have flashed a bln mod for another device by accident but i'm having trouble finding the links i clicked so i'm not positive.. all i know is after i flashed it my boot animation changed to i 9000 and then it got stuck and then it got stuck in boot lock
Click to expand...
Click to collapse
illtema said:
to be frank, i can't find what the **** i did so i'm starting to think i was in a diff device forum or something... i musta flashed something for another device
Click to expand...
Click to collapse
yeah you are pretty much screwed
screwed as in i should go to verizon w/ a sob story or screwed as in try odin
Couldn't you use Odin to restore? Or have you already tried that?
yeah man just revert to stock via Odin . Youre fine , happens to everyone at some point . Get back on that Android horse and ride it haha .
Yes, use odin.
If flashing other kernels doesn't fix this, (ie you still get stuck after the Verizon logo with lit buttons) let me know. I've got a trick up my sleeve for this, but I've only seen it happen twice, it's pretty rare.
i'm not proud of myself but i went to verizon and they gave me a brand new device...
illtema said:
i'm not proud of myself but i went to verizon and they gave me a brand new device...
Click to expand...
Click to collapse
if you plan to root/mod this device dont put other sgs firmware on it
illtema said:
i'm not proud of myself but i went to verizon and they gave me a brand new device...
Click to expand...
Click to collapse
awwwww wheres the fun in that XD
OK I did the same thing last week. I fixed it by running voodoo uninstaller. Don't know why it worked or how but I was desperate after being without a phone for 2 days. Then that afternoon my replacement showed up via fedex
Sent from my SCH-I500 using XDA App
hey guys. im trying to be a good guy and help out a friend who is currently working on his phone. ok now lemme get in every detail as much as possible as you guys can fully understand what we're doing and what we've been done.
his phone is rooted. with s-off. now we tried flashing cm7 last night. did everything right. full wipe and all of that. so.. cm7 did finish the installation. it went thru the white mytouch4g screen, then onto the cm7 blue circle splash screen. after that it asked him all of his info to login to google. it was working for a good 2 hours. later that night, he told me he took out the battery to restart his phone. when he restarted.. white screen finished loading. but on the blue cm7 circle, it stayed there forever.
now im not sure what he did wrong since he told me he just wanted to restart his phone. we cant even go back since it gets stuck on the blue cm7 splash screen. i really really really need your help guys. maybe you guys can private message me or hit me up directly on my email. i would greatly appreciate all the help. i tried searching and searching and all i got was to go thru rom manager, but how are we gonna do that if we cant even get the phone to boot up correctly. thanks in advanced guys.
Sent you a pm
Sent from my HTC Glacier using XDA App
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
What's the point in searching for it it means you bricked
cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
tvotony said:
Sent you a pm
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ok i will try and see what he says. ill pm you back tony. thanks a lot.
cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
my bad i forgot to answer your question. ok we tried reflashing everything. nothing of that kind of error showed up. it just said complete. then when we tried booting up the phone.. it just got stuck on the blue circle thing.
tony, i sent you an email. anyone else willing to help?
i was thinking.. maybe the cm7 that we downloaded was corrupt? he said he has clockwork version 5.X.X.X
not sure if thats gonna make a difference but yeah. also since we cant go to the phone since it gets stuck on the blue circle, we tried flashing cm7. in the end, the last line says "installation aborted"
so right now, im completely clueless. i have searched everywhere and tried other methods to see what will work. my phone is rooted with royal ginger and everything is fine with it. i have already restarted maybe 10x the last couple of hours trying to help my friend.
Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base
zelendel said:
Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base
Click to expand...
Click to collapse
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.
beryenbeh said:
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.
Click to expand...
Click to collapse
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.
zelendel said:
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.
Click to expand...
Click to collapse
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
Best bet would be to redownload the rom, boot into recovery and mount it so you can copy the new rom zip to the sd card. Do a full wipe and then reflash the rom. Other then that his only chance maybe going back to a stock rom and doing a clean rom flash just in case
help
beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..
underyourskyn said:
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..
Click to expand...
Click to collapse
i followed everything correctly and accurately. i even had him double check what i was doing to make sure. we rooted perfectly and flashed cm7 without a problem. i am not sure what happened when he restarted his phone.
can any of you guys speak to me directly? maybe via aim or any kind of instant messenger? i really wanna help him fix this problem but im not sure what else to do.
how did you root the phone to begin with?
neidlinger said:
how did you root the phone to begin with?
Click to expand...
Click to collapse
this way..
http://forum.xda-developers.com/showthread.php?t=858996
tvotony said:
What's the point in searching for it it means you bricked
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Cause me & a couple other people were able to recover frm those errors with the pd15 zip file... Some people were lucky..
Sent from my HTC Glacier using xda premium
beryenbeh said:
this way..
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.
Please look at the Glacier Wiki, Troubleshooting section. Link in my signature.
thanks a lot. hopefully his emmc isnt the problem. i checked his hboot and it says 0.86.0000 not sure if that rings a bell to any of you guys. ill keep reading more information and a possible solution. i read one that says to update the PDIMG file or whatever.. and then re-flash RG3.0. will try this one, hope itll work. once again, thanks for all the help guys. really appreciate it.
Rillusion08 said:
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.
Click to expand...
Click to collapse
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
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