Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
fastboot
just check for fastboot. the rest is easy cheeze.
how much is a good deal ?
unlocked $300 (cad)
What should I check? Instruct me plz, I never had a nexus one or even a Droid phone before ... (coming from 2 years old HTC cruise, with WM 6.5 with an XDA rom ....)
If I meet the guy, how to I check that hes not selling me a bricked nexus lol ?
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Amritttt said:
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Click to expand...
Click to collapse
are you 100% ?
I dont mind working on it, I just want to make sure that it is reparable via software/roms.
ppl plz tell yours, im just about calling this guy, really dont wanna waste $300
what is its restarts so much, that I cant flash the rom or something? there's no way that that could be the case, right?
sold ... goddamit lol But I'll get one one way or another
I was having this happen to me a lot. I moved in to a new place with no cable or internet yet, so my N1 was under extremely heavy use. And when it was warm, it would get both the touch screen problem and the random reboots.
I was using pershoots 2.35 Kernal. I went back to the stock kernal and the phone has since been running a lot cooler. Zero reboots, touch screen responds correctly. I take the stock kernal stability over an OC kernal any day.
It's a kernel issue that can most likely be fixed by flashing a new
ROM/Kernel, however there is always a small chance that it is triggered by faulty hardware.
My Nexus had this Problem Was unfixable by software. Hardware defect. I wouldn't buy.
Still waiting for my swap unit
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
xxlikquidxx said:
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
Click to expand...
Click to collapse
all is not lost if you can still get into hboot:
Have you tried to restore these original files via adb?
boot boot.img
recovery.img
system.img
I have this problem now...
It keeps on rebooting and rebooting ... and just comes not forther than the flashing X..
I tried system wipe but this didnt help ( I installed a battery widget which wasn't for my rom)
how can i restore my nexus now?
Pleas help!
Edit: Found a way...
Unlock you phone, fastboot, clockworkmod(?) recovery and the select the nandroid backup...
about passimg (see lower) i have no clue
passimg FRG33...
Sent from my Nexus One using XDA App
Even though solved, something to keep in mind: Its probably a ROM (or kernel issue as they said), but I had a revolving X due to a bad battery too.
it can be solved
ViSK said:
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
Click to expand...
Click to collapse
4 color problem can be solved ..
Related
Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?
Shaihalud9 said:
Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?
Click to expand...
Click to collapse
Should have posted this in the q&a but try THIS post and we'll go from there.
I should have, but thanks, I will try that.
Shaihalud9 said:
I should have, but thanks, I will try that.
Click to expand...
Click to collapse
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App
Yellowcard8992 said:
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Rebooting the bootloader doesnt help, still getting Error 170, so hopefully flashing a new recovery from HBoot will.
Okay so copying the PC36IMG to my SDcard, the bootloader recognizes it, and reads it, and I get a progress bar on the right.... but no option to flash the image, and booting into recovery does nothing.
Im going to try an HBoot run of the PCIMG36 RUUs I found on another page... I dont mind going back to stock, I just want the damn phone to work.
Double post.
So I used the latest PC36IMG Signed zip from here: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu&page=7, and it went through, did all the updates, but when asked to reboot, which I did, I get a blinking yellow LED that goes solid, boots up, get the EVO 4G white splah for a few moments... then nothing.
Im hoping its just a dead battery. =\ Gonna try it again in a bit.
Nope. Still getting bootloops, even with the new PCIMG flashed. What the f*cking hell.
Hey Guys,
Nexus S the phone which I love the most and I do own this one from a long time.
Please read the whole thing don't ignore as it's toooo big.
Straight away to my issue. Thing is I've unlocked boot loader, rooted and I was using CM9 MOD. Everything was going fine. And i saw Cyber GR-MOD with more customization in the forums, I also flashed Cyber GR-MOD. Every thing was again fine with the Cyber GR, but I was facing few bugs in it. I was often wiping the data/doing factory reset. I was bored with Cyber GR. Then I saw ROM MIUI based on CM9 build with IMM76D. I was really attracted by UI of the MIUI ROM. I decided the flash that ROM. Before finding the MIUI ROM I was facing some problem with the Recovery. I was often getting error E:\ can't mount SD Card and the phone doesn't boot up. I did solve it by locking and unlocking the bootloader. Even after doing that I was facing that issue. Some how i managed to get into the recovery and flashed the MIUI Rom. After flashing i rebooted the device and the thing is i ain't get MIUI boot logo. I was getting CM9 Boot logo and the phone boots up with the Setup wizard sometime along with that i get pop ups for all the apps in the system getting forced closed or it won't boot up, it just keep loading with the CM9 logo. And am not able to use any of the ROM. Again now am stuck in that f***king [don't mind this ] E:\ Can't mount SD Card and when i tried to lock and unlock my bootloader, It did get locked successfully but when I tried to unlock it. It freezes in the Unlock bootloader menu. And am not even able to restore the phone or install a custom ROM coz of the error which i mentioned above. What eva ROM I install the only things it always boots up with CM9.
Please give me a permanent solution for that E:\ Can't mount SD card and to get my handset back with a new MIUI ROM
Please help me out guys. My dad will screw me up if he comes to know that my phone is bricked. LOL!! but this is the fact
U can force ur phone into recovery using cmd in windows.search in google how to do it.
I forget the command
After get into cwm u can wipe data.cache.dalvik and try flash stock rom.
Good luck
This made me lol.
I've seen a link with a probable fix for it but I'm on my phone and can't find it.
Sent from my Nexus S 4G using xda premium
You can try this.
You should try this post:
http://forum.xda-developers.com/showthread.php?t=1447040
There's a guide for unbricking nexus s.
Good luck
akabadnews said:
You can try this.
Click to expand...
Click to collapse
Yeah, give this a try. Nowadays, even if you aren't on a linux OS, you can set that up in maybe less than 30 minutes.
All the best, hope you can de-brick your phone.
I'll try and post the report.
How did it go?
own3dpl0x said:
I'll try and post the report.
Click to expand...
Click to collapse
How did it go? I'm curious, because I'm presently on CM9 nightlies (which is already 4.0.4 based), but am thinking of flashing the stock ICS 4.0.4 just for a look at it. But... don't want to brick out.
Please help!!
Followed all the steps.
But while resurrecting the device am getting error as SBL Injection Failure.
I don't know what to do.
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
hkbladelawhk said:
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
Click to expand...
Click to collapse
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
taodan said:
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=872441 << Flashed this.
So far, I've knocked my network to 2g and it's been fine. though not really much of a fix. And I had cleared all of the above using CWM prior to the attempted flash. I'd rather not have to wipe everything again just to get AmonRa. I've wiped quite a few times. Though did get something about /sd-ext missing when erasing via CWM. Also, I tried erasing recovery, and got this: "erasing 'recovery'... FAILED (remote: not allowed)". Not sure if that matters. Just seems that flashing via Fastboot has failed everytime. I flashed CWM via fastboot and that failed too, I ended up getting it working via RomManager.
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
jojogangsta said:
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
Click to expand...
Click to collapse
Yea, though I still feel like I'm getting intermittent reboots. IT's not an everyday use phone, so I'll have to see how it fares when I'm overseas.
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
joelshawdow said:
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Done and done. Still have a problem with boot looping. Google X with vibration, then goes black and does it again, and it loops like that indefinitely. Though this isn't new, been since I unlocked it....POS.
Deleted
Leave it in a freezer for a day no joke
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
my sugestion 2 u - use cm7.2. use 4ext touch recov, wipe all ur stuff, flash blackrose hboot with no repartitioning, flash cm7.2 rom, finally, stop b!tching!
ai6908 said:
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
Click to expand...
Click to collapse
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
hkbladelawhk said:
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
Click to expand...
Click to collapse
I never had any luck flashing recovery using fastboot either. Anyhow, it sounds like a motherboard issue to me. Sorry pal!
ai6908 said:
Anyhow, it sounds like a motherboard issue to me. Sorry pal!
Click to expand...
Click to collapse
This. The description fits overheating and overly sensitive to temperature CPU.
yon can flash another rom
yon can flash another rom
Still having bootup problems
Okay, sorry to bring this back up, but I am still having an issue with the phone booting. If I get the phone on, it's fine, doesn't randomly turn off or anything. However, if I try to reboot, power off and power back on for any reason....it becomes a pain to get back up and running. I usually have to do a couple battery pulls before it comes back up. Does the same thing. Hits the X, vibrates once like it's gonna turn on. Then a few seconds to a min later, goes black, then flashes the x and vibrates once again. It loops like this until I pull the battery and try again. Sometimes it takes a couple times to work. Its not the ROM either, because this is the issue I had when I first got the phone and did fastboot oem unlock. It would hang on stock. It's done it on all 3 ROMs I've tried. I don't wanna say fully it's a CPU issue, because I don't have issues once it's on.
Any new idears?
PS. I tried CM7, and I didn't like it. Not a fan of AOSP ironically enough.
The Nexus One will give off 7 Vibrations to indicate a hardware issue, we will just have to wait and see
i have a nexus thats completely stock( out of the box) worked fine for about a month, let the tablet die and has been unplugged for about a week. got it charged up and and would not turn on. using the nexus root toolkit i was able to get to turn on. unlocked the device( unlock logo below google icon on startup) was unable to get past that point. now finally i can get past the nexus boot logo but it gets stuck on aindroid is upgrading " optimizing app 1 of 11" i cant root using the root tool kit bc when i unlocked device it got rid of developer options ( by what the msg said before i unlocked). im simply trying to get my device to turn back on. i dont plan to root or install a rom, im fine with the stock rom. i just want to damn device to turn back on. when i was able to power on the device when i first got it i did upgrade to the newest jelly bean rom. any one can help me on this issue ??
thanks
Boot into temporary custom recovery using Nexus root toolkit(Advance menu). Now wipe cash and devlock than try rebooting into system. If it doesn't work you can try factory reset. Last but not the least will be Flash Stock + Unroot(Soft brick/boot loop).
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
dac2009 said:
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
Click to expand...
Click to collapse
If the factory reset doesn't work just go for the Flash. I don't think you are much worried about the data so it's not a big deal for you. and I'm quit sure this is gonna work. Best of luck.
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
dac2009 said:
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
Click to expand...
Click to collapse
Okay, that's weird!!!
Are you using Nexus Root Toolkit?? If yes are you using pre-downloaded android??
Try Automatically download + Extract.....
Last of all I'm really confused how there could be a problem when you got a fresh OS and Stock.
I agree with the messing thing that you told... Try checking and double checking everything... Check if you have selected the correct device or not.
And do a full wipe(including system) using TWRP before flashing again.
Edit: Make sure you are using the latest toolkit. You can get it from the link bellow.
http://forum.xda-developers.com/showthread.php?t=1766475
Try flash stock image throught toolkit.
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
dac2009 said:
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
Click to expand...
Click to collapse
I don't see a way how the problem still exists... :S
Whatever the problem is it's seems to be with android OS. But how it exists in completely new android. Sorry can't find a reason behind the problem. You can still try flashing any older android (like 4.1.2).
ok i got a zip of stock 4.1.2 and using the root tool kit i can install a zip via the twrp but it wont let me bc it says adb device not found and that developer options need to be turned on. im un able to turn it on bc i cant even get into the rom on the device.
thanks
ok i got it working. i was able to flash the older rom to my device and its working so far. no force closes yet.
thanks for everyone's help
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21%2018.37.24.jpg
dac2009 said:
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21 18.37.24.jpg
Click to expand...
Click to collapse
I can't just think of anything else. Just telling you the things that I'd have done if I were you.
* reinstall boot
* change kernel
* turn off the auto update of android.
* try some costume room.
Don't throw it out the window you call always donate it to me if you really wanna throw it or make a drop test video...
Last of all just don't lose hope keep trying. you'll find out something surely and share it with us.
Sent from my Nexus 7 using XDA Premium HD app
Daft question, but the few times you managed to get it running, was your Wifi on?
Sent from my GT-I9300 using xda app-developers app
yes my wifi was on and was able to stream . spotify among other things
Not the exact same situation, but I found certain Wifi router's would trip my nexus into reboots until I rooted
Sent from my GT-I9300 using xda app-developers app
Phone is stuck in "Android is upgrading. Optimizing application 1 of 1" HELP!!!!!!!!!
hey guys, my phone is stuck in "Android is upgrading. Optimizing application 1 of 1"
and all I can do is
1. apply sdcard/update.zip
2. reboot system now ( does NOT work coz it brings me back to optimizing apps )
3. apply update from external storage
4. wipe data / factory reset
5. wipe cache partition
6. apply update from cache
is there a way i can backup first all my files before factory resetting my phone (if thats the only option i have)????
help me please
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